Keeping pclink2.pub.sys in mind as the 'other end' of Reflection is indeed 
a good point.  Just this week (after months of Reflection File transfer 
not working well) we REVERTED back to an old version of Pclink2 (something 
about it being 'single direction') and we're back working again. 
Assistance came from the HP Response Center who had the older version for 
us.  Apparently there are 'fire-wall rules' in place (not owned nor 
maintained by our dept) that had gotten in the way of the newer PcLink2 
'2-way' communication.

--------

Date:    Fri, 28 Apr 2006 19:53:31 -0400
From:    Neil Armstrong <[log in to unmask]>
Subject: Re: Reflection: transferring monster files

At 03:07 PM 4/28/2006, William Brandt wrote:
Dear William,

As someone familiar with fserr 106 and extent size exceeds maximum, I
highly doubt that this
is in Reflection itself, but rather likely is an error returned from
pclink2.pub.sys. It just may be
that all you would have to do is upgrade your version of PCLINK2. I did a
lot of research into
this when dealing with large files on MPE. It may also be how the
Reflection side estimates the
size of the file to build.

In taking a look at WRQ's support site there is the following:

http://support.wrq.com/techdocs/1348.html

Hope this helps.
Sincerely,
Neil

----------------------------------------------------------------------------
  Deane Bell; Computer Services Coordinator, Affiliate Assistant Professor
  The University of Washington           Vmail    : (206) 598-6009
  Medical Centers Pharmacy - ea151       TextPager: (206) 995-2720
  1959 N.E. Pacific Street, Box 356015   facsimile: (206) 598-4901
  Seattle, WA  98195-6015  U.S.A.        internet : [log in to unmask]
----------------------------------------------------------------------------

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *