RENT

Your code is "naturally reentrant" if it does not alter any of its static variables. The RENT option specifies that the compiler is to take code that is not naturally reentrant and make it reentrant.

For a detailed description of reentrancy, see the z/OS Language Environment Programming Guide. If you use the RENT option, the Linkage Editor cannot directly process the object module that is produced; you must use PDSEs.

   .-NORENT-.   
>>-+-RENT---+--------------------------------------------------><

The NORENT option specifies that the compiler is not to specifically generate reentrant code from nonreentrant code. Any naturally reentrant code remains reentrant.

If you link a module (either MAIN or FETCHABLE) containing one or more programs compiled with the RENT option, you must specify DYNAM=DLL and REUS=RENT on the link step.

If you specify the options NORENT and LIMITS(EXTNAME(n)) (with n <= 7), the text decks generated by the compiler will have the same format as those generated by the older PL/I compilers. If you use any other options, you must use PDSEs.

The code generated under the NORENT option might not be reentrant unless the NOWRITABLE option is also specified.

The use of the NORENT does preclude the use of some features of the compiler. In particular, note the following considerations:

• DLLs cannot be built.
• Reentrant, writeable static is not supported.
• A STATIC ENTRY VARIABLE cannot have an INITIAL value.

You can mix RENT and NORENT code subject to the following restrictions:

• Code compiled with RENT cannot be mixed with code compiled with NORENT if they share any EXTERNAL STATIC variables.
• Code compiled with RENT cannot call an ENTRY VARIABLE set in code compiled with NORENT.
• Code compiled with RENT cannot call an ENTRY CONSTANT that was fetched in code compiled with NORENT.
• Code compiled with RENT can fetch a module containing code compiled with NORENT if one of the following conditions is true:
  • All the code in the fetched module was compiled with NORENT.
  • The code containing the entry point to the module was compiled with RENT.
• Code compiled with NORENT code cannot fetch a module containing any code compiled with RENT.
• Code compiled with NORENT WRITABLE cannot be mixed with code compiled with NORENT NOWRITABLE if they share any external CONTROLLED variables or any external FILEs.

Given the above restrictions, the following is still valid:

• A NORENT routine, called say mnorent, statically links and calls a RENT routine, called say mrent.
• The RENT routine mrent then fetches and calls a separately-linked module with an entry point compiled with RENT.