Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
 
Can we write a job so as to attach a date to a file name?

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> Mainframe Interview Questions
View previous topic :: :: View next topic  
Author Message
garuabhash

New User


Joined: 02 Nov 2005
Posts: 12
Location: Delhi

PostPosted: Wed Jan 10, 2007 5:52 pm    Post subject: Can we write a job so as to attach a date to a file name?
Reply with quote

Need your help for the following issue:

Can we write a job so as to attach a date to a file name? For example, suppose file name is AAA.BBB.CCC and it gets generated everyday so can we name the file as AAA.BBB.CCC.DDMMYY so that DDMMYY will change according to run date?

I tried by passing a PARM, but am not being sure where to put values for the PARM, or how the JCL can pick up the current date.

See below the JCL and PROC that I had written:

JCL:
Code:
     
//MYLIBS JCLLIB ORDER=(APG.INFY.DATE.PARM)             
//STEP1   EXEC DATEPARM,DATE='CYYMMDD'


PROC:
Code:

//DATEPARM  EXEC  PGM=SYNCSORT,PARM='CENTWIN=1995'     
//SORTIN    DD  DSN=APG.INFY.DATE.PARM.INPUT,         
//          DISP=SHR                                   
//*                                                   
//SORTOUT   DD  DSN=APG.INFY.DATE.PARM.&DATE,         
//            DISP=(,CATLG),UNIT=DISK,                 
//            SPACE=(CYL,(4,3),RLSE),                 
//            DCB=(RECFM=FB,LRECL=80,BLKSIZE=0)       
//SYSIN     DD  DSN=APG.INFY.DATE.PARM(SYSIN),DISP=SHR
//SYSPRINT DD SYSOUT=*                                 


The file that I am getting is APG.INFY.DATE.PARM.CYYMMDD and not APG.INFY.DATE.PARM.C070108 as intended.

Abhash
Back to top
View user's profile Send private message

superk

Moderator Team Head


Joined: 26 Apr 2004
Posts: 4650
Location: Raleigh, NC, USA

PostPosted: Wed Jan 10, 2007 6:57 pm    Post subject: Re: Can we write a job so as to attach a date to a file name
Reply with quote

Abhash, think about what you're doing for a moment.

When a job is submitted, before it ever executes on the JES Internal Reader, any variables you specify must be resolved into their designated values. This means that the values any variables you use MUST be known to the job BEFORE it is ever allowed to start execution.

In your case, you assigned the value 'CYYMMDD' to the variable 'DATE', so that is its value. You need to assign the actual value, i.e. 'DATE='C070110' before the job is submitted. One easy way to do this is with the SET statement, such as this:

Code:

//  JCLLIB ORDER=(APG.INFY.DATE.PARM)             
//  SET DATE='C070110'
//STEP1   EXEC DATEPARM


or by using an INCLUDE statement:

Code:

PDS 'MY.PROD.PARMLIB' member 'CURRDATE' contains one record with the value:
// SET DATE='C070110'

//  JCLLIB ORDER=(APG.INFY.DATE.PARM,MY.PROD.PARMLIB)             
//  INCLUDE CURRDATE
//STEP1   EXEC DATEPARM


You can use the EZACFSM1 System Symbolic Variable Resolution utility to output the current system date to an output DD:

Code:

//JOB1 JOB ...
//  JCLLIB ORDER=(APG.INFY.DATE.PARM) 
//STEP1 EXEC PGM=EZACFSM1 
//SYSIN  DD *,DLM=@@       
//JOB2 JOB ...
//  JCLLIB ORDER=(APG.INFY.DATE.PARM) 
//STEP1   EXEC DATEPARM,DATE='C&LYYMMDD'
@@   
//SYSOUT DD   SYSOUT=(*,INTRDR)
//*


or, handle the dataset allocation dynamically within a program, or use system variables provided by your job scheduling system, etc.
Back to top
View user's profile Send private message
superk

Moderator Team Head


Joined: 26 Apr 2004
Posts: 4650
Location: Raleigh, NC, USA

PostPosted: Wed Jan 10, 2007 7:00 pm    Post subject: Re: Can we write a job so as to attach a date to a file name
Reply with quote

Here is just a short list of some of the ways to handle DATE/TIME in batch jobs:

Quote:

Enabling System Date and/or Time Stamps In JCL

Section 1. Using Job Schedulers

CA7 Example:

Say you want your JCL to look like this if todays date was 11/7/03:

//JOBCARD...
//STEP010 EXEC PGM=IEFBR14
//DD1 DD DSN=NODE1.NODE2.D110703,
// DISP=(NEW,CATLG, DELETE),
// etc....

Create a member in your CA7ONL //CARPROC DD, call it "CURRDATE". Copy in this information:

// DPROC MMDDYY
// DSET MMDDYY=MDY(&C_JDATE)
//DD1 DD DSN=NODE1.NODE2.D&MMDDYY,

Create your CA-7 JCL to look like this:
//JOBCARD...
//STEP010 EXEC PGM=IEFBR14
//D EXEC CURRDATE
// DISP=(NEW,CATLG, DELETE),
// etc....

In CA-7, do the "LJCK,LIST=ONLY,JOB=jobname" command to see what will be submitted to JES2


Section 2. Strictly JCL

Example 1. Using a PROCedure with variables.

//JOB123 JOB (accounting),CLASS=X,MSGCLASS=X
//*
//STEP1 EXEC MYPROC,SYSDATE=110703,SYSTIME=080000
//*

//MYPROC PROC SYSDATE=,SYSTIME=
//*
//PROC1 EXEC PGM=IEFBR14
//DD1 DD DSN=NODE1.NODE2.D&SYSDATE.T&SYSTIME,
// DISP=(NEW,CATLG, DELETE),
// etc....

Example 2. Using SET command to set JCL variables. The values for the SET statements must be defined prior to the job submission.

//JOB123 JOB (accounting),CLASS=X,MSGCLASS=X
//*
// SET SYSDATE=110703
// SET SYSTIME=080000
//*
//STEP1 EXEC PGM=IEFBR14
//DD1 DD DSN=NODE1.NODE2.D&SYSDATE.T&SYSTIME,
// DISP=(NEW,CATLG, DELETE),
// etc....

Example 3. Using SET/INCLUDE commands to set JCL variables in an external library.

Step 1. Application creates a member SETDATE in the library 'MYLIB.CNTL' with the following two records:

// SET SYSDATE=110703
// SET SYSTIME=080000

Step 2. Now, job can be submitted with an INCLUDE statement for the associated library.

//JOB123 JOB (accounting),CLASS=X,MSGCLASS=X
//*
// JCLLIB ORDER=(MYLIB.CNTL)
// INCLUDE MEMBER=SETDATE
//*
//STEP1 EXEC PGM=IEFBR14
//DD1 DD DSN=NODE1.NODE2.D&SYSDATE.T&SYSTIME,
// DISP=(NEW,CATLG, DELETE),
// etc....


Section 3. Using a program to create and submit the JCL.

/* REXX to capture the current date and save it in an INCLUDE group */
Drop jcl. /* clear STEM */
jcl.0 = 1 /* plug in record count. */
jcl.1 = "// SET DATE="D20||DATE('J') /* create SET statement */
jcl.1 = LEFT(jcl.1,80) /* Pad to 80 bytes, and */
"EXECIO 1 DISKW DATEDD (FINIS STEM jcl." /* Output to library */
Exit 0 /* quit with COND CODE = 0 */

Sample Job to capture the date

//LIST OUTPUT DEFAULT=YES,CLASS=*,JESDS=ALL
//S0010 EXEC PGM=IKJEFT01,PARM='SETDATE'
//SYSTSIN DD DUMMY
//SYSTSPRT DD SYSOUT=(,)
//SYSPRINT DD SYSOUT=(,)
//CEEDUMP DD SYSOUT=(,)
//SYSEXEC DD DSN=&SYSUID..REXX.EXEC,DISP=SHR
//DATEDD DD DSN=&SYSUID..JCL.CNTL(TODAY),DISP=SHR

Sample Job to include the Date.

// JCLLIB ORDER=(&SYSUID..JCL.CNTL)
// INCLUDE MEMBER=TODAY
// EXEC PGM=IEFBR14
//DDA DD DSN=&SYSUID..SEQ.&DATE,DISP=(,DELETE,DELETE),
// SPACE=(80,(100,100)),LRECL=80,RECFM=FB,BLKSIZE=0,
// AVGREC=K,UNIT=SYSDA

Time stamp method
This solution could be used when multiple versions of a data set are to be created through out the day, and both date and time are to form part of the data set name. It requires two steps, the first creates the data set, and the second renames the data set replacing a particular node with the date and time. The issue not dealt with directly here is one of co-ordination to ensure that two jobs do not attempt to create data sets with the same time stamp. If an installation runs with the standard JES2 default of NOT allowing concurrent execution of jobs with duplicate names, it provides some assistance.

Sample REXX Routine to rename the data set

/* REXX to rename a data set to include current date as part of the
data set name. */
Parse Arg odsn onode /* Obtain parameters
odsn = existing dsn
onode = date location */
tod = TIME('N') /* Get Time of Day */
Parse var tod hh ':' mm ':' ss /* Remove the semi-colons */
lnode = LENGTH(onode) /* Get length of node */
lodsn = LENGTH(odsn) /* Get length of dsname */
start = POS(onode,odsn) /* Find onode */
more = POS('.',odsn,start) /* Anything after onode */
ndsn = SUBSTR(odsn,1,start-1)||'D20'||DATE('J')||'.T'||hh||mm||ss
If more > 0 Then ndsn = ndsn||SUBSTR(odsn,more)
x = MSG('OFF') /* Suppress messages */
"RENAME '"odsn"' '"ndsn"' " /* Rename the data set */
If rc ?= 0 Then Do /* Check for success */
Say "Rename Error"
Exit rc
End
Exit 0 /* quit with COND CODE = 0 */

Sample Job using the above REXX routine.

//LIST OUTPUT DEFAULT=YES,CLASS=*,JESDS=ALL
// SET DATEF='OPSSTU1.TEST.FILE'
//S0010 EXEC PGM=IEFBR14
//DDA DD DSN=&DATEF,DISP=(,CATLG,DELETE),
// SPACE=(80,(100,100)),LRECL=80,RECFM=FB,BLKSIZE=0,
// AVGREC=K,UNIT=SYSDA
//S0020 EXEC PGM=IKJEFT01,
// PARM='SETDATE2 &DATEF TEST'
//SYSTSIN DD DUMMY
//SYSTSPRT DD SYSOUT=(,)
//SYSPRINT DD SYSOUT=(,)
//CEEDUMP DD SYSOUT=(,)
//SYSEXEC DD DSN=&SYSUID..REXX.EXEC,DISP=SHR

//*
/*JOBPARM ROOM=SOP,LINES=9999
//*
//STEP0001 EXEC PGM=IEFBR14
##DD1
// DISP=(,CATLG,DELETE),UNIT=SYSDA,SPACE=(CYL,(1,1)),
// RECFM=FB,LRECL=80
//*
//STEP0002 EXEC PGM=IEBGENER
//SYSUT1 DD DATA
TEST RECORD 01 OF 10
TEST RECORD 02 OF 10
TEST RECORD 03 OF 10
TEST RECORD 04 OF 10
TEST RECORD 05 OF 10
TEST RECORD 06 OF 10
TEST RECORD 07 OF 10
TEST RECORD 08 OF 10
TEST RECORD 09 OF 10
TEST RECORD 10 OF 10
/*
##SYSUT2
// DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//*

Next, I created the JCL that follows. I am using DFSORT to:

first, generate a sequential number for each record so that they can be kept in order.

then, I separate the JCL into two datasets - one with everything minus the ## records, and one with just the ## records, with the ## replaced by //, the data 'DD DSN=', and a dataset, with the SORT function DATE3 supplying the current Julian date.

lastly, the two sets of JCL are concatenated back together, using the sequence numbers to retain the proper order, with the resulting concatenated file going to the Internal Reader for submission. I'm sure it could use some tweaking here and there, but here goes nothing:

//*
//STEP0001 EXEC PGM=ICETOOL
//TOOLMSG DD SYSOUT=*
//DFSMSG DD SYSOUT=*
//IA DD DISP=SHR,DSN=TPPAT07.JCL(JCLDATEX)
//OA DD DSN=&&OA,DISP=(,PASS),UNIT=SYSDA,SPACE=(CYL,(1,1))
//IB DD DSN=*.OA,VOL=REF=*.OA,DISP=(OLD,PASS)
//OB DD DSN=&&OB,DISP=(,PASS),UNIT=SYSDA,SPACE=(CYL,(1,1))
//OC DD DSN=&&OC,DISP=(,PASS),UNIT=SYSDA,SPACE=(CYL,(1,1))
//IC DD DSN=*.OB,VOL=REF=*.OB,DISP=(OLD,PASS)
// DD DSN=*.OC,VOL=REF=*.OC,DISP=(OLD,PASS)
//OD DD SYSOUT=(*,INTRDR)
//*
//TOOLIN DD DATA
COPY FROM(IA) TO(OA) USING(CTLA)
COPY FROM(IB) TO(OB) USING(CTLB)
COPY FROM(IB) TO(OC) USING(CTLC)
SORT FROM(IC) TO(OD) USING(CTLD)
/*
//*
//CTLACNTL DD DATA
INREC FIELDS=(1,80,SEQNUM,6,ZD)
OUTREC FIELDS=(1:1,86)
/*
//*
//CTLBCNTL DD DATA
INCLUDE COND=(1,2,CH,NE,C'##')
/*
//*
//CTLCCNTL DD DATA
INCLUDE COND=(1,2,CH,EQ,C'##')
OUTREC FIELDS=(1:C'//',3:3,8,12:C'DD DSN=',
C'&SYSUID..DATA.#',DATE3,C',',81:81,6)
/*
//CTLDCNTL DD DATA
SORT FIELDS=(81,6,ZD,A)
OUTREC FIELDS=(1:1,80)
/*

Section 4. Using system variables in the JCL.

//STEP0001 EXEC PGM=EZACFSM1
//SYSIN DD DATA,DLM=@@
//MYJOB JOB (...),CLASS=X,MSGCLASS=X
//*
//STEP0001 EXEC PGM=IEFBR14
//FILE1 DD DSN=&SYSUID..CUST.AF.#&LYR2&LMON&LDAY..#000001.DAT,
// DISP=(MOD,DELETE,DELETE),UNIT=SYSDA,
// SPACE=(CYL,(0,0),RLSE)
//*
//STEP0002 EXEC PGM=ICEGENER
//SYSUT1 DD DUMMY
//SYSUT2 DD DSN=&SYSUID..CUST.AF.#&LYR2&LMON&LDAY..#000001.DAT,
// DISP=(,CATLG,DELETE),UNIT=SYSDA,
// SPACE=(CYL,(100,100),RLSE)
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
@@
//SYSOUT DD SYSOUT=(A,INTRDR)
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Thu Jan 11, 2007 8:16 am    Post subject:
Reply with quote

Hello,

A different approach might be to consider creating a generation data set. It would not have the current date in the dsn, but WOULD allow for multiple runs in the same day with no penalty.

Let's suppose "this" job runs every night at 21:30. Now let's suppose that something happens that it cannot run until 03:45 the next morning. By the time 21:30 comes around the next night, the file for that day will already exist and have to be dealt with.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> Mainframe Interview Questions All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts ISSUE IN copying Sequential file reco... thesumitk JCL & VSAM 2 Wed Dec 13, 2017 3:07 pm
No new posts File Tailoring -- Temporary dataset i... samzee71 CLIST & REXX 3 Fri Dec 01, 2017 3:12 am
No new posts Rexx - File tailoring samzee71 CLIST & REXX 10 Thu Nov 30, 2017 10:47 pm
No new posts Fetching data from JHS as per the cur... arunsoods All Other Mainframe Topics 4 Wed Nov 22, 2017 1:54 pm
No new posts Moving a PS file as body of a mail! Vignesh Sid JCL & VSAM 4 Tue Nov 21, 2017 9:23 pm

Facebook
Back to Top
 
Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us