File not found failure on ftp

[Wim Van den Wyngaert]

Make that ucx show version.

Wim

[Steven Schweda]

TCPIP SHOW VERSION works if you have a recent
version of the DEC/Compaq/HP product, but
there are others. For older versions of the
same product, you could also try:

UCX SHOW VERSION

When that fails, you might try some commands
like:
SHOW LOGICAL *TCP*
SHOW LOGICAL *MULTINET*
SHOW LOGICAL *TWG*
and so on, and look for any suspicious hits.
Be creative, if necessary.

[Jan van den Ende]

Alex,


because we need the files to be in fixed length format, but as far as we are aware, when transferred using ftp, the files are in stream format and therefore variable length. I could not see any way around this, hence the DCL scripts. Can anyone confirm this limitation (ie. variable length on ftp send to VAX) ?


Yeah,
welcome to the wonderful cripple shortsighted Unix world :-(

This is an precisely defined behavior of FTP, inherited from its U*X basiscs:
_ALL_ files are _ALWAYS_ and _ONLY_ stream_lf.

Some OSses have special extensions (I know about VMS, might well also exist for IBM) that, IF the connection is setup between 2 VMS systems, using the same TCP stack, it can be specified to use extra functions, and retain (or actually: restore) the file structure.
I definitely do NOT expect such to exist between two different non-UX OSses.

So, what remains is what you have already got: add the knowledge yourself into the script, and reconstruct things.

Sorry, no better news.

Proost.

Have one on me.

jpe

[Joseph Huber_1]

If the file is fixed-length records , then You could transfer in FTP BINARY mode, and it will be FIXED-512 on the receiving VMS side, and You would just have to set the record length correctly (set file/attr=(lrl:n)) instead of converting.

Second, the script can test if the file exists by
f$search(file), and if the result is empty string, jump to error exit:
if f$search(file).eqs."" then goto not_found.

The question as to why the file doesn't (or not yet) exist after "successfull" FTP :could it be for some reason the FTP server on the VMS side has not yet finished, i.e. not yet closed the file ? Check it next time on the VMS side: do a "show system" and see if an ftp server process is still there.

[Alex Tough]

Joseph
Sorry, i should have made this clearer. We cannot use binary mode because we have to convert from EBCDIC (IBM mainframe code tables) to ASCII, so binary is not an option.
regards, Alex