WallPapers

Amazon Books

Driver Image Banner 728 x 90

CICS ABEND CODES

 

 

*AACA*

Explanation:  An invalid error code has been passed to the DFHTFP or

DFHACP programs.

System Action:  CICS terminates the task abnormally with a dump.

User Response:  Notify the system programmer.

Module:  DFHTFP,DFHACP

 

*AALM*

Explanation:  An error (INVALID, DISASTER or unexpected EXCEPTION

response) has occurred on a call to the log manager (LM) domain. The

domain that detected the original error provides an exception trace, a

console message, and possibly a system dump (depending on the options

specified in the dump table).

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  See the related message produced by the domain that

detected the original error.

Module:  DFHAMLM

 

*AALN*

Explanation:  An error (INVALID, DISASTER or unexpected EXCEPTION

response) has occurred on a call to the TD manager. The domain that

detected the original error provides a trace entry and possibly a system

dump (depending on the options specified in the dump table).

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Inform the system programmer. Examine the trace and the

dump to identify the point of error.

Module:  DFHAMTD

 

*AALO*

Explanation:  An error (INVALID, DISASTER or unexpected EXCEPTION

response) has occurred on a call to the CICS/DB2 table manager DFHD2TM.

The domain that detected the original error provides a trace entry and

possibly a system dump (depending on the options specified in the dump

table).

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Inform the system programmer. Examine the trace and the

dump to identify the point of error.

Module:  DFHAMD2

 

*AALP*

Explanation:  An error (INVALID, DISASTER or unexpected EXCEPTION

response) has occurred on a call to the Program Manager. The domain that

detected the original error provides a trace entry and possibly a system

dump (depending on the options specified in the dump table).

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Inform the system programmer. Examine the trace and the

dump to identify the point of error.

Module:  DFHAMPG

 

*AALQ*

Explanation:  An error (INVALID, DISASTER or unexpected EXCEPTION

response) has occurred on a call to the Business Application Manager.

The domain that detected the original error provides a trace entry and

possibly a system dump (depending on the options specified in the dump

table).

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Inform the system programmer. Examine the trace and the

dump to identify the point of error.

Module:  DFHAMBA

 

*AALR*

Explanation:  An error (INVALID, DISASTER or unexpected EXCEPTION

response) has occurred on a call to the Temporary Storage Manager. The

domain that detected the original error provides a trace entry and

possibly a system dump (depending on the options specified in the dump

table).

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Inform the system programmer. Examine the trace and the

dump to identify the point of error.

Module:  DFHAMBA

 

*AALS*

Explanation:  An error (INVALID, DISASTER or unexpected EXCEPTION

response) has occurred on a call to the Global Enqueue Manager. The

domain that detected the original error provides a trace entry and

possibly a system dump (depending on the options specified in the dump

table).

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Inform the system programmer. Examine the trace and the

dump to identify the point of error.

Module:  DFHAMBA

 

*AALT*

Explanation:  An error (INVALID, DISASTER or unexpected EXCEPTION

response) has occurred on a call to the Internet Inter-Orb Protocol

Manager. The domain that detected the original error provides a trace

entry and possibly a system dump (depending on the options specified in

the dump table).

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Inform the system programmer. Examine the trace and the

dump to identify the point of error.

Module:  DFHAMOP

 

*AALU*

Explanation:  An error (INVALID, DISASTER or unexpected EXCEPTION

response) has occurred on a call to the Sockets Domain Manager. The

domain that detected the original error provides a trace entry and

possibly a system dump (depending on the options specified in the dump

table).

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Inform the system programmer. Examine the trace and the

dump to identify the point of error.

Module:  DFHAMSO

 

*AALV*

Explanation:  An error (INVALID, DISASTER or unexpected EXCEPTION

response) has occurred on a call to the Enterprise Java Domain. The

domain that detected the original error provides a trace entry and

possibly a system dump (depending on the options specified in the dump

table).

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Inform the system programmer. Examine the trace and the

dump to identify the point of error.

Module:  DFHAMEJ

 

*AAL1*

Explanation:  DFHALP was processing a request that deadlocked. The most

likely reason for the abend is that an ALLOCATE QUEUE request has been

suspended because there are no contention-winning links available. AAL1

is issued for non time-out related deadlocks, for instance the task may

have been cancelled. AAL8 is issued for stall purges and deadlock time-outs.

System Action:  CICS terminates the task abnormally. A dump is taken.

User Response:  Ensure that there are enough contention-winning sessions

available to satisfy the ALLOCATE QUEUE request.

If you are running with modegroups, ensure that there are

contention-winning sessions available to satisfy the ALLOCATE request in

that modegroup.

Module:  DFHALP

 

*AAL2*

Explanation:  Either an incorrect response (other than PURGED) was

returned from the suspend of the allocated task, or an incorrect

response was

returned from the resume.

System Action:  The transaction is abnormally terminated with a dump.

User Response:  Check the return code from the resume or the suspend to

determine the cause of the error.

Module:  DFHALP

 

*AAL3*

Explanation:  The task has been purged before a GETMAIN request to the

storage manager (SM) domain was able to complete successfully. The task

that first detected the purged condition provides an exception trace.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Investigate the reason why the task was purged. It was

purged either by the master terminal operator or as a result of a

deadlock timeout.

Module:  DFHALP

 

*AAL4*

Explanation:  An error (INVALID, DISASTER or unexpected EXCEPTION

response) has occurred on a call to the storage manager (SM) domain. The

domain that detected the original error provides an exception trace, a

console message, and possibly a system dump (depending on the options

specified in the dump table).

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  See the related message produced by the domain that

detected the original error.

Module:  DFHALP

 

*AAL6*

Explanation:  An error (INVALID, DISASTER or EXCEPTION response) has

occurred on a call to SIGNOFF_TERMINAL_USER by DFHALP during sign-off

for a surrogate terminal session running CRTE. The domain that detected

the original error provides an exception trace, a console message and,

possibly, a system dump (depending on the options specified in the dump

table).

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  See the related message produced by the domain that

detected the original error.

Module:  DFHALP

 

*AAL7*

Explanation:  An error (INVALID, DISASTER or EXCEPTION response) has

occurred on a call to schedule a remote terminal delete by DFHALP during

sign-off for a surrogate terminal session running CRTE. The domain that

detected the original error provides an exception trace, a console

message and, possibly, a system dump (depending on the options specified

in the dump table).

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  See the related message produced by the domain that

detected the original error.

Module:  DFHALP

 

*AAL8*

Explanation:  DFHALP was processing a request that deadlocked. The most

likely reason for the abend is that an ALLOCATE QUEUE request has been

suspended because there are no contention-winning links available. AAL1

is issued for non time-out related deadlocks. AAL8 is issued for stall

purges and deadlock time-outs.

System Action:  CICS terminates the task abnormally. A transaction or

system dump is not taken unless the transaction dump table has been

modified for AAL8.

User Response:  Ensure that there are enough contention-winning sessions

available to satisfy the ALLOCATE QUEUE request. If you are running with

modegroups, ensure that there are contention-winning sessions available

to satisfy the ALLOCATE request in that modegroup.

It might be necessary to increase the deadlock timeout (DTIMEOUT) value

for the transaction to prevent this abend from recurring.

If you require a transaction or system dump for this abend then add AAL8

to the transaction dump table.

Module:  DFHALP

 

*AAMA*

