Shmuel's post very accurately characterizes the behavior of the linkage editor . It does not characterize that of the binder, which in this context is very different. even when it is pretending to be the linkage editor in order to produce load modules.
>From page 31 of the current z/OS MVS program management: user's guide and reference <begin extract> The linkage editor processed the serially reusable (REUS), reenterable (RENT), and refreshable (REFR) attributes as separate and independent attributes. The binder, however, treats them as a single, multivalued attribute with an implied hierarchical relationship: "refreshable" implies "reenterable" and "reenterable" implies "serially reusable". This might result in some confusion for prior linkage editor users, who are accustomed to specifying inconsistent combinations of these attributes, such as "REFR,NORENT". In such circumstances the binder selects the strongest reusabiluty attribute among those specified. In addition, unlike the linkage editor, the binder honors any override of reusability specified in the PARM statement. </end extract> Binder documentation has sometimes been prospective, characterizing what hopefully was to be rather than what is. In this case, however, the manual describes exactly what the binder now---i.e., for z/OS 1.13 and 2.1---does. It is, of course, a break with tradition, but this manual's further recommendation, loc. cit., <begin extract> In order to eliminate such conflicts, specify only a single attribute from the set. Use the keyword(value) form, such as REUS(RENT), rather than keyword only forms, such as NORENT or REFR. </end extract> should be complied with, at least prospectively. For only serially reusable code the use of this keyword(value) form admittedly yields the barbarism REUS(REUS); but. since serially reusable code is at best obsolescent, there should be no actual occasion to employ it. John Gilmore, Ashland, MA 01721 - USA ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
