Reason:
A lock manager start up message estimating how much storage will be needed.
Module:
IDMSLKMC
Severity:
0
Reason:
A lock manager start up message telling how much storage will be used.
Module:
IDMSLKMC
Severity:
0
Reason:
A lock manager start up message indicating that insufficient storage was available for the lock manager tables.
Module:
IDMSLKMC
Severity:
0
Reason:
A lock manager start up message. Contact Technical Support.
Module:
IDMSLKMC
Severity:
0
Reason:
A lock manager start up error message. Contact Technical Support.
Module:
IDMSLKMC
Severity:
0
Reason:
A lock manager start up error message. Contact Technical Support.
Module:
IDMSLKMC
Severity:
0
Reason:
A lock manager module has detected an error. Contact Technical Support.
Module:
IDMSLMGR
Severity:
0
Reason:
Another member of this CA IDMS system's data sharing group has failed. This member has acknowledged the failure so that the CA IDMS system can now be restarted. Restart the failed member as soon as possible.
Module:
IDMSLMGR (LKXT)
Severity:
0
Reason:
Another member of this CA IDMS system's data sharing group has failed. In response, recovery locks have been acquired to prevent access to the resources that need to be recovered. Restart the failed member as soon as possible.
Module:
IDMSLMGR (LKXT)
Severity:
0
Reason:
Another member of this CA IDMS system's data sharing group has failed and has been successfully restarted. In response, this CA IDMS system has released the recovery locks it was holding on behalf of the failed member.
Module:
IDMSLMGR (LKXT)
Severity:
0
Reason:
An error occurred issuing an IXLLOCK request. The return and reason codes from the IXLLOCK request are displayed as is the resource id on which the request was issued. The task requesting the lock is abended. Refer to the appropriate IBM manuals to determine the cause of the error and take appropriate action.
Module:
IDMSLMGR (LKXE)
Severity:
5
Reason:
A system internal error has occurred, possibly caused by storage having been overwritten.
Module:
RHDCTSKI
Severity:
1
Reason:
Check to see whether any programs are using too much storage, and fix any that are. Otherwise, it may be necessary to specify a bigger storage pool size at system generation time. The entry point is TSKIEP1.
Module:
RHDCTSKI
Severity:
0
Reason:
The named service driver is being restarted after a failure.
Module:
RHDCTSKI
Severity:
0
Reason:
The named ERUS task is not in service. The ERUS cannot be processed.
Module:
RHDCTSKI
Severity:
0
CA IDMS scratch performance is optimal. For more information about health checks related to CA IDMS, see the CA IDMS System Operations Guide.
Module:
RHDCHCHK
Severity:
0
Reason:
A scratch request has failed because it could not obtain storage for a new Scratch Index Area (SIA). If this error occurs frequently, determine which resources are using storage ineffectively, or increase the size of the storage pool.
Module:
RHDCSCRM
Severity:
3
Reason:
A scratch request has failed because it could not obtain an RCE or RLE. 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 RCE or RLE count specified in the SYSTEM statement of the SYSGEN.
Module:
RHDCSCRM
Severity:
3
The system configuration of the CA IDMS system <node-name> is producing less than optimal performance. Using the scratch in memory option is a CA IDMS best practice. CA IDMS utilizes a temporary working storage area referred to as the scratch area. In severely storage constrained environments, this area can be supported on DASD through standard file I/O. The performance of the CA IDMS system can be significantly improved by enabling this scratch area for support in main storage and optionally permitting dynamic extensions to provide for the self tuning of this storage use.
This message is produced through the IBM Health Checker facility. For more information about health checks related to CA IDMS, see the CA IDMS System Operations Guide.
Module:
RHDCHCHK
Severity:
0
Reason:
Either a user program has specified an invalid parameter list for a scratch request, or a system internal error has occurred, possibly caused by storage having been overwritten. Check the parameter list on the scratch request.
If this message is issued at startup of PMIM, the problem could be that the Scratch page size is not large enough. PMIM writes interval blocks for every area and must be able to write the entire interval in 255 or less pages. If there are a lot of areas, this message may occur and PMIM will terminate. You can reduce scratch needed by coding DBKMAX=0 on the PMOPT macro.
Module:
RHDCSCRM
Severity:
3
Reason:
An attempt has been made to access a scratch area that does not exist. Probable causes of this error are as follows:
Module:
RHDCSCRM
Severity:
3
Reason:
A system internal error has occurred, possibly caused by storage having been overwritten.
Module:
RHDCSCRM
Severity:
3
Reason:
Open of the current scratch area failed. <reason> contains more detailed information:
Module:
RHDCSCRM
Severity:
5
Reason:
An I/O error has occurred during a write operation on the current scratch area, DDLDCSCR (if running CV or a batch job with SYSIDMS parm DC SCRATCH=ON) or DDLOCSCR (if running a batch job without the SYSIDMS parm DC SCRATCH=ON). Run the FORMAT utility statement of the corresponding scratch area and restart the system or batch program.
Module:
RHDCSCRM
Severity:
3
Reason:
An I/O error has occurred during a read operation on the current scratch area, DDLDCSCR (if running CV or a batch job with SYSIDMS parm DC SCRATCH=ON) or DDLOCSCR (if running a batch job without the SYSIDMS parm DC SCRATCH=ON). Run the FORMAT utility statement for the corresponding scratch area and restart the system of batch program.
Module:
RHDCSCRM
Severity:
3
Reason:
The current scratch area, DDLDCSCR (if running CV or batch job with SYSIDMS parm DC SCRATCH=ON) or DDLOCSCR (if running a batch job without the SYSIDMS parm DC SCRATCH=ON) is full. The probable cause is that an insufficient number of pages were assigned to the corresponding scratch area. Increase its number of pages by altering the parameters for scratch-in-storage or by changing the DMCL.
Module:
RHDCSCRM
Severity:
3
Reason:
The current scratch area, DDLDCSCR (if running CV or a batch job with SYSIDMS parm DC SCRATCH=ON) or DDLOCSCR (if running a batch job without the SYSIDMS parm DC SCRATCH=ON) has been defined to span two or more physical files. Only the first physical file will be used for scratch records. The scratch area should be defined within a single physical file.
Module:
RHDCSCRM
Severity:
0
Reason:
The specified dictionary name contains more than eight characters. Reexecute the task, specifying a valid dictionary name.
Module:
RHDCSDEL
Severity:
0
Reason:
No user definitions in the user catalog were found to have been logically deleted. When this condition is encountered no examination of individual dictionary areas for associated resource definitions is required.
Module:
RHDCSDEL
Severity:
0
Reason:
After issuing a DML verb an unexpected status code was returned from the database manager. Refer to that status code to determine the nature of the error. If necessary consult the system administrator.
Module:
RHDCSDEL
Severity:
0
Reason:
The specified dictionary name is invalid or has no corresponding DDLDML or DDLCAT area. Specify the correct dictionary name as defined by the DB name table.
Module:
RHDCSDEL
Severity:
0
Reason:
This is a confirmation that requires no action. This message indicates that the number of resource authorizations for logically deleted users in the user catalog have been erased from the indicated dictionary area.
Module:
RHDCSDEL
Severity:
0
Reason:
An 0966 error status code was encountered during an attempt to ready the indicated area name. Notify the system administrator.
Module:
RHDCSDEL
Severity:
0
Reason:
When running as a startup autotask the scan of the DMCL for DDLDML and DDLCAT areas has been terminated because an illogical area name has been encountered. Contact the system administrator.
Module:
RHDCSDEL
Severity:
0
Reason:
This is a confirmation message that requires no action. This message indicates that the number of resource group authorizations, for logically-deleted users in the user catalog, have been erased from the indicated dictionary area.
Module:
RHDCSDEL
Severity:
0
|
Copyright © 2014 CA.
All rights reserved.
|
|