Re: Terminated Interactive Job Impacts Nightly Processing

On 07 Jun 2013 09:11, Victor Hunt wrote:

<<SNIP>>

On Wednesday at 16:45, a user went into this program using his
client (iAccess for Windows), did some work, and then hit the "red X"
and closed the session (he normally doesn't do this). There were no
messages of any kind in QSYSOPR or in DSPLOG for this session.

Our nightly process runs at 21:00, that night a number of processes
did not complete due to locked files (mostly file reorgs). At 00:15
on Thursday we see an entry in DSPLOG where the users session is
finally ended due to the QINACTITV time-out, which is set to 150
minutes. QINACTMSGQ is set to *ENDJOB.

The job was likely in DSC status per the "Device Recovery Action" (DEVRCYACN) for the job; that *may* resolve from the QDEVRCYACN system value, but could come from elsewhere or changed within a job with CHGJOB. I would have expected however, that the DSPLOG JOB(the_job) would have revealed the disconnect activity. Perhaps that effect was not recorded, and thus confuses the [understanding of the] issue. The subsystem monitor job however, I believe would have a message about the job being disconnected, IIRC.

In addition, we have a job that runs 15 minutes before our nightly
job that kills all the jobs in QINTER. This job reported no running
jobs in QINTER Wednesday night. <<SNIP>>

Verify that the program does not overlook jobs in the Disconnected status.