ca mim for z/os - 12.5 best practices · ca mim for z/os - 12.5 best practices. ... and ibm...

13-Jul-2016Date:

CA MIM for z/OS - 12.5Best Practices

CA MIM for z/OS - 12.5

13-Jul-2016 3/35

This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation is proprietary information of CA and may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA.

If you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy.

The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.

The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice.

The manufacturer of this Documentation is CA.

Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.

Copyright 2016 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Best Practices 4

Table of Contents

CA MIM Best Practices for Installation ........................................................ 7Install Using CA CSM .................................................................................................................................. 7

Implement a Proactive Preventive Maintenance Strategy ........................................................................... 7

Keep Current on CA Common Services ...................................................................................................... 9

Install on Test System First ......................................................................................................................... 9

Apply Current IBM APARS ........................................................................................................................ 10

Check Parmlib Syntax ............................................................................................................................... 10

Best Practices for General CA MIM Configuration .................................... 11Support ...................................................................................................................................................... 11

COMPATLEVEL ........................................................................................................................................ 12

Use Restart Manager ................................................................................................................................ 12

HYPERSTAR ............................................................................................................................................ 12

Message Prefixing ..................................................................................................................................... 13

Separate Address Spaces ......................................................................................................................... 14

Backup Control Files ................................................................................................................................. 15

DASD Control File Placement ................................................................................................................... 15

Channel Paths for CTC Devices ............................................................................................................... 16

Backup CTC .............................................................................................................................................. 16

Tracing ...................................................................................................................................................... 17

MIMMSGS ................................................................................................................................................. 17

ACF2 NO-SMC .......................................................................................................................................... 17

Use Restart Manager ................................................................................................................................ 18

VCF Multiple Eligible Masters ................................................................................................................... 18

VARY DEDUPLICATION Health Check .................................................................................................... 19

Control File AUTOTUNE ........................................................................................................................... 19

Best Practices for CA MIA Configuration .................................................. 20Use Delay Detection and Notification ........................................................................................................ 20

Tape Device Group Lock Delays ............................................................................................................... 21

Limit VARY Commands ............................................................................................................................. 21

Best Practices 5

VARY Command Placement ..................................................................................................................... 22

VARY REQUEUE NOTIFICATION ........................................................................................................... 22

VARY DEDUPLICATION .......................................................................................................................... 23

DIAGNOSE ALL ........................................................................................................................................ 24

Automate DIAGNOSE ALL Command ...................................................................................................... 25

Limit SHUTDOWN FREE .......................................................................................................................... 25

Use SYSDUMP Command ........................................................................................................................ 26

Restarting CA MIA in an Active MIAPlex ................................................................................................... 26

Best Practices for CA MII Configuration .................................................... 28PROCESS=ALLSYSTEMS and GDIF ....................................................................................................... 28

PAGEFIX=COND ...................................................................................................................................... 29

GDIF COUNT Settings .............................................................................................................................. 29

Exempt Statements in GDIF Exempt List .................................................................................................. 30

Start with the Early Start Mechanism ........................................................................................................ 30

Preferred VCF Master ............................................................................................................................... 31

Control File Sizing ..................................................................................................................................... 31

SMF RECORDING .................................................................................................................................... 32

Dispatching Priority ................................................................................................................................... 32

Best Practices for CA MIC Configuration .................................................. 34Use COLLECT SYSID=EXTERNAL .......................................................................................................... 34

COLLECT Command and Non-existent Consoles .................................................................................... 34


13-Jul-2016 6/35

Best PracticesThis section introduces the CA Technologies mainframe management strategy and features, and describes the best practices for installing and configuring your product.

The intended audience of this content is systems programmers and administrators who install, maintain, deploy, and configure your product.

CA MIM Best Practices for Installation (see page 7)Best Practices for General CA MIM Configuration (see page 11)Best Practices for CA MIA Configuration (see page 20)Best Practices for CA MII Configuration (see page 28)Best Practices for CA MIC Configuration (see page 34)


13-Jul-2016 7/35

CA MIM Best Practices for InstallationReview the installation best practices provided in this section.

Install Using CA CSM (see page 7)Implement a Proactive Preventive Maintenance Strategy (see page 7)Keep Current on CA Common Services (see page 9)Install on Test System First (see page 9)Apply Current IBM APARS (see page 10)Check Parmlib Syntax (see page 10)

Install Using CA CSMUse the CA Chorus Software Manager (CA CSM) to acquire, install, and maintain your product.

Business Value:

CA CSM provides a web interface, which works with Electronic Software Delivery (ESD) and standardized installation, to provide a common way to manage CA mainframe products. You can use it to download and install CA MIM for z/OS.

CA CSM lets you download product and maintenance releases over the Internet directly to your system from the CA Support website. After you use CA CSM to download your product or maintenance, you use the same interface to install the downloaded software packages using SMP/E.

Additional Considerations:

After you install the product, follow the appropriate steps in the CA MIM for z/OS Installation (to set it up. CA CSM can continue to help you https://docops.ca.com/display/CMFZS125/Installation)

maintain CA MIM for z/OS.

More Information:

For more information about CA CSM, see the . For more CA Chorus Software Manager Guideinformation about product setup, see the CA MIM for z/OS Installation (https://docops.ca.com/display

./CMFZS125/Installation)

Implement a Proactive Preventive Maintenance Strategy

CA Technologies formerly delivered product maintenance using Service Packs. We have replaced this model with CA Recommended Service (CARS) for z/OS (https://support.ca.com/irj/portal/anonymous

, which provides more flexibility and granular application intervals. /phpsupcontent?contentID=244552)CA RS is patterned after the IBM preventive maintenance model, Recommended Service Upgrade

(RSU). With CA RS, you can install preventive maintenance for most CA Technologies z/OS-based

https://docops.ca.com/display/CMFZS125/Installationhttps://docops.ca.com/display/CMFZS125/Installationhttps://docops.ca.com/display/CMFZS125/Installationhttps://docops.ca.com/display/CMFZS125/Installationhttps://docops.ca.com/display/CMFZS125/Installationhttps://docops.ca.com/display/CMFZS125/Installationhttps://support.ca.com/irj/portal/anonymous/phpsupcontent?contentID=244552https://support.ca.com/irj/portal/anonymous/phpsupcontent?contentID=244552https://support.ca.com/irj/portal/anonymous/phpsupcontent?contentID=244552


13-Jul-2016 8/35

(RSU). With CA RS, you can install preventive maintenance for most CA Technologies z/OS-based products in a consistent way on a schedule that you select (for example, monthly, quarterly, annually).

We recommend that you develop and implement a proactive preventive maintenance strategy whereby you regularly apply maintenance. You could follow the same schedule that you use to apply IBM maintenance, or you could implement a schedule for CA Technologies products only.

Business Value:

Keeping your products current with maintenance helps your team remain productive and minimize errors while safely protecting your systems. If you do not install preventive maintenance regularly, you risk encountering known problems for which we have published and tested fixes.

Our mainframe maintenance philosophy is predicated upon granting you the flexibility to maintain your sites and systems consistent with industry best practices and site-specific requirements. Our philosophy focuses on two maintenance types. Understanding each type can help you maintain your systems in the most efficient manner.

Note: This philosophy applies to the CA Data Center Management stack products (. For legacy products, https://support.ca.com/phpdocs/0/8319/mainframe20_support.html)

contact CA Support for maintenance details.

Corrective MaintenanceHelps you address a specific and immediate issue. This type of maintenance is necessary after you encounter a problem. We may provide a test APAR when a new problem is uncovered, or a confirmed PTF when the problem has been resolved. Your primary goal is to return your system to the same functional state that it was before you experienced the issue. This type of maintenance is applied on an as-needed basis.

Preventive MaintenanceLets you apply PTFs that we have created and made public. You may have experienced the issues that each PTF addresses. CA RS provides a way to identify all published maintenance that has been successfully integration-tested. This maintenance has been tested with other CA Technologies products, current z/OS releases, and IBM subsystems, such as CICS and DB2. Major CA RS service levels are published quarterly, with updates for HIPER and PE-resolving PTFs that are published monthly. After you test the CA RS level, we recommend that you accept that level before you apply a new CA RS level.You can initiate a maintenance installation activity at any time. You can then install the current CA RS level of maintenance (recommended) or an earlier level. Additionally, you can install maintenance to support a new hardware device, software upgrade, or function using our FIXCAT (https://support.ca.com/irj/portal/anonymous/phpsupcontent?contentID=%7b1426C7AF-3D50-49C1-ACE7-

method.FCC325DCC1B0%7d)

For all maintenance, you initiate any maintenance action, obtain the current SMP/E before HOLDDATA.

https://support.ca.com/phpdocs/0/8319/mainframe20_support.htmlhttps://support.ca.com/phpdocs/0/8319/mainframe20_support.htmlhttps://support.ca.com/phpdocs/0/8319/mainframe20_support.htmlhttps://support.ca.com/irj/portal/anonymous/phpsupcontent?contentID=%7b1426C7AF-3D50-49C1-ACE7-FCC325DCC1B0%7dhttps://support.ca.com/irj/portal/anonymous/phpsupcontent?contentID=%7b1426C7AF-3D50-49C1-ACE7-FCC325DCC1B0%7dhttps://support.ca.com/irj/portal/anonymous/phpsupcontent?contentID=%7b1426C7AF-3D50-49C1-ACE7-FCC325DCC1B0%7dhttps://support.ca.com/irj/portal/anonymous/phpsupcontent?contentID=%7b1426C7AF-3D50-49C1-ACE7-FCC325DCC1B0%7d


13-Jul-2016 9/35

Important! CA Chorus Software Manager (CA CSM) (https://support.ca.com/irj/portal - formerly known as CA Mainframe Software /prddtlshome?prdhmpgform=p&productID=8319)

Manager (CA MSM) - is an intuitive web-based tool that can automate and simplify many CA Technologies product installation and maintenance activities. We strongly recommend that you use CA CSM to maintain your CA Technologies z/OS-based products.

More Information:

To apply preventive maintenance using CA CSM or from CA Support Online on , see the Installation for your product and the CA CSM online help.Guide

Keep Current on CA Common ServicesMake sure you have installed the most current release of CA Common Services.

Business Value:

The latest release of CA Common Services contains the most current infrastructure updates allowing you to use newer features of CA MIM, including licensing changes, service desk integration, and product health checks. Staying on the current release and maintenance of CA Common Services helps you avoid previous issues, allowing you to enjoy full features and functionality of the most current product.

More Information:

For more information on CA Common Services, see the CA MIM CCS for z/OS Component Requirements (https://docops.ca.com/pages/viewpage.action?pageId=95326654)

Install on Test System FirstPerform your installation and initial evaluations of the product and its components on a test system. New releases of CA MIM for z/OS are always compatible with previous releases, letting you run a new release on a test system while still running the older version on a production system.

Business Value:

Evaluating CA MIM for z/OS in a test environment helps you detect any possible problems before you roll out the product to a production system.

https://support.ca.com/irj/portal/prddtlshome?prdhmpgform=p&productID=8319https://support.ca.com/irj/portal/prddtlshome?prdhmpgform=p&productID=8319https://support.ca.com/irj/portal/prddtlshome?prdhmpgform=p&productID=8319https://docops.ca.com/pages/viewpage.action?pageId=95326654https://docops.ca.com/pages/viewpage.action?pageId=95326654


13-Jul-2016 10/35

Apply Current IBM APARSReview our current list of IBM APARs that could affect CA MIM for z/OS and install them as appropriate for your environment.

Business Value:

Having current IBM APARS installed can help you avoid potential problems that may affect the operation or performance of CA MIM for z/OS due to changes in the z/OS operating system.

More Information:

For a list of IBM APARs that affect CA MIM for z/OS, see the Release Notes (https://docops.ca.com. You can also find the most current list of IBM APARs on the CA MIM /display/CMFZS125/Release+Notes)

for z/OS page of CA Support Online.

Check Parmlib SyntaxBefore starting CA MIM for z/OS components, check for parmlib statement syntax errors using the CA MIM for z/OS SyntaxSCAN Utility.

Business Value:

Syntax errors in parmlib statements can cause problems at run time. The CA MIM for z/OS SyntaxSCAN Utility checks CA MIM for z/OS parmlib statements and commands for such errors so you can correct them before starting CA MIM for z/OS.

Additional Considerations:

The CA MIM for z/OS SyntaxSCAN Utility runs as a started task and interrogates various CA MIM for z/OS parmlib members.

When started, the utility simulates CA MIM for z/OS address space activation. Statements and commands found in the CA MIM for z/OS parmlib members are parsed and checked for errors, all errors are noted, and the utility ends.

More Information:

For more information about using this utility, see the section Parmlib SyntaxSCAN Utility in the .Programming (https://docops.ca.com/display/CMFZS125/CA+MIM+Programming)

https://docops.ca.com/display/CMFZS125/Release+Noteshttps://docops.ca.com/display/CMFZS125/Release+Noteshttps://docops.ca.com/display/CMFZS125/Release+Noteshttps://docops.ca.com/display/CMFZS125/CA+MIM+Programminghttps://docops.ca.com/display/CMFZS125/CA+MIM+Programming


13-Jul-2016 11/35

Best Practices for General CA MIM Configuration

This section describes general best practices to configure CA MIM for z/OS for optimal performance.Support (see page 11)COMPATLEVEL (see page 12)Use Restart Manager (see page 12)FEATURE=HYPERSTAR (see page 12)Message Prefixing (see page 13)Separate Address Spaces (see page 14)Backup Control Files (see page 15)Control File Placement (see page 15)Channel Paths for CTC Devices (see page 16)Backup CTC (see page 16)Tracing (see page 17)MIMMSGS (see page 17)ACF2 NO-SMC (see page 17)Use Restart Manager v12.1.0 (see page 18)VCF Multiple Eligible Masters (see page 18)VARY DEDUPLICATION Health Check 1 (see page 19)Control File AUTOTUNE (see page 19)

SupportMake sure that you are running a currently supported version of CA MIM for z/OS.

You can determine which release you are running by issuing the following command:

F MIM,DISPLAY FACILITIES

Business Value

To obtain full support from CA Support, you must be running a supported version of the product.

Health Check

None

Reference

For more information, see: CA MIM Resource Sharing Release and Support Lifecycle Dates (http://www.ca.com/us/support/ca-support-online/product-content/status/support-life-cycle/indexes/ca-mim-resource-sharing-release-and-support-lifecycle-dates.aspx)

http://www.ca.com/us/support/ca-support-online/product-content/status/support-life-cycle/indexes/ca-mim-resource-sharing-release-and-support-lifecycle-dates.aspxhttp://www.ca.com/us/support/ca-support-online/product-content/status/support-life-cycle/indexes/ca-mim-resource-sharing-release-and-support-lifecycle-dates.aspxhttp://www.ca.com/us/support/ca-support-online/product-content/status/support-life-cycle/indexes/ca-mim-resource-sharing-release-and-support-lifecycle-dates.aspxhttp://www.ca.com/us/support/ca-support-online/product-content/status/support-life-cycle/indexes/ca-mim-resource-sharing-release-and-support-lifecycle-dates.aspx


13-Jul-2016 12/35

COMPATLEVELVerify that CA MIM is running at the current highest supported COMPATLEVEL.

You determine the COMPATLEVEL the MIMplex is currently running at by entering the following command:

F MIM,DISPLAY INIT

Business Value:

Running at the current highest supported COMPATLEVEL allows CA MIM to take advantage of all features for the release.

More Information:

For more information, see:

How You Activate New Features with ACTIVATE COMPATLEVEL (https://docops.ca.com/display/CMFZS/How+You+Activate+New+Features+with+ACTIVATE+COMPATLEVEL)

How You Use ACTIVATE COMPATLEVEL with Checkpoint Files (https://docops.ca.com/display/CMFZS/How+You+Use+ACTIVATE+COMPATLEVEL+with+Checkpoint+Files)

(MIM) ACTIVATE Command-Activate (https://docops.ca.com/display/CMFZS/%28MIM%29+ACTIVATE+Command-Activate)

Selectable Features (https://docops.ca.com/display/CMFZS/Selectable+Features)

Use Restart ManagerBusiness Value:This feature provides the capability to restart CA MIM components automatically after a failure, or to perform a planned restart on a single system. When used with CA MII, the restart manager maintains the integrity of global resources throughout the process. Local ENQ/DEQ activity is suspended for managed QNAMEs from the instant a failure is detected or a LOADLIB REFRESHFROM command is issued. Activity remains suspended until the restart is complete and normal global operation resumes.

More Information:For more information, see Restart Manager Usage.

HYPERSTARIf you are running in a Virtual Control File (VCF) environment, verify that the HYPERSTAR feature is activated.

You determine which features are active by entering the following command:

https://docops.ca.com/display/CMFZS/How+You+Activate+New+Features+with+ACTIVATE+COMPATLEVELhttps://docops.ca.com/display/CMFZS/How+You+Activate+New+Features+with+ACTIVATE+COMPATLEVELhttps://docops.ca.com/display/CMFZS/How+You+Use+ACTIVATE+COMPATLEVEL+with+Checkpoint+Fileshttps://docops.ca.com/display/CMFZS/How+You+Use+ACTIVATE+COMPATLEVEL+with+Checkpoint+Fileshttps://docops.ca.com/display/CMFZS/%28MIM%29+ACTIVATE+Command-Activatehttps://docops.ca.com/display/CMFZS/%28MIM%29+ACTIVATE+Command-Activatehttps://docops.ca.com/display/CMFZS/Selectable+Features


13-Jul-2016 13/35

You determine which features are active by entering the following command:

F MIM,DISPLAY FEATURE

Best Practice

For a MIMplex that has three or more active systems, you can improve the performance of Virtual Control Files (VCF) by activating the Hyperstar feature. When this feature is active, CA MIM examines a ''look ahead list'' of systems waiting for the VCF. If the list is not empty, and the client has a CTC or XCF path to the next system in the list, the client transfers the VCF directly to that system instead of the master.

The primary effect of Hyperstar is to reduce the amount of VCF I/O performed by the VCF master system. This action reduces the amount of CPU time that is used on the master system, reduces the control file access times and increases global ENQ and RESERVE throughput across all systems in the MIMplex.

Health Check

The MIM_DRVR_HYPERSTAR Health check verifies that the Hyperstar feature is active when running in a VCF environment. This health check is a low severity health check that will run at whenever the state of Hyperstar changes.

More Information:

For more information, see .Hyperstar (https://docops.ca.com/display/CMFZS/HYPERSTAR)

How You Activate New Features with ACTIVATE FEATURE (https://docops.ca.com/display/CMFZS/How+You+Activate+New+Features+with+ACTIVATE+FEATURE)

How You Use ACTIVATE FEATURE with Checkpoint Files (https://docops.ca.com/display/CMFZS/How+You+Use+ACTIVATE+FEATURE+with+Checkpoint+Files)

(MIM) ACTIVATE Command-Activate (https://docops.ca.com/display/CMFZS/.%28MIM%29+ACTIVATE+Command-Activate+v12.1.0)

Message PrefixingWhen running CA MIM components in multiple address spaces, set the MSGPREFIX value to one of the following:

CMDPREFIX

Specifies that the command prefix string as specified by the MIMINIT CMDPREFIX statement or the SETOPTION MIM CMDPREFIX command is prefixed to all messages issued by CA MIM.

ppp

Replaces the characters 'MIM' in messages issued by CA MIM. These three characters correspond to the CA MIM address space generating the message. For example, MIM0067I becomes MIA0067I, when issued from an address space running the CA MIA Tape Sharing component.

https://docops.ca.com/display/CMFZS/HYPERSTARhttps://docops.ca.com/display/CMFZS/How+You+Activate+New+Features+with+ACTIVATE+FEATUREhttps://docops.ca.com/display/CMFZS/How+You+Activate+New+Features+with+ACTIVATE+FEATUREhttps://docops.ca.com/display/CMFZS/How+You+Use+ACTIVATE+FEATURE+with+Checkpoint+Fileshttps://docops.ca.com/display/CMFZS/How+You+Use+ACTIVATE+FEATURE+with+Checkpoint+Fileshttps://docops.ca.com/display/CMFZS/.%28MIM%29+ACTIVATE+Command-Activate+v12.1.0https://docops.ca.com/display/CMFZS/.%28MIM%29+ACTIVATE+Command-Activate+v12.1.0


13-Jul-2016 14/35

Note: The default value of MSGPREFIX is NONE.

Business Value

This parameter lets each CA MIM address space uniquely identify its own CA MIM messages. Changing the format of the CA MIM messages helps system operators and programmers easily identify the CA MIM address space from which a particular message originated.

Health Check

None

More Information


(MIM) MIMINIT Statement-Define Initialization Values (https://docops.ca.com/display/CMFZS/.%28MIM%29+MIMINIT+Statement-Define+Initialization+Values+v12.1.0)

Separate Address SpacesRun CA MII Data Sharing in a separate address space from CA MIA Tape Sharing.

Business Value:

CA MIM supports the activation of any combination of MIM facilities within a single CA MIM address space. To achieve optimal ENQ service times, it is a CA MIM best practice to activate the Global Data Integrity Facility (GDIF) in a separate address space as the Global Tape Allocation Facility (GTAF). Eliminating GTAF activity from the CA MIM address space will improve GDIF ENQ service times and reduce overall CPU utilization.

Another benefit of running the GDIF and GTAF facilities in separate address spaces is that problems affecting one faciity will not affect the other. For example, if you run both facilities in a single CA MIM address space, a problem involving the tape resource management may adversely affect DASD resource management. Running CA MIM facilities in separate address spaces will limit the impact facility-specific problems will have on your data-sharing environment.

Health Check

The MIM_GDIF_GTAF_ISOLATION health check verifies that GTAF and GDIF are not active in the same CA MIM address space. This heath check is a medium severity, one-time check that occurs during CA MIM initialization.

Reference


Running Components in Separate Address Spaces (https://docops.ca.com/display/CMFZS/Running+Components+in+Separate+Address+Spaces)

https://docops.ca.com/display/CMFZS/.%28MIM%29+MIMINIT+Statement-Define+Initialization+Values+v12.1.0https://docops.ca.com/display/CMFZS/.%28MIM%29+MIMINIT+Statement-Define+Initialization+Values+v12.1.0https://docops.ca.com/display/CMFZS/Running+Components+in+Separate+Address+Spaceshttps://docops.ca.com/display/CMFZS/Running+Components+in+Separate+Address+Spaces


13-Jul-2016 15/35

Backup Control FilesMake sure alternate or backup DASD control files or XES list structures are available to CA MIM for z/OS.

Business Value

CA MIM uses backup or control files if the current control file becomes unusable. If an error alternateis encountered on the primary control files and no backup control file exists, CA MIM terminates on all systems. Employing this best practice helps prevent product system outages and potential data integrity exposures.

Health Check

The MIM_DRVR_CF_STATUS health check periodically checks defined control files to determine if all are usable (can be written and read by CA MIM), and raises an exception if any allocated control file is not usable. This heath check is a medium severity, one-time check that occurs during CA MIM initialization.

Reference

For more information see:

Allocate DASD Control Files (https://docops.ca.com/display/CMFZS/.How+You+Allocate+Control+and+Checkpoint+Files+v12.1.0#id-.HowYouAllocateControlandCheckpointFilesv12.1.0-AllocateDASDControlFiles)

Performance Considerations (https://docops.ca.com/display/CMFZS/Performance+Considerations)

DASD Control File PlacementVerify that the CA MIM control files are located on a relatively isolated volume with no other RESERVE activity and verify that the DASD unit is connected using channel paths that are not being over-utilized.

Business Value:

Where you place the CA MIM DASD control file can impact the performance of CA MIM for z/OS, and subsequently, the performance of your entire complex. The CA MIM address space on each system contends for access to the DASD control file by issuing hardware reserve requests. Access to the control file is serialized, because only one system can reserve the control file at any point in time. Non-MIM use of the DASD device will affect CA MIM throughput and performance.

Place the CA MIM control file on DASD units that do not meet these criteria to ensure increased performance and MIMplex-wide system throughput.

More Information:

See the CA MIM Programming section titled: "DASD Control Files (https://docops.ca.com/display/CMFZS"/DASD+Control+Files)

https://docops.ca.com/display/CMFZS/.How+You+Allocate+Control+and+Checkpoint+Files+v12.1.0#id-.HowYouAllocateControlandCheckpointFilesv12.1.0-AllocateDASDControlFileshttps://docops.ca.com/display/CMFZS/.How+You+Allocate+Control+and+Checkpoint+Files+v12.1.0#id-.HowYouAllocateControlandCheckpointFilesv12.1.0-AllocateDASDControlFileshttps://docops.ca.com/display/CMFZS/.How+You+Allocate+Control+and+Checkpoint+Files+v12.1.0#id-.HowYouAllocateControlandCheckpointFilesv12.1.0-AllocateDASDControlFileshttps://docops.ca.com/display/CMFZS/Performance+Considerationshttps://docops.ca.com/display/CMFZS/DASD+Control+Fileshttps://docops.ca.com/display/CMFZS/DASD+Control+Fileshttps://docops.ca.com/display/CMFZS/DASD+Control+Files


13-Jul-2016 16/35

Channel Paths for CTC DevicesMake sure that the channel paths associated with the CA MIM for z/OS CTC devices are not over-utilized or experiencing high channel path busy rates.

Business Value

High-performing channel paths can help prevent unnecessary CTC I/O delays, allowing global ENQs to be processed much faster.

Health Check

none

Reference

For more information, see How You Define CTC Devices for Use in VCF Environments (https://docops.ca.com/display/CMFZS/.How+You+Define+CTC+Devices+for+Use+in+VCF+Environments+v12.1.0)

Backup CTCIf you are running with a Virtual Control file utilizing CTC paths, you should define at least two backup or alternate CTC addresses for each system in your MIMplex. You can define up to 15 alternate CTC paths between any two systems.

Business Value

Configuring alternate CTC addresses for your CA MIM for z/OS address space allows for additional recovery options if the primary CTC address has an error. This helps to guarantee uninterrupted communication between systems.

Health Check

None

Reference

For more information, see

How You Define CTC Devices for Use in VCF Environments (https://docops.ca.com/display/CMFZS/.How+You+Define+CTC+Devices+for+Use+in+VCF+Environments+v12.1.0)

Configure CTCPATH Statements for Disaster Recovery (https://docops.ca.com/display/CMFZS/Configure+CTCPATH+Statements+for+Disaster+Recovery)

https://docops.ca.com/display/CMFZS/.How+You+Define+CTC+Devices+for+Use+in+VCF+Environments+v12.1.0https://docops.ca.com/display/CMFZS/.How+You+Define+CTC+Devices+for+Use+in+VCF+Environments+v12.1.0https://docops.ca.com/display/CMFZS/.How+You+Define+CTC+Devices+for+Use+in+VCF+Environments+v12.1.0https://docops.ca.com/display/CMFZS/.How+You+Define+CTC+Devices+for+Use+in+VCF+Environments+v12.1.0https://docops.ca.com/display/CMFZS/.How+You+Define+CTC+Devices+for+Use+in+VCF+Environments+v12.1.0https://docops.ca.com/display/CMFZS/Configure+CTCPATH+Statements+for+Disaster+Recoveryhttps://docops.ca.com/display/CMFZS/Configure+CTCPATH+Statements+for+Disaster+Recovery


13-Jul-2016 17/35

TracingMake sure CA MIM for z/OS tracing is turned off.

Business Value

Having tracing turned on all the time can cause unnecessary overhead. Tracing should be activated only when you are diagnosing a specific problem.

Health Check

None

Reference


How You Activate Tracing (https://docops.ca.com/display/CMFZS/.How+You+Activate+Tracing+v12.0)

MIMMSGSIf you use MIMMSGS members to customize messages, then make sure that you are using the latest MIMMSGS members. If you do not customize CA MIM message members, then do not use MIMMSGS members.

Business Value:

MIMMSGS members contain the attributes of various CA MIM for z/OS messages and are customizable. Sometimes, message attributes change as product maintenance is published, and it is important to refresh the various members when you install a new product release or service pack. If you do not customize your messages, then the MIMMSGS members can be omitted.

Health CheckNone

Reference:

For more information, see MIMMSGS Message Table (https://docops.ca.com/display/CMFZS/MIMMSGS+Message+Table)

ACF2 NO-SMCAdd the NO-SMC attribute on the CA ACF2 logon ID record for the CA MIM for z/OS address space.

Best Practice

https://docops.ca.com/display/CMFZS/.How+You+Activate+Tracing+v12.0https://docops.ca.com/display/CMFZS/MIMMSGS+Message+Tablehttps://docops.ca.com/display/CMFZS/MIMMSGS+Message+Tablehttps://docops.ca.com/display/CMFZS/MIMMSGS+Message+Table


13-Jul-2016 18/35

Setting the NO-SMC attribute to the CA MIM for z/OS address space will ensure that concurrent security requests in the CA MIM for z/OS address space, which require access to the CA ACF2 databases, do not get single threaded and result in possible system suspends.

Health Check

The MIM_GDIF_ACF2_NOSMC health check verifies the CA ACF2 logon ID record of the CA MIM for z/OS address space has the NO-SMC attribute set. This is a high-severity, one-time check that runs when GDIF is started.

Reference

See Step 13 in the .CA ACF2 Installation Guide (http://All%20Guides%20with%20Searchable%20Index)

Use Restart ManagerConfigure MIM to use the Restart Manager.

Business Value

The Restart Manager provides the capability to restart CA MIM for z/OS components automatically after a failure or to perform a planned restart on a single system. When used with CA MII, Restart Manager maintains the integrity of global resources throughout the restart process. Local ENQ/DEQ activity is suspended for managed QNAMEs from the instant a failure is detected or a LOADLIB REFRESHFROM command is issued. Activity remains suspended until the restart is complete and normal global operation resumes.

Health Check

The MIM_GDIF_RESTART_MNGR health check verifies that GDIF is started with the Restart Manager feature active. This heath check is a medium severity, one-time check that occurs during CA MIM initialization.

Reference


Restart Manager Usage (https://docops.ca.com/display/CMFZS/.Restart+Manager+Usage+v12.1.0).

How to Set Up Restart Manager (https://docops.ca.com/display/CMFZS/.How+to+Set+Up+Restart+Manager+v12.1.0)

How to Use Restart Manager to Apply Maintenance Dynamically (https://docops.ca.com/display/CMFZS/.How+to+Apply+Maintenance+Updates+Without+Restarting+Your+System+Dynamically+v12.1.0)

VCF Multiple Eligible MastersBusiness Value:

http://All%20Guides%20with%20Searchable%20Indexhttps://docops.ca.com/display/CMFZS/.Restart+Manager+Usage+v12.1.0https://docops.ca.com/display/CMFZS/.How+to+Set+Up+Restart+Manager+v12.1.0https://docops.ca.com/display/CMFZS/.How+to+Set+Up+Restart+Manager+v12.1.0https://docops.ca.com/display/CMFZS/.How+to+Apply+Maintenance+Updates+Without+Restarting+Your+System+Dynamically+v12.1.0https://docops.ca.com/display/CMFZS/.How+to+Apply+Maintenance+Updates+Without+Restarting+Your+System+Dynamically+v12.1.0


13-Jul-2016 19/35

When running CA MIM with a Virtual Control File (VCF), at least one system must be designated as being master eligible. It is a CA MIM best practice to have at least a secondary master eligible system so that if the current master is unable to continue managing the VCF, management responsibility is passed to a new master. Ideally all systems in a MIMplex should have a CTC or XCF path to all other systems in the MIMplex so that all systems are eligible to become the master system. This redundancy provides the best recovery options.

Health Check

The MIM_DRVR_VCF_MSTR ELGBL health check verifies that at least one system is eligible to _become the master system. The health check runs one minute after a request for the check is made. For example, a request to run the health check is made when a change to the master preference list is recognized. The health check is added as INACTIVE, then activated 1 minute after the VCF becomes active. If a switch to a physical control file is made, the health check is deactivated and will show as INACTIVE. If fewer than three systems are currently active, the health check will show SUCCESS. This heath check is a medium severity check and can be run in many difference scenarios depending on master eligibility.

Reference:

For more information, see How you Select Master Systems (https://docops.ca.com/display/CMFZS/How+You+Select+Master+Systems)

VARY DEDUPLICATION Health CheckThis health check was added to raise awareness of when the SETOPTION VARYDEDUP is set to NO.

CA MIA serializes VARY ONLINE processing with z/OS allocation processes on all active systems in the MIAplex while z/OS acquires SYSIEFSD ENQs to serialize VARY processing with allocation on the local system. Redundant VARY commands that do not change the state of the target device can be automatically discarded. Elimination of duplicate VARY commands removes the processing overhead that is incurred for CA MIA and z/OS serialization of redundant VARY commands.

Control File AUTOTUNEWhen the AUTOTUNE option is enabled, MIM will periodically evaluate the recent transaction process rate, i.e., the average number of transactions processed per CF cycle during the evaluation interval. If the rate is too high, the effective interval will be lowered; if too low, the effective interval will be raised, but never higher than the current SETOPTION INTERVAL value.

https://docops.ca.com/display/CMFZS/How+You+Select+Master+Systemshttps://docops.ca.com/display/CMFZS/How+You+Select+Master+Systemshttps://docops.ca.com/display/CMFZS/How+You+Select+Master+Systems


13-Jul-2016 20/35

Best Practices for CA MIA ConfigurationThis section discusses best practices that apply to CA MIA configuration.

Use Delay Detection and Notification (see page 20)Tape Device Group Lock Delays (see page 21)Limit VARY Commands (see page 21)VARY Command Placement (see page 22)VARY REQUEUE NOTIFICATION (see page 22)VARY DEDUPLICATION (see page 23)DIAGNOSE ALL (see page 24)Automate DIAGNOSE ALL Command (see page 25)Limit SHUTDOWN FREE (see page 25)Use SYSDUMP Command (see page 26)Restarting CA MIA in an Active MIAPlex (see page 26)

Use Delay Detection and NotificationThe Delay Detection and Notification (DDN) SETOPTION should be turned on and the CONTENTION and WAITNOHOLD sub-options should be set.

Business Value

The Delay Detection and Notification service acts as a real time tape allocation delay detection service. The sub-options, CONTENTION and WAITNOHOLD, provide warnings for tape allocation delays. Having these options turned on can significantly reduce the length and severity of tape allocation delays. If these options are not turned on, then CA MIA will not warn you of potential tape device allocation delays. We recommend as a best practice that the Delay Detection and Notification service stay active when running GTAF.

Health Check

The MIM_GTAF_DDN_SERVICE health check verifies that the Delay Detection and Notification service, Contention notification and Wait No-Hold options, are turned on when GTAF is active. This heath check runs during initialization and when the state of DDN changes, such as a SETOPTION DDN command. The health check severity is low.

Reference

For more information, see Delay Detection and Notification (https://docops.ca.com/display/CMFZS/..Delay+Detection+and+Notification+v12.0)

https://docops.ca.com/display/CMFZS/.Delay+Detection+and+Notification+v12.0https://docops.ca.com/display/CMFZS/.Delay+Detection+and+Notification+v12.0https://docops.ca.com/display/CMFZS/.Delay+Detection+and+Notification+v12.0


13-Jul-2016 21/35

Tape Device Group Lock DelaysUse identical ordering for z/OS generic device group searches on all systems in the CA MIA complex.

Business Value

Mismatched search orders for generic device groups containing CA MIA-managed devices can cause cross-system deadlocks to occur on device group locks. Specifying an identical search order prevents this type of deadlock.

Health Check

None

Reference

For more information, see the section

Assign a Preference Value to a Device (https://docops.ca.com/display/CMFZS/Assign+a+Preference+Value+to+a+Device)

Factors That Influence TPCF Preferencing (https://docops.ca.com/display/CMFZS/Factors+That+Influence+TPCF+Preferencing)

Limit VARY CommandsAvoid issuing repetitive VARY commands to problem devices that do not appear to be responding.

Business Value

CA MIA preserves the order in which commands are entered. If a VARY ONLINE command is hung in IEEVARYD due to hardware problems, subsequent VARY commands queue in CA MIA, waiting to execute.

When the current active command completes, the next queued VARY is processed. In a hardware problem scenario, VARY commands cannot complete or fail until the MIH value for the device expires. With distributed MIH values of 45 minutes or more, a sequence of four VARY commands can take three hours or more to fail at MIH expiration.

CA MIA can optionally discard duplicate VARY commands that do not result in a state change for the target device.

Health Check

None

Reference


https://docops.ca.com/display/CMFZS/Assign+a+Preference+Value+to+a+Devicehttps://docops.ca.com/display/CMFZS/Assign+a+Preference+Value+to+a+Devicehttps://docops.ca.com/display/CMFZS/Factors+That+Influence+TPCF+Preferencinghttps://docops.ca.com/display/CMFZS/Factors+That+Influence+TPCF+Preferencing


13-Jul-2016 22/35


VARY Device Serialization (https://docops.ca.com/display/CMFZS/.VARY+Device+Serialization+v12.0)

VARY Command PlacementPlace VARY commands in the MIMSYNCH member.

Business Value

VARY commands are used to alter the online/offline status of a tape device and to assign a special CA MIA status to a device in order to influence device selection.

Commands in the MIMSYNCH member execute MIMINIT statements and MIMCMNDS aftercommands have executed, and only after all CA MIM for z/OS address spaces in the complex have synchronized. Placing VARY commands in the MIMSYNCH member ensures that the commands are executed after synchronization is complete and that tape devices are brought online only after the product initializes and is fully functional. This practice avoids integrity exposures that can occur when devices are online to more than one system and CA MIA is not running.

Health Check

None.

Reference


Plan the CA MIA MIMSYNCH Member (https://docops.ca.com/display/CMFZS/Plan+the+CA+MIA+MIMSYNCH+Member)

Configure Tape Devices Offline until CA MIA Synchronization (https://docops.ca.com/display/CMFZS/Configure+Tape+Devices+Offline+until+CA+MIA+Synchronization)

VARY REQUEUE NOTIFICATIONEnable VARY REQUEUE Notification to identify if SYSIEFSD ENQ Contention is adversely impacting VARY command completion.

Business Value:

z/OS acquires SYSIEFSD ENQs to serialize VARY processing with allocation. VARY commands can be requeued for later processing if SYSIEFSD ENQ resources are not available to VARY processing within 5 seconds. While VARY commands WAIT for the ENQ, other tasks can be delayed in the allocation process for both DASD and TAPE resources.

https://docops.ca.com/display/CMFZS/.VARY+Device+Serialization+v12.0https://docops.ca.com/display/CMFZS/Plan+the+CA+MIA+MIMSYNCH+Memberhttps://docops.ca.com/display/CMFZS/Plan+the+CA+MIA+MIMSYNCH+Memberhttps://docops.ca.com/display/CMFZS/Configure+Tape+Devices+Offline+until+CA+MIA+Synchronizationhttps://docops.ca.com/display/CMFZS/Configure+Tape+Devices+Offline+until+CA+MIA+Synchronization


13-Jul-2016 23/35

Enabling VARY Requeue Notification by setting the GTAF/TPCF VARYRQNTFY parameter to a value in the VARYRQNTFY parameter range of 1 to 5, will cause MIA to generate a MIM2225W diagnostic message when the number of times that a VARY command has been requeued is equal to the current VARYRQNTFY threshold value.

For example, setting VARYRQNTFY=3 will cause a MIM2225W to be generated after a VARY command has been requeued 3 times. This will result in a MIM2225W notification, minimally, once every 15 seconds.

To disable MIM2225W notification, reset the VARYRQNTFY parameter to NONE.

Health Check

None.

Reference


Change the Status of Managed Devices (VARY) (https://docops.ca.com/display/CMFZS/.How+You+Change+the+Status+of+Managed+Devices+%28VARY%29+v12.1.0)

(MIA) SETOPTION TPCF Command-Set TPCF Operating Values (https://docops.ca.com/display/CMFZS/.%28MIA%29+SETOPTION+TPCF+Command-Set+TPCF+Operating+Values+v12.1.0)

VARY DEDUPLICATIONEnable SETOPTION VARYDEDUP to eliminate serialization of redundant VARY requests that do not change the state of the target device.

Business Value

CA MIA serializes VARY ONLINE processing with z/OS allocation processes on all active systems in the MIAplex while z/OS acquires SYSIEFSD ENQs to serialize VARY processing with allocation on the local system. Redundant VARY commands that do not change the state of the target device can be automatically discarded. Elimination of duplicate VARY commands removes the processing overhead that is incurred for CA MIA and z/OS serialization of redundant VARY commands.

Health Check

The MIM_GTAF_VARY_DEDUP health check verifies that SETOPTION VARYDEDUP=YES. This heath check runs during initialization and when the state of the SETOPTION changes. The health check severity is low.

Reference


https://docops.ca.com/display/CMFZS/.How+You+Change+the+Status+of+Managed+Devices+%28VARY%29+v12.1.0https://docops.ca.com/display/CMFZS/.How+You+Change+the+Status+of+Managed+Devices+%28VARY%29+v12.1.0https://docops.ca.com/display/CMFZS/.%28MIA%29+SETOPTION+TPCF+Command-Set+TPCF+Operating+Values+v12.1.0https://docops.ca.com/display/CMFZS/.%28MIA%29+SETOPTION+TPCF+Command-Set+TPCF+Operating+Values+v12.1.0


13-Jul-2016 24/35

Change the Status of Managed Devices (VARY) (https://docops.ca.com/display/CMFZS/.How+You+Change+the+Status+of+Managed+Devices+%28VARY%29+v12.1.0)

(MIA) SETOPTION GTAF Command-Set GTAF Operating Values (https://docops.ca.com/display/CMFZS/.%28MIA%29+SETOPTION+GTAF+Command-Set+GTAF+Operating+Values+v12.1.0)

DIAGNOSE ALLWhen you use the DIAGNOSE command to troubleshoot allocation delays, always use the DIAGNOSE ALL version of the command.

Business Value

Collecting too much information is usually far less of a problem than not collecting enough information.

The DIAGNOSE ALL command displays the following:

The SYSTEMS portion of the display, which identifies the systems in the MIAplex where tape device group locks are held

The JOBSTATUS portion of the display, which identifies local jobs in various stages of tape device group lock acquisition

The VARY portion of the display, which identifies ACTIVE and queued VARY commands for managed devices.

Using the DIAGNOSE ALL command provides a complete picture. If tasks in the JOBSTATUS portion of the display are being DELAYED for LOCKS, the SYSTEMS portion of the display above it identifies which locks are in use and where. The DIAGNOSE ALL command is a useful real-time tool for analyzing allocation delays.

Health Check

None

Reference


Diagnosing Allocation Issues (https://docops.ca.com/display/CMFZS/.Diagnosing+Allocation+Issues+v12.0)

(MIA) DIAGNOSE Command-Diagnose Allocation Delays (https://docops.ca.com/display/CMFZS/.%28MIA%29+DIAGNOSE+Command-Diagnose+Allocation+Delays+v12.1.0)

https://docops.ca.com/display/CMFZS/.How+You+Change+the+Status+of+Managed+Devices+%28VARY%29+v12.1.0https://docops.ca.com/display/CMFZS/.How+You+Change+the+Status+of+Managed+Devices+%28VARY%29+v12.1.0https://docops.ca.com/display/CMFZS/.%28MIA%29+SETOPTION+GTAF+Command-Set+GTAF+Operating+Values+v12.1.0https://docops.ca.com/display/CMFZS/.%28MIA%29+SETOPTION+GTAF+Command-Set+GTAF+Operating+Values+v12.1.0https://docops.ca.com/display/CMFZS/.Diagnosing+Allocation+Issues+v12.0https://docops.ca.com/display/CMFZS/.%28MIA%29+DIAGNOSE+Command-Diagnose+Allocation+Delays+v12.1.0https://docops.ca.com/display/CMFZS/.%28MIA%29+DIAGNOSE+Command-Diagnose+Allocation+Delays+v12.1.0


13-Jul-2016 25/35

Automate DIAGNOSE ALL CommandAutomate the CA MIM for z/OS DIAGNOSE ALL command.

Business Value:

Periodically reviewing the displays resulting from an automated DIAGNOSE ALL command can help you identify problems for which no error messages are produced. While viewing problem windows, you have automatic access to an audit trail of Allocation throughput so you do not have to manually issue a DIAGNOSE ALL command.

CA MIM for z/OS and CA OPS/MVS product teams have collaborated to produce automation rules that interrogate the DIAGNOSE command for any jobs appearing in the GIVEN clause of the display. If a subsequent DIAGNOSE command shows that the same job still appears as having been GIVEN tape device group locks by z/OS, the automation takes an SVCDUMP of the offending task, and any additional address spaces identified on the SYSDUMP command that the automation issues.

Health Check

None.

More Information


Diagnosing Allocation Issues (https://docops.ca.com/display/CMFZS/.Diagnosing+Allocation+Issues+v12.0)

(MIA) DIAGNOSE Command-Diagnose Allocation Delays (https://docops.ca.com/display/CMFZS/.%28MIA%29+DIAGNOSE+Command-Diagnose+Allocation+Delays+v12.1.0)

Limit SHUTDOWN FREEUse the FREE option of the CA MIM for z/OS SHUTDOWN command only when tape device allocation has been quiesced.

Business Value

The FREE option of the SHUTDOWN command makes any resources in use on the FREEd system available to other tasks running on the other active systems in the MIAplex. If you issue the SHUTDOWN FREE command when tape device allocation is not quiesced, multiple tape devices can be allocated, resulting in tape label overwrites, block count errors, and rewind/unloads.

Health Check

None

Reference

https://docops.ca.com/display/CMFZS/.Diagnosing+Allocation+Issues+v12.0https://docops.ca.com/display/CMFZS/.%28MIA%29+DIAGNOSE+Command-Diagnose+Allocation+Delays+v12.1.0https://docops.ca.com/display/CMFZS/.%28MIA%29+DIAGNOSE+Command-Diagnose+Allocation+Delays+v12.1.0


13-Jul-2016 26/35

For more information, see Local Shutdown Processing (https://docops.ca.com/display/CMFZS/..Local+Shutdown+Processing+v12.1.0)

Use SYSDUMP CommandWhen taking SVCDUMPs of tasks potentially involved in tape allocation hangs, use the CA MIM for z/OS SYSDUMP command and include the ALLOCAS, IOASAS, and GRS address spaces, plus the suspected hung job name ( ). Use the following syntax:jjjjjjjj

F MIM,SYSDUMP JOBNAMES=( ,ALLOCAS,IOSAS,GRS)jjjjjjjj

Business Value

CA MIA serializes access to z/OS Tape Device Allocation. If a problem occurs in the z/OS process, the only outwardly identifiable manifestation of the problem may be a delay in the process, and may appear to be caused by CA MIA.

Including the ALLOCAS, IOASAS, and GRS address spaces on the SYSDUMP command (CA MIM for z/OS is included by default) gives vendor technical support (CA and IBM) the best chance of identifying the root cause of an allocation delay or VARY hang.

Health Check

None

Reference

For more information see (MIM) SYSDUMP Command-Obtain a System Dump (https://docops.ca.com./display/CMFZS/.%28MIM%29+SYSDUMP+Command-Obtain+a+System+Dump+v12.1.0)

Restarting CA MIA in an Active MIAPlexUnderstanding the effect that Recovery Allocation can have on system functions related to Tape Device Allocation within an MIAplex identifies the importance of monitoring and addressing Recovery Alloc sues at all times.ation is

Business Value

Eliminating Recovery Allocation is especially important during MIA startup, when Recovery Allocation related contention can delay or prevent the completion of VARY commands submitted by MIA during synchronization.

The following recommendations will prevent Recovery Allocation resource contention from delaying the availability of ONLINE Tape Devices during MIA startup:

Prior to STARTING or RESTARTING CA MIA on a system, respond to ALL Recovery Allocation WTORs on ALL systems in the MIAplex.

https://docops.ca.com/display/CMFZS/.Local+Shutdown+Processing+v12.1.0https://docops.ca.com/display/CMFZS/.Local+Shutdown+Processing+v12.1.0https://docops.ca.com/display/CMFZS/.Local+Shutdown+Processing+v12.1.0https://docops.ca.com/display/CMFZS/.%28MIM%29+SYSDUMP+Command-Obtain+a+System+Dump+v12.1.0https://docops.ca.com/display/CMFZS/.%28MIM%29+SYSDUMP+Command-Obtain+a+System+Dump+v12.1.0https://docops.ca.com/display/CMFZS/.%28MIM%29+SYSDUMP+Command-Obtain+a+System+Dump+v12.1.0


13-Jul-2016 27/35

PURGE INITIATORS to prevent new Tape work from starting while Tape Devices are in an OFFLINE state prior to MIA startup.

Order the sequence of VARY commands issued during MIA synchronization so that VARY ONLINE commands are issued BEFORE VARY OFFLINE commands.

Restart INITIATORs as soon as VARY ONLINE processing has completed.

Taking these actions will expedite resumption of SERIALIZED Global Tape Device Allocation by reducing or eliminating resource contention that delays the completion of VARY processing within an MIAplex.

Health Check

None

More Information

For more information and detail examples see How to Restart CA MIA in an ACTIVE MIAplex ( in the https://docops.ca.com/display/CMFZS/.Restarting+CA+MIA+in+an+Active+MIAPlex+v12.0) CA MIA

.Programmer (https://docops.ca.com/display/CMFZS/.Restarting+CA+MIA+in+an+Active+MIAPlex+v12.0)

https://docops.ca.com/display/CMFZS/.Restarting+CA+MIA+in+an+Active+MIAPlex+v12.0https://docops.ca.com/display/CMFZS/.Restarting+CA+MIA+in+an+Active+MIAPlex+v12.0https://docops.ca.com/display/CMFZS/.Restarting+CA+MIA+in+an+Active+MIAPlex+v12.0https://docops.ca.com/display/CMFZS/.Restarting+CA+MIA+in+an+Active+MIAPlex+v12.0https://docops.ca.com/display/CMFZS/.Restarting+CA+MIA+in+an+Active+MIAPlex+v12.0


13-Jul-2016 28/35

Best Practices for CA MII ConfigurationThis section discusses best practices that apply to CA MII Data Sharing configuration.

PROCESS=ALLSYSTEMS and GDIF (see page 28)PAGEFIX=COND (see page 29)GDIF COUNT Settings (see page 29)Exempt Statements in GDIF Exempt List (see page 30)Start with the Early Start Mechanism (see page 30)Preferred VCF Master (see page 31)Control File Sizing (see page 31)MIM_DRVR_SMF_RECORDING (see page 32)MIM_GDIF_DPRTY 1 (see page 32)

PROCESS=ALLSYSTEMS and GDIFWhen running the Global Data Integrity Facility (GDIF), set GDIINIT PROCESS=ALLSYSTEMS.

Business Value

When running GDIF in PROCESS=SELECT mode, qname resources must manually be entered to provide ENQs/RESERVE data integrity which may result in possible data integrity exposures.Running GDIF in ALLSYSTEMS mode allows GDIF to automatically convert and manage SCOPE=SYSTEMS resources, limiting the potential for possible data integrity exposures, as well as decreasing maintenance of the QNAME member to only include resources that require special management (SYSDSN for example).

Health Check

The MIM_GDIF_PROCESS_ALLSYS health check verifies GDIF is running in PROCESS=ALLSYSTEMS mode. This is a medium-severity, one-time check that runs when GDIF is started.

More Information


(MII) GDIINIT Statement-Set GDIF Initialization Values (https://docops.ca.com/display/CMFZS/%28MII%29+GDIINIT+Statement-Set+GDIF+Initialization+Values)

CA Support provides a free evaluation and conversion service for all customers with an active CA MIM license. These services assist customers in converting to PROCESS=ALLSYSTEMS mode, and requiresthe completion of two questionnaires - the first to gather required environmental data to perform the conversion, and the other following the conversion to ensure the GDIF address space is optimally configured to increase enqueue throughput while decreasing the address space footprint.

https://docops.ca.com/display/CMFZS/%28MII%29+GDIINIT+Statement-Set+GDIF+Initialization+Valueshttps://docops.ca.com/display/CMFZS/%28MII%29+GDIINIT+Statement-Set+GDIF+Initialization+Values


13-Jul-2016 29/35

PAGEFIX=COND(https://docops.ca.com/display/CMFZS125/CA+MIM+Programming)

If you will be running the Global Data Integrity Facility (GDIF), set PAGEFIX=COND in the MIMINIT statement.

Business Value:

PAGEFIX=COND specifies that cell-pooled control blocks should be page-fixed as long as the system is not expecting a real page storage condition. Typically, the CA MIM for z/OS working set size remains fixed in real storage, you do not need to page-fix its cell-pool resident control blocks. However, in times of critical pageable storage shortages, frames can be stolen from the working set pages. If a system is configured so that it is real-storage constrained, setting PAGEFIX=COND can help improve the ability of CA MIM for z/OS to provide a consistent level of service, even during times of storage shortage.

Health Check

The MIM_GDIF_PAGEFIX health check verifies that GDIF is started with PAGEFIX=COND or PAGEFIX=YES. This heath check is a low severity, one-time check that occurs during CA MIM initialization.

Reference:

For more information, see How You Page-fix Cell Pooled Control Blocks (https://docops.ca.com/display./CMFZS/How+You+Page-fix+Cell+Pooled+Control+Blocks)

GDIF COUNT SettingsSet SETOPTION GDIF COUNT=SYSTEMS.

Business Value

This setting tells the Global Data Integrity Facility (GDIF) to collect information about ENQ requests that have a scope of SYSTEMS, RESERVE requests. Setting COUNT to LOCAL or RESERVES including limits the scope of information collected; setting COUNT to ALL collects too much information.

Setting COUNT=SYSTEMS allows CA MII to accumulate statistics on RESERVES and SCOPE=SYSTEMS ENQs. Once this has been completed, the CA MII DISPLAY COUNT command is more valuable to technicians when assessing which QNAMEs to manage or exempt from CA MII processing.

Health Check

None

More Information

https://docops.ca.com/display/CMFZS125/CA+MIM+Programminghttps://docops.ca.com/display/CMFZS/How+You+Page-fix+Cell+Pooled+Control+Blockshttps://docops.ca.com/display/CMFZS/How+You+Page-fix+Cell+Pooled+Control+Blockshttps://docops.ca.com/display/CMFZS/How+You+Page-fix+Cell+Pooled+Control+Blocks


13-Jul-2016 30/35

For more information, see (MII) SETOPTION GDIF Command-Set GDIF Operating Values (https://docops..ca.com/display/CMFZS/.%28MII%29+SETOPTION+GDIF+Command-Set+GDIF+Operating+Values+v12.1.0)

Exempt Statements in GDIF Exempt ListExempt statements should specify a qname for every rname.

Business Value:

You can use the GDIEXMPT member if you need to make certain resources exempt from GDIF global ENQ processing. The GDIEXMPT member is used for all qnames that have GDIF=YES and EXEMPT=YES coded on the QNAME statement. To ensure that only the intended resources are exempted from global processing, you should be as specific as possible with the rname that you specify, and you should always specify a qname.

If you do not specify a qname for an exempt statement, then the exempt statement will be applied to every qname that has GDIF=YES and EXEMPT=YES coded on the QNAME statement.

The sample GDIEXMPT member includes examples on specifying a qname with each rname that is being exempted.

Health Check

None.

Reference:

For more information, see the (MII) EXEMPT Command-Modify Exempt List (https://docops.ca.com/display/CMFZS/%28MII%29+EXEMPT+Command-Modify+Exempt+List)

Start with the Early Start MechanismStart CA MII with the Early Start Mechanism.

Business Value

Running with the CA MIM Early Start Mechanism ensures CA MII synchronization occurs early in the IPL process so all RESERVE and SYSTEMS ENQ requests are suspended to avoid unconverted reserves, deadly embraces, and/or integrity exposures.

Health Check

The MIM_GDIF_EARLY_START health check verifies that the Early Start feature was used to start this instance of CA MIM. This heath check is a medium severity, one-time check that occurs during CA MIM initialization.

Business Value:

https://docops.ca.com/display/CMFZS/.%28MII%29+SETOPTION+GDIF+Command-Set+GDIF+Operating+Values+v12.1.0https://docops.ca.com/display/CMFZS/.%28MII%29+SETOPTION+GDIF+Command-Set+GDIF+Operating+Values+v12.1.0https://docops.ca.com/display/CMFZS/.%28MII%29+SETOPTION+GDIF+Command-Set+GDIF+Operating+Values+v12.1.0https://docops.ca.com/display/CMFZS/%28MII%29+EXEMPT+Command-Modify+Exempt+Listhttps://docops.ca.com/display/CMFZS/%28MII%29+EXEMPT+Command-Modify+Exempt+Listhttps://docops.ca.com/display/CMFZS/%28MII%29+EXEMPT+Command-Modify+Exempt+List


13-Jul-2016 31/35

If CA MII is not synchronized early enough, it is possible that some hardware reserves are not converted. Late synchronized can lead to integrity exposures and deadly embraces.

Reference:

This information is detailed in the CA MIM for z/OS Installation (https://docops.ca.com/display/CMFZS125./Installation)

Preferred VCF MasterMake sure that the preferred VCF MASTER system is the system with the highest ENQ volume.

Business Value

Because the master system reads the virtual control file (VCF) directly from its own storage, it incurs no device I/O overhead.

Health Check

None.

Reference


(MIM) GLOBALVALUE Command-Assign Global Parameters (https://docops.ca.com/display/CMFZS/.%28MIM%29+GLOBALVALUE+Command-Assign+Global+Parameters+v12.1.0)

How You Select Master Systems (https://docops.ca.com/display/CMFZS/How+You+Select+Master+Systems)

Control File SizingMake sure your CA MIM for z/OS control files are large enough to handle the active ENQ workload.

Business Value:

Control files that are undersized can cause product or system outages and potential data integrity exposures.

Note: If MIMINIT COMMUNICATION=CTCONLY or XCF, CA MIM automatically resizes the control files.

https://docops.ca.com/display/CMFZS125/Installationhttps://docops.ca.com/display/CMFZS125/Installationhttps://docops.ca.com/display/CMFZS125/Installationhttps://docops.ca.com/display/CMFZS/.%28MIM%29+GLOBALVALUE+Command-Assign+Global+Parameters+v12.1.0https://docops.ca.com/display/CMFZS/.%28MIM%29+GLOBALVALUE+Command-Assign+Global+Parameters+v12.1.0https://docops.ca.com/display/CMFZS/How+You+Select+Master+Systems


13-Jul-2016 32/35

Health CheckThe MIM_GDIF_CF_SZ health check verifies all of your defined control files are of adequate size to accommodate your ENQ workload. This is a medium-severity health check that runs once per hour.

Reference

For more information, see Control File Size Considerations (https://docops.ca.com/display/CMFZS/..Control+File+Size+Considerations+v12.1.0)

SMF RECORDINGTurn CA MIM GDIF SMF recording on.

Business Value

CA MIM SMF recording is an effective tool to evaluate the MIM control file performance of the MIMPLEX. SMF records include a range of information such as the average control file response time, the number of control file cycles per second, and so on. You can use these metrics for evaluation of CA MIM control file usage over a period of time.

Health Check

The MIM_DRVR_SMF_RECORDING health check verifies that the GDIF SMF recording mechanism is active. This is a low priority health check that is issued whenever the SMF status changes.

More Information

For more information, see SMF Recording (https://docops.ca.com/display/CMFZS/..SMF+Recording+Health+Check+v12.1.0)

Dispatching PrioritySet the Dispatching priority for CA MIM to x'FF'.

Best Practice

Service providers, such as CA MIM (GDIF), should execute with a higher dispatching priority than service requestors. CA MIM (GDIF) provides vital system services for z/OS address spaces and users. If the CA MIM (GDIF) address space is not running at the recommended dispatching priority, then degraded system performance can occur due to less than optimal ENQ performance and throughput. Therefore, CA MIM (GDIF) should run at a dispatching priority of x'FF' to obtain resources necessary to provide a time critical service.

Health Check

The MIM_GDIF_DPRTY health check verifies that the CA MIM Global Data Integrity Facility (GDIF) address space is running the optimal dispatching priority of x'FF'.

Reference

https://docops.ca.com/display/CMFZS/.Control+File+Size+Considerations+v12.1.0https://docops.ca.com/display/CMFZS/.Control+File+Size+Considerations+v12.1.0https://docops.ca.com/display/CMFZS/.Control+File+Size+Considerations+v12.1.0https://docops.ca.com/display/CMFZS/.SMF+Recording+Health+Check+v12.1.0https://docops.ca.com/display/CMFZS/.SMF+Recording+Health+Check+v12.1.0https://docops.ca.com/display/CMFZS/.SMF+Recording+Health+Check+v12.1.0


13-Jul-2016 33/35

Reference

For more information, see Start CA MII with the Address Space Creation Utility (https://docops.ca.com/display/CMFZS/Start+CA+MII+with+the+Address+Space+Creation+Utility)

https://docops.ca.com/display/CMFZS/Start+CA+MII+with+the+Address+Space+Creation+Utilityhttps://docops.ca.com/display/CMFZS/Start+CA+MII+with+the+Address+Space+Creation+Utilityhttps://docops.ca.com/display/CMFZS/Start+CA+MII+with+the+Address+Space+Creation+Utility


13-Jul-2016 34/35

Best Practices for CA MIC ConfigurationThis section discusses best practices that apply to CA MIC configuration.

Use COLLECT SYSID=EXTERNAL (see page 34)COLLECT Command and Non-existent Consoles (see page 34)

Use COLLECT SYSID=EXTERNALTo prevent CA MIC from collecting LOCAL messages, use COLLECT SYSID=EXTERNAL

Business Value

Because z/OS already routes messages to local consoles, you can avoid the unnecessary overhead of having CA MIC also route local messages to a local console.

Health Check

None

Reference


CA MIC Message Processing (https://docops.ca.com/display/CMFZS/CA+MIC+Message+Processing)

(MIC) COLLECT Command-Create Message Routing Definition (https://docops.ca.com/display/CMFZS/.%28MIC%29+COLLECT+Command-Create+Message+Routing+Definition+v12.1.0)

COLLECT Command and Non-existent ConsolesAvoid using the COLLECT command for consoles that no longer exist on your system.

Business Value

You can avoid unnecessary overhead by removing any COLLECT command for a console that no longer exists. This prevents CA MIC from routing unnecessary messages through the control file.

Health Check

None.

Reference

https://docops.ca.com/display/CMFZS/CA+MIC+Message+Processinghttps://docops.ca.com/display/CMFZS/.%28MIC%29+COLLECT+Command-Create+Message+Routing+Definition+v12.1.0https://docops.ca.com/display/CMFZS/.%28MIC%29+COLLECT+Command-Create+Message+Routing+Definition+v12.1.0


13-Jul-2016 35/35

For more information, see (MIC) COLLECT Command-Create Message Routing Definition (https://docops.ca.com/display/CMFZS/.%28MIC%29+COLLECT+Command-Create+Message+Routing+Definition+v12.1.0)

https://docops.ca.com/display/CMFZS/.%28MIC%29+COLLECT+Command-Create+Message+Routing+Definition+v12.1.0https://docops.ca.com/display/CMFZS/.%28MIC%29+COLLECT+Command-Create+Message+Routing+Definition+v12.1.0https://docops.ca.com/display/CMFZS/.%28MIC%29+COLLECT+Command-Create+Message+Routing+Definition+v12.1.0https://docops.ca.com/display/CMFZS/.%28MIC%29+COLLECT+Command-Create+Message+Routing+Definition+v12.1.0

CA MIM Best Practices for InstallationInstall Using CA CSMImplement a Proactive Preventive Maintenance StrategyKeep Current on CA Common ServicesInstall on Test System FirstApply Current IBM APARSCheck Parmlib Syntax

Best Practices for General CA MIM ConfigurationSupportCOMPATLEVELUse Restart ManagerHYPERSTARMessage PrefixingSeparate Address SpacesBackup Control FilesDASD Control File PlacementChannel Paths for CTC DevicesBackup CTCTracingMIMMSGSACF2 NO-SMCUse Restart ManagerVCF Multiple Eligible MastersVARY DEDUPLICATION Health CheckControl File AUTOTUNE

Best Practices for CA MIA ConfigurationUse Delay Detection and NotificationTape Device Group Lock DelaysLimit VARY CommandsVARY Command PlacementVARY REQUEUE NOTIFICATIONVARY DEDUPLICATIONDIAGNOSE ALLAutomate DIAGNOSE ALL CommandLimit SHUTDOWN FREEUse SYSDUMP CommandRestarting CA MIA in an Active MIAPlex

Best Practices for CA MII ConfigurationPROCESS=ALLSYSTEMS and GDIFPAGEFIX=CONDGDIF COUNT SettingsExempt Statements in GDIF Exempt ListStart with the Early Start MechanismPreferred VCF MasterControl File SizingSMF RECORDINGDispatching Priority

Best Practices for CA MIC ConfigurationUse COLLECT SYSID=EXTERNALCOLLECT Command and Non-existent Consoles

ca mim for z/os - 12.5 best practices · ca mim for z/os - 12.5 best practices. ... and ibm...

Documents