IC91464: STRUCT ERROR ON MISMATCHED DATA AND MAP WITH TRAILING SPACES

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • It looks like the problem is caused by the newline character in
    the data, after "5005" is being included in the string that is
    then used as part of the look up in the XREF table.
    
    
    appbuf.str:856   80004909  5005:str:856   80004909  5005
    :  <- notice the ':' is on the next line
    
    This is caused by the input file Document Header record not
    being as long as the DDF definition, or at least as long as the
    Application TP Rules definition for the field.
    
    The current field is only 4 characters long, 5 if you count the
    '0x0a' newline character.
    
    ##VISHATFIELD5005                    856   PRODCAMCAR
                           2614
    80004909                                5005
    
    If you pad the first line to a length greater than that
    specified by the Application TP Rules, 24 in this case, the TP
    record is found, as seen below.  I got a No Cfg error, but that
    is expected in this case.
    
    appm:21286:03072013:105008:  0:Began appm/EDI856QAD:
    appm:21286:03072013:105008:  0:No Document Specifier Table for
    TP VIS8562S225005, 111; tp_code = VIS8562S225005:
    appm:21286:03072013:105008:  0:Document reference number not
    created:
    appm:21286:03072013:105008:  2:no cfg: tp=VIS8562S225005,
    name=appm, mod=:
    appm:21286:03072013:105008:  0:Ended appm/EDI856QAD:
            ok=0
            no tp=0
            no cfg=1
            duplicate=0
            struct error=0
            routing error=0
            app file error=0:
    

Local fix

Problem summary

  • Users Affected:
    Customers with Trading Partner Cross Reference configurations
    that contain fields in the application data records that contain
    fewer characters than specified, as the field size, and
    terminated with a newline within the field size bounary.
    
    Problem Description:
    Trading Partner not found in application data manager, due to
    the newline being included in the comparison data.
    

Problem conclusion

  • Resolution Summary:
    Truncate comparison string to remove newline characters when
    building Cross Reference string for Trading Partner lookup.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC91464

  • Reported component name

    STR GENTRAN UNI

  • Reported component ID

    5725D0902

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-04-10

  • Closed date

    2013-04-12

  • Last modified date

    2013-04-12

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    STR GENTRAN UNI

  • Fixed component ID

    5725D0902

Applicable component levels

  • R610 PSY

       UP

  • R620 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Sterling Gentran:Server for UNIX

Software version:

6.1

Reference #:

IC91464

Modified date:

2013-04-12

Translate my page

Machine Translation

Content navigation