How about using an IF statement to check the current time (HPTIMEF)against
some time prior to 12:00 AM - such as, 11:59 PM.  PAUSE x seconds to make
sure the clock progresses past midnight and then reference the HP date
variables.

Steven P. Barrett             |
Network Manager               |  Voice:  1-703-222-3132
Fairfax County Public Library |    FAX:  1-703-222-3135
Technical Operations Center   | e-mail:  [log in to unmask]

--- The opinions expressed here are mine alone. ---


-----Original Message-----
From: Rick Clark [mailto:[log in to unmask]]
Sent: Monday, November 29, 1999 1:19 PM
To: [log in to unmask]
Subject: Re: dates and CI vars


Good point. This would be true if the job was scheduled to run late at
night. Since we run it early in the evening it is not a concern for us.

Rick

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
Behalf Of VANCE,JEFF (HP-Cupertino,ex1)
Sent: Monday, November 29, 1999 12:45 PM
To: [log in to unmask]
Subject: Re: dates and CI vars


FWIW, the below scheme for creating a month-day-year date has at least
one risk: the HPDATE value could change after the HPMONTH value was
referenced.  Or, the HPYEAR value could change after HPDATE was
referenced, depending on exactly when this job was executing.
On 6.0 systems you can use the new predefined CI variable HPYYYYMMDD
which is guaranteed to not have these month/year boundary problems.
Alternatively, you can check your resulting date after it is
constructed, e.g.:
   setvar month HPMONTH
   setvar date HPDATE
   setvar year HPYYYY
   setvar curr_day "!month/!date/!year"
   if year <> HPYEAR or month <> HPMONTH then
      # year or month boundary -- recompute curr_day
      setvar curr_day "!hpmonth/!hpdate/!hpyyyy"
   endif

...
> JCL WWA:SETVAR CURR_DAY "!HPMONTH"+"/"+"!HPDATE"+"/"+"!HPYEAR"

regards,
Jeff Vance, CSY