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.
The task is abnormally terminated with a CICS transaction dump. The EXEC CICS HANDLE ABEND command cannot handle this abend.
Investigate why the activity did not process any events.
DFHBASP
An activity issued EXEC CICS RETURN ENDACTIVITY while there were activity completion events pending. The activity was executed with a RUN command.
The task is abnormally terminated with a CICS transaction dump. The EXEC CICS HANDLE ABEND command cannot handle this abend.
Investigate why the activity had pending activity completion events.
DFHBASP
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.
The task which issued the LINK is abnormally terminated with a CICS transaction dump. The EXEC CICS HANDLE ABEND command cannot handle this abend.
Investigate why the activity did not process any events.
DFHEIBAM
An activity issued EXEC CICS RETURN ENDACTIVITY while there were activity completion events pending. The activity was executed with a LINK command.
The task which issued the LINK is abnormally terminated with a CICS transaction dump. The EXEC CICS HANDLE ABEND command cannot handle this abend.
Investigate why the activity had pending activity completion events.
DFHEIBAM
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.
The task is abnormally terminated with a CICS transaction dump.
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.
DFHMCP, DFHMCPE, DFHM32, DFHPBP, DFHRLR
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).
The task is abnormally terminated with a CICS transaction dump.
Please see the related message produced by the domain that originally detected the error.
DFHMCP, DFHMCPE, DFHM32, DFHPBP, DFHRLR
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).
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:
Register 4 or OSPTIOA points to the TIOA. In the TIOA, the following fields are relevant:
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.
The transaction is abnormally terminated with a CICS transaction dump.
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.
DFHPBP, DFHMCP
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.
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:
If the abend occurs in DFHMCP or DFHMCX:
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.
The transaction is abnormally terminated with a CICS transaction dump.
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.
DFHPBP, DFHMCP (for minimum-function BMS), DFHMCX
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.
The transaction is abnormally terminated with a CICS transaction dump.
Redefine the route list.
DFHMCP
DFHTPR or DFHTPP has issued a DFHDI TYPE=SEND and has received a return code other than "FUNCERR-REQUEST FOR CHANGE DIRECTION SIGNALED" or "NORESP"
The transaction is abnormally terminated with a CICS transaction dump.
Inform your system programmer.
DFHTPP, DFHTPR
DFHTPR or DFHTPP has detected an invalid datastream or DFHWBBMS detected invalid forms data while processing a basic mapping support (BMS) request.
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.
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.
DFHTPP, DFHTPR, DFHWBBMS
The value specified for the length option of the basic mapping support (BMS) send map is greater than the length of the ‘from’ area.
The transaction is abnormally terminated with a CICS transaction dump.
Redefine the value for the length option.
DFHPBP
The user has requested a basic mapping support (BMS) service that was not specified at system generation, or at initialization.
The transaction is abnormally terminated with a CICS transaction dump.
Correlate services requested against options specified in the system generation of BMS.
Follow this procedure:
The following modules differ between standard and full-function BMS:
DFHMCP, DFHTPQ
The map specified for a BMS input mapping request was not an input map.
The transaction is abnormally terminated with a CICS transaction dump.
Either define another input map or redefine the existing map.
DFHMCP, DFHMCX, DFHMCY
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.
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
The transaction is abnormally terminated with a CICS transaction dump.
You need further assistance from IBM to resolve this problem. See 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.
DFHRLR for full-function BMS
An invalid map was specified.
The transaction is abnormally terminated with a CICS transaction dump.
Use the supplied dump to diagnose the problem. Register 6 contains the address of the BMS instruction being executed when the error was recognized.
DFHPBP
The map specified for a BMS output mapping request was not an output map.
The transaction is abnormally terminated with a CICS transaction dump.
Either define another output map or redefine the existing map.
DFHMCP, DFHMCX, DFHMCY
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.
The task is abnormally terminated with a CICS dump.
Ensure that the terminal associated with CQRY is of the 3270 or SCSPRINT family of devices.
DFHQRY
The Page Retrieval transaction (CSPG) has been initiated but the task is not terminal-oriented.
The task is abnormally terminated with a CICS dump.
Ensure that a terminal is associated with the CSPG transaction.
DFHTPR
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:
X'01' - Title address (TCAMSTA)
X'02' - Alternate I/O area address (TCAMSIOA)
X'03' - Map address (TCABMSMA)
X'04' - Header address (TCAMSHDR)
X'05' - Route list address (TCAMSRLA)
X'06' - Trailer address (TCAMSTRL)
X'07' - Map set address (TCAMSMSA)
X'08' - TIOA address (TCTTEDA)
The transaction is abnormally terminated with a CICS transaction dump.
Correct the application program that is supplying the erroneous address.
DFHMCP, DFHEMS
DFHRLR has detected an invalid route list entry.
The transaction is abnormally terminated with a CICS transaction dump.
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.
DFHRLR
A text string passed to BMS contained a set attribute order that was invalid for one of the following reasons:
The task is abnormally terminated with a CICS transaction dump.
Correct the application program.
DFHPBP
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:
The task is abnormally terminated with a CICS transaction dump.
Check the TERMINAL and TERMTYPE definitions which determined the attributes of the offending TCTTE.
DFHRLR
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.
The transaction is abnormally terminated with a CICS transaction dump.
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.
DFHMCP, DFHMCX, DFHMCY
The map specified for a basic mapping support (BMS) request could not be located.
The transaction is abnormally terminated with a CICS transaction dump.
Check if the map has been defined. If it has, check that it has been specified correctly.
DFHMCP, DFHMCX, DFHMCY
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.
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.
The transaction is abnormally terminated with a CICS transaction dump.
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.
DFHRLR
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 a task attempts to pass addresses from both TCTTEDA and TCAMSIOA, the address in TCTTEDA is the one selected.
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:
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
TYPE=MAP MCPMAP
TYPE=PAGEBLD,DATA=YES/ONLY MCPPGBLD
MCPGTIOA
TYPE=TEXTBLD,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.
The transaction is abnormally terminated with a CICS transaction dump.
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
TYPE=MAP.
R9=@OSPWA MCPPGBLD OSPTR5 has OSPTRB
(X'80') bit set and
BMS sets bit
OSPLMPB (X'08') in
OSPIND01 for
TYPE=PAGEBLD.
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
TYPE=PAGEBLD.
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.
DFHMCP
A BMS input or output request has been issued from a task that is not terminal-oriented.
The task is abnormally terminated with a CICS dump.
The task issuing a BMS input or output request must be attached to a terminal.
DFHMCP
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.
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
The transaction is abnormally terminated with a CICS transaction dump.
You need further assistance from IBM to resolve this problem. See 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:
If the page buffer length is too large, this may be because more data than intended is being built into the page. If the page buffer length is greater than the length of the storage area indicated in the preceding storage accounting area, an error has occurred in page or text building, and the page buffer extends beyond the area allocated to it (that is, storage violation).
DFHMCP, DFHTPP
A DFHTS TYPE=PURGE 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).
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 TYPE=PURGE 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.
The transaction is abnormally terminated with a CICS transaction dump.
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.
DFHMCP, DFHTPR
Transaction CSPS, scheduled internally by BMS, has not been installed.
The transaction is abnormally terminated with a CICS transaction dump.
Install the transaction CSPS (Group DFHBMS).
DFHMCP
The trailer specified to be used while building pages of text data is longer than the page.
The transaction is abnormally terminated with a CICS transaction dump.
Correct the application program that issues the request with too long a trailer.
DFHPBP
A BMS text request specified a value for the JUSTIFY option which is zero or too large for the page being built.
The transaction is abnormally terminated with a CICS transaction dump.
Correct the application program that specified too large or zero value for the JUSTIFY option.
DFHPBP
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.
The transaction is abnormally terminated with a CICS transaction dump.
Reduce the number of lines required for the header and/or trailer or increase the page size of the terminal.
DFHPBP
The task is abnormally terminated with a CICS transaction dump.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
DFHTPS
Either the principal facility of the task is not a TCTTE of the correct type, or the task has no principal facility.
The task is abnormally terminated with a CICS transaction dump.
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.
DFHTPS
An attempt to access a temporary storage queue failed.
The task is abnormally terminated with a CICS transaction dump.
Ensure that temporary storage is correctly generated.
DFHTPS
An error response was received from an invocation of a BMS TYPE=ROUTE or TYPE=STORE request.
The task is abnormally terminated with a CICS transaction dump.
Check that BMS was correctly generated.
DFHTPS
The transaction was not in send mode when it sent data to the remote system.
The task is abnormally terminated with a CICS transaction dump.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
DFHTPS
An attach request was received from the remote system without any data indicating the reason for the request.
The task is abnormally terminated with a CICS transaction dump.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
DFHTPS
An attempt to ship data to the remote system failed.
The task is abnormally terminated with a CICS transaction dump.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
DFHTPS
CICS could not find a profile for an LU6.2 transaction routing request.
CICS terminates the task abnormally.
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.
DFHTPS
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.
The task is abnormally terminated with a CICS transaction dump.
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.
DFHTPS
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).
The task is abnormally terminated with a CICS transaction dump.
See the related message produced by the domain that detected the original error.
DFHTPS
The bridge exit is not defined and could not be autoinstalled.
The task is abnormally terminated with a CICS transaction dump. The user transaction will not be started.
Either define the program using RDO or change the program autoinstall exit to allow it to be autoinstalled.
DFHBRMS, DFHBRTC
The bridge exit is disabled.
The task is abnormally terminated with a CICS transaction dump. The user transaction will not be started.
Identify why the bridge exit is disabled. Enable the bridge exit and retry the action.
DFHBRMS, DFHBRTC
The bridge exit could not be loaded.
The task is abnormally terminated with a CICS transaction dump. The user transaction will not be started.
Investigate why it cannot be loaded. It may not have been defined in the DFHRPL library.
DFHBRMS, DFHBRTC
The bridge exit is defined as remote.
The task is abnormally terminated with a CICS transaction dump. The user transaction will not be started.
Define the bridge exit as a local program.
DFHBRMS, DFHBRTC
An invalid bridge facility token was specified
The task is abnormally terminated with a CICS transaction dump. The user transaction will not be started.
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.
DFHBRXM
The bridge facility token specified is not known to CICS.
The task is abnormally terminated with a CICS transaction dump. The user transaction will not be started.
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.
DFHBRXM
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.
The task is abnormally terminated with a CICS transaction dump. The user transaction will not be started.
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.
DFHBRXM
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.
The task is abnormally terminated with a CICS transaction dump. The user transaction will not be started.
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
DFHBRXM
The USERID check failed following the call to the bridge exit.
The task is abnormally terminated with a CICS transaction dump. The user transaction will not be started.
Enter the correct password. If the password is correct or was not supplied, review the RACF definitions.
DFHBRXM
The bridge exit returned a value in BRXA_RESP that is not valid for the command for which it was invoked.
The transaction is backed out.
Change the bridge exit to only return valid response settings.
DFHBRIC, DFHBRMS, DFHBRSP, DFHBRTC
The bridge exit issued an abend.
The transaction is backed out.
Identify why the bridge exit abended.
DFHBRMS, DFHBRTC
The user transaction's profile could not be found.
The task is abnormally terminated with a CICS transaction dump. The user transaction is not started.
Check that the profile name in the user transaction definition is correct, and that this profile has been defined.
DFHBRXM
The bridge facility was invalid when a transaction started. This can occur when MAXTASK is reset to a low value on a busy system. The bridge facility can time out and be deleted before the user transaction is started.
The user transaction will abend during initialisation.
None.
DFHBRXM
CICS returned an unexpected error running the bridge exit. This is a CICS internal error.
The task is abnormally terminated with a CICS transaction dump.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
DFHBRMS, DFHBRTC
The bridge exit returned invalid data in the BRXA.
The task is abnormally terminated with a CICS transaction dump.
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 CICS Problem Determination Guide for guidance on how to proceed.
DFHBRIC, DFHBRMS, DFHBRSP, DFHBRTC, DFHXMBR
An unsupported BMS request was received by the bridge exit.
The task is abnormally terminated with a CICS transaction dump.
The bridge only supports minimum function BMS and SEND TEXT. This transaction cannot be used in a bridge environment.
DFHEMS
The link DFHL3270 command did not specify a commarea.
The task is abnormally terminated with a CICS transaction dump.
The link DFHL3270 command must specify a commarea to contain the BRIH and any message vectors.
DFHBRMR
The commarea specified in the link DFHL3270 command is shorter than the BRIH.
The task is abnormally terminated with a CICS transaction dump.
The link DFHL3270 command must specify a commarea to contain the BRIH and any message vectors.
DFHBRMR
The commarea specified in the link DFHL3270 command does not contain a valid BRIH.
The task is abnormally terminated with a CICS transaction dump.
The link DFHL3270 command must specify a commarea which must contain a valid BRIH.
DFHBRMR
A message passed to DFHBSMSG is too long. This is a CICS internal error.
CICS terminates the task abnormally with a dump.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
DFHTBS
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.
The task is abnormally terminated with a CICS transaction dump.
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.
DFH0CBRF
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.
The task is abnormally terminated with a CICS transaction dump.
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.
DFHBRMF
An error occurred when a SYNCPOINT request was issued by the bridge exit.
The task is abnormally terminated with a CICS transaction dump.
Check for other CICS messages and exception trace entries to investigate the cause of the SYNCPOINT error.
DFH0CBRE
An error occurred when a SYNCPOINT ROLLBACK request was issued by the bridge exit.
The task is abnormally terminated with a CICS transaction dump.
Check for other CICS messages and exception trace entries to investigate the cause of the SYNCPOINT ROLLBACK error.
DFH0CBRE
The bridge exit was expecting data to be passed on the BRDATA parameter of the START command. No data was found.
The task is abnormally terminated with a CICS transaction dump.
Correct the transaction which issued the START. Recompile, reload and retry.
DFH0CBAE,DFH0CBRE
An error was detected by the bridge exit when it tried to input the next message.
An exception trace is made of any error information. The task is abnormally terminated with a CICS transaction dump.
Check for other CICS messages and exception trace entries to investigate the cause of the input error.
DFH0CBAE,DFH0CBRE,DFH0CBAI
An error was detected by the bridge exit when it tried to output the next message.
An exception trace is made of any error information. The task is abnormally terminated with a CICS transaction dump.
Check for other CICS messages and exception trace entries to investigate the cause of the output error.
DFH0CBAE,DFH0CBRE
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.
The task is abnormally terminated with a CICS transaction dump.
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.
DFH0CBRF
A message received by the bridge exit, exceeded the maximum message size.
An exception trace is made of the first 4K of data in error. The task is abnormally terminated with a CICS transaction dump.
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.
DFH0CBAE,DFH0CBRE
The bridge exit detected an error in the MQCIH header passed by the client application.
An exception trace is written containing the MQCIH header. The task is abnormally terminated with a CICS transaction dump.
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.
DFH0CBAE,DFH0CBRE
The bridge exit detected an error in the data passed on the BRDATA parameter of the START command.
An exception trace is made of the data in error. The task is abnormally terminated with a CICS transaction dump.
Correct the transaction which issued the START. Recompile, reload and retry.
DFH0CBAE,DFH0CBRE
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.
An exception trace is made of the data in error. The task is abnormally terminated with a CICS transaction dump.
Check the BRXA data in the trace to see if there has been a storage overwrite, or whether the exit supports this command.
DFH0CBAE,DFH0CBRE,DFH0CBRF
The formatter detected that the input message was truncated.
An exception trace is made of the first 4K of the message. The task is abnormally terminated with a CICS transaction dump.
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.
DFH0CBRF
The formatter detected an error in a BRMQ vector passed by the client application.
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.
Correct the client application. Recompile, reload and retry.
DFH0CBRF
The formatter detected an error in a BRMQ vector header passed by the client application.
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.
Correct the client application. Recompile, reload and retry.
DFH0CBRF
The formatter could not find an ADSD vector as part of the BRMQ-RM vector when MQCIH-ADSDESCRIPTOR specified MQCADSD-MSGFORMAT.
An exception trace is made of the request. The task is abnormally terminated with a CICS transaction dump.
Correct the client application. Recompile, reload and retry.
DFH0CBRF
An error was detected by the bridge exit when it tried to open the queue for the input or output message.
An exception trace is made of any error information. The task is abnormally terminated with a CICS transaction dump.
Check for other CICS messages and exception trace entries to investigate the cause of the open error.
DFH0CBRE
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.
The transaction is abnormally terminated with a transaction dump.
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.
DFHBRMF
The client code page which has been requested by the client is not one which CICS can support.
The transaction is abnormally terminated with a transaction dump.
Ensure that the Client codepage is valid.
DFHBRMF
The bridge exit or formatter was called with an invalid BRXA-HEADER. This indicates a storage overwrite.
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.
Investigate the cause of the storage error, and retry.
DFH0CBAE,DFH0CBRE,DFH0CBRF
The bridge exit or formatter was called with an invalid BRXA-TRANSACTION-AREA. This indicates a storage overwrite.
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.
Investigate the cause of the storage error, and retry.
DFH0CBAE,DFH0CBRE,DFH0CBRF
The bridge exit or formatter was called with an invalid BRXA-COMMAND-AREA. This indicates a storage overwrite.
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.
Investigate the cause of the storage error, and retry.
DFH0CBAE,DFH0CBRE,DFH0CBRF
The bridge exit or formatter was called without a user-area. This probably indicates an error in the bridge exit.
An exception trace is made of the data in error. The task is abnormally terminated with a CICS transaction dump.
Investigate the cause of the storage error, and retry.
DFH0CBAE,DFH0CBRE,DFH0CBRF
The bridge exit or formatter was called with an invalid user-area. This indicates a storage overwrite or an error in the bridge exit.
An exception trace is made of the data in error. The task is abnormally terminated with a CICS transaction dump.
Investigate the cause of the storage error, and retry.
DFH0CBAE,DFH0CBRE,DFH0CBRF
A TC command passed to the formatter, exceeded the maximum message size.
An exception trace is made of the first 4K of data in error. The task is abnormally terminated with a CICS transaction dump.
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.
DFH0CBRF
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.
The task is abnormally terminated with a CICS transaction dump.
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.
DFH0CBRF
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.
The task is abnormally terminated with a CICS transaction dump.
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.
DFH0CBRF