On Mon, 26 Feb 2007 08:46:23 -0600, David A. Wright <[EMAIL PROTECTED]> wrote:
>Hello: > >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? > Have not seen this... but we have been running CTCONLY for years. Are the test systems part of the same MIMplex? Are the control files on their own dasd volumes? Do any non-MIMplex LPARs share the same dasd (a sandbox for example)? Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group: G-ITO mailto:[EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- 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
