Greg asks:
> > In our HP3000 S918 we have HP variable YYYYMMDD availabe,
> > [yet at] my customer site (same machine and OS)
> > they are missing that HP variable.....

Wirt suggests:
> The HPYYYYMMDD variable wasn't introduced until relatively
> recently, either
> at 6.0 or 6.5.

Greg clarifies:
> I am sorry for not being clear... Both machines are on MPE/iX 6.0.....

but I noticed a particular detail: Greg calls it "[an] HP variable [called]
YYYYMMDD", while Wirt refers to it as "HPYYYYMMDD".  If Greg's original
question wasn't an oversite in specifying the name, we're talking about two
different variables: HPYYYYMMDD vs. YYYYMMDD.  Greg, is it possible that on
your machine, buried in some startup script (do you have MPEX or
Security/3000?) you are "setting and forgetting" the variable directly?

The reason I mention VEsoft's products is that MPEX looks so much like the
normal MPE/iX environment that many people simply forget they are "in" that
shell.  If so, remember that MPEX has a file called MPEXMGR, that if it
exists, it will execute upon starting MPEX.  MPEX looks for this file in
your group, the pub group of your account, and finally in PUB.SYS, executing
any and all it finds.

Likewise, Security/3000 has a provision for specifying commands at startup,
i.e., $LOGON-EXECUTE.  At one site, we had this looking for and executing
the file "LOGON[.PUB[.SYS]]" of which the PUB.SYS version set certain
variables our applications expected to exist.  (essentially "naming" the
system as "A", "B", "C", or "D"; this was in the classic days when you
couldn't set a system name as easily as you can now...)

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *