Skip to content
CA Endevor® SCM - 18.0
Documentation powered by DocOps

Message and Code Reference

Last update May 7, 2018

Use this page to search for messages that CA Endevor SCM generates. These messages describe normal processing, warning situations, and error conditions that might occur. 

Messages and codes display in the upper right corner of the terminal screen, in accordance with TSO/ISPF message conventions. To display the one-line expanded message on your screen, press the Help key (F1). 

Note: To browse all CA Endevor SCM messages or download a PDF or EPUB file, go to CA Endevor SCM - Messages v17 and v18.

Search Tips

  • To search for a message that includes a colon, enclose the search string in quotes. For example: "C1BM4100:E066"
  • A wildcard, asterisk (*), can be used within, or at the end of, a search value. For example: EN*E or ENB*


Message Formats

Messages are formatted to indicate the product function that produced the message, a message number, and severity level.

Messages appear in one of the following formats.

Format 1:

Prefix -- message number -- suffix

All messages use this format, except for C1BM and C1BR messages.

  • The prefix indicates a three- or four-letter product function.
  • The message numbers are three or four digits.
  • The suffix indicates a severity level.

The following examples illustrate this format:

Prefix Message Number Suffix Example
abc nnnn x API0000E
abcd nnn x ENBE002I 

Format 2:

Prefix -- module number -- suffix

The prefix is C1BM for the SCL parser, or C1BR for the reporting utilities.

  • The module number identifies the CA Endevor SCM utility that produces the message.
  • The suffix includes a severity level and message number.

The following examples illustrate this format:

Prefix Module Number Suffix Example
C1BM mmmm :xnnn C1BM4100:E066
C1BR mmmm :xnnn C1BR3040:W001

Message Codes

CA Endevor SCM issues the C1EI messages. These messages use the following codes when describing corrective actions:

  • A
    Retry the action after increasing the region size. If the retry does not work, proceed according to the other suggestions for corrective action.
  • B
    Provide the full message text and return codes.
  • C
    Provide a SYSM or SYSABEND dump.
  • D
    Provide the concatenation for the PIDT table.
  • E
    Provide the data set attributes.
  • F
    Provide the JES job log and all output listings.
  • G
    Send the script that is used as input to the batch utility.

Severity Levels

Severity levels correspond to product return codes. Messages are issued with the following severity levels:

  • I
    This letter indicates an informational message. The process concluded normal, the message is for information purposes only.
    Return Code:                00
  • W 
    This letter indicates a warning message. An error was encountered which was not serious enough to terminate processing.
    Return Code:                04
  • C
    This letter indicates a caution message. An error was encountered which prevents further processing.
    Return Code:                08
  • E
    This letter indicates an error message. An error was encountered which terminated processing of a current action. The error allowed CA Endevor SCM to continue with the next action request.
    Return Code:                12
  • S
    This letter indicates that a severe error was encountered which prevented CA Endevor SCM from completing the requested action. Processing terminates immediately. This category includes internal, System, and I/O errors.
    Return Code:                16
  • F 
    This letter indicates a fatal error. The reporting job terminates.
    Return Code:                20 

Abend, Return and Reason Codes

For Abend code, see 0047 Abend Code.

For API Return and Reason codes, see API Return and Reason Codes.

For Codes that result from Source Sync Checks, see Source Sync Check Return and Reason Codes.

Was this helpful?

Please log in to post comments.

  1. RICHARD ROZENTALS
    2016-08-29 11:08

    Hi, This method of error messages is not searchable within GOOGLE. If a customer looks for a message, for example c1u0000e. The v17 message shows up when they search in google. The v18 version of the message is not found. Going forward this would be a problem.

    1. MARGARET ALLEN
      2016-11-15 07:12

      Hi Richard,

      Now, there is only one wiki space for both v17 and v18 messages. This change was made after you entered your comment here. The message descriptions are valid for both v17 and v18, unless stated otherwise when you look at the message description. Previously, there was a wiki space for the v17 messages and a separate wiki space for the v18 messages, which was unnecessary and led to confusion. Even with this change, when you search for a message using a browser search engine (for example, Google) you can also find the message in the v16 bookshelf on support, so the viewer always to look to see what source the the search result is accessing. If I've misunderstood and this doesn't answer your question, please let me know. Thanks.

  2. Patricia Gabriela Simon
    2017-08-01 02:16

    quiero hacer un browse desde el panel de display element y me da el error "SOURCE MANAGEMENT", F1: BASE FILE CONTAINS TOO MANY DATA RECORDS ... a que se debe solo me pasa en laboratorio

    1. MARGARET ALLEN
      2017-08-01 05:53

      Hi Patricia,

      I located the following message description. Does this answer your question? If not, please contact CA Support at https://support.ca.com

      SMGR042E
      BASE FILE CONTAINS TOO MANY DATA RECORDS

      Reason:
      CA Endevor SCM has encountered more lines than it expected in the file.
      Action:
      If the error is associated with the Element, delete the Element and restore it from a prior unload tape or archive file.
      If the error is associated with the component list, use the DELETE action with only component option to delete the component list base and delta, and regenerate the Element to recreate the component list.

  3. Bernie Beriau
    2017-11-15 08:30

    The following messages are not in the doc and there are no diagnostic suggestions: ***
    *** USED IN: C1GSEXTI, END-TO-END USS LOGGING ONLY
    ***
    CONMSGN TYPE=MSG,MSID=C1E0146I,TSTAMP=YES, X MSG='THE END-2-END LOGGING PATH WAS NOT FOUND, LOGGING SX KIPPED.'

         CONMSGN TYPE=MSG,MSID=C1E0147I,TSTAMP=YES,                    X
               MSG='ERROR OPENING THE END-2-END LOGGING OUTPUT FILE, LOX
               GGING SKIPPED.'                                          
    
         CONMSGN TYPE=MSG,MSID=C1E0148I,TSTAMP=YES,                    X
               MSG='ERROR WRITING TO THE END-2-END LOGGING FILE, LOGGINX
               G SKIPPED.'                                              
    
         CONMSGN TYPE=MSG,MSID=C1E0149I,TSTAMP=YES,                    X
               MSG='ERROR CLOSING THE END-2-END LOGGING OUTPUT FILE.'   
    

    1. MARGARET ALLEN
      2017-11-16 09:12

      Hi Bernie, I am working with Fred to get these doc'ed. Thanks for bringing this to our attention.