.we used to have occasional woe with GRS...but RESTART(YES) has
allowed us to recover in all situations when dinking with our TEST LPAR
has messed up GRS...is still not pretty; lost of ugly messages; but our
PROD LPAR recovers...
BROWSE SYS1.PARMLIB(GRSCNF11) - 01.02 Line 00000043 Col 0
Command ===> Scroll ===
CTRACE(CTIGRS00) /* TRACE PARMS ARE IN CTIGRS00 */ 0
REJOIN(YES) /* CAN IT JOIN THE RING ? */ 0
RESMIL(10) /* RESIDENCY TIME IN MILLISECONDS */ 0
RESTART(YES) /* CAN IT RESTART THE RING ? */ 0
* RESTART(NO) CAN IT RESTART THE RING ? */ 0
TOLINT(180) /* TOLERANCE INTERVAL IN SCEONDS */ 0
-----Original Message-----
From: Scott Rowe [mailto:[EMAIL PROTECTED]
Sent: Monday, May 19, 2008 1:54 PM
To: [email protected]
Subject: Re: GRS Tales of Tribulation
I think you sort of hung yourself here, GRS was bringing TEST into the
ring just fine when you shot test. If you had waited, TEST would most
likely have joined the ring without error. The JES2 messages are just a
symptom of the join process, which can be VERY slow in non-XCF RING
mode, if there are a lot of resources enqueued.
I am in the process of converting from an old RING into an XCF RING, and
the join process takes 5 minutes the old way, but only about 8 seconds
w/XCF.
Feel free to contact me off-list if you have any questions.
>>> Daniel McLaughlin <[EMAIL PROTECTED]> 5/19/2008 1:27
PM >>>
We were attempting GRS startup. PROD was up and happy when the TEST
LPAR was IPL'd. Then we started getting all sorts of JES2 CKPT dataset
alerts
about some allocated type condition. OK, let's take TEST down. But TEST,
at
the same time, was having heartburn over the ACDS (posted earlier). TEST
wouldn't come down gracefully with automation because SMS had never come
up. Long story short - we nailed TEST all the way down to DEACTIVATE.
PROD, in the meantime, was spewing the JES2 message, and nothing was
there to reply to. D GRS showed all player inactive. Tried to smoke
JES2, but
he was in the bog and not coiming out.
One unscheduled IPL...
GRS seemed to recognize that another member was gone, but as stated, we
were severly boxed up. We're researching, telling IBM, and any one else
who
will perhaps have a clue, such as the membership of this forum.
Monday - and I'm only allowed 1 cup of coffee per day!
----------------------------------------------------------------------
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
Note that my email domain has changed from jo-annstores.com to
joann.com. Please update your address book and other records to reflect
this change.
CONFIDENTIALITY/EMAIL NOTICE: The material in this transmission contains
confidential and privileged information intended only for the addressee.
If you are not the intended recipient, please be advised that you have
received this material in error and that any forwarding, copying,
printing, distribution, use or disclosure of the material is strictly
prohibited. If you have received this material in error, please (i) do
not read it, (ii) reply to the sender that you received the message in
error, and (iii) erase or destroy the material. Emails are not secure
and can be intercepted, amended, lost or destroyed, or contain viruses.
You are deemed to have accepted these risks if you communicate with us
by email. 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
----------------------------------------------------------------------
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
