Update element error SMGR160E "INVALID SOURCE RECORD LENGTH"

Products

• Endevor

Issue/Introduction

Endevor update element fails with SMGR160E error:

*****
           11:54:19  C1Y0015I  STARTING PARSE OF REQUEST CARDS

            STATEMENT #1
            SET STOPRC 16 .

            STATEMENT #2
            UPDATE ELEMENT 'ELEM1'
              FROM DSNAME 'TEST.WORK.TYPE1'
              TO   ENVIRONMENT 'DEV' SYSTEM 'SYS1' SUBSYSTEM 'SYS1'
                TYPE 'TYPE1'
              OPTIONS CCID '1234' COMMENTS "testing" OVERRIDE SIGNOUT
             .

            STATEMENT #3
            EOF STATEMENT GENERATED
           11:54:19  C1Y0016I  REQUEST CARDS SUCCESSFULLY PARSED
...

           11:54:19  C1G0202I  ACTION #1 / STMT #2
           11:54:19  C1G0203I     UPDATE   ELEMENT ELEM1
           11:54:19  C1G0205I        FROM DSNAME:  TEST.WORK.TYPE1
           11:54:19  C1G0204I        TO   ENVIRONMENT: DEV     SYSTEM: SYS1
           11:54:19  C1G0232I        OPTIONS:  OVERRIDE SIGNOUT
           11:54:19  C1G0232I                  CCID: 1234
           11:54:19  C1G0232I                  COMMENT: testing
           11:54:20  C1G0265I  PROCESSOR GROUP COBDB2B FOR THIS ELEMENT WAS OBTA
           11:54:20  SMGR160E  INVALID SOURCE RECORD LENGTH - 00259 EXCEEDS MAXI
           11:54:20  C1G0277I  UPDATE PROCESSING TERMINATED BECAUSE OF THE PREVI
           11:54:20  C1G0200I  ELEMENT ACTION REQUEST PROCESSING COMPLETED, HIGH
                     END OF EXECUTION LOG - HIGHEST ENDEVOR RC = 0012
*****

Also encounter similar problem trying to add an element.

Environment

Endevor
Any Release

Cause

The output is truncated and per doc page for SMGR160E the full message should have this format:
*****
SMGR160E
INVALID SOURCE RECORD LENGTH - length EXCEEDS MAXIMUM RECORD LENGTH FOR TYPE - length
Reason:
The record length of the source exceeds the maximum record length allowed for this type.

Action:
Classify the source under a type that allows the requisite record length.
*****

Therefore the SMGR160E message is due to the input data in member ELEM1 from dataset TEST.WORK.TYPE1 having a record that is longer than the maximum record length allowed by the type definition TYPE1.

Resolution

Check the following:

1. If the input dataset TEST.WORK.TYPE1 has RECFM=V or VB, then check the member ELEM1 for any records with spurious trailing blanks that are taking the record length beyond the type TYPE1 maximum record length. Remove those trailing blanks to try to resolve the problem.
   
   
2. If the input dataset TEST.WORK.TYPE1 has RECFM=F or FB, then all records have the same length so the problem is dataset itself exceeding the maximum record length of type TYPE1.