Oppolzer - Informatik / Blog

Hello together,

I too have PL/1 (F) installed on VM 6.2 (or what is the version number of the VM
sixpack installation).

The difference is that I call the PL/1 compiler thru a PLICOMP EXEC which does
the FILEDEF * CLEAR before the call to the compiler, so I did not recognize the
problem that the OP had. Maybe I had the problem before and found the solution
myself.

I also saw the solution when I saw that the compiler complained about a missing
SYSPRINT declaration on the compile of ARITH on the OP's run, but there is no
PUT statement in there. So the compiler must have compiled DRIVER PLI again.

Thanks for the LOAD ... (NODUP suggestion.

Kind regards

Bernd



Am 22.03.2013 08:59, schrieb R.F.:
>
>
>
>
> --- In H390-VM@yahoogroups.com, G.M. wrote:
> > Now why the duplicate identifier?
>
> The compiler generates a IHENTRY CSECT as an entry point for the module. The
> loader keep the one of the MAIN module and ignores the others (but warn you
> about them). You can suppress the message with the option "nodup":
>
> load driver arith ( nodup
>
> There may be a way to compile a module without producing this CSECT but I
> haven't look for it.
>
> > why does one have to do the filedef * clear?
>
> Beacuse the PLI command does not clear them. First compile driver and query
> the file definitions:
>
> pli driver
> query filedef
>
> you should see the file definitions for LISTING, TEXT, PLI, and SYSUT1. Those
> were re-used in your arith compilation, hence the absence of TEXT and LISTING
> for arith.
>
> Yours truly,
>
> R.F.
>
>