Starting CA MIM for Z/OS, it can happen that the task gets an abend with TITLE=MIM R12.5 @ 0000 MSIERROR CODE=0098 at MIMDRDRV.MIMDRENG+nnnn; Issuer=MIM but the task doesn’t end abnormally and it completes correctly the initialization phase.

Document ID : KB000007568
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

 

At startup time, CA MIM for z/OS examines the system IDs in its DEFSYS statement to see which systems will be joining the MIMplex. Synchronization does not complete until you start CA MIM on each system identified in the control file.

To tell CA MIM to ignore a system ID for this execution because the system is not joining the complex, issue a FREE command for that system.

With the latest releases of CA MIM it can happen that, starting CA MIM for Z/OS, the task gets an abend looking like:

 

… TITLE=MIM R12.5 @ 0000 MSIERROR CODE=0098 at MIMDRDRV.MIMDRENG+nnnn; Issuer=MIM …

 

but the task doesn’t end abnormally and it completes correctly the initialization phase and works without any problem managing the MIMplex.

Why this abend and how to prevent it from happening again or causing more serious problems in the MIMplex?

 

Environment:
CA MIM 12.1 and above
Cause:

 

There are some rare conditions in which, when a System is marked FREED in the MIMplex and it results in Status FREED in the DISPLAY SYSTEMS output command, the same Status is not reflected into the DASD Control File for this same System.

This situation can generate problems in the product functionality if not detected immediately at task startup.

 

Resolution:

 

There was some diagnostic code added to MIM at newer releases that causes a diagnostic SVC dump to capture a rare condition where a System is not marked as FREED in the DASD control file, but it is really freed looking at the DISPLAY SYSTEMS output command.

There should be no business impact other than the dump being generated. 

So, looking at the DISPLAY SYSTEMS output, there should be some systems showing as FREED but in the control file they are not actually in the proper FREED status. 

To prevent future diagnostic dumps next time CA MIM is started, the following MIM command should be entered: 

“FREE (sys1,sys2…)

 

where sys1,sys2  are the systems marked as FREED in the DISPLAY SYSTEMS output command.

The command only needs to be entered from one system of the MIMPLEX.

These Systems will still show as FREED in the DISPLAY SYSTEMS command output, so it will not look any different. However, the control file itself will have been updated correctly.

 

If, after this suggestion, the dump is still generated when task started and/or the task doesn’t work correctly after the dump, please open a Case with CA Support.