I've not seen any problem like that here with Charlotte even on the latest level of Pipelines (110C0008).
I don't think there's been any fix to Charlotte itself for anything like this, at least not since I took over looking after it about 15 years ago. This sounds like the sort of problem you get when nucleus extensions get dropped while there are still pointers to the code. Do you have some NUCXLOAD/NUCXDROP logic in your front-end procedure for Charlotte? Does the problem still occur if you switch to the uplevel PIPE before the first time you try to run Charlotte within a session? Jonathan Scott IBM Hursley, UK Frank M. Ramaekers Jr. wrote: > pickpipe up > > PIPINX086I CMS/TSO Pipelines, 5654-030/5655-A17 1.0112 > (Version.Release/Mod) - Generated 3 Jul 2010 at 11:32:36. > > Source: Princeton Runtime Distribution > > Ready; T=0.01/0.01 09:21:29 > > charlott > > DMSABE141T Operation exception occurred at 80000002 in routine PIPE
