Various conditions can result in the abnormal termination (ABEND) of:
Each of these ABEND conditions is associated with a 4-character code. When one of these conditions occurs, a message is usually produced that indicates the 4-character code associated with the ABEND. The message can appear in a different region from where the abend occurred. The message may or may not indicate the abnormal termination of an IDMS task or system.
Each of the ABEND codes is explained in this chapter. For convenience, these messages are also stored in the message area of the CA IDMS dictionary (DDLDCMSG area). All messages are prefixed with the characters "ABND" which are followed by the ABEND code and have an associated "Severity" code. For standard messages, the severity has a specific meaning as explained in the Introduction of this guide. These severity codes do not apply to the ABND messages, so they are all stored with a severity of 0.
Reason:
An external request unit executing under the active DC/UCF task has abended. The abend may have been caused when the request unit exceeded the maximum time allowed between database requests, or it may have been caused by other factors, as described in the system log. If the abend condition was detected by the check-user, look around-time, or external-wait mechanism, or by the code in the IDMSREL<x> routine (teleprocessing-monitor programs only), the system writes a snap dump to the log file, if requested during system generation.
Refer to the CA IDMS System Generation Guide for a description of these abend detection mechanisms and of the SYSTEM statement ABRU SNAP/NOSNAP parameter.
Module:
IDMSSERV or IDMSTASK
Severity:
0
Reason:
GETSTG request failed. An internal logic error has occurred. Contact Technical Support.
Module:
RHDCUCFC
Severity:
0
Reason:
TIMER request failed.
An internal logic error has occurred. Contact Technical Support.
Module:
RHDCUCFC
Severity:
0
Reason:
Bad terminal ID from back-end.
An internal logic error has occurred. Contact Technical Support.
Module:
RHDCUCFC
Severity:
0
Reason:
WRITE request failed.
An internal logic error has occurred. Contact Technical Support.
Module:
RHDCUCFC
Severity:
0
Reason:
FREELTE request failed.
An internal logic error has occurred. Contact Technical Support.
Module:
RHDCUCFC
Severity:
0
Reason:
READ request failed.
An internal logic error has occurred. Contact Technical Support.
Module:
RHDCUCFC
Severity:
0
Reason:
WAIT request failed.
An internal logic error has occurred. Contact Technical Support.
Module:
RHDCUCFC
Severity:
0
Reason:
EXIT request failed.
An internal logic error has occurred. Contact Technical Support.
Module:
RHDCUCFC
Severity:
0
Reason:
TRANSFER request failed.
An internal logic error has occurred. Contact Technical Support.
Module:
RHDCUCFC
Severity:
0
Reason:
PDAT data has bad descriptor.
An internal logic error has occurred. Contact Technical Support.
Module:
RHDCUCFC
Severity:
0
Reason:
Link edit or environment error.
One of the following errors has occurred:
Module:
#UDASBCH
Severity:
0
Reason:
A UDAS application was unable to acquire enough storage to begin a conversation. The region size should be increased.
Module:
#UDASBCH
Severity:
0
Reason:
An invalid request was received by a UDAS batch front-end module from RHDCUCFC. This indicates an internal error.
Module:
#UDASBCH
Severity:
0
Reason:
A UDAS application was unable to acquire enough storage during a conversation. The region size should be increased.
Module:
#UDASBCH
Severity:
0
Reason:
A UDAS batch front-end program has received an invalid IDMS request from RHDCUCFC. This indicates an internal error.
Module:
#UDASBCH
Severity:
0
Reason:
An error was encountered using the Batch Dialog Compiler. Contact Technical Support.
Module:
ADSOBCOM
Severity:
0
Reason:
An error was encountered while executing a Batch dialog. Contact Technical Support.
Module:
ADSOBDAG
Severity:
0
Reason:
The Data Services Interface returned an unexpected error. Contact Technical Support.
Module:
IDMSBCF, IDMSOCF, IDMSOCFX
Severity:
0
Reason:
An error was encountered using the Batch logging facility. Contact Technical Support.
Module:
ADSOBLOG
Severity:
0
Reason:
DC task initiated by an external batch run unit to access data from DC queues has abended. The run unit has issued a request for a queue record that is larger than the packet-data-movement buffer allocated to contain the queue data. To increase the size of the buffer, specify a larger value in the MAX LENGTH <buffer-length-n> parameter of the BIND TASK statement. Refer to the CA IDMS Navigational DML Programming Guide for more information about batch access to DC queues and printers.
Module:
IDMSSERV
Severity:
0
Reason:
The private, internal, stack overflowed in source module IDMSXCF. This is not the TCE stack and cannot be corrected by any user action. Contact Technical Support.
Module:
IDMSBCF, IDMSOCF, IDMSOCFX
Severity:
0
Reason:
A task executing on a local 3270-or 3280-type device has abended. The BTAM line driver has encountered an undefined BTAM error code or an unexpected return code from BTAM. Attempt to reattach the line using the DCMT VARY LINE command.
Module:
RHDCD01B
Severity:
0
Reason:
Bad request code <nn> from back end.
The UCF front end has detected an invalid request code. This usually indicates one of the following conditions:
Module:
RHDCUCFC
Severity:
0
Reason:
A C load module called the "abort" function. It is typically preceded by other messages in the log which should elucidate the condition.
Module:
Abort (can be called from any SAS C load module).
Severity:
0
Reason:
RHDCWAIT has detected that a #CHAP, Change Priority, command has been issued for Task 0, RHDCMSTR or Task 1, RHDCDBRC. The task is aborted.
Module:
RHDCWAIT
Severity:
0
Reason:
RHDCCKUR has detected that a batch to CV job with an open run unit is no longer running. The run unit is aborted. This can happen if the batch job abended or ended without issuing a finish.
Module:
RHDCCKUR
Severity:
0
Reason:
A C load module called the "warning" function. This is often called from other C functions, which should give some other indication as to the problem. Module(s) =$warning (Can be called from any SAS C load module).
Severity:
0
Reason:
A UCF terminal has disconnected. The user has invoked a BYE task prior to the disconnect. This code displayed in DC087100 message. Probably application coding error.
Module:
RHDCD0ZU
Severity:
0
Reason:
A UCF terminal has disconnected. The user invoked a SUSPEND task. The terminal may have been varied out. Message DC087100 accompanies this code.
Module:
RHDCD0ZU
Severity:
0
Reason:
A UCF terminal has disconnected ABNDBSTK. An application is being transferred to Front End task and will disconnect. Message DC087100 accompanies this code.
Module:
RHDCD0ZU
Severity:
0
Reason:
The SAS C service routine L$UALOC has unsuccessfully issued an unconditional GETSTG.
Module:
L$UALOC
Severity:
0
Reason:
A C load module has issued a "longjmp" request, and the destination could not be found. This is caused by a corrupted C runtime stack and is typically the result of an internal logic error.
Contact Technical Support.
Module:
LONGJMP
Severity:
0
Reason:
A request for a CA IDMS/DC resource resulted in a DEADLOCK. The preceding message on the system log (DC001002) supplies the task code, the program name, and the resource that the DEADLOCK occurred on.
Module:
RHDCWAIT
Severity:
0
Reason:
A DML request resulted in a status with a minor code of 29 and the call in error was not followed by a ROLLBACK or ROLLBACK CONTINUE command. The task and run-unit are aborted, forcing a rollback to release resources and free the deadlock condition.
This abend should not occur for application program DML requests. This abend can occur for DML requests made within an LRF path.
Module:
IDMSDBMS
Severity:
0
Reason:
An attempt to dynamically load a nucleus module has failed. The most likely cause of this abend is attempting to run the job or started task in too small a region or partition. Other possible causes are a discrepancy between the number of entry points in the module and the number of entry points in the NLE or a corruption of the DYLE table.
Module:
RHDCLODR
Severity:
0
Reason:
An error has occurred with a severity level that has caused the system to terminate the active task. The system or the CA IDMS user program has issued a message with a severity code of 3, 4, or 5. The preceding message on the system log indicates the cause of the error and recommends corrective actions.
Module:
RHDCPCTL
Severity:
0
Reason:
A program check has occurred during run-unit processing. A system internal error has occurred, possibly because storage has been overwritten. The preceding message on the system log (DC027002) supplies the offset and PSW at which the error occurred.
Module:
RHDCPCTL
Severity:
0
Reason:
The DC task/run unit has been terminated because it has executed longer than the time specified in the system generation SYSTEM statement RUNAWAY INTERVAL parameter without an intervening wait. A possible cause of this error is a loop in the application program; the DCUF user trace facility may be helpful in detecting application-related problems. If no application-related problems are found, divide the abended task/run unit into several shorter tasks/programs or increase the runaway interval.
Module:
RHDCCSA
Severity:
0
Reason:
A DC user-mode program has invoked an invalid DC function or has specified an invalid address for a valid function. Check the address specified, examine the snap to determine whether the abend results from a user-program logic error, and use the DCUF user trace facility to determine the last DML command executed. For that command, check the parameters passed to verify that they were valid.
Module:
RHDCWAIT
Severity:
0
Reason:
An unexpected database error has occurred. Check the ERROR-STATUS value in the CA IDMS/DC Communications Block.
Module:
ADSOAODS
Severity:
0
Reason:
The task/run unit has been terminated because it has exceeded its register stack space. Increase the value of the system generation SYSTEM statement STACKSIZE parameter if necessary. If OLQ is running under the DC/UCF system, the stack size may need to be doubled.
Module:
RHDCCSA
Severity:
0
Reason:
The physical terminal has been varied offline by means of a DCMT VARY PTERM command.
Module:
RHDCD0ZU
Severity:
0
Reason:
The DC system is in the process of shutdown.
Module:
RHDCD0ZU
Severity:
0
Reason:
The front-end terminal has been disconnected or has gone out of service while performing a write operation.
Module:
RHDCD0ZU
Severity:
0
Reason:
The front-end terminal has been disconnected or has gone out of service while performing a read operation.
Module:
RHDCD0ZU
Severity:
0
Reason:
The amount of data to be transferred from the back end to the front end is larger than the I/O buffer. Increase the value specified by the BUFSIZ parameter of the #UCFUTD macro in the UCF front-end table.
Module:
RHDCD0ZU
Severity:
0
Reason:
A nonzero status has occurred in a previous ERASE command which was not followed by a ROLLBACK or ROLLBACK CONTINUE command. The run unit is aborted, forcing a rollback to preserve the integrity of the database. <nn> is the minor code of the previous call.
Module:
IDMSDBMS
Severity:
0
Reason:
Run Unit signons are currently not allowed. The CV could be quiescing or may not be completely started.
Module:
IDMSSERV
Severity:
0
Reason:
CICS/VSAMT no z/OS VSAMT subsystem installed. Run ESVSSBLD.
A CICS/VSAMT interface was started but there is no z/OS subsystem installed. Run ESVSSBLD to install the z/OS VSAMT subsystem.
Module:
IDMSINTC
Severity:
0
Reason:
CICS/VSAMT interface not active. Run ESVSINIT.
A CICS/VSAMT interface was started but the VSAMT interface is not active. Run ESVSINIT to activate the VSAMT interface.
Module:
IDMSINTC
Severity:
0
Reason:
CICS/VSAMT bad EAVT - internal error.
A CICrS/VSAMT interface was started but the EAVT block is invalid. This is an internal error.
Module:
IDMSINTC
Severity:
0
Reason:
CICS/VSAMT has no VSAMT FILES in z/OS startup CICS JCL.
A CICS/VSAMT interface was started but there are no VSAMT FILES in z/OS startup CICS JCL.
Module:
IDMSINTC
Severity:
0
Reason:
A CICS/VSAMT interface was started but there is an invalid EJCT structure. In z/OS this is an internal error. In z/VSE this means there was an error processing the SYSESVS parms at CICS startup.
Module:
IDMSINTC
Severity:
0
Reason:
CICS/VSAMT bad AMFE interface address - internal error.
A CICS/VSAMT interface was started but the AMFE interface address is invalid. This is an internal error.
Module:
IDMSINTC
Severity:
0
Reason:
CICS/VSAMT failed doing an OPEN or a CLOSE in the AMFE interface. This is a result of an error communicating with the CA IDMS/DC Central Version.
Module:
IDMSINTC
Severity:
0
Reason:
DISCONNECT timed out.
An internal logic error has occurred. Contact Technical Support.
Module:
RHDCD0ZU
Severity:
0
Reason:
ERUS SIGNON failed.
An internal logic error has occurred. Contact Technical Support.
Module:
RHDCD0ZU
Severity:
0
Reason:
ERUS RECEIVE failed.
An internal logic error has occurred. Contact Technical Support.
Module:
RHDCD0ZU
Severity:
0
Reason:
Buffer control has bad format.
An internal logic error has occurred. Contact Technical Support.
Module:
RHDCD0ZU
Severity:
0
Reason:
URB is wrong format.
An internal logic error has occurred. Contact Technical Support.
Module:
RHDCD0ZU
Severity:
0
Reason:
URB request code is invalid.
An internal logic error has occurred. Contact Technical Support.
Module:
RHDCD0ZU
Severity:
0
Reason:
ERUS FINISH failed.
An internal logic error has occurred. Contact Technical Support.
Module:
RHDCD0ZU
Severity:
0
Reason:
ERUS PHASE 2 FINISH failed.
An internal logic error has occurred. Contact Technical Support.
Module:
RHDCD0ZU
Severity:
0
Reason:
ERUS POST failed.
An internal logic error has occurred. Contact Technical Support.
Module:
RHDCD0ZU
Severity:
0
Reason:
Error during BUFFERing of the SEND/RECEIVE.
An internal logic error has occurred. Contact Technical Support.
Module:
RHDCD0ZU
Severity:
0
Reason:
Run Unit signon not allowed because front end UCF line is offline.
Module:
IDMSSERV
Severity:
0
Reason:
Run Unit signon not allowed because front end UCF line is quiescing.
Module:
IDMSSERV
Severity:
0
Reason:
Run Unit signon not allowed because front end UCF line is at max sessions.
Module:
IDMSSERV or RHDCTSKC
Severity:
0
Reason:
A #FREESTG request failed in a batch job because the address of the storage to be freed is no longer in the storage pool. This condition can occur if storage has been corrupted since the time that the storage was originally acquired.
Module:
IDMSSTGP
Severity:
0
Reason:
UCFLINE closed or abended while task was active
An internal logic error may have occurred or a shutdown immediate was issued. Contact Technical Support if an ABEND occurred in the UCF line during normal processing.
Module:
RHDCC00A
Severity:
0
Reason:
Nonzero return code from #GETLTE call.
Module:
IDMSSERV
Severity:
0
Reason:
The abend is caused by the severity of the previous message that was #WTL as a result of an internal Architect error.
Module:
ASDFCALL, ASDFCTRL
Severity:
0
Reason:
The abend is caused by the severity of the previous message that was #WTL as a result of the error.
Module:
IDBCAT
Severity:
0
Reason:
The abend is caused by the severity of the previous message that was #WTL as a result of the error.
Module:
IDBCOPY
Severity:
0
Reason:
The abend is caused by the severity of the previous message that was #WTL as a result of the error.
Module:
IDBMAIL
Severity:
0
Reason:
Invalid LTE. An error was detected while trying to resume a suspended session.
Module:
IDMSSERV
Severity:
0
Reason:
The abend is caused by the severity of the previous message that was #WTL as a result of an internal Architect error.
Module:
ASDFCOMM, ASDFIDMS
Severity:
0
Reason:
Run Unit stalled on internal wait.
Module:
IDMSSERV
Severity:
0
Reason:
A nonzero status has occurred in a critical DBMS indexing routine and the call in error was not followed by a ROLLBACK or ROLLBACK CONTINUE command. The run unit is aborted, forcing a rollback to preserve the integrity of the database. <nn> is the minor code of the previous call.
Module:
IDMSDBMS
Severity:
0
Reason:
An unrecoverable error occurred in IDMSJSRV.
This abend is preceded by a DC396xxx message identifying the specific error that occurred.
Module:
IDMSJSRV
Severity:
0
Reason:
SYSCTL open failed.
The CICS external interface attempted to open SYSCTL at startup time, but the open failed.
Module:
IDMSINTC
Severity:
0
Reason:
IDMSTRUE enable failed
The CICS external interface attempted to enable the task user exit IDMSTRUE, but the enable failed. One possible reason for this abend is that the #CICSOPT macro has been assembled without a TRANSID parameter specified.
Module:
IDMSINTC
Severity:
0
Reason:
EXEC CICS ASSIGN SYSID failed
The CICS external interface attempted to identify the interface by issuing an EXEC CICS ASSIGN SYSID, but an error was returned.
Module:
IDMSINTC
Severity:
0
Reason:
CWA is not found
The CICS external interface failed to locate the CWA.
Module:
IDMSINTC
Severity:
0
Reason:
CWADISP is already in use
The location specified on the CWADISP parameter was found to be non-zero when IDMSINTC interface was started. This indicates that some other CICS program or facility already claimed this spot in the CWA. It may be that another IDMSINTL or IDMSINTC interface specifies the same CWADISP.
Module:
IDMSINTC
Severity:
0
Reason:
EXEC CICS INQUIRE TRANSACTION(xxxx) PROGRAM(INTCNAME) failed
The CICS external interface attempted to use the CICS INQUIRE macro to establish the name of the IDMSINTC module being used, but the CICS INQUIRE failed.
Module:
IDMSINTC
Severity:
0
Reason:
CWADISP is greater than CWASIZE.
The value specified as the CWADISP for the named interface module exceeded the value of the CWASIZE.
Module:
IDMSINTC
Severity:
0
Reason:
ESVSEXIT enable failed
The CICS external interface attempted to enable the Global file exit ESVSEXIT, but the enable failed
Module:
IDMSINTC
Severity:
0
Reason:
ESVSVSAM enable failed
The CICS external interface attempted to enable the task user exit ESVSVSAM, but the enable failed
Module:
IDMSINTC
Severity:
0
Reason:
ESVSEXIT load failed for an unknown reason
The CICS external interface attempted to load the ESVSEXIT exit, but the load failed for an unknown reason
Module:
IDMSINTC
Severity:
0
Reason:
ESVSEXIT load failed - module not found
The CICS external interface attempted to load the ESVSEXIT exit, but the module was not found
Module:
IDMSINTC
Severity:
0
Reason:
IDMSOCIC load failed
The CICS external interface attempted to load IDMSOCIC at startup time, but the LOAD failed.
Module:
IDMSINTC
Severity:
0
Reason:
IDMSOCIC program is not defined to CICS
The CICS external interface attempted to load IDMSOCIC at startup time, but a PGMIDERR error occurred
Module:
IDMSINTC
Severity:
0
Reason:
CICS external interface initialization failed
The CICS external interface attempted to startup the common external interface but startup failed.
Module:
IDMSINTC
Severity:
0
Reason:
Reading a temp-storage record failed
The CICS external interface attempted to read a temp-storage record, but the read failed.
Module:
IDMSINTC
Severity:
0
Reason:
GETMAIN failed.
The CICS external interface issued a GETMAIN request, but CICS failed to allocate the requested storage.
Module:
IDMSINTC
Severity:
0
Reason:
IDMSINTC interface already started
An IDMSINTC program was invoked to start a particular IDMS interface. However, this same program had already been invoked previously in the same CICS region.
Module:
IDMSINTC
Severity:
0
Reason:
Start task failed
The CICS external interface attempted to start the non-PLT startup task, but the start failed
Module:
IDMSINTC
Severity:
0
Reason:
Receive data failed
The CICS external interface attempted to receive data passed by start task but the receive failed
Module:
IDMSINTC
Severity:
0
Reason:
K209 - error trying to attach RSYN task
The CICS external interface attempted to attach RSYN task using the name specified in the CICSOPT for RSYNTXN, and failed. You must create a CICS RSYN transaction and program for each CICS interface module used within the CICS system.
Module:
IDMSINTC
Severity:
0
Reason:
K210 - some error detected running the RSYN task
The CICS external interface attempted to attach the RSYN task using the name specified in CICSOPT for RSYNTXN, and the RSYN task specified in CICSOPT for RSYNTXN, detected some problem trying to gather the required CICS resynchronization information from the backend CV. Look at the previous CA IDMS message on the CICS JES log for the specifics of the problem that was encountered.
Module:
IDMSINTC
Severity:
0
Reason:
K211 - NODE table exceeded - MAXIDMS parm too small
The CICS external interface determined that the maximum number of backend CVs has exceeded the number specified in the CICSOPT parameter MAXIDMS. The MAXIDMS parameter should be increased to specify the maximum number of backend CVs that the IDMSINTC interface will be accessing.
Module:
IDMSINTC
Severity:
0
Reason:
K212 - TRUE table exceeded - MAXCON parm too small
The CICS external interface determined that the maximum number of backend CVs has exceeded the number specified in the CICSOPT parameter MAXCON. The MAXCON parameter should be increased to specify the maximum number of backend CVs that can participate in a CICS unit of work (UOW).
Module:
IDMSINTC
Severity:
0
Reason:
K213 - conflicting CICSOPT TPNAME detected
The CICS external interface determined that the CICSOPT parm TPNAME used for the IDMSINTC interface being started conflicts with the TPNAME used for another IDMSINTC interface that has been previously started for this CICS system. It is recommended that the TPNAME value be the same for all IDMSINTC interfaces within a single CICS system. If it is imperative that two interfaces on the same CICS system have different TPNAME values, then you must include a SYSIDMS DD statement in the startup JCL for your CICS system.
The SYSIDMS input must include a CICS_NAME parameter to uniquely identify the CICS system.
Module:
IDMSINTC
Severity:
0
Reason:
K214 - "USERCNT" parameter has been exceeded
The size of the internal temporary storage table CA IDMS maintains to track active run units has been exceeded. This value is specified via the "CICSOPTS" macro. The default value is 100.
Module:
IDMSINTC
Severity:
0
Reason:
An unexpected internal error was detected in the IDMSLINR module.
Module:
IDMSLINR
Severity:
0
Reason:
An error was encountered using the Batch logging facility. Contact Technical Support.
Module:
ADSOLOGR
Severity:
0
Reason:
A subprogram encountered an error but was unable to return a message to its caller because no message buffer was provided by the caller.
Module:
IDMSUTIL, IDMSULIO, IDMSMSGM
Severity:
0
Reason:
An internal error has occurred in the module IDMSRCOM, during an attempt to issue an error message. Print the task snap before calling Technical Support.
Module:
IDMSRCOM
Severity:
0
Reason:
The task has been terminated following a DCMT VARY PROGRAM NEW COPY IMMEDIATE request that named a program being used by the task.
Module:
RHDCMTPR
Severity:
0
Reason:
The DC task has been terminated following a DCMT VARY ACTIVE TASKTERMINATE request that named the code associated with the executing task. The terminate request originated either from a DCMT task invocation or from the Realtime Monitor component of the CA IDMS Performance Monitor.
Module:
RHDCMTTA
Severity:
0
Reason:
An attempt to allocate a null PDE in the batch environment has failed. Rerun the SYSGEN, increasing the number of primary undefined PDEs.
Module:
RHDCLODR
Severity:
0
Reason:
An attempt to load a program into the storage pool has failed in the batch environment or while starting up central version due to lack of storage. Rerun the job in a larger region or partition.
Module:
RHDCLODR
Severity:
0
Reason:
A task code sent from the front end is not defined on the back end DC system.
Module:
RHDCTSKC
Severity:
0
Reason:
An internal error has occurred in CA OLQ An OLQ level12 message has been issued which indicates the type of error and module where it occurred.
Module:
IDMSOLQS, etc.
Severity:
0
Reason:
A partially-applied PTF has attempted to branch into the CA OLQ patch module. This module does not have the corresponding patch applied to it. Check the log for the halfword offset to where the patch was not applied.
Module:
OLQSP102
Severity:
0
Reason:
The task has been terminated due to a C XX CANCEL command entered from the OPER task. There is a shortage of CSA space or there has been a packet request of more than the 32K-byte maximum.
Module:
RHDCOPER
Severity:
0
Reason:
Run Unit signon not allowed because front-end taskid is out of service.
Module:
RHDCTSKC
Severity:
0
Reason:
Insufficient storage to access a PAKET work area required for an external request unit executing under the active DC/UCF task.
Module:
IDMSTASK
Severity:
0
Reason:
Run Unit signon for this program not allowed because it is not defined as an IDMS PROGRAM and all batch-CV programs must be defined. Or the IDMS PROGRAM is offline. Or the signon is using a different subschema than the one defined in the IDMS PROGRAM table.
Module:
IDMSSERV
Severity:
0
Reason:
An unrecoverable error was encountered by IDMSQSRT.
Contact Technical Support.
Module:
IDMSQSRT
Severity:
0
Reason:
An unrecoverable error was encountered by IDMSQSRV.
Contact Technical Support.
Module:
IDMSQSRV
Severity:
0
Reason:
The DC task has been abended following a DCMT QUIESCE AREA command because the task is holding an update lock on an area that is trying to be quiesced.
Module:
RHDCDBRC
Severity:
0
Reason:
The abend is caused by the severity of the previous message that was printed.
Module:
IDMSRAD6
Severity:
0
Reason:
The abend occurs because no storage was available to print an error message.
Module:
IDMSRAD6
Severity:
0
Reason:
A task executing under VTAM has been terminated. The VTAM line driver has encountered an invalid return code or an unexpected return code from a VTAM macro.
Module:
RHDCD05V
Severity:
0
Reason:
The previous error message should have caused an abend. The abend probably did not occur because its severity was changed in the Dictionary.
Module:
IDMSRCM1
Severity:
0
Reason:
The previous error message should have caused an abend. The abend probably did not occur because its severity was changed in the Dictionary.
Module:
IDMSROLI
Severity:
0
Reason:
The VTAM SNA driver has abended due to an unrecoverable shortage of RPLs. It may be necessary to increase the amount of RPLs defined to the VTAM SNA line in order to correct this problem.
Module:
RHDCD0EV
Severity:
3
Reason:
The task has been terminated following an abend request issued by a 3270 terminal user.
Module:
RHDCD01B
Severity:
0
Reason:
The task has been terminated by resynchronization services. This occurs when resynchronization detects backend tasks that are still awaiting a response from a front-end after that front-end has recycled. Those tasks will be aborted with an RSYN abend code.
Module:
IDMSTMGC
Severity:
0
Reason:
RUNAWAY task detected. The preceding message on the system log (DC002001) specifies task code running at the time the problem occurred.
Module:
RHDCWAIT
Severity:
0
Reason:
Operator shutdown was requested in a Batch dialog. Contact Technical Support.
Module:
ADSORUNB
Severity:
0
Reason:
z/OS only. A security violation was detected during an attempt to use IDMS SVC number 172. The user program is abended with system completion code EAC. Possible causes are:
When attempting to use the Secured SVC, additional possible causes are:
Module:
IDMSMSVC
Severity:
9
Reason:
z/OS only. A security violation was detected during an attempt to use IDMS SVC number 173. The user program is abended with system completion code EAD. Possible causes are:
When attempting to use the Secured SVC, additional possible causes are:
Module:
IDMSMSVC
Severity:
9
Reason:
z/OS only. A security violation was detected during an attempt to use IDMS SVC number 174. The user program is abended with system completion code EAE. Possible causes are:
When attempting to use the Secured SVC, additional possible causes are:
Module:
IDMSMSVC
Severity:
9
Reason:
z/OS only. A security violation was detected during an attempt to use IDMS SVC number 175. The user program is abended with system completion code EAF. Possible causes are:
When attempting to use the Secured SVC, additional possible causes are:
Module:
IDMSMSVC
Severity:
9
Reason:
z/OS only. A security violation was detected during an attempt to use IDMS SVC number 176. The user program is abended with system completion code EB0. Possible causes are:
When attempting to use the Secured SVC, additional possible causes are:
Module:
IDMSMSVC
Severity:
9
Reason:
z/OS only. This is actually an IBM message and is only documented here as a special courtesy to our clients. In all cases, the current IBM description shall take precedence. (IDMS) SVC number 172 has not been installed.
Module:
z/OS SVC FLIH
Severity:
9
Reason:
z/OS only. This is actually an IBM message and is only documented here as a special courtesy to our clients. In all cases, the current IBM description shall take precedence. (IDMS) SVC number 173 has not been installed.
Module:
z/OS SVC FLIH
Severity:
9
Reason:
z/OS only. This is actually an IBM message and is only documented here as a special courtesy to our clients. In all cases, the current IBM description shall take precedence. (IDMS) SVC number 174 has not been installed.
Module:
z/OS SVC FLIH
Severity:
9
Reason:
z/OS only. This is actually an IBM message and is only documented here as a special courtesy to our clients. In all cases, the current IBM description shall take precedence. (IDMS) SVC number 175 has not been installed.
Module:
z/OS SVC FLIH
Severity:
9
Reason:
z/OS only. This is actually an IBM message and is only documented here as a special courtesy to our clients. In all cases, the current IBM description shall take precedence. (IDMS) SVC number 176 has not been installed.
Module:
z/OS SVC FLIH
Severity:
9
Reason:
The system is short on RLEs, RCEs, or DPEs. The preceding message on the system log (DC002003, DC002004, or DC002005) specifies the task code running at the time the shortage occurred.
Module:
RHDCWAIT
Severity:
0
Reason:
The task has been terminated following a DCMT SHUTDOWN IMMEDIATE request. The database is no longer available for processing, and the DC system is no longer active.
Module:
RHDCWTL
Severity:
0
Reason:
The userid associated with the front-end job or task was rejected by the back end security system.
Module:
RHDCTSKC
Severity:
0
Reason:
An unexpected internal error was detected in the IDMSSORT module.
Module:
IDMSSORT
Severity:
0
Reason:
Bad data was received from a C printf request. This is typically the result of a logic error in some SAS C-based module.
Module:
printf (in some SAS C load module).
Severity:
0
Reason:
A backend RUN UNIT aborted and the STAE exit was invoked. However there was no abort code associated with the aborted run unit so this one was assigned. If CICS, the front end is notified so it can abend.
Module:
IDMSSERV
Severity:
0
Reason:
A security check on the task code failed.
Module:
RHDCTSKC
Severity:
0
Reason:
A task executing under VTAM has been terminated. The VTAM line driver cannot be started because a MODCB or SETLOGON command has failed, or an unexpected return code from a VTAM macro has been encountered.
Module:
RHDCD05V
Severity:
0
Reason:
An unrecoverable error was encountered manipulating save points. This abend will generally be preceded by a message identifying the specific error that was encountered.
Module:
IDMSQCLI(IDMSQASM)
Severity:
0
Reason:
UCF line is out of service.
An internal logic error has occurred. Contact Technical Support.
Module:
RHDCD0ZU
Severity:
0
Reason:
Bad front-end terminal ID.
An internal logic error has occurred. Contact Technical Support.
Module:
RHDCD0ZU
Severity:
0
Reason:
No matching PTE found for printer.
The front-end program is attempting to connect a printer terminal to the back end; however, no PTE exists for which the value specified by the NAME parameter of the PTERM statement matches the UCF front-end terminal identifier.
Module:
RHDCD0ZU
Severity:
0
Reason:
Matching PTE is quiesced.
The physical terminal has been varied offline by means of a DCMT VARY PTERM command.
Module:
RHDCD0ZU
Severity:
0
Reason:
Matching PTE is active.
An internal logic error has occurred. Contact Technical Support.
Module:
RHDCD0ZU
Severity:
0
Reason:
Matching PTE is conversing.
An internal logic error has occurred. Contact Technical Support.
Module:
RHDCD0ZU
Severity:
0
Reason:
Back-end terminal is not a printer.
The front-end program is attempting to connect a printer terminal to the back end; however, the corresponding logical terminal was not defined as a printer in the SYSGEN LTERM statement.
Module:
RHDCD0ZU
Severity:
0
Reason:
System ID is not in table.
The value specified by the SYSTEM parameter of the #UCFUFT macro in the front-end table does not match any of the front-end system identifiers defined by #FESTENT macros in the back-end system table.
Module:
RHDCD0ZU
Severity:
0
Reason:
System is quiescing or is not online.
The system specified by the #UCFUFT macro in the front-end table has been quiesced or varied offline by means of a DCMT VARY UCF command.
Module:
RHDCD0ZU
Severity:
0
Reason:
RE-SINON - terminal names do not match.
This abend code usually indicates that the terminal has been idle for a period of time that exceeds the resource timeout interval defined for the back-end system.
Module:
RHDCD0ZU
Severity:
0
Reason:
RE-SINON - session numbers do not match.
This abend code usually indicates that the terminal has been idle for a period of time that exceeds the resource timeout interval defined for the back-end system.
Module:
RHDCD0ZU
Severity:
0
Reason:
PTE not conversing, or is suspended.
An internal logic error has occurred. Contact Technical Support.
Module:
RHDCD0ZU
Severity:
0
Reason:
Printer not disconnected.
An internal logic error has occurred. Contact Technical Support.
Module:
RHDCD0ZU
Severity:
0
Reason:
No available PTERM.
All of the UCF-type physical terminals defined for the back-end system are either in use or out of service.
Module:
RHDCD0ZU
Severity:
0
Reason:
Nothing for printer to print.
The print task has been invoked with nothing to print.
Module:
RHDCD0ZU
Severity:
0
Reason:
RE-SINON PTERM has no LTERM.
Another attempt has been made to sign on to a physical terminal that has no associated logical terminal.
Module:
RHDCD0ZU
Severity:
0
Reason:
New SINON to a suspended PTERM.
An attempt has been made to sign on to a physical terminal that has a suspended session.
Module:
RHDCD0ZU
Severity:
0
Reason:
Matching PTERM waiting for VARY IN.
The signon physical terminal is in the process of being varied in service.
Module:
RHDCD0ZU
Severity:
0
Reason:
FAILURE IN SIGNON TO SECURITY.
An attempt was made to connect to a UCF back-end, but the front-end user was not a valid user known to the internal or external security system used on the back-end. If MULTIPLE SIGNONS IS NO has been specified during system generation and the front-end user is already signed-on to the CV, this S019 abend code will also be returned. Also note that after some abends of UCF-batch jobs (e.g. RHDCUCFC ABEND - 0073 or 1473), the front-end user will remain signed-on to the CV.
Module:
RHDCD0ZU
Severity:
0
Reason:
RESIGNON - ERE ALREADY QUEUED.
An attempt was made to connect to a particular back-end terminal, but another front-end session is already waiting to connect to the same terminal
Module:
RHDCD0ZU
Severity:
0
Reason:
RESIGNON - ERE ALREADY QUEUED.
A terminal timed out or was varied offline while a front-end session was in the process of connecting to the back-end terminal
Module:
RHDCD0ZU
Severity:
0
Reason:
An attempt was made to connect to a UCF back-end, but no storage was available (for example, system SOS) to allocate a Security Request Block (SRB) required to SIGNON to the back-end security system.
Module:
RHDCD0ZU
Severity:
0
Reason:
An unrecoverable error was encountered by IDMSTMGR.
This abend is always preceded by a DC329xxx message identifying the specific error that was encountered.
Module:
IDMSTMGR, IDMSTMGC
Severity:
0
Txxx
Reason:
An invalid SVC has been issued for a program which is under the control of SVC Screening on a CA IDMS online system. This can occur if an illegal verb is issued from a COBOL, C, or PL/I program or an assembler LE-compliant program. It can also occur if a non-LE-compliant program issues an SVC and the program has been invoked from a high level language program without going through a TRANSFER CONTROL to allow the CA IDMS online system to handle the transfer.
The actual abend code will be Txxx where xxx is the hexadecimal equivalent of the SVC number. For example, if SVC 56 is invalidly issued,the abend code will be 038.
For more information about SVC screening, see the appropriate DML guide and the System Operations Guide.
Module:
RHDCOSCR, RHDCSCRN
Severity:
0
Reason:
Temp storage record not found
The CICS task termination exit could not find the temp storage record for the terminating task
Module:
IDMSTRUE
Severity:
0
Reason:
Temp storage read error
The CICrS task termination exit could not read the temp storage record for the terminating task
Module:
IDMSTRUE
Severity:
0
Reason:
CICS freemain failed
The CICS task termination exit received a bad return code on a CICS freemain request
Module:
IDMSTRUE
Severity:
0
Reason:
Abend while in system-mode
The CICS task termination exit can not continue since an abend already occurred while the external interface was in system mode. This is an internal error
Module:
IDMSTRUE
Severity:
0
Reason:
Start of a CICS task failed
The CICS task termination exit failed to start another CICS task
Module:
IDMSTRUE
Severity:
0
Reason:
A suspended session has timed out.
The CICS task termination exit forced off a timed out suspended session
Module:
IDMSTRUE
Severity:
0
Reason:
UCF Line not genned.
Module:
IDMSSERV
Severity:
0
Reason:
The nucleus module necessary to process the requested function was not loaded by DC at startup because the corresponding component was not specified in the SYSGEN. The preceding message on the system log (DC002002) supplies the task code, the program name, and the nucleus module name for the requested function.
Module:
RHDCWAIT
Severity:
0
Reason:
Run Unit signon request is coming from an unsupported front end release or the ERETYPE is invalid.
Module:
IDMSSERV
Severity:
0
Reason:
The DC task has been abended following a DCMT VARY AREA command because the task is holding a conflicting lock on an area that is trying to be Varied with the IMMEDIATE option.
Module:
RHDCDBRC
Severity:
0
Reason:
A #FREESTG request failed in a batch job because the storage to be freed has had its bookends overlayed with other data. This condition can occur if storage has been corrupted since the time that the storage was originally acquired.
Module:
IDMSSTGP
Severity:
0
Reason:
An external request unit is no longer active. CHKUSER will now abort the internal portion of the request unit.
Severity:
0
Reason:
An unrecoverable error occurred in IDMSXCLI.
This abend is preceded by a DB395xxx message identifying the specific error that occurred.
Module:
IDMSXCLI
Severity:
0
Reason:
Run Unit stalled on external wait.
Module:
IDMSSERV
Severity:
0
Reason:
Invalid UCFC function code.
An internal logic error has occurred. Contact Technical Support.
Module:
UCFCICS, RHDCDBDC
Severity:
0
Reason:
Invalid IDMS function code.
An internal logic error has occurred. Contact Technical Support.
Module:
UCFCICS, RHDCDBDC
Severity:
0
Reason:
Front-end table not linked in.
The front-end program, UCFCICS or RHDCDBDC, has not been installed properly. The linkage editor statements must include a front-end table module and the RHDCUCFC module.
Module:
UCFCICS, RHDCDBDC
Severity:
0
Reason:
Task has no terminal.
UCF dedicated tasks and intermittent tasks must be associated with an interactive terminal.
Module:
RHDCDBDC
Severity:
0
Reason:
No usable #UCFUTD in front-end table.
The UCF front-end table that is linked with RHDCDBDC or UCFCICS does not contain a UCF terminal descriptor that matches the type, model, and identifier of the user's terminal.
Module:
UCFCICS, RHDCDBDC
Severity:
0
Reason:
No printers in front-end system.
The UCF front-end program has been invoked by means of the UCF Print Control Task code, but no printer LTERMs are defined in the DC system.
Module:
RHDCDBDC
Severity:
0
Reason:
No valid printers in F-E table.
The UCF front-end program has been invoked by means of the UCF Print Control Task code or transaction ID, but the front-end table does not contain any UCF terminal descriptors for valid printers.
Module:
UCFCICS, RHDCDBDC
Severity:
0
Reason:
RHDCUCFC not linked in.
The front-end program, UCFCICS or RHDCDBDC, has not been installed properly. The linkage editor statements must include a front-end table module and the RHDCUCFC module.
Module:
UCFCICS, RHDCDBDC
Severity:
0
Reason:
PDAT has bad record descriptor.
The user storage with a STGID of PDAT (that is, the storage to be passed to the back end) does not begin with a proper record descriptor. The first halfword contains a value less than four.
Module:
RHDCDBDC
Severity:
0
Reason:
PDAT larger than buffer.
An internal logic error has occurred. Contact Technical Support.
Module:
RHDCDBDC
Severity:
0
Reason:
UCF print exit not linked in.
Module:
UCFCICS
Severity:
0
Reason:
PUT to CICS temporary storage failed.
A DFHTS TYPE=PUT macro has failed. Contact Technical Support.
Module:
UCFCICS
Severity:
0
Reason:
DFHIC TYPE=PUT failed.
A DFHIC TYPE=PUT macro has failed. Contact Technical Support.
Module:
UCFCICS
Severity:
0
Reason:
Retrieve of CICS data failed.
UCFCICS has been invoked by means of an interval control function, and an attempt to retrieve passed data with a DFHIC TYPE=GET has failed. Contact Technical Support.
Module:
UCFCICS
Severity:
0
Reason:
The TWA size is too small. This message is returned to the user; however, the task is not abended.
Module:
UCFCICS
Severity:
0
Reason:
Finishing the UCF session failed
UCFCICS has issued a @FINISH to terminate the UCF session, but the finish request failed Contact Technical Support.
Module:
UCFCICS
Severity:
0
Reason:
Internal logic error— UCFC function.
An internal logic error has occurred in the interface between RHDCUCFC and UCFTSO. Contact Technical Support.
Module:
UCFTSO
Severity:
0
Reason:
Internal logic error— IDMS verb.
An internal logic error has occurred in the interface between RHDCUCFC and UCFTSO. Contact Technical Support.
Module:
UCFTSO
Severity:
0
Reason:
RHDCUCFC not linked in.
UCFTSO has not been installed properly. The linkage editor statements for UCFTSO must include modules RHDCUCFC and IDMS.
Module:
UCFTSO
Severity:
0
Reason:
IDMS not linked in.
UCFTSO has not been installed properly. The linkage editor statements for UCFTSO must include modules RHDCUCFC and IDMS.
Module:
UCFTSO
Severity:
0
Reason:
ABEND with a dump when a function call to IDMSUTIO returned with a bad condition code/return code.
Module:
(ADSORPT0,ADSORPT1,ADSORPT2,ADSOPRT5,ADSORPT6)
Severity:
0
Reason:
ABEND without a dump when a function call to IDMSUTIO returned with a bad condition code/return code.
Module:
(ADSORPT0,ADSORPT1,ADSORPT6)
Severity:
0
Reason:
Unable to open SYSIPT file.
The JCL for UCFBTCH must include a SYSIPT file of input statements.
Module:
UCFBTCH
Severity:
0
Reason:
RHDCUCFC was not linked in.
UCFBTCH has not been installed properly. The linkage editor for UCFBTCH must include modules RHDCUCFC, IDMS, and IDMSUTIO.
Module:
UCFBTCH
Severity:
0
Reason:
IDMS was not linked in.
UCFBTCH has not been installed properly. The linkage editor for UCFBTCH must include modules RHDCUCFC, IDMS, and IDMSUTIO.
Module:
UCFBTCH
Severity:
0
Reason:
First GETMAIN failed.
Increase the size of the region/partition in which UCFBTCH is run.
Module:
UCFBTCH
Severity:
0
Reason:
Invalid UCFC function code.
An internal logic error has occurred. Contact Technical Support.
Module:
UCFBTCH
Severity:
0
Reason:
Second GETMAIN failed.
Increase the size of the region/partition in which UCFBTCH is run.
Module:
UCFBTCH
Severity:
0
Reason:
Invalid IDMS function code.
An internal logic error has occurred. Contact Technical Support.
Module:
UCFBTCH
Severity:
0
Reason:
Batch print requires printer name.
#UCFBTCH has been assembled with PRINT=YES specified. The first card of the SYSIPT file must contain a front-end terminal identifier starting in column 1.
Module:
UCFBTCH
Severity:
0
Reason:
IDMSDBMS was called without pointer to VB50. This is most likely caused by a storage overlay.
Module:
IDMSDBMS
Severity:
0
Reason:
A FIND NEXT IN SET command found a record type which is not recorded by the subschema as being in the set. This can be caused by an invalid next pointer (corrupt database) or a subschema load module which does not match the database.
Module:
IDMSDBMS
Severity:
0
Reason:
RHDCEVAL was invoked for a WHERE clause which should have given a true/false result but returned a non-valued result. This can be caused by a corrupt LRF subschema, a logic error, or a destroyed XDE stack or parmlist on the DBMS call.
Module:
IDMSDBMS
Severity:
0
Reason:
RHDCEVAL returned an unexpected return code on a call from the DBMS.
Module:
IDMSDBMS
Severity:
0
Reason:
A bad suggested page was specified in the user CALC exit. It does not belong to the range of the record.
Module:
IDMSDBMS
Severity:
0
Reason:
An invalid error code has been returned by IDMSDBIO to IDMSDBMS.
Module:
IDMSDBMS
Severity:
0
Reason:
An attempt was made to lock a dbkey of zero or null. This is probably a result of a bad database pointer.
Module:
IDMSDBMS
Severity:
0
Reason:
After deleting a logically deleted record, the DBMS was unable to adjust the other records on the page to recover the free space on the page. A possible cause is a corrupt database page.
Module:
IDMSDBMS
Severity:
0
Reason:
The SR-MR chain in the subschema load module contains a control block other than an SR51 or MR53. The likely cause is a bad or overlaid subschema load module.
Module:
IDMSDBMS
Severity:
0
Reason:
The SR-OR chain in the subschema load module contains a control block other than an SR51 or OR52. The likely cause is a bad or overlaid subschema load module.
Module:
IDMSDBMS
Severity:
0
Reason:
The end of the OR-MR chain was encountered for a set in the subschema load module before it should have. This is caused by a subschema load module that does not match the database.
Module:
IDMSDBMS
Severity:
0
Reason:
While assembling/disassembling a variable-length record, the remaining length to move went negative. The possible causes are corrupt fragment chain or RDW length, or a DBMS logic error.
Module:
IDMSDBMS
Severity:
0
Reason:
When trying to delete a root or fragment of a variable-length record, the DBMS was unable to adjust the space on a database page. The possible causes are a broken chain, corrupt page, or running in retrieval CV with retrieval nolock specified in the SYSGEN.
An ABRT17 (1117) occurs when the DBMS has problems with a fragment chain. If the abend occurs in a retrieval job, it would have to be due to an attempt to walk a variable length record's fragment chain, but the SR4 it requested could not be accessed. The SR4's dbkey is passed to the routines that issue the reads, but if that dbkey cannot be located, or it is a different record type, these routines will return a non-zero minor value from the lower level routines.
Module:
IDMSDBMS
Severity:
0
Reason:
In reading a variable-length record by dbkey, the DBMS found an RDW greater than what could be accounted for by the root and all the fragments. The possible cause is a logic error in the DBMS when the record was stored or last modified, or a bad database page.
Module:
IDMSDBMS
Severity:
0
Reason:
A problem assembling fragments or relocating records was detected. If relocating home, the record pointed to by the SR3 is not an SR3, or it cannot be read. If assembling fragments, the fragment chain is bad. If relocating record, the DBMS could not convert the current record to an SR2. The likely cause for these is a corrupt database.
Module:
IDMSDBMS
Severity:
0
Reason:
When attempting to collapse fragments, more space was requested on the current page than was available. This is caused by a dbms logic error.
Module:
IDMSDBMS
Severity:
0
Reason:
A request to open or close space on a page where the amount requested was less than 0. This is caused by either a dbms logic error or a bad line index.
Module:
IDMSDBMS
Severity:
0
Reason:
A request to open or close space on a page found the free space on the page was less than 0. This is caused by a bad SR1 for the page.
Module:
IDMSDBMS
Severity:
0
Reason:
An attempt to read a variable length record whose fragment chain is broken so that some fragments cannot be located. This is caused by a corrupt database.
Module:
IDMSDBMS
Severity:
0
Reason:
A transaction attempted to exclusively lock more than four database pages during a single DBMS call. This is caused by a DBMS logic error.
Module:
IDMSDBMS
Severity:
0
Reason:
An attempt was made to release a buffer lock on a BME that was not locked. This is caused by a DBMS logic error.
Module:
IDMSDBMS
Severity:
0
Reason:
In setting a must-write switch for a BME, the DBMS found it contained a different page than the expected one. This is caused by a DBMS logic error.
Module:
IDMSDBMS
Severity:
0
Reason:
An internal error was encountered while trying to modify data in a variable length record. This is caused by a DBMS logic error.
Module:
IDMSDBMS
Severity:
0
Reason:
An attempt was made to modify an existing record, but either the calculated length of the record is less than or equal to zero, or the record could not be read by dbkey. The probable cause is a program logic error, DBMS logic error, locking problem, or a corrupt database.
Module:
IDMSDBMS
Severity:
0
Reason:
In attempting to update a sorted set, the DBMS found a bad subschema SR-MR chain. The record type appears not to be a member in the set. This is caused by a bad subschema or a subschema that does not match the database.
Module:
IDMSDBMS
Severity:
0
Reason:
The requested length for a move of data is negative. The possible causes are a bad FD54 in the subschema, a bad line index, or a DBMS logic error.
Module:
IDMSDBMS
Severity:
0
Reason:
A problem was encountered attempting to bring home a relocated or fragmented record. This is caused by a DBMS logic error.
Module:
IDMSDBMS
Severity:
0
Reason:
An attempt was made to set a must-write switch for a page that was not exclusively locked. This is caused by a DBMS logic error.
Module:
IDMSDBMS
Severity:
0
Reason:
When searching for free space on a page, the DBMS found a line index that points into freespace or beyond the end of the database page. This is probably caused by a bad line index.
Module:
IDMSDBMS
Severity:
0
Reason:
While the DBMS attempted to store a record and connect it into its automatic sets, a set connection error occurred. The DBMS then attempted to disconnect and erase the record but was unable to do so. The probable cause is a buffer overlay.
Module:
IDMSDBMS
Severity:
0
Reason:
An unaccounted for length in a variable-length record was encountered during a store operation. The possible causes are a DBMS logic error or a bad subschema load module.
Module:
IDMSDBMS
Severity:
0
Reason:
An attempt was made to store a fragment with length less than or equal to zero. This is caused by a DBMS logic error.
Module:
IDMSDBMS
Severity:
0
Reason:
A FIND CALC request was issued for a VSAM record, but the SR51 in subschema load module is not connected to the CALC set. This is caused by a subschema load module that does not match the program.
Module:
IDMSDBMS
Severity:
0
Reason:
A page which should be a space management page is a normal database page instead. This is caused by a bad ORIGINAL PAGE SIZE clause in the AREA statement of the DMCL.
Module:
IDMSDBMS
Severity:
0
Reason:
Set name can not be found in the native VSAM set currency table (NVCT). This is caused by a set name difference between the program and the subschema load module, or the set is not in the subschema.
Module:
IDMSDBMS
Severity:
0
Reason:
The DBMS is attempting to set the generic key in the NVCT for native VSAM but cannot find the right one. This is caused by a set name difference between the program and the subschema load module, or the set is not in the subschema.
Module:
IDMSDBMS
Severity:
0
Reason:
Split SR8 up pointer is NULL. This is an internal logic error.
Module:
IDMSDBMS
Severity:
0
Reason:
No space on a page when splitting a full SR8 index record. The possible causes are a full database or failure to use page reserve on the initial index load.
Module:
IDMSDBMS
Severity:
0
Reason:
An entry for an indexed record entry cannot be found in the appropriate index. This is caused by either a bad SR8 or a bad pointer in the indexed record.
Module:
IDMSDBMS
Severity:
0
Reason:
A binary search was attempted on an empty SR8. This may be caused by a DBMS logical error or a corrupted database. This abend may also occur for a retrieval-only run-unit when a concurrent update run-unit empties the contents of the SR8 record. This is most likely to occur if the retrieval run-unit is running locally and another copy of IDMS (local or CV) is updating the index components. But it may also occur in a single CV if RETRIEVAL NOLOCKS has been specified in the CV's SYSGEN. In these later cases the retrieval run-unit should be able to be rerun with no additional corrective action.
Module:
IDMSDBMS
Severity:
0
Reason:
An attempt was made to remove an index entry from an empty SR8.
This is caused by a corrupt database.
Module:
IDMSDBMS
Severity:
0
Reason:
Adjusting the length of an SR8 resulted in a length less than or equal to 0. This is caused by key offset that is not legitimate or by a corrupt index.
Module:
IDMSDBMS
Severity:
0
Reason:
A compressed symbolic key in an SR8 has a length less than or equal to 0. This is caused by a corrupt SR8 or a DBMS logic error.
Module:
IDMSDBMS
Severity:
0
Reason:
The OR52 for the CALC set is not connected to the SR51of the record. This is caused by a mismatch of the subschema and database.
Module:
IDMSDBMS
Severity:
0
Reason:
Split of orphan-only SR8 not possible. This message indicates an internal logic error in the caller of DBMSEP3 function 2. IDMSTUNE (TUNE INDEX) is such a caller.
Module:
IDMSDBMS
Severity:
0
Reason:
The upper level SR8 of an INDEX was found not to be full size. To correct this situation you must rebuild the INDEX using UNLOAD/RELOAD, MAINTAIN INDEX, or a user written program.
Module:
IDMSDBMS
Severity:
0
Reason:
While splitting an SR8, an error was encountered in the attempt to move records on the target page to make room for the new index entries. The possible cause is a DBMS logic error.
Module:
IDMSDBMS
Severity:
0
Reason:
During an index split, one or more SR8s seem to overlap on the database page. This is caused by possible index or page corruption, or by a logic error.
Module:
IDMSDBMS
Severity:
0
Reason:
The DBMS is trying to search the index for an entry which is lower or higher than any entry at the current level, and this level is not the top level. This is caused by a DBMS logic error or a corrupted index.
Module:
IDMSDBMS
Severity:
0
Reason:
During the insertion of an entry into a sorted index the DBMS has determined that an out-of-sequence condition exists or will be caused if the insertion is completed. This may be due to contention with a concurrent transaction updating the same location within the index or an index that is already corrupt.
Module:
IDMSDBMS
Severity:
0
Reason:
During update of index currencies from member record, that same member record is found not to be current. This is caused by DBMS logic error.
Module:
IDMSDBMS
Severity:
0
Reason:
While walking an index structure, an attempt was made to read an SR8. However, the record read was not an SR8 occurrence. This may be caused by a DBMS logic error or a corrupted index.
Module:
IDMSDBMS
Severity:
0
Reason:
An SR8 or index set member record is an orphan, but its uppointer does not point to the SR8 from which it was orphaned. Probably caused by DBMS logic error or a corrupt database.
Module:
IDMSDBMS
Severity:
0
Reason:
Presspack is installed and returned a nonzero status from a compress or decompress operation. This is caused by one of the following:
Module:
IDMSDBMS
Severity:
0
Reason:
The DBMS is trying to compress a record, but it is already compressed. This is caused by a logic error.
Module:
IDMSDBMS
Severity:
0
Reason:
On a CLOSE call, the LKG for the area can not be found. There is a possible storage overlay of the VAC control block.
Module:
IDMSDBMS
Severity:
0
Reason:
While journaling an area checkpoint, the cumulative lock mode is found to be invalid. There is a possible overlay of the VAC control block.
Module:
IDMSDBMS
Severity:
0
Reason:
A nonzero return code was returned from posting a NOTIFY lock. The possible cause is an internal locking error.
Module:
IDMSDBMS
Severity:
0
Reason:
An error was encountered while trying to back out of a previous error that occurred while linking a record into its sets. The possible causes are broken database or logic error.
Module:
IDMSDBMS
Severity:
0
Reason:
A call to DBMSEP3 was made with an invalid parameter list. Contact Technical Support and provide the system snap produced by the abend for analysis.
Module:
IDMSDBMS
Severity:
0
Reason:
A retrieval-only run-unit was about to go into a loop. This is probably occurring due to a concurrent update run-unit modifying the same set occurrence that the retrieval run-unit is walking and the CV in which they are running having RETRIEVAL NOLOCK specified within its SYSGEN. The abending job should be able to be rerun without further problems. If the problem continues to occur, contact Technical Support.
Module:
IDMSDBMS
Severity:
0
Reason:
An attempt was made to initialize database procedure control blocks but the call time of the requested procedure did not match the current conditions of the run-unit. This is usually indicating some type of problem with the run-unit's RP71/AP72 structure. Contact Technical Support and provide the system snap produced by the abend for analysis.
Module:
IDMSDBMS
Severity:
0
Reason:
About to break the database on a delinking record from chain because the old next of set is not the current of set. The possible causes are broken database or logic error.
Module:
IDMSDBMS
Severity:
0
Reason:
About to break the database while linking record into chain because the next pointer in prefix does not match the set currencies. The possible causes are broken database or logic error.
Module:
IDMSDBMS
Severity:
0
Reason:
A failure in the coupling facility lock structure was detected during the processing of a global transaction lock. Determine the cause of the failure and correct it. Then restart the failing CA IDMS systems.
Module:
IDMSLMGR
Severity:
0
Reason:
The lock manager service driver (IDMSLMSD) attempted to resume execution after 5 consecutive failures, but was unable to do so. The system is abnormally terminated.
Examine the log to determine the cause of the failures. In most cases, the system can simply be restarted.
Module:
IDMSLMSD
Severity:
0
Reason:
The Restructure Compare Utility (IDMSRSTC) was unable to obtain the storage it required. Increase the region allocated to the job and rerun.
Module:
IDMSRSTM
Severity:
0
Reason:
CA IDMS has returned a nonzero status. Through the IDMS-STATUS routine, the run unit has requested an ABORT with a dump. This abend code is preceded by the following debugging information:
*+ PROGRAM NAME ..... <program-name>
*+ ERROR STATUS ..... <status-code>
*+ ERROR RECORD ..... <error-record-name>
*+ ERROR SET ........ <error-set-name>
*+ ERROR AREA ....... <error-area-name>
*+ DBKEY (IN HEX) ... <db-key>
*+ LAST GOOD RECORD . <record-name>
*+ LAST GOOD AREA ... <area-name>
*+ DML SEQUENCE ..... <internal-dml-sequence-number>
Module:
IDMSCANC
Severity:
0
Reason:
Stack overflow.
The internal memory stack based off R13 has overflowed. Either insufficient space has been allocated for the stack or a runaway task has filled it up.
Severity:
0
Reason:
An unexpected internal error was detected in the IDMSUNXD module, or in one of the IDMSDBXn modules.
Module:
IDMSUNXD, IDMSDBXn
Severity:
0
Reason:
A general purpose abend code; an informational message will print at the end of the SYSLST output. Use the message code information provided in the SYSLST output to determine the cause of the problem.
Module:
ADSOGNDB
Severity:
0
Reason:
A #GETSTG failed prior to control block initialization. The control blocks that are needed to issue standard DC/UCF messages cannot be allocated due to a problem concerning allocation of the #GETSTG macro. The most probable cause is insufficient storage in the DC/UCF storage pool. A dump accompanies the abend; the return code from the #GETSTG macro is in Register 5.
Module:
ADSOGNDB
Severity:
0
Reason:
The READY of the message area failed. In an attempt to ready the message area to obtain an error message from the dictionary, there was an unsuccessful attempt to return the status code. This abend causes a dump to be printed. The exact status code is located at X'658' from Register 11.
Module:
ADSOGNDB
Severity:
0
Reason:
An OBTAIN of the MESSAGE-116 record failed. During an obtain of a MESSAGE-116 record (used to find an error message code) from the dictionary, there was an unsuccessful attempt to return the status code. This abend causes a dump to be printed. The exact status code is located at X'658' from Register 11.
Module:
ADSOGNDB
Severity:
0
Reason:
The OBTAIN of the MSG-LINE-144 record failed. During an obtain of a MSG-LINE-144 record to find an error message description in the dictionary, there was an unsuccessful attempt to return the status code. This abend causes a dump to be printed. The exact status code is located at X'658' from Register 11.
Module:
ADSOGNDB
Severity:
0
Reason:
Stack overflow in ADSOGEN2.During what was possibly a recursive call in the ADSOGEN2 load module, an end-of-register-stack-save-area condition was reached.
Module:
ADSOBABT
Severity:
0
Reason:
A general purpose abend code for ADSOGEN2. An informational message is printed at the end of the SYSLST output. Use the message code information provided in the SYSLST output to determine the cause of the problem.
Module:
ADSOBABT
Severity:
0
Reason:
A stack overflow occurred in ADSOGNRC or ADSOGNPR. The end of the register stack save area was encountered in ADSOGNRC or ADSOGNPR.
Module:
ADSOGNRC
Severity:
0
Reason:
A general purpose abend code for ADSOGNRC or ADSOGNPR. An informational message is printed at the end of the SYSLST output. Use the message code information provided in the SYSLST output to determine the cause of the problem.
Module:
ADSOGNRC
Severity:
0
Reason:
The subschema bind failed during an attempt to start a run unit (batch only). When the subschema could not be bound, the message area could not be accessed; no dictionary message records could be read to report the error. Check with the system administrator for possible system problems. This abend causes a dump to be printed. The IDMS status code is located at X'658' from Register 11.
Module:
ADSOGNDB
Severity:
0
Reason:
The MESSAGE-116 record bind failed (batch only).The dictionary message records could not be read in order to report the error. Check with the system administrator for possible system problems. This abend causes a dump to be printed. The IDMS status code is located at X'658' from Register 11.
Module:
ADSOGNDB
Severity:
0
Reason:
The MSG-LINE-144 record bind failed (batch only).The dictionary message records could not be read in order to report the error. Check with the system administrator for possible system problems. This abend causes a dump to be printed. The IDMS status code is located at X'658' from Register 11.
Module:
ADSOGNDB
Severity:
0
Reason:
During batch processing, a database deadlock condition occurred (that is, a minor code of 29). Notify the system administrator of contention problems. This abend causes a dump to be printed. The IDMS status code is located at X'658' from Register 11.
Module:
ADSOGNDB
Severity:
0
Reason:
This is a general purpose abend code in ADSOGSYM. An informational message is printed at the end of the SYSLST output. Use the message code information provided in the SYSLST output to determine the cause of the abend.
Module:
ADSOGSYM
Severity:
0
Reason:
A stack overflow occurred in ADSOGSYM. An end-of-register-stack-save-area condition was encountered.
Module:
ADSOGSYM
Severity:
0
Reason:
A BIND record for a MESSAGE-116 or MSG-LINE-144 record failed. At the beginning of a run of ADSOBTAT, program ADSOPTAT binds a run unit to the message area so that it can read any MESSAGE-116 and MSG-LINE-144 records it might need during the job. ADSOPTAT received an unsuccessful status code. Check the status of DC/UCF and resubmit the job. This abend occurs in batch processing only.
Module:
ADSOPTAT
Severity:
0
Reason:
A SYSLST CLOSE failed; the output source and diagnostics listing was closed unsuccessfully. At the end of a run of ADSOBTAT (after any updates were made to the TAT), program ADSOPTAT called IDMSUTIO to close the SYSIPT and SYSLST files. The SYSIPT file was closed successfully, but IDMSUTIO returned a status code when it attempted to close SYSLST. This error occurs in batch processing only. Check with the system administrator for possible system problems.
Module:
ADSOPTAT
Severity:
0
Reason:
At the start of a run of ADSOBTAT (before opening the SYSIPT and SYSLST files), program ADSOPTAT called IDMSUTIO to turn off automatic parsing of the DICTNODE and DICTNAME parameters (since ADSOPTAT parses for these explicitly). IDMSUTIO returned a status code during the 'NODBN' call. This error occurs in batch processing only. Resubmit the job.
Module:
ADSOPTAT
Severity:
0
Reason:
An OBTAIN of a MESSAGE-116 record failed (with a status code other than 0000 or 0326), or an OBTAIN of the first MSG-LINE-144 owned by a MESSAGE-116 failed (with a status code other than 0000). Check the current status of DC/UCF and of the message area and resubmit the job. If the error recurs, then one of the MESSAGE-116 records used by ADSOPTAT (with a CALC key beginning DC4740..) may not own any MSG-LINE-144 records. This error occurs in batch processing only. Contact the database administration group.
Module:
ADSOPTAT
Severity:
0
Reason:
A SYSLST OPEN failed; the output source and diagnostics listing was assigned unsuccessfully. At the start of the run of ADSOBTAT (before opening the SYSIPT file or any input parameters), program ADSOPTAT called IDMSUTIO to open the SYSLST file. IDMSUTIO returned a status code and the job was terminated. Check the JCL for errors in file assignments. If the file is properly defined, then check with the system administrator for possible system problems. This abend occurs in batch processing only.
Module:
ADSOPTAT
Severity:
0
Reason:
The READY of the message area failed. When trying to ready the message area (to make a table of all the messages that might be needed during a run of ADSOBTAT), ADSOPTAT received an unsuccessful status code. Check the current status of DC/UCF and of the message area and resubmit the job. This abend occurs in batch processing only.
Module:
ADSOPTAT
Severity:
0
Reason:
The BIND SUBSCHEMA for the message run unit failed. At the beginning of a run of ADSOBTAT, program ADSOPTAT attempts to bind a run unit to the message area to build a table of any messages it might need during the job. ADSOPTAT received an unsuccessful status code. Check the status of the central version and resubmit the job. This abend occurs in batch processing only.
Module:
ADSOPTAT
Severity:
0
Reason:
A GETSTG failed prior to work area initialization. At the start of a run of ADSOBTAT, program ADSOPTAT issues a GETSTG requesting that IDMS allocate storage from the batch partition or address space. The storage is needed for ADSOPTAT's work area, and must be acquired successfully before ADSOPTAT can put out standard messages. This abend occurs in batch processing only.
Module:
ADSOPTAT
Severity:
0
Reason:
A SYSLST write failed; an attempt to write to the output source and diagnostics listing was unsuccessful. During a run of ADSOBTAT, program ADSOPTAT called IDMSUTIO to write a report line. IDMSUTIO returned a status code and the job was terminated. Check with the system administrator for possible system problems. This abend occurs in batch processing only.
Module:
ADSOPTAT
Severity:
0
Reason:
Utility abend.
A general purpose abend code to end the current job. Check the last message on SYSLST or on the job log for a message indicating the reason for the abend.
Severity:
0
Reason:
An attempt by the attach subroutine (IDMSATCM) to communicate with the system has failed. An invalid request has been encountered. This is a system internal error.
Module:
IDMSATCO, RHDCATCD
Severity:
0
Reason:
An attempt by the attach subroutine (IDMSATCM) to communicate with the system has failed. The system has failed to initialize. The following problems can be checked:
This code is issued only in the z/VSE operating environment.
Module:
RHDCATCD
Severity:
0
Reason:
An attempt by the attach subroutine (IDMSATCM) to start up the system has failed. The loader subtask could not be restarted. This message is issued only in the z/VSE operating environment.
Module:
RHDCATCD
Severity:
0
Reason:
An attempt by the attach subroutine (IDMSATCM) to start up the system has failed. A required module could not be loaded. The module should be identified by a prior message to the console and/or log.
This code is issued only in the z/VSE operating environment.
Module:
RHDCATCD
Severity:
0
Reason:
An attempt by the attach subroutine (IDMSATCM) to start up the system has failed. The IDMSLOW phase has been link edited with the startup routine, but IDMSHIGH has not. Check to make sure that both phases have been linked with the startup routine, then rerun the job. This code is issued only in the z/VSE operating environment.
Module:
RHDCATCD, IDMSATCM
Severity:
0
Reason:
An attempt by the attach subroutine (IDMSATCM) to start up the system has failed. The RHDCODVS module could not be loaded. The region is not large enough to accommodate the module or the module is in a private core-image library that has not been assigned. This code is issued only in the z/VSE operating environment.
Module:
RHDCATCD
Severity:
0
Reason:
A PROCESS statement has not been included as input to a run of the CA IDMS mapping facility. Prepare a PROCESS statement as described in the CA IDMS Mapping Facility Guide, and rerun the job.
Module:
RHDCMPUT
Severity:
0
Reason:
An attempt to map a database page number to a file has failed. A logical database page number has been generated for which no associated file description can be found in the DMCL tables. Check that all necessary areas are copied in the DMCL tables.
Module:
IDMSDBIO
Severity:
0
Reason:
An attempt to lock or unlock a buffer has failed. The system may have attempted to unlock a buffer that was locked, or to upgrade a shared lock to exclusive without first releasing it. This is a system internal error. Contact Technical Support.
Module:
IDMSDBIO
Severity:
0
Reason:
An attempt to validate a database page number has failed. The DBMS has retrieved a page that does not have the page number requested. Check the schema description to make sure that each file is associated with the correct external name and check to see that the page size of the area in the DMCL agrees with the actual page size.
Module:
IDMSDBIO
Severity:
0
Reason:
Cannot locate a required BUFFER pointer. An internal logic error has occurred. Contact Technical Support.
Module:
IDMSDBIO
Severity:
0
Reason:
An attempt to open a database file has failed. Check the JCL for a missing or invalid DD (z/OS), ASSGN statement (z/VSE), or for a mismatch between the DMCL page size and the disk dataset block size.
For VSAM files, check that the cluster has been properly defined using the IBM IDCAMS utility and that the buffer in the DMCL being used is large enough to hold the control interval (not just the page size). Also the database page must be at least 8 bytes smaller than the control interval.
Under VSAM, this error can also occur if insufficient storage exists for the required VSAM control blocks in the storage pool (DC/UCF) or in the partition (local mode).
Other possible reasons: An attempt to open an unallocated file.
Module:
IDMSDBIO
Severity:
0
Reason:
An attempt to access the database has failed because a READY statement has not been issued.
Module:
IDMSDBIO
Severity:
0
Reason:
An attempt to locate the required DMCL table has failed. The internal DMCL name does not match the external DMCL name. The internal name is the name used in the DMCL compile. The DMCL table is cataloged to the load or core-image library under the external name; these names must be identical. This error also occurs if the system is using a DMCL that was compiled under a previous release of CA IDMS.
Module:
IDMSDBIO
Severity:
0
Reason:
A deadlock on database buffers would have occurred. Increase the number of buffers.
Module:
IDMSDBIO
Severity:
0
Reason:
IDMSDBIO has detected a fatal internal error condition while handling the control blocks that represent database buffers. A possible cause is corruption of the run unit's IOP. Call Technical Support.
Module:
IDMSDBIO
Severity:
0
Reason:
An attempt to read from the database or disk journal file has failed. Typically, this error occurs as a result of one of the following:
Module:
IDMSDBIO
Severity:
0
Reason:
An attempt to write to the database or disk journal file has failed. Typically, this error occurs as a result of one of the following:
Module:
IDMSDBIO
Severity:
0
Reason:
Did not pass an FCB or BCR to OPEN
Module:
IDMSDBIO
Severity:
0
Reason:
RDJFCB failed.
Module:
IDMSDBIO
Severity:
0
Reason:
If data sharing the cache write must be successful or it could cause corruption if other CVs read the old image from cache. The task is abended.
Module:
IDMSDBIO
Severity:
0
Reason:
An attempt to write a Journal Record failed because the journal blocksize is too small, and the record cannot be split across multiple journal blocks.
Module:
IDMSDBIO
Severity:
0
Reason:
A read or write was requested for a block that is beyond the defined size of the file.
Module:
IDMSDBIO
Severity:
0
Reason:
An attempt to access a database area has failed. If running in local mode, this error indicates that the area is locked against update. If running under DC/UCF, this error indicates that the area is not available in the desired usage mode. This code can also occur when IDMSRTSR is run with the AREALOCK=ABORT option and the area to be restored has an active in-use indicator.
This code is accompanied by a user runtime status code of <nn>66.
Module:
IDMSDBIO
Severity:
0
Reason:
An attempt to unlock an area has failed because the area was not locked. A possible cause is that the UNLOCK utility statement has been run against an area in update mode to the CV.
Module:
IDMSDBIO
Severity:
0
Reason:
An attempt to open a disk journal file has failed because the journal file assignment in the JCL is incorrect. Some, but not all, disk journal files have the DUMMY (z/OS) or IGN (z/VSE) attribute. All disk journals must be assigned or dummied.
Module:
IDMSDBIO
Severity:
0
Reason:
An attempt to open a disk journal file has failed because the journal file is being used by a batch program. Check the JCL for proper assignment.
Module:
IDMSDBIO
Severity:
0
Reason:
An attempt to open a disk journal file has failed because the journal file is already being used by another system (either currently executing or abended) and NO WARMSTART was specified. WARMSTART must be specified to recover disk journals.
Module:
IDMSDBIO
Severity:
0
Reason:
An attempt to open a disk journal file has failed because the current disk journal segment could not be found. This condition indicates the presence of a faulty disk journal caused by a defective journal file header. This is a system internal error.
Module:
IDMSDBIO
Severity:
0
Reason:
An attempt to open a disk journal file has failed because more than one current journal segment has been found. The probable cause of this error is incorrect JCL. If two sets of disk journal files have been specified, check the JCL to make sure that their respective volumes have not been mixed.
Module:
IDMSDBIO
Severity:
0
Reason:
An attempt to locate the journal header or segment record has failed. Either the journal header cannot be written to the first block, or the file header table incorrectly references the journal segment headers. The probable cause of this error is the presence of a defective journal file header or disk file header.
Module:
IDMSDBIO
Severity:
0
Reason:
A journal segment table has overflowed because the page size of the disk journal is too small to accommodate the number of run-unit entries. If this error occurs frequently, increase the page size of the disk journal file in the DMCL.
Module:
IDMSDBIO
Severity:
0
Reason:
Not enough JHDS records.
Module:
IDMSDBIO
Severity:
0
Reason:
An attempt was made to read a journal header but no disk journals were defined in the DMCL. Or an internal logic error occurred was detected while attempting to read a journal header.
Module:
IDMSDBIO
Severity:
0
Reason:
The number of pages in the physical journal file is NOT equal to the number of pages specified in the DMCL. The journal was probably created using a different DMCL than the one being used by the current program.
Module:
IDMSDBIO
Severity:
0
Reason:
The database file cannot be accessed according to the disposition specified by the DMCL DISP parameter.
Module:
IDMSDBIO
Severity:
0
Reason:
Allocate or deallocate was not specified.
Module:
IDMSDBIO
Severity:
0
Reason:
Unsupported return code from IDMSIOX2 user exit. Either the IDMSIOX2 is returning an incorrect return code, or the exit being used is incompatible with the version of IDMSDBIO that you are executing.
Module:
IDMSDBIO
Severity:
0
Reason:
Unable to lock or release a database area because it is being shared with another CV and its definition did validate against the data sharing group definition. Usually, this means the DMCL area or file definition is out of sync with the DMCL definition used by another CV in the data sharing group.
Module:
IDMSDBIO
Reason:
CV startup was attempted using journals formatted with a different release of CA IDMS that is not compatible with the CA IDMS release being started. If warmstart is required, warmstart using the release of IDMS that matches the journals. If upgrading to a new release, first offload any data from the journals using the Archive Journal utility from the previous release. Then format the journals using the Format utility from the new release.
Module:
IDMSWARM
Reason:
A file was defined with memory or shared cache and the cache failed to open.
Module:
IDMSDBIO
Severity:
0
Reason:
The file info function was called and there was some problem processing the file in question.
Module:
IDMSDBIO
Severity:
0
Reason:
An attempt to allocate memory has failed. The probable cause of this error is insufficient memory available for a database buffer. If running in local mode, increase the region/partition size; if running under DC/UCF, increase the size of the storage pool.
Module:
IDMSDBIO
Severity:
0
Reason:
An attempt to load a module has failed, because it would result in a deadlock.
Module:
IDMSDBIO
Severity:
0
Reason:
An attempt to load a module has failed; the requested load module could not be found in the load (z/OS) or core-image (z/VSE) library. In most cases, the module involved is IDDSCIDD, IDDSMAIN, IDMSUBCM, or a database procedure. Check the JCL for proper assignment.
Module:
IDMSDBIO
Severity:
0
Reason:
An I/O error has occurred during an attempt to load a module dynamically. In most cases, the module involved is a subschema, DMCL, or database procedure. Rerun the job.
Module:
IDMSDBIO
Severity:
0
Reason:
An error has occurred during an attempt to close a VSAM data set.
Module:
IDMSDBIO
Severity:
0
Reason:
An I/O error has occurred during an attempt to access a native VSAM file, or an attempt has been made to run an invalid CA IDMS utility against a native VSAM file. ROLLBACK and ROLLFORWARD are the only utilities that can be used with native VSAM files. To perform other utility functions, use the appropriate IBM VSAM utility.
Module:
IDMSDBIO
Severity:
0
Reason:
An unexpected return code from an #XESLOCK request was encountered. Additional information has been saved in the IOP. Contact Technical Support.
Module:
IDMSDBIO
Severity:
0
Reason:
A shared area being recovered by Warmstart failed to validate against the current definition in use by the group. Since Warmstart should not be recovering a shared area unless it had validated previously, it suggests that perhaps there is a problem with coupling facility structures and that a group restart may be needed.
Module:
IDMSDBIB
Severity:
0
Reason:
The TCE stack area has overflowed.
Module:
IDMSDBIO
Severity:
0
Reason:
A #ABEND request has been issued for a batch job. This code is accompanied by system message DC208001 which includes the original abend code indicating the reason for the #ABEND.
Module:
IDMSPCTL
Severity:
0
Reason:
An attempt to acquire storage for a batch job has failed. Increase the size of the region/partition and rerun the job.
Module:
IDMSSTGP
Severity:
0
Reason:
A single-threaded program was already in use. Reinvoke the task or define the module in the DC/UCF system as reentrant. This abend code occurs under DC/UCF only.
Module:
IDDMFEND, IDDSFEBT, IDDSFEDC, IDDSMISC
Severity:
0
Reason:
A load conflict has occurred during an attempt to load an overlayable module. Reinvoke the task or define the module in the CV system as nonoverlayable.
Severity:
0
Reason:
In the second step of IDMSDBAN runs, the sort package has issued a nonzero return code. Check the messages issued by the sort program. This abend is accompanied by a DC599203 message that lists the nonzero return code passed by the sort program.
Severity:
0
Reason:
A DC040200 error message has been requested but due to a current problem being debugged by Technical Support and your site, a CV abend has been requested rather than the normal process associated with the DC040200 error.
Action:
Capture the dump and provide it to your CA IDMS Technical Support. Representative.
Module:
IDMSLKER
Severity:
0
Reason:
While a task was abending, the task deadlocked waiting for a resource. Message DC001002 was issued. This message requires a task abend. Since the task was already abending, this is a recursive abend.
Module:
RHDCWAIT
Severity:
0
Reason:
A task was in the process of abending and while abending, it stalled while waiting for a resource. Message DC001003 was issued. The severity of this message requires a task abend. However, the task was already abending so this is a recursive abend.
Module:
RHDCWAIT
Severity:
0
Reason:
Invalid CV startup override parameter encountered:
Module:
RHDCOS00
Severity:
0
Reason:
Failed trying to do a BLDL for required module IDMSSTRT when starting up an IDMS batch job.
Module:
RHDCOS00
Severity:
0
Reason:
An attempt has been made to bring up a z/VM version of IDMS-DC in a non-z/VM environment.
Module:
RHDCOS00
Severity:
0
Reason:
Failed trying to do a LOAD for required module IDMSSTRT when starting up an IDMS batch job.
Module:
RHDCOS00
Severity:
0
Reason:
Invalid operating system release.
An attempt has been made to start IDMS on an older version of the operating system.
This release of the operating system does not provide the functionality that CA IDMS requires.
Module:
RHDCOESA
Severity:
0
Reason:
An attempt to issue an SVC while executing in enclave SRB mode was detected.
This is an internal system logic error. Please save the dump and contact CA Technical Support.
If the problem recurs, specify ZIIP=N on the execute parm.
Module:
RHDCOESA
Severity:
0
Reason:
The SYSIDMS parm IDMSDBUG=ON was set to allow tracing of the local mode portion of CV startup. Once the local mode portion of CV startup has ended the CV must be abended, because IDMSDBUG tracing is not supported in a IDMS/DC central version.
Module:
RHDCSTRT
Severity:
0
Reason:
A mismatch has been detected in the local/shared status of a queue updated by a transaction requiring resynchronization. This abend is preceded by message DC245021 identifying the queue and the current and prior statuses. This abend occurs during system startup.
Module:
RHDCQUEM
Severity:
0
3937
Reason:
RHDCDBRC has detected a error during startup or shutdwon and aborted the CV. Another message should have been issued describing the reason.
For all other occurrences or repeat occurrences of the above mentioned messages contact CA Technical Support supplying the associated dump and the DCLOG.
Module:
RHDCDBRC
Severity:
0
Reason:
The journal sequence numbers were about to exceed (2**63)-1.This would result in negative journal sequence numbers and would cause severe problems for warmstart, ARCHIVE JOURNAL, and the recovery utilities.
For central version: Warmstart the central version and then shut it down immediately. Offload all non-empty journals using ARCHIVE JOURNAL ALL. Initialize the journals, backup all databases, and bring central version up normally.
For local mode jobs: Restore the affected databases and rerun the local mode job with the journals dummied out.
Module:
IDMSDBMS
Severity:
0
Reason:
A bad version of RHDCSRTT module has been loaded. Recompile RHDCSRTT with the IDMS macro library from the current release.
Module:
RHDCSCEN
Severity:
0
Reason:
Security init failure. An error has been detected during the initialization of the security tables (SON table or group list), or during the initialization of the external security system.
Module:
RHDCSCEN
Severity:
0
Reason:
An error occurred while processing an #MPLOCK or #MPUNLK request for the ticker or dispatcher task. This abend code applies only to sites using z/OS multitasking support.
Module:
RHDCLOCK
Severity:
0
Reason:
The system is out of interval lock elements (ILEs).This abend code applies only to sites using z/OS multitasking support.
Module:
RHDCLOCK
Severity:
0
Reason:
During startup, the system was unable to acquire storage for a packet either because the #GETSTG request failed, or because the request for storage for the z/OS CSA failed.
Module:
IDMSSERV
Severity:
0
Reason:
The system has abended because a startup autotask defined at SYSGEN with the ABEND option of the AUTOTASK statement has abended.
Module:
RHDCPCTL
Severity:
0
Reason:
The system has abended because no more deadlock prevention elements (DPEs) are available.
Module:
RHDCWAIT
Severity:
0
Reason:
The system has abended because no more resource control elements (RCEs) are available.
Module:
RHDCRMGR
Severity:
0
Reason:
The system has abended because no more resource link elements (RLEs) are available.
Module:
RHDCRMGR
Severity:
0
Reason:
A second DC/UCF system has been started using the same version number as the DC/UCF system currently running.
Severity:
0
Reason:
The deadlock detector, RHDCDEAD, has abended and the optional apar to abort the CV under this condition has been activated. This optional functionality is activated by specifying #DEFOPT OPT00202 in the RHDCOPTF module.
Severity:
0
Reason:
Multitasking support has been requested but the startup module is linked to IDMSUSVC. Multitasking support cannot be specified when the start up module is linked with IDMSUSVC. This abend code applies only to sites using z/OS multitasking support.
Module:
RHDCBLD3
Severity:
0
Reason:
An error occurred at startup while attaching one of the operating system subtasks. This abend code applies only to sites using z/OS multitasking support.
Module:
RHDCOS00
Severity:
0
Reason:
An attempt to load module RHDCSTXA has failed. The probable cause is that the module is not in CDMSLIB.
Module:
RHDCOS00
Severity:
0
Reason:
A logical error condition has been encountered in the system log during a run of the RHDCPLOG utility. Review the printed output, make the necessary corrections, and rerun the job.
Module:
RHDCPLOG
Severity:
0
Reason:
An I/O error has occurred during an attempt to write to the DDLDCLOG area. Restart the system and rerun the job.
Module:
RHDCMISC
Severity:
0
Reason:
During startup, an attempt to prepare the DDLDCRUN, DDLDCQUE,DDLDCLOG, or DDLDCLOD area has failed or an attempt to establish extent area processing has failed. Refer to the preceding message on the system log to determine the cause of the failure.
Module:
RHDCRUAL
Severity:
0
Reason:
For non-z/VSE operating systems, an attempt to attach a check-user subtask has failed. For z/VSE users, this indicates there is insufficient GETVIS storage available.
Module:
RHDCOS00
Severity:
0
Reason:
An attempt to obtain storage for a DCB for a CDMS library has failed. Increase the storage size specification using the JCL EXEC parameter FREESTG= or FSTG=.
Module:
RHDCOS00
Severity:
0
Reason:
An attempt to obtain storage to queue a message to the system log has failed.
Module:
RHDCMISC
Severity:
0
Reason:
A recursive deadlock has occurred; that is, a task has deadlocked while abending because of a previous deadlock.
Module:
RHDCPCTL
Severity:
0
Reason:
The warmstart routine has failed.
Module:
RHDCBLDT
Severity:
0
Reason:
An error has been detected in the IDMSNWKS subschema during an attempt to service a queue request. The probable cause of this error is that the SR51 record for the SEXT record could not be located. This is a system internal error.
Module:
RHDCQUEM
Severity:
0
Reason:
RHDCMSTR (TASK 0) or RHDCDBRC (TASK 1) has abended. Check for any other messages that might indicate trouble. RHDCMSTR and RHDCDBRC open files, open and initialize buffers, set up both internal and external run units, and attach line drivers. Any problem (such as JCL errors, SVC errors, or files not initialized properly) will cause a 3964 abend code to be issued. This abend code can occur at any time the DC/UCF system is executing. Program checks in user-written code for certain system-invoked exits such as exit 13 can cause this abend.
Module:
RHDCPCTL
Severity:
0
Reason:
An error has been detected in the IDMSNWKI subschema during an attempt to load a module from the dictionary. Reassemble IDMSNWKI using the installed macro.
Module:
RHDCSTRT
Severity:
0
Reason:
An attempt to load a line driver module has failed. The module associated with the physical line was not found in CDMSLIB.
Severity:
0
Reason:
No LTE can be found for a given PTE at startup.
Module:
RHDCBLDT
Severity:
0
Reason:
An attempt to ready the DDLDML or DDLDCLOD area has failed. Check the value of ERROR-STATUS in the IDMS communications block to determine the cause of the failure.
Module:
RHDCBLDT
Severity:
0
Reason:
A signon or record bind failed for the startup subschema IDMSNWKI. Verify that IDMSNWKI exists in CDMSLIB and check the value of ERROR-STATUS in the IDMS communications block.
Module:
RHDCBLDT
Severity:
0
Reason:
A task has issued a #ABEND request when the system was not allowing abends, or a recursive abend has occurred. Probable causes of this error are as follows:
Note that the writing of diagnostic messages to the log may be incomplete with this abend. The last 33 message numbers and abend codes along with the task ids of the issuing tasks can be found at CSA plus X'804'.
This code is accompanied by message DC027006.
Module:
RHDCPCTL
Severity:
0
Reason:
An attempt to terminate a runaway task has failed. The probable cause of this error is that the system generation SYSTEM statement specifies SVC IS NO. For the system to detect runaway tasks, an SVC must be used.
Severity:
0
Reason:
An attempt to switch storage keys has failed.
Possible causes are as follows:
Severity:
0
Reason:
An attempt by the system to acquire abend storage has failed. The storage area is already owned by another task. Increase the size of the working storage stack within the system's task control element (TCE) using the system generation SYSTEM statement STACKSIZE parameter.
Severity:
0
Reason:
An attempt to open a disk log file has failed. Check to determine if the file assignments are correct in the applicable JCL.
Module:
RHDCOS00
Severity:
0
Reason:
An attempt to start up the system has failed because IDMSUSVC has not been linked with the system startup routine. Either specify SVC IS YES in the system generation SYSTEM statement, or link edit IDMSUSVC with the appropriate startup routine.
Module:
RHDCBLDT
Severity:
0
Reason:
The external ECB list is empty. This is a system internal error.
Module:
RHDCWAIT
Severity:
0
Reason:
An attempt to start up the system has failed because the requested system is already active. The DC/UCF system number associated with each active system, as supplied in the system generation SYSTEM statement CVNUMBER parameter, must be unique.
This message also applies when there are two different SVC numbers with the same central version number. To ensure communication with the proper DC/UCF system at all times, the central version number should be unique. This alleviates confusion in trying to identify which CV number goes with what system.
Module:
RHDCOS00
Severity:
0
Reason:
An attempt to load the z/VSE system has failed because the FREEVIS routine did not execute properly. Normally, after the DC system has been loaded into its allocated storage space, any remaining storage is freed (with a FREEVIS) for use by the operating system and any other programs executing in the partition. This is a system internal error.
Module:
RHDCODVS, RHDCATCD
Severity:
0
Reason:
An attempt to issue a z/VSE GETVIS request from REAL mode has failed because of a request by GETVIS for a negative amount of storage. GETVIS cannot be issued from REAL mode. Either use a different storage acquisition method, such as COMREG, or do not run the system in REAL mode.
Module:
RHDCATCD
Severity:
0
Reason:
An unrecoverable problem has occurred during an attempt to update the journal header record and the area update indicator lock in the database.
Module:
RHDCDBRC
Severity:
0
Reason:
An attempt to start up the system has failed because a nonreentrant module was found in the link pack area. This abend code is accompanied by message DC390021, which provides the name of the module that has caused the problem. Remove the indicated module from the link pack area and restart the system.
Module:
RHDCSTRT
Severity:
0
Reason:
The specified system does not exist. Probable causes of this error are as follows:
Module:
RHDCBLDT
Severity:
0
Reason:
An attempt to start up the system has failed because the keys tables have been corrupted.
Module:
RHDCBLDT
Severity:
0
Reason:
An attempt to start up the system has failed because a z/VSE GETVIS request could not be executed. Review the FREESTG= parameter on the CV startup JCL and check other storage-related parameters. Increase the sizes if necessary.
Module:
RHDCATCD
Severity:
0
Reason:
A second systems program interrupt exit (SPIE) intercept occurred before task control element (TCE) SPIE information could be moved to the abend control element (ACE).
Module:
RHDCOS00
Severity:
0
Reason:
Failed trying to load a nucleus module at CV startup. The preceding message on the system log (DC999999L) supplies the nucleus module name on which the load failed.
Module:
RHDCSTRT
Severity:
0
Reason:
An I/O request failed trying to allocate an XIOB. Either all XIOB indexes were used up, or a #GETSTG for a new XIOB failed. This should happen only in a batch job.
Module:
RHDCOS00
Severity:
0
Reason:
Storage protection has been requested via the PROTECT option of the SYSTEM statement in system generation. However, the primary protect key is equal to the alternate protect key. The effect of this will be no storage protect.
Severity:
0
Reason:
A fatal error has occurred while loading the nucleus. Check to determine if the library assignment is correct in the applicable JCL and rerun the job.
Module:
RHDCSTRT
Severity:
0
Reason:
A program check has occurred and SCACURTK is zero for the TCB in control at the time of the program check. This means there is no known active IDMS-DC/UCF task running.
Module:
RHDCOMVS
Severity:
0
Reason:
An attempt to load the nucleus load table (NLT) has failed. Check to determine if the library assignment is correct in the applicable JCL and rerun the job.
Module:
RHDCSTRT
Severity:
0
Reason:
Failed trying to load a module required for CV startup. The preceding message on the system log supplies the module name on which the load failed.
Module:
RHDCSTRT
Severity:
0
Reason:
An attempt to load the system has failed because the region/partition was too small to accommodate the system configuration. Increase the size of the region/partition and rerun the job.
Module:
RHDCATCD, RHDCNTRY, RHDCODVS, RHDCSTRT
Severity:
0
Reason:
A program check error has occurred in a system program with R13 set to an invalid value. A system internal error has occurred, or a program check is present in a user-written database procedure, a user exit or startup routine, or a DC user program not running with storage protection. Contact Technical Support.
Module:
RHDCOS00
Severity:
0
Reason:
A system error has occurred with a severity level that has caused the system to abend. The system or a DC user program has issued a message with a severity code of 8 or 9. The preceding message on the system log indicates the cause of the error.
Module:
RHDCWTL
Severity:
0
Reason:
An attempt to start up the system has failed because the RHDCNTRY module was not found in the load or core-image library. Check to determine if the library assignment is correct in the applicable JCL and rerun the job.
Module:
RHDCOS00
Severity:
0
Reason:
A failure occurred trying to load
Module:
RHDCEVAL.
Severity:
0
Reason:
An ABORT command has been received from the operator, signaling the system to reject new tasks/run units. No new tasks can start execution, all active tasks are abended, and external run units are returned a status code of <nn>69 (indicating that the system is not active).
Module:
RHDCWTL
Severity:
0
Reason:
A recursive task abend has occurred in an IDMS batch job.
Module:
RHDCTSKI
Severity:
0
Reason:
An unidentified OPSYS has been defined in module IDMSSTRT. An internal logic error has occurred. Contact Technical Support.
Module:
IDMSSTRT
Severity:
0
Reason:
Failed trying to do a BLDL or a LOAD of a required module when starting up an IDMS batch job. The preceding message on the system log (DC999999L) supplies the module name on which the BLDL or LOAD failed.
Module:
IDMSSTRT
Severity:
0
Reason:
A bad entry has been detected in the IDMSNLT load table. An internal logic error has occurred. Contact Technical Support.
Module:
IDMSSTRT
Severity:
0
Reason:
Failed trying to do a BLDL or a LOAD of the RHDCCSA module when starting up an IDMS batch job.
Module:
IDMSSTRT
Severity:
0
Reason:
Failed trying to do a BLDL for the users application program when starting up an IDMS batch job. The BLDL is required to determine certain attributes of the users application program. The preceding message on the system log (DC999999L) supplies the module name on which the BLDL failed.
Module:
IDMSSTRT
Severity:
0
Reason:
Failed trying to acquire storage for internal control blocks when starting up an IDMS batch job. Increase the storage in the region and rerun the job.
Module:
IDMSSTRT
Severity:
0
Reason:
Failed trying to load the RHDCCODE module which is required when starting up an IDMS batch job.
Module:
IDMSSTRT
Severity:
0
Reason:
Failed trying to load the IDMSNLT module which is required when starting up an IDMS batch job.
Module:
IDMSSTRT
Severity:
0
Reason:
Failed trying to load the RHDCOPTF module which is required when starting up an IDMS batch job.
Module:
IDMSSTRT
Severity:
0
Reason:
Failed trying to allocate TMGR storage on call to IDMSTMMC at entry point TMMCEP1. Try increasing storage.
Module:
IDMSSTRT
Severity:
0
4012
Reason:
An attempt to start up the system has failed because the IDMSUXIT module was not found in the load or core-image library.
Action:
Check to determine if the library assignment is correct in the applicable JCL and rerun the job.
Module:
RHDCOS00
Severity:
0
4013
Reason:
An attempt to start up the system has failed because the IDMSUTAB module was not found in the load or core-image library. Check to determine if the library assignment is correct in the applicable JCL and rerun the job.
Module:
IDMSSTRT
Severity:
0
Reason:
An attempt to start up the system has failed because the RHDCTAPE module was not found in the load or core-image library. Check to determine if the library assignment is correct in the applicable JCL and rerun the job.
Module:
IDMSSTRT
Severity:
0
Reason:
A connectivity loss event was encountered.
This abend will happen only when the CV is a data sharing member and the ON CONNECTIVITY LOSS ABEND option is in effect.
Module:
RHDCCFSD
Severity:
0
Reason:
A bad RLE chain has been detected in the RHDCRMGR module. An internal logic error has occurred. Contact Technical Support.
Module:
RHDCRMGR
Severity:
0
Reason:
The RHDCDEAD deadlock detector module has abended, and after being restarted the maximum number of times allowed, the system is abended and a dump is produced. This is a system internal error. Contact Technical Support.
Module:
RHDCDEAD
Severity:
0
Reason:
The CA-SYSTEM/ADAPTER is not active. Activate the CA-SYSTEM/ADAPTER and rerun the job.
Module:
RHDCODVS
Severity:
0
Reason:
Executing in a DYNAMIC partition without the ESA option enabled is prohibited.
Module:
RHDCODVS
Severity:
0
Reason:
An attempt to set the CA IDMS z/VSE SVC hook has failed. Ensure that the IDMSVCTB is available and that the SVC number specified by the SYSGEN has been installed.
Module:
RHDCODVS
Severity:
0
Reason:
An attempt to locate the IDMSDSVC module has failed. An internal logic error has occurred. Contact Technical Support.
Module:
RHDCODVS
Severity:
0
Reason:
An SVC function call returned a nonzero return code. An internal logic error has occurred. Contact Technical Support.
Module:
RHDCODVS
Severity:
0
Reason:
An attempt to load IDMSIDMS has failed. Possible causes could be the program was not found, or there was not enough storage to load the module.
Module:
IDMSSTUB
Severity:
0
Reason:
The ESA option is not installed, which is required for XA support. But CA IDMS was called in A mode 31. Relink the calling program to run in A mode 24. Or install the ESA option.
Module:
RHDCODVS
Severity:
0
Reason:
WTO function issued a WRITEQ TD and it failed. Possibly bad DFHDCT destination id or RECSIZE too small.
Module:
IDMSOCIC
Severity:
0
Reason:
Parameter validation error
This abend is preceded by either the DC040103 or DC040104 error messages. Both of these messages indicate that the lock manager was unable to complete the allocation of its control blocks due to questionable parameters passed to it by RHDCSTRT. Contact Technical Support.
Module:
IDMSLMGR
Severity:
0
Reason:
Parameter validation error
This abend is preceded by the message DC040106 and is the result of an incorrect scaling option being passed from RHDCSTRT. Contact Technical Support.
Module:
IDMSLMGR
Severity:
0
Reason:
LKM validation error
This abend is the result of the lock manager being unable to validate the LKM control block. Contact Technical Support.
Module:
IDMSLMGR
Severity:
0
Reason:
Control block validation error
This abend is the result of the lock manager being unable to validate one or more of its control blocks. Contact Technical Support.
Module:
IDMSLMGR
Severity:
0
Reason:
Internal system error
An unrecoverable error was encountered by the lock manager during the course of processing. If encountered during system startup it will be preceded by message DC040105 which describes the specific error that was encountered. After startup this abend will be preceded by message DC040200. Contact Technical Support.
Module:
IDMSLMGR
Severity:
0
Reason:
Insufficient storage during error processing
During the processing of an error the lock manager was unable to acquire enough storage to issue a message describing the error. Contact Technical Support.
Module:
IDMSLMGR
Severity:
0
Reason:
Local variable area validation error
During the processing of an error the lock manager was unable to validate its local variable area after issuing a #SNAP request. Contact Technical Support.
Module:
IDMSLMGR
Severity:
0
Reason:
Task cancelled due to an outstanding recovery lock
The cancelled task tried to access a resource that was currently locked by a failed CA IDMS system and the system definition or the user exit indicated that the task should be cancelled.
Either the failed CA IDMS system has not yet been restarted or its recovery is incomplete.
Action:
Restart all failed CA IDMS systems or take the necessary steps to recover the database and retry the cancelled task.
Module:
IDMSLMGR
Severity:
0
Reason:
An unexpected internal error was detected in the IDMSBLDR module. This abend is preceded with a message on the console which gives specific information on the nature of the error detected.
Module:
IDMSBLDR
Severity:
0
Reason:
An invalid DBNAME TABLE load module was detected.
Module:
IDMSBLDR
Severity:
0
Reason:
Not enough storage available to satisfy request.
Module:
IDMSBLDR
Severity:
0
Reason:
Failed trying to load a required module.
Module:
IDMSBLDR
Severity:
0
Reason:
An invalid DMCL load module was detected.
Module:
IDMSBLDR
Severity:
0
Reason:
An unexpected internal error was detected in the IDMSBLDR module while trying to convert a release 10.x subschema structure to a Release 12.0 subschema structure.
Module:
IDMSBLDR
Severity:
0
Reason:
A BIND has been issued for a subschema using a DBNAME defined in the DBNAME table that includes SEGMENTS which have different PAGE GROUPS. The subschema contains AREAS which would map to the different PAGE GROUPS, which is not supported.
Module:
IDMSBLDR
Severity:
0
Reason:
An unexpected internal error was detected in the IDMSLRBK module. This abend is preceded with a message on the console which gives specific information on the nature of the error detected.
Module:
IDMSLRBK
Severity:
0
Reason:
An unexpected internal error was detected in the IDMSCONN module. This abend is preceded with a message on the console which gives specific information on the nature of the error detected.
Module:
IDMSCONN
Severity:
0
Reason:
Not enough storage available to satisfy request.
Module:
IDMSCONN
Severity:
0
Reason:
Failed trying to load a required module.
Module:
IDMSCONN
Severity:
0
Reason:
An invalid SYSIDMS parameter was specified. The invalid parameter is displayed on the operator console.
Module:
IDMSCONN
Severity:
0
Reason:
An unexpected internal error was detected in the IDMSTRAK module. This abend is preceded with a message on the console which gives specific information on the nature of the error detected.
Module:
IDMSTRAK
Severity:
0
Reason:
CV Change Tracking disabled, manual intervention required. This abend is preceded with a message on the console which gives specific details of the action to be taken.
Module:
IDMSTRAK
Severity:
0
Reason:
Not enough storage available to satisfy request.
Module:
IDMSTRAK
Severity:
0
Reason:
An unexpected internal error was detected in the IDMSLOAD module. This abend is preceded with a message on the console which gives specific information on the nature of the error detected.
Module:
IDMSLOAD
Severity:
0
Reason:
Not enough storage available to satisfy request.
Module:
IDMSLOAD
Severity:
0
Reason:
An IDMSBCF utility statement conflicts with a previous utility statement issued within the same job step.
Module:
IDMSLOAD
Severity:
0
Reason:
A LOAD, BUILD, or VALIDATE statement was issued against an SQL TABLE which is defined in a NATIVE VSAM file, which is not supported.
Module:
IDMSLOAD
Severity:
0
Reason:
An unexpected error was returned by the IDMSQSRT module while doing an internal SORT.
Module:
IDMSLOAD
Severity:
0
Reason:
A fatal database error was detected. This abend is preceded by a message on SYSLST which gives the details on the IDMS-STATUS at the time of the database error.
Module:
IDMSLOAD
Severity:
0
Reason:
An unexpected internal error was detected in the IDMSTUNE module. This abend is preceded with a message on the console which gives specific information on the nature of the error detected.
Module:
IDMSTUNE
Severity:
0
Reason:
Not enough storage available to satisfy request.
Module:
IDMSTUNE
Severity:
0
Reason:
An Internal Error has occurred in an IDD architecture product (that is, IDD, schema, subschema, SYSGEN, and so on).
A dump accompanies the abend. Please notify Technical Support.
Module:
IDDSMAIN, IDDSMEDI, IDDSMELM, IDDSMGEN, IDDSMIDD, IDDSMISC, IDDSMREP, IDDSMTBL, IDDSMTGN, IDDSTGEN, IDDSTIID
Severity:
0
Reason:
An internal error has occurred in an IDD architecture product (that is: IDD, schema, subschema, SYSGEN, and so on) due to insufficient storage to load a module and/or acquire internal work space.
Increase the storage available for the job or task and rerun.
A dump accompanies the abend.
Module:
IDDSFEDC, IDDSFEBT, IDDSFEII, IDDSMIID, IDDSMISX, IDDSXIID
Severity:
0
Reason:
An internal error has occurred in an IDD architecture product (that is: IDD, schema, subschema, SYSGEN, and so on). A request to load a required module has failed.
A dump accompanies the abend. Please notify Technical Support.
Module:
IDDSFEDC, IDDSFEBT, IDDSFEII, IDDSMAIN
Severity:
0
Reason:
The external ECB list is empty. This is a system internal error.
Module:
IDMSWAIT
Severity:
0
Reason:
A WAIT for a resource in a batch job would cause a DEADLOCK. This is a system internal error.
Module:
IDMSWAIT
Severity:
0
Reason:
An unsupported CA IDMS function was called by a batch job. This is a system internal error.
Module:
IDMSWAIT
Severity:
0
|
Copyright © 2014 CA.
All rights reserved.
|
|