Very Computer

I need to write to a D3 NT file using OSFI within D3 AIX.  I can use the
COPY verb just fine.  Quite often when I use the WRITE verb, I get the
message:

Write/Delete (ITEM ID) Remote Operation Failed

O=Logoff / Q=Quit / R=Retry / C=Continue ?

ITEM ID being the item id I'm trying to write at the time.

You just have to Quit out of it.  Can anyone give advice on how to solve
this problem?

I'm running D3 NT v.7.1.4 , D3 AIX v.7.1.0.RS
I open the file like this:
OPEN "NT_SERV:TPS.DATA,MV_EMAIL," TO FILE.FAX ELSE STOP 201, 'MV_EMAIL'

NT_SERV = the name of my D3 NT Server
TPS.DATA = the account the file resides in
MV_EMAIL = the file name   (this was created in FSI)

Didn't you try to make a q-pointer in the account's MD for
nt_serv:tps.data,mv_email, file?

What about open "nt_serv:mds,tps.data,mv_email, ... ?

It looks like it helps,
Nick

Quote:> I need to write to a D3 NT file using OSFI within D3 AIX.  I can use the
> COPY verb just fine.  Quite often when I use the WRITE verb, I get the
> message:

> Write/Delete (ITEM ID) Remote Operation Failed

> O=Logoff / Q=Quit / R=Retry / C=Continue ?

> ITEM ID being the item id I'm trying to write at the time.

> You just have to Quit out of it.  Can anyone give advice on how to solve
> this problem?

> I'm running D3 NT v.7.1.4 , D3 AIX v.7.1.0.RS
> I open the file like this:
> OPEN "NT_SERV:TPS.DATA,MV_EMAIL," TO FILE.FAX ELSE STOP 201, 'MV_EMAIL'

> NT_SERV = the name of my D3 NT Server
> TPS.DATA = the account the file resides in
> MV_EMAIL = the file name   (this was created in FSI)

I've tried setting up a q-pointer and opening it that way and I just tried
it to open it the other way. It still doesn't work.
I looks like it writes the first set of items the first time and when I try
to rerun to program to write another set of items, thats when I get the
message.
I then have to logoff and then log back on to get it to write.
Could this be some kind of internal locking problem?

If the COPY command works, then your code should work as well.

Have you tried the (R)etry option?  Does it ever work?

If you weren't making the connection at all, you would get "TPS.DATA is not
an md" something similar.  Since it is only the write operation that is
failing, it's either a network timeout and a real write problem such as an
update protection violation.

You could try making a local Q-pointer (although what you are doing should
work)

1)    Q
2)
3)    NT_SERV:TPS.DATA,MV_EMAIL,

Mark

=================

--

Mark Brown
Manager Continuing Engineering
Pick Systems
Irvine, CA   USA

Mark,
I have tried making the local Q-pointer and it acts the same way.
I have tried the (R)etry option and it just keeps printing the message.

What is strange to me is that sometimes I can run the program 3 or 4 times
and it will work fine.
Sometimes it won't display the message, but it won't write the items.
I was also wondering about the network timeout.  If this the case, what can
I do about it?

Thanks, Poppy

Is your TPS.DATA account an FSI account, or VME?  If you do a LF to list the
files, do they have bases or NA?

And (stupid question of the day) are the OSFI servers running on NT and if so,
how many.  If you do WHERE, how many ports show up in RPS.GETCMD?  Any?

If none, there is a program in DM called NETWORK-SETUP.  It's a menu and it
lets you define your host and start or stop your "servers".  These are phantom
processes which 'listen' to remote requests.

Send me a screen shot of the WHICH CDA from each of the two systems so I can
see if there are any release inconsistencies and I'll do what I can to help.

Mark

--

Mark Brown
Manager Continuing Engineering
Pick Systems
Irvine, CA   USA

Hi Poppy

What we need to find out is the patch levels on both machines ie monitor &
abs .

Quote:> Mark,
> I have tried making the local Q-pointer and it acts the same way.
> I have tried the (R)etry option and it just keeps printing the message.

> What is strange to me is that sometimes I can run the program 3 or 4 times
> and it will work fine.
> Sometimes it won't display the message, but it won't write the items.
> I was also wondering about the network timeout.  If this the case, what
can
> I do about it?

> Thanks, Poppy

I get the same problem, but during a copy, between D3-AIX and D3-Linux.
Below is my which cda on both machines.  Hope this is helpfull and I look
forward to seeing a solution.

AIX is:
                   System Release Information
                   ==========================
    D3 Release Version  7.1.0.RS
    Most recent mload into boot abs performed at 17:05:12 on 06 Jun 2000

    Implementation. . . . . . RS6000
    System Serial Number. . . 11024618
    System ID Number  . . . . 60145060
    Release . . . . . . . . . D3/UNIX: RS6000
    Unix Information. . . . . AIX;pick0:AIX;3;4;01012467

    Boot Monitor. . . . . . . 7.1.X.M9; 15 Sep 1999
    Boot ABS. . . . . . . . . 7.1.0.A13; 13 Nov 1997
    Boot ABS Data File. . . . 7.1.0.A13; 13 Nov 1997
    System Data Files . . . . 7.1.0.D13; 13 Nov 1997
    FlashBASIC Revision . . . 7.1.0.F16; 04 Jan 2000
    SQL Revision. . . . . . . 7.1.x.S23; 03 May 2000
    Abs Patch Level . . . . . 7.1.0.A106; 31 Oct 1996

Linux:
                    System Release Information
                    ==========================
     D3 Release Version  7.1.0.LINUX
     Most recent mload into boot abs performed at 11:35:36 on 01 Dec 1998.

     Implementation. . . . . . 6386
     System Serial Number. . . 11026175
     System ID Number  . . . . 40151188
     Release . . . . . . . . . D3/UNIX: LINUX
     Unix Information. . . . . Linux;pick0:LINUX;2.0.36;#1 Sun Aug 1
05:22:42 /e
tc/localtime 1999;9EFC186A

     Boot Monitor. . . . . . . 7.1.X.M1; 29 Jul 1998
     Boot ABS. . . . . . . . . 7.1.0.A13; 21 Oct 1998
     Boot ABS Data File. . . . 7.1.0.A13; 21 Oct 1998
     System Data Files . . . . 7.1.0.D13; 21 Oct 1998
     FlashBASIC Revision . . . 7.1.0.F11; 15 Sep 1997
     SQL Revision. . . . . . . 7.1.0.S9; 16 Sep 1997
     Abs Patch Level . . . . . 7.1.0.A67;

Quote:> I need to write to a D3 NT file using OSFI within D3 AIX.  I can use the
> COPY verb just fine.  Quite often when I use the WRITE verb, I get the
> message:

> Write/Delete (ITEM ID) Remote Operation Failed

> O=Logoff / Q=Quit / R=Retry / C=Continue ?

> ITEM ID being the item id I'm trying to write at the time.

> You just have to Quit out of it.  Can anyone give advice on how to solve
> this problem?

> I'm running D3 NT v.7.1.4 , D3 AIX v.7.1.0.RS
> I open the file like this:
> OPEN "NT_SERV:TPS.DATA,MV_EMAIL," TO FILE.FAX ELSE STOP 201, 'MV_EMAIL'

> NT_SERV = the name of my D3 NT Server
> TPS.DATA = the account the file resides in
> MV_EMAIL = the file name   (this was created in FSI)

I'm so glad to know someone else is having this.  I've been testing and
re-testing and this is what I have found so far.

My COPY also fails on occasion, but get this.  By accident, I discovered
that when I COPY or WRITE and AIX thinks it has (no error message given) ,
it is actually copying or writing to my BP file on NT instead of the file I
told it to.
I keep second-guessing myself about my q-pointers, but this also happens
when I give the explicit command.

Tim, see if your items are in your bp.
I still don't know what to do about the error message.