WallPapers

Amazon Books

Driver Image Banner 728 x 90

Abend Code CICS  da ABNC a ABX9

 

 

 

ABNC

Explanation:  An attempt to access a temporary storage queue failed.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Ensure that temporary storage is correctly generated.

Module:  DFHTPS

 

 

ABNE

Explanation:  An error response was received from an invocation of a BMS

TYPE=ROUTE or request.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Check that BMS was correctly generated.

Module:  DFHTPS

 

ABNF

Explanation:  The transaction was not in send mode when it sent data to

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

 

ABNG

Explanation:  An attach request was received from the remote system

without any data indicating the reason for the request.

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

 

ABNH

Explanation:  An attempt to ship data to the remote system failed.

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

 

 

ABNI

Explanation:  CICS could not find a profile for an LU6.2 transaction

routing request.

System Action:  CICS terminates the task abnormally.

User Response:  Either you have specified an incorrect name in the

PROFILE parameter of an EXEC CICS ALLOCATE command, or you have not

Installed the profile.

Correct the error before resubmitting the transaction.

Module:  DFHTPS

 

ABNJ

Explanation:  The task was 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:  DFHTPS

 

ABNK

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:  DFHTPS

 

ABRC

Explanation:  The bridge exit is not defined and could not be autoinstalled.

System Action:  The task is abnormally terminated with a CICS

transaction dump. The user transaction will not be started.

User Response:  Either define the program using RDO or change the

program autoinstall exit to allow it to be autoinstalled.

Modules: DFHBRMS, DFHBRTC

 

ABRD

Explanation:  The bridge exit is disabled.

System Action:  The task is abnormally terminated with a CICS

transaction dump. The user transaction will not be started.

User Response:  Identify why the bridge exit is disabled. Enable the

bridge exit and retry the action.

Modules: DFHBRMS, DFHBRTC

 

ABRE

Explanation:  The bridge exit could not be loaded.

System Action:  The task is abnormally terminated with a CICS

transaction dump. The user transaction will not be started.

User Response:  Investigate why it cannot be loaded. It may not have

been defined in the DFHRPL library.

Modules: DFHBRMS, DFHBRTC

 

ABRF

Explanation:  The bridge exit is defined as remote.

System Action:  The task is abnormally terminated with a CICS

transaction dump. The user transaction will not be started.

User Response:  Define the bridge exit as a local program.

Modules: DFHBRMS, DFHBRTC

 

ABRG

Explanation:  An invalid bridge facility token was specified

System Action:  The task is abnormally terminated with a CICS

transaction dump. The user transaction will not be started.

User Response:  This error was probably caused by the incorrect data

being sent to the bridge exit from the client application.

Check the data set by tracing the data sent from the client application.

Ensure that the bridge facility token in the data transmitted by the

application is correct.

Module:  DFHBRXM

 

ABRH

Explanation:  The bridge facility token specified is not known to CICS.

System Action:  The task is abnormally terminated with a CICS

transaction dump. The user transaction will not be started.

User Response:  The most likely error is that the client application

specified too small a keep time for the bridge facility. Before the

client reused the bridge facility token, CICS had already discarded it.

Check the bridge facility keep time in the outbound messages.

CICS will use the keep time value specified in the last message used by a transaction. Alternatively use the trace or CEDX to look at the keep time in the BRXA passed back on the terminate call to the bridge exit.

Another possible error is that the client application passed a request

to a CICS system other than that on which the original request was sent.

Bridge facilities are only valid on a single CICS system.

Module:  DFHBRXM

 

ABRI

Explanation:  There are no free bridge facility tokens available. This

is probably due to excessive keep time values being specified on the

bridge exit termination call.

System Action:  The task is abnormally terminated with a CICS

transaction dump. The user transaction will not be started.

User Response:  Review the keep time values used by the client

applications. If some client applications are returning excessive

values, modify the bridge exit to specify a limit to the values.

Module:  DFHBRXM

 

ABRJ

Explanation:  An invalid FACILITYLIKE value was specified.

The FACILITYLIKE value can be specified on the bridge exit

initialization call. If the default value (blanks) is returned, the

value in the user transaction profile definition is used.

If no FACILITYLIKE value is specified in the profile definition, a value of CBRF is used.

The name must be that of an installed VTAM 3270 terminal.

System Action:  The task is abnormally terminated with a CICS

transaction dump. The user transaction will not be started.

User Response:  Define the terminal specified by FACILITYLIKE, change

the value on the profile definition, change the value supplied by the

client application, or install a terminal definition for CBRF

Module:  DFHBRXM

 

ABRK

Explanation:  The USERID check failed following the call to the bridge exit.

System Action:  The task is abnormally terminated with a CICS

transaction dump. The user transaction will not be started.

User Response:  Enter the correct password. If the password is correct

or was not supplied, review the RACF definitions.

Module:  DFHBRXM

 

ABRN

Explanation:  The bridge exit returned a value in BRXA_RESP that is not

valid for the command for which it was invoked.

System Action:  The transaction is backed out.

User Response:  Change the bridge exit to only return valid response

settings.

Modules: DFHBRIC, DFHBRMS, DFHBRSP, DFHBRTC

 

ABRQ

Explanation:  The bridge exit issued an abend.

System Action:  The transaction is backed out.

User Response:  Identify why the bridge exit abended.

Modules: DFHBRMS, DFHBRTC

 

ABRR

Explanation:  The user transaction's profile could not be found.

System Action:  The task is abnormally terminated with a CICS

transaction dump. The user transaction is not started.

User Response:  Check that the profile name in the user transaction

definition is correct, and that this profile has been defined.

Module:  DFHBRXM

 

ABRY

Explanation:  CICS returned an unexpected error running the bridge exit.

This is a CICS internal 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.

Modules: DFHBRMS, DFHBRTC

 

ABRZ

Explanation:  The bridge exit returned invalid data in the BRXA.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  If a user supplied bridge exit was used, review the

format of the data returned by the exit.

If a CICS supplied exit was used, this is a CICS error. 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: DFHBRIC, DFHBRMS, DFHBRSP, DFHBRTC, DFHXMBR

 

ABR3

Explanation:  An unsupported BMS request was received by the bridge exit.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  The bridge only supports minimum function BMS and SEND

TEXT. This transaction cannot be used in a bridge environment.

Module:  DFHEMS

ABR4

Explanation:  The link DFHL3270 command did not specify a commarea.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  The link DFHL3270 command must specify a commarea to

contain the BRIH and any message vectors.

Module:  DFHBRMR

 

ABR5

Explanation:  The commarea specified in the link DFHL3270 command is

shorter than the BRIH.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  The link DFHL3270 command must specify a commarea to

contain the BRIH and any message vectors.

Module:  DFHBRMR

 

ABR6

Explanation:  The commarea specified in the link DFHL3270 command does

not contain a valid BRIH.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  The link DFHL3270 command must specify a commarea which

must contain a valid BRIH.

Module:  DFHBRMR

 

ABSA

Explanation:  A message passed to DFHBSMSG is too long. This is a CICS

internal 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:  DFHTBS

 

ABXA

Explanation:  A next BRMQ vector in the input message passed to the

formatter is the wrong type of a RECEIVE vector. RECEIVE and RECEIVE MAP

have separate vectors.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  This may just indicate that the transaction has gone

down an error path which should result in a transaction backout. If not,

the input message should have a BRMQ vector for this command. Change the client

application, recompile and retry.

Module:  DFH0CBRF

 

ABXB

Explanation:  The BRIH requested that outbound BMS vector must include

the ADS descriptor.  The map did not contain an ADS descriptor. This means

that the mapset was not assembled with CICS TS 1.2 or later.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Either reassemble the mapset using the current level of

BMS macros, or set BRIH-ADSDESCRIPTOR to BRIHADSD-NO (the default value

is BRIHADSD-YES). Note that BRIHADSD-YES is required when codepage

conversion of the Link3270 message is required (e.g. using ECI). If you

need to reassemble the mapset and don't have the mapset source, the utility

DFHBMSUP can be used to recreate it.

Module:  DFHBRMF

 

ABXC

Explanation:  An error occurred when a SYNCPOINT request was issued by

the bridge exit.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Check for other CICS messages and exception trace

entries to investigate the cause of the SYNCPOINT error.

Module:  DFH0CBRE

 

ABXD

Explanation:  An error occurred when a SYNCPOINT ROLLBACK request was

issued by the bridge exit.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Check for other CICS messages and exception trace

entries to investigate the cause of the SYNCPOINT ROLLBACK error.

Module:  DFH0CBRE

 

ABXE

Explanation:  The bridge exit was expecting data to be passed on the

BRDATA parameter of the START command. No data was found.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  Correct the transaction which issued the START.

Recompile, reload and retry.

Module:  DFH0CBAE,DFH0CBRE

 

ABXF

Explanation:  An error was detected by the bridge exit when it tried to

input the next message.

System Action:  An exception trace is made of any error information. The

task is abnormally terminated with a CICS transaction dump.

User Response:  Check for other CICS messages and exception trace

entries to investigate the cause of the input error.

Module:  DFH0CBAE,DFH0CBRE,DFH0CBAI

 

ABXG

Explanation:  An error was detected by the bridge exit when it tried to

output the next message.

System Action:  An exception trace is made of any error information. The

task is abnormally terminated with a CICS transaction dump.

User Response:  Check for other CICS messages and exception trace

entries to investigate the cause of the output error.

Module:  DFH0CBAE,DFH0CBRE

ABXH

Explanation:  The user transaction issued a request which requires more

data (such as a RECEIVE request). No data was available in the message, and

mqcih-conversationaltask was set to mqcct-no which specifies that the

transaction is non conversational.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  This may be correct behaviour as defined by the client

application. If it is not, the client application should either supply

additional data, or be redesigned to allow the transaction to be conversational.

Module:  DFH0CBRF

 

 

 

ABXI

Explanation:  A message received by the bridge exit, exceeded the

maximum message size.

System Action:  An exception trace is made of the first 4K of data in

error. The task is abnormally terminated with a CICS transaction dump.

User Response:  Check that the client application is passing the correct

data. If it is, it will be necessary to change the size of the buffer.

This is in field block-length in the sample exit. Recompile and reload the exit and retry.

Module:  DFH0CBAE,DFH0CBRE

 

ABXJ

Explanation:  The bridge exit detected an error in the MQCIH header

passed by the client application.

System Action:  An exception trace is written containing the MQCIH

header. The task is abnormally terminated with a CICS transaction dump.

User Response:  The client application has either not set the MQCIH

header, or is using a version of the header which is incompatible with

the bridge exit.

Correct the client application. Recompile, reload and retry.

Module:  DFH0CBAE,DFH0CBRE

 

 

ABXK

Explanation:  The bridge exit detected an error in the data passed on

the BRDATA parameter of the START command.

System Action:  An exception trace is made of the data in error. The

task is abnormally terminated with a CICS transaction dump.

User Response:  Correct the transaction which issued the START.

Recompile, reload and retry.

Module:  DFH0CBAE,DFH0CBRE

 

ABXM

Explanation:  The bridge exit or formatter was called with a function or

command which it doesn't support. This either indicates a storage

overwrite, or that the bridge exit is not designed for this command.

System Action:  An exception trace is made of the data in error. The

task is abnormally terminated with a CICS transaction dump.

User Response:  Check the BRXA data in the trace to see if there has

been a storage overwrite, or whether the exit supports this command.

Module:  DFH0CBAE,DFH0CBRE,DFH0CBRF

 

ABXN

Explanation:  The formatter detected that the input message was truncated.

System Action:  An exception trace is made of the first 4K of the

message. The task is abnormally terminated with a CICS transaction dump.

User Response:  Check that the transport mechanism allows for messages

of this length. If this is correct, it indicates that the client

application is issuing an incorrect message. Trace the outbound message on the client application. Recompile, reload and retry.

Module:  DFH0CBRF

 

 

ABXO

Explanation:  The formatter detected an error in a BRMQ vector passed by

the client application.

System Action:  The field MQCIH-ERROROFFSET is set to indicate the

position of the error in the message An exception trace is made of the

MQCIH and

BRMQ vector. The task is abnormally terminated with a CICS transaction dump.

User Response:  Correct the client application. Recompile, reload and retry.

Module:  DFH0CBRF

 

ABXP

Explanation:  The formatter detected an error in a BRMQ vector header

passed by the client application.

System Action:  The field MQCIH-ERROROFFSET is set to indicate the

position of the error in the message An exception trace is made of the

MQCIH and

BRMQ vector. The task is abnormally terminated with a CICS transaction dump.

User Response:  Correct the client application. Recompile, reload and retry.

Module:  DFH0CBRF

 

ABXQ

Explanation:  The formatter could not find an ADSD vector as part of the

BRMQ-RM vector when MQCIH-ADSDESCRIPTOR specified MQCADSD-MSGFORMAT.

System Action:  An exception trace is made of the request. The task is

abnormally terminated with a CICS transaction dump.

User Response:  Correct the client application. Recompile, reload and retry.

Module:  DFH0CBRF

 

ABXS

Explanation:  An error was detected by the bridge exit when it tried to

open the queue for the input or output message.

System Action:  An exception trace is made of any error information. The

task is abnormally terminated with a CICS transaction dump.

User Response:  Check for other CICS messages and exception trace

entries to investigate the cause of the open error.

Module:  DFH0CBRE

 

ABXU

Explanation:  The conversion between client code page and server code

page is not supported by CICS/390; for example conversion has been

requested between Japanese code page 932 and Latin-1 code page 500.

System Action:  The transaction is abnormally terminated with a

transaction dump.

User Response:  Ensure that the Client codepage, both default and

overrides are in the same group as the Server codepage. for example

client code page 852 from Latin-2 group, is only supported to server

code page 870.

Module:  DFHBRMF

 

 

 

ABXV

Explanation:  The client code page which has been requested by the

client is not one which CICS can support.

System Action:  The transaction is abnormally terminated with a

transaction dump.

User Response:  Ensure that the Client codepage is valid.

Module:  DFHBRMF

ABX1

Explanation:  The bridge exit or formatter was called with an invalid

BRXA-HEADER. This indicates a storage overwrite.

System Action:  An exception trace is made of the data in error. The

task is abnormally terminated with a CICS transaction dump.

As CICS also does a check of the BRXA on return from the call to the

exit, there will probably be a subsequent ABRZ abend.

User Response:  Investigate the cause of the storage error, and retry.

Module:  DFH0CBAE,DFH0CBRE,DFH0CBRF

ABX2

Explanation:  The bridge exit or formatter was called with an invalid

BRXA-TRANSACTION-AREA.  This indicates a storage overwrite.

System Action:  An exception trace is made of the data in error. The

task is abnormally terminated with a CICS transaction dump.

As CICS also does a check of the BRXA on return from the call to the

exit, there will probably be a subsequent ABRZ abend.

User Response:  Investigate the cause of the storage error, and retry.

Module:  DFH0CBAE,DFH0CBRE,DFH0CBRF

ABX3

Explanation:  The bridge exit or formatter was called with an invalid

BRXA-COMMAND-AREA.  This indicates a storage overwrite.

System Action:  An exception trace is made of the data in error. The

task is abnormally terminated with a CICS transaction dump.

As CICS also does a check of the BRXA on return from the call to the

exit, there will probably be a subsequent ABRZ abend.

User Response:  Investigate the cause of the storage error, and retry.

Module:  DFH0CBAE,DFH0CBRE,DFH0CBRF

 

ABX5

Explanation:  The bridge exit or formatter was called without a

user-area. This probably indicates an error in the bridge exit.

System Action:  An exception trace is made of the data in error. The

task is abnormally terminated with a CICS transaction dump.

User Response:  Investigate the cause of the storage error, and retry.

Module:  DFH0CBAE,DFH0CBRE,DFH0CBRF

 

 

 

ABX6

Explanation:  The bridge exit or formatter was called with an invalid

user-area. This indicates a storage overwrite or an error in the bridge

exit.

System Action:  An exception trace is made of the data in error. The

task is abnormally terminated with a CICS transaction dump.

User Response:  Investigate the cause of the storage error, and retry.

Module:  DFH0CBAE,DFH0CBRE,DFH0CBRF

 

ABX7

Explanation:  A TC command passed to the formatter, exceeded the maximum

message size.

System Action:  An exception trace is made of the first 4K of data in

error. The task is abnormally terminated with a CICS transaction dump.

User Response:  Check that the user transaction is passing the correct

data. If it is, it will be necessary to change the size of the buffer.

This is in field block-length in the sample exit. Recompile and reload the exit and retry.

Module:  DFH0CBRF

 

ABX8

Explanation:  A next BMS BRMQ vector in the input message passed to the

formatter does not contain the mapset requested to answer a RECEIVE MAP

request.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  This may just indicate that the transaction has gone

down an error path which should result in a transaction backout. If not,

the input message should have a BRMQ vector for this mapset.

Change the client application, recompile and retry.

Module:  DFH0CBRF

 

ABX9

Explanation:  A next BMS BRMQ vector in the input message passed to the

formatter does not contain the mapname requested to answer a RECEIVE

MAP request.

System Action:  The task is abnormally terminated with a CICS

transaction dump.

User Response:  This may just indicate that the transaction has gone

down an error path which should result in a transaction backout. If not,

the input message should have a BRMQ vector for this mapname. Change the client

application, recompile and retry.

Module:  DFH0CBRF