IBM Improves the Handling of the Inactivity Timeout

The inactive job time-out (QINACTITV) system value defines the minimum amount of time that an interactive job can be inactive before an action is taken. The action that is taken is defined by the inactive job message queue (QINACTMSGQ) system value. A related system value, time interval before disconnected job ends (QDSCJOBITV), defines how long a job can be disconnected before the job is ended.


IBM i Simplifies Leap Year

By now, you probably have already heard that this year is a leap year. And you have a good understanding of what a leap year is and why we have them. But if you hadn’t already heard about 2012 being a leap year, or didn’t have a calendar handy, would you know how to determine which years have an extra day in February? If your answer is, “That’s simple! Just divide the year by 4 and if there is no remainder, it’s a leap year,” you would be right…most of the time. But there’s more to it than that.


Interrupt Job Exit – Invoking a Program in Another Job

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.


Job Log Output

Last week I wrote about Job Log Pending. With job log pending, you do not have to write job logs to spooled files.

At the end of that blog, I mentioned how you can use the Log Output (QLOGOUTPUT) system value or job attribute to take advantage of job log pending. This week, I’ll explain the values available for “Log output” and give some general recommendations.