On Sun, 3 Apr 2016 20:29:09 -0500, Barry Merrill wrote: >Using IBM FTP CS V2R1, the uploaded INFILE's excess space is not RLSE'd. > >//FTPUP EXEC PGM=FTP,PARM='(EXIT=4' >//SYSPRINT DD SYSOUT=*,DCB=BLKSIZE=133 >//SYSABEND DD SYSOUT=* >//SYSOUT DD SYSOUT=* >//FTPOUT DD SYSOUT=* >//INFILE DD DSN=MXGLRG.CICS.UNTERSE,DISP=(NEW,CATLG,CATLG), >// UNIT=(3390,1),DSNTYPE=LARGE, >// DSORG=PS,RECFM=FB,LRECL=1024,BLKSIZE=6144, >// SPACE=(CYL,(500,500),RLSE) >//SYSIN DD * >99.99.99.99 >USERID PASSWORDPHRASE >BINARY >GET CICS2.terse + > 'MXGLRG.CICS.UNTERSE' (replace >CLOSE >QUIT
RLSE is not an attribute that stays with the data set. AFAIK, it only applies to the access with that DD statement. If you were to run a step like this: //COPY EXEC PGM=IEBGENER //SYSPRINT DD SYSOUT=* //ALLOC DD DISP=(NEW,CTLG),DSN=SOME.DATA.SET, // SPACE=(TRK,(20,20),RLSE) //SYSUT1 DD * record 1 record 2 //SYSUT2 DD DISP=OLD,DSN=SOME.DATA.SET I think that you would find that the excess space for SOME.DATA.SET is not released because the data is not written using the DD statement that has RLSE specified. Likewise, FTP isn't using the INFILE DD statement. This is only a guess, based upon my understanding of how RLSE works. I could be wrong. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
