Ambiguity with HEXSIGN field storage length

Converts cobol copybooks to Xml/Java objects

Status: Beta

Brought to you by: bruce_a_martin, ptrthomas

Ambiguity with HEXSIGN field storage length

Forum: Open Discussion

Creator: Sumeru Saha

Created: 2014-05-23

Updated: 2014-05-23

Sumeru Saha - 2014-05-23

I have a copybook with hexsign fields like "09 O-HGSTE-JR-INLG-BEDR PIC S9(18) HEXSIGN", for this the xml configuration generated is like ... below

<item display-length="22" level="09" name="O-HGSTE-JR-INLG-BEDR" numeric="true" picture="S9(18)HEXSIGN" position="875" signed="true" storage-length="22" />

Can anyone explain why Storage Length is 4 more than what it is mentioned in PIC phrase, which in this case is S9(18)?

This is causing problems with parsing as the actual message has only 18 chars for this field

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jean-Francois Gagnon - 2014-05-23

CB2XML needs to be updated to accept HEXSIGN. It is not currently supported.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.