In our case the VSAM file is ESDS, not KSDS, and therefore is not "naturally sorted".
It is ESDS because its updated through CICS. ________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Bill Woodger <[email protected]> Sent: Wednesday, August 31, 2016 11:29 AM To: [email protected] Subject: Re: DFSORT mixed VSAM & sequential. SyncSort allows use of SORTINnn DDs, so a VSAM dataset can have its own DD. There aren't many places you can naturally concatenate VSAM. It is not DFSORT preventing it. Using a different key for the VSAM data? Otherwise it is already sorted anyway. REPRO you may find substantially more efficient at reading a KSDS. Although all the extra typing for another step may seem inefficient, give it a go (SORT a KSDS on a different key vs. REPRO and SORT). ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
