The structured symptoms consist of a prefix keyword, which identifies the type of symptom, followed by a slash (/) and the data portion of the symptom.
For example, the following is a structured symptom string for a message identifier of CSQC223D:
MS/CSQC223D
The following list shows the structured symptom strings:
Keyword | Meaning |
---|---|
AB | Abend code. |
FLDS | Name of a field or control block involved with the problem. |
LVLS | Level of the base system or licensed program. |
MS | Message identifier. |
OPCS | Operation code (opcode) for software, such as an assembler-language opcode. |
PCSS | Program command or other software statement, such as JCL, a parameter, or a data set name. |
PIDS | Program identifier for a component involved in the problem. |
PRCS | Program return code, generated by software, including reason codes and condition codes. |
PTFS | Program temporary fix (PTF) for software associated with a problem. |
PUBS | Identifier of a publication associated with a problem. |
RECS | Record associated with a problem. |
REGS | Register for a software program associated with a problem. The value can be the register/PSW difference (rrddd), which the STATUS FAILDATA subcommand of IPCS provides for abends. The difference (ddd) is a hexadecimal offset from a probable base register or branch register (rr). |
RIDS | Routine identifier, such as the name of a CSECT or subroutine.
If the RIDS/ value has no suffix, the value is a CSECT name. The following
suffixes are supported:
|
VALU | Value in a field or register. One of the following
qualifiers is required as the first character of the value:
|
WS | Wait state code issued by the system, or device-issued
wait code. One of the following qualifiers is required as the first character
of the value:
|
For more information about which prefix keyword to use for which type of symptom, see Appendix A. SDB format symptom-to-keyword cross reference.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csqsaq03100 |