Abend code 0A8

Explanation: VTAM® detected an error that occurred during the execution of a user application program. The contents of the two low-order bytes of Register 15 indicate the cause of the error.

Register 15 contents (in hex): Explanation
2101: A VTAM validity check of the user request parameter list (RPL) failed because the RPL does not have the same protection key as the application program task control block (TCB).
7001: The user’s event control block (ECB) is not valid.
7002: A VTAM request for storage failed.
7003: The pointer to the request parameter list (RPL) is not valid.
7004: An ACB OPEN failed due to an access method control block (ACB) address that is not valid.
7005: Storage pointed to by RPLAREA is not valid.
7006: Storage pointed to by RPLAAREA is not valid.
7007: The request parameter list (RPL) is not valid. Unable to find ACB.
7008: RPL6 pointed to by RPLAAREA is not valid.
7009: Node initialization block(s) (NIB) pointed to by the request parameter list (RPL) is not valid.
700A: Model terminal support (MTS) data pointed to by node initialization block (NIB) is not valid.
700B: Restore parameter list pointed to by node initialization block (NIB) is not valid.
700C: Application-supplied dial parameters storage pointed to by node initialization block (NIB) is not valid.
700D: Bind area pointed to by node initialization block (NIB) is not valid.
7010: An RPL header that was not valid was encountered.
FC01: Network management interface abend.
FC02: VTAM agent user read queue PAB had a storage failure.
FF01: A session awareness (SAW) data buffer that is not valid was passed to VTAM data space services release routine.

System action: The task abnormally terminates.

Programmer response: This is probably a user error.

For reason codes 2101, 7001, 7003, 7005, 7006, 7007, 7008, 7009, 700A, 700B, and 700C, verify that the RPL and ECB pointers are correct, and execute the job step again.
For reason code 7004, verify that the ACB pointer is valid and check the storage to be sure it resides in the application storage protection key.
For reason code 7002, verify that the operator entered the buffer pool or CSA start options as specified in the start procedures.
Increase storage as required. For insufficient storage errors, you might want to redefine your buffer pool or CSA limits. If the start option cannot be modified using the MODIFY VTAMOPTS command, you must modify the VTAM start options file (ATCSTRxx) and restart VTAM to use the new start option.
- See the Storage Estimate Worksheets in the z/OS Communications Server: SNA Network Implementation Guide to determine the storage requirements for VTAM.
- See z/OS Communications Server: SNA Resource Definition Reference for a description of VTAM start options.
- See z/OS Communications Server: SNA Operation for information about the DISPLAY BFRUSE Command, the DISPLAY STORUSE Command, and the MODIFY VTAMOPTS Command.
- See z/OS Communications Server: SNA Network Implementation Guide for an explanation and description of buffer pools, and for general information about buffer pool specification and allocation.
- See z/OS Communications Server: SNA Diagnosis Vol 2, FFST Dumps and the VIT for information about analyzing dumps and for information about analyzing storage using the VIT analysis tool if external trace is active.
For reason code 700D, check the application program.
For reason code FC01, save the dump for problem determination.
For reason code FF01:
- If you have access to IBMLink, search for known problems in this area. If no applicable matches are found, report the problem to IBM® by using the electronic technical report (ETR) option on IBMLink.
- If you do not have access to IBMLink, report the problem to the IBM software support center.

Problem Determination:

If MSGLEVEL=(1,1) was not specified in the JOB statement, specify it and rerun the job.
Save the console log from the primary console. For systems with remote consoles, save the remote console log. For systems with multiple-console support (MCS), save a copy of the hard copy log.
Save the job stream associated with the job.
Make sure that the failing job step includes the SYSABEND DD statement.
Save all the associated output.
Save the program listing associated with the job.
Save the dump.
Have the linkage editor/loader map available.