This section details messages generated by the Automated Configuration Manager (ACM) of the CA Endevor Automated Configuration option, along with possible causes and corrective actions to take in error situations.
Reason:
This message indicates that allocation of ACM root and cross reference data sets failed.
Action:
Check for the reason. Normally, you will also receive a C1A0011E or C1A0012E message that explains the problem further.
Reason:
An attempt to open the ACM root or cross reference data set failed.
Action:
Make sure the data set names specified in the C1DEFLTS table are correct and the data sets exist and are available.
Reason:
The indicated number of Root Records was successfully added to the ACM root data set.
Action:
None.
Reason:
An ACM Parent record could not be retrieved, added, or both.
Action:
Add the Element to your Environment and retry the transaction. Make sure the ACM Root file is not full. If the error still occurs, rebuild the ACM Root and XREF files.
Reason:
If this message occurs as part of component updates, it implies the ACM VSAM root is out of space or non-accessible. If it occurs as part of the batch load procedure, BUILDX, an ACM root associated with the CHILD component was deleted.
Action:
For component update, review the VSAM characteristics, reallocate and rebuild. For batch load, review the integrity of the ACMLIST and ACMCOMP files used by BUILDR and BUILDX and correct the discrepancy.
Reason:
This is an informational message. For batch load, it represents the number of component Objects processed and related, and the maximum return code. For component processing, it indicates that the child Element record could not be retrieved or added.
Action:
For batch load, no action is required. For component processing, review the ACM root VSAM file to determine if there is a space or authority problem.
Reason:
A related member component could not be retrieved or added to the ACM Root file.
Action:
Review the VSAM attributes of the ACM Root file to detect a space or authority problem. If the problem was caused by an out of space condition, REPRO and rebuild the VSAM file in error.
Reason:
This message indicates that the ACM Root and XREF files were successfully initialized.
Action:
None.
Reason:
The Element which was specified for the query was not found in the ACM configuration data.
Action:
Check the Element name specification; if the specification was correct, contact CA Technical Support for help.
Reason:
During dynamic allocation of the ACM Root and XREF VSAM files, an error occurred. The ddname indicates the file in error, operation is the operation being attempted, and RC is the R15 value from the operation.
Action:
Based on the information in the message, correct the problem and re-execute the job.
Reason:
The ACM ROOT/XREF data sets, which were in optimized format, were updated by a version of the CA Endevor SCM software which was superseded.
Action:
Make sure that older releases of CA Endevor SCM are not used to update the ACM ROOT and XREF data sets. Run BC1JACMO to re-optimize the ROOT and XREF data sets.
Reason:
The indicated comment or object component was not retrieved or added in the ACM root file. This is probably due to a space or authority problem on the VSAM file.
Action:
Review the characteristics of the ACM Root file, and correct. If it is a space problem, the ACM Root and XREF must be resized and rebuilt.
Reason:
ACM component processing received an invalid child-value during component update.
Action:
Contact CA Technical Support with the invalid child-value.
Reason:
A job was submitted to perform your ACMQ request.
Action:
None.
Reason:
Your ACMQ request was completed.
Action:
None.
Reason:
No updates to the ACM index data set are necessary. Updates are necessary only when component relationships are modified.
Action:
None.
Reason:
The ACMIDXUP option of the C1DEFLTS table is set to a value of 'N'. This causes this feature to be bypassed.
Action:
None.
Reason:
Updates to the ACM index data set are complete. Updates are necessary when component relationships are modified.
Action:
None.
Reason:
This informational message is issued by component processing. The component-type is one of the types listed next, and the count is the numeric count of the indicated type added to the ACM Root and XREF files.
Component-Type:
ACM ELEMENT UPDATES: ACM MEMBER UPDATES: RELATED ELEMENT UPDATES: RELATED MEMBER UPDATES: RELATED OBJECT UPDATES: RELATED COMMENT UPDATES:
Action:
None.
Reason:
Informational message. This message specifies the number of Elements that are referenced by this Element.
Action:
None.
Reason:
Informational message. This message informs the user that this Element is not referenced by any other Element.
Action:
None.
Reason:
Informational message. This message informs the user that this Element is referenced by one other Element.
Action:
None.
Reason:
This message appears with a RC=4. BC1PACMO notifies you with this message if the file ACMCOMP was present during the BC1PACMO run (not dummy or nullfile), and the ACMCOMP file did not contain any Element relation information different from what was already contained in the ACMQ files before the run.
Action:
None.
Reason:
Invalid records were found in XREF while running BC1JACMO.The reorganization utility has removed these records.
Action:
Contact CA Technical Support for help with the problem analysis.
Reason:
BC1PACMO utility was run with parameter VALIDATE and has detected orphaned ACM entries and deleted them.
Action:
None.
Reason:
The ROOT or XREF file does not contain a logical EOF record and is now considered logically corrupted.
Action:
Check when the file was last used and why, and when it stopped working.
Reason:
Informational message. LIST used/using components for ELEMENT/MEMBER/RELATED OBJECT/RELATED COMMENT. This message is issued when a wildcarded ACMQ batch request is translated into one or more specific ACMQ requests.
Action:
None.
Reason:
Informational message. LIST used/using components for ELEMENT/MEMBER/RELATED OBJECT/RELATED COMMENT. This message is issued when a wildcarded ACMQ batch request is translated into one or more specific ACMQ requests.
Action:
None.
Reason:
Informational message. LIST used/using components for ELEMENT/MEMBER/RELATED OBJECT/RELATED COMMENT. This message is issued when a wildcarded ACMQ batch request is translated into one or more specific ACMQ requests.
Action:
None.
Reason:
Informational message. LIST used/using components for ELEMENT/MEMBER/RELATED OBJECT/RELATED COMMENT. This message is issued when a wildcarded ACMQ batch request is translated into one or more specific ACMQ requests.
Action:
None.
Reason:
Informational message. LIST used/using components for ELEMENT/MEMBER/RELATED OBJECT/RELATED COMMENT. This message is issued when a wildcarded ACMQ batch request is translated into one or more specific ACMQ requests.
Action:
None.
Reason:
Informational message. LIST used/using components for ELEMENT/MEMBER/RELATED OBJECT/RELATED COMMENT. This message is issued when a wildcarded ACMQ batch request is translated into one or more specific ACMQ requests.
Action:
None.
Reason:
Informational message. LIST used/using components for ELEMENT/MEMBER/RELATED OBJECT/RELATED COMMENT. This message is issued when a wildcarded ACMQ batch request is translated into one or more specific ACMQ requests.
Action:
None.
Reason:
The ACMQ batch query #nn has completed with return code=xx. RC=04 indicates that no entries were found.
Action:
None.
Reason:
Entity contains no references or is not referenced. An ACMQ query did not find any references.
Action:
Make sure that you have no spelling errors.
Reason:
The name specified in your query does not exist in the ACMQ database.
Action:
Make sure that you have no spelling errors.
Reason:
BC1PACMC abended.
Action:
Check when this worked last time, and compare to see what has changed. Contact CA Technical Support for help if necessary.
Reason:
BC1PACMC returned a non-zero return code.
Action:
Contact CA Technical Support.
Reason:
An internal function call returned a bad return code.
Action:
Contact CA Technical Support.
Reason:
An internal function call returned a bad return code.
Action:
Contact CA Technical Support.
Reason:
An internal function call returned a bad return code.
Action:
Contact CA Technical Support.
Reason:
An internal function call returned a bad return code.
Action:
Contact CA Technical Support.
Reason:
BC1PACMC returned a non-zero return code.
Action:
Contact CA Technical Support.
Reason:
An internal function call returned a bad return code.
Action:
Contact CA Technical Support.
Reason:
Informational message. This message indicates the ACMOUT data set name.
Action:
None.
Reason:
Informational message. This message indicates the ACMOUT data set name and member name.
Action:
None.
Reason:
Informational message. LIST used/using components for ELEMENT/MEMBER/RELATED OBJECT/RELATED COMMENT. This message is issued when a wildcarded ACMQ batch request is translated into one or more specific ACMQ requests.
Reason:
Informational message. LIST used/using components for ELEMENT/MEMBER/RELATED OBJECT/RELATED COMMENT. This message is issued when a wildcarded ACMQ batch request is translated into one or more specific ACMQ requests.
Action:
None.
Reason:
Informational message. LIST used/using components for ELEMENT/MEMBER/RELATED OBJECT/RELATED COMMENT. This message is issued when a wildcarded ACMQ batch request is translated into one or more specific ACMQ requests.
Action:
None.
Reason:
Informational message. LIST used/using components for ELEMENT/MEMBER/RELATED OBJECT/RELATED COMMENT. This message is issued when a wildcarded ACMQ batch request is translated into one or more specific ACMQ requests.
Action:
None.
Reason:
Informational message. LIST used/using components for ELEMENT/MEMBER/RELATED OBJECT/RELATED COMMENT. This message is issued when a wildcarded ACMQ batch request is translated into one or more specific ACMQ requests.
Action:
None.
Reason:
ACMQ could not open the Root or XREF files (or both).
Action:
Make sure the following:
Reason:
A query was issued against the ACM files, but the indicated component-type is not in the ACM root file.
Action:
Check the specification screen to make sure that all fields are either specified explicitly, or contain wildcard (*) character. A blank specification screen attempts to query using a blank value. Retry the query after modifying the criteria.
Reason:
Action:
Rebuild the Root and XREF ensuring that the source ACMLIST and ACMCOMP outputs are properly related.
Reason:
One or more of the selected children components are not associated with any parent components.
Action:
Either refine your query to avoid these children, or disregard these entries.
Reason:
The last update data/timestamps in the ROO and XREF files are not the same.
Action:
Determine when this condition started and how the files got out of SYNC. Contact CA Technical Support. You may have to rebuild your ROOT/XREF files.
Reason:
This informational message appears as an SCL comment to direct the user to copy the SCL file from the temporary data set to a permanent location.
Action:
None.
Reason:
The name of the ACM root data set name is missing from the C1DEFLTS table.
Action:
Specify the name of the data set in the C1DEFLTS ACMROOT parameter.
Reason:
The name of the ACM cross-reference data set name is missing from the C1DEFLTS table.
Action:
Specify the name of the data set in the C1DEFLTS ACMXREF parameter.
Reason:
Unable to load the C1DEFLTS table.
Action:
Make sure the C1DEFLTS table exists in the authorized load library and the library exists within your login procedure.
Reason:
An ACM query was directed to go directly to print, but a printer class was not specified. A default printer class was chosen as the target of the output.
Action:
Either specify a printer class, or take the default of A.
Reason:
An ACM query was directed to go directly to print, but a destination was not specified. Output will go to the System-defined destination.
Action:
None.
Reason:
The ACMOUT file, required for your query, cannot be allocated because someone else is already using it.
Action:
Determine who is using the file, or wait until the file is available.
Reason:
When processing a SET FROM ENV/STG the program detected that the named ENV does not contain the named Stage.
Action:
Correct the SCL statement and resubmit.
Reason:
The ACMQ ROOT file is in use by another user.
Action:
Retry the action when the ACMQ ROOT file is no longer in use.
Reason:
ACMQ is not activated.
Action:
The CA Endevor SCM administrator can activate ACMQ by entering Y in the ASCM field in the CA Endevor SCM C1DEFLTS table, provided your site is licensed for this option.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|