On Mon, 4 Jan 2021 16:32:47 +0100, Massimo Biancucci wrote: > >I've tried to use sort to help. > >// EXPORT SYMLIST=* >// SET INPMOD=oldmd >// SET OUTMOD=newmod >// SET INPLIB=myold.lib >// SET OUTLIB=mynew.lib > I like that sort of parameterizing. It puts the variables up front, viewable at a glance. I'd add the AMBLIST2 DSNs to the SET list.
Can something such as "SET DISP={PASS|CATLG} be used to control temp vs. permanent workfiles? >//* * >//*-------------------------------------------------------------------* >//ST010 EXEC PGM=IDCAMS >//SYSPRINT DD SYSOUT=* >//SYSIN DD *,SYMBOLS=(JCLONLY,SYMBLOG) > DELETE &SYSUID..AMBLIST2 > IF MAXCC=8 THEN SET MAXCC=0 >/* >//*-------------------------------------------------------------------* >//* * >//*-------------------------------------------------------------------* >//ST020 EXEC PGM=AMBLIST >//SYSPRINT DD DSN=&SYSUID..AMBLIST2,DISP=(,CATLG), >// SPACE=(TRK,(5,5),RLSE) >//LOADLIB DD DISP=SHR,DSN=&INPLIB >//SYSIN DD *,SYMBOLS=(JCLONLY,SYMBLOG) > LISTIDR DDN=LOADLIB,MEMBER=&INPMOD >/* ... My very peculiar preference is to omit the IDCAMS steps and code either: //HANDLE DD DSN=&SYSUID..AMBLIST2,DISP=(MOD,CATLG), // SPACE=(TRK,(5,5),RLSE) //SYSPRINT DD DISP=OLD,DSN=*.HANDLE,VOL=REF=*.HANDLE Or: //HANDLE DD DSN=&SYSUID..AMBLIST2,DISP=(MOD,DELETE), // SPACE=(TRK,(5,5),RLSE) //SYSPRINT DD DSN=&SYSUID..AMBLIST2,DISP=(MOD,CATLG), // SPACE=(TRK,(5,5),RLSE) But, performance? Is a failing IDCAMS step less overhead than an otiose DISP=(MOD,DELETE) etc.? >I used "no-temp" dataset to better help in understanding the process. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN