[EMAIL PROTECTED] wrote Fri, 30 Jun 2000:
I have been experiencing outrageous email trouble. Please forgive
duplicate messages - this is a modification of another message that
you may or may not have seen already.
> My Perl is not built to pre-load the ENV array.
>
> The logicals that are set up are defined in a startup procedure. The same
> procedure is called from both the functioning and the non functioning node
> in my cluster.
I think this may be the root of the problem. In your initial report perlbug
mentioned that:
> perl_root:[lib.VMS_AXP.5_00503]
> perl_root:[lib]
> perl_root:[lib.site_perl.VMS_AXP]
> perl_root:[lib.site_perl]
> PERLSHR=PERL_ROOT:[000000]PERLSHR.EXE
> PERL_ROOT=DISK104:[PERL5_005_03.]
^^^^^^^^
Is DISK104 the Volume label rather than the physical name?
What is the physical name of the disk as seen by other cluster
members? Is it $1$DKA100:? What does:
directory perl_root:[000000]perl.exe
do on _all_ of your nodes? I presume it will work OK on your
"functioning" node, but do you see any "%DIRECT-W-NOFILES, no files found"
on the other nodes? If so then try replacing the definition of
PERL_ROOT in your perl_setup.com with something like the following,
with perl_disk symbols suitably to resemble your physical disk names:
$ nodename = f$getsyi("NODENAME")
$ if nodename .eqs. "SEB090" then perl_disk := $1$DKB100:[perl5_005_03.]
$ if nodename .eqs. "SEB100" then perl_disk := $1$DKA100:[perl5_005_03.]
$ define/translation=concealed PERL_ROOT 'perl_disk
etcetera.
Peter Prymmer
