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


800

z/OS MVS System Codes
SA38-0665-00

800

Explanation

During processing of an I/O request, execute channel program (EXCP) processing encountered an error. Most instances of the X'800' ABEND code have a reason code that explains the error. After the pages for a buffer were fixed, an LRA instruction for a page in the buffer got a nonzero condition code. This means that page is not valid.
Code
Explanation
01
An error occurred during Start of changechannel program validity check processing. Either an access protection error or a page fixEnd of change error occurred when:
  • The EXCP IDAW routine tried to access the IDAW using an incorrect storage protection key.
  • The EXCP CCW validity check routine tried to access the virtual channel program using an incorrect storage protection key.
  • The Start of changeCCWEnd of change channel program attempted to execute a restricted operation.
  • The EXCP zHPF validity check routine tried to access the virtual channel program using an incorrect storage protection key.
  • An error occurred during page-fix or page-unfix processing. A page-fix error can occur if the EXCP processor tries to fix pages that are not assigned to the caller's address space identifier (ASID).
Note: An access protection or page-fix error can occur when there is an error in the channel program. Correct the channel program.
02
System error. Search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM® Support Center.
03
An error occurred during page-fix processing Start of changefor a data extent block (DEB) for an EXCP V=R request.End of change
04
A program issued SVC 114, the EXCPVR macro, but an error occurred during page-fix or page-unfix processing. A page-fix error can occur if the EXCP processor tries to fix pages that are not assigned to the caller's ASID.
05
The IOBE specified that 64-bit IDAWs are to be used for an EXCPVR request, but they are not supported by the hardware.
06
The IOBE specified that 64-bit IDAWs are to be used for an EXCPVR request but they are not supported by the device support code
07
The IOBE specified that format 1 CCWs are to be used for an EXCP request, but format 1 CCWs are only supported with EXCPVR requests.
08
The IOBE specified that MIDAWs are to be used for an EXCP request, but MIDAWs are only supported with EXCPVR requests.
Start of change09End of change
Start of changeThe IOBE specified that this is a zHPF channel program request, but zHPF channel programs are only supported for EXCPVR and EXCP Start of changevirtual requests for non-VIO data sets. They are not supported for VIO data sets or EXCP V=R requests.End of changeEnd of change
0A
A zHPF channel program request specified a TCW that is not on a 64-byte boundary.
0B
A zHPF channel program request used a TIDAL to point to the TCCB.
0C
A zHPF channel program request specified a TCW that contained a non-zero value for the TSB pointer or the interrogate TCW pointer.
Start of change0DEnd of change
Start of changeA zHPF channel program for an EXCP virtual request specified a TCCB that crossed a page boundary.End of change
Start of change0EEnd of change
Start of changeStart of changeThe number of virtual TIDAWs in a zHPF channel program has exceeded the maximum allowed value (65,536). This can occur due to an error in the channel program. For example:
  • A virtual TIDAW in the list is linked to a previous virtual TIDAW causing a loop.
  • An incorrect TIDAL virtual storage address is specified in the TCW.
  • The last virtual TIDAW in the list does not have the last TIDAW in the list flag turned on.
End of changeEnd of change

System action

The system abnormally ends the current task. The system writes a logrec data set error record and issues a system dump.

System programmer response

In the dump, look at field TCBEXCPD at offset X'C0' in the task control block (TCB) for the current task. TCBEXCPD points to the EXCP debugging area (XDBA). The XDBA contains diagnostic data associated with the EXCP processor.

If the error recurs and the program is not in error, look at the messages in the job log for more information. Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the logrec data set error record, the JCL for the job, and the SNAP dump.

Programmer response

Correct the problem that the reason code indicates.

If you get reason code 3 or 4, or if the error cannot be determined, run the job again, requesting an ABEND dump. Notify the system programmer.

Source

Execute channel program (EXCP)

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014