SORT provides a rich control card language for record selection and rejection and other "data processing" operations that I don't have to program. Having the capabilities of that language between the E15 and E35 exits allows me to take advantage of those rich capabilities without having to program them myself. As it stands, I have to perform a useless SORT operation in order to use both exits, and be careful in specifying the SORT key that I don't disturb the original order of the records in so doing. BTW, MODS-type E15 and E35 exits for a JCL-invoked SORT do NOT need to do their own I/O. SORT passes the records it reads from SORTIN to the E15 exit to manipulate and the "sorted" or "merged" records to the E35 exit to manipulate. This lets me take advantage of SORT's superior (i.e., faster) I/O facilities. Both exits use the "REPLACE" record function to return the manipulated records to SORT.
In my particular case the exits allow me to decode RECFM=VB records stored on disk in an application-specific scheme on the way in through the E15 exit, yielding a fixed-length record easily processed with SORT capabilities, and to re-code processed records using that application-specific scheme on the way out in the E35 exit. No COBOL I/O involved. Peter > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On > Behalf Of Charles Mills > Sent: Tuesday, March 29, 2011 6:21 PM > To: IBM-MAIN@bama.ua.edu > Subject: Re: Why does SORT forbid E15+E35 in COBOL for OPTION COPY? > > As I think about this -- am I missing something? > > I don't know much about the z sort programs but does a COPY function do > what I would guess it does -- copy from the input to the output? > > Now you propose doing your own input and output? While you're at it, why > not just tie one to the other -- could it be much more work than writing > the exits themselves? -- and skip the sort program altogether? > > Or does SORT have some "data processing" options that you are going to use > to massage the data during the copy? > > Charles > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On > Behalf Of Farley, Peter x23353 > Sent: Tuesday, March 29, 2011 8:51 AM > To: IBM-MAIN@bama.ua.edu > Subject: Why does SORT forbid E15+E35 in COBOL for OPTION COPY? > > I have a fairly simple application requirement to be able to use BOTH an > E15 and an E35 exit in an OPTION COPY execution of SORT, but this is > specifically disallowed (generates RC=16 message ICE161A from DFSORT and > WER102A from SYNCSORT). > > If I use a MERGE FIELDS=(p,l,f,A) on a known ascending field (and the > EQUALS option just for insurance that the record order is not disturbed) > and use SORTIN01 for the input instead of SORTIN, it works just fine > with both exits in COBOL. > > Can Mr. Yeager or some other SORT knowledgeable soul explain to me why > this simple and straightforward use of SORT exits in a COPY operation is > specifically forbidden? It simply makes no sense to me whatsoever. -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
