Procedure

  1. If the failure involves a DFSMSdfp component and ISMF does not seem to be involved, go to Type-of-failure keyword.
  2. If the failure seems related to ISMF, use Figure 1 to identify the failing function, and continue.
    1. Use this table together with the associated entry in the ISPF log to isolate the failure source. ISMF's use of the ISPF log. Locate the SERVICE item in the failure-related log entry. Each SERVICE has its own description for failure-related return codes and reason codes.
    2. If the job control language (JCL) that ISMF created for a DFSMSdss or ICKDSF function is correct, or if DFSMShsm is in control, and the failure occurs in either DFSMSdss or DFSMShsm, use z/OS DFSMSdss Storage Administration or z/OS DFSMShsm Diagnosis, as appropriate. If the failure occurs in DFSMSrmm, use the z/OS DFSMSrmm Diagnosis Guide.
    3. If the failure involves a reason code associated with one of the DASD common services, use the DASD common services-specific sections of the keyword build procedures and see DASD common services diagnostic aids to gather additional failure-related information.
    4. To begin developing the keyword string, go to Type-of-failure keyword.
Figure 1. ISMF Failure Isolation Aid
Areas of failure are: ISMF-related functions (Main Dialog, Profile Application, Data Set Application, Volume Applications, Storage Group Application, ACS Application, CDS Application, Aggregate Group Application, Library Management Applications, Data Collection Application, and List Application), DFSORT/ISMF-related functions, ICKDSF-related functions, DASD common services, DFSMSdss/ISMF-related functions (SORTREC), ICKDSF related functions, DASD Common Services, DFSMSdss/ISMF-related functions, DFSMShsm/ISMF-related functions, DFSMSrmm and NaviQuest/ISMF-rleated functions