some products or utilities will reserve the volume but if you are not in the same MIM PLEX or GRS, I think you're taking a big chance, I'll assume this volume is not a critical, or I'd hope a non critical volume and does not contain any PDS/E's or PDS/E sharing is turned off for that system . if the SMS environment is always the same, this volume is in the same storage pool name and the SMS configuration is kept identical should be OK, I've done it, don't like it but sometime you have to. I'D really be careful not putting anything that NEEDS to be shared , catalogs , loadlibs (PDS/E) TMC, or control datasets that are needed for both system on this volume, but I'll assume its not if its SMS managed. in a perfect world all system should be in the same plex and GRS=STAR, if not don't share datasets/volumes, but working for an outsourcer some clients LPARS did not want to play in the PLEX but there was a need to share some volumes, on this system we turned off PDSE sharing and used MIM to manage resources.
Carmen ----- Original Message ----- From: "RICHARD W. PINION" <[email protected]> To: [email protected] Sent: Wednesday, November 22, 2017 9:44:42 AM Subject: Re: IBM GRS Monitor report It's a long story. But yes we are doing this. The ACDS, COMMDS, and SCDS are not shared. The second system's ACDS and SCDS were derived from the first system's ACDS and SCDS. It was our thinking, perhaps we are wrong, that hardware reserves would protect the integrity of the volume. Using IBM's GRS Monitor, we can see that SYSZVVDS, SYSIGGV2, and SYSVTOC have a scope of reserve. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Carmen Vitullo Sent: Wednesday, November 22, 2017 10:36 AM To: [email protected] Subject: Re: IBM GRS Monitor report [External Email] I must not have had enough coffee, you said you share an SMS managed volume between two systems but they are no in the same plex? is the SMS ACDS and SCDS shared? how do you manage to use RESERVES to manage this volume if not in a GRS environment? MIM? Carmen ----- Original Message ----- From: "RICHARD W. PINION" <[email protected]> To: [email protected] Sent: Wednesday, November 22, 2017 9:30:10 AM Subject: IBM GRS Monitor report We ran IBM's GRS Monitor batch reports and noticed something in one of the reports. Notice the second entry, it has a x'004D'. The reason this is interesting to us is because we are sharing this particular volume between two systems. The second system is not in the GRS Star configuration of the first system. We are using RESERVES to protect the integrity of the resources. And this particular volume has encountered errors, i.e. VTOC entries but no SMS NVR records. And yes, this volume is in a SMS SG which is defined to the two systems. ** RESOURCES USAGE REPORT ** ---------------------------------------------------- ** MAJOR SYSZVVDS ** --------------------- COUNT MAJOR 00008260 SYSZVVDS SCOPE=RESERVE SMFID=DEVA RNL (ML) COUNT MAJOR MINOR 006 00000032 SYSZVVDS TS0007 008 00000004 SYSZVVDS TS0007 ( FIRST TENNESSEE Confidentiality notice: This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer. ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
