Directory name fetching logged in Users' name as default

[Swain]

Hi,

I am logged in with user UTIL
When I change directory to AMS$COM: on server, It's redirecting me to AMS$COM:[UTIL]

$ set def ams$com:
$ dir
%DIRECT-E-OPENIN, error opening AMS$COM:[UTIL]*.*;* as input
-RMS-F-DEV, error in device name or inappropriate device type for operation
$ sh def
AMS$COM:[UTIL]
%DCL-I-INVDEF, AMS$COM:[UTIL] does not exist

I tried
$ help/message dev /facil=rms
but didn't find any appropriate solution. I have to run a command procedure from UTIL user which invokes AMS$COM:TRANSMIT.COM and it searches for AMS$COM:[UTIL]TRANSMIT.COM which fails.

Please help!!

Thanks,
Amaresh

[Duncan Morris]

Amaresh,

this suggests that your logical name AMS$COM either does not exist, or is inappropriately defined.

do

$ show logical/full ams$com

and post the results.

Duncan

[Joseph Huber_1]

Show us the translation of the logical AMS$COM :
It seems it translates into a device or a concealed device, therefore the set default adds the current directory.

You need somehow to learm which directory on device AMS$COM: contains transmit.com.

[Swain]

$ sh log/full ams$com
%SHOW-S-NOTRAN, no translation for logical name AMS$COM

But I am getting reply from AMS prompt

AMS$W sh log/full ams$com
"AMS$COM" [super] = "AMS$CODE:[COM]" (LNM$PROCESS_TABLE)

Do I need to add the same entry to system table?

Thanks,
Amaresh

[The Brit]

Amaresh,

The earlier response is likely correct, i.e. that the logical is a "concealed" or 'rooted' logical.

It also looks like the logical name does not exist until the AMS(?) startup/setup executes, and then it is defined as a process logical. It may not be appropriate to define it system wide.

Instead of typing

"$ set def ams$com:",

try

"$ set def ams$com:[000000]"

Dave.

[Swain]

Brit,
Since this is used in script, I have to replace all entries for AMS$COM: by AMS$COM:[000000]

Is there any other way?

Thanks

[Joseph Huber_1]

>> AMS$CODE:[COM]" (LNM$PROCESS_TABLE)
This means: it is a directory, but know only to the user cited.
If You want to use it from other users (like SYSTEM), then You have to define it /GROUP or /SYSTEM as appropriate.

And no, the logical is not a concealed devicfe, so
@AMS$COM:transmit is correct.

[Hein van den Heuvel]

>> Since this is used in script, I have to replace all entries for AMS$COM: by AMS$COM:[000000]

No you don't. Even if AMS$COM was a rooted diretory, and that might make it work, it would still not be what was intended. For properly used rooted directories the root itself is only used to hold directories, not files.

But in your case the root is not AMS$COM, but
rather AMS$CODE.
The definition for that appears to be missing.
It is not unlikely supposed to be a system logical.
Try to figure out where/how AMS$CODE is supposed to be defined!


>> But I am getting reply from AMS prompt

Besides suggestion a certain unfamiliarity with OpenVMS that comment suggests that somewhere along the line a 'change environment 'script was used. That could be hidden as a command: "ams" or be something like @SET_ENV_AMS. You should figure out what steps take you to the AMS prompt, and then dive in to see what it (tries to) does.

[Swain]

Exactly, Joseph!

another error I am finding while transmiting reports is:

-RMS-E-CRE, ACP file create failed
-SYSTEM-F-INVLOGIN, login information invalid at remote node
%COPY-W-NOTCOPIED, DKC500:[TRANSFER.DEFAULT.AMSXFER.RTF]WAT$T0810001.RTF;1 not copied

This error came while running the script from SYSTEM user.

[Joseph Huber_1]

Look in the script where a COPY file remote_node::disk:[dir] is done.
Either the username/password combination (if explicit) is wrong, or it uses a proxy (node"user"::) account, but the proxy (on the remote node!) is missing, invalid (node name changed ?).
Since this was apparently working for the user AMS (?), and not with Your (or SYSTEM), I suppose it is a proxy problem.