I can't remember exactly what you are replying to, but I'm guessing that
someone
must have said that you must duplicate the lines in IEASYMxx for your
production LPAR and your DR VM Guest. The definitions can be an exact
replication, or you may have some differences between the two. With a bunch
of junk removed to shorten it, here's what I have. This should
get you started:
SYSDEF
SYMDEF(&IPLV1='&SYSR1')
SYMDEF(&IPLV2='&SYSR1(1:5).2')
SYMDEF(&IPLV3='&SYSR1(1:5).3')
SYMDEF(&IPLV4='&SYSR1(1:5).4')
/* VM GUEST HMIPRD1 FOR SYSTEM PRD1 AT SUNGARD */
/* SYNC ALL CHANGES WITH THE ENTRY FOR HWNAME(HMI1)*/
SYSDEF
VMUSERID(HMIPRD1)
SYSNAME(HMI1)
/* LPAR PRD1 SYSTEM MVS SPECIFIC DEFINITIONS */
/* SYNC ALL CHANGE WITH ENTRY FOR VMUSERID(HMIPRD1)*/
SYSDEF
HWNAME(HMI1)
LPARNAME(PRD1)
SYSNAME(HMI1)
Tom Chicklon
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Lizette Koehler
Sent: Friday, May 04, 2007 11:20 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: MVS as a guest OS at D/R
I am working on setting up our DR constructs and am interested in having one
IEASYSM member for both DR and normal.
When you say must be duplicate, does that mean that you have the
VMUSERID be the same as the LPARNAME? I thought the VMUSERID was
specific to the hot site requiremenst?
I am just getting into this, so sorry for a basic question.
Lizette
----------------------------------------------------------------------
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
