|
|
|
The following messages are produced by the CAICCI, CAIRIM, CAIENF, CAIENF/CICS, CAIENF/DB2, and CAIENF/SNMP components.
Reason:
Informational. Title for the CAISMFU-installed SMF program display.
Action:
No action is required.
Reason:
Informational. Blank display for spacing of CAIRIMU and CAISMFU output.
Action:
No action is required.
Reason:
Informational. Heading for the CAISMFU-installed SMF program display.
Action:
No action is required.
Reason:
The message displays information about a CAISMFU-installed SMF program.
Displays the load module name of the installed program.
Identifies the product, version, and level of the installed program in the format ppvl, where pp is the product code, v is the version level, and l is the release level.
Indicates the status of the installed module:
Action:
No action is required.
Reason:
The message displays the following information in the CAISMFU utility output:
Displays the total number of interfaces that have been installed, including active interfaces made inactive due to abends.
Displays the total number of SMF programs called for processing. This number is roughly the number of active interfaces multiplied by the number of SMF calls.
Action:
No action is required.
Reason:
Informational. Title from the CAIRIMU-initialized product and component display.
Action:
No action is required.
Reason:
Informational. Heading for the CAIRIMU-initialized product and component display.
Action:
No action is required.
Reason:
Entries in the CAIRIMU-installed initialized product and component display. Fields defined as follows:
Displays the name of the product or component initialized.
Identifies the version of the product or component initialized.
Identifies the product module name that performed the initialization.
Note: These modules are delivered with the products and not with CAIRIM.
Displays the date on which the product or component was initialized.
Displays the time at which the product or component was initialized.
Action:
No action is required.
Reason:
Indicator in the CAIRIMU-initialized product and component display that defines the load library from which the product or component was initialized. This is only present if an alternate load library was specified in the CAIRIM parameter library, as defined through the PARMLIB DD statement.
Action:
No action is required.
Reason:
Output from CAIRIMU. Displays the total number of product and component interfaces that have been initialized through CAIRIM.
Action:
No action is required.
Reason:
If executing CAIRIMU, the CAIRIM Resource Initialization Manager has not been run or has abended prior to creating the in-storage initialization index.
If executing CAISMFU, the CAISMFI dynamic SMF interceptor program has not been run or has abended prior to creating the in-storage module index.
Action:
If executing CAIRIMU, make sure that a valid file (as defined through the PARMLIB DD statement) exists and that it contains one or more initialization parameters. Then rerun CAIRIMU by executing the CAIRIM procedure supplied as CAS9. For assistance, contact CA Support at http://ca.com/support.
If executing CAISMFU, check the CAIRIM System Requirements section of your product Installation Guide for information on the use of CAISMFI by the product. If there are no products installed that use CAISMFI, this is a normal condition. If your installation contains one or more products using CAISMFI, then rerun CAIRIM. For assistance, contact CA Support at http://ca.com/support.
Reason:
The indicated number of warnings and violations have occurred for all software solutions using CA LMP on the specified CPU's serial number.
Action:
If you have contacted CA LMP support and your software solution licensing agreement has been updated for the solution in warning or violation, or both, this message is informational.
If you have not contacted CA LMP support or your software solution licensing agreement has not been updated for the solution in warning or violation, see message CAS9013A for further details on the solutions in warning or violation.
Reason:
CAIRIM has initialized product xx and that product is running (xx is your CA solution's product code). However, your CA LMP agreement for this product is about to expire or has expired and CA LMP execution software may deactivate the product in the near future if the situation is not corrected.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The CA LMP execution key is required to run the CA solution.
Action:
Contact CA LMP support. Report the seed value displayed in this message to obtain the execution key.
Reason:
An access code is required to extend operation of a CA solution for which the licensing agreement has expired.
Action:
Enter the access code obtained from CA LMP support.
Reason:
The access code entered is invalid according to CA LMP execution software.
Action:
Verify that you entered the correct access code as given to you by CA LMP support. If the access code was entered correctly, contact CA LMP support.
Reason:
The access code you entered to obtain a licensing extension has been accepted and the extension is in effect.
Action:
No action is required.
Reason:
The CA LMP seat license service routine has detected an error condition while processing the indicated function request. The LMP key for the request, or ‘**’ if the LMP key cannot be identified or is not applicable, is displayed. The hexadecimal return code, rc, and the hexadecimal reason code, rsn, are returned to the caller.
Action:
This message is informational for the component calling the LMP seat license common service. The return code and reason codes typically reflect error conditions that the calling program must correct. See LMP Seat License Return Codes and Reason Codes.
Reason:
An invalid parameter has been detected on input to S910INIT.
Action:
Review the PARM() identified in the message. Valid parameters are REINIT, REFRESH, and DELETE. Correct the parameter field and resubmit the job. For more information on valid operands, refer to the Administration Guide.
Reason:
No valid security system exists within the environment. RACF or a RACF-compatible security product is required.
Action:
Remove the product initialization control card from the CARIMPRM file until a valid security environment is installed (like CA Top Secret, CA ACF2, RACF, or a RACF-compatible product).
Reason:
Informational message pertaining to the execution of S910INIT.
Action:
No action is required.
Reason:
An error was encountered during CAISSF initialization.
Action:
Ensure routines CAS9SEC and the external security translator are available through the CAS9 STEPLIB or linklisted data set:
|
Security System |
Translator |
|---|---|
|
CA Top Secret |
CAS9TS42 |
|
CA ACF2 |
CAS9ACF2 |
|
RACF or RACF compatible |
CAS9SAFC |
If the routines are already present on the system and you wish to update CAISSF through maintenance, use the PARM(REFRESH(SSF)) parameter. For more information, see the Administration Guide.
Reason:
The installed security system does not match the security system name coded in the SSF parameter.
Action:
Correct the SSF parameter to have the proper security system name and rerun the job.
Reason:
No valid security system exists within this environment.
Action:
Reply with a security system to continue or N to cancel. If you reply N, message 'CAS9021E ENVIRONMENT ERROR DETECTED. UNABLE TO ADD CAISSF ROUTINES' will be displayed, indicating there is no security system available.
Reason:
No valid security system exists within this environment.
Action:
Reply with a security system to continue or N to cancel. If you reply N, message 'CAS9021E ENVIRONMENT ERROR DETECTED. UNABLE TO ADD CAISSF ROUTINES' will be displayed, indicating there is no security system available.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |