Operating System - OpenVMS
1752525 Members
4715 Online
108788 Solutions
New Discussion юеВ

Re: Problem while copying thro tcpip

 
RAJESH.J
Occasional Contributor

Problem while copying thro tcpip

Dear all,

When i copy a file thro TCPIP i get the following error message.

Command:

copy/ftp yyyy.txt Nodename"username password "::Dka100:[test]

Error:

%DCL-I-IGNQUAL, qualifiers appearing before this item were ignored
\FTP\
A Phase 1 Integration compliant OpenVMS TCP/IP product has not been
installed or properly configured on this system.
%SYSTEM-E-UNSUPPORTED, unsupported operation or function


Kindly reply me ASAP

With regards
Rajesh.J
11 REPLIES 11
Richard Whalen
Honored Contributor

Re: Problem while copying thro tcpip

What TCP/IP stack are you using?
Do the following logicals exist:
OPENVMS$FTP, OPENVMS$FTPDEL, OPENVMS$FTPDIR
labadie_1
Honored Contributor

Re: Problem while copying thro tcpip

Hello

If you do
$ ftp nodename /user=username/pass=password
put yyyy.txt

Does it work ? Or do you get an error message ?
RAJESH.J
Occasional Contributor

Re: Problem while copying thro tcpip


labadie,

I have executed the command there is no issues. It copies to another node without any exception.

Command:
$ ftp nodename /user=username/pass=password
put yyyy.txt

please reply if any ting else.....

regards
Rajesh
Hein van den Heuvel
Honored Contributor

Re: Problem while copying thro tcpip

Is 'copy' per chance defined as a symbol?
Exectue $ SHOW SYMB COP*

But that's just your first problem...

Hein.


$ copy/ftp x y
Cannot use COPY/FTP for local copies.
$ copy:=copy/log
$ copy/ftp x y
%DCL-I-IGNQUAL, qualifiers appearing before this item were ignored
\FTP\
Cannot use COPY/FTP for local copies.


Brian Reiter
Valued Contributor

Re: Problem while copying thro tcpip

Annoyingly the /FTP qualifier has to be the first qualifier on the command line, so it looks as though Hein was right and your COPY symbol has been redefined.

COPY/FTP/LOG is fine
COPY/LOG/FTP is not

Funnily enough, in the HELP, the /FTP qualifier is listed in HELP COPY, but isn't when you do HELP COPY QUALIFIER.
mike wagner_4
Occasional Advisor

Re: Problem while copying thro tcpip

What do you expect VMS should print?

>>> %DCL-I-IGNQUAL, qualifiers appearing before this item were ignored
\FTP\

DCL tells you that it happily will try a copy/ftp, but it also tells you that it sees other qualifiers before the /ftp, which DCL will ignore based on the CLD which defines the copy/ftp (as a new syntax, which doesn't know of the qualifier which came before the /ftp). As other pointed out, there is very likely a symbol for copy defined and the definition contains another qualifier.

Then DCL tries, but fails due to

>>> A Phase 1 Integration compliant OpenVMS TCP/IP product has not been
installed or properly configured on this system.
%SYSTEM-E-UNSUPPORTED, unsupported operation or function.

The first reply here asked the question: is there a compliant OpenVMS TCP/IP product on your system? Using the FTP utility doesn't show if there is such a compliant product installed. It only shows that there is an FTP utility and that it does what you expect it to do.

So, what else should VMS tell you to understand and resolve the copy problem?

mw
YJTAN
Occasional Advisor

Re: Problem while copying thro tcpip

Hi,

I have the similar problem on FTP, on only one of our nodes.

********************************************

The node with the problem:

CSP101$ dir/ftp csp101"system password"::welcome.txt
A Phase 1 Integration compliant OpenVMS TCP/IP product has not been
installed or properly configured on this system.
%SYSTEM-E-UNSUPPORTED, unsupported operation or function
CSP101$

********************************************
The node without problem :

CSP001$ dir/ftp csp101"system password"::welcome.txt

Directory CSP101"system password"::

SYS$COMMON:[SYSMGR]WELCOME.TXT;1

********************************************

COPY/FTP has the same problem. However, manual FTP is fine. I could do PUT or GET and other commands without any problem.

OpenVMS version 8.3
Steven Schweda
Honored Contributor

Re: Problem while copying thro tcpip

> I have the similar problem [...]

You're allowed to start a new thread for your
new, similar, problem, and cite the old
thread for reference.

Did you read the old thread?

> Is 'copy' per chance defined as a symbol?
> Exectue $ SHOW SYMB COP*

Did you try:

SHOW SYMBOL DIR*

???

And, if not, why not?


> [...] on only one of our nodes.

Different [SY]LOGIN.COM files, I'd guess.
Hoff
Honored Contributor

Re: Problem while copying thro tcpip

These two cases are similar in that both are involving ftp. Beyond that, these two cases are quite different. As a typical and general practice here in ITRC, start a new thread and reference the old thread as needed. In particular, you have no control and no management over a thread you've borrowed.

The following command and error sequence indicates that the TCP/IP stack installed is not compatible with OpenVMS V6.2 or later, or not installed correctly, or not configured and started correctly.

[[[CSP101$ dir/ftp csp101"system password"::welcome.txt
A Phase 1 Integration compliant OpenVMS TCP/IP product has not been
installed or properly configured on this system.
%SYSTEM-E-UNSUPPORTED, unsupported operation or function
CSP101$]]]

Loosely translated, tjat means DCL can't connect to the local ftp client, or that the local ftp client is incompatible with the DCL interface into ftp.

What to do here? First, please identify and confirm the IP stack and its version and ECO level, as a start. Please also confirm the OpenVMS versions and current ECOs on both platforms; either OpenVMS Alpha or OpenVMS I64 V8.3 is reported on one node; please confirm that the other node involved is also using OpenVMS Alpha V8.3 or OpenVMS I64 V8.3. There are various ECOs for both OpenVMS Alpha and for OpenVMS I64, and the various IP stacks can also have ECOs.

Ensure that the ftp client has been configured. If this is TCP/IP Services, a failure to configure the ftp client can sometimes almost work.

Do also ensure that the IP stack has been started, and that the system and IP startup are not logging relevant errors.