B1TS messages are issued by initialization, if the option Global Type Sequencing is enabled. This section details these messages along with possible causes and corrective actions to take in error situations.
Reason:
The type sequence data set is specified in the C1DEFLTS table but the parmlib data set is missing. The type sequence file must be a member of the Parmlib dataset.
Action:
Update the C1DEFLTS' PARMLIB= parameter with the correct data set name.
Reason:
Allocation failure.
Action:
Check the C1DEFLTS' Parmlib and Typeseqmbr specification. Check the output for any relevant error messages. If the problem cannot be resolved, contact CA Technical Support.
Reason:
Open failure.
Action:
Check the C1DEFLTS' Parmlib and Typeseqmbr name specification. Check output for any relevant error messages. If the problem cannot be resolved, contact CA Technical Support.
Reason:
This message is generated when you specify a LRECL value greater than 80 for the Type Seq Parser Input.
Action:
Re-build the type sequence file with a LRECL of 80.
Reason:
See previous error message for the actual problem. The likely problem is invalid data within the file.
Action:
Correct the erroneous type sequence statement within the type sequence file and invoke CA Endevor SCM.
Reason:
Memory problem.
Action:
Increase the region size of the job and invoke CA Endevor SCM. If the problem continues, contact CA Technical Support.
Reason:
Memory problem.
Action:
Increase the region size of the job and invoke CA Endevor SCM. If the problem continues, contact CA Technical Support.
Reason:
Memory problem.
Action:
Increase the region size of the job and invoke CA Endevor SCM. If the problem continues, contact CA Technical Support.
Reason:
User error. Only one type sequence statement can be specified with the same type and System name.
Action:
Choose the correct statement by deleting the other duplicates and invoke CA Endevor SCM.
Reason:
Errors have been detected with the named (dsn/member) TYPE SEQUENCE table.
Action:
Correct the errors so that TYPE SEQUENCE processing can be enabled.
Reason:
The named TYPE SEQUENCE table (dsn/member) in message B1TS010I is not usable, and CA Endevor SCM disallows any action attempting to use TYPE SEQUENCING.
Action:
Notify your administrator that the named TYPE SEQUENCE table (dsn/member) in message B1TS010I is unusable, and needs to be corrected.
BC1PSVCS is the SVCS program. This program is the SVC screen services module, which manages the SVC and DESERV exit screening Environments. It is called to activate, terminate, setup, and tear down, the SVC and DESERV Environments. In addition, it establishes the tables required for DDNAME monitoring for the Automated Configuration Manager (ACM). This section details these messages along with possible causes and corrective actions to take in error situations.
Reason:
A RACFROUT VERIFY request was issued for the CA Endevor SCM alternate ID and the request failed. Following the text, three parameters are returned: the return code from the RACFROUT request, the return code issued by the Security Authorization Facility (SAF) interface, and the reason code issued by the Security Authorization Facility (SAF) interface. The second part of message E010 displays the name of the one-to eight-character alternate ID that is being verified. The alternate ID value is specified in the C1DEFLTS table.
Action:
Check with your security administrator to ensure the alternate ID security access was properly setup in your security product.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|