Re: Query: CA-MIM ENQ Processing Mode
[EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]... I'm curious how other shops are 'configured'. We currently use the CA-MII ( Multi-Image Integrity ) and CA-MIA ( Multi-Image Allocation ) products. We are having a discussion/issue regarding the ENQ Processing Mode of CA-MII, which can be either 'SELECT' or 'ALLSYSTEMS. Currently, we use the 'SELECT' ENQ Processing mode of CA-MII. If you have the CA-MII product, which mode do you use, 'SELECT' or 'ALLSYSTEMS? IIRC, if you run a parallel sysplex, you *must* run with PROCESS=ALLSYSTEMS. We changed this years ago and it must be documented in the MIM manuals. Kees. ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. ** -- 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
Re: Query: CA-MIM ENQ Processing Mode
Kees, The only parallel sysplex 'sharing' requirement we have been told is no reserve's are allowed in a GDPS/PPRC Hyperswap environment. CA-MIM has strongly recommended the use of ALLSYSTEMS mode for a number of reasons: ALLSYSTEMS mode allows Unicenter CA-MII to automatically manage all SCOPE=SYSTEMS ENQs at run-time - as it sees them occurring. ALLSYSTEMS mode provides the highest level of resource serialization protection. ALLSYSTEMS mode eliminates data integrity exposures that occur when new ENQs are introduced into your environment unknowingly. ALLSYSTEMS mode eliminates the need for systems programmers to add new ENQ management definitions to Unicenter CA-MII every week or month. ALLSYSTEMS mode is the CA recommended mode of operation for the Unicenter CA-MII product. CA has a document titled: Unicenter CA-MII Data Sharing for z/OS that describes what happens when running CA-MII in SELECT vs. ALLSYSTEMS mode. Its dated March 2005, so its a recent document. I received it from our CA-MIM SysProg, so I don't know if its available on CA's Website. Thanks to all who responded to my query. Glenn Miller --- This message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorised use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. ABN AMRO Bank N.V. (including its group companies) shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. ABN AMRO Bank N.V. (or its group companies) does not guarantee that the integrity of this communication has been maintained nor that this communication is free of viruses, interceptions or interference. --- -- 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
Re: Query: CA-MIM ENQ Processing Mode
On Thu, 22 Sep 2005 20:11:14 -0500, Glenn Miller [EMAIL PROTECTED] wrote: I'm curious how other shops are 'configured'. We currently use the CA-MII ( Multi-Image Integrity ) and CA-MIA ( Multi-Image Allocation ) products. We are having a discussion/issue regarding the ENQ Processing Mode of CA-MII, which can be either 'SELECT' or 'ALLSYSTEMS. Currently, we use the 'SELECT' ENQ Processing mode of CA-MII. If you have the CA-MII product, which mode do you use, 'SELECT' or 'ALLSYSTEMS? We converted to PROCESS=ALLSYSTEMS several years ago. I believe that CA strongly recommends it, but I suspect the majority of MII customers are still PROCESS=SELECT (ALLSYSTEMS is certainly NOT required in parallel sysplex). Really, the only negatives to ALLSYSTEMS are that it requires a global MII restart to implement and that all RESERVES are converted to global ENQs unless GDIF=NO is specified for the RESERVE's QNAME. We'd prefer to keep the RESERVE unless we specifically ask to convert it. That was my only concern going in, but we haven't experienced any negative repercussions converting RESERVEs we weren't expecting. The GRS Monitor can help identify SYSTEMS ENQs that MIM is not processing. Also, if you do this make sure you have SET GDIF COUNT=SYSTEMS and issue DISPLAY COUNTS commands before and after the change. I was amazed at the number of SYSTEMS ENQs we were not serializing because we didn't specifically code them in the QNAME list. I sleep a lot better at night now. I can't think of many valid reasons for running with PROCESS=SELECT. You're certainly setting yourself up for trouble if some new component/product/application comes along issuing SYSTEMS ENQs expecting them to be serialized. Dave -- 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
Re: Query: CA-MIM ENQ Processing Mode
On Fri, 23 Sep 2005 14:18:50 -0500, Dave Danner [EMAIL PROTECTED] wrote: Also, if you do this make sure you have SET GDIF COUNT=SYSTEMS and issue DISPLAY COUNTS commands before and after the change. I was amazed at the number of SYSTEMS ENQs we were not serializing because we didn't specifically code them in the QNAME list. I sleep a lot better at night now. I guess I should look into having it changed in our environment for this reason alone. It would have avoided a recent problem we had with Compuware's LMS after we upgraded to V3. Their LMSEXIT STC updates license information in a shared VSAM control file (the file doesn't have to be shared) on multiple LPARs and kicks off at the same time on all LPARs. Of course this led to problems. We did resolve the problem by adding an undocumented QNAME to MII after talking to Compuware support. I've probably not run into issues with PROCESS=SELECT at this shop or others in the past because most products that issue special ENQs or RESERVES document them in their installation guides or at least their system programming guides. RESERVEs are not an issue regardless of the PROCESS= setting. You can always find the ones your not processing with a DISPLAY COUNTS command. Cheers, Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America and Farmers Insurance Group mailto: [EMAIL PROTECTED] Systems Programming expert at http://Search390.com/ateExperts/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- 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
Re: Query: CA-MIM ENQ Processing Mode
On Sep 23, 2005, at 5:19 PM, Mark Zelden wrote: ---SNIP-- RESERVEs are not an issue regardless of the PROCESS= setting. You can always find the ones your not processing with a DISPLAY COUNTS command. Cheers, Mark ark, In previous years, (SDSI and MIM) put out the enq counts when the product ended. For some reason (I never did an explanation as to why they stopped doing so) they stopped giving out a 1 page total of counts. This was sorely missed as I always looked at the report to find any new enq's that were being issued so I could call the vendor and see if they could be included in (SDSI/MIM) . The only thing that I could get out of them is to have an operator issue the command to get the report. Most operators have hard enough time IPLing let alone shutting the system down. So how can you expect operators to issue *ANOTHER COMMAND*? I got nowhere with the CA-MIM people . Having a document on how to shutdown the system was useless as the operators (and their bosses) thought it was too much work to do. Having Automated Ops do it wasn't an option as they were too cheap to spend the $$ for it. One shop couldn't IPL (sysprogs were called in to do so). Even with typed instructions it was hopeless. There were vendors out there that issued enq's and unless you saw the report you had no way of getting the info as the installation doc (usually) never mentioned that they did. I caught one vendor who denied they issued the ENQ and I showed them in a trace that they were the issuer. I would have been happy if CA/MIM would have an option in the parms to create the report. Seems simple correct? Not with CA-MIM. FWIW SDSI was written by Duquesne Systems in Pittsburg for a company that I was working at. Glen Chatfield(sp?) was the main coder . Ed -- 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
Query: CA-MIM ENQ Processing Mode
I'm curious how other shops are 'configured'. We currently use the CA-MII ( Multi-Image Integrity ) and CA-MIA ( Multi-Image Allocation ) products. We are having a discussion/issue regarding the ENQ Processing Mode of CA-MII, which can be either 'SELECT' or 'ALLSYSTEMS. Currently, we use the 'SELECT' ENQ Processing mode of CA-MII. If you have the CA-MII product, which mode do you use, 'SELECT' or 'ALLSYSTEMS? Thank you for your time. Glenn Miller PS: To display your CA-MII ENQ Processing mode, use the following command: F MIMx,D GDIF INIT You should see the following on the console: MIM1019 GDIF INIT DISPLAY EXEMPT=MIIXEMPT MISMATCHQNAME=ACCEPT NMCOUNT=255 PROCESS=SELECTRESERVES=CONVERT TEMPORARYDSN=YES The PROCESS= should be either SELECT or ALLSYSTEMS --- This message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorised use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. ABN AMRO Bank N.V. (including its group companies) shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. ABN AMRO Bank N.V. (or its group companies) does not guarantee that the integrity of this communication has been maintained nor that this communication is free of viruses, interceptions or interference. --- -- 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
