z/OS Security Server RACF Diagnosis Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Error recording for callable services

z/OS Security Server RACF Diagnosis Guide
GA32-0886-00

Environmental errors must be reported to allow their correction. Some of the RACF® callable services create symptom records for errors and store them in the LOGREC data set.

z/OS MVS Programming: Assembler Services Guide categorizes information contained in the symptom records as:
  • Component data

    This identifies the application in which the error occurred (that is, the RACF subsystem address space).

  • Primary SDB symptoms

    This contains the primary string of problem symptoms. This data is used for duplicate problem recognition (see Table 1).

  • Secondary SDB symptoms

    This contains any additional diagnostic values saved at the time of the error. See Table 2.

  • Variable data

    This contains diagnostic data, such as portions of data areas or parameter lists pertinent to the error. See Table 3.

Table 1 shows the contents of the primary symptom string in the symptom record.
Table 1. Contents of primary symptom string for a callable service error
SDB key literal Usage
RIDS/ Module CSECT name
RIDS/ Load module name (IRRRFR10)
PCSS/ System service (MVS™ or RACF macro) that failed
PRCS/ Return code from service
PRCS/ Reason code from service (if no reason code is available, this field contains a value of zero)
Table 2 shows the contents of the secondary symptom string.
Table 2. Contents of secondary symptom string for a callable service error
SDB key literal Usage
ADRS/ Offset of service that failed
Table 3 shows the additional information that the symptom record contains.
Table 3. Additional LOGREC data for a callable service error
Field Value
COMPDSC RACF callable service
PROBLEM Name of failing service
SERVLEV Service level of module
COMPID Component ID (5752XXH00)
COMPLEV Component level (260)

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014