Well, got part of the problem resolved. Apparently the CHARLOTT VMARC
doesn't have a CHARLOTT EXEC. I was expanding the VMARC and overlaying
my previous version, so the CHARLOTT * was not getting replaced.
I've fixed that, but now I'm getting:
i cms
z/VM V5.4.0 2010-09-15 11:19
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.02/0.02 12:13:52
acc vmsysa:.charlott m
Ready; T=0.01/0.01 12:14:00
ww2
DMSEXI240E Alternate exec processor "EAGRTPRC" not found
55 *-* 'EXEC WW2MAIN' arg(1) /* Invoke Charlotte main
program */
+++ RC(-3) +++
Ready(-0003); T=0.01/0.01 12:14:03
list ww2main * *
WW2MAIN EXEC M1
Ready; T=0.01/0.01 12:14:32
list eag* * *
EAGALPRC MODULE M1
EAGALUME TXTAMENG M1
EAGRTALT MODULE M1
Ready; T=0.01/0.01 12:14:49
So, now it doesn't appear to be a PIPELINE problem.
Frank M. Ramaekers Jr.
-----Original Message-----
From: CMSTSO Pipelines Discussion List
[mailto:[email protected]] On Behalf Of Jonathan Scott
Sent: Wednesday, February 16, 2011 12:02 PM
To: [email protected]
Subject: Re: [CMS-PIPELINES] CHARLOTTe abends in low storage
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
_____________________________________________________
This message contains information which is privileged and confidential and is
solely for the use of the
intended recipient. If you are not the intended recipient, be aware that any
review, disclosure,
copying, distribution, or use of the contents of this message is strictly
prohibited. If you have
received this in error, please destroy it immediately and notify us at
[email protected].
