On 5 Sep 2010 08:10:55 -0700, in bit.listserv.ibm-main you wrote: > On 9/5/2010 2:51 AM, Robert A. Rosenberg wrote: >> At 09:26 -0700 on 09/02/2010, Edward Jaffe wrote about Re: Where doc for >> STORAGE LINKAGE=SYSTEM: >> >>> We've been burned by that unintuitive CALLRKY= default more than once. >> >> Theoretically there is a solution. Add a CALLERKEY= Parm and have it checked >> for first. If it is set then in that path check for CALLRKY and MNOTE if >> both >> defined and has a different value (otherwise ignore the CALLRKY). If >> CALLERKEY >> has not been used then do the normal check for CALLRKY. There have been >> other >> depreciated parms that have been handled this way if I remember correctly. > >I wasn't clear. We weren't burned because the CALLRKY= keyword has no vowels. >We >were burned by the unexpected fact that the STORAGE OBTAIN service assigns key >zero (by default) to storage acquired from key-specifiable subpools, thus >requiring explicit specification of CALLRKY=YES in nearly every case.
The vendor inappropriate default strikes again (I use the term vendor because the problem is not unique to IBM). Clark Morris ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
