Hi Sam:
We share DASD across two SYSPLEXs, so the coupling facility won't
help us.
Thanks,
_________________________________________________________________________
David A. Wright
Dominion Resources Services, Inc.
One James River Plaza
Enterprise Operations-IT Systems Programming
IT-DP/OJRP-10
Richmond, VA 23219
Tie Line: 8-736-3354
Pager: (804) 273-3030 #2942
Phone: (804) 771-3354
Fax: (804) 771-6146
Email: [EMAIL PROTECTED]
"Knutson, Sam" <[EMAIL PROTECTED]>
Sent by: IBM Mainframe Discussion List <[email protected]>
02/26/2007 01:51 PM
Please respond to
IBM Mainframe Discussion List <[email protected]>
To
[email protected]
cc
Subject
Re: MIM control file volume DASD lockout
I don't know much about MIM but as the doctor says "then don't do
that"... Have you considered to get away from the DASD control file as
the primary control file? If the sharing is all inside the scope of a
parallel Sysplex you could use list structures in a coupling facility.
This is what we do though admittedly we only use MIA as we are using
only GRS for serialization and never used MIC. If not Coupling Facility
then perhaps you could use CTCONLY.
*==============================================================*
* FOR COMMUNICATION METHODS DASDONLY AND CTCDASD,
* DYNAMICALLY ALLOCATE CONTROL FILES IF MIMTBL00 AND MIMTBL01
* ARE COMMENTED OUT OF MIMPROC, OR USE COUPLING FACILITY
* LIST STRUCTURE CONTROL FILES
*==============================================================*
*
ALLOCATE XESFILEID=00 STRNAME=(MIMGR#TABLE00)
ALLOCATE XESFILEID=01 STRNAME=(MIMGR#TABLE01)
ALLOCATE DDNAME=MIMTBL02,DSNAME=SYSOP.MIMGTAF.CF02
ALLOCATE DDNAME=MIMTBL03,DSNAME=SYSOP.MIMGTAF.CF03
*
Best Regards,
Sam Knutson, GEICO
Performance and Availability Management
mailto:[EMAIL PROTECTED]
(office) 301.986.3574
"Think big, act bold, start simple, grow fast..."
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of David A. Wright
Sent: Monday, February 26, 2007 1:33 PM
To: [email protected]
Subject: Re: MIM control file volume DASD lockout
Hi Mark:
We start all of our MIMGR address spaces through MIMASC.
We have taken GTF traces, at STKs recommendations.
We have not taken a system dump, because STK feels that the
problem is in the channel subsystem.
Thanks,
________________________________________________________________________
_
David A. Wright
Dominion Resources Services, Inc.
One James River Plaza
Enterprise Operations-IT Systems Programming IT-DP/OJRP-10 Richmond, VA
23219
Tie Line: 8-736-3354
Pager: (804) 273-3030 #2942
Phone: (804) 771-3354
Fax: (804) 771-6146
Email: [EMAIL PROTECTED]
-----------------------------------------
CONFIDENTIALITY NOTICE: This electronic message contains
information which may be legally confidential and/or privileged and
does not in any case represent a firm ENERGY COMMODITY bid or offer
relating thereto which binds the sender without an additional
express written confirmation to that effect. The information is
intended solely for the individual or entity named above and access
by anyone else is unauthorized. If you are not the intended
recipient, any disclosure, copying, distribution, or use of the
contents of this information is prohibited and may be unlawful. If
you have received this electronic transmission in error, please
reply immediately to the sender that you have received the message
in error, and delete it. Thank you.
----------------------------------------------------------------------
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
