<snip> Curious. I have a "WHOHAS" which shows SYSDSN enqueues on a DSN. On both a z/OS 1.12 and 2.3 system, it shows:
sys1.miglib, OWNERS= 2 ,WAIT EXCLUSIVE= ,WAIT SHARED=, JOBNAME=XCFAS ,TYPE=OWNER ,USE=SHARED, JOBNAME=LLA ,TYPE=OWNER ,USE=SHARED, </snip> And your curiosity is? Perhaps "why XCFAS?" That is how LNKLST processing has worked since 1992 when dynamic LNKLST was implemented. It has been mentioned multiple times over the years. The ENQs are obtained specifically so that someone doing something properly (such as a compress of a LNKLST data set with DISP=OLD, or a delete) will not be able to get through and damage the system (we cannot stop someone who does compress of a LNKLST data set with DISP=SHR from damaging the system). XCFAS happened to be a convenient full-function never-terminating address space in which to obtain the ENQ. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
