FTP error messages

[tim lloyd_1]

Hi, I am maintaining a legacy system using VMS pascal. Recently there was a problem with FTP - trying to copy files from one node to another node running the same software.

Basically we are trying to shift user information from the node on which the user signs on to all other active nodes. So, it is something which is used frequenty during the day.

Ripping through the code I see a couple of status checks which are lightly documented (ie. not documented). I can't find this on the net anywhere so can anyone shed light on what status these codes refer to:

X1001828A I think this is just a VMS error code when opening a file
X17649B11 this is after a copy/ftp command

thanks

[Steven Schweda · Accepted solution]

As usual, some description of the system, its
software, and the commands used might be more
helpful than vague ramblings and
interpretations. As a start:

tcpip show version

Around here:

ALP $ write sys$output f$message( %X1001828A)
%RMS-E-FLK, file currently locked by another user

ALP $ write sys$output f$message( %X17649B11)
%TCPIP-S-FTP_NORMAL, normal successful completion

[Hoff]

$ x=f$message(%x1001828A)
$ sho sym x
X = "%RMS-E-FLK, file currently locked by another user"
$ set mess sys$message:TCPIP$MSG.EXE
$ x=f$message(%x17649B11)
$ sho sym x
X = "%TCPIP-S-FTP_NORMAL, normal successful completion"
$

[RBrown_1]

$ HELP/MESSAGE/STATUS=%X1001828A

gives you good information.

The other status is a success status. My usual tricks for finding out what it means have not been fruitful.

[tim lloyd_1]

thanks all. That answers my question. I'll close this later

[Steven Schweda]

> [...] My usual tricks for finding out what
> it means have not been fruitful.

And they were?

> $ set mess sys$message:TCPIP$MSG.EXE

The trick is knowing which is the magic file
in SYS$MESSAGE. I have a DCL procedure to
try them all until it gets something better
than "NOMSG". (I probably used it recently
to check on an FTP status of my own, which is
most likely why I didn't need an explicit SET
MESSAGE of my own to get what I got above.)

[RBrown_1]

>>>> From Steven:
> [...] My usual tricks for finding out what
> it means have not been fruitful.

And they were?

> $ set mess sys$message:TCPIP$MSG.EXE

The trick is knowing which is the magic file
in SYS$MESSAGE. I have a DCL procedure to
try them all until it gets something better
than "NOMSG".
<<<<

I have the same command file. It did not find anything because TCPIP$MSG does not exist on my system.