Oppolzer - Informatik / Blog

NORENT is the option that tells the EP compiler to do the same that all the
"old" compilers did, that is, put the static variables in the STATIC CSECT.  If
the program is reentrant or not, depends on the programmer; if he or she changes
static variables during execution, the program will not be reentrant.

With option RENT (inherited from C++), the program is made artificially
reentrant, even if the static variables are changed.

RENT was the only option in the first versions of EP PL/1, but it is now not
recommended any longer.

See these older discussions on ASSEMBLER-L:

http://bernd-oppolzer.de/blog_20100605_145144.htm
http://bernd-oppolzer.de/blog_20100605_155102.htm
http://bernd-oppolzer.de/blog_20100606_022547.htm
http://bernd-oppolzer.de/blog_20100606_084424.htm
http://bernd-oppolzer.de/blog_20100606_132541.htm

Kind regards

Bernd



Am 24.02.2015 um 12:47 schrieb E.E.:
> Warning: My PL/1 skills are really decayed...
>
> P.B. wrote:
>
>> Our customer has been trialling Enterprise PL/1 4.4, with the intention of
>> upgrading from their current compiler, PL/1 for MVS&VM.
>
> At what level of z/OS, VM, Language Environment and CICS?
>
>> They have issues with performance, particularly with CICS programs, where the
>> CPU time of a transaction is 3 times what it was with PL/1 for MVS&VM.
>
> With specific transactions or all transactions? With all or some CICS regions?
>
>> We have a PMR open with IBM, who suggested the NORENT option, which did
>> reduce the CPU to just double the old value.
>
> NORENT? Hmmm, I think it is something how your programs are linked or
> combined with CICS and CICS programs.
>
> Based on what is IBM suggesting NORENT?
>
> Groete / Greetings
> E.E.