Discussion List On Behalf Of
Massimo Biancucci
Sent: Wednesday, March 31, 2021 12:58 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Syncsort merge question - How to report exact keys out of sequence?
Peter,
I don't know if you need a "general" solution or a way to diagnose the specific
problem
Peter,
another way is to run a "DUMMY" JOIN of SORTIN02 with itself specifying
SORTED.
The result will be something like:
WER485A F2 OUT OF SEQUENCE, RECORD NUMBER = n
Remember to avoid coding OMIT/INCLUDE using JNFxCNTL because this way SS
won't give you the record number (eventually
Peter,
I don't know if you need a "general" solution or a way to diagnose the
specific problem.
WER068A tells you that the out of sequence record is on SORTIN02 (first
tip) and specifically on block 56,917 (second tip).
Depending on the block size of your file you could "point to the block" and
"To a man with a hammer, everything looks like a nail." I'd write a REXX
for it.
---
Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313
/* There are some days when it takes all you've got to keep up with the
losers. */
-Original Message-
From: IBM Mainframe Discussion List On
I have the following situation which causes me to get an "out of sequence"
error for a merge operation.
Three input files, all RECFM=VB, all the same LRECL and BLKSIZE. Files 2 and 3
are frequently (but NOT always) empty except for header and trailer records. I
believe that the DATA records