Explanation:  There is an internal logic error in DFHAMP.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  You need further assistance from IBM to resolve this

problem. See Part 4 of the CICS Problem Determination Guide for guidance

on how to proceed.

Module:  DFHAMP

 

*AAMC*

Explanation:  The task was purged before a GETMAIN request to the

storage manager domain was able to complete successfully.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Investigate the reason the task was purged. It was

purged either by the master terminal operator or as a result of deadlock

timeout.

Module:  DFHAMP

 

*AAMD*

Explanation:  An unexpected return code has been received from DFHDMP.

This is due to an internal logic error.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  You need further assistance from IBM to resolve this

problem. See Part 4 of the CICS Problem Determination Guide for guidance

on how to proceed.

Module:  DFHAMP

 

*AAMF*

Explanation:  An unexpected return code has been received following a

call to the kernel (KE) domain. This might be due to an internal logic

error.

System Action:  CICS terminates the task abnormally with a dump.

User Response:  You need further assistance from IBM to resolve this

problem. See Part 4 of the CICS Problem Determination Guide for guidance

on how to proceed.

Module:  DFHAMP

 

*AAMH*

Explanation:  An unexpected return code has been received following a

call to DFHFCMT. This might be due to an internal logic error.

System Action:  CICS terminates the task abnormally with a dump.

User Response:  You need further assistance from IBM to resolve this

problem. See Part 4 of the CICS Problem Determination Guide for guidance

on how to proceed.

Module:  DFHAMP

 

*AAMI*

Explanation:  An unexpected return code has been received following a

call to DFHFCRL. This might be due to an internal logic error.

System Action:  CICS terminates the task abnormally with a dump. You

need further assistance from IBM to resolve this problem. See Part 4 of

the CICS Problem Determination Guide for guidance on how to proceed.

 

Module:  DFHAMP

 

*AAMJ*

Explanation:  While installing a file, using RDO, a call was made to

DFHFCFS to enable the file. An irrecoverable error was returned from

DFHFCFS.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

At the time the error is detected, CICS writes a message to the console,

records an exception trace entry and takes a system dump.

User Response:  Inform the system programmer. Examine the trace and the

dump to identify the point of error.

Module:  DFHAMP

 

*AAMK*

Explanation:  While installing a file, using RDO, a call was made to

DFHFCDN. An irrecoverable error was returned from DFHFCDN.

System Action:  The task is abnormally terminated with a CICS

transaction dump. At the time the error is detected, CICS writes a

message to the console,

records an exception trace entry, and takes a system dump.

User Response:  Inform the system programmer, Examine the trace and dump

to identify the point of error.

 

Module:  DFHAMP

 

*AAMN*

Explanation:  There has been an unexpected return code from a call to

DFHPRPT. This might be due to an internal logic error.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  You need further assistance from IBM to resolve this

problem. See Part 4 of the CICS Problem Determination Guide for guidance

on how to proceed.

Module:  DFHAMP

 

*AAMO*

Explanation:  An invalid return code was returned from DFHTOR, the CICS

terminal object resolution program.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  You need further assistance from IBM to resolve this

problem. See Part 4 of the CICS Problem Determination Guide for guidance

on how to proceed.

Module:  DFHAMP

 

*AAMP*

Explanation:  An unexpected return code has been received from DFHPUP.

This might be due to an internal logic error.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  You need further assistance from IBM to resolve this

problem. See Part 4 of the CICS Problem Determination Guide for guidance

on how to proceed.

Module:  DFHAMP

 

*AAMQ*

Explanation:  An attempt has been made to install a partner using RDO.

However, the partner resource manager (PRM) is unavailable having failed to

initialize during CICS initialization.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  If you need to use the PRM, correct the problem which

prevented the PRM from initializing, and restart CICS.

Module:  DFHAMP

 

*AAMS*

Explanation:  There has been an unexpected return code following a

GETMAIN request to the storage manager. This is due to an internal logic

error.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  You need further assistance from IBM to resolve this

problem. See Part 4 of the CICS Problem Determination Guide for guidance

on how to proceed.

Module:  DFHAMP

 

*AAMT*

Explanation:  There is an internal logic error in DFHAMP due to an

unexpected return code from DFHTMP.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  You need further assistance from IBM to resolve this

problem. See Part 4 of the CICS Problem Determination Guide for guidance

on how to proceed.

Module:  DFHAMP

 

*AAMZ*

Explanation:  An unexpected return code has been received from DFHZCP.

This is due to an internal logic error.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  You need further assistance from IBM to resolve this

problem. See Part 4 of the CICS Problem Determination Guide for guidance

on how to proceed.

Module:  DFHAMP

 

*AAM1*

Explanation:  DFHXMCL has returned an unexpected response during the

install of a transaction class. This can be caused by the task being

purged during the install.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

If an error has occurred, at the time the error is detected, CICS issues

a DFHXMnnnn console message, records an exception trace entry and takes

a system dump.

User Response:  Determine why the task has failed. If there is a system

dump, use it together with the trace entry and the console message to

resolve the problem. If there is no system dump, the task has been

purged either by the master terminal operator or as a result of deadlock

timeout.

Module:  DFHAMP

 

*AAM2*

Explanation:  DFHXMXD has returned an unexpected response during the

install of a transaction definition. This can be caused by the task

being purged during the install.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

If an error has occurred, at the time the error is detected, CICS issues

a DFHXMnnnn console message, records an exception trace entry and takes

a system dump.

User Response:  Determine why the task has failed. If there is a system

dump, use it together with the trace entry and the console message to

resolve the problem. If there is no system dump, the task has been

purged either by the master terminal operator or as a result of deadlock

timeout.

Module:  DFHAMP

 

*AAOA*

Explanation:  An application has issued a CPI verb which CICS does not

support. The entry point referenced in the application program was

resolved in the link edit stub, but the function requested could not be

resolved when control passed to CICS.

There are two possible reasons for this: You have linkedited your

application program with a CPI stub which supports more function than

this release of CICS.  The linkedit stub has been corrupted.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump. An exception trace entry is also written.

User Response:  At the time of the error, general register 0 points to

an 8-byte character string which should match the name of the issued CPI

call. Use the trace or the dump to verify that this character string is

the name of a CPI function which is supported.

If the character string is not an intelligible character string, the

stub has probably been corrupted.

Module:  DFHCPI

 

*AAOB*

Explanation:  An application has issued a CPI verb which specifies more

than eight parameters.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump and an exception trace entry is also written.

User Response:  Change your application program so that the correct

number of parameters is specified on the CPI call.

Module:  DFHCPI

 

*AAOC*

Explanation:  CPI Communications is invoked with an invalid number of

parameters for call

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  The exception trace point produced with this abend

contains the incorrectly issued CPI Communications verb name. Use this

to determine where the application program was in error and amend it

accordingly.

The SAA CPI Communications Reference manual, SC26-4399, provides a

detailed description of all the CPI Communications verbs and how they

should be called.

Module:  DFHCPARH

 

*AAOD*

Explanation:  The task was purged before a GETMAIN request to the

storage manager (SM) domain was able to complete successfully. The

domain that first detected the purged condition provides an exception

trace.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Investigate the reason the task was purged. It was

purged either by the master terminal operator or as a result of deadlock

timeout.

Module:  DFHCPCBI

 

*AAOE*

Explanation:  The task was purged before a GETMAIN request to the

storage manager (SM) domain was able to complete successfully. The

domain that first detected the purged condition provides an exception

trace.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Investigate the reason the task was purged. It was

purged either by the master terminal operator or as a result of deadlock

timeout.

Module:  DFHCPCBA

 

*AAOF*

Explanation:  The task was purged before a GETMAIN request to the

storage manager (SM) domain was able to complete successfully. The

domain that first detected the purged condition provides an exception

trace.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Investigate the reason the task was purged. It was

purged either by the master terminal operator or as a result of deadlock

timeout.

Module:  DFHCPCBS

 

*AAOG*

Explanation:  During the processing of CMACCP (accept conversation), CPI

Communications detected that the application was attached with an

unsupported sync level.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  This condition is caused by a back-end CPI

Communications transaction being attached with a sync level that is not

CM_NONE (0) or CM_CONFIRM (1).

Change the front-end transaction, (that is, the initiator of the

conversation in the other system) so that it defines the sync level

correctly.

Module:  DFHCPCBA

 

*AAOH*

Explanation:  Journaling of data sent on a CPI communications mapped

conversation has failed. This condition is caused by a nonzero response

from the CICS log manager.

Problem Determination:  Register 12 addresses the current TCA and field

TCAJCAAD and register 4 address the JCA. The log manager request is

contained in JCATR2 and the response code is in JCAJCRC.

Possible request codes are:

X'8001' - WRITE

X'8003' - PUT

Possible response codes are:

X'01' - IDERROR - Journal identification error

X'02' - INVREQ  - Invalid request

X'03' - STATERR - Status error

X'05' - NOTOPEN - Journal not open

X'06' - LERROR  - Journal record length error

X'07' - IOERROR - I/O error.

The address of the TIOA is contained in register 8 and its data length

is in TIOATDL.

Analysis:

Register  Label     Description

R4=@JCA   TCZARQPJ  JCAJCRC is nonzero.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  Use the dump to ascertain why the journal or log record

could not be written correctly. If a journal record length error is

indicated, TIOATDL

may have been corrupted.

Module:  DFHCPCOJ

 

*AAOI*

Explanation:  The journaling of data received on a CPI Communications

mapped conversation has failed.

Problem Determination:  Register 12 addresses the current TCA and field

TCAJCAAD and register 4 address the JCA. The CICS log manager request is

contained in JCATR2 and the response code is in JCAJCRC.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  This condition is caused by an invalid response from the

log manager. Use the dump to ascertain why the journal or log record

could not be  written correctly. If a journal record length error is indicated,

TIOATDL may have been corrupted.

Modules: DFHCPCRI, DFHCPCRW

 

*AAOJ*

Explanation:  CPI Communications has detected an unexpected response

from one of its internal routines.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  This is a CICS internal logic error.

A level 2 trace for 'CP' of the transaction shows the course of events

prior to this error. For example, the modules called and their

parameters. The level 2 trace also provides details of the error itself.

You need further assistance from IBM to resolve this problem. See Part 4

of the CICS Problem Determination Guide for guidance on how to proceed.

Module:  DFHCPIC

 

*AAOK*

Explanation:  CPI Communications has detected an unexpected call to one

of its internal routines.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  This is a CICS internal logic error.

A level 2 trace for 'CP' of the transaction shows the course of events

prior to this error, for example, the modules called and their

parameters. The level 2 trace also provides details of the error itself.

You need further assistance from IBM to resolve this problem. See Part

4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module:  DFHCPIC

 

*AAOL*

Explanation:  CPI Communications has made an invalid call to DFHLUC.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  This is a CICS internal logic error.

A level 2 trace for 'CP' of the transaction shows the course of events

prior to this error, for example, the modules called and their

parameters. The level 2 trace also provides details of the error itself.

You need further assistance from IBM to resolve this problem. See Part

4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module:  DFHCPCLR

 

*AAOM*

Explanation:  The CPI Communications and the DFHZUSR state machines are

out of synchronization.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  This is a CICS internal logic error.

A level 2 trace for 'CP' of the transaction shows the course of events

prior to this error. For example, the modules called and their

parameters. The level 2 trace also provides details of the error itself.

You need further assistance from IBM to resolve this problem. See Part

4 of the CICS Problem Determination Guide for guidance on how to proceed.

Modules: DFHCPCLR, DFHCPSRH

 

*AAON*

Explanation:  CPI Communications has detected an unexpected response

from DFHLUC.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  This is a CICS internal logic error.

A level 2 trace for 'CP' of the transaction shows the course of events

prior to this error. For example, the modules called and their

parameters. The level 2 trace also provides details of the error itself.

You need further assistance from IBM to resolve this problem. See Part

4 of the CICS Problem Determination Guide for guidance on how to proceed.

Modules: DFHCPCLR, DFHCPCLC

 

*AAOO*

Explanation:  CPI Communications has been invoked with an invalid first

parameter. The first parameter should be the code of the function to be

performed. This is a CICS internal logic error.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  A level 2 trace for 'CP' of the transaction shows the

course of events before this error occurred (such as the modules called

and their parameters) plus details of the error itself.

You need further assistance from IBM to resolve this problem. See Part

4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module:  DFHCPARH

 

*AAOP*

Explanation:  The CPI Communications state machine has been requested to

perform a state transition request that is considered to be an 'impossible'

situation.  (The SAA CPI Communications Reference manual, (SC26-4399)

documents all these situations.)

There are two possible causes of this error:

The CPC (conversation control block) has been overwritten in such a

way that the conversation state has been altered, or

There is an error in the CPI Communications state machine.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  A level 2 trace for 'CP' of the transaction shows the

course of events prior to this error, for example, the modules called

and their parameters. The level 2 trace also provides details of the error itself.

The transaction dump shows the CPC. You may need further assistance from

IBM to fully resolve this problem. You need further assistance from IBM to

resolve this problem. See Part 4 of the CICS Problem Determination Guide

for guidance on how to proceed.

Module:  DFHCPCFS

 

*AAOQ*

Explanation:  The return code generated by CPI Communications does not

have an entry in the state table against the current CPI Communications

verb.

This error is detected by the CPI Communications state machine.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  This is a CICS internal logic error.

A level 2 trace for 'CP' of the transaction shows the course of events

prior to this error, for example, the modules called and their

parameters. The level 2 trace also provides details of the error itself.

You need further assistance from IBM to resolve this problem. See Part

4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module:  DFHCPCFS

 

*AAOR*

Explanation:  CPI Communications has detected an invalid value in the

CPC (conversation control block).

There are 2 possible causes of this error:

The CPC (conversation control block) has been overwritten, or

There is an error in CPI Communications which causes it to reject

valid values.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  A level 2 trace for 'CP' of the transaction shows the

course of events prior to this error, for example, the modules called

and their parameters. The level 2 trace also provides details of the error itself.

Module:  DFHCPIC

 

*AAOS*

Explanation:  CPI Communications has detected that the conversation

state is RESET for a situation where this should not occur. That is, the

conversation control block (CPC) is about to be deleted.

There are two possible causes of this error:

The CPC has been overwritten, or   There is an error in CPI

communications.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  A level 2 trace for 'CP' of the transaction shows the

course of events prior to this error, for example, the modules called

and their parameters. The level 2 trace also provides details of the error itself.

You may need further assistance from IBM to fully resolve this problem.

You need further assistance from IBM to resolve this problem. See Part 4 of the CICS

Problem Determination Guide for guidance on how to proceed.

