Reason:
The initialization procedure is about to open the TILF file in order to activate the transaction logging facility.
Module:
RHDCMSTR
Severity:
0
Reason:
The initialization procedure is activating task 1(RHDCDBRC) in order to ready the database.
Module:
RHDCMSTR
Severity:
0
Reason:
The initialization procedure is activating the system run unit facility.
Module:
RHDCMSTR
Severity:
0
Reason:
The initialization procedure is activating the line driver for the named line.
Module:
RHDCMSTR
Severity:
0
Reason:
The initialization procedure has been completed successfully.
Module:
RHDCMSTR
Severity:
0
Reason:
The tasks defined in the SYSGEN as startup autotasks are being attached by DC.
Module:
RHDCMSTR
Severity:
0
Reason:
DC was unable to attach the named autotask. Check the return code against those for the #ATTACH macro in order to determine the cause of the failure.
Module:
RHDCMSTR
Severity:
0
Reason:
The tasks defined in the SYSGEN as shutdown autotasks are being attached by DC in response to a SHUTDOWN request.
Module:
RHDCMSTR
Severity:
0
Reason:
The system has failed to attach a task that was defined in the SYSGEN as a preempt startup autotask, resulting in a system abend. Check the return code supplied with the message for the cause of the failure, and either remedy the problem or run the batch SYSGEN compiler to remove the PREEMPT attribute from the autotask.
Module:
RHDCMSTR
Severity:
8
Reason:
The attach for the task that sweeps the data dictionary queue area has failed with the specified return code. Refer to the indicated return code for more information and attempt to execute the task from a terminal.
Module:
RHDCMSTR
Severity:
0
Reason:
DC is attaching the task that sweeps the data dictionary queue area. If this task terminates abnormally, the queue area may contain expired queues. This condition can be corrected by executing the queue cleanup task from a terminal.
Module:
RHDCMSTR
Severity:
0
Reason:
The attach for the task that sweeps data dictionary load areas and erases logically-deleted load modules has failed. Refer to the indicated return code for more information and attempt to execute the task from a terminal.
Module:
RHDCMSTR
Severity:
0
Reason:
DC attached the task that sweeps the primary and secondary data dictionary load areas and erases logically-deleted load modules. If this task terminates abnormally, the load areas may contain logically deleted load modules. You can correct this condition by executing the load area cleanup task from a terminal.
Module:
RHDCMSTR
Severity:
0
Reason:
The initialization procedure is starting the named service driver.
Module:
RHDCMSTR
Severity:
0
Reason:
The master task was attempting to build an index for a system table. The attempt failed. This is an internal system failure.
Severity:
8
Module:
RHDCMSTR
Reason:
The Security system initialization has been started by the DC initialization processing.
Module:
RHDCMSTR
Severity:
0
Reason:
The security system initialization completed.
Module:
RHDCMSTR
Severity:
0
Reason:
The named task has issued a storage request that specifies an invalid value.
Module:
RHDCSTGP
Severity:
3
Reason:
No RCEs were available to satisfy a storage 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 RCE count specified in the SYSTEM statement of the SYSGEN.
Module:
RHDCSTGP
Severity:
3
Reason:
A system internal error has occurred during an attempt to acquire storage in a storage pool page. Contact Technical Support.
Module:
RHDCSTGP
Severity:
4
Reason:
A system internal error has occurred, possibly caused by storage having been overwritten.
Module:
RHDCSTGP
Severity:
3
Reason:
A task is attempting to wait for storage held by another task, but waiting would cause a deadlock. The value specified in the SYSGEN STORAGE POOL parameter may be too small to accommodate processing demands. If this condition occurs repeatedly, increase the size of the storage pool.
Module:
RHDCSTGP
Severity:
3
Reason:
A 24-bit task requested storage using a storage identifier for storage that was initially allocated for a 31-bit task from an XA storage pool. The requested storage cannot be addressed by this task unless the AMODE for the task is changed to 31. The program can specify the XAST condition to intercept the error and switch to 31-bit mode to access the storage.
Module:
RHDCSTGP
Severity:
3
Reason:
One of two conditions has occurred in the indicated storage pool. Either condition may indicate that the storage pool needs to be increased or that the MAXIMUM TASK value should be lowered. An SOS condition can become severe enough to hang the system. Because these conditions can arise with extreme frequency, the message is not written if it has already been written for the same condition in the same pool within the previous 60 seconds.
Condition 0:
A storage request has just been satisfied, but the total amount of free storage remaining in the pool is less than the storage cushion for that pool.
Condition 1:
A storage request has been issued. The DC system determined that this pool is eligible to satisfy the request, but that not enough contiguous storage is available in the pool to satisfy the request. Depending on the options specified on the GET STORAGE request and availability of storage in other eligible pools, one of four actions may have been taken:
The message includes the size, task code and current program for the request which resulted in the SOS condition. This information may be useful in determining why the SOS condition is occurring. Note, however, that the particular request which resulted in the condition is not necessarily an indicator of the real cause of the problem. Another task or tasks may have made large requests or multiple requests which brought the system close to the SOS condition, which was actually reached by the reported request.
Module:
RHDCSTGP
Severity:
0
Reason:
The address specified on a free storage request is invalid. Either the task does not own the specified storage, or the address specified is zeros. A user logic error or a system internal error has occurred.
Module:
RHDCSTGP
Severity:
3
Reason:
A system internal error has occurred during an attempt to free storage in a storage pool page. Contact Technical Support.
Module:
RHDCSTGP
Severity:
4
Reason:
Either a system internal error has occurred, or a user program has overwritten the control words that precede and follow the piece of storage being freed. The snap dump that accompanies this message gives the contents of the violated and freed storage, plus an additional 128 (X'80') bytes at each end.
Module:
RHDCSTGP
Severity:
3
Reason:
An error has occurred during an attempt to write relocatable storage to scratch upon task termination. The storage is still flagged as relocatable but will not be written to scratch until after the next task termination on the same logical terminal.
Module:
RHDCSTGP
Severity:
0
Reason:
The storage identifier specified on a free storage request is invalid. No storage identifier with the value specified can be found. Check that the storage identifier is specified correctly.
Module:
RHDCSTGP
Severity:
3
Reason:
A user program is doing a FREESTG of a piece of storage (i.e., storage-frame) belonging to a multi-allocation storage-block, but most probably one or more storage-frames together with the control words that precede and follow each storage-frame, have been accidentally moved to another location within the global storage block.
For example, frame A with length X'200', frame B with length X'80' and frame C with length X'100', followed by a MOVE from B to A+X'100' over an invalid length of X'100'.
The control words (i.e., 8 bytes = address of the RCE + length of the storage-frame) preceding the address of the storage-frame that is passed from the user program, are checked (i.e., address of the RCE should match and the length of the storage-frame should be positive, a multiple of 128 and within the scope of the total length of the storage-block).
Only if this check fails, the complete multi-allocation storage-block is walked, starting with the address of the first frame provided in the RCE (i.e., RCERADDR) and for each storage-frame, the control words that precede (i.e., A(RCE) + Length) and follow (i.e., A(RCE)) it, are checked. If one of the above checks fails, this message will be issued together with a SNAP dump giving the contents of the complete multi-allocation storage-block.
Reason:
Text of message issued by VS COBOL II run time system. Consult VS COBOL II documentation for information about the message.
Module:
RHDCSCRN
Severity:
0
Reason:
The SVC defined in SYSGEN is not installed on the system. This message is used only on z/VSE operating systems. Check the CA System Adapter initialization messages at IPL for possible errors installing the SVC.
Module:
RHDCODVS
Severity:
0
Reason:
A 64-bit storage manipulation request (IARV64) failed. <function> (<function-dependent-info>) can be:
<return-code> and <reason-code> are R15 and R0 from IARV64. For more information on the IARV64 macro and its return codes, refer to IBM z/OS Assembler Services or IBM z/VSE System Macro Reference documentation.
The amount of 64-bit storage available is controlled by the operating system MEMLIMIT value. For more information on MEMLIMIT, refer to IBM z/OS JCL Reference or IBM z/VSE System Control Statements.
Module:
RHDCOMVS
Severity:
0
Reason:
An invalid freeform CV startup parm --> <parm-text> was detected. The parameter in error is displayed. Correct the invalid parameter and resubmit the CA IDMS Central Version startup job.
Module:
RHDCOPTS
Severity:
0
Reason:
An invalid positional CV startup parameter was detected. The parameter in error is displayed below. Correct the invalid parameter and resubmit the CA IDMS Central Version startup job.
Module:
RHDCOMVS
Severity:
0
Reason:
Operating system level HBB7709 or above is required. Consult your systems programmer and retry after the environment has been upgraded.
Module:
RHDCOMVS
Severity:
0
Reason:
Predictive mode has been forced because the operating system or hardware does not contain support for zIIP processors. Consult your systems programmer and retry after the environment has been upgraded.
Module:
RHDCOMVS
Severity:
0
Reason:
The specified number of zIIP processors have been detected on your hardware. By default, CA IDMS will not attempt to use them. CA IDMS can usually achieve various operating efficiencies by employing these processors. You should consider permitting CA IDMS to use them.
Module:
RHDCOMVS
Severity:
0
Reason:
The specified CA IDMS nucleus module was loaded from a pds that was not APF authorized. This module must be loaded from an APF authorized library.
Either APF authorize the specified library or move the module to an APF authorized library.
Module:
RHDCOMVS
Severity:
0
Reason:
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
CA IDMS optionally exploits zIIP processors on the z9 series and above for the z/OS operating system. This feature permits offloading computing cycles to the zIIP processors, thereby increasing overall CPU throughput while decreasing operational costs.
Reason:
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:
The use of XTIOT for dynamic allocation of CA IDMS database files for Central Version processing is controlled by the setting of NON_VSAM_XTIOT statement in the DEVSUPxx member of SYS1.PARMLIB. In z/OS 1.12, a setting of NON_VSAM_XTIOT=NO (the default) will disable the use of XTIOT for dynamic allocation and normal TIOT will be used for dynamic allocation.
Module:
RHDCOMVS
Severity:
0
Reason:
The use of XTIOT for dynamic allocation of CA IDMS database files for Central Version processing is controlled by the setting of NON_VSAM_XTIOT statement in the DEVSUPxx member of SYS1.PARMLIB. In z/OS 1.12, a setting of NON_VSAM_XTIOT=YES will enable the use of XTIOT for dynamic allocation.
Module:
RHDCOMVS
Severity:
0
Reason:
An internal error was encountered. The program that issued the message is listed along with an error-code that helps identify the location in the program. <misc-info> can be any additional information that the program wishes to display. Normally the job is aborted at this time.
This is not a normal error condition.
Contact Technical Support.
Module:
RHDCODVS
Severity:
0
Reason:
This is an informational message saving IDMS/CV startup is starting to attach the CHECKUSER subtasks.
Module:
RHDCODVS
Severity:
0
Reason:
This is an informational message that may be useful in debugging a SUBMIT function call. It is intended for knowledgeable users or technical support.
A VSE XPCC call was made and ended with a non-zero return code. Information from the XPCCB control block is displayed. These codes are documented in the VSE macro MAPXPCCB.
Module:
RHDCODVS
Severity:
0
Reason:
This is an informational message that may be useful in debugging a SUBMIT function call. It is intended for knowledgeable users or technical support.
A VSE XPCC call was made to communicate with the VSE POWER application. The XPCC call was successful, but POWER found a problem and returned information in the 8-byte receive data field.
The 8-byte send data and 8-byte receive data fields are displayed here in hex. These fields are documented in the VSE PWRSPL macro.
Module:
RHDCODVS
Severity:
0
Reason:
This message is displayed when a MSG XX command is entered and CV is not waiting for it. CV may be processing a previous operator message. Wait a moment and try again.
Module:
RHDCODVS
Severity:
0
Reason:
This message is displayed when a MSG XX command is entered before CV startup is ready. Wait for CV startup to complete and retry the MSG command.
Module:
RHDCODVS
Severity:
0
Reason:
A logical I/O error was returned from CACNPHY0 on a request for EXCP I/O.
This message is used only on z/VSE operating systems. The <xx> in the message is the value returned in R15 from CACNPHY0. The <yy> in the message is the actual reason code for the logical I/O error. The <RBN> in the message is the block number relative to zero that was being read or written.
Module:
RHDCODOC
Severity:
3
Reason:
An error was detected while processing an I/O related function. The function-name, an error-code, and the DDname related to the request are displayed. Optionally, additional information related to a particular request may also be displayed. The function-name is an eight-character description of the internal function being done or called to support an I/O request. The Error-code is a unique value assigned in the I/O module to associate the error with a specific piece of code. The following is a partial list, but the module itself must be checked for the most current meanings.
Error-Code Description 001 LABEL function error 002 DTFSD GETSTG error 003 Open failed 004 Allocate CACB failed 005 Allocate IOW failed 006 Free IOW failed 007 Free CACB failed 008 **No longer used** 009 GETVCE macro error 010 Blksize will not fit on track 011 **No longer used** 012 XIOB area allocation failed 013 I/O error 014 RDJFCB #GETSTG failed 015 RDJFCB failed 016 XDCB: invalid function 017 **No longer used** 018 **No longer used** 019 CLOSE: XDCB already closed 020 GETXDCB: XIOB #GETSTG failed 021 I/O: XIOB #GETSTG failed 022 OPEN: TRKCALC failed 023 OPEN: 255 blocks on track 024 OPEN: XDCB not passed 025 I/O: Plist not an XDECB 026 I/O: No XDCB provided 027 I/O: Invalid XDECB function 028 I/O: Read against output file 029 I/O: Write against input file 030 I/O: RBN outside file 031 CHECK: No XIOB passed 032 CHECK: No ECB passed 033 I/O: Record not found 034 I/O: Uncorrectable I/O error 035 I/O: Correctable I/O error 036 I/O: XDCB not Open 037 OPEN: Invalid Parmlist 038 OPEN: IOBUFF Getstg error 039 ALLOC: File is open 040 ALLOC: WORK GETSTG failed 041 ALLOC: No DSN or DDN supplied 042 ALLOC: DYNALLOC error 043 GETXIOB: XIOB #GETSTG Failed. 044 GETXIOB: IOW #GETSTG Failed. 045 OPENXCP: VIO not supported
Module:
RHDCODVS
Severity:
3
|
Copyright © 2014 CA.
All rights reserved.
|
|