Procedure

  1. The failure indications should enable you to establish whether ISMF is involved or not. If you suspect a failure in ISMF, see ISMF—Wait and loop keywords.
  2. For all other DFSMSdfp components, obtain the following:
    • A console dump initiated by the MVS DUMP command before the operator cancels the job.
    • A copy of the SYS1.LOGREC data set. Use IEBGENER to copy the SYS1.LOGREC data set to a standard label tape. This data set contains the event history leading up to the wait problem.
  3. Using the dump, scan the RBs to see if a WAIT SVC was issued. The INTCODE field of the RB contains 0001 for jobs that issued a WAIT SVC, if the high-order byte of the LINK field of the RB contains a nonzero value, indicating the number of events being waited or suspended on.
  4. If these fields do not indicate a WAIT condition, assume that the failure is a LOOP.
  5. In either case, record the current PSW address in the waiting or looping RB's OPSW field as the failing address. You will use it to determine the failing module. Specify either the WAIT keyword or the LOOP keyword.
    You might find the following information useful in isolating the source of a LOOP failure to a specific module:
    • If the FLCDE field for the RB is nonzero, it points to a cde entry of the entry point of a load module. That load module might contain the failing CSECT.
    • A system branch trace (invoked by the operator from the console). This makes an entry in the system trace table for every successful branch instruction. (See z/OS MVS Diagnosis: Tools and Service Aids for the format of the system trace table.)
    • An AMBLIST listing or SPZAP dump of a CSECT or CSECTs that you suspect (see z/OS MVS Diagnosis: Tools and Service Aids).
  6. A wait on the ENQ and DEQ major resource names IGDCDS, IGDCDSXS, or SYSZIGDI, indicates that the Storage Management Subsystem (SMS) is involved in the failure. Record the indicated major resource name and the minor resource name as modifier keywords on the Keyword worksheet.
  7. A wait on the ENQ/DEQ major resource names SYSZIGW0 and SYSZIGW1 indicates that the program manager binder, HFS, or PDSE is involved in the failure. Record the indicated major resource name and the minor resource name as modifier keywords on the Keyword worksheet.
  8. For VSAM Record Management, see VSAM record management—wait and loop keywords.
  9. For all other DFSMSdfp components, see Module keyword.
Parent topic: Symptoms of the failure