Reason:
Provides a listing of control statements as read from the CALMP KEYS file.
Action:
None.
Reason:
Informational message issued when a valid EKG device code has been entered:
is the month the device was activated
is the day the device was activated
is the year the device was activated
Action:
None.
Note: This message can have many different causes and responses
Reason:
Invalid data has been encountered in the CALMP KEYS file. Processing continues with the next input record.
Action:
Review the CALMP KEYS file for invalid data.
Reason:
Missing keyword, where one of the following is listed:
Action:
Verify the indicated field on the input record.
Reason:
One of the keywords is a duplicate, and was found more than once on the input record.
Action:
Verify the indicated field on the input record and remove the duplication.
Reason:
CPU keyword is too long.
Action:
Verify the correct definitions for the CPU and confirm it is correctly defined to the input record.
Reason:
CPU operand is too long.
Action:
Ensure the CPU keyword is in the proper format of mmmm-tttt.
Reason:
CPU serial number is not six characters.
Action:
Confirm that the correct serial number of six characters is defined to the CPU keyword of the input record.
Reason:
DATE keyword is not seven characters.
Action:
Confirm that the DATE keyword defined to the input record is in the format ddmmmyy.
Reason:
LMPcode keyword is invalid.
Action:
Ensure that the LMPcode on the input record has been defined correctly.
Reason:
Key tampering detected or transcription error.
Action:
Call LMP support. The LMPcode defined to the input record is now invalid.
Reason:
LMPcode listed ID for another CPU.
Action:
Verify that the LMPcode defined to the input record is correct and that you are attempting to start your CA solution on the correct CPU.
Reason:
The length of the data within the () of the EKG control record is not eight bytes long.
Action:
Verify that the length of the data within the () of the EKG control record is eight bytes long.
Reason:
LMP was unable to LINK to the product's x'1FF' disk.
Action:
Ensure there is a x'1FF' minidisk or link defined for the service machine. For more information about the actual cause of the LINK failure, see the return codes of the CP LINK command.
Reason:
LMP was unable to ACCESS the CALMP KEYS file.
Action:
Ensure that a CALMP KEYS file exists on the service machine's x'1FF' disk. For more information about the actual cause of the ACCESS failure, see the return codes of the CMS ACCESS command.
Reason:
LMP was unable to READ the CALMP KEYS file.
Action:
Ensure that the CALMP KEYS file on the service machine's x'1FF' disk contains fixed 128-byte records.
Reason:
The CA LMP licensing agreement for the indicated product is about to expire. The key expires in the specified number of days.
Note: For CA Mainframe VM Product Manager components at genlevel 0212 or above, the LMP enforcement software does not cause a component to fail. Instead, the software issues enforcement messages.
Action:
Contact CA LMP support as soon as possible to avoid potential expiration of CA solution licensing agreement and discontinuance of CA solution initialization.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|