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.

Alan Wyman
Programming Manager - Information Systems
Alliant Foodservice - Minneapolis
2864 Eagandale Boulevard
Eagan, MN 55121
(651) 683-4253
(651) 683-4438 fax
e-mail: [log in to unmask] <mailto:[log in to unmask]>

        -----Original Message-----
        From:   Stan Sieler [SMTP:[log in to unmask]]
        Sent:   Thursday, December 07, 2000 7:32 PM
        To:     [log in to unmask]
        Subject:        Re: [HP3000-L] jobq - user job queues

        Re:
        > > :SETVAR HPJOBQ JINFO("#J!HPJOBNUM","JOBQ")
        >
        > You might want not want to prefix your own variable with "HP"
        > since CSY might later invent a new predefined variable with the
        > same name (like we did with HPLASTJOB which broke a few of my
        > own scripts).

        Which is why I suggested, years ago, that the CI reject any
        user attempt to create a variable with the prefix "HP"!

        First, it would prevent mistakes like:

           setvar hptypahead true         (missing "e")

        Second, it would prevent problems from simple-minded software doing
        things like:

           if hp...... exists, then we're on 5.0 or later

        Third, it prevents problems like Jeff described!


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