On Tue, Sep 2, 2014 at 9:09 AM, John Gilmore <[email protected]> wrote: > This message is less informative that it should be. > > The value +32767 is of course the [decimal] capacity of a signed > binary halfword, and what we notionally have here is an instance of > control-block field overflow; but I suspect that this message is an > artefact of the use of IEFBR14---As Elardus has already pointed out, > it does nothing itself and wots not of VSAM---to trigger the deletion > of a VSAM dataset identified in a JCL DD statement. > > Use IDCAMS instead! > > John Gilmore, Ashland, MA 01721 - USA >
I can only think of two reason people still use IEFBR14 in this manner. The first is that it predates the existence of IDCAMS. And so "inertia" has set in. The other reason is that by being in JCL, the DSN, or portion, can be a symbolic parameter. We use something like this in our JCL procedures so that a single PROC can be used for Test, Model Office, or Production just by something like: //JS010 EXEC PROC=PRODPROC,NODE=T (or M or P). And then have: //SOMEDD DD DISP=SHR,DSN=aaa&NODE..REST.OF.NAME This can be emulated, with difficulty, with a PROC similar to //DELIT PROC NODE=T //DELIT EXEC PGM=IKJEFT01, // PARM='DEL aaa&NODE..REST.OF.NAME' //SYSTSPRT DD SYSOUT=Z //SYSTSIN DD DUMMY // PEND But we've gotten even lazier. We just use a CA-11 step in _all_ (even programmers submitted) jobs as the first step. That lets _it_ find and delete all DISP=NEW datasets referenced in the JCL. -- There is nothing more pleasant than traveling and meeting new people! Genghis Khan Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
