Re: Q: Can anyone explain this cursious behaviour.

If you don't run the perl startup script, PERLLIB is undefined.   That's 
basically the guts of PERL.  The PERL.EXE tries to load it using
the logical and fails.

Are you running the startup you should?

-- Alan


'On 7/14/2014 6:10 AM, [email protected] wrote:
> Hi,
>
> we came across this curious behaviour. Here enclosed please find a
> reproducer.
>
>
> When running the enclosed perl script without any logical definitions we
> get the message:
> $ perl x.pl
> Why do I get %SYSTEM-F-NOLOGNAM? at x.pl line 5.
> %SYSTEM-F-NOLOGNAM, no logical name match
>
> When we define a logical name X we get:
> $ def/user X Y
> $ perl x.pl
> Y
> Why do I get %SYSTEM-F-NOLOGNAM? at x.pl line 5.
> %SYSTEM-F-ABORT, abort
> $
>
> $ perl -v
>
> This is perl 5, version 20, subversion 0 (v5.20.0) built for VMS_IA64
>
>
> Kind regards
> John
>
> PS. Why can't a PRODUCT INSTALL of PERL leave an older installation
> alone (ie. do not start deleting files in the directory tree), or at
> least offer an OPTION to leave the old installation as is?
>
>