Re: Automating SNDNETF and RCVNETF

For what it is worth: 
I have seen the error codes mentioned in the attached note when using
ObjectConnect:
*       When I first set up ObjectConnect between a system at V4R2 and V3R2
(this was a while back as you can imagine). The fix was a PTF on V3R2 (it
was listed in the V4R2 PSP).
*       Between V4R4 and V4R2 (I've just run into this one). I assume I have
another PTF to locate and install (I do have the PTF for ObjectConnect in
the V4R4 PSP installed on the V4R2 box).
In both of the above cases I used SNDNETF/RCVNETF with save files to get the
job done.

I also had a nuisance problem when I set up ObjectConnect on our new V4R4
box and out old V3R2 system during our recently completed side-by-side
migration. I got unexpected messages at the system operators console on the
V3R2 system when whenever SAVRSTOBJ was used to or from the V3R2 system (but
the object was moved successfully). We installed several PTF's on both
systems to no avail.  Rochester support had a list of version to version
specific PTF's that are not on the CUME or HIPER that were installed, but
did not resolve the problem. Despite numerous traces and conversations with
Rochester development we reached the point where we shut down the old system
before a fix was worked out, so as far as I know that problem still exists.


********************************* (Original note)
*******************************
Date: Fri, 31 Mar 2000 10:11:02 -0600
From: "Jim Oberholtzer/Computech" <joberhol@compures.com>
Subject: Re: Automating SNDNETF and RCVNETF

<*snip>
4 > SAVRSTLIB LIB(LNOTES) RMTLOCNAME(S104N5GM)
    ObjectConnect/400 internal error, function code 03, return code 04.
    An error occurred during the SAVRSTLIB operation.
<endsnip>

At first glance, I wonder if distribution services is set up on both boxes.
If the SNDNETF works, then this option should as well.  Do you have the
options installed on both boxes  (on another message this was correctly
identified as option 22 of OS/400)?  I suspect that if you look at the
distribution queue messages you will get better information about why this
did not work.

Jim
***************
George Lemen
Sr. Project Analyst, CIBER Inc.
Weyerhaeuser CER Operations Manager
Weyerhaeuser phone: (253) 924-7648; E-mail: George.Lemen@Weyerhaeuser.com
CIBER phone and voice mail: (425) 451-2575 extension 142; E-mail:
glemen@ciber.com
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---