The short answer is that what you want to do is very possible. We've been 
running with similar configurations for many years through various hardware 
combinations and LPAR distribution. Our specific IEASYMxx members would 
probably not fit your particular needs and are overly complicated anyway. I can 
offer a few suggestions. 

1. In addition to SYM, you also want two LOADxx members. When we IPL in 
'normal' mode, we use LOAD00. When we IPL in DR mode, we use LOADDR. The choice 
is determined by the load parm value in the IPL profile: '00' for normal 
profile, 'DR' for DR mode profile. That suffix is appended to 'LOAD' to select 
the appropriate member in the IPLPARM library.

2. The primary difference between LOAD00 and LOADDR is the concatenation list 
for IEASYMxx. Within each concatenation, system symbols are set according to 
the environment being IPLed. This accounts for, among other values, different 
CTC addresses, gazinta and gazouta, among LPARs in normal vs. DR configuration.

3. IEASYMxx contains statements like these, which are specified for each 
hardware-LPAR combination, normal or DR mode

SYSDEF HWNAME(box-1) LPARNAME(LPAR-1) /* FOR THIS LPAR-PROCESSOR */ 
                                                                      
    SYSNAME(sysname-1)    /* USE THIS SYSNAME */                        
                                                                     
    SYMDEF(&CTCPID#1='i-xxx,i-yyy')  /* SET INPUT ADDRESS LIST */               
     
    SYMDEF(&CTCPOD#1='o-xxx,o-yyy')  /* SET OUTPUT ADDRESS LIST */              
       
                                                                      
4. Here are some sample statements from COUPLExx. 

COUPLE                                    
         SYSPLEX(SYSPLEX&OURPLXID)  /* Symbol set in IEASYSxx */
         PCOUPLE(SYS1.COUPLE.SYSPLEX1)  
         ACOUPLE(SYS1.COUPLE.SYSPLEX2)    

PATHIN                      /* BACKUP CTC FOR CF */ 
         DEVICE(&CTCPID#1,&CTCPID#2,&CTCPID#3)  /* Symbol strings set in 
IEASYSxx  */    
                                                    
PATHOUT                     /* BACKUP CTC FOR CF */ 
         DEVICE(&CTCPOD#1,&CTCPOD#2,&CTCPOD#3)   /* Symbol strings set in 
IEASYSxx  */   
         CLASS(DEFSMALL)                            

You're on the right track. You should be able to completely initialize either 
environment by changing only the HMC load parm, which really means choosing--by 
name--between a 'normal' profile and the corresponding 'DR' profile. 

If you have not done so, install the SYSPARM dialog from SYS1.SAMPLIB(SPPINST). 
It is immensely helpful in testing system symbol settings. 

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
jo.skip.robin...@sce.com

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Anonymous
Sent: Saturday, February 21, 2015 2:04 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: IEASYMxx: How is possible define more than one LPARNAME at same time 
in SYSDEF?

Hi, all

Is possible define more than one LPARNAME at same time in the parameter SYSDEF 
in the IEASYMxx member?

I try to explain our problem:

We have two z196 in different buildings. The definition is the following:

z196-1:
with the following LPARs: PROD1, PROD2 and TEST1 and
z196-2:
with the following LPARs: PROD3, PROD4 and TEST2

The problem that we have is that in the movements of FDR (Full Disaster 
Recovery) some Partitions change to the other building, except the Partitions 
TEST-1 and TEST-2 and the  channel addresses for CTC (FICON) are different 
according to definition in the IODF for each Building (z196-1 or z196-2).

That is, after FDR final test the situation is as follows:

z196-1:
has the following LPARs: PROD3, PROD4 and TEST1 and
z196-2:
has the following LPARs: PROD1, PROD2 and TEST2

The LPARs: TEST1 and TEST2 never change your location, however the channel 
addresses for CTCs are now different to connect with the new partitions that 
have been moved to the z196-1 or z196-2.

Q.1) Can be possible to use a definition of Symbols like this..?

SYSDEF HWNAME (z196-1) LPARNAME (PROD1) LPARNAME (PROD2) LPARNAME (TEST1)
        SYMDEF (&CTCP1T1 = '662E') / * CTC BETWEEN PROD1 - TEST1 * /
        .....................................
        SYMDEF (&CTCP2T1 = '6822') / * CTC BETWEEN PROD2 - TEST1 * /

Q.2) It would be possible to use combinations (ie. as in REXX) ​​using special 
characters like '&' (AND) '|' (OR) in the IEASYM..?

SYSDEF HWNAME (z196-1) & LPARNAME (PROD1) & LPARNAME (PROD2) LPARNAME (TEST1)


for example, if we use the following combination:
SYSDEF HWNAME (z196-1) LPARNAME (TEST1)
        SYMDEF (&CTCP1T1 = '662E') / * CTC BETWEEN PROD1 - TEST1 * /

it does not work because the channel addresses for CTC of TEST1 are different 
when after FDR has to connect with the new LPARs: PROD3 and PROD4 (and in this 
case, the Partition PROD1 doesn't exist in the machine z196-1).

Q.3) Then. How could define in the same configuration of the IEASYM member to 
before and after of the FDR movement..?

It is important to mention that the channel addresses for CTC are different in 
a z196-1 with respect to the channel addresses for CTC in the other z196-2 
(different building). There are not have a specific IEASYSxx and IEASYMxx 
settings for FDR because we only use two LOADxx members where they have defined 
in the IODF the Partitions directly with a matrix for the CHPIDs for one 
Building (z196-1) and other different matrix (also with different CHPIDs) for 
the other Building (z196-2).

Q.4) Please, someone have any idea about it..?
No matter how complex can become the definition of IEASYMxx if with that 
definition a solution is found.

Honestly, I'm confused because I do not find a way to merge two partitions that 
always move to another machine, with a partition (TEST1) that never moves from 
that machine (z196-1) and vice versa (TEST2 never moves from z196-2).

Any ideas are welcome.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to