Module:  DFHCPIC

 

* AAOT*

Explanation:  While chaining through the CPCs (conversation control

blocks) for a given conversation, CPI Communications detected that the

chain was broken.

There are two possible causes of this error.

1.  The CPC chain has been overwritten, or

2.  There is an error in the CPI Communications chaining mechanism.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  Determine which of the above caused the error.

A level 2 trace for 'CP' of the transaction shows the course of events

prior to this error, for example, the modules called and their

parameters. The level 2 trace also provides details of the error itself.

You may need further assistance from IBM to fully resolve this problem.

You need further assistance from IBM to resolve this problem. See Part 4

of the CICS Problem Determination Guide for guidance on how to proceed.

Module:  DFHCPCBI

 

*AAOU*

Explanation:  CPI Communications has detected an error in the TP_name

or partner_LU_name while processing an initialize conversation request.

The TP_name or partner_LU_name is obtained by lookup of the

sym_dest_name in the partner resource table (PRT).

There are two possible causes of this error.

1.  The entry in the PRT contains invalid data, or

2.  There is an error in the mechanism that returns the data from the

PRT and interprets it.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  A level 2 trace for 'CP' of the transaction shows the

course of events prior to this error, for example, the modules called

and their parameters. The level 2 trace also provides details of the error itself.

You need further assistance from IBM to resolve this problem. See Part

4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module:  DFHCPCBI

 

*AAOV*

Explanation:  CPI Communications has detected that its internal state

table is corrupted.

This error is detected by the CPI Communications state machine.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  This is a CICS internal logic error.

A level 2 trace for 'CP' of the transaction shows the course of events

prior to this error, for example, the modules called and their

parameters. The level 2 trace also provides details of the error itself.

You need further assistance from IBM to resolve this problem. See Part

4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module:  DFHCPCFS

 

*AAOW*

Explanation:  CPI Communications has detected an internal logic error

in DFHCPCLC.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  This is a CICS internal logic error.

A level 2 trace for 'CP' of the transaction shows the course of events

prior to this error, for example, the modules called and their parameters.

The level 2 trace also provides details of the error itself.

You need further assistance from IBM to resolve this problem. See Part 4

of the CICS Problem Determination Guide for guidance on how to proceed.

Module:  DFHCPCLC

 

*AAOX*

Explanation:  CPI Communications has detected a bad syncpoint return

code which has been set on a synclevel 0 or 1 conversation. The bad

return code is only expected on a synclevel 2 conversation.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  This is a CICS internal logic error.

A level 2 trace for 'CP' of the transaction shows the course of events

prior to this error, for example, the modules called and their

parameters. The level 2 trace also provides details of the error itself.

You need further assistance from IBM to resolve this problem. See Part 4

of the CICS Problem Determination Guide for guidance on how to proceed.

Module:  DFHCPIC

 

*AAOY*

Explanation:  CPI Communications detected an invalid LL field in the GDS

records from which it was receiving on a mapped conversation.

Although it is possible that the remote system is sending invalid

records, it is more likely to be an error in the receive logic because

DFHZARRC (a lower level receive module) also checks the LLs before

passing them to CPI Communications.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  Use CICS traces and, possibly a VTAM trace, to determine

the data that was sent between both systems.

A level 2 CICS trace for 'CP' of the transaction documents the course of

events prior to this error (such as the modules called and their

parameters). The level 2 trace also provides details of the error itself.

You may need further assistance from IBM to fully resolve this problem.

You need further assistance from IBM to resolve this problem. See Part 4

of the CICS Problem Determination Guide for guidance on how to proceed.

Module:  DFHCPCRB

 

*AAOZ*

Explanation:  CPI Communications has detected an invalid ID field in the

GDS records it was receiving on a mapped conversation. The exception

trace point that accompanies this abend gives the ID field in data 3.

The valid IDs are '12FF'X for application data and '12F1'X for null data.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  Use CICS traces and, possibly, a VTAM trace to determine

the data that was sent between both systems.

A level 2 CICS trace for 'CP' of the transaction documents the course of

events prior to this error (such as the modules called and their

parameters). The level 2 trace also provides details of the error itself.

You may need further assistance from IBM to fully resolve this problem.

You need further assistance from IBM to resolve this problem. See Part 4

of the CICS Problem Determination Guide for guidance on how to proceed.

Module:  DFHCPCRB

 

*AAO2*

Explanation:  CPI Communications has detected an unexpected response

from DFHLUC.

 

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  This is a CICS internal logic error.

A level 2 CICS trace for 'CP' of the transaction documents the course of

events prior to this error (such as the modules called and their

parameters). The level 2 trace also provides details of the error itself.

You need further assistance from IBM to resolve this problem. See Part 4

of the CICS Problem Determination Guide for guidance on how to proceed.

Module:  DFHCPCBA

 

*AAO3*

Explanation:  The CPI interface detected that a call was made to a CPI

Communications function without CPI Communications being initialized.

This implies that CPI Communications initialization failed while CICS

was initializing.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump. An exception trace entry is also written when this

event occurs.

User Response:  Check the console listing to determine the reason why

CPI Communications failed to initialize during CICS initialization.

Correct the problem and restart CICS.

If the console listing indicates that CPI Communications initialized

successfully, you need further assistance to resolve the problem.

Collect the console listing, the traces and the transaction dump.

You need further assistance from IBM to resolve this problem. See Part 4 of the CICS

Problem Determination Guide for guidance on how to proceed.

Module:  DFHCPI

 

*AAO4*

Explanation:  DFHZARL, or a module called by DFHZARL, has detected a

logic error. This error is almost certainly caused by the module

receiving invalid data or indicators from VTAM.

System Action:  Before returning to the CPI Communications layer,

DFHZARL calls DFHZNAC to clean up the session and put out messages on

the CSNE log. CPI Communications abnormally terminates the transaction with a

CICS transaction dump, and produces an exception trace entry.

User Response:  Check the CSNE log to determine the type of error. You

may need further assistance from IBM to fully resolve this problem. You

need further assistance from IBM to resolve this problem. See Part 4 of the

CICS Problem Determination Guide for guidance on how to proceed.

Module:  DFHCPCLR

 

AAO5

Explanation:  The task was purged before a GETMAIN request to the

storage manager (SM) domain was able to complete successfully. The

domain that first detected the purged condition provides an exception trace.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Investigate the reason why the task was purged. It was

purged either by the master terminal operator or as a result of deadlock

timeout.

Modules: DFHCPCBA, DFHCPCBI, DFHCPCBS

 

AAO7

Explanation:  The CPI Communications syncpoint request handler has been

passed an invalid DFHLUC parameter list. This is a CICS internal logic

error.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  A level 2 trace for 'CP' of the transaction shows the

course of events before this error occurred (such as the modules called

and their parameters) plus details of the error itself. You need further

assistance from IBM to resolve this problem. See Part 4 of the CICS

Problem Determination Guide for guidance on how to proceed.

Module:  DFHCPSRH

 

AAO8

Explanation:  The CPI Communications syncpoint request handler has been

passed an invalid conversation control block (CPC). This is a CICS internal

logic error.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  A level 2 trace for 'CP' of the transaction shows the

course of events before this error occurred (such as the modules called

and their parameters) plus details of the error itself. You need further

assistance from IBM to resolve this problem. See Part 4 of the CICS

Problem Determination Guide for guidance on how to proceed.

