Yes that works for fixed length but not variable length which is possible for packed decimal with bigEndian.


Regards,

Bradd Kadlecik
z/TPF Development

Phone: 1-845-433-1573
E-mail:
braddk@us.ibm.com
2455 South Rd
Poughkeepsie, NY 12601-5400
United States


Inactive hide details for Mike Beckerle ---04/14/2020 03:56:45 PM---Not sure I understand the mixture of the concepts of justifMike Beckerle ---04/14/2020 03:56:45 PM---Not sure I understand the mixture of the concepts of justification and packed decimal here.

From: Mike Beckerle <mbeckerle.dfdl@gmail.com>
To: Bradd Kadlecik <braddk@us.ibm.com>, DFDL-WG <dfdl-wg@ogf.org>
Date: 04/14/2020 03:56 PM
Subject: [EXTERNAL] Re: [DFDL-WG] Behavior of nilKind literalValue with respect to binaryNumberRep of packed






Not sure I understand the mixture of the concepts of justification and packed decimal here.

I usually think of packed decimal as fixed length and without padding.

Let me assume this example: 12345C is value 12345, 00000C is zero, and 00000F is the nil indicator.

So, bigEndian byte order, I think dfdl:nilvalue="%#r00;%#r00;%#r0F;" is what I'd expect to see for a literalValue nilValue to match that.
 
I'm guessing some assumption in the above doesn't match your use case, so please correct.

Mike Beckerle | OGF DFDL Workgroup Co-Chair | Owl Cyber Defense | www.owlcyberdefense.com
Please note: Contributions to the DFDL Workgroup's email discussions are subject to the OGF Intellectual Property Policy



On Tue, Apr 14, 2020 at 2:59 PM Bradd Kadlecik <braddk@us.ibm.com> wrote:
Regards,

Bradd Kadlecik

z/TPF Development

Phone: 1-845-433-1573
E-mail:
braddk@us.ibm.com
2455 South Rd
Poughkeepsie, NY 12601-5400
United States