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.