Ok, sorry, here we go:
THE FOLLOWING NAMES ARE UNDEFINED:
IHE012I U &Â ABENDED IN STMT 00008 AT OFFSET 000B6E FROM ENTRY POINT
DRIVER WITH CC 15A (SYSTEM)
DMSABN148T SYSTEM ABEND 15A CALLED FROM 7F5502.
global txtlib plilib
Ready; T=0.01/0.03 13:11:06
Ready; T=0.01/0.03 13:11:10
filedef sysprint term
Ready; T=0.01/0.01 13:11:21
5 6 11
Ready; T=0.01/0.03 13:11:22
the first driver call is immediately after LOGON, and it ABENDs with SYSTEM 15A.
the second one works well (after GLOBAL TXTLIB PLILIB), but since there is no
FILEDEF for SYSPRINT, the output goes to a disk file.
the third one shows the output on the terminal.
My opinion was that the generated module (like a load module in MVS) contains
all the code needed to run the application. But this seems not to be the case;
the module needs the GLOBAL TXTLIB anyway, and the PL/1 runtime objects are
fetched from there at runtime, is this true? Or: does the MVS / CMS analogy not
Am 22.03.2013 11:47, schrieb P.C.:
> > there is another problem I observed yesterday with those PL/1 programs.
> > I generate a module using LOAD ... GENMOD.
> > This runs well, as I pointed out.
> > But, when I log off from my CMS session and log on again later, I get
> > strange ABENDs,
> > when I try to run the generated module again. It only runs after I did
> > another PL/1 compile,
> > of maybe the GLOBAL TXTLIB PLILIB. There are some prerequisite which I
> > didn't analyze
> > so far.
> > I know similar behaviour from the Stanford PASCAL compiler, which I
> > improved and
> > extended last year. This is why I do not generate modules regularly, but
> > instead rely
> > on LOAD ... START.
> > When I worked with VM/SP in the 90s, we never had such problems.
> > What is the difference here?
> Maybe you had GLOBAL TXTLIB PLILIB in your PROFILE EXEC or SYSPROF EXEC when
> you used VM/SP?
> It's hard to speculate further without knowing what kind of strange ABENDs you
> are getting.