Greg Saccomanno wrote on 03/15/2007 06:42:22 PM:
Would DFSORT at release 1.4 (z/OS 1.4 and I think OS/390 2.10) using
EQUALS=VBLKSET produce the same results run after run if the input data
were the same but produce different results when run under DFSORT 1.5
(All
jobs ran with EQUALS=N)? I know what EQUALS= does, it's just that the
results between two parallel runs always matched even back to os/390 2.10
and now they do not and the difference is in the sequence of duplicate
records.
If the answer to the above is YES, is there some way to get 1.5 to
produce
the same results as I used to get under 1.4 (I don't know if the
duplicate
records were in input order or not under 1.4 so I don't know that
EQUALS=YES would get me what I want, just that the two executions would
always match before)?
The shipped default is EQUALS=VLBLKSET for both DFSORT 1.4 and 1.5. This
only guarantees that the first duplicate will be kept for VLR Blockset
applications. For all other applications, the default is EQUALS=NO which
means that any record from a set of duplicates can be selected. Which
record is selected with EQUALS=NO depends on different factors like the
technique selected, how storage is laid out, etc. So with EQUALS=NO, you
might get the same duplicates run after run or you might not, even for the
same release. The only way to ensure that you always get the same
duplicates for every run and every release is to use EQUALS=YES. There's no
way to guarantee that you'll get the same results with 1.5 that you got
with 1.4 without having used EQUALS=YES for both.
Frank Yaeger - DFSORT Team (IBM) - [EMAIL PROTECTED]
Specialties: PARSE, JFY, SQZ, ICETOOL, IFTHEN, OVERLAY, Symbols, Migration
= DFSORT/MVS is on the Web at http://www.ibm.com/storage/dfsort/
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