Module:  DFHCPSRH

 

AAO9

Explanation:  A task has been purged either as a result of a purge from

the master terminal operator via the CEMT transaction, or by the task

being timed out after waiting for longer than the DTIMOUT (deadlock timeout) value

specified for the transaction.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Investigate why the task was purged.

If the task was purged by the master terminal operator, this may have

been in an attempt to clear the system which appeared to be deadlocked

for some reason.

If the task was timed out automatically as a result of the DTIMOUT value

being exceeded, this may be due to insufficient main storage being

available for the number of tasks in the system. If the amount of main storage cannot be

increased, the number of tasks in the system should be reduced to avoid

short-on-storage situations. Another possibility would be to increase

the value of the DTIMOUT option for the transaction.

Module:  DFHCPCLR

 

ABAC

Explanation:  An activity issued EXEC CICS RETURN (without the

ENDACTIVITY option) but no events were processed during the activation.

The activity was executed with a RUN command.

System Action:  The task is abnormally terminated with a CICS

transaction dump. The EXEC CICS HANDLE ABEND command cannot handle this

abend.

User Response:  Investigate why the activity did not process any events.

Module(s): DFHBASP

 

ABAD

Explanation:  An activity issued EXEC CICS RETURN ENDACTIVITY while

there were activity completion events pending. The activity was executed

with a RUN command.

System Action:  The task is abnormally terminated with a CICS

transaction dump. The EXEC CICS HANDLE ABEND command cannot handle this

abend.

User Response:  Investigate why the activity had pending activity

completion events.

Module(s): DFHBASP

 

ABAE

Explanation:  An activity issued EXEC CICS RETURN (without the

ENDACTIVITY option) but no events were processed during the activation.

The activity was executed with a LINK command.

System Action:  The task which issued the LINK is abnormally terminated

with a CICS transaction dump. The EXEC CICS HANDLE ABEND command

cannot handle this abend.

User Response:  Investigate why the activity did not process any events.

Module(s): DFHEIBAM

 

ABAF

Explanation:  An activity issued EXEC CICS RETURN ENDACTIVITY while

there were activity completion events pending. The activity was executed

with a LINK command.

System Action:  The task which issued the LINK is abnormally terminated

with a CICS transaction dump. The EXEC CICS HANDLE ABEND command

cannot handle this abend.

User Response:  Investigate why the activity had pending activity

completion events.

Module(s): DFHEIBAM

 

ABLA

Explanation:  The task was purged before a GETMAIN request to the

storage manager (SM) domain was able to complete successfully. The

domain that first detected the purged condition provides an exception trace.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Investigate why the task was purged. It was purged

either by the master terminal operator or as a result of deadlock timeout.

If the task was purged by the master terminal operator, this may have

been in an attempt to clear the system which appeared to be deadlocked

for some reason.

If the task was timed out automatically as a result of the DTIMOUT value

being exceeded, this may be due to insufficient main storage being

available for the number of tasks in the system. If the amount of main storage cannot be

increased, the number of tasks in the system should be reduced to avoid

short-on-storage situations. Another possibility would be to increase

the value of the DTIMOUT option for the transaction.

Modules: DFHMCP, DFHMCPE, DFHM32, DFHPBP, DFHRLR

 

ABLB

Explanation:  An error (INVALID, DISASTER, or unexpected EXCEPTION

response) has occurred on a call to the storage manager (SM) domain. The

domain that detected the original error provides an exception trace, a

console message and, possibly, a system dump (depending on the options

in the dump table).

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Please see the related message produced by the domain

that originally detected the error.

Modules: DFHMCP, DFHMCPE, DFHM32, DFHPBP, DFHRLR

 

ABMA

Explanation:  The user has supplied a terminal I/O area (TIOA) with an

invalid data length that was either equal to zero or greater than the

storage accounting length minus 12.

Alternatively, the length field of a header or trailer area provided by

the application program is invalid (that is, not positive).

Problem Determination:  The output services work area (OSPWA) is in user

storage and will be printed in a transaction dump. It is addressed by

register 2 at the time of the abend.  Relevant fields are:

OSPTR7

OSPHDRA

OSPTRLA

Register 4 or OSPTIOA points to the TIOA. In the TIOA, the following

fields are relevant:

TIOATDL

TIOASAL

Analysis:

Register          Label            Description

R4=@TIOA    PBCKTDL    TIOATDL is zero or greater

than TIOASAL-12.

R2=@OSPWA   PBD20080   R0 (= first halfword of

R0=length              trailer)  is zero.

of trailer             R8=OSPTRLA.

R8=@trailer            OSPTR7 has X'20' bit set.

R2=@OSPWA   PBDTXHDR   R0 (= first halfword of

R8=@header             header) is zero.

R0=length              R8=OSPHDRA.

of header.            OSPTR7 has X'40' bit set.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  Correct the program that supplied the erroneous data length.

Check the TIOA. If either of the conditions described is present, check

the application program. For programs using command-level interface, the

TIOA is obtained by CICS using the length of the data item passed in the FROM

option on an EXEC CICS SEND MAP or EXEC CICS SEND TEXT command, or in

the TRAILER or HEADER option on an EXEC CICS SEND TEXT or an EXEC CICS

SEND PAGE command.  Check the data item for zero length.

Header and trailer records have a special format described in the CICS

Application Programming Reference. An ABMA abend occurs if the first

halfword (the length) is not positive. Check the remainder of the header/trailer

record for validity when the length is checked.

Modules: DFHPBP, DFHMCP

 

ABMB

Explanation:  The user has specified a cursor position in the BMS output

request. It is larger than the current screen size for the 3270 for

which output is being built.

Problem Determination:  If the abend occurs in DFHPBP:

At the time of the abend, register 2 points to the OSPWA and register 1

to the TTP. Relevant fields are:

OSPTR3 has X'10' bit set to indicate a user-specified cursor position

OSPCP contains a halfword cursor position specified by user

TTPSCSZ contains the halfword value of the screen size to compare

against.

If the abend occurs in DFHMCP or DFHMCX:

OSPCP contains a halfword cursor position specified by user

OSPTR3 has X'10' bit set to indicate a user-specified cursor position

OSPSCSZ contains the halfword value of the screen size to compare

against.

Analysis:

Register    Label     Description

In DFHPBP:

R2=@OSPWA   PBDBADC   OSPTR3 X'10' bit set

indicates the user-

R1=@TTP               specified cursor position.

TTPSCSZ halfword screen size.

OSPCP halfword cursor position.

In DFHKCP or DFHMCX:

R6=@OSPWA   MCENEAU2  OSPTR3 X'10' bit set

indicates the user-specified cursor position.

OSPSCSZ halfword screen size.

OSPCP halfword cursor position.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  Correct the program that specified the incorrect cursor

location.

Use trace to identify the statement issuing the request. Check that the

cursor position is being correctly set. The program may have been

designed to run in alternate screen size mode but is being run in default screen size mode,

or it may have been designed to run on a 3270 model different from the

one in use.

If  the program is routing a message, the route list should be checked. If

the program is to run with various 3270 models, the cursor position

should be within the size of the smallest screen.

Modules: DFHPBP, DFHMCP (for minimum-function BMS), DFHMCX

 

ABMC

Explanation:  The CMSG transaction is attempting to send a message to a

greater number of terminals than is possible. There is no fixed maximum

because the value depends on the other operands specified on the routing

command.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  Redefine the route list.

