When I "production-ized" SCRT, I created the following JCL stream in my production job.
//JS0010 EXEC PGM=LOADER //SYSLOUT DD SYSOUT=* //SMF DD DSN=SYS2.SMF.WEEK.ALLSYS.TYPE7089(-4),DISP=SHR // DD DSN=SYS2.SMF.WEEK.ALLSYS.TYPE7089(-3),DISP=SHR // DD DSN=SYS2.SMF.WEEK.ALLSYS.TYPE7089(-2),DISP=SHR // DD DSN=SYS2.SMF.WEEK.ALLSYS.TYPE7089(-1),DISP=SHR // DD DSN=SYS2.SMF.WEEK.ALLSYS.TYPE7089(0),DISP=SHR // DD DSN=SYS2.SMF.DAY.ALLSYS.TYPE7089,DISP=SHR //SYSPRINT DD DISP=(,CATLG),DSN=SYS2.SCRT.SYSPRINT, // SPACE=(TRK,(1,1)),UNIT=SYSDA //OUTPUT DD DISP=(,CATLG),DSN=SYS2.SCRT.REPORT, // SPACE=(TRK,(15,15,15)),UNIT=SYSDA //PARMS DD DSN=SYS2.SCRT.PDS(PARMS),DISP=SHR //NO89 DD DSN=SYS2.SCRT.PDS(NO89),DISP=SHR //SYSLIN DD DSN=SYS2.SCRT.PDS(PROGRAM),DISP=SHR I extract all of the 'in stream' elements from the SCRT download into a PDS with three members (PARMS, NO89 and PROGRAM). This way, my production JCL never (or hardly ever) changes, while I can replace the SCRT code and parms for each SCRT release as needed. The next step in this job uses XMITIP to automatically email me the SCRT spreadsheets the above JCL generated. No muss, no fuss. Works every month, automatically. Perhaps something like this would assist you. If it was me, I wouldn't bother waiting for SCRT support to change their object deck for compatability with your scheduling software.... Brian On Wed, 4 Jun 2008 17:16:13 -0500, Hal Merritt wrote: >Is anyone besides us using the ESP scheduler and doing sub capacity >billing? > >The latest version of the load and go module appears to be triggering >ESP's rather powerful symbol substitution engine and is going bonkers. > > Anyone else seen that, and, if so, what did you do about it? > >I have a query into the SCRT folks. > >Thanks!! ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
