The Binder RENT option is not needed for your use case, as you've discovered, as it is for cases when the binder input isn't marked as RENT already. Your Cobol compiles with the RENT option will pass that to the Binder. The use case where RENT or REUS is needed is when there are non-Cobol subroutines involved and you need to control the attributes for correct execution. Cobol manual is a suggesting it is good practice to specify the option as things could break with non-Cobol components added, I'm pretty sure it is never needed for all Cobol.
On Sat, Aug 14, 2021 at 9:16 AM Frank Swarbrick <[email protected]> wrote: > For our COBOL program binder step we've never specified the RENT (or > REUS=RENT) option, even though we always use the RENT compiler option. > This has never seemed to cause us any problems. I now see in the > Enterprise COBOL manual, section "Compiling programs to create DLLs"( > https://www.ibm.com/docs/en/cobol-zos/6.3?topic=application-compiling-programs-create-dlls), > where it states "Applications that use DLL support must be reentrant. > Therefore, you must compile them with the RENT compiler option and link > them with the RENT binder option." However, I've been doing testing with > DLLs recently and have never had any (noticeable?) issues even though we > are not specifying RENT or REUS=RENT. > > So what's up with this? And what about for non-DLL dynamic calls? I've > had no issues there, either. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
