SMP/E for z/OS Messages, Codes, and Diagnosis
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Recovering from x37 abends

SMP/E for z/OS Messages, Codes, and Diagnosis
GA32-0883-01

You can often recover from x37 abends by using the following methods:
  • If an SMP/E command fails because there is not enough space, check if the COMPRESS operand is allowed and was specified for that command. If the COMPRESS operand is valid, and if it was not specified the last time, rerun the SMP/E command with COMPRESS.
  • To obtain additional space in the SMPLOG data set, use one of the following methods:
    • Allocate a new SMPLOG data set and create a backup copy of the old SMPLOG data set, retaining it according to your usual recovery procedures.
    • Create a backup copy of the old SMPLOG, and retain it according to your usual recovery procedures. The next time you run SMP/E commands, specify DISP=OLD for SMPLOG. This overlays the contents of the old SMPLOG that you saved.

      You must specify DISP=MOD every time you run SMP/E, or you will continue to overlay the SMPLOG every time SMP/E commands are processed.

    Note: You can also allocate an alternative SMPLOG data set, SMPLOGA, to be used when the primary SMPLOG data set is full. See SMP/E for z/OS Reference for more information.
  • To obtain additional space for the target libraries or the distribution libraries, allocate a new, larger data set and copy the old data set that is out of space into the new data set.
  • To obtain additional space for the SMPCSI data set, you can do one of the following:
    • Allocate a new, larger CSI and copy the old data set that is out of space into the new one. (You can use the AMS REPRO command to copy the old CSI into a new, larger CSI.)
    • Use the AMS ALTER ADDVOLUMES command to add another volume to the CSI.
    • Use the AMS IMPORT and EXPORT commands to move the old CSI to a new, larger CSI.
    Note: If the job fails again after you have taken steps to get more space, the reason could be that SMP/E updated or created CSI entries before processing stopped for the original abend. If this was the case, do one of the following:
    • Restore your CSI with a previously made backup, or
    • Check which element entries (including LMOD entries) were affected by the processing. The Element Summary report from your first attempt to run the job will help you with this step. Then use UCLIN to undo changes to updated entries and to delete any entries that were created and rerun the job.
  • To obtain additional space in the SMPMTS, SMPPTS, SMPSCDS, or SMPSTS data set, use one of the following methods:
    • Run the CLEANUP command to delete unnecessary entries from SMPMTS, SMPSTS, or SMPSCDS. You may need to do this when you apply SYSMODs after accepting them, or when you accept SYSMODs that were applied to a group of target libraries built from the same distribution library.
    • Run the ACCEPT command or the REJECT command for any SYSMODs that have not been accepted. On the next ACCEPT or REJECT command you process, specify the COMPRESS operand with a value of SMPMTS, SMPPTS, or SMPSTS. For ACCEPT processing, you must specify PURGE in the OPTIONS entry that is in effect.
    • If no SYSMODs are candidates for an ACCEPT or REJECT command, allocate a new, larger data set, and copy the old data set that is out of space into the new data set.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014