At 6:56 AM -0700 12/11/00, Wyman, Alan wrote:
>Another problem this could cause is for sites with multiple machines on
>different patch levels.  I just had a contractor code a program using the
>HPYYYYMMDD variable.  This was made available in a 6.0 powerpatch.  The
>contractor checked the two local machines and they had it.  We installed on
>a remote machine that hadn't been patched (long story there) and the program
>failed.  My workaround was to make my own HPYYYYMMDD variable in the
>jobstream that executes the program.  I wouldn't have been able to do that
>with the restriction in place.


A possible solution to that problem is to do something like

  if bound(HPYYYYMMDD)
     setvar MY_yyyymmdd HPYYYYMMDD
  else
     setvar MY_yyyymmdd "!HPYYYY" + &
                        rht("0"+"!HPMONTH",2) + &
                        rht("0"+"!HPDAY",2)
  endif

Then use MY_yyyymmdd throughout your job instead of HPYYYYMMDD. That way,
your job will work whether or not you're on a level of the OS that has the
HPYYYYMMDD variable.


Barry Lake                              [log in to unmask]
Allegro Consultants, Inc.               www.bogus.allegro.com
(408)252-2330
--------
Attempting to reduce spam influx.
Remove ".bogus" to create valid address.