What type of program check occurred?

Knowing what type of program check occurred can be helpful to find the cause of the error. The type of program check is indicated by the program interrupt code (PIC), which you can find in the program status word (PSW) at the start of the transaction dump.

For details about the PSW, see z/Architecture Principles of Operation.
PIC
PIC explanation
1
Operation exception - incorrect operation attempted.
Possible causes are as follows:
  • Overlaid program
  • Overlaid register save area, causing incorrect branch
  • Resource unavailable, but program logic assumed valid address returned and took inappropriate action
  • Incorrect branch to data that contains no instruction known to the machine
  • In an assembler-language program, a base register was inadvertently changed
2
Privileged operation - this program is not authorized to execute this instruction.
A possible cause is as follows:
  • Incorrect branch to this code. Possible reasons for this situation are as follows:
    • Overlaid register save area
    • Program overlaid by data that contains the privileged operation code
3
Execution exception - you are not allowed to EXECUTE an EXECUTE instruction.
Possible causes are as follows:
  • Incorrect branch to this code
  • Incorrect register contents. Possible reasons for this situation are as follows:
    • Overlaid register save area
    • Program overlaid by data that contains the incorrect instruction
    • Incorrect program logic
4
Protection exception - read or write access violation has occurred.
Possible causes are as follows:
  • Resource unavailable, and return code not checked. Program logic assumed valid address returned and took inappropriate action.
  • Incorrect interface parameters to another program or subsystem (for example, VSAM or DL/I).
  • Overlaid register save area, causing incorrect reference to data.
  • In an assembler-language program, incorrect initialization or modification of a register used to address data.
  • Attempt to access internal control blocks illegally or use a CICS® system or application programming macro call.
  • Attempt to write to storage for which the application does not have an adequate key. For example, in a CICS system with storage protection, an application running in USER key attempts to write to the CDSA, RDSA, ECDSA, ERDSA, ETDSA, or GCDSA.
  • Attempt to write to the ERDSA or RDSA when PROTECT is specified for the RENTPGM parameter.
  • Attempt to read or write to another transaction's storage. For example, in a system running with transaction isolation, a program running in USER key might experience a protection exception when attempting to access the USER key task-lifetime storage of another transaction.
  • Storage that is passed to CICS as an output parameter through the EXEC interface that is not addressable by the application issuing the call. The transaction is abended AEYD, and the PSW shows that a protection exception has occurred.
5
Addressing exception - the address that you referenced is not available or is not valid.
A possible cause is as follows:
  • Incorrect register contents, which might be because of an overlaid register save area.
6
Specification exception - incorrect format of an instruction or invalid registers.
Possible causes are as follows:
  • Overlaid program
  • Incorrect field lengths used in packed decimal multiply and divide instructions
  • Branch to an odd-numbered address, caused by an overlaid register save area
7
Data exception - data invalid in a packed or signed display decimal operation. One, or both of the operands contain data that is not suitable for the instruction.
Possible causes are as follows:
  • Incorrect input data (often because blanks are used where numeric data is expected)
  • Overlaid data
  • Overlaid register save area, causing an incorrect branch
  • Incorrect program logic, execution of code with uninitialized variables
  • Wrong length
8 through F
Arithmetic exceptions, such as divide checks, overflow, and underflow. They differ in the form of arithmetic that was being used: binary, packed decimal, or floating point.
Possible causes are as follows:
  • Incorrect user data
  • Overlaid data areas
  • Overlaid register save area, causing incorrect reference to data
10 and above
Program checks associated with system-related interrupts.


dfhs10q.html | Timestamp icon Last updated: Monday, 5 June 2017