On Sat, 3 May 2008 05:58:25 -0500, Saravanan J wrote: >In one of our programs say XYZ, we are accessing USER catalog by >dynamically allocating the Catalog using SVC 99 (in shared access mode) to >get some dataset related information from the catalog. > >Before this dynamic allocation we are actually turning-on all the wait bits >(S99WTVOL+S99WTDSN+S99WTUNT+S99OFFLN) in S99FLG21 byte. So far so >good, but we seem to be getting allocation failures on the catalog in our >program XYZ, whenever our catalog compression jobs are running (Catalog >compress jobs have exclusive ENQ on the catalog during compress). > >As per our understanding, the dynamic allocation in XYZ program should wait >for the shared access of Catalog as the catalog is locked for exclusive use by >Catalog compression jobs. And since the DSN is unavailable to our program >XYZ, it should wait for the DSN till the catalog compress job releases the >exclusive lock on catalog. > >Any pointers to why the S99FLG21 wait bits are not working would be of great >help to us? I suspect that the problem your program is having has less to do with the SYSDSN enqueue that S99WTDSN was designed to cope with, and more to do with the SYSVSAM enqueue that Catalog management and VSAM use for proper serialization during the catalog compression processes. I do not recall any user control over that SYSVSAM intersect via SVC99. -- Tom Schmidt
---------------------------------------------------------------------- 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
