search cancel

MIM leaves exits ISGNQXITBATCHCND installed

book

Article ID: 42196

calendar_today

Updated On:

Products

MIM Resource Sharing (MIM) MIM Data Sharing (MII) MIM Tape Sharing (MIA) MIM Message Sharing (MIC)

Issue/Introduction

Question:

We brought our systems down for maintenance, which includes shutting down MII. We found that two GRS exits were still installed at MII termination. Using the MVS Display command, we receive:

 
D PROG,EXIT,EXITNAME=ISGNQXITBATCHCND         
CSV461I 07.47.29 PROG,EXIT DISPLAY 891        
EXIT             MODULE   STATE MODULE   STATE
ISGNQXITBATCHCND MIM>XXBC   A   MIM>QXFX   A  
 
We performed the normal "F MII,SHUTDOWN FREE" command which took MII down, but these exits were still installed.
 
Shouldn't the exits be removed if MII is shut down?  How do we get the exits removed?
 
 

 

Answer: 

 

Both ISGNQXITBATCH and ISGNQXITBATCHCND are dynamic IBM exits that are called/invoked by CA MIM at initialization. CA MIM uses these exits to intercept
enqueue/dequeue processing. Both exits remain active following the initial startup of MIM on the system, as shown in the example here:
 

Before Starting MIM:

07:54:58.38 62S00051 00000090  GSVX014I (VTAM.FRAJU03) FRAJU03 entered command MVS D PROG,EXIT,      
                               EXITNAME=ISGNQXITBATCHCND                                             
07:54:58.38 STC00051 00000290  D PROG,EXIT,EXITNAME=ISGNQXITBATCHCND                                 
07:54:58.42 62       00000090  CSV463I NO MODULES ARE ASSOCIATED WITH EXIT ISGNQXITBATCHCND     
    

After MIM Synchronization Completes:

08:00:12.81 62S00059 00000290  IEF196I IEF237I JES2 ALLOCATED TO MIMLOG                            
08:00:27.95 62S00051 00000090  GSVX014I (VTAM.FRAJU03) FRAJU03 entered command MVS D PROG,EXIT,    
                               EXITNAME=ISGNQXITBATCHCND                                           
08:00:27.96 STC00051 00000290  D PROG,EXIT,EXITNAME=ISGNQXITBATCHCND                               
08:00:27.97 62       00000090  CSV461I 08.00.27 PROG,EXIT DISPLAY 029                              
                 029 00000090  EXIT             MODULE   STATE MODULE   STATE MODULE   STATE       
                 029 00000090  ISGNQXITBATCHCND MIMFXXBC   A   MIMFQXFX   A                             
 
After MIM Shutdown:
 
08:00:52.17 62       00000090  IEF352I ADDRESS SPACE UNAVAILABLE                                  
08:00:52.17 62       00000290  IEF196I IEF352I ADDRESS SPACE UNAVAILABLE                          
08:00:52.17 62       00000290  IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME=*UNAVAIL, ASID=002A.   
08:00:52.50 62S00051 00000090  GSVX014I (VTAM.FRAJU03) FRAJU03 entered command MVS D PROG,EXIT,   
                               EXITNAME=ISGNQXITBATCHCND                                          
08:00:52.51 STC00051 00000290  D PROG,EXIT,EXITNAME=ISGNQXITBATCHCND                              
08:00:52.52 62       00000090  CSV461I 08.00.52 PROG,EXIT DISPLAY 080                             
                 080 00000090  EXIT             MODULE   STATE MODULE   STATE MODULE   STATE      
                 080 00000090  ISGNQXITBATCHCND MIMFXXBC   A   MIMFQXFX   A       


Looking further into why the exit is not set to inactive after the MIM address space ends, the exit code performs a check to see if MIM is active. This allows the exit to be reused for subsequent restarts of MIM. 

Environment

Release: MIMALM00200-12.1-MIM-Resource Sharing-for z/OS-Plus MSU
Component: