Re: COPY bug with remote task as input.

From: Fred Zwarts (F.Zwarts_at_KVI.nl)
Date: 09/16/04


Date: Thu, 16 Sep 2004 10:18:56 +0200


"Hoff Hoffman" <hoff@hp.nospam> wrote in message news:pO_1d.10735$H85.1647@news.cpqcorp.net...
> In article <ci6f5r$nlo$1@info.service.rug.nl>, "Fred Zwarts" <F.Zwarts@KVI.nl> writes:
>
> Details on how to perform task-to-task without using the classic
> TYPE hackery are shown in the Ask The Wizard area, in topics such
> as (5409), (159) (798), and (1910).
>
> :We run OpenVMS Alpha 7.3-1 with DECnet IV.
> :On a remote (VAX-ELN) node we have a task running which provides data =
> :via DECnet.
> :On the OpenVMS system, we have a logical DAQ_DATA_UNI defined as =
> :KVIE11::"task=3DEVENTS_UNI".
> :The DUMP DAQ_DATA_UNI command shows the data as expected.
> :The CONVERT DAQ_DATA_UNI X.X command reads and writes the data as =
> :expected.
> :The TYPE DAQ_DATA_UNI command displays the data as expected.
> :
> :However, the COPY DAQ_DATA_UNI X.X command complains that it cannot open
> :the input file "DISK$1:[USER].".
>
> Exact error message, please?
>
> Is it:
>
> %COPY-E-OPENIN, error opening DISK$1:[USER].; as input
> -RMS-E-FNF, file not found

Indeed.

> :DISK$1:[USER] happens to be the default drectory of the user.
> :COPY /FTP has the same problem.
> :
> :I think this is a bug in the COPY command.
> :Or has somebody another idea?
>
> First, please show me the statement in the OpenVMS manuals or the
> SPD where this particular construction is supported or documented.
> (AFAIK, this is not a supported operation for COPY or COPY/FTP.)

Well, I cannot find it anymore in the VMS 7.3 documentation.
The documentation about DECnet seems to contain not everything that
was contained in older versions.
I still have the VMS 5.0 documentation set, from the time that this application
was developped.
In the System management Volume 5A Networking Networking manual, section 8.5.1
I read:

To perform transparent task-to-task operations, you can use DCL commands to
construct and execute command procedures.

Here in the same section also the TYPE command is shown as an example.
This section seems to imply that any command which accepts an input file
parameter can be used.
Nowhere I can find that COPY is an exception.

Where is this limitation of COPY documented?
As soon as it is documented, it is no longer a bug :)

> COPY must acquires transfer-related information and defaulting based
> on the input source. The other commands cited do not require that.

COPY works on all types of devices, not only on disks. So it seems that COPY
is capable to obtain this information.

You should at least admit that the error message is confusing.
If the reason is that COPY cannot perform the operation it should state that.
It should not talk about input files that it cannot find that have no relation
with the specified input file.

>
> :But it would be nice if this bug could be fixed.
>
> There are ECOs out for V7.3-1. Do you have them loaded. (Again,
> I am not convinced that this is a bug in COPY.)
>
> Please replicate this with an OpenVMS client task and using COPY,
> or -- better -- using DECnet task-to-task communications as described
> above, as a start, and please provide the procedures and the messages
> received.
>
> And, as mentioned, I expect this could easily be a limitation of the
> way COPY works with its source file specification processing and its
> filename defaulting.
>
> ---------------------------- #include <rtfaq.h> -----------------------------
> For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq
> --------------------------- pure personal opinion ---------------------------
> Hoff (Stephen) Hoffman OpenVMS Engineering hoff[at]hp.com
>

F.Z.



Relevant Pages

  • Re: MiKTeX / pstricks problem (pst-infixplot,pst-math)
    ... one or more lines will result in the error message. ... I only found in the documentation of the pst-infixplot package which uses the ... consider this command as deprecated. ... cosh has never been defined in pst-math as far as I remember. ...
    (comp.text.tex)
  • Re: Outlook out of the office
    ... the error message is: the command is not available. ... documentation on how to use this extention. ...
    (microsoft.public.outlook.general)
  • Re: [SLE] Wireless Internet at public hotspots -- update
    ... >> command, but it wants some input file. ... Isn't there an INSTALL ... There wasn't an error message. ... Just a query for an input file. ...
    (SuSE)
  • Re: cursmgr syntax
    ... Do note that the switches with CUSRMGR are case sensitive. ... Do you get an error message when you do this? ... What does the documentation for the command say? ...
    (microsoft.public.win2000.security)
  • Re: strange problem
    ... the name of the input file as an argument. ... get the following error message. ... This allows MPI_Init to strip off any command line arguments ... This signature was left intentionally almost blank. ...
    (comp.parallel.mpi)