z/OS MVS System Codes
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


075

z/OS MVS System Codes
SA38-0665-00

075

Explanation

A program running in supervisor state, key 0 issued a SCHEDULE macro to schedule a service request block (SRB). The system checked the acronym in the address space control block (ASCB) pointed to by SRBASCB. The acronym failed the check. Possible reasons are:
  • The issuer of the SCHEDULE macro put an incorrect address into SRBASCB. Consequently, SRBASCB did not point to a valid ASCB.
  • SRBASCB pointed to a valid ASCB, but the ASCB has gone away normally or abnormally.
  • SRBASCB pointed to a valid ASCB, but the ASCB was overlaid.

Register 14 contains the value from SRBASCB. Register 15 at the time of error points to the SRB that was being scheduled.

System action

The system ends processing of the SCHEDULE macro. The system may write an SVC dump, a logrec data set error record, or both.

Operator response

If the system programmer asks for an SVC dump, set the following SLIP trap:
SLIP SET,ENABLE,COMP=075,ACTION=SVCD,END

System programmer response

Do the following:
  1. If an SVC dump is not produced with the abend, ask the operator to set a SLIP trap to obtain an SVC dump.
  2. Examine SRBASCB to see if it contains a valid address. Check for an incorrect address in the SRBASCB field. The address in SRBASCB is not valid if:
    • It is all zeros
    • It does not end in X'00' or X'80'
    • It is not an address in the system queue area (SQA)
    If the address in SRBASCB does not look like a valid address, search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM® Support Center. Provide all problem data collected.
  3. If SRBASCB looks like a valid ASCB address, check the address space vector table (ASVT) for this address. The ASVT contains a list of ASCB addresses. The CVTASVT field of the communications vector table (CVT) points to the ASVT. ASVTENTY begins the ASCB addresses. Scan for the address that is in SRBASCB.
  4. If the address in SRBASCB is in the ASVT, then the ASCB pointed to by SRBASCB has been overlaid. See if you recognize the overlay by looking for any EBCDIC eye-catchers around the overlay. Search problem reporting data bases for a fix for the problem. Include in the search argument:
    • EBCDIC eye-catcher that is a module name: PIDS/cccccccc
    • Abend X'075': AB/S075
    • Overlay of the ASCB: OVS/ASCB

    The size and content of the overlay can also be added to the search argument.

    If no fix exists, contact the supervisor control component group at the IBM Support Center. Provide data collected in previous steps and, if available, the logrec data set error record.

  5. If the address in SRBASCB cannot be found in the ASVT, then either:
    • The ASCB was deleted when the address space went away abnormally.
    • The ASCB went away normally.
    • The ASCB is not valid. The issuer of the SCHEDULE macro put a bad address into SRBASCB.
    Search problem reporting databases for a fix for the problem. If no fix exists, contact the supervisor control component group at the IBM Support Center. Provide data collected in previous steps and, if available, the logrec data set error record.

Source

Supervisor control

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014