S/390 PartnerWorld for Developers, ITSO/EFS Project EFS Systems on a Linux Base: Additional Topics

Chapter 8. z/OS base sysplex on z/VM 115

SYSCLONE(01)

SYMDEF(&UNIXVER='V1R4M0')

SYMDEF(&SYSR2.='ZP4RS2')

SYMDEF(&SYSSYS.='ZP4SYS')

SYSNAME named the system. We used the SYSCLONE number when we needed a

numeric index for the systems. UNIXVER was used to mount the proper HFS for UNIX

System Services. SYSR2 was the second residence volume and SYSSYS named the volume

containing the master catalog and SYS1.IPLPARM (this volume was similar to OS39M1 in the

standard ADCD volume set).

Our IEASYM02 member contained:

SYSDEF SYSNAME(ZOS2)

SYSCLONE(02)

SYMDEF(&UNIXVER='V1R4M0')

SYMDEF(&SYSR2.='ZP4RS2')

SYMDEF(&SYSSYS.='ZP4SYS')

We were thus able to set the system ID elsewhere in PARMLIB and PROCLIB using the

&SYSNAME variable. For example, we set the SMF system ID and we give each system its

own SMF data sets this way in SMFPRM00:

ACTIVE

DSNAME(ZPLEX.&SYSNAME..MAN1A,

ZPLEX.&SYSNAME..MAN1B,

ZPLEX.&SYSNAME..MAN1C,

ZPLEX.&SYSNAME..MAN1D,

ZPLEX.&SYSNAME..MAN1E,

ZPLEX.&SYSNAME..MAN2A )

NOPROMPT

REC(PERM)

MAXDORM(3000)

STATUS(010000)

JWT(1200)

SID(&SYSNAME)

LISTDSN

SYS( NOTYPE(14:17,19,62:69),

EXITS(IEFU83,IEFU84,IEFACTRT,IEFUSI,IEFUJI,IEFU29),

NOINTERVAL,

NODETAIL )

SUBSYS(STC,EXITS(IEFU29,IEFU83,IEFU84,IEFUJP,IEFUSO))

This scheme allowed us to have separate SMF data sets for each system, which was required

if we wanted to collect SMF data. Note that JES2 used the SMF system ID as the MAS

member name because no other name was given in JES2PARM.

8.11.1 Other IPL parameters

Several other PARMLIB members needed minor adjustments.

IEASYS00 member of PARMLIB

All systems were IPLed with the same, default, member of ZPLEX.PARMLIB:

CLOCK=00,

CMB=(UNITR,COMM,GRAPH,CHRDR),

CMD=00,

CON=(00,NOJES3),

COUPLE=&SYSCLONE,

CSA=(3000,40000),

116 EFS Systems on a Linux Base: Additional Topics

CVIO,

DIAG=00,

DUMP=DASD,

FIX=00,

GRS=TRYJOIN,

GRSCNF=00,

GRSRNL=00,

ILMMODE=NONE,

IOS=00,

LNKAUTH=LNKLST,

LOGCLS=L,

LOGLMT=999999,

LOGREC=SYS1.&SYSNAME..LOGREC,

LPA=00,

MAXUSER=250,

MLPA=00,

MSTRJCL=00,

OMVS=00,

OPI=YES,

PAGTOTL=(12),

PAGE=(SYS1.&SYSNAME..PLPA.PAGE,

SYS1.&SYSNAME..COMMON.PAGE,

SYS1.&SYSNAME..LOCAL.PAGE,L),

PAK=00,

PROD=00,

PROG=00,

PLEXCFG=MULTISYSTEM,

REAL=128, ALLOWS 2 64K OR 1 128K JOB TO RUN V=R

RSU=0, NO RECONFIG STORAGE UNITS

RSVNONR=100, RESERVED ASVT ENTRIES

RSVSTRT=5, RESERVED ASVT ENTRIES

SCH=00, SELECT SCHED00

SMF=00, SELECT SMFPRM00,SMF PARAMETERS

SMS=00,

SQA=(15,64), SQA SIZE APPROX 640K

SSN=00,

SVC=00,

VAL=00, SELECT VATLST00

VIODSN=SYS1.&SYSNAME..STGINDEX, VIO DS

VRREGN=64 DEFAULT REAL-STORAGE REGION SIZE

Most of the items in the parameter list applied equally to all images; some of them, however,

were customized for sysplex operation or on a per-image basis:

򐂰 COUPLE=&SYSCLONE selected one of the COUPLEnn members of PARMLIB,

depending upon which system was initializing. The &SYSCLONE variable was set by the

selected IEASYMnn member of PARMLIB. When we IPLed as z/VM user zos1, member

IEASYM01 set &SYSLCLONE=01, this parameter became COUPLE=01,and member

COUPLE01 was selected for the IPL. When we IPLed with z/VM user ID zos2, then

member IEASYM02 set &SYSCLONE=02, this parameter became COUPLE=02,and

member COUPLE02 was selected for the IPL. We needed to select different COUPLE

members so that the PATHIN and PATHOUT statements that identify the CTC connections

were correct for the initializing member.

򐂰 GRS=TRYJOIN told the Global Resource Serialization component to attempt to join a

GRS ring at IPL if one already was running. If no GRS complex existed, then the IPLing

system started the GRS complex. GRS is required for base sysplex. Systems

communicated using the channel-to-channel adapters defined in the COUPLEnn member

of PARMLIB.