TP EXPORT FAILS with Error 13 - MCH3601 fo und in R3TRANS joblog
Thanks, Diane! You're correct: my old kernel library had the old version of TP and R3TRANS. When I purposely backleveled the kernel library, I backleveled them, too. Apparently the "speed" problem has been addressed, but must be something else in R3TRANS that doesn't like a particular kind of object. Most of the transports EXPORT just fine, just not this particular one.
--- In SAP on System iZegroups.com, Diane Piccirello <dpiccirelloZt...> wrote: > Hi Jim, > > There is a TP patch to correct the "long running" time on transports. We're > at Kernel 4.6D, level 308, but we had to bring TP up to 357. The problem > wasn't with the kernel, but with TP itself. I also updated R3TRANS at the > same time. > > Regards, > > ******************************* > Diane Piccirello > Twin Laboratories, Inc. > 150 Motor Parkway, Suite 210 > Hauppauge, NY 11788 > > Phone: 631.467.3140. ext. 8321 > Fax: 631.630.3588 > Email: dpiccirelloZt... > > > -----Original Message----- > From: Jim Doll [mailto:jdollZp...] > Sent: Tuesday, January 02, 2001 2:16 PM > To: SAP on System iZegroups.com > Subject: Re: TP EXPORT FAILS with Error 13 - MCH3601 > found in R3TRANS joblog > > > Some additional info: > I tried a "TP EXPORT" at the OS/400 level (which I didn't even know > was possible) and got the error with the following version: > This is R3D46O338/TPOS4 version 305.12.19 (release 46D) .... > > I added my old kernel library into my library list (first), and it > exported successfully! In this case, it showed this version: > This is R3D46O308/TPOS4 version 305.12.17 (release 46D) .... > > (Note that we put the kernel patch level in the library list: patch > level 338 failed, but 308 worked.) > > It took a long time to complete, which was a problem on 308, but it > did run successfully. > > --- In SAP on System iZegroups.com, "Jim Doll" <jdollZp...> wrote: > > We're seeing this now too, but it doesn't seem to be size related. > > We're on same Support pack, kernel, and OS/400 level. Our > transport > > has 1 table and half a dozen programs. We split out just the > > programs, and we're having the same trouble. It hasn't been > > transported previously, so we don't know if it is the object or our > > maintenance level. > > > > > > --- In SAP on System iZegroups.com, "Anderson, Doreen" <dandersoZb...> > > wrote: > > > > > > Just wondering if anyone else on 46C support pck 12; 46D kernel > lvl > > 338; V4R5 compliant with IBM APAR > > > has hit the error below on Exporting (releasing) a change > request. > > > > > > Export Error 13 > > Cancelled > > > R3trans received signal 1595176880 from operating > > system > > > > > > > > > This is a very large change request & this error occurs after > quite > > a > > > few of the objects export properly. Are there Change Request > > size > > > constraints that would cause this error to occur part way through? > > > > > > > > > R3trans Joblog on Operating > > System..... > > > > > > MCH3601 > > ERROR > > > From module . : > > TWEXPDAT > > > From procedure : > > exp_cualt__FP16Transport_unit_tP11Selection_t > > > Statement . . .: > > 127 > > > To module . .. : > > TWEXPDAT > > > To procedure . : > > exp_cualt__FP16Transport_unit_tP11Selection_t > > > Statement . . .: > > 127 > > > > > > > > > Thanks > > > Doreen Anderson > > > Operations / SAP Basis Manager > > > Ball Horticultural Company > > > 630-588-3214 > > > dandersoZb... > > > To unsubscribe from this group, send an email to: > SAP on System i-unsubscribeZegroups.com