

Procedure Modules › Converting Packed Decimal to Binary (CULLUS33) › Helpful Hints
Helpful Hints
- A binary output field can also be created with the FB format code placed on a type 5 parameter.
- Inaccurate specification of the input field length produces unpredictable binary results.
- High order bytes are truncated if the size of the receiving field is too small.
- If CULLUS33 is invoked to create the RDW for variable-length output records, the receiving field should be defined as alphanumeric. If the result is placed in a binary field, CA Culprit attempts to output the number in zoned decimal format.
Example
This example shows the CA Culprit parameters required to convert a packed decimal input field to binary output.
The following code:
Copyright © 2014 CA.
All rights reserved.
 
|
|