I thought that some in IBM-MAIN (who aren't participants in the SHARE DVLG project requirement process) might be interested in the following note that I just sent out.
P.S. For those of you who DO participate in SHARE and are interested in the "Binder" - please make certain that you work with the DVLG project (Possibly renamed or soon to be renamed) to let you wishes and concerns be heard. -----Original Message----- to: DVLG requirements distribution list Although I am no longer "handling" DVLG requirements, I thought that I would point out the following. For the requirement: "SSDVLG04003 - Remove requirement for separate Binder/Pre-Link Steps" IBM (on Nov 29, 2005) indicated "Reason for rejection forthcoming" The "forthcoming" still hasn't happened (at least it isn't reflected in the SHARE database). However, if anyone missed it in the z/OS v1.8 "preview" that was issued this week and can be seen at: http://www.ibm.com/isource/cgi-bin/goto?it=usa_annred&on=206-039 It states, "Statement of general direction IBM plans to take the following actions effective with the general availability of z/OS V1.8: IBM intends to stabilize the prelinker. The prelinker was designed to process long names and support constructed reentrancy in earlier versions of the C compiler on the MVS and OS/390R operating systems. The prelinker, shipped with the z/OS C/C++ run-time library, provides output that is compatible with the linkage editor, shipped with the binder. The binder is designed to include the function of the prelinker, the linkage editor, the loader, and a number of APIs to manipulate the program object. Its functionality delivers a high level of compatibility with the prelinker and linkage editor, but provides additional functionality in some areas. For more information on the compatibility between the binder and the linker and prelinker, refer to z/OS MVS Program Management: User's Guide and Reference . Further enhancements will not be made to the prelinker utility. Enhancements will be made only to the binder, the strategic tool for program object manipulation." *** For those of you going to Seattle, I would LOVE to hear how IBM reconciles the refusal to remove the requirement for the pre-linker (in "all cases") with this statement of direction. My best "reading" of this is that if you rely on "load modules" (rather than "program objects") you have VERY dim future ahead of you. Other uses of the pre-linker (i.e. NON-C-only applications) may have equally troublesome futures. Maybe when we actually see the "forthcoming" reason, it will explain SOMETHING. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
