Information to collect for critical path problems

Information to collect when you encounter critical path problems

If you receive an error message related to critical path problems, gather the following information:
  1. When possible, reconstruct the sequence of events that caused the problem. Include any commands entered just before the problem occurred.
    1. What was the first indication of the problem?
    2. What were you trying to do?
    3. What should have happened?
    4. What did happen?
  2. Before running the daily plan batch, collect an APAR tape including the new current plan and a console dump including data spaces as shown below: 
    DUMP COMM=(reason for taking dump)
R xx,JOBNAME=(ZZZZ),CONT
R xx,DSPNAME=(‘ZZZZ'.*),CONT
R xx,SDATA=(COUPLE,ALLNUC,LPA,LSQA,PSA,RGN,SQA,TRT,
CSA,GRSQ,XESDATA,WLM),END
    where:
    xx
    Specify the replay number ID.
    ZZZZ
    Specify the name of the controller.