Alan writes:
> 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.

yes you would....by *correctly* using a new variable:

   my_yyyymmdd

e.g.,:

    continue
    setvar my_yyyymmdd hpyyyymmdd
    if it failed then
       setvar my_yyyymmdd some other method
       endif

    ...
    use my_yyyymmdd in some manner

We're not stopping you!

However, if you use your own HPYYYYMMDD, you open yourself up to
various problems:

   - you might have the wrong data in it

   - another programmer could see the usage and (incorrectly) say
     "oh, I've got that variable on this release...great...let's
     use it everywhere" ... not understanding that it took special
     care to setup a fake HP variable!

Yes...it's *easy* to use your own HPYYYYMMDD ... but discipline
pays off.   It's like the rule against putting your own programs
or command files in PUB.SYS ... it's *easy* to put files there,
but the discipline of doing things correctly pays off (e.g., using
UDCs or HPPATH).  (Heck, I'm still learning this truism myself,
over and over!)


Stan Sieler                                           [log in to unmask]
www.allegro.com/sieler/wanted/index.html          www.allegro.com/sieler