Possible job hang on V4

If you're running V4 I would highly recommend you install PTF SF47821
(V4R1 - not on a cum package), or SF46473 (on cum package C8041420).
We had a job that was hung in EOJ processing (eating about 29% of CPU
cycles on our S10-2118).  Any other job that attempted to do an ENDJOB
against it would just loop, logging MCH5802 every 60 seconds.

Message ID . . . . . . :   MCH5802       Severity . . . . . . . :   20

Date sent  . . . . . . :   04/24/98      Time sent  . . . . . . :
18:06:31 
Message type . . . . . :   Escape

>From program . . . . . . . . . :   RmslLockMiObject

  Instruction  . . . . . . . . :     0010D0

To program . . . . . . . . . . :   QSPCNJOB

  To library . . . . . . . . . :     QSYS

  Instruction  . . . . . . . . :     002D

Coded character set ID . . . . :   65535

Message . . . . :   Lock operation for object QSPSCB not satisfied.

Cause . . . . . :   The lock operation was not satisfied for object
QSPSCB in
  the specified time interval of 60 seconds.


Of course an ENDSBS QINTER also hung because this job wouldn't go away.

I had tried ENDJOBABN against the original hung job but at first it
wouldn't take.  (It did when I tried it again about 12 hours later, and
QINTER ended normally, so I did an ENDSYS as per PTF cover letter,
applied SF47821, and restarted controlling subsystem).

Here's the APAR:

Item SA71103 

  APAR Identifier ...... SA71103       Last Changed..98/04/14  
  OSP-QSPCHJOB LOOPING CAUSING MCH5802 FOR WRKOUTQ OR DSPSPLF
 
 
  Symptom ...... MS MSGMCH5802        Status ........... CLOSED  PER
  Severity ................... 2      Date Closed ......... 98/01/27
  Component .......... 5769SS1SP      Duplicate of ........
  Reported Release ......... 420      Fixed Release ............ 999
  Component Name 5769 PRINT/SPOO      Special Notice
  Current Target Date ..98/01/29      Flags
  SCP ...................
  Platform ............
 
  Status Detail: SHIPMENT - Packaged solution is available for
                            shipment.
 
  PE PTF List:
 
  PTF List:
  Release 410   : SF47821 available 98/04/14 (1000 )
  Release 420   : SF46473 available 98/02/06 (8041 )
 
 
  Parent APAR:
  Child APAR list:
 
 
  ERROR DESCRIPTION:
   QSPCHJOB caused a tight loop during the termination of a job
   causing locks to be left on the job's SCB and on the outq
   QEZDEBUG.
 
  LOCAL FIX:
 
   PROBLEM SUMMARY:
  QSPCHJOB is looping indefinitely during the termination of a
  job.  During the looping process, QSPCHJOB holds an exclusive
  lock on the SCB of the job that is ending.  Any attempt to
  display a spooled file associated with that job results in
  MSGMCH5802.
 
  This looping condition will also hold an exclusive lock on an
  output queue.  This will result in MSGMCH5802 when attempting a
  WRKOUTQ on that particular output queue.
 
  PROBLEM CONCLUSION:
  An AS/400 system program has been changed to handle the scenario
  that caused QSPCHJOB to loop.
 
   TEMPORARY FIX:
 
   COMMENTS:
 
   MODULES/MACROS:   QSPCHJOB
 
   SRLS:      NONE
  
  RTN CODES:
 
   CIRCUMVENTION:
  When spooled files are created, use the default spooled output
  schedule of *FILEEND.  QSPCHJOB is only called during job
  termination if that particular job has one or more spooled files
  created with SCHEDULE(*JOBEND).
  
  MESSAGE TO SUBMITTER: UPDATED 04/08/98


Neil Palmer                                AS/400~~~~~      
NxTrend Technology - Canada   ____________          ___  ~     
Thornhill, Ontario,  Canada   |OOOOOOOOOO| ________  o|__||=   
Phone: (905) 731-9000  x238   |__________|_|______|_|______)   
Cell.: (416) 565-1682  x238    oo      oo   oo  oo   OOOo=o\   
Fax:   (905) 731-9202       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
mailto:NPalmer@NxTrend.com    AS/400  The Ultimate Business Server      
http://www.NxTrend.com

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---