Thomas Berg wrote: > > > -----Ursprungligt meddelande----- > > Från: IBM Mainframe Discussion List [mailto:[email protected]] För Don > > Poitras > > Skickat: den 25 januari 2012 13:11 > > Till: [email protected] > > Ämne: Re: STEPLIB problems - was: PDSE > > > > In article > > <a90e503c23f97441b05ee302853b0e62616721c...@fspas01ev010.fspa.myntet.se> > > you wrote: > > > The original case by Juergen touches the main shortcoming of IBM's > > STEPLIB-stance. > > > > > There are cases when putting steplib(s) in linklist simply do not work! > > And where the alternative of putting it in the logon procedures is working > > nearly as bad. > > > I have several times seen those cases luckily (= allowed by management) > > been solved by dynamic steplib functions from outside IBM. > > > > > This happens when You must use conflicting software or software > > versions. One such case was when we were upgrading DB2 and during that > > period was the different test/development DB2 systems on different release > > levels. Another case was when we had different software (in the TSO > > development environments) that relied on the same set of "SAS/C" modules > > for I/O and other things - but of different releases of these modules. > > (At least one of those SW was IBM's.) And other cases. > > > > Did you try putting the then-current SAS/C release in linklist? If that > > didn't > > work, you could have opened a problem report with SAS and we would have > > tried to fix it. For the WSA (back when it was written in SAS/C), we > > actually > > prefixed the library so that you could put two (or more) versions in > > linklist without disrupting running programs. > > IIRC, these "SAS/C" modules was delivered as a part of these SW's own > libraries, not as a part of the SAS product. > (I call these "SAS/C" as that was what I saw when browsing the loadmodules.) > In fact, one of the SW's was ISPF/WSA and the other (IIRC) was a product > called ProEdit. > > BTW, what do You mean by "prefixed the library" ?
SAS/C != SAS. The "SAS/C Transient Library" contains portions of the C run-time library and is freely distributable by ISVs. We ask that they distribute it as provided, but we can't force them to do so. Back in '96, we worked with IBM to take advantage of a feature that was already present. In order to allow the CICS transient library to co-exist with the non-CICS version, the calling code was written to use a prefix for each load module. "LSH" for CICS and "LSC" for non-CICS. These names are actually aliases of the L$C prefix that we use for zapping the modules with maintanence. User programs would pick up the prefix by linking with the appropriate link library. For IBM, we externalized this feature and they started delivering the transient library with (as I recall) "ISP" as the prefix. The idea being that IBM wouldn't be forced to use a newer transient library (or back-level if the customer for some reason did that.) A few other ISV's used this as well. > > > Regards, > Thomas Berg > _________________________________________ > Thomas Berg Specialist A M SWEDBANK -- Don Poitras - zSeries R & D - SAS Institute Inc. - SAS Campus Drive mailto:[email protected] (919)531-5637 Fax:677-4444 Cary, NC 27513 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
