Thanks for the response. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Staller, Allan Sent: Wednesday, October 10, 2012 1:53 PM To: [email protected] Subject: Re: Question about Catalogs and VSAM
This is normal GRS behavior (not a GRS issue). The GRS SYSDSN major resource does not include the volser as a minor resource. A better solution would be to move JUNK.DATASET to a common user catalog, or use system symbols in the dataset name. More targeted advice can be provided with a better idea of what you are trying to accomplish. HTH, <snip> We have a SYSPLEX of four LPARs, each LPAR has a separate Master Catalog and a separate User Catalog defined to the Master Catalog. Each Master Catalog has an alias called JUNK, which is defined to a User Catalog. If I define a dataset on all four LPARs called JUNK.DATASET, I have four separate files, each residing in their own SMS Storage Group. If I open the JUNK.DATASET with exclusive control on the first LPAR, I would think that I cannot open the JUNK.DATASET with exclusive control on the other LPARs. Is this correct ? If so, is there a way to get around it ? I am thinking this is a GRS issue but I do not have any proof. </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