Module:  DFHMCP

 

ABMD

Explanation:  DFHTPR or DFHTPP has issued a DFHDI and has

received a return code other than "FUNCERR-REQUEST FOR CHANGE

DIRECTION SIGNALED" or "NORESP"

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  Inform your system programmer.

Modules: DFHTPP, DFHTPR

 

ABME

Explanation:  DFHTPR or DFHTPP has detected an invalid datastream or

DFHWBBMS detected invalid forms data while processing a basic mapping

support (BMS) request.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump. If the ABEND was issued from DFHTPR or DFHTPP then

register 7 indicates the location at which the ABEND was detected.

User Response:  If DFHTPR or DFHTPP issued the ABEND then examine the

transaction dump for bad data in the TIOA. If the origin of the bad data

is an application program, correct the program. If DFHWBBMS issued the ABEND

then check the validity of the incoming forms data in the CICS trace.

Modules: DFHTPP, DFHTPR, DFHWBBMS

 

ABMF

Explanation:  The value specified for the length option of the basic

mapping support (BMS) send map is greater than the length of the 'from'

area.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  Redefine the value for the length option.

Module:  DFHPBP

 

ABMG

Explanation:  The user has requested a basic mapping support (BMS)

service that was not specified at system generation, or at initialization.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  Correlate services requested against options specified

in the system generation of BMS.

Follow this procedure:

1.  Scan the trace table for the transaction ID that issued the abend.

If this is CSPQ (page cleanup), module DFHTPQ abnormally terminated

because a message purge delay of zero has been specified and CSPQ has been

entered via a terminal. The message purge delay is specified in the

PRGDLAY of the DFHSIT macro, and its value can be found in SITPRGD.

2.  Scan the trace table for the last BMS request (code 'FA'). Use the

option bytes at the start of the failing module to see if the requested

functions have been generated. For example, paging may have been requested, but

standard or minimum BMS was specified in the SIT.

3.  If the BMS request is compatible with the BMS options in the CICS

system generation, some incompatible suffixing amongst BMS modules must

have occurred. This can happen if the DFHSIT macro specified individual

suffixes for the BMS modules.

The following modules differ between standard and full-function BMS:

DFHMCP

DFHRLR

DFHPBP

DFHTPP

Modules: DFHMCP, DFHTPQ

 

ABMI

Explanation:  The map specified for a BMS input mapping request was not

an input map.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  Either define another input map or redefine the existing

map.

Modules: DFHMCP, DFHMCX, DFHMCY

 

ABML

Explanation:  The terminal control locate routine received invalid data

from DFHRLR and returns with an error return code. DFHRLR is attempting

to scan the TCT for a BMS ROUTE request with LIST=ALL or operator class or operator

ID specified in the route list. The terminal control table may have been

corrupted.

Problem Determination:  Register 11 points to the current TCTTE in the

search.

The TCT prefix (DFHTCTFX) can be located from CSATCTBA.

The first terminal entry (TCTTE) in the TCT is addressed by TCTVTEBA.

TCTTETEL is the halfword offset from current TCTTE to the next.

Analysis: The current TCTTE address is either not on a full-word

boundary or is not within the limits of the TCT, or the address of the

next TCTTE, obtained by adding TCTTETEL to the current address, is invalid.

This check is made by locate code (DFHZLOC) in DFHZCX.

Register    Label    Description

R11=@TCTTE  RLRLOCN  Issue DFHTC CTYPE=LOCATE

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  You need further assistance from IBM to resolve this

problem. See Part 4 of the CICS Problem Determination Guide for guidance

on how to proceed.

The terminal control table has probably been corrupted during execution.

Attempt to scan through the TCT in a dump. (Because the system dump uses

the same technique for printing all TCTTEs, the system dump fails at the

same point.)

Determine which entry is incorrect. It may be that the TCTTE has been

overwritten by user data that is recognizable in the dump.

Check the application program for references to the TCTTE pointer. Check

for user data that may be addressed from the same pointer.

In an assembler program, there may be multiple equates for the TCTTE

base register.

It may be that the TCT is being overwritten by some earlier transaction.

If this is so, it is probably one associated with the terminal whose

TCTTE is overwritten.

Modules: DFHRLR for full-function BMS

 

ABMM

Explanation:  An invalid map was specified.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  Use the supplied dump to diagnose the problem. Register

6 contains the address of the BMS instruction being executed when the error

was recognized.

Module:  DFHPBP

 

ABMO

Explanation:  The map specified for a BMS output mapping request was not

an output map.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  Either define another output map or redefine the

existing map.

Modules: DFHMCP, DFHMCX, DFHMCY

 

ABMQ

Explanation:  The query transaction (CQRY) has been initiated and either

the task is not terminal-oriented, or the associated terminal is not

defined to CICS as a 3270 or SCSPRINT device. This abend will occur if CQRY is entered

at a console, even when the console is a 3270 device, since the console

has the appearance to CICS of a keyboard/printer device. The CQRY transaction

does not have an operator interface, and under normal conditions there

is no need for an operator to invoke CQRY or for a user transaction to START the

CQRY transaction. CQRY is run automatically by CICS when a 3270 or SCSPRINT

device connects. In the transaction dump, register 8 contains the

address of the TCTTE for the associated terminal. If register 8 contains

zero, this indicates that the task is not terminal-oriented.

System Action:  The task is abnormally terminated with a CICS dump.

User Response:  Ensure that the terminal associated with CQRY is of the

3270 or SCSPRINT family of devices.

Module:  DFHQRY

 

ABMR

Explanation:  The Page Retrieval transaction (CSPG) has been initiated

but the task is not terminal-oriented.

System Action:  The task is abnormally terminated with a CICS dump.

User Response:  Ensure that a terminal is associated with the CSPG

transaction.

Module:  DFHTPR

 

ABMU

Explanation:  The application program supplied an address that is not

within region boundaries. The low-order 3 bytes of general register 1 in

the transaction dump contain the erroneous address. The high-order byte of register 1

indicates the address type as follows:

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  Correct the application program that is supplying the

erroneous address.

Modules: DFHMCP, DFHEMS

 

ABMV

Explanation:  DFHRLR has detected an invalid route list entry.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  Check that the route list is correctly built with

reserved field in the entry containing blank and a stopper of halfword

X'FFFF' to terminate the list.

Module:  DFHRLR

 

ABMX

Explanation:  A text string passed to BMS contained a set attribute

order that was invalid for one of the following reasons:

1.  The set attribute sequence was less than three characters.

2.  The attribute type was invalid.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Correct the application program.

Module:  DFHPBP

 

ABMY

Explanation:  BMS is building a TTP (Terminal Type Parameter) control

block but the pagesize selected for a terminal by BMS is zero because

either the default or alternate screensize has been defined as zero.

In the transaction dump, significant general purpose register contents

are as follows:

1.  Register 6 points to the BMS extension of the TCTTE

2.  Register 10 points to the TTP (Terminal Type Parameter) control block

3.  Register 11 points to the TCTTE

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Check the TERMINAL and TERMTYPE definitions which

determined the attributes of the offending TCTTE.

Module:  DFHRLR

 

ABMZ

Explanation:  The address of the terminal I/O area (TIOA) in TCTTEDA was

found to be zero.

When using BMS fast path as a result of an EXEC CICS RECEIVE MAP, DFHEMS

always initializes TCTTEDA with the address of the TIOA. If TCTTEDA is

