We migrated from z/OS R4 to z/OS R6 and allowed the default to be in
effect so we implemented SYNCRES=YES on each system at the same time as
z/OS R6.  We ran a mixed level Sysplex for many months as the migration
of R6 onto a couple production LPARs had some interesting technical
challenges.

SYNCRES=YES is recommended as a best practice by the Health Checker for
z/OS. 

CHECK(IBMGRS,GRS_SYNCHRES)                                              
START TIME: 01/23/2007 17:54:46.124930                                  
CHECK DATE: 20050105  CHECK SEVERITY: LOW                               
                                                                        
ISGH0304I Global Resource Serialization synchronous RESERVE processing  
is active. This is consistent with the IBM suggestion for Global        
Resource Serialization synchronous RESERVE processing.                  
                                                                        
END TIME: 01/23/2007 17:54:46.125948  STATUS: SUCCESSFUL                

We saw no ill effects or need to override the default in R6 till we
implemented it across the Sysplex.

        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 Greg Saccomanno
Sent: Tuesday, January 23, 2007 2:04 PM
To: [email protected]
Subject: z/OS 1.7 SYNCHRES=YES & z/OS 14 SYNCHRES=NO

I have checked the manuals and the archives on this and I am still
unsure about mixing the yes and no values for SYNCHRES in a GRSPlex
(Basic sysplex if that matters any).  I need to bring my TEST LPAR into
our plex for testing.  I would rather wait until either our outage
weekend next month to change the value of this on the systems that are
already in the sysplex or until each cuts over to 1.7 but I need to
bring the TEST system up in the plex and test before I can migrate 1.7
to the next system. I see that I can change the value via the SETGRS
command and I guess I could always code the 1.7 system as SYNCRES=NO for
this phase but from the way I interpret the FM it doesn't seem like it
should be a concern.  However, nothing I found gave a definitive answer.
Does anyone know of any problems with having two z/OS 1.4 systems with
SYNCHRES=NO and a z/OS 1.7 systems with SYNCHRES=YES active in a basic
sysplex?  Has anyone run this way when migrating to 1.7 from 1.4?

Thank you,
Greg 
====================
This email/fax message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution of this
email/fax is prohibited. If you are not the intended recipient, please
destroy all paper and electronic copies of the original message.

----------------------------------------------------------------------
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

Reply via email to