Determining the Size of QTEMP
In the 7.2 release, the List Job (QUSLJOB) and the Open List of Jobs (QGYOLJOB) APIs were enhanced to return the size of QTEMP.
(more…)In the 7.2 release, the List Job (QUSLJOB) and the Open List of Jobs (QGYOLJOB) APIs were enhanced to return the size of QTEMP.
(more…)In the 7.2 release, IBM made many changes to improve temporary storage tracking. I’ve written about these enhancements in IBM i 7.2 Improved Temporary Storage Tracking Part 1, Part2, and Part 3 blogs. You may also want to reread the blog, Understanding Disk Space Usage, which reviews IBM i temporary and permanent storage concepts.
In addition to improving temporary storage tracking, IBM also made some improvements for permanent storage tracking in the 7.2 release. This post reviews three of them.
(more…)In last week’s blog on QTEMP, I mentioned at the very end that I’d write about the interrupt job exit program this week.
Introduced in the 5.4 release, the interrupt job capability allows a program to be run within a specified job. A user wanting to run a program in a different job prior to 5.4 was essentially limited to using the submit job command to start a new job to run the program; however, sometimes there was a need to run a program in a job that had already been started. The interrupt job support enabled this capability.
(more…)I received a question regarding the QTEMP library, prompted by the post Understanding Disk Space Usage. I thought sharing the question and providing the answer in this week’s blog would be helpful for everyone, as well as expanding upon how the system views and manages QTEMP when it comes to disk space usage.
(more…)