Error Codes and Messages › B1E Message Codes › B1E Messages

B1E Messages

This section details the B1E messages issued by the CA Endevor SCM InfoMan Interface, along with possible causes and corrective actions to take in error situations.

B1EI001I

Text

Reason:

Informational message.

Action:

None.

B1EI010E

INFO/MAN API NOT ACTIVE

Reason:

The CA Endevor SCM side of the interface has failed to establish a connection with the CA Endevor SCM InfoMan Interface, because the CA Endevor SCM InfoMan Interface is not active.

Action:

Contact your CA Endevor SCM InfoMan Interface Administrator.

B1EI050E

INFO/MAN API OBTAIN RESOURCE REQUEST FAILURE IN module name: routine name PIDT: pidt name

Reason:

This is a CA Endevor SCM InfoMan Interface error.

Action:

Examine any CA Endevor SCM InfoMan Interface error codes, and then contact your CA Endevor SCM InfoMan Interface Administrator.

B1EI051E

INFO/MAN API INQUIRY REQUEST FAILURE IN module name: routine name

Reason:

This is a CA Endevor SCM InfoMan Interface error.

Action:

Examine any CA Endevor SCM InfoMan Interface error codes; then contact your CA Endevor SCM InfoMan Interface Administrator.

B1EI052E

$PKMR EXTRACT FAILURE IN module name: routine name, RC=return code (HEX) REASON=reason code (HEX)

Reason:

Internal error.

Action:

Provide the JES job log and all output listings; then contact your CA Endevor SCM Administrator.

B1EI053E

REQUIRED PIDT SWORD s-word MISSING FROM table name TABLE

Reason:

A required S-word is missing from the IBM PIDT tables.

Action:

Contact your CA Endevor SCM InfoMan Interface Administrator. The required S-word must be included in the PIDT table and in all other relevant places in the Info/Man System. After updating the PIDT tables, rerun the batch utility before trying to restart the interface.

B1EI054E

MORE THAN ONE INFO/MAN CHANGE RECORD EXISTS FOR PACKAGE Package name

Reason:

There should be only one CA Endevor SCM InfoMan Interface Change record per Package.

Action:

Examine the Info/Man database, determine which Change record is the correct one; then delete the other record.

B1EI055E

$PKMR CREATE FAILURE IN module name: routine name, RC=return code (HEX) REASON=reason code (HEX)

Reason:

Internal error.

Action:

Provide the JES job log and all output listings; then contact your CA Endevor SCM Administrator.

B1EI056E

THE CHANGE RECORD FOR PACKAGE Package name WAS NOT FOUND IN INFO/MAN DB

Reason:

The interface expects a Change record to exist in Info/Man for the named Package, but the record does not exist.

Action:

Create the record, reset the Package if the message was generated during Package processing; then resubmit.

B1EI056W

THE CHANGE RECORD FOR PACKAGE Package name WAS NOT FOUND IN INFO/MAN DB

Reason:

The interface expects a Change record to exist in Info/Man for the named Package, but the record does not exist.

Action:

Create the record, reset the Package if the message was generated during Package processing; then resubmit.

B1EI057E

INFO/MAN API FREE PIDT REQUEST FAILURE IN module name: routine name

Reason:

This is a CA Endevor SCM InfoMan Interface error.

Action:

Examine any Info/Man error codes; then contact your Info/Man Administrator.

B1EI058E

INFO/MAN API FREE PIRT REQUEST FAILURE IN module name: routine name

Reason:

This is a CA Endevor SCM InfoMan Interface error.

Action:

Examine any Info/Man error codes; then contact your Info/Man Administrator.

B1EI059E

PURGE OF ACTIVITY RECORDS DURING RESET/AFTER FAILED

Reason:

This is a CA Endevor SCM InfoMan Interface error.

Action:

Examine any Info/Man error codes; then contact your Info/Man Administrator.

B1EI060E

INFO/MAN API OBTAIN CREATE RESOURCE REQUEST FAILURE IN module name: routine name PIDT: pidt name

Reason:

This is a CA Endevor SCM InfoMan Interface error.

Action:

Examine any Info/Man error codes; then contact your Info/Man Administrator.

B1EI061E

INFO/MAN API CREATE REQUEST FAILURE IN module name: routine name

Reason:

This is a CA Endevor SCM InfoMan Interface error.

Action:

Examine any Info/Man error codes; then contact your Info/Man Administrator.

B1EI062E

INFO/MAN API OBTAIN ADD RELATION REQUEST FAILURE IN module name: routine name PIDT: pidt name

Reason:

This is a CA Endevor SCM InfoMan Interface error.

Action:

Examine any Info/Man error codes; then contact your Info/Man Administrator.

B1EI063E

INFO/MAN API CHECK-IN REQUEST FAILURE IN module name: routine name

Reason:

This is a CA Endevor SCM InfoMan Interface error.

Action:

Examine any Info/Man error codes; then contact your Info/Man Administrator.

B1EI064E

INFO/MAN API CHECK-OUT REQUEST FAILURE IN module name: routine name

Reason:

This is a CA Endevor SCM InfoMan Interface error.

Action:

Examine any Info/Man error codes; then contact your Info/Man Administrator.

B1EI065E

INFO/MAN API ADD RELATION REQUEST FAILURE IN module name: routine name

Reason:

This is a CA Endevor SCM InfoMan Interface error.

Action:

Examine any Info/Man error codes; then contact your Info/Man Administrator.

B1EI066E

INFO/MAN API UPDATE REQUEST FAILURE IN module name: routine name

Reason:

This is a CA Endevor SCM InfoMan Interface error.

Action:

Examine any Info/Man error codes; then contact your Info/Man Administrator.

B1EI067E

INTERNAL ERROR - UNKNOWN STRUCTURE FOUND IN LABEL label name UNDER USE: module name: routine name

Reason:

The script used to create the E/PIDT table contains an error.

Action:

Provide the JES job log and all output listings, obtain the script, and contact your CA Endevor SCM Administrator.

B1EI068E

INFO/MAN TSP INVOCATION FAILURE IN BC1PEI50: TSPRUTN

Reason:

This is a CA Endevor SCM InfoMan Interface error.

Action:

Examine any Info/Man error codes; then contact your Info/Man Administrator.

B1EI069E

INFO/MAN API RETRIEVE REQUEST FAILURE IN module name: routine name

Reason:

This is a CA Endevor SCM InfoMan Interface error.

Action:

Examine any Info/Man error codes; then contact your Info/Man Administrator.

B1EI070E

S-WORD s-word NOT FOUND IN RETRIEVE table name PIDT TABLE

Reason:

The named IBM PIDT table does not include the specified S-word.

Action:

Contact your Info/Man site Administrator. The specified S-word must be included in the named PIDT table, and in all related locations in Info/Man. Make sure to rerun the batch utility before restarting the interface.

B1EI071E

INTERNAL ERROR IN BC1PEI50 AT CRITRUTN, ENDEVOR KEYWORD keyword code NOT RECOGNIZED OR DATE CONVERSION ERROR

Reason:

Internal error.

Action:

Provide the JES job log and all output listings; then contact your CA Endevor SCM Administrator.

B1EI072E

INTERNAL ERROR IN BC1PEI50, UNKNOWN STRUCTURE FOUND FOLLOWING A CFLD SEGMENT IN LABEL label name

Reason:

Internal error.

Action:

Provide the JES job log and all output listings; then contact your CA Endevor SCM Administrator.

B1EI073E

S-WORD s-word NOT FOUND IN table name PIDT TABLE

Reason:

The named IBM PIDT table does not include the specified S-word.

Action:

Contact your Info/Man site Administrator. The specified S-word must be included in the named PIDT table, and in all related locations in Info/Man. Make sure to rerun the batch utility before restarting the interface.

B1EI074E

INTERNAL ERROR IN BC1PEI50 AT POPLRUTN, ENDEVOR KEYWORD keyword code NOT RECOGNIZED OR DATE CONVERSION ERROR

Reason:

Internal error.

Action:

Provide the JES job log and all output listings; then contact your CA Endevor SCM Administrator.

B1EI075W

POPULATION OF s-word BYPASSED. ONLY S-WORDS WHOSE DEFINITIONS ARE "R" OR "X" CAN BE POPULATED

Reason:

The specified S-word has a definition that is other than R or X.

Action:

Contact your Info/Man Administrator. If you specify the S-word again, make sure to rerun the batch utility before attempting to restart the interface.

B1EI076W

POPULATION OF s-word BYPASSED. TEXT FORMAT MUST BE USED AGAINST A FREE FORM S-WORD DEFINITION

Reason:

The specified S-word was not populated because the script used to create the E/PIDT table did not associate the TEXT keyword with the information to be stored in Info/Man.

Action:

Change the keyword associated with the relevant information to TEXT; then rerun the batch utility.

B1EI077E

PURGE OF ACTIVITY RECORDS DURING THE CREATE ACTIVITY PROCESS FAILED

Reason:

This is a CA Endevor SCM InfoMan Interface error.

Action:

Examine any Info/Man error codes; then contact your Info/Man Administrator.

B1EI078E

PURGE OF ACTIVITY RECORDS DURING THE PACKAGE DELETE PROCESS FAILED

Reason:

This is a CA Endevor SCM InfoMan Interface error.

Action:

Examine any Info/Man error codes; then contact your Info/Man Administrator.

B1EI079E

PURGE OF PARENT RECORD DURING THE PACKAGE DELETE PROCESS FAILED

Reason:

This is a CA Endevor SCM InfoMan Interface error.

Action:

Examine any Info/Man error codes; then contact your Info/Man Administrator.

B1EI080E

INTERNAL ERROR - INSUFFICIENT STORAGE: module name routine name

Reason:

Internal error.

Action:

Provide the JES job log and all output listings; then contact your CA Endevor SCM Administrator.

B1EI081E

INTERNAL ERROR - ALLOCATION ERROR IN BC1PEI50 ALLORUTN

Reason:

Internal error.

Action:

Provide the JES job log and all output listings; then contact your CA Endevor SCM Administrator.

B1EI082E

OPEN FOR OUTPUT ON FREE FORM TEXT DSN: data set name FAILED

Reason:

Internal error.

Action:

Provide the JES job log and all output listings; then contact your CA Endevor SCM Administrator.

B1EI083E

WRITE TO FREE FORM TEXT DSN: data set name FAILED

Reason:

The interface was unable to write freeform text to the named data set.

Action:

Provide the JES job log and all output listings; then contact your CA Endevor SCM Administrator.

B1EI084E

CLOSE OF FREE FORM TEXT DSN: data set name FAILED

Reason:

The interface was unable to close the named data set.

Action:

Provide the JES job log and all output listings; then contact your CA Endevor SCM Administrator.

B1EI085E

$PKMR DELETE FAILURE IN module name: routine name, RC=return code (HEX) REASON=reason code (HEX)

Reason:

Internal error.

Action:

Provide the JES job log and all output listings; then contact your CA Endevor SCM Administrator.

B1EI086E

INVALID ACTION CCID VALUE

Reason:

The CCID specified for an action contains blanks.

Action:

Submit the request again with a valid CCID. Contact your CA Endevor SCM Administrator for a list of valid CCIDs.

B1EI200E

NO PICA CONTROL BLOCK

Reason:

Initialization with the CA Endevor SCM InfoMan Interface failed, and the PICA block was not allocated.

Action:

Provide the JES job log and all output listings; then contact your CA Endevor SCM Administrator.

B1EI201E

LOAD OF THE INFO/MAN API SERVER "BLGYSRVR" FAILED

Reason:

The Info/Man BLGYSRVR module failed to load.

Action:

Examine any Info/Man error codes, then contact your Info/Man Administrator.

B1EI202E

INFO/MAN API INITIALIZATION FAILED, RC=return code (HEX), REASON=reason code (HEX)

Reason:

The interface was unable to initialize the CA Endevor SCM InfoMan Interface.

Action:

Look up the specified return and reason code in the appropriate IBM Information Management Family documentation and proceed accordingly.

B1EI203E

INFO/MAN API SERVER NOT ACTIVE

Reason:

The CA Endevor SCM InfoMan Interface server is not active.

Action:

Contact the Info/Man Administrator.

B1EI204E

INFO/MAN API SERVER TRANSACTION transaction number FAILED, RC=return code (HEX), REASON=reason code (HEX)

Reason:

The specified CA Endevor SCM InfoMan Interface server transaction failed.

Action:

Look up the specified transaction number, return code and reason code in the appropriate IBM Information Management Family documentation and proceed accordingly.

B1EI205E

INFO/MAN API SERVER INITIALIZATION OR TRANSACTION FAILURE

Reason:

The CA Endevor SCM InfoMan Interface server could not be started.

Action:

Contact your Info/Man System Administrator (check SYSLOG for possible Info/Man-related error messages).