Re: Passing a packed field into a command string

On Oct 11, 2017, at 4:15 PM, Barbara Morris <bmorris@xxxxxxxxxx> wrote:

On 2017-10-11 2:22 PM, Brian Johnson wrote:

I don't see why not. For example (assuming CCSID 37) for a
packed(3:0) with value 146 you would have x'146F', right? Viewed as
characters that would be an SO and '?'.
On Wed, Oct 11, 2017 at 11:02 AM, Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:

Given that SO (X'14') and SI (X'15') can't occur in a packed number, the technique I described of using a DS to "convert" packed to character would appear to be a valid approach. But as you note it wouldn't work for an integer.

Jon is right that the SO/SI isn't an issue for packed, he just gave the wrong hex values for them. Actually, SO is x'0E' (decimal 14) and SI is x'0F' (decimal 15).

x'0E' could theoretically occur at the end of a packed number, but only if the preferred signs of x'D' and x'F' weren't being used. I don't think that applies here.

x'0F' could reasonably occur at the end of a packed number, but I believe it's only interpreted as SI if the SO (x'0E') preceded it in the string.

--
Barbara

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD