On Sep 30, 2:15 pm, rsmereka <rsmer...@future-lab.com> wrote:
> I work with D3 VME on a daily basis and I have started experimenting
> with the open source version of OpenQM.
> On D3 I can run the following command from TCL:
> COPY DOS:C: /transfer/somefile.txt
When you do this you are using D3's OSFI, which allows D3 to
communicate with various file systems and/or hosts via existing
"drivers". "DOS" is a driver entry in the DM,HOSTS file which defines
communication with the underlying Windows file system. AFAIK, QM does
not have such a concept, thus you must first define the directory
"file" in your VOC so that the QM COPY command can find/access it.
Btw, using "COPY DOS:C: /" on D3 is somewhat redundant because there
exists in the D3 Hosts file an entry for "C". You should be able to
accomplish exactly the same thing with the command COPY C: /transfer/
somefile.txt
Works like a charm. At first, I was concerned that OpenQM may not
properly translate the LF's to FM's/AM's but once I copied a sample
text file from Linux and then read it in OpenQM using CT and ED, I
could see that OpenQM did the translation.
>When you do this you are using D3's OSFI, which allows D3 to
>communicate with various file systems and/or hosts via existing
>"drivers". "DOS" is a driver entry in the DM,HOSTS file which defines
>communication with the underlying Windows file system. AFAIK, QM does
>not have such a concept, thus you must first define the directory
>"file" in your VOC so that the QM COPY command can find/access it.
>Btw, using "COPY DOS:C: /" on D3 is somewhat redundant because there
>exists in the D3 Hosts file an entry for "C". You should be able to
>accomplish exactly the same thing with the command COPY C: /transfer/
>somefile.txt
Kevin,
After reading Tony's G's post of this topic, I understood what D3 was
doing. I, however, did not know how to accomplish this in OpenQM. I
just tried using your tip on D3:
COPY C: /transfer/somefile.txt
[202] '/transfer/somefile.txt not on file.
[401] no items present.
When I change the syntax to:
COPY DOS:C: /transfer/somefile.txt
the copy works fine.
It appears that the item in the Hosts file is missing. BTW, I cannot
find a file called Hosts.
The hosts file is in DM, so you can see it using: sort dm,hosts,
The hosts item DOS goes to the default Windows drive. It's different from the "C" and other drivers in that it does not convert between tabs and spaces - which may or may not be what you want.
I believe it's legal to cascade hosts references (like DOS:C:) but it shouldn't be necessary and is probably subject to issues.
When using OSFI, the driver:path is equivalent to the MV file and the DOS filename is the MV item ID, so: COPY DOS:/temp myprog.txt TO: (bp myprog or COPY BP PROG1 PROG2 TO: (d:/backups/bp
Note that all slashes are forward and normal rules apply for changing file=item names. Keep the host:path reference together as though it's all a single filename. Casing doesn't matter in DOS but does for *nix.
References like //server/path are possible but there are complications - see the TL forum or contact TL for assistance.
I present this here in case at some point QM users need to work out migration, or if Martin wants to add similar functionality at some point.
> After reading Tony's G's post of this topic, I understood what D3 was > doing. I, however, did not know how to accomplish this in OpenQM. I > just tried using your tip on D3: > COPY C: /transfer/somefile.txt > [202] '/transfer/somefile.txt not on file. > [401] no items present.
> When I change the syntax to: > COPY DOS:C: /transfer/somefile.txt
> the copy works fine.
> It appears that the item in the Hosts file is missing. BTW, I cannot > find a file called Hosts.
|
