> On Oct 21, 2019, at 2:49 AM, Jouk Jansen <jo...@hrem.nano.tudelft.nl> wrote: > > I noticed problems with Perl, when JAVA80 is configured. I tracked down the > problem to some decc$xxxx logicals, which are defined by the java setup.
Yes, I ran into this when the first HPE/VSI Java kit came out. > Maybe it is a good idea to define the required logicals inside the perl.exe. > An example how to do this can be found (i.e.) in the sources of bzip2 > (http://antinode.info/dec/sw/bzip2.html) (see file vms_misc.c) > > What do you think of this idea? Perl already has a lib$initialize set-up and does enable the things that it needs: <https://github.com/Perl/perl5/blob/blead/vms/vms.c#L13835> (Yes, we moved to GitHub recently). I guess we could also make Perl disable things that are enabled by the Java command procedures and break Perl. This seems backwards to me and it is really Java that should enable what it needs at run time rather than requiring anyone who has Java installed to take evasive action. If I remember correctly, Java set-up actually does DEFINE/SYSTEM so ordinary users can't even deassign the problem logicals but have to override by assigning different values. Thanks for the suggestion. I'd be happy to hear what others think. I was hoping HPE/VSI would fix Java, but at this point there will likely never be another truly new Java kit on Itanium, even if there is a minor update to the current one. ________________________________________ Craig A. Berry "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser
