Joined: 15 Feb 2005 Posts: 7129 Location: San Jose, CA
Well, you didn't say what your data looks like in those 48 characters, but I can take an educated guess at what you're talking about.
Do you mean your 48 characters can have numeric values that can't be distinguished from blanks or special characters? For example:
X'00127C'
is a PD value of +00127, but since you have 7C40 in your ALTSEQ statement, it would be changed to:
X'001240'
If that's the case, how would you possibly expect DFSORT to know which bytes contain blanks or special characters, and which bytes are part of numeric fields? You would have to have some way of distinguishing the two (for example, some pattern that indicates a value is numeric) and let DFSORT know about it before DFSORT could know what to do. Do you have some way of distinguishing the two? If so, what is it?
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
Hello,
As Frank mentioned - you haven't posted what is in those 48 bytes.
Using browse/edit with HEX ON, copy/paste and the "Code" tag to post the contents of a few of the 48-byte values. Explain what needs to be coverted and what needs to remain unchanged and the rules for knowing wh8ich is which.
Joined: 17 Oct 2008 Posts: 4 Location: Auburn Hills, MI
Hi All,
Here is a sample input and output:
Input ->
Code:
20080118Chrysler 300
20080905 Jeep-Commander
20080923 Jeep_Commander
20080912 Jeep Grand/Cherokee
20080606 Chrysler Town & Country
20080905 Chrysler Town & Country
Joined: 15 Feb 2005 Posts: 7129 Location: San Jose, CA
The control statements you showed would NOT do that. Things do NOT fit together here. All of your ALTSEQ pairs change something to a blank, yet you show the output as having something changed to a non-blank. It just doesn't make any sense.
When I ran your control statements against that data starting in position 1508 with DFSORT, I got the following output data starting in position 1508:
please please, refrain from using attachments, not everybody can see/download them
reducing the number of people who can help
also, please do not post screenshot images
You are just causing lots of network traffic without any added value
You can get the same result with a text cut and paste ...
for the info You posted ( 4 screen of usable info )
You could have used 24*80*4 bytes instead of 384 Kbytes
also You are not using DFSORT,
the WER prefixed messages show that You are using SYNCSORT
the fact that You are invoking ICEMAN does not mean that You are using DFSORT
I' ll just move the whole thread/topic were it belongs ( the JCL forum )
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
Hello,
Where did you get the hex values you posted in the "flat-hex" format? Is there some reason you did not post the hex for the same records you posted when you presented the problem?
Those values would not be presented as your "bad" values are
Please re-post some input, the output from that input, and the HEX ON for the exact same input . . .