We have been getting MIM control file lockouts for almost a year. We have
been working with STK (the DASD manufacturer), IBM and CA (MIM). So far,
nothing has resolved the problem. It usually occurs on the weekends, on
our test systems, when all the other systems are fairly quiet.
Occasionaly, we will also get start pendning messages.
This issue only occurs for a few seconds, or upto a few minutes. It always
clears itself up without operator intervention.
We have 8 LPARs, with MIM running on each LPAR.
We are running on an IBM 2064-105. The DASD is an STK MODEL V2XF.
Has anyone else experienced this problem? How was it resolved?
No, I have never experienced it but I have some thoughts. However, I
would be surprised if these haven't been suggested by one or more vendors.
* do you have any other datasets on the same volume as the control file?
* can you identify the system holding the RESERVE? Is it always the
same system? Anything unusual about the z/OS or MIM level on that system?
* on the system holding the RESERVE, does a console D U command show the
device as RESERVED (-R)? This would imply a software error (RESERVE
with no DEQ to release it).
--
Bruce A. Black
Senior Software Developer for FDR
Innovation Data Processing 973-890-7300
personal: [EMAIL PROTECTED]
sales info: [EMAIL PROTECTED]
tech support: [EMAIL PROTECTED]
web: www.innovationdp.fdr.com
----------------------------------------------------------------------
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
