MIMQUERY Setup Summary

Products

MIM Data Sharing (MII) MIM Resource Sharing (MIM)

Issue/Introduction

You are planning to enable new feature MIMQUERY, ISGQUERY and GQSCAN.

Any changes to MII configuration in EDIPARMS, MIIEXMPT and MIIQNAME necessary?
Any possible impact to current MIM processing.

Resolution

To answer the specific questions...

There are no required changes to the qname, exempt, or ediparms members.
Global enqs will be handled the same way after MIMQUERY is activated. MIMQUERY will intercept and process GQSCANS and ISGQUERY requests globally after activation.

Below we will highlight some recommendations and guidance in the following topics.

SETUP (Review each):

MIMQUERY - General Introduction
How to Activate MIMQUERY in the MIMplex
- Note: You can skip over the section titled “Verify that You Installed the Maintenance and Activate MIMQUERY Dynamically”
LU11488 is good to have on as well as IBM GRS APAR OA65023
CCI needs to be configured in advance with connectivity between all systems in the MIMplex. A CCITCPGW connection is probably recommended if any systems are not in the same sysplex. Refer to the Common Components and Services documentation for any CCI connectivity inquiries.

ACTIVATION and TESTING:

The MIMQUERY/GQSCAN/ISGQUERY features must be activated on all systems at once - so would be ideal to test this on a non-production MIMPLEX.

Here is one method of rolling out the features:

On one system only:

- F MIMGR,ACTIVATE FEATURE=(MIMQUERY,FORCE)
  The feature will be activated on all active systems in the MII plex.
- F MIMGR,DISPLAY FEATURE
  Should show MIMQUERY active

The MIM DISPLAY RESERVES, CONFLICTS, ENQRESOURCE commands use MIMQUERY to gather global information so you can test the feature.

After activating the feature, you’ll need to solidify the change in the MIM INIT member:

MIMINIT FEATURE=(HYPERSTAR,MIMQUERY)

After you feel comfortable with the above behavior:

On one system only:

F MIMGR,ACTIVATE FEATURE=(GQSCAN,FORCE)
The feature will be activated on all active systems in the MII plex.
F MIMGR,DISPLAY FEATURE
Should show GQSCAN active

The D GRS,C and D GRS,RES=(qname,rname) commands use GQSCAN to gather global information so you can test the feature .

After activating the feature, you’ll need to solidify the change in the MIM INIT member:

MIMINIT FEATURE=(HYPERSTAR,MIMQUERY,GQSCAN)

After you feel comfortable with the above behavior:

On one system only:

F MIMGR,ACTIVATE FEATURE=(ISGQUERY,FORCE)
The feature will be activated on all active systems in the MII plex.
F MIMGR,DISPLAY FEATURE
Should show ISGQUERY active
Simple ISGQUERY test:
- On SYS1, edit a sequential.dataset in ISPF
- On SYS2, enter the following TSO command:
  ALLOC DS('sequential.dataset') OLD

Messages similar to the following should be issued:

IKJ56225I DATA SET sequential.dataset ALREADY IN USE, TRY LATER+
IKJ56225I DATA SET IS ALLOCATED TO ANOTHER JOB OR USER        
IEFA110I DATA SET CONTENTION                                  
DATA SET sequential.dataset IN USE BY                          
SYSNAME  JOBNAME  ASID                                        
SYS1     tsoid    nnnn

After activating the feature, you’ll need to solidify the change in the MIM INIT member:

MIMINIT FEATURE=(HYPERSTAR,MIMQUERY,GQSCAN,ISGQUERY)

DEACTIVATION (as needed):

If there is problem and you wish to turn off any of the features:

F MIMGR,DEACTIVATE FEATURE=(ISGQUERY,FORCE)
F MIMGR,DEACTIVATE FEATURE=(GQSCAN,FORCE)
F MIMGR,DEACTIVATE FEATURE=(MIMQUERY,FORCE)

Remove the feature that was deactivated on the MIMINIT FEATURE= statement in the MIM INIT member.

Note:
ISGQUERY and GQSCAN both require MIMQUERY, so you cannot deactivate MIMQUERY without first deactivating ISGQUERY/GQSCAN.

MISCELANEOUS:

If you have any automation rules in place for the following messages, the rule may need to be changed:

MIM1028I - replaced with -> MIM1181I
MIM1017I - replaced with -> MIM1186I
MIM1091I - replaced with -> MIM1180I