subsequently found to be zero by DFHMCX, an overwrite must have occurred.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  Investigate why TCTTEDA is zero.

Scan the trace table for the last BMS request (code FA) for the failing

task and try to determine which user programs have been given control

since that BMS request.

Modules: DFHMCP, DFHMCX, DFHMCY

 

ABM0

Explanation:  The map specified for a basic mapping support (BMS)

request could not be located.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  Check if the map has been defined. If it has, check that

it has been specified correctly.

Modules: DFHMCP, DFHMCX, DFHMCY

 

ABM1

Explanation:  A basic mapping support (BMS) service is requested by a

task associated with a terminal that is not supported by BMS. The

request is not a routing request.

Problem Determination:  At the time of the abend, register 11 addresses

the TCTTE, and TCTTETEA and register 6 address the TCTTE extension,

TCTETTE.

Relevant fields are:

TCTTEDDS  the device dependent suffix.

TCTTEMSS  the map set suffix.

Analysis: DFHRLR tests the device dependent suffix and the map set

suffix in the TCTTE extension. If both of these are zero, the terminal

is not supported by BMS and DFHRLR abends the task with the abend code ABM1.

Register  Label     Description

R4=       RLRSFXCK  TCTEDDS=X'00' and

TCTEMSS=X'00'.

@TCTTETE            The device dependent suffix

and the map set suffix have loaded into the lower two bytes of register 3 by the

subroutine RLRSUFXS.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  Do not use terminals not supported by BMS for

applications using BMS services.

Check the terminal type and model number. Confirm that it is a terminal

that is not supported by BMS. A list of terminals supported by BMS is

given in the CICS Application Programming Guide. Check that the TCT macro for the

terminal accurately describes the physical terminal.

Module:  DFHRLR

 

ABM2

Explanation:  No user data was supplied for this BMS request. That is,

the address of a user data area was not found in either TCTTEDA or TCAMSIOA.

When a BMS macro level output request is issued, the user must have

placed the address of the data to be passed to BMS in TCTTEDA or TCAMSIOA

before issuing the macro. The choice is made on the following criteria:

If the data is to be passed in a TIOA by a terminal-oriented task,

the address of this TIOA may be placed either at TCTTEDA, or in TCAMSIOA

together with the setting of binary zeros into TCTTEDA.

If the data is being passed by a terminal-oriented task but not in a

TIOA, the address of the TIOA-like area of this data must be placed in

TCAMSIOA and binary zeros set into TCTTEDA.

If the data is being passed by a non-terminal-oriented task, the

address of the TIOA-like area of this data must be placed in TCAMSIOA.

TCTTEDA

cannot be referenced, because there is no TCTTE associated with this

task.

If a task attempts to pass addresses from both TCTTEDA and TCAMSIOA, the

address in TCTTEDA is the one selected.

Problem Determination:  The output services work area (OSPWA) is

addressed by register 9. The TCTTE is addressed by register 11. The TCA is addressed by register 12.

The relevant fields are:

Field     Description

OSPIND01  OSPWA indicator byte 1

OSPIOA    Alternate I/O area address

OSPSIOA   Address of address of data (TCTTEDA/TCAMSIOA)

OSPTIOA   Address of user data found by BMS

OSPTR1-8  BMS request data saved from the TCA

TCTTEDA   Terminal data area address

TCAFCI    Facility control indicator

TCAMSIOA  Alternate I/O area address

Analysis: The ABM2 abend is invoked at one point in DFHMCP, at label

MCPABEND. There are five regions in DFHMCP in which the user's data is

sought: Labels

MCPMAP,DATA=YES/ONLY       MCPPGBLD

MCPGTIOA,DATA=YES/ONLY   MCPPGBLD

MCPGTIOA

Mapping but not PAGEBLD,DATA=YES/ONLY  MCPMAPNG

No (mapping,PAGEBLD,TEXTBLD,PAGEOUT)   MCPDFALT

"Mapping" refers to BMS requests that specify maps, that is OSPTR3 bits

5 or 6 or 7 or OSPTR4 bit 3 set on.

Each of these functional regions does a BAL to subroutine MCPFTIOA to

search for a user data area. If a valid area (abend ABMU if not) is

found, its address is put into OSPTIOA and the address of the data address (of TCAMSIOA or

TCTTEDA) is set into OSPSIOA. If a data area is not found, OSPTIOA is cleared

and OSPSIOA is now loaded with the address of OSPTIOA as a null data area.

On the BAL return, OSPTIOA is tested for a nonzero value. If it is zero,

a branch to MCPABEND is taken.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  The programmer must place the address of the data into

TCTTEDA or TCAMSIOA, whichever is appropriate.

Firstly, check that the user has loaded TCTTEDA or TCAMSIOA with the

address of the user data, by checking the application listing and the

contents of  TCTTEDA and/or TCAMSIOA.

Next, check that the BMS request has been correctly decoded by CICS by

referring to the OSPWA request bytes (OSPTR1-8) or decoding the last BMS

entry in the trace table. See OSPIND01 to check correct decoding of

PAGEBLD or TEXTBLD, and TCAFCI bit 7 to identify whether the task is

terminal-oriented or not.

At the abend point, register 1 contains the user data address last

loaded, and register 4 the address of OSPTIOA as an address of null data.

If a CICS error is suspected, concentrate initially on subroutine

MCPFTIOA, because this is a simple piece of code that shows the

data-fetch logic. ABM2 condition is trapped early in the CICS decoding of the DFHBMS request

and involves module DFHMCP only.

Case/Register  Label    Description

R9=@OSPWA      MCPMAP    OSPTR4 has OSPTRM

(X'04') bit set for

R9=@OSPWA      MCPPGBLD  OSPTR5 has OSPTRB

(X'80') bit set and BMS sets bit OSPLMPB (X'08') in OSPIND01 for OSPTR4 has X'40',

X'80', or X'C0' set for DATA=NO, ONLY,or YES respectively, so should be X'80' or X'C0'.

R9=@OSPWA      MCPTXBLD  OSPTR7 has OSPTRX

(X'80') bit set and BMS sets bit OSPLMTB (X'04') in OSPIND01 for OSPTR4 has X'40', X'80', or X'C0' set

for DATA=NO, ONLY,or YES respectively, so should be X'80' or X'C0'.

R9=@OSPWA      MCPMAPNG  OSPTR3 has OSPTSN

(X'01'), OSPTSA

(X'02'), or OSPTMN

(X'04')  bits set, or OSPTR4 has OSPTMA

(X'10') bit set for mapping.

OSPTR4 has X'04' or X'80' or X'C0' set for DATA=NO, ONLY, or YES respectively, so should be X'80' or X'C0'.

All R12=@TCA   MCPFTIOA  TCAFCI has TCAFCTRM (X'01') bit set if the task is terminal-oriented.

All R11=@TCTTE MCPFTIOA  TCTTEDA could point to a use TIOA but does not, thus causing the abend.

All R12=@TCA   MCPFTIOA  TCAMSIOA could point to a user data area (TIOA or otherwise),

but does thus causing the abend.

All R9=@OSPWA  MCPNTOTM  OSPTIOA contains the address of the user area found, so is zero.

OSPSIOA points to OSPIOA (which is copied from TCAMSIOA) as being the second-dry data area sought by

BMS for data .

OSPIA (TCAMSIOA) was also zero so causing the abend.

Module:  DFHMCP

 

ABM3

Explanation:  A BMS input or output request has been issued from a task

that is not terminal-oriented.

System Action:  The task is abnormally terminated with a CICS dump.

User Response:  The task issuing a BMS input or output request must be

attached to a terminal.

Module:  DFHMCP

 

ABM4

Explanation:  An invalid request response has been received to a

temporary storage PUT or PUTQ request issued by BMS. The data passed to the

temporary storage program has an invalid length.

Problem Determination:  Abend in DFHMCP (see Analysis)

The OSPWA (output services work area) is in user storage and is printed

in a transaction dump. It is addressed by register 9 at the time of the

abend.

Relevant fields are:

OSPTITLE

OSPTTCNT

OSPPLTI

OSPTOTPG

The message control record (MCR) is an area of user storage obtained by

BMS. It is addressed by register 8 at the time of the abend. The first 8

bytes contain storage accounting information. MCRLLBB contains the length of

the MCR (halfword) abend in DFHTPP.

The page buffer is addressed by register 7 at the time of the abend. It

contains storage accounting fields in the first 8 bytes and a halfword

length at offset 8 (TSIOAVRL).

In both cases, the temporary storage use map (DFHTSMAP) is addressed

from CSATSATA. TSMAPCOM contains the number of available bytes in a control

interval on the temporary storage data set.

Analysis: If the temporary storage request preceding the abend is a

DFHTS PUT, the abend occurred in DFHMCP. If the temporary storage request

preceding the abend is a DFHTS PUTQ, the abend occurred in DFHTPP. If

the abend occurred in DFHMCP, DFHMCP is attempting to put the message

control record to temporary storage. Check the length of the MCR

(MCRLLBB). It may be negative.

The length of the MCR is calculated by code following label MCPNODDS and is:

28 + 21 * OSPTTCNT + (length of title record) + (space for page/LDC table, if needed)

The address of the title record is at OSPTITLE and the length is

contained in the first halfword. Space for the page/LDC table is

required if OSPPLT1 is nonzero, which should occur only for messages routed to LDC devices

(3600, 3650, 3767, 3770, 3790). The number of entries is in OSPTOTPG. 2 bytes are

required per entry.

If the abend occurred in DFHTPP, BMS is attempting to add a page to the

temporary storage queue, and the page buffer will not fit in the control

interval.

TSIOAVRL contains the length of the page buffer.

For messages directed to 3270 devices, the page buffer consists of a

3270 data stream with a 4-byte page control area following it (a 3270

data stream may be larger than the number of characters available on the screen,

particularly if extended 3270 attributes are used). For messages directed to other devices,

the page buffer consists of a message formatted with NL characters, a 4-byte page control area following it.

The length in TSIOAVRL should be less than the length in the preceding storage accounting area, otherwise an error has

occurred in constructing the page, possibly in prior BMS requests.

In either of the above cases, if the length of the area being output appears valid, it is necessary to increase the control interval size for

the temporary storage data set.

Register   Label     Description

DFHMCP

R8=@MCR    MCPMCRTS  The MCR is too long or has invalid length (?4).

DFHTPP

R7=@pgbuf  TPNOPGL   The page buffer is or  too large.

TPNODDS

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  You need further assistance from IBM to resolve this

problem. See Part 4 of the CICS Problem Determination Guide for guidance

on how to proceed.

Determine from the trace table whether the abend occurred in DFHMCP or

DFHTPP.

Check the length of the appropriate area.

If the MCR length is invalid, possible reasons are:

more than 64 characters.

there are a large number of terminals in the TCT.

Modules: DFHMCP, DFHTPP

 

ABM5

Explanation:  A DFHTS request has been issued with an invalid

REQID. This incorrect request was issued by basic mapping support (BMS).

DFHTPR cannot find the terminal identifier for the current terminal in

the terminal list in the message control record (MCR).

Problem Determination:  The TS identifier is built in TCATSDI before the

TS purge is issued, although this has probably been overwritten before

the dump is taken. The trace table entry for the DFHTS contains the TS

identifier in the last 8 bytes.

The OSPWA is addressed by register 9.

OPSTSID temporary storage identifier (8 bytes).

Register 8 points to the MCR.

Register 5 points to the current entry.

Register 0 points to the end of table.

Register 9 points to the TCTTE.

The terminal list starts at MCRIDLST and the terminal identifier is at

the start of the terminal entry. Each terminal entry is X'15' bytes long.

Analysis: DFHMCP uses the temporary storage identifier in OSPTSID.

Cannot find the terminal identifier for this terminal in the terminal

list in the MCR.

Register    Label     Description

R9=@(OSPWA) MCPCKPGS  Code builds the temporary storage code in TCATSDI and issues DFHTS

TYPE=PURGE macro, specifying IDERROR exit

of MCPTSIDE, where the abend is raised.

R8=@(MCR)   TPRCKID   Code scans terminal list for a terminal entry that has the id of the current

terminal, and if it cannot be found, links to TPRSNH to raise the abend.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  Check the trace table and find the preceding PUT/PUTQ TS

requests. Check whether the identifier for the PUT/PUTQ is the same as that

for the PURGE. If it is not, find out how they differ. Check to see if

the OSPWA has been corrupted.

This error is very unlikely, as the label indicates (TPRSNH - "Should

Not Happen"). DFHTPS has scanned the MCR to identify the terminals to

which this message is directed, and has created an AID to initiate CSPG (DFHTPR) at

each of them. However, when DFHTPR retrieves the MCR, it cannot find the

current terminal identifier in the list of terminals. Presumably the MCR

has been corrupted between creation of the AID and dispatching of CSPG

at the terminal. Check back through the trace table to find the instance of

DFHTPS that built the AID for this terminal (transaction CSPS); it will

have issued a TC LOCATE request to verify that the terminal identifier is valid, and this

identifier can be seen in the trace entry.

Modules: DFHMCP, DFHTPR

 

ABM6

Explanation:  Transaction CSPS, scheduled internally by BMS, has not been installed.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  Install the transaction CSPS (Group DFHBMS).

Module:  DFHMCP

 

ABM7

Explanation:  The trailer specified to be used while building pages of

text data is longer than the page.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  Correct the application program that issues the request

with too long a trailer.

Module:  DFHPBP

 

ABM8

Explanation:  A BMS text request specified a value for the JUSTIFY

option which is zero or too large for the page being built.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  Correct the application program that specified too large

or zero value for the JUSTIFY option.

Module:  DFHPBP

 

ABM9

Explanation:  The text data overflow routines have been reentered while

text overflow was in process. This condition occurs when the line

requirements for the text header and/or trailer exceed the line capacity of the page for

which data is being formatted.

System Action:  The transaction is abnormally terminated with a CICS

transaction dump.

User Response:  Reduce the number of lines required for the header

and/or trailer or increase the page size of the terminal.

Module:  DFHPBP

 

ABNA

Explanation:  No route list was supplied with a route request received

from the remote system.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  You need further assistance from IBM to resolve this

problem. See Part 4 of the CICS Problem Determination Guide for guidance

on how to proceed.

Module:  DFHTPS

 

ABNB

Explanation:  Either the principal facility of the task is not a TCTTE

of the correct type, or the task has no principal facility.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Ensure that DFHTPS has not been specified as the initial

program of a transaction other than CSPS. Check that the operator did

not enter

CSPS from the terminal.

ABModule:  DFHTPS