On Tue, 7 Jan 2014 06:09:37 -0800, Juan Mautalen  wrote:
�
Example:
If the job runs today, january 7 of 2014, it must create�the member�F140106 ( 
and not F140107). That is because the job processes information from the day 
before (and not from the day it is indeed running).
�
Is there a way to achieve this purely from JCL? we have z/OS 1.13.
� 
z/OS 2.1 will remove some silly antiquated restrictions concerning use of
system symbols in batch JCL.  But I doubt even that will support your
need for "day before" and a specific member name format.  So,
how about:

o INCLUDE from JCLLIB a member containing a SET statement with
  the desired member name.

o Add a final step to your job to update that JCLLIB member to
  the current date in preparation for running the job the next day.

Beware the restart concerns mentioned elsewhere in this thread --
this technique will yield undesired results if the job is run twice
in the same day.

Are there any ENQ concerns with a job's updating its own JCLLIB?

-- gil

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to