Abend codes APxx

APCF
Explanation:

A CICS task has invoked a program which was defined as PL/I, but the program was not compiled with a supported PL/I compiler, or the program may not be written in the PL/I language.

System action:

CICS terminates the task, and disables the program.

User response:

Check that the program is PL/I. If the program is PL/I, recompile it with an LE conforming compiler such as VisualAge PL/I for OS/390 in which case you may need to change the source program. If the program is not PL/I, redefine it correctly.

Modules:

DFHAPLI

APCG
Explanation:

The transaction was purged either by master terminal actions or due to deadlock timeout actions as part of a request to the loader for a usable program copy. Deadlock timeout could be caused by a program whose size exceeds the available space in the DSAs or EDSAs.

System action:

CICS terminates the task with a transaction dump.

User response:

Use the dump to investigate why the transaction was purged. This may be due to waiting for loader resources or for program storage. Check the program size. It may be necessary to increase the overall size limits of the DSAs or EDSAs.

Modules:

DFHACP, DFHCRNP, DFHCRSP, DFHDBCT, DFHDBDSC, DFHEDFP, DFHEIP, DFHEICRE, DFHEIDEF, DFHEIDEL, DFHEIINS, DFHEIPSH, DFHEIQIR, DFHEIQSJ, DFHFCRP, DFHFEP, DFHICP, DFHKCQ, DFHMCP, DFHMCPE, DFHMCY, DFHMSP, DFHPCPG, DFHPHP, DFHPSIP, DFHPUP, DFHRDCAL, DFHRTC, DFHSII1, DFHSIJ1, DFHSPP, DFHSTP, DFHTACP, DFHTBSGB, DFHTCRP, DFHTDX, DFHTFP, DFHTSPA, DFHTSRP, DFHUSBP, DFHXRCP, DFHXRE, DFHXRSP, DFHZATA, DFHZATD, DFHZCPLN, DFHZGAI, DFHZQ00, DFHZNCA, DFHZOPA, DFHZXCU

APCH
Explanation:

A request for a program which CICS has identified as VS COBOL II cannot be executed because either Language Environment is not active in this address space or Language Environment cannot provide support for the COBOL language.

System action:

The transaction is abnormally terminated and the program is disabled.

User response:

Ensure that the correct Language Environment support is present. Refer to messages issued during CICS initialization to determine why COBOL support is not present.

Modules:

DFHAPLI

APCI
Explanation:

A request for a program which CICS as identified as an OS/PLI program cannot be executed because either Language Environment is not active in this address space or Language Environment cannot provide support for the PL/I language.

System action:

The transaction is abnormally terminated and the program is disabled.

User response:

Ensure that the correct Language Environment support is present. Refer to messages issued during CICS initialization to determine why PL/I support is not present.

Modules:

DFHAPLI

APCJ
Explanation:

A request for a C/370 program could not be executed either because Language Environment was unable to recognize the program as having been compiled under the C/370 Compiler, or because the program was not link-edited with the attribute AMODE(31).

System action:

The transaction is abnormally terminated and the program is disabled.

User response:

Ensure that the program is link-edited with the attribute AMODE(31). If necessary, recompile the program with a Language Environment conforming compiler such as OS/390 C/C++.

Modules:

DFHAPLI

APCK
Explanation:

A request for a C program could not be honored either because Language Environment is not active in this address space or because Language Environment cannot provide support for the C language.

System action:

The transaction is terminated abnormally and the program is disabled.

User response:

Ensure that the correct Language Environment support is present. Refer to messages issued during CICS initialization to determine why C support is not present.

Modules:

DFHAPLI

APCL
Explanation:

A request for a program which CICS has identified as 'LE-enabled' has failed because Language Environment is unable to execute the program.

System action:

The transaction is abnormally terminated and the program is disabled.

User response:

Ensure that the program has been compiled either with a Language Environment conforming compiler or with a compiler which is supported by Language Environment in compatibility mode. Refer to the Language Environment Migration Guide to verify this conformance.

If the compiler is supported, and the relevant language migration guides do not indicate any special actions, refer this problem to your installation systems programming facility.

Modules:

DFHAPLI

APCN
Explanation:

An attempt to release an internal CICS program, a mapset, or a partitionset because the program, mapset or partitionset has not been loaded or has already been deleted. This is probably an internal CICS error.

System action:

The transaction is abnormally terminated with a CICS transaction dump. The name of the program for which the RELEASE was attempted can be found in the abend dump at TCAPCPI.

User response:

This is either an internal CICS error or is due to the overwriting of CICS internal control blocks. You need further assistance from IBM to resolve this problem. See CICS® Problem Determination Guide for guidance on how to proceed.

Modules:

DFHAMPEN, DFHFEP, DFHMCP, DFHMCPE, DFHMCY, DFHPHP, DFHTBSSP, DFHZCPLN

APCO
Explanation:

A GETMAIN of storage for LEVEL 2 trace failed during transaction initialization.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

See the related message from the domain that detected the original error.

Modules:

DFHAPXM

APCS
Explanation:

An attempt to run the program failed because CICS was unable to make a successful connection with Language Environment to determine the run-time characteristics of the program. This abend is accompanied by message DFHAP1200 which gives the reason code set by Language Environment indicating the nature of the error.

System action:

The transaction is abnormally terminated and the program is disabled.

User response:

Refer to the Language Environment Debugging Guide and Runtime Messages manual for the meaning of the reason code, and take whatever action is necessary to correct the error.

Modules:

DFHAPLI

APCT
Explanation:

One of the following has occurred:

  1. The program name in the EXEC CICS HANDLE ABEND program is not usable at the time an abend occurs because:
    • The program is not on the relocatable program library (RPL).
    • The program is disabled.
    • The program cannot be loaded.
  2. An attempt to load a mapset or partitionset failed because although the program is defined to CICS
    • It is not available on the RPL, or
    • It is disabled, or
    • It cannot be autoinstalled.
  3. An attempt to link to, load, or release an internal CICS program failed because:
    • The program is not on the RPL.
    • The program is disabled.
    • The program cannot be loaded.
Problem determination:

The trace preceding the abend indicates the program, mapset, or partitionset that could not be loaded, linked to, or released. The name is also in TCAPCEPI.

System action:

The transaction requiring the program is abnormally terminated with a CICS transaction dump.

User response:

In cases 1 and 2, define the program, mapset partitionset to CICS using CEDA and ensure it is enabled.

In case 3, the definition of a CICS-provided module is incorrect. Check for associated messages issued during CICS start up.

Modules:

DFHACP, DFHAMPEN, DFHCRSP, DFHEDFP, DFHEIP, DFHEICRE, DFHEIDEF, DFHEIDEL, DFHEIINS, DFHEIPSH, DFHEIQSJ, DFHFEP, DFHICP, DFHMCP, DFHMCPE, DFHMCY, DFHMELDE, DFHPCPG, DFHPHP, DFHPUP, DFHRDCAL, DFHSII1, DFHTBSGB, DFHTFP, DFHTSRP, DFHZCPLN, DFHZQ00, DFHZXCU

APCW
Explanation:

The program language is defined as COBOL but the level of the compiler under which it is compiled cannot be determined. Most probably, the program was compiled under an OS/VS COBOL compiler but the required level of support for that compiler is not present in the system.

System action:

The transaction is abnormally terminated and the program is disabled.

User response:

Check that the OS/VS COBOL runtime is present in the Language Environment SCEERUN dataset, and that this dataset is referenced via both STEPLIB and the DFHRPL concatenation of datasets in this CICS region. Otherwise, the program source may need to be converted and compiled with an Language Environment conforming COBOL compiler such as COBOL for OS/390 and VM.

Modules:

DFHAPLI

APCY
Explanation:

In an MVS/ESA environment, a CICS macro request has been issued from a PL/I or COBOL application. Alternatively, it is possible that the application program has been link edited without the EXEC interface module (for example, DFHECI or DFHELII) which is used by the CICS high-level language programming interface. See the CICS System Definition Guide for details of what has to be done to include this module.

System action:

The transaction is abnormally terminated and the program is disabled.

User response:

Remove the macro request from the application program.

Modules:

DFHAPLI

APCZ
Explanation:

An attempt has been made to run either an 'old-style' application program (that is, a program with a pre-release 1.6 or a DFHE program stub) or an OS/VS COBOL program, either having been link-edited with the RENT or REFR attributes. These types of programs are not reentrant and therefore cannot be loaded into read-only storage.

System action:

The transaction is abnormally terminated.

User response:

Relink the program without the RENT and REFR attributes.

Modules:

DFHAPLI

APC0
Explanation:

A serious error occurred in a call to the program manager domain when trying to link a system program.

System action:

CICS terminates the task with a transaction dump.

User response:

Use the dump to investigate why the error occurred. Look at the trace records prior to the error for abnormal conditions in processing the PGLK domain call. This may be due to a problem with directory manager, loader, or storage manager. Check the program size. It may be necessary to increase the overall size limits of the DSAs or EDSAs.

Modules:

DFHEICRE, DFHEIDEF, DFHEIDEL, DFHEIINS, DFHPCP, DFHMCY

APC1
Explanation:

A request for a TGT exceeding 64KB has been detected.

System action:

CICS abnormally terminates the transaction and disables the installed program definition.

User response:

Change the application program to reduce the working storage requirement. Perform CEMT NEWCOPY and ENABLE for the program when it has been corrected.

Modules:

DFHAPLI

Start of change
APC2
Explanation:

An illegal branch has been attempted by a Language Environment user program following an abend condition with an active handle label abend. Usually an Out-Of-Block GOTO will have resulted, implying that the program tried to branch to, for example, an inactive block.

System action:

The transaction is abnormally terminated and the program is disabled.

User response:

Use the dump and trace to determine the cause of the error and amend the GOTO in error.

Modules:

DFHAPLI

End of change
APC3
Explanation:

An attempt to run the program has failed because CICS has identified the program as 'Language Environment enabled' but Language Environment support is not present in the system.

System action:

The transaction is abnormally terminated and the program is disabled.

User response:

Refer to messages issued during CICS initialization to determine why Language Environment is not present in the system.

Modules:

DFHAPLI

APGB
Explanation:

An error has occurred releasing a lock within the Program Manager domain.

System action:

CICS abnormally terminates the task. CICS processing continues.

User response:

Contact your local IBM support center for assistance.

Modules:

DFHPGAI, DFHPGAQ, DFHPGDD, DFHPGDM, DFHPGEX, DFHPGIS, DFHPGLD, DFHPGLE, DFHPGLK, DFHPGLU, DFHPGPG, DFHPGRE, DFHPGRP, DFHPGST, DFHPGUE, DFHPGXE, DFHPGXM

Start of change
APIA
Explanation:

The transaction id (CPIH) of the Pipeline Inbound HTTP router program has been initiated invalidly, probably by entering the id at a terminal. This transaction must only be initiated by CICS internal processes.

System action:

The transaction is abnormally terminated.

User response:

Do not initiate CPIH directly.

Modules:

DFHPIDSH

End of change
Start of change
APIB
Explanation:

The Pipeline HTTP outbound router program received an error response from the Pipeline Manager when it started the pipeline.

System action:

The outbound router program is abnormally terminated.

User response:

Examine the trace and associated messages to determine why the Pipeline Manager failed to start successfully.

Modules:

DFHPIRT

End of change
Start of change
APIC
Explanation:

The Pipeline HTTP outbound router program received an error response from its attempt to do an EXEC CICS GET CONTAINER call to obtain the pipeline name from the DFHWS-PIPELINE container. Both a trace and message DFHPI0998 are issued and these will be an indication of what the error was. If the trace point id is '09DD'x then a CONTAINERERR was returned to DFHPIRT. A point id of '09DE'x indicates that a LENGERR was returned.

System action:

The outbound router program is abnormally terminated.

User response:

Examine the trace and associated messages to determine why the Pipeline failed to start successfully.

Modules:

DFHPIRT

End of change
APID
Explanation:

The CICS supplied program for handling webservices has tried to getmain storage into which to copy containers which have been passed into it. The getmain call has failed.

System action:

CICS abends the transaction with a transaction dump.

User response:

Examine the CICS joblog for associated messages, correct the problem and retry the transaction.

Modules:

DFHPITL

APIE
Explanation:

The CICS supplied program for handling webservices has tried to determine the operation which has been called for a webservice. The signature supplied did not match any of the operations on the webservice.

System action:

CICS abends the transaction with a transaction dump.

User response:

Examine the CICS joblog for associated messages, correct the problem and retry the transaction.

Modules:

DFHPITL

APIF
Explanation:

An attempt has been made to invoke a webservice in CICS but the status of the webservice is not inservice. The webservice cannot be used.

System action:

CICS abends the transaction with a transaction dump.

User response:

Examine the CICS joblog for associated messages, correct the problem and retry the transaction.

Modules:

DFHPITL

APIG
Explanation:

An attempt has been made to invoke a CICS application program but the conversion of the SOAP message or the commarea has failed.

System action:

CICS abends the transaction with a transaction dump.

User response:

Examine the CICS trace for exception traces issued from DFHPITL. These will identify the source of the failure. If validation is currently disabled for the failing WEBSERVICE then consider enabling it and reproduce the problem. This causes CICS to call a Java based program to validate the SOAP message against the WSDL for the WEBSERVICE. If the SOAP message is malformed then a message will be issued to describe the problem in more detail.

Modules:

DFHPITP

Start of change
APIH
Explanation:

The transaction id (CPIL) of the Pipeline MQ Listener program has been initiated invalidly, probably by entering the id at a terminal. This transaction must only be initiated by being triggered by an inbound Websphere MQ message.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Do not initiate CPIL directly.

Modules:

DFHPILSQ

End of change
Start of change
APII
Explanation:

An attempt has been made to use Websphere MQ as the transport for CICS Web Services, but the Websphere MQ stub CSQCSTUB could not be loaded during CICS Initialisation. The Websphere MQ library SCSQLOAD needs to be included in the DFHRPL concatenation to permit use of Websphere MQ as a transport for CICS Web Services

System action:

The attempt to use Websphere MQ as a transport for CICS Web Services has been rejected. Any further such attempts will also be rejected.

Message DFHAP0900 is produced.

The task is abnormally terminated with a CICS transaction dump.

User response:

The Websphere MQ library SCSQLOAD must be included in the DFHRPL concatenation to allow use of Websphere MQ as a transport for CICS Web Services. This is in addition to the other Websphere MQ libraries needed for MQ support in CICS.

Modules:

DFHPILSQ

End of change
Start of change
APIJ
Explanation:

A Websphere MQ function call issued by transaction CPIL was unsuccessful and has set a non-zero reason code. The transaction CPIL is used to start a PIPELINE for a message received from Websphere MQ.

System action:

Message DFHPI0111 is produced, which includes the Websphere MQ reason code. The task is abnormally terminated with a CICS transaction dump.

User response:

Check the Websphere MQ reason code in the MQ Messages and Codes manual, and examine the trace to determine why the MQ function call failed. You may need help from IBM to resolve this problem.

Modules:

DFHPILSQ

End of change
APIK
Explanation:

The CICS supplied SOAP Handler received an unexpected response from another module.

System action:

CICS attempts to run the pipeline in an error mode. No dump is taken.

User response:

Examine the CICS joblog for associated messages.

Modules:

DFHPISN

APIL
Explanation:

The CICS supplied SOAP Handler has failed with a disaster response.

System action:

CICS attempts to run the pipeline in an error mode. A dump is taken.

User response:

Keep the dump and contact your IBM Support Center.

Modules:

DFHPISN

Start of change
APIM
Explanation:

The transaction id (CPIQ) of the Pipeline Inbound MQ router program has been initiated invalidly, probably by entering the id at a terminal. This transaction must only be initiated by CICS internal processes.

System action:

The transaction is abnormally terminated.

User response:

Do not initiate CPIQ directly.

Modules:

DFHPIDSQ

End of change
Start of change
APIN
Explanation:

The transaction id (CPIS) of the Pipeline WSAT resync program has been initiated invalidly, probably by entering the id at a terminal. This transaction must only be initiated by CICS internal processes.

System action:

The transaction is abnormally terminated.

User response:

Do not initiate CPIS directly.

Modules:

DFHPIR

End of change
Start of change
APIO
Explanation:

The WSAT Registration Services program has encountered and error, which has prevented it from completing the processing of a registration or 2PC protocol request. The program is abnormally terminated.

User response:

Examine the trace and associated messages to determine why the Registration Services program has failed.

Modules:

DFHPIRS

End of change
Start of change
APIP
Explanation:

The WSAT Coordination Context header handler program has encountered an unrecoverable error, which has prevented it from successfully creating or processing a coordination context. The program is abnormally terminated.

User response:

Examine the trace and associated messages to determine why the Registration Services program has failed.

Modules:

DFHWSATH

End of change
Start of change
APIQ
Explanation:

The WSAT application handler programs has encountered an unrecoverable error, which has prevented it from creating or processing a registration message or a protocol message The program is abnormally terminated.

User response:

Examine the trace and associated messages to determine why the Registration/Protocol Services program has failed.

Modules:

DFHWSATX.

End of change
Start of change
APIR
Explanation:

The Web Services Atomic Transaction (WS-AT) handler has detected a problem. The WSAT application handler program has encountered an attempt to use one-way messages in a WS-AT message. This combination is not permitted in WS-AT. The program is abnormally terminated.

User response:

Examine the trace and associated messages to determine which messages are at fault.

Modules:

DFHWSATH

End of change
Start of change
APIS
Explanation:

CICS detected an error during transaction initialization for a web services task.

System action:

The transaction is abnormally terminated.

User response:

Examine the trace to determine the root cause of this problem.

Modules:

DFHPIXM

End of change
Start of change
APIT
Explanation:

The Web Services Atomic Transaction (WS-AT) handler has detected a problem. The attempt to resynchronize outstanding units of work has failed.

System action:

The transaction is abnormally terminated.

User response:

Investigate why the UOWs cannot be resynchronized.

Modules:

DFHPIR

End of change
APLx
Explanation:

Abend codes with ‘PL’ as the middle two characters are issued by PL/I, and are described in further detail in the OS PL/I Optimizing Compiler: Programmer’s Guide.

APP1
Explanation:

The DFHIC TYPE=GET response code was not a normal response.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Analyze the dump. The response code is in the low-order byte of register 0.

Modules:

DFHP3270

APP2
Explanation:

The length of data that has been passed to DFHP3270 via temporary storage is less than or equal to 5.

Problem determination:

Register 6 points to the data retrieved from temporary storage via a DFHIC TYPE=GET macro invocation. The layout of this data is:

Analysis: DFHP3270 has been called to handle a print request from a 3270 Information Display System terminal. It obtains from temporary storage the data to be printed, via a DFHIC TYPE=GET invocation. It ensures that some data to be printed is present. The area returned from temporary storage contains the data to be printed preceded by 4 bytes as described above. DFHP3270 has found that, because the length of data passed to it is less than or equal to 5, there is no data to be printed.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Check the user DFHTEP. If it is not at fault, submit an APAR.

If this abend has occurred, the data that DFHP3270 obtained from temporary storage was probably put there with an incorrect length. The user may have requested indirectly that this data be placed in temporary storage either by an application request for printing (for example ISSUE PRINT) or by pressing the Print Request key. However, CICS should control the data length for this request. Under normal circumstances, the only way the user could have requested directly that data is to be placed in temporary storage is in the user’s TEP. The user should check any invocations of DFHIC TYPE=PUT in handling print requests, particularly when dealing with the "printer unavailable or busy" condition, and ensure that the length field is set correctly.

Modules:

DFHP3270

APP3
Explanation:

An attempt to request data has been sent to a nonprinter or unsupported device type by either:

System action:

The transaction is abnormally terminated. A CICS transaction dump is not provided.

User response:

  1. Ensure that the terminal operator ceases to use CSPP as a transaction code, or
  2. Correct the user DFHTEP program.
Modules:

DFHP3270

APR1
Explanation:

An abnormal DFHIC TYPE=PUT response code was received during print key processing.

System action:

The transaction is abnormally terminated with a CICS transaction dump. The keyboard of the terminal on which the print key was depressed remains locked to indicate the failure of the operation.

User response:

Analyze the dump. The response code is in low-order byte of register 0.

Modules:

DFHPRK

APSJ
Explanation:

The abending transaction invoked the system spooler initialization program (DFHPSIP) illegally, that is from a program other than the CICS module, DFHSIJ1.

System action:

CICS terminates the transaction abnormally. The EXEC CICS HANDLE ABEND command can not handle this abend.

User response:

Remove any calls or links to DFHPSIP from your application programs. If you can find no invocation of DFHPSIP in your application, you need further assistance to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHPSIP

APST
Explanation:

A task issued a SPOOL command without the mandatory NOHANDLE operand.

System action:

CICS terminates the task abnormally with a dump.

User response:

Correct the syntax of the command, specifying NOHANDLE.

Modules:

DFHEPS

APSU
Explanation:

The CICS SVC passed an invalid JES interface return code to the CICS system spooler (an MVS subtask).

System action:

CICS terminates the task abnormally.

User response:

This is an internal error - check any JES failures that occurred at the same time.

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHPSPST

APSV
Explanation:

A storage area for VSAM macro return codes contained an invalid value.

System action:

CICS terminates the task abnormally with a dump.

User response:

Check the syntax and input data of the spool commands issued by the failing transaction. Check any JES failures that occurred at the same time.

Modules:

DFHPSPST

APSW
Explanation:

An abend occurred within a CICS system spooler subtask.

System action:

CICS terminates the task abnormally with a dump.

User response:

This is an internal CICS error. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHPSPST

APSX
Explanation:

A CICS storage area used for notification of invalid parameters contained an invalid value.

System action:

CICS terminates the task abnormally with a dump.

User response:

Check the syntax and input data of the spool commands issued by the failing transaction. Check any JES failures that occurred at the same time.

Modules:

DFHPSPST

APSY
Explanation:

A CICS storage area for MVS macro return codes contained an invalid value.

System action:

CICS terminates the task abnormally with a dump.

User response:

Check the syntax and input data of the spool commands issued by the failing transaction. Check any JES failures that occurred at the same time.

Modules:

DFHPSPST

APSZ
Explanation:

A CICS area, used to store a JES interface return code, contained an invalid value.

System action:

CICS terminates the task abnormally with a dump.

User response:

Check the syntax and input data of the spool commands issued by the failing transaction. Check any JES failures that occurred at the same time.

This is an internal CICS error. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHPSPST

APTI
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 will have provided 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 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.

If the master terminal operator purged the task, 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, reduce the number of tasks in the system to avoid short-on-storage situations. Another possibility is to increase the value of the DTIMOUT option for the transaction.

Modules:

DFHPSPST

APTJ
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 will have provided 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 from the domain that detected the original error.

Modules:

DFHPSPST

APUA
Explanation:

An internal error was detected when module DFHPUP was invoked. The GETSTG parameter is missing on a call to DFHPUP (PUPF).

System action:

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHPUP

APUB
Explanation:

An internal error was detected when module DFHPUP was invoked. The GETSTG parameter is missing on a call to DFHPUP (PUPU).

System action:

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHPUP

APUC
Explanation:

An internal error was detected when module DFHPUP was invoked. An invalid function code was supplied for a domain call to DFHPUP.

System action:

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHPUP

APUD
Explanation:

The RDO language definition table (DFHEITSP) could not be located in the library.

System action:

User response:

Ensure that module DFHEITSP is in the library and is valid for this release of CICS.

Modules:

DFHPUP

APUE
Explanation:

The RDO language definition table (DFHEITSP) could not be loaded because of a lack of available storage.

System action:

Processing is abnormally terminated with an operating system dump.

User response:

Allocate more storage and resubmit the offline COPY or APPEND command(s) that failed.

Modules:

DFHPUP (Batch environment)

APUF
Explanation:

Either the RDO language definition table is invalid or it is missing from the library.

System action:

User response:

Ensure that module DFHEITSP is in the library and is valid for this release of CICS.

Modules:

DFHPUP

APUG
Explanation:

An internal error was detected in module DFHPUP. Storage could not be obtained for the CSD record buffer.

System action:

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHPUP

APUH
Explanation:

An internal error was detected in module DFHPUP. Storage could not be obtained for the argument list.

System action:

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHPUP

APUI
Explanation:

An internal error was detected in module DFHPUP. Storage cannot be freed for the argument list.

System action:

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHPUP

APUJ
Explanation:

An internal error was detected in module DFHPUP. Storage cannot be freed for the CSD record buffer.

System action:

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHPUP

APUK
Explanation:

System action:

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHPUP

APUL
Explanation:

Note:
The description of this abend also applies to APUM, APUN and APUO.

CICS cannot find a match for a function code in the language definition table, because the parameterized resource definition contains an unrecognized resource type code.

The abend code issued depends on the DFHPUP operation that was invoked before the error occurred:

Abend
DFHPUP operation
APUL
FLATTEN
APUM
TRANCASE
APUN
COMPARE
APUO
BACKTRANS

The cause of the abend is either:

  1. A language definition table (DFHEITSP or DFHEITCU) in the library is invalid for the CICS release you are running, or
  2. A CICS logic error has occurred.
System action:

User response:

Your response depends on which of the two possible reasons apply:

  1. Ensure that the DFHEITSP and DFHEITCU modules in the library are valid for this release of CICS.
  2. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Modules:

DFHPUP

APUM
Explanation:

Refer to the description of abend APUL.

Modules:

DFHPUP

APUN
Explanation:

Refer to the description of abend APUL.

Modules:

DFHPUP

APUO
Explanation:

Refer to the description of abend APUL.

Modules:

DFHPUP

APUP
Explanation:

An internal error occurred in DFHPUP processing of the language definition table for RDO. There was a stack error building a keyword list for the syntax tree.

System action:

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHPUP

APUQ
Explanation:

An internal error occurred in DFHPUP processing of the language definition table for RDO. Too many keywords found in syntax expansion.

System action:

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHPUP

APUR
Explanation:

An internal error occurred in DFHPUP processing of an argument list or a CSD record buffer. The data type for a keyword field conflicts with the data type specified in the language definition table.

System action:

User response:

Ensure that the module DFHEITSP is in the library and is valid for this release of CICS.

Modules:

DFHPUP

APUS
Explanation:

An internal error occurred in DFHPUP processing of a CSD record buffer. The integer data length for a keyword field is invalid.

System action:

User response:

Ensure that the module DFHEITSP is in the library and is valid for this release of CICS.

Modules:

DFHPUP

APUT
Explanation:

An internal error occurred in DFHPUP processing of an argument list or a CSD record buffer. The keyword existence bit number, which is the KEP(1) value in language definition table DFHEITSP, is not valid.

System action:

User response:

Ensure that the module DFHEITSP is in the library and is valid for this release of CICS.

Modules:

DFHPUP .*---------------------------------------------------------------

APUZ
Explanation:

CICS has found an unrecognized resource type code in a CSD record. The unrecognized code does not match any of the function codes in the language definition table. This abend can occur for one of the following reasons:

  1. You are using a CICS release that does not support a type of definition that was created on the CSD file by a later CICS release.
  2. The language definition table (DFHEITSP or DFHEITCU) is invalid for this CICS release.
  3. The CSD manager (DFHDMP) has passed an invalid CSD record buffer to DFHPUP. This is a CICS internal logic error.
System action:

User response:

Determine which of the possible reasons caused the error. If you can eliminate reasons 1 and 2, you can assume that reason 3 applies.

Take action corresponding to the reason you have established as follows:

  1. Avoid operations on groups containing definition-types that are unsupported by the CICS release you are running.
  2. Ensure that the library contains versions of DFHEITSP and DFHEITCU that are valid for the CICS release you are running.
  3. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Modules:

DFHPUP

Start of change
APXA
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.

Modules:

DFHAPXM

End of change [[ Contents Previous Page | Next Page Index ]]