Check first 57 ne Space and next 57 bytes Eq Space
Second input file
check opposite of previous check
Third file
Add SAVE before build in your outfil
Bill Woodger wrote:
You are using one byte at position 60 in the REFORMAT record to decide on file 1/2, and you are using a particular value for that position.
If you have an unmatched file 1, then the whole 1,57 for file two will be space (or binary zeros, or whatever, depending on your installation).
If you have unmatched file 2, then the whole 1,57 for file one will be, as above.
If you have a match, both 1,57s will have data.
If you have a particular byte which cannot contain the FILL value used for unmatched records on the JOINKEYS then you can test that byte. At worst you can test the whole record as Pandora-box has already suggested.
There are examples in the JCL forum. Search for JOINKEYS and FILL.
bhavin.mehta,
Nobody is 'backfiring' you. But, the previous posts implied what you mentioned in your post. So as Bill mentioned you didn't test (possibly) for FILL character in Syncsort.
Joined: 05 Jan 2007 Posts: 101 Location: chennai (India)
Quote:
As per my experience in SYNCSORT I don't think you can get all the 3 outputs using 1 Sortcard. You will have to use 3 Sortcards (i.e. you will require 3 steps) 1 for each file.
