OA36460: AFTER ACTIVATING AN SCDS, SOME JOBS MAY REMAIN HUNG IN CI(RESCHEDULED) FOREVER

APAR status

• Closed as suggestion for future release.

Error description

• External symptoms:
  After a SMS configuration change (IGD008I) some jobs might stay
  in CI(RESCHEDULED) "waiting for SMS resources".
  Impact to customer:
  Jobs do not start, requiring manual intervention
  Analysis:
   IATGRJS is the one that will put such jobs into that status
  based on the return code from the CI DSP. IATGRJS will also
  remove these jobs from the SMS wait for resources queue when
  we receive the ENF signal from SMS.
  
  Verification steps:
  1)  SMS configuration change issued
  2)  Jobs submitted to JES3 do not start, inquiry shows
  a status of CI RESCHEDULED
  3)  SMS signal trace shows SMS signalled resources are available
  at the same time that JES3 is receiving a signal indicating the
  resource isn't available
  
  The projected closing code for this APAR is SUG.
  
  This requirement has been implemented in the base of
  release V2R1.
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• After an SMS (Storage Management Subsystem) reconfiguration, a
  user noticed that a job submitted during the reconfiguration
  did not run because it was on the SMS wait queue.
  
  During the job's converter/interpreter (CI) phase, a required
  resource was unavailable and the job was marked for the SMS
  wait queue.  Between the time the job was marked and when it
  was placed on the queue, SMS signalled that the  resource was
  available, and JES3 received and processed the signal. However,
  because the job was already destined for the SMS wait queue,
  it was put on the queue where it remained.
  
  To avoid stranding jobs for this reason, the Job Scheduling
  Service (JSS) needs to coordinate job CI processing and
  SMS signal processing.
  
  This change is accepted as a requirement for a future change
  in the product design.  An internal request has been opened
  to deliver this function in a future release of JES3.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

  OA36420

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels