I haven't played with DSABs since the mid '70s, at which time there was no 
GETDSAB service that I was aware of.  However, you would normally know whether 
or not the TIOT had already been serialized.  For example, if your code is 
running as part of allocation, it's extremely likely that the TIOT is already 
ENQd.  Yes, there is an option to bypass the ENQ on some services, but that 
would be because you know that it's already in place.  

QNAME:  As implied in the GETDSAB description, the major name is "SYSZTIOT".  

RNAME:  "ASID + DSAB QDB address"  (See MVS Diagnosis: Reference)  

===

 
 
 
<Original Post>  

Gereldy  

The GETDSAB service documentation states as one of the programming 
requirements: 

"The caller must provide or inherit serialization on the SYSZTIOT resource 
before calling the GETDSAB macro and while using the output addresses of the 
macro. The minimum required level of serialization is shared (SHR)." 


What is needed to satisfy this requirement? 

"..provide.." implies some service needs to be performed first. ENQ, and if so 
what would the major/minor be?  

"..inherit.." implies knowing one has the needed serialization already, and how 
is that known?  How would that inheritance persist for the duration of the use 
of GETDSAB? 

</Original Post>  







GETDSAB programming requirements wrt SYSZTIOT   
  This topic is a duplicate of another discussion.    You were redirected here 
from a duplicate topic.    1 post by 1 author    Previous Previous   Page 1   
Next Next   Gereldy   11:44 (1 hour ago)  Other recipients:    The GETDSAB 
service documentation states as one of the programming requirements: "The 
caller must provide or inherit serialization on the SYSZTIOT resource before 
calling the GETDSAB macro and while using the output addresses of the macro. 
The minim The GETDSAB service documentation states as one of the programming 
requirements: 

"The caller must provide or inherit serialization on the SYSZTIOT resource 
before calling the GETDSAB macro and while using the output addresses of the 
macro. The minimum required level of serialization is shared (SHR)." 


What is needed to satisfy this requirement? 

"..provide.." implies some service needs to be performed first. ENQ, and if so 
what would the major/minor be?  

"..inherit.." implies knowing one has the needed serialization already, and how 
is that known?  How would that inheritance persist for the duration of the use 
of GETDSAB? 

</Original Post>  This topic is a duplicate of another discussion.    You were 
redirected here from a duplicate topic.                            Previous 
Previous   Page 1   Next Next     1:44 (1 hour ago)  Other recipients:    The 
GETDSAB service documentation states as one of the programming requirements: 
"The caller must provide or inherit serialization on the SYSZTIOT resource 
before calling the GETDSAB macro and while using the output addresses of the 
macro. The minim                                            
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to