Colin--I'm striking out as far as getting the info I know used to be there.  I found what possibly could be the problem on VM.IBM.com/RELATED/RSCS.

P4:
I installed RSCS RSU 9801 or 9802, now I am having NJE link problems
A4:
CP APARS VM61399 and VM61468 as well as RSCS APAR VM61888 must be applied when installing the RSCS RSU to correct CP performance problems, FRF002 or UDR001 abends and RSCS NJE link hangs (caused when receiving files containing no records), which are all due to RSCS's use of ASYNCHRONOUS CLOSE.

Unless I can find something else, you may have to wait for the flooding to recede in Endicott and Les Geer to get back in or possibly for the holiday weekend to be over.  July 4th is a big holiday over here celebrating the Declaration of Independence that started a little fracas that kicked you Brits out of the Colonies.  Lotta people take a longer holiday.

Jim



At 09:13 AM 6/30/2006, you wrote:
This is a multipart message in MIME format.
--=_alternative 0048A58AC125719D_=
Content-Type: text/plain; charset="US-ASCII"

Jim,

Thanks - any suggestions are welcome.  None of the files going over this
link are particularly large so, normally, 1 stream would suffice. What I
am not sure about is if 2 streams would increase or decrease the conflicts
I am seeing.

However, as both sides match, I guess this is something else. If you are
able to get details of the parms in use at your old site then this would
be very helpful.

Colin.

Jim Bohnsack <[EMAIL PROTECTED]> wrote:

Colin--Again, it's been a long time, but I'll see if the shop that I was
in
before still has the NJE connection and will try to get the JES and RSCS
definitions.  I don't remember if we had more than one stream.  I am
pretty
sure that even a single stream can handle sending and receiving at the
same
time.  Multiple streams, at least on the RSCS end, appear to only handle
one stream at a time but at least you don't have to have all of the little

tiny files queued behind a humongous one.

Jim

Jim Bohnsack
Cornell Univ.
(607) 255-1760


Reply via email to