On Thu, 3 Mar 2022 00:34:24 +0000, Sri h Kolusu wrote: > >You can schedule a job that runs SDSF in batch and then extracts the contents. >I assumed that your systems have SYSSYM=ALLOW so that you can save the >results using the date and time. >Something like this > >// EXPORT SYMLIST=* >// SET CDATE=Y&LYR4..M&LMON..D&LDAY >// SET CTIME=H&LHR..M&LMIN..S&LSEC >/* ... SYSINI DD * generated here?? >//SORTOUT DD DSN=&SYSUID..CPU.&CDATE..&CTIME, >// DISP=(NEW,CATLG,DELETE), >// SPACE=(CYL,(1,1),RLSE) > There are recurrent discussions here of the difficulty of embedding DATE.TIME in a data set name because the initiator must issue ENQs before the first EXEC. Are the symbols above resolved by the converter or the scheduler, avoiding this problem?
Also, is there a hazard that if the job runs at midnight (or any lesser boundary) the date may be obtained before midnight; the time the next day, resulting in a DATE.TIME almost 24 hours too small? Rexx handles this right. I suspect that JCL does not. <https://www.ibm.com/docs/en/zos/2.5.0?topic=functions-date> -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
