To put it in the saved segment, I had to make the segment larger. As a result it conflicted with the next segment in memory.
I am home and don't remember the names right now, but I think it might have been the CMSFILES segment used only by SFS servers. Since I have the VSEG product (now 'component of VM:SPOOL') I saved the *old* pipes segment as IBMPIPES, and defined an alias for all machines in the SFS accounting group to load IBMPIPES when asking for CMSPIPES. That way all my users get the new runtime, and only the SFS servers get the old one. (Why would an SFS server need that segment? I haven't figured that part out yet... but didn't want to rock the boat) Shimon On Fri, Jun 25, 2010 at 4:25 PM, John P. Hartmann <[email protected]>wrote: > Some things may start to work. I'm not aware of any APAR fixes that I > haven't picked up. > > There is an incompatibility with spec. See the pipline news file. > > The module is larger, given the function added over the past decade. > > So, I'd say "no", but I am hardly unbiased. > > j. > > On 25 June 2010 15:18, Hughes, Jim <[email protected]> wrote: > > Is there a downside to replacing the PIPELINES distributed with Z/VM 5.4 > > with the current PIPELINES Runtime Library from Marist? > > > > > > > > > > > > > > > > ____________________ > > > > Jim Hughes > > > > 603-271-5586 > > > > "It is fun to do the impossible." > > > > > > >
