|
|
|
The following messages are produced by the CAIENF/USS (UNIX System Services) Common Service.
Messages of the form CARRnnnD are debugging messages that should generally not occur. For any such message, examine messages just prior and subsequent and collect relevant information. If the issues cannot be resolved provide the documentation to CA Support.
Reason:
CAIENF/USS is being started.
Action:
No action is required.
Reason:
CAIENF/USS has run the initialization program and has returned with a return code RC=@@@@.
Action:
No action is required.
Reason:
A debugging message showing the memory address of a CAIENF/USS data structure.
Action:
No action is required. This message is informational only.
Reason:
A debugging message showing the PC number assigned to CAIENF/USS.
Action:
No action is required. This message is informational only.
Reason:
A debugging message showing the memory address where CAIENF/USS has loaded a module.
Action:
No action is required. This message is informational only.
Reason:
A debugging message showing that CAIENF/USS is ready to free memory no longer needed after reinitialization.
Action:
No action is required. This message is informational only.
Reason:
A debugging message showing where CAIENF/USS has allocated its two primary cell pools.
Action:
No action is required. This message is informational only.
Reason:
The CAIENF/USS initialization program has detected the OMVS kernel is not active. It will retry until it is active.
Action:
No action is required.
Reason:
An internal CAIENF/USS debugging message.
Action:
No action is required. This message is informational only.
Reason:
An error checking the userid used to start CAIENF.
Action:
Check that the OMVS segment is defined correctly.
Reason:
An error has occurred during CAIENF/USS initialization. The message provides the name of the system service invoked, as well as the return and reason codes that resulted.
Action:
Correct the error and reinitialize CAIENF.
Reason:
The CAIENF/USS initialization module has detected an OS level lower than the minimum required.
Action:
The minimum operating system level for CAIENF/USS is z/OS V1R4.
Reason:
The CAIENF/USS initialization module has detected changes to the CAIENF/USS product that require an IPL for implementation.
Action:
CAIENF/USS Initialization fails. An IPL must be performed to implement changes.
Reason:
The CAIENF/USS initialization program has detected an error connecting to the OMVS Kernel.
Action:
Check the OMVS segment is defined correctly. For assistance, contact CA Support at http://ca.com/support.
Reason:
CAENF/USS was attempting to rebuild its Kernel Info structure and an error occurred while invoking an OMVS service routine.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
CAENF/USS was attempting to install one of its intercept routines when an error occurred.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The CAIENF/USS initialization module has detected an OS level lower than the minimum required.
Action:
The minimum operating system level for CAIENF/USS is z/OS V1R4.
Reason:
The COFVLFxx member has not been updated to create a CAIENF/USS cache entry.
Action:
It is recommended that the cache entry be added as documented in the Installation Guide. The process will continue running.
Reason:
The user ID assigned to the ENF procedure does not have UID 0 or access to BPX.SUPERUSER.
Action:
Update the user ID assigned to the ENF procedure to be UID 0 or have access to BPX.SUPERUSER.
Reason:
If tracing has been enabled, this is an information message to indicate ENF/USS is accessing certain OMVS Kernel information. If OMVS is not active, code will wait for OMVS to initialize.
Action:
No action is required.
Reason:
If tracing has been enabled, this is an information message to indicate ENF/USS is either initializing or reinitializing internal representations of OMVS Kernel resources.
Action:
No action is required.
Reason:
If tracing has been enabled, this is an information message to indicate ENF/USS is about to issue the sysconf() function for code “xxxxxxxx”.
Action:
No action is required.
Reason:
If tracing has been enabled, this is an information message to indicate ENF/USS is about to issue the getrlimit() function for code “xxxxxxxx”.
Action:
No action is required.
Reason:
If tracing has been enabled, this is an information message to indicate ENF/USS is about to issue the w_getmntent() function.
Action:
No action is required.
Reason:
If tracing has been enabled, this is an informational message to indicate ENF/USS has completed updating its internal representations of OMVS Kernel resources. The first two “xx” characters are the z/OS release; the second two are the OMVS release.
Action:
No action is required.
Reason:
The CAIENF/USS initialization routine displays the number of intercept points that have been for OMVS services.
Action:
No action is required.
Reason:
The CAIENF/USS initialization routine is initializing applications that have been defined to the CAIENF database.
Action:
No action is required.
Reason:
No application DCM modules have been installed into the CAIENF database.
Action:
Install the DCM module for the application utilizing CAIENF/USS.
Reason:
CAIENF/USS has initialized an application, but no event points have been defined for that application.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The number of applications that use CAIENF/USS services has exceeded the maximum of 16.
Action:
Determine what DCMs have been defined to CAIENF.
Reason:
An error occurred during the initialization on a CAIENF/USS application.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
Message returned from CAIENF/USS application initialization failure.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
A CAIENF/USS application has successfully initialized.
Action:
No action is required.
Reason:
An error occurred attempting to locate the CAMASTER address space.
Action:
Contact CA Support for further assistance.
Reason:
An unexpected return code, reason code was returned by CSVDYNEX DELETE trying to delete the USS Exit used by ENF/USS.
Action:
An attempt to define the required exit will proceed. If that fails then ENF/USS initialization will terminate. The return code and reason codes are documented by IBM. If the problem cannot be resolved then contact CA Support for further assistance.
Reason:
An unexpected return code, reason code was returned by CSVDYNEX ADD trying to add the USS Exit used by ENF/USS.
Action:
The return code and reason codes are documented by IBM. If the problem cannot be resolved then contact CA Support for further assistance.
Reason:
CAIENF/USS is being reinitialized.
Action:
No action is required.
Reason:
The CARRPC routine has been loaded and is active.
Action:
No action is required.
Reason:
An error occurred in CARRPC while trying to process an intercept point routine.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
Error in a CAIENF/USS intercept routine.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
An installed CAIENF/USS application has requested that it be deactivated.
Action:
No action is required.
Reason:
A CPOOL GET was unable to acquire the amount of storage requested.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
A CPOOL GET was unable to acquire the amount of storage requested.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
During processing of an intercepted USS function, the required control blocks could not be located.
Action:
Determine if other messages are being issued. If the problem cannot be resolved, contact CA Support for further assistance.
Reason:
After processing an intercepted USS function, an attempt to cleanup one of the control blocks resulted in an error.
Action:
Determine if other messages are being issued. If the problem cannot be resolved, contact CA Support for further assistance.
Reason:
After a new copy of a CAIENF/USS module has been loaded, an attempt to free the previous version of the module has failed.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
An abend has occurred while CAIENF/USS was processing an event and has been captured by the recovery routine.
Action:
See accompanying messages for a more detailed description of the error. Save all dumps and other diagnostics for analysis. For assistance, contact CA Support at http://ca.com/support.
Reason:
An abend has been captured by the CAIENF/USS recovery routine but it has been determined the CAIENF/USS is not currently processing an event.
Action:
Save all dumps and other diagnostics for analysis. For assistance, contact CA Support at http://ca.com/support.
Reason:
An abend has occurred while CAIENF/USS was processing an event. The variable fields indicate registers 0 through 3 at the time of the abend.
Action:
See accompanying messages for a more detailed description of the error. Save all dumps and other diagnostics for analysis. For assistance, contact CA Support at http://ca.com/support.
Reason:
An abend has occurred while CAIENF/USS was processing an event. The variable fields indicate registers 4 through 7 at the time of the abend.
Action:
See accompanying messages for a more detailed description of the error. Save all dumps and other diagnostics for analysis. For assistance, contact CA Support at http://ca.com/support.
Reason:
An abend has occurred while CAIENF/USS was processing an event. The variable fields indicate registers 8 through 11 at the time of the abend.
Action:
See accompanying messages for a more detailed description of the error. Save all dumps and other diagnostics for analysis. For assistance, contact CA Support at http://ca.com/support.
Reason:
An abend has occurred while CAIENF/USS was processing an event. The variable fields indicate registers 12 through 15 at the time of the abend.
Action:
See accompanying messages for a more detailed description of the error. Save all dumps and other diagnostics for analysis. For assistance, contact CA Support at http://ca.com/support.
Reason:
An abend has occurred while CAIENF/USS was processing an event.
Action:
See accompanying messages for a more detailed description of the error. Save all dumps and other diagnostics for analysis. For assistance, contact CA Support at http://ca.com/support.
Reason:
An invalid parameter has been specified on the RELOAD command.
Action:
Review the invalid parameter identified in the message. Re-issue the RELOAD command with a correct parameter.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |