Previous Topic: SMGR MessagesNext Topic: BC1PVSIO Messages


SYN Messages

SYN messages are generated by the catalog synchronization utility. The following list of SYN messages includes possible causes and corrective actions to take in error situations.

SYN0000I

BEGINNING PHASE 1.

Reason:

Informational. Start of the Master Control File to catalog verification phase of the verification and synchronization process.

Action:

None.

SYN0000I

BEGINNING PHASE 2.

Reason:

Informational. Start of the catalog to Master Control File synchronization phase of the verification and synchronization process.

Action:

None.

SYN0001E

NO ENVIRONMENT COMMAND WAS SPECIFIED. SYNCHRONIZATION CHECKS WILL NOT BE DONE.

Reason:

R/C = 12. An input environment statement was expected, but none was found. Processing is terminated.

Action:

Specify an environment statement and resubmit the command.

SYN0002I

ENVIRONMENT env-name MCF ELEMENT TO CATALOG SYNCHRONIZATION STARTING.

Reason:

Informational. Identifies the environment for which the synchronization process is starting.

Action:

None.

SYN0003I

TOTAL CATALOG SEGMENTS CREATED FOR ENVIRON env-name: count

Reason:

Informational. Identifies the number of catalog segments created for the specified environment.

Action:

None.

SYN0003I

TOTAL # OF MISSING CTLG SGMTS FROM ENVIRON env-name: count

Reason:

Informational. Identifies the number of catalog segments missing from the specified environment.

Action:

None.

SYN0004I

TOTAL CATALOG SEGMENTS UPDATED FOR ENVIRON env-name: count

Reason:

Informational. Identifies the number of catalog segments updated for the specified environment.

Action:

None.

SYN0004I

TOTAL # OF OLD CTLG SGMTS FOUND IN ENVIRON env-name: count

Reason:

Informational. Identifies the number of old catalog segments found in the specified environment.

Action:

None.

SYN0005I

TOTAL # OF ELEMENTS PROCESSED FROM ENVIRON env-name: count

Reason:

Informational. Identifies the number of elements processed from the specified environment.

Action:

None.

SYN0006E

ENVIRONMENT: env-name DOES NOT EXIST.

Reason:

R/C = 12. The environment specified by the user input does not exist in the C1DEFLTS table. Processing continues with the next environment.

Action:

None.

SYN0007E

$IMR REQUEST FAILED. $IMR ERROR MESSAGE FOLLOWS.

Reason:

R/C = 12. An Inventory Manager error occurred. Processing terminates.

Action:

See the next message for the actual error.

SYN0008E

C1BMINIT FAILURE. CALL ENDEVOR TECHNICAL SUPPORT.

Reason:

R/C = 12. Internal error occurred. Processing terminates.

Action:

Contact CA Endevor SCM Technical Support.

SYN0009E

PROCESSING TERMINATED.

Reason:

R/C = 12. Processing terminates.

Action:

Contact CA Endevor SCM Technical Support.

SYN0010E

PROCESSING TERMINATED BECAUSE OF CONTROL STATEMENT ERRORS, RESULT=parser literal.

Reason:

R/C = 12. Processing terminates.

Action:

Refer to the parser literal and any other parser error log created by the utility. Correct the problem and resubmit job.

SYN0011I

TOTAL # OF ELEMENTS PROCESSED, ALL ENVIRONMENTS: count

Reason:

Informational. Indicates the number of elements processed from all environments.

Action:

None.

SYN0032I

TOTAL CATALOG SEGMENTS DELETED FOR ENVIRON env-name: count

Reason:

Informational. Indicates the number of catalog segments deleted for the specified environment.

Action:

None.

SYN0032I

TOTAL # OF ORPHAN CTLG SGMTS IN ENVIRON env-name: count

Reason:

Informational. Indicates the number of catalog segments in the specified environment that are orphaned.

Action:

None.

SYN0033I

TOTAL CATALOG SEGMENTS PROCESSED FOR ENVIRON env-name: count

Reason:

Informational. Indicates the number of catalog segments processed for the specified environment.

Action:

None.

SYN0034I

TOTAL CATALOG SEGMENTS PROCESSED, ALL ENVIRONMENTS: count

Reason:

Informational. Indicates the number of catalog segments processed for all environments.

Action:

None.

SYN0035E

STORAGE PROBLEM WHILE ACQUIRING ENVIRON ENTRY SPACE.

Reason:

R/C = 12. Processing is terminated.

Action:

Refer to messages contained in the job log.

SYN0036E

$IMR EXTRACT ALL SEGMENTS REQUEST FAILED. $IMR ERROR MESSAGE FOLLOWS.

Reason:

R/C = 12. An Inventory Manager error occurred. Processing terminates.

Action:

See the next message for the actual error.

SYN0037E

BAD PARM STATEMENT ON EXEC STATEMENT, MUST BE UPDATE OR VALIDATE.

Reason:

R/C = 12. Processing terminates. The execution statement did not specify update or validate.

Action:

Correct the PARM statement and resubmit the job.

SYN0040I

TOTAL # OF EINDEX RECORDS CREATED FOR ENV env-name: count

Reason:

Informational. Identifies the number of element index records created for the specified environment.

Action:

None.

SYN0040I

TOTAL # OF MISSING EINDEX RECORDS FOR ENV env-name: count

Reason:

Informational. Identifies the number of element index records missing in the specified environment.

Action:

None.

SYN0999W

OUT OF SYNC DATA FOUND, DATA has/has not BEEN UPDATED

Reason:

Informational message. The utility found discrepancies between the MCF and the catalog. If the utility processed in update mode, it corrected the discrepancies. The step finished with RC 4.

Action:

None.

*ERROR * $SMR ERROR ON DELTA RETRIEVAL, MCF ELEMENT ele-name TYPE typ-name, PROCESSING BYPASSED.

Reason:

R/C = 12. An error occurred while trying to retrieve the element’s long name from its delta file. The element is bypassed and the job continues to run. At end of processing, the job ends with a return code of at least 12.

Action:

See previous error messages for additional information.

*WARNING* LONG NAME NOT FOUND IN DELTA, MCF ELEMENT ele-name TYPE typ-name USED FOR CATALOG.

Reason:

R/C = 8. For some reason unknown, a long named element did not have its name recorded in its delta file. The Master Control File element name is substituted for the long element name. Processing continues. At the end of processing, the job ends with a return code of at least 8.

Action:

Review all the elements that were created this way. If its name is invalid, retrieve the element, delete it from CA Endevor SCM, and then add the element back into CA Endevor SCM with its actual name.

*WARNING* INVALID ELEMENT LENGTH OR NAME FIELD W/IN DELTA FILE, MCF ELEMENT ele-name TYPE typ-name USED FOR CATALOG.

Reason:

R/C = 8. For some reason unknown, the long named element was recorded incorrectly in its delta file. The Master Control File element name is substituted for the long element name. Processing continues. At end of processing, the job ends with a return code of at least 8.

Action:

Review all the elements that were created this way. If its name is invalid, retrieve the element, delete it from CA Endevor SCM, and then add the element back into CA Endevor SCM with its actual name.

*UPDATE* CTLG SGMT: ELEMENT ele-name

TYPE typ-name AT ENV env-name SID stg-id SYS sys-name SBS sbs-name

Reason:

R/C = 4. An out of date element segment was found. The segment was updated with the Master Control File element data.

Action:

None.

*OLD * CTLG SGMT: ELEMENT ele-name

TYPE typ-name AT ENV env-name SID stg-id SYS sys-name SBS sbs-name

Reason:

R/C = 4. An out of date element was found. The utility is running in validation mode, the catalog is not updated.

*CREATED* CTLG SGMT: ELEMENT ele-name

TYPE typ-name AT ENV env-name SID stg-id SYS sys-name SBS sbs-name

Reason:

R/C = 4. The catalog did not contain an element entry for the Master Control File element identified in the above message. A segment was created for it.

*MISSING* CTLG SGMT: ELEMENT ele-name

TYPE typ-name AT ENV env-name SID stg-id SYS sys-name SBS sbs-name

Reason:

R/C = 4. The catalog did not contain an element entry for the Master Control File element identified in the above message. The utility is running in validation mode, the catalog was not updated.

*DELETED* CTLG SGMT: ELEMENT ele-name

TYPE typ-name AT ENV env-name SID stg-id SYS sys-name SBS sbs-name

Reason:

R/C = 4. A catalog segment was found for a nonexistent Master Control File element record. The segment was deleted.

*ORPHAN * CTLG SGMT: ELEMENT ele-name

TYPE typ-name AT ENV env-name SID stg-id SYS sys-name SBS sbs-name

Reason:

R/C = 4. A catalog segment was found for a nonexistent Master Control File element record identified in the message above. The utility is running in validation mode, no changes are made to the catalog.

VAL Messages

VAL messages are generated during processing of the Validate action. The following list of VAL messages includes possible causes and corrective actions to take in error situations.

VAL0001I

ELEMENT MASTER VALIDATION STARTED

Reason:

Informational. This message notifies you that the element master validation process has begun.

Action:

None.

VAL0002E

STATUS OF PROCESSOR OUTPUT IS UNKNOWN - ELEMENT WAS RESTORED W/O REPROCESSING

Reason:

Error message. This message notifies you that the Restore action was executed for this element, but it has not been generated following the restore.

Action:

If this element is valid, consider executing the Generate action against it.

VAL0003E

ELEMENT HAS NOT BEEN RE-GENERATED SINCE LAST SOURCE UPDATE

Reason:

Error message. This message notifies you that this element has not been generated since after the source was last changed.

Action:

If this element is valid, consider executing the Generate action against it.

VAL0004E

THE LAST GENERATE PROCESSOR EXECUTION FAILED

Reason:

Error message. This message notifies you that the last time this element was generated, the generate failed.

Action:

If this element is valid, view the listing to determine why the generate action failed. Correct the error and generate the element.

VAL0005E

ELEMENT IS LOCKED IN PACKAGE: package-id

Reason:

Error message. This message notifies you that this element is currently locked in a package.

Action:

None.

VAL0006I

ELEMENT MASTER VALIDATION COMPLETE: HIGHEST RC = nn

Reason:

Informational message. This message notifies you that the element master validation process is complete. The return code indicates if any element master validation errors were detected.

Action:

None.

VAL0010I

SYNCHRONIZATION PROCESSING STARTED

Reason:

Informational message. This message notifies you that the synchronization validation process has begun.

Action:

None.

VAL0011I

A COPY OF THIS ELEMENT WAS FOUND UP THE LOGICAL MAP AT LOCATION:

Reason:

Informational message. This message notifies you that a copy of the element was found up the logical map and it will be used in the synchronization validation process.

Action:

None.

VAL0012I

ENV: env-name SYSTEM: sys-name SUBSYSTEM: subsys-name TYPE: type-name STAGE ID: stage-id

Reason:

Informational message. This message notifies you of the location of the copy of the element found up the logical map that will be used in the synchronization validation process.

Action:

None.

VAL0013I

THESE TWO COPIES OF THE ELEMENT ARE SYNCHRONIZED

Reason:

Informational message. This message notifies you that the two copies of the element are synchronized.

Action:

None.

VAL0014I

NO OTHER COPY OF THIS ELEMENT EXISTS UP THE LOGICAL MAP

Reason:

Informational message. This message notifies you that no other copy of this element was found up the logical map. Therefore, synchronization validation is not performed.

Action:

None.

VAL0015I

SYNCHRONIZATION PROCESSING COMPLETE: HIGHEST RC = nn

Reason:

Informational message. This message notifies you that the synchronization validation process is complete. The return code indicates if any element synchronization validation errors were detected.

Action:

None.

VAL0020I

SEARCHING FOR AN IN-BETWEEN COPY OF ELEMENT IN THE PHYSICAL MAP

Reason:

Informational message. This message notifies you that two copies of this element were found in the logical map. Therefore, a search for an in-between copy in the physical map is performed.

Action:

None.

VAL0021I

AN IN-BETWEEN COPY OF THIS ELEMENT DOES NOT EXIST

Reason:

Informational message. This message notifies you that two copies of this element were found in the logical map. A search for an in-between copy in the physical map was performed and no copy exists.

Action:

None.

VAL0022I

SEARCH FOR IN-BETWEEN COPY COMPLETE: HIGHEST RC = = nn

Reason:

Informational message. This message notifies you that the search for an in-between copy of this element in the physical map is complete. The return code indicates if an in-between copy of this element exists.

Action:

None.

VAL0030W

ACM IS NOT INSTALLED AT YOUR SITE. THE COMPONENT VALIDATION OPTION IGNORED

Reason:

Warning message. The component validation option was specified, but the ASCM parameter in the C1DEFLTS table is not enabled.

Action:

Determine if the CA Endevor SCM Automated Configuration Manager option is available at your site. If so, talk to the Administrator to determine why it in not enabled.

VAL0031I

NO COMPONENTS EXIST FOR THIS ELEMENT

Reason:

Informational message. The component validation option was specified, but no components exist for this element. Therefore, component validation processing is not performed for this element.

Action:

None.

VAL0032I

NUMBER OF COMPONENTS VALIDATED: cmp-cnt, NUMBER CONTAINING ERRORS: error-cnt

Reason:

Informational message. The component validation option was specified. This message indicates how many components were validated and how many errors were detected.

Action:

None.

VAL0040W

NO ACTION OPTIONS SPECIFIED – ALL VALIDATE ACTION OPTIONS WILL BE PERFORMED

Reason:

Warning message. None of the action options were specified. The validate action will assume all were specified.

Action:

None.

VAL0090S

UNABLE TO OBTAIN STORAGE FOR COMPONENT CHAIN - BC1PVLDE, INITRUTN RC- return-code

Reason:

An unexpected internal error occurred while attempting to obtain storage.

Action:

Contact your CA Endevor SCM Administrator.

VAL0091S

ELEMENT MASTER ADDRESS PASSED TO BC1PVLVC BY BC1PVLDE IS INVALID

Reason:

An unexpected internal error occurred. The element master address passed to the component validation program is invalid.

Action:

Contact your CA Endevor SCM Administrator.