Creation of LOGREC data set entries
When the RACF® subsystem address space requests an MVS™ system resource or uses an MVS system service and is unsuccessful, this failure is recorded. If the failure is not recorded by MVS, RACF puts the symptom records in the LOGREC data set.
z/OS MVS Programming: Assembler Services Guide categorizes information contained within the symptom records as:
- Component Data − This identifies the application in which the error occurred (that is, 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.
- Variable Data − This contains diagnostic data, such as portions of data areas or parameter lists pertinent to the error.
| SDB key literal | Usage |
|---|---|
| RIDS/ | Module CSECT name |
| RIDS/ | Load module name |
| 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 that the symptom record contains.
| SDB key literal | Usage |
|---|---|
| ADRS/ | Offset of service that failed |
Table 3 shows the contents of the variable symptom string that the symptom record contains.
| Field | Description |
|---|---|
| LUNAME | APPC partner LUNAME |
| TPNAME | APPC partner TPNAME |
| MODENAME | APPC partner MODE NAME |
| ADDRESS | TCP partner host address |
| PORTNUM | TCP listener port number |
| MISC STRING | Additional information for some service failures |
Table 4 shows the additional information that the symptom record contains.
| Field | Value |
|---|---|
| COMPDSC | RACF subsystem address space |
| PROBLEM | Name of failing service |
| SERVLEV | Service level of module |
| COMPID | Component ID (5752XXH00) |
| COMPLEV | Component level (260) |