Abend code 0A9

Explanation: When accompanied by a zero value in Register 15, a VTAM® HALT command has been successfully completed. If Register 15 is not zero, an error has occurred during the execution of a VTAM module. The contents of the two low-order bytes of Register 15 indicate the cause of the error.

Register 15 contents (in hex)

Explanation

0000

A VTAM HALT CANCEL command has been successfully completed.

10F1

The ABEND was issued by VTAM retry functional recovery routine (FRR) to pass the original abend to the next recovery routine (if any) associated with the task control block (TCB). See the original abend, which was recorded in SYS1.LOGREC and appears just prior to the supervisor call (SVC) dump that was generated and indicated by reason code 10F1.

6901

Error in CP-CP sessions processing. Missing element on list pointed to by AND_BOTH_CP_STATUS_STORAGE_PTR.

6902

Error in CP-CP sessions processing. Missing element on list pointed to by AND_CW_CP_STATUS_STORAGE_PTR.

6903

Error in CP-CP sessions processing. Missing element on list pointed to by AND_CL_CP_STATUS_STORAGE_PTR.

7002

Storage was not available to drive a user exit.

7005

VTAM was unable to restore its registers from the RPH after a user exit routine returned to VTAM.

7006

CPPROC was unable to obtain adequate storage from the vary work area (VWA).

7007

TPEXIT code or CRA RELSTORE code was entered while the process was holding a PSS lock.

7008

A CPWAIT was attempted with an event ID length greater than EIDMAX.

7009

A message module needs more vary work area (VWA) storage within the component recovery area (CRA) than is currently available.

700F

Encountered a session awareness block (SAB) that was not valid.

7010

A GETRDTE or RDTFIND for a resource failed because the resource definition table entry (RDTE) chain has been corrupted.

7012

A lock's count shows no user is holding the lock, but the lock is held.

7013

Lock hierarchy violation.

7014

TSLINK found the component recovery area (CRA) too small to hold all of the data.

7015

A transmission subsystem control block (TSCB) was encountered that is not valid.

7016

ISTAPCPD detected a work element that was not valid or an overlaid work element.

7017

Resource exhausted condition. For example, an internal table is full.

7018

An attempt to initialize a Remote Direct Memory Access (RDMA) over Converged Ethernet (RoCE) anchor pool failed.

7019

A RoCE anchor pool entry could not be obtained.

701A

A RoCE anchor pool entry could not be marked active.

701B

An attempt to free a RoCE anchor pool failed.

701C

An attempt to initialize a RoCE shared lock failed.

701D

An attempt to free a RoCE shared lock failed.

7071

This error is issued for one of the following reasons:

A RELSTORE was issued for a previously freed buffer.
A buffer was overlaid.

7072

A VTFREE was issued for a previously freed area.

7074

A VTFREE was issued for a buffer that is not valid.

7075

A FREEBLK was issued for a previously freed storage area.

7076

C code ran out of ISA storage for autodata.

7077

Storage management header has been overlaid.

7078

The last word in the buffer being RELSTOREd is not BFPPCBA (fence corrupted).

7079

Header in REQSTORE buffer being allocated is not valid (no match on fence word).

707A

A FREESTOR was issued for a previously freed storage area.

707B

ISTORMMG detected an overlaid storage management header.

707C

A FREEBLK was issued for a previously free storage area. It is currently queued and waiting to be freed.

CD01

CDRM error detected.

CF01

An error was found and corrected in a CDRM minor node during CDRM major node deactivation.

FA01

DS process error.

FA02

The DS disk I/O subtask has abended due to insufficient storage. The checkpoint has been disabled.

FA09

Initialization error.

FE02

A pool has been defined by the POOLDEF macro with an unacceptable length or the lengths in a variable-length pool were not defined in ascending order.

FE03

The GETSTOR pool was defined with an unacceptable length or lengths not ascending.

FF02

A FREEBLK macro returned a nonzero return code.

FF03

A utility module detected a function code that is not valid.

FF04

A request, response, or vector was not defined to the RU information table.

FF05

The main entry for the extended router was invoked but processing was already occurring within a CALLSSCP environment.

FF06

No sense code was set, but one should have been.

FF07

The CPCBURC field contained no format, but the response has a format.

FF08

The limit of topology elements (SWBVDCVD) has been exceeded. D3/D4 vectors for elements exceeding limit were not built.

FF09

The VWA area in use is too small to satisfy this request.

FF10

A request was made to queue a response to a process anchor block (PAB).

FF11

A suspend code that is not valid was passed to suspend.

FF12

A SENDER invocation that is not valid was made.

FF13

An unexpected value was received. The value might be valid in another context.

FF14

An unexpected finite state machine (FSM) state was encountered.

FF15

An unexpected field value was encountered for an enumerated type.

FF16

An unexpected control block was received as input.

FF17

A session information block (SIB) or SIB address that is not valid was passed to FREESIB.

FF18

The SENDER buffer area is not large enough.

FF19

The DETERMINER routine returned results that are not valid.

FF20

The BUILD routine returned results that are not valid.

FF22

SRTDEL failed.

FF23

A VR out-of-sequence error has occurred. The ABEND has been initiated by VTAM (no dump) to initiate VR recovery.

FF24

VTAM agent user read queue PAB dispatched with incorrect application work element.

FF25

HPRCTL was issued with the TOKEN option and the value passed was not valid.

FF26

Secondary Access Point (SAP) table overflow.

FF27

A freed TG record is still queued to a topology and routing services (TRS) routing tree.

FF99

Indicates that a FFST™ probe was tripped. Console messages with prefix EPW will be issued by FFST to provide information about the probe trip. See z/OS Communications Server: SNA Diagnosis Vol 2, FFST Dumps and the VIT for a description of FFST probes.

System action: The task that initiated the VTAM request abnormally terminates.

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:
1. SYSABEND DD statement.
2. SYSUDUMP DD statement.
Save all the associated output.
Save the dump.
Execute the EREP service aid to dump the LOGREC file, and save the resulting output. For MSS, execute the following program to dump the LOGREC file:
1. Service aid IFCISDA0
2. Program ISDASDAO with the DETAIL(ALL) parameter
If Register 15 is 7015, take the following actions to try to determine the cause of the TSCB integrity loss:
1. Save the dump.
2. If VTAM internal trace is running MODE=EXT, save this trace.
  Note: The default trace internal options might not be enough to resolve this problem. All options but LOCK, with a trace table of at least SIZE=200, might be required.