Guaranteeing an end to QINTER

["Burns, Bryan" <Bryan_Burns@xxxxxxxxxxxx>]

Just want to confirm that, even if you specify ENDSBS SBS(QINTER) as
*IMMED, that's no guarantee that QINTER will end.  Because part of the
ENDSBS is an ENDJOB, which sometimes hangs?  For example, perhaps the
following could occur:
 
 
Received call at my home at 4:50 AM.
Using a console session from home, I observed that QINTER was still in
ENDING status although job started at 12:03 AM.
Observed only one job in QINTER (Job SN77, still in ENDING STATUS).
Drove into work and called IBM at 6 AM.
While waiting for IBM to call back, observed that SN77 workstation (a
thin client running TermPro emulation) had a bar code scanner on the
keyboard and the display showed JOB ENDING and was input inhibited.
Closed the session.
Varied off device and started QINTER at 6:20 AM.
 
 
And the only way to prevent this from occurring again is to ensure users
never put a bar code scanner on a keyboard when they don't sign off??
 
TIA
 
Bryan Burns