Operating System - OpenVMS
1829664 Members
17407 Online
109992 Solutions
New Discussion

Re: %RMS-F-LNE, logical name translation error

 
Bob Forsythe
Occasional Contributor

%RMS-F-LNE, logical name translation error

I am getting this error in a dcl script on a system running VMS 7.1-2. I also have this script running on a VMS 7.1-3 with no errors. I not sure if it's sysgen param set to low on the 7.3-1 system or not. Any information will be greatly appreciated
3 REPLIES 3
Volker Halle
Honored Contributor

Re: %RMS-F-LNE, logical name translation error

Bob,

please have a look at $ HELP/MESS LNE and try to check for the possible reasons given for this error.

This is more likely a logical name definition problem on your V7.1-2 system than a system parameter problem.

Volker.
Jeff Chisholm
Valued Contributor

Re: %RMS-F-LNE, logical name translation error

Bob,
There are typically a pair of errors, with %RMS-F-LNE being the second of these. What is the other error? What are you trying to do with logical names? Do you have multiple nested levels or a search list logical involved? Simpler is often better.

Turn on verify ($ SET VER) as the first line in your procedure. This will give you some clues about what the problem might be.
/jeff
le plus ca change...
Hein van den Heuvel
Honored Contributor

Re: %RMS-F-LNE, logical name translation error


Yeah, the HELP/MESS LNE is pretty explicit about the places to look.


My notes suggest this message used to be more restrictive/explicit:
%RMS-F-LNE, LOGICAL NAME TRANSLATION COUNT EXCEEDED


Tyipcally you get this from doing odd things like $ DEFINE FOO FOO
which results in endless translations. Also there are variants such
as $ DEFINE FOO BAR $ DEFINE BAR FOO.

If you know the name being translated, just $ SHOW LOGICAL
and you should see a long list of translations.


Are you using your own logical name tables with ACL's perhaps?

Also... you are not per chance using logical names with node"username password":: are you???
If the actual password is 'password' that is not going to work and will give this error.

This is because RMS does some logical name magic replacing the real password with the string 'password' in order to avoid showing the actual password.

And there might just be a version dependend change in this space around V7.1
Try some DIR node"user pass"::login.com on the various systems and see if they all react the same or not.

fwiw,
Hein.