Reason:
An I/O error has occurred during an attempt to load a program, map, subschema, database procedure, or CA ADS dialog.
Module:
RHDCLODR
Severity:
3
Reason:
An attempt to load the named program has failed. Probable causes for this error are as follows:
Module:
RHDCLODR
Severity:
5
Reason:
A load request has failed because its execution would have resulted in a deadlock. The resource involved is the program pool or, if the program is defined as reentrant and a reentrant pool exists, the reentrant pool. If this condition occurs frequently, increase the value specified by the PROGRAM POOL or REENTRANT POOL parameter of the SYSGEN SYSTEM statement.
Module:
RHDCLODR
Severity:
5
Reason:
The named program is larger than the size of the program pool or the reentrant pool, as specified in the SYSGEN by the PROGRAM POOL or REENTRANT POOL parameter of the SYSTEM statement.
Module:
RHDCLODR
Severity:
0
Reason:
The named program has been defined in the SYSGEN with a security class not included in the user's security class list. To obtain authority to access the program, contact the system administrator.
Module:
RHDCLODR
Severity:
5
Reason:
A nonzero status code has been returned to the loader run unit. Consult messages DC076001-DC076006 for the subschema control error information.
Module:
RHDCLODR
Severity:
3
Reason:
An attempt to reload the named program from the data dictionary load area has failed. The LOADHDR record found on the first load is no longer present, and the program was not defined in the SYSGEN with NEWCOPY AUTOMATIC. Manually vary the program to new copy, enable the program, and reinvoke the task.
Module:
RHDCLODR
Severity:
5
Reason:
A debugging error has occurred. Refer to the previous message on the log and terminal to determine the cause of the problem.
Module:
RHDCLODR
Severity:
5
Reason:
This error condition currently can occur only in CA ADS Batch applications. Insufficient memory was available to load the indicated module. The partition size is not large enough and should be increased. This is more likely to occur at z/VSE sites, although it can occur at z/OS sites as well.
Module:
IDMSLLOD (batch loader)
Severity:
3
Reason:
An attempt to load the named program SYSGENned as resident was unsuccessful. Processing will continue.
Check the <return-code> supplied for the reason the load failed.
Module:
RHDCLODR
Severity:
0
Reason:
A failure occurred trying to load a nucleus load module in a CA IDMS batch job. Either the load module could not be found in the load library, or there is not enough storage available to load the module. This message is followed with an abend with abend code DYLD.
Module:
RHDCLODR
Severity:
0
Reason:
The indicated resource has not been defined to the security system. This message is issued for internally secured resources only. Define the resource using IDMSBCF or OCF.
Module:
RHDCSCEN
Severity:
0
Reason:
The user has attempted to access a resource without the required authorizations. This message may be accompanied by additional messages.
This message may not be issued for all security violations, since issuing this message is the responsibility of the caller.
Module:
RHDCSCEN
Severity:
0
Reason:
Either the current security request is invalid, or an internal error has occurred while processing the request. The most likely cause of an invalid request is an incomplete or invalid Security Request Block (SRB). Internal errors most often result from DB errors during catalog access for internal security, or interfacing errors for external security. In this case, message DC021103 will be accompanied by other messages.
Module:
RHDCSCEN
Severity:
0
Reason:
The security system has received an unexpected error status while attempting to access the security catalogs. This message will be accompanied by additional messages providing specific information about the error; including ERROR-AREA, ERROR-RECORD and the ERROR-STATUS returned by DBMS.
Module:
RHDCSCEN
Severity:
0
Reason:
The user is currently signed on to one terminal and is attempting to sign on to another while the system was not defined to allow multiple signon. A given user may be signed on only from one terminal at any time.
Module:
RHDCSCEN
Severity:
0
Reason:
The password supplied to SIGNON does not match the current password, or no password was supplied. This message will be followed by a password prompt from SIGNON.
Module:
RHDCSCEN
Severity:
0
Reason:
This message is issued only in systems genned to allow multiple signon. The user has attempted to change the password while signed on to more than one terminal. Signon password can be changed only if the user is not signed on elsewhere in this system. The new password is ignored. To change your password, be sure you are not signed on to other terminals.
Module:
RHDCSCEN
Severity:
0
Reason:
An attempt has been made to delete a program that was not loaded by the requesting task.
Module:
RHDCLODR
Severity:
5
Reason:
An attempt to delete the named program has failed because the program was not defined in the SYSGEN.
Module:
RHDCLODR
Severity:
5
Reason:
In the process of deleting the named program, the task failed in its attempt to lock the PDE and waiting would have caused a deadlock.
Module:
RHDCLODR
Severity:
5
Reason:
No RLEs, RCEs, or DPEs were available to satisfy a load request. A possible cause is that a program either is looping while acquiring resources or is failing to free resources. Check for an error in program logic. Alternatively, the system may be using more resources than expected. In this case, increase the RLE count, RCE count, or DPE count specified in the SYSTEM statement of the SYSGEN.
Module:
RHDCLODR
Severity:
4
Reason:
A debugging error has occurred. Refer to the previous message on the log and terminal to determine the cause of the problem.
Module:
RHDCLODR
Severity:
5
Reason:
During the startup process of the CA IDMS CV, the CA IDMS Health Check routines invoke the CA Health Checker interface. For each CA IDMS Health Check routine, a parameter list is passed to the CA Health Checker interface for validation before the requested function can proceed.
This does not imply the requested function will be successful when parameter validation completes. To monitor the status of the CA IDMS Health Checks use the CA SYSVIEW Health Checker Menu or the z/OS Health Checker facility command F HZSPROC DISPLAY,CHECK=(CA_IDMS,*).
Reason:
During normal CA IDMS CV shutdown or in abend processing of the CA IDMS CV, a request is made to terminate the CA IDMS health check routines. The CA Health checker interface is called to remove the CA IDMS health checker routines from the z/OS Health Checker infrastructure.
Reason:
A request to reload CA IDMS health checker support module RHDCHCHK or RHDCHCHR was successful. RHDCHCHK and RHDCHCHR are CA IDMS nucleus modules and require a nucleus reload. For more information about reloading CA IDMS nucleus modules, refer to the DCMT VARY NUCLEUS command in the CA IDMS System Tasks and Operator Commands Guide.
Module:
RHDCHCHK,RHDCOESA
Severity:
0
Reason:
The CA Health Checker is not installed or unavailable in the system. The CA Health Checker is a component of the CA Common Services product. Contact your systems programmer for assistance.
Module:
RHDCHCHK
Severity:
0
Reason:
The main control block for CA Health Checker is invalid and may not be populated. Check for simultaneous CV startup and CA Health Checker initialization causing a timing error. Start and initialize the CA Health Checker before CA IDMS CV startup.
Module:
RHDCHCHK
Severity:
0
Reason:
The CA Health Checker was unable to add the CA IDMS Health Check routine to the z/OS Health Checker infrastructure. See the accompanying CA Health Checker error message CAHCxxxE or IBM z/OS Health Checker error message HZSxxxxx for more details.
Module:
RHDCHCHK
Severity:
0
Reason:
The CA Health Checker was unable to add some CA IDMS Health Check routines to the z/OS Health Checker infrastructure. See the accompanying CA Health Checker error message CAHCxxxE or IBM z/OS Health Checker error message HZSxxxxx for more details.
Module:
RHDCHCHK
Severity:
0
Reason:
An initialization request to the initialization service of the CA Health Checker has failed. The z/OS level must be 1.8 or higher or the CA Health Checker modules CASHCCMN and/or CASHCSRV are not available. See the accompanying CA Health Checker error message CAHCxxxE or IBM z/OS Health Checker error message HZSxxxxx for more details.
Module:
RHDCHCHK
Severity:
0
Reason:
An invalid internal function call was made to the CA Health Checker interface by the CA IDMS health checker support modules. Contact CA IDMS support for assistance.
Module:
RHDCHCHK
Severity:
0
Reason:
The CA Health Checker interface is disabled and the CA IDMS health check routines are unavailable. Accompanied by error messages:
or
or
Contact your systems programmer for assistance.
Module:
RHDCHCHK
Severity:
0
Reason:
An attempt to load the named program has failed. Probable causes of this error are as follows:
Module:
RHDCPCTL
Severity:
5
Reason:
Change the program to pass no more than 4093 parameters.
Module:
RHDCPCTL
Severity:
0
Reason:
A DC RETURN was issued by a COBOL program with a rununit still open. Change the program to issue a FINISH before the DC RETURN.
Module:
RHDCPCTL
Severity:
5
Reason:
The specified task was not able to transfer control to the named program because the program is not known to the system. No PDE exists for the program because the program was neither defined in the SYSGEN nor defined dynamically by means of a DCMT VARY DYNAMIC PROGRAM command.
Module:
RHDCPCTL
Severity:
5
Reason:
The specified task was not able to transfer control to the named program. Either the named program is not in a load library, or a library I/O error has occurred.
Module:
RHDCPCTL
Severity:
5
Reason:
The specified task was not able to transfer control to the named program for one of the following reasons:
Module:
RHDCPCTL
Severity:
5
Reason:
The specified task was not able to transfer control to the named program because the program is disabled. Possible reasons are as follows:
Module:
RHDCPCTL
Severity:
5
Reason:
The specified task is not able to transfer control to the named program. A database I/O error occurred previously, and the program was enabled without being varied to a new copy.
Module:
RHDCPCTL
Severity:
5
Reason:
An attempt has been made to load a resident program marked for a new copy, but the load has failed. Replace the program in the load library and try again.
Module:
RHDCPCTL
Severity:
5
Reason:
The named program is larger than the size of the program pool or the reentrant pool, as specified in the SYSGEN by the PROGRAM POOL or REENTRANT POOL parameter of the SYSTEM statement.
Module:
RHDCPCTL
Severity:
5
Reason:
The LINK/XCTL to the named program failed because the program could not be loaded. The reason for the load failure is unknown because the return code is not recognizable.
Module:
RHDCPCTL
Severity:
3
Reason:
A program check has occurred in the named program. Obtain a copy of the dump of the task using the PRINT LOG utility statement. Use the PSW reported to locate the point at which the error occurred. The Abend Control Element in the snap contains the registers at the time of the program check.
Module:
RHDCPCTL
Severity:
0
Reason:
A system internal error has occurred, possibly caused by storage having been overwritten. Contact Technical Support.
Module:
RHDCPCTL
Severity:
0
Reason:
At the time a task abnormally terminated, the system had insufficient storage; therefore, the task could not abend normally. If this condition occurs frequently, increase the size of the storage pool.
Module:
RHDCPCTL
Severity:
0
Reason:
A task defined in the SYSGEN as a preempt startup autotask has failed to terminate successfully. This has prevented completion of the startup process and has resulted in a system abend. Either determine the cause of the abend from the preceding log messages, correct the indicated problems, and restart the system; or run the batch SYSGEN compiler, removing the PREEMPT attribute from the named autotask.
Module:
RHDCPCTL
Severity:
9
Reason:
The named task has been abended by the operating system. Check the appropriate operating system debugging manual for a description of the codes.
Module:
RHDCPCTL
Severity:
0
Reason:
In the process of abending the named task, a second abend for the task has occurred. This message is accompanied by a system abend code of 3970.
Module:
RHDCPCTL
Severity:
0
Reason:
The named task has abended. For more information, see the description of the indicated task or user abend code.
Module:
RHDCPCTL
Severity:
0
Reason:
The named program has been disabled because it exceeded the error threshold specified in the PROGRAM statement in the SYSGEN. Check the program for programming errors.
Module:
RHDCPCTL
Severity:
0
Reason:
This message is issued with message DC027007; the message identifies the task that abended.
Module:
RHDCPCTL
Severity:
0
Reason:
This message is issued with message DC027007; the message identifies the logical terminal associated with the task that abended.
Module:
RHDCPCTL
Severity:
0
Reason:
This message is issued with message DC027007; the message identifies the user associated with the task that abended.
Module:
RHDCCPTL
Severity:
0
Reason:
An operating system abend has been detected. <abend-code> is in the form Sxxx or Uxxx where xxx is the hexadecimal value of the User or System abend code. The current task will be abended and the DC system will attempt to recover and continue processing. Note that a system task may have abended. In this case, the DC system may subsequently abend with a different abend code. The cause of the problem should be determined as soon as possible and the system should be cycled if necessary.
If possible, the registers and PSW at the time of the operating system abend will be preserved in the TCE of the abending task in fields TCESPRGS and TCESPPSW.
The abend occurred under one of the following circumstances:
Module:
RHDCPCTL
Severity:
0
Reason:
Either an I/O error has occurred during a #PUTQUE or, for OPTNS=DIRECT, a permanent I/O error has occurred on the direct printer. If this condition occurs when the options COND=IOER and IOERXIT are specified for the #PRINT macro, this message is not issued, and control is returned to the user program.
Module:
RHDCPRNT
Severity:
3
Reason:
The parameter list passed to the #PRINT macro contains an invalid field. The probable cause is that the value of the RECLEN parameter was negative. If this condition occurs when the options COND=INVP and INVPXIT are specified for the #PRINT macro, this message is not issued, and control is returned to the user program.
Module:
RHDCPRNT
Severity:
3
Reason:
No printer logical terminals have been defined for the system. If this condition occurs when the options COND=NOPR and NOPRXIT are specified for the #PRINT macro, this message is not issued, and control is returned to the user program.
Module:
RHDCPRNT
Severity:
5
Reason:
A print-screen request has been made from a non-3270-type terminal. If this condition occurs when the options COND=INVT and INVTXIT are specified for the #PRINT macro, this message is not issued, and control is returned to the user program.
Module:
RHDCPRNT
Severity:
5
Reason:
Either the specified print destination is invalid or, for OPTNS=DIRECT, the value specified for LTEID or LTEADDR is invalid. If this condition occurs when the options COND=UNDF and UNDFXIT are specified for the #PRINT macro, this message is not issued, and control returns to the user program.
Module:
RHDCPRNT
Severity:
5
Reason:
A terminal I/O error has occurred during a PRINT SCREEN CONTENTS request. If this condition occurs when the options COND=SCRN and SCRNXIT are specified for the #PRINT macro, this message is not issued, and control is returned to the user program.
Module:
RHDCPRNT
Severity:
3
Reason:
The direct printer identified by <lterm-id> or by<lterm-address> is out of service or dead. If this condition occurs when the options COND=OUTS and OUTSXIT are specified for the #PRINT macro, this message is not issued, and control is returned to the user program.
Module:
RHDCPRNT
Severity:
5
Reason:
A DCMT VARY PRINTER CANCEL command has been issued for the indicated direct printer. If this command is issued when the options COND=CANC and CANCXIT are specified for the #PRINT macro, this message is not issued, and control is returned to the user program.
Module:
RHDCPRNT
Severity:
5
Reason:
A DCMT VARY PRINTER REQUEUE command has been issued for the indicated direct printer. If this command is issued when the options COND=REQU and REQUXIT are specified for the #PRINT macro, this message is not issued, and control is returned to the user program.
Module:
RHDCPRNT
Severity:
5
Reason:
A task that was writing a report directly to a printer either has issued a ROLLBACK TASK request or has abended. The report should probably be disregarded. The message text is hard-coded in the module; no #WTL is issued.
Module:
RHDCPRNT
Severity:
0
Reason:
A rollback of changes made by an SQL request was required, but a table procedure invoked during the request wrote lines to a direct report. Since there is no means to rollback changes made to the report, the task is abended.
Module:
RHDCPRNT
Severity:
5
Reason:
Probable causes for this message are as follows:
Module:
RHDCPCBO
Severity:
0
Reason:
Insufficient storage is available for the system to acquire working storage for a COBOL program, and waiting for storage would cause a deadlock. If this condition occurs frequently, increase the size of the storage pool.
Module:
RHDCPCBO
Severity:
1
Reason:
A system internal error has occurred. Contact Technical Support.
Module:
RHDCPCBO
Severity:
3
Reason:
A program compiled with VS COBOL II has a control block structure different from that expected by DC when setting up the program to run quasi-reentrant. Contact Technical Support. To bypass the problem, run the program non-reentrant or recompile it with RES/RENT compiler options.
Module:
RHDCPCBO
Severity:
0
|
Copyright © 2014 CA.
All rights reserved.
|
|