Add a TYPE=V parameter to the JOINKEYS statement for the VSAM file. It might also need a RECFM=V on the SORTJNFx DD for the VSAM file. Alan -----Original Message----- From: IBM Mainframe Discussion List Sent: Jun 6, 2022 6:07 PM To: Subject: SYNCSORT question: How to treat variable length KSDS as variable length input to SORT JOINKEYS I have two files, one a flat file with RECFM=VB,LRECL=8004, one a VSAM KSDS with RECORDSIZE(3000 26000) denoting variable length records for that KSDS. However, when using that VSAM file as one side of a JOINKEYS operation, SYNCSORT claims the KSDS is RECFM=F: WER482I JNF2 STATISTICS WER483B 32,780K BYTES OF VIRTUAL STORAGE AVAILABLE, MAX REQUESTED, WER483B 0 BYTES RESERVE REQUESTED, 996K BYTES USED WER108I IN2 : RECFM=F ; LRECL= 26000; CISIZE = 28672 Listcat of the VSAM file shows it is, in fact, defined as variable: ATTRIBUTES KEYLEN----------------15 AVGLRECL------------3000 BUFSPACE-----------61440 CISIZE-------------28672 RKP--------------------1 MAXLRECL-----------26000 EXCPEXIT----------(NULL) CI/CA-----------------26 STRIPE-COUNT-----------1 ACT-DIC-TOKEN----X'40000009054005FE08FE0DFE0EFE0AFE0000000000000000000000000000000000000000' SHROPTNS(2,3) SPEED UNIQUE NOERASE INDEXED NOWRITECHK UNORDERED REUSE NONSPANNED COMP-FORMT EXTENDED EXT-ADDR How do I get SYNCSORT to recognize and treat this variable-length KSDS as variable, just like the flat file which is my other JOINKEYS input? Copying the VSAM to a flat RECFM=VB isn't a currently viable alternative due to large file size and limited "test" disk space. Besides, I ought to be able to process a variable length file as a variable length file no matter what the actual file organization may be. Peter 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 [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
