I found the answer something like 15 minutes after I posted my
requests, buried in a mail message from two years ago. Coincidentally, the
message was in response to the same problem I reported locally back then.
As those of you who run PMDF under VMS probably know, PMDF typically
runs under the SYSTEM account. A couple years ago, and apparently again back
on 1-MAR of this year, a subsystem identifier was granted to the SYSTEM
account here. Perl (or at the least the version we're running) sees this as a
"tainting" of the process, and skips copying the environment, so resources
like symbols aren't available. (FWIW, I forgot to mention on the VMSPERL list
that PERL_ENV_TABLES is, in fact, defined as CLISYM_LOCAL.) I ended up making
the same accommodation for this change in system context today as was done
two years ago, and everything's peachy. It's a quick little hack in the code
run by the PMDF conversion queue that merely uses "SET RIGHTS/DISABLE
<id-name>" for the subsystem identifier(s) in question. (The PMDF conversion
queue doesn't need these.) I wasn't seeing the problem when I tested the
code interactively, since I don't typically use the SYSTEM account.
Cheers,
Mike
--
| Systems Specialist: CBE,MSE
Michael T. Davis (Mike) | Departmental Networking/Computing
http://www.ecr6.ohio-state.edu/~davism/ | The Ohio State University
| 197 Watts, (614) 292-6928
