"Vernooy, C.P. - SPLXM" <[email protected]> wrote in message
news:<3310ac9d797ec94db8d89ccabdea47a7c6b...@kl1221tc.cs.ad.klmcorp.net>
...
> 
> 
> "McKown, John" <[email protected]> wrote in message
>
news:<[email protected]>.
> ..
> > > -----Original Message-----
> > > From: IBM Mainframe Discussion List 
> > > [mailto:[email protected]] On Behalf Of Vernooy, C.P. - SPLXM
> > > Sent: Wednesday, June 10, 2009 1:41 AM
> > > To: [email protected]
> > > Subject: Re: MIM - GRS conversion in practice
> > > 
> > > 
> > > 
> > > "McKown, John" <[email protected]> wrote in message
> > > news:<[email protected]
> > > cnrh.dom>.
> > > ..
> > > > > -----Original Message-----
> > > > > From: IBM Mainframe Discussion List 
> > > > > [mailto:[email protected]] On Behalf Of Dennis Trojak
> > > > > Sent: Tuesday, June 09, 2009 11:08 AM
> > > > > To: [email protected]
> > > > > Subject: Re: MIM - GRS conversion in practice
> > > > > 
> > > > > Did you ever get around this hurdle? We wanted to try moving 
> > > > > from MIM to
> > > > > GRS also.
> > > > > Dennis
> > > > > 
> > > > 
> > > > I run MIM/Integrity and GRS=nn. We need the ECMF and EDIF
> > > functionality without the global ENQ. We do this by having a 
> > > PARM member
> > > with
> > > > 
> > > > MIMINIT GDIF=OFF
> > > > 
> > > > That leaves MIMIT up without the Gloabal ENQ. You might want to
> try
> > > that and see if it helps,
> > > > 
> > > > --
> > > > John McKown 
> > > 
> > > We want to stop and remove MIM entirely.
> > > 
> > > Kees.
> > 
> > I wonder if you bring up MIMIT with EDIF=OFF, will it remove the
exits
> you mentioned in GRS? If so, then you could just stop MIMIT after its
> initialization has removed the exits. But I don't kown if that will
work
> or not. Can you try?
> > 
> > --
> 
> I think we already have the trick working and it is not as complicated
> as it seemed.
> More news by the end of the week (probably).
> 
> Kees.

Well, we found the working procedure and it was not as simple as we
thought, but well doable.

Chronology:

We stopped MIM and did the first conversion and we received:
ISG881I SET GRSRNL COMMAND CANCELED. AN ISGNQXITBATCH OR AN
ISGNQXITBATCHCND EXIT IS CURRENTLY ACTIVE.


The active exits were from the GRS ENQmonitor (modname ISGASTUB) on Exit
ISGNQXITBATCH and the 2 MIM exits on Exit ISGNQXITBATC. Information from
IBM told us that the MIM exits were no problem and needed not be
removed.

However this did not work, after stopping the GRS Enqmonitor (which
removed its exit) we again received ISG881I, so now for the MIM exits
only.

We already discovered that the MIM command character was used for
several purposes in MIM, a.o. for creating the name of the MIM SSI
subsystem en for custructing the ISG exit names (for what purpose, can I
have 2 MIM's in 1 system?). We then changed the MIM command character
and reIPL'd the system.

We checked that the GRS Enqmonitor was stopped, stopped MIM and tried
the conversion again and again received ISG881I, complaining only about
the 2 MIM exits.

Then we also DELeted the MIM Exits (SETPROG
EXIT,DELETE,EN=ISGNQXITBATCHCND,MOD=xxxxxxxx) and retried the conversion
and then it succeeded. We ran this testsystem for the rest of the day
and did not notice problems caused by dynamically DELete-ing the MIM
exits.

So the trick is to have no exits on the above mentioned GRS exits and to
achieve that, you must create standardized MIM exit names by choosing a
alphanumeric or national command character or, as we did, choose
something like "MIM". 

This action is now planned for the production sysplex at the end of this
month. If new information comes up then, I will let you know here.

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.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
Dutch Airlines) is registered in Amstelveen, The Netherlands, with
registered number 33014286 
**********************************************************************

----------------------------------------------------------------------
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

Reply via email to