120 EFS Systems on a Linux Base: Additional Topics
We modified the TCPIP, FTPD, NFSC, and NFSS procedures because we created a separate
TCPIP profile data set for each system. For example, here is our procedure for TCPIP:
//TCPIP EXEC PGM=EZBTCPIP,REGION=0M,TIME=1440,
// PARM='&PARMS'
//STEPLIB DD DSN=ADCD.ZOSV1R4.VTAMLIB,DISP=SHR
//SYSPRINT DD SYSOUT=*,DCB=(RECFM=VB,LRECL=132,BLKSIZE=136)
//ALGPRINT DD SYSOUT=*,DCB=(RECFM=VB,LRECL=132,BLKSIZE=136)
//CFGPRINT DD SYSOUT=*,DCB=(RECFM=VB,LRECL=132,BLKSIZE=136)
//SYSOUT DD SYSOUT=*,DCB=(RECFM=VB,LRECL=132,BLKSIZE=136)
//CEEDUMP DD SYSOUT=*,DCB=(RECFM=VB,LRECL=132,BLKSIZE=136)
//SYSERROR DD SYSOUT=*
//PROFILE DD DISP=SHR,DSN=TCPIP.&SYSNAME..PROFILE.TCPIP
//SYSTCPD DD DSN=TCPIP.&SYSNAME..TCPIP.DATA,DISP=SHR
With this method, we selected TCPIP.ZOS1.PROFILE.TCPIP and TCPIP.ZOS1.TCPIP.DATA
when zos1 was IPLed.
8.12 Couple data set preparation
A primary couple data set is required for the sysplex to operate; several other couple data
sets must be defined for various purposes. Some are required and others are optional. We
describe only the required ones.
Creating the couple data sets is described in detail in MVS: Setting up a Sysplex,
SA22-7625-05. Each couple data set contains the name of the sysplex; for this reason, since
we changed the name of our sysplex, we could not use the data sets in the ADCD distribution.
The procedure to create new data sets was very straightforward, however.
Sysplex couple data set
To create the primary couple data set and a backup, we used this job:
//COUPLEDS JOB ('0'),'FLEX',CLASS=Z,MSGCLASS=A
//S1 EXEC PGM=IDCAMS,REGION=30M
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DELETE SYS1.ZPLEX.CDS01
DELETE SYS1.ZPLEX.CDS02
SET MAXCC=0
/*
//S EXEC PGM=IXCL1DSU,REGION=30M
//STEPLIB DD DSN=SYS1.MIGLIB,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DEFINEDS SYSPLEX(ZPLEX)
DSN(SYS1.ZPLEX.CDS01) VOLSER(ZP4CDS)
MAXSYSTEM(8)
CATALOG
DATA TYPE(SYSPLEX)
ITEM NAME(GROUP) NUMBER(32)
ITEM NAME(MEMBER) NUMBER(64)
ITEM NAME(GRS) NUMBER(1)
DEFINEDS SYSPLEX(ZPLEX)
DSN(SYS1.ZPLEX.CDS02) VOLSER(ZP4SMS)
MAXSYSTEM(8)
CATALOG
DATA TYPE(SYSPLEX)
ITEM NAME(GROUP) NUMBER(32)
Chapter 8. z/OS base sysplex on z/VM 121
ITEM NAME(MEMBER) NUMBER(64)
ITEM NAME(GRS) NUMBER(1)
/*
//
Couple data sets are created with the IXCL1DSU utility as described in MVS: Setting up a
Sysplex. A base sysplex may or may not use the ARM, SFM, and LOGR data sets to good
advantage. The SYSPLEX, WLM, and OMVS data sets are mandatory for the system to
function properly, however.
COUPLEnn members of PARMLIB
Couple data sets are cataloged in the master catalog and are specified in the COUPLEnn
member of PARMLIB selected for a given IPL. Our COUPLEnn members were identical with
the exception of the PATHIN and PATHOUT statements. In COUPLE01, used by zos1 (shown
below), we specified PATHIN of 1032 and PATHOUT of 1031; in COUPLE02, we reversed the
specification, coding PATHIN of 1031 and PATHOUT of 1032.
COUPLE SYSPLEX(&SYSPLEX.)
INTERVAL(85)
PCOUPLE(SYS1.&SYSPLEX..CDS01)
ACOUPLE(SYS1.&SYSPLEX..CDS02)
DATA TYPE(LOGR)
PCOUPLE(SYS1.&SYSPLEX..LOGR.CDS01)
ACOUPLE(SYS1.&SYSPLEX..LOGR.CDS02)
DATA TYPE(BPXMCDS)
PCOUPLE(SYS1.&SYSPLEX..OMVS.CDS01)
ACOUPLE(SYS1.&SYSPLEX..OMVS.CDS02)
DATA TYPE(WLM)
PCOUPLE(SYS1.&SYSPLEX..WLM.CDS01)
ACOUPLE(SYS1.&SYSPLEX..WLM.CDS02)
DATA TYPE(SFM)
PCOUPLE(SYS1.&SYSPLEX..SFM.CDS01)
ACOUPLE(SYS1.&SYSPLEX..SFM.CDS02)
DATA TYPE(ARM)
PCOUPLE(SYS1.&SYSPLEX..ARM.CDS01)
ACOUPLE(SYS1.&SYSPLEX..ARM.CDS02)
PATHIN DEVICE(1032) MAXMSG(10240) RETRY(15)
PATHOUT DEVICE(1031) MAXMSG(10240) RETRY(15)
LOCALMSG MAXMSG(8192)
IBM recommends that each class of couple data sets have both a primary and an alternate,
and that’s how we did it. The SYSPLEX primary and alternate are used by XCF to store
information about the systems in the sysplex, the members running in the sysplex, and status
information. The OMVS couple data sets must be defined before UNIX System Services can
properly share file systems among the members of a sysplex; without it, UNIX Systems
Services sessions will fail. The WLM couple data set is used to store the Workload Manager
service definitions. See MVS Planning: Workload Management, SA22-7602-05, for more
information.
Note that the couple data set defined the inbound and outbound CTC connections. The
systems automatically contacted each other on these connections; no other information was
required beyond the device numbers.
OMVS couple data set
We created a new OMVS couple data set with this job:
//OMVSDS JOB ('0'),FLEX,CLASS=Z,MSGCLASS=A
//S EXEC PGM=IXCL1DSU,REGION=30M
//STEPLIB DD DSN=SYS1.MIGLIB,DISP=SHR
122 EFS Systems on a Linux Base: Additional Topics
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DEFINEDS SYSPLEX(ZPLEX)
DSN(SYS1.ZPLEX.OMVS.CDS01) VOLSER(ZP4SMS)
CATALOG
MAXSYSTEM(8)
DATA TYPE(BPXMCDS)
ITEM NAME(MOUNTS) NUMBER(500)
ITEM NAME(AMTRULES) NUMBER(50)
DEFINEDS SYSPLEX(ZPLEX)
DSN(SYS1.ZPLEX.OMVS.CDS02) VOLSER(ZP4LOG)
CATALOG
MAXSYSTEM(8)
DATA TYPE(BPXMCDS)
ITEM NAME(MOUNTS) NUMBER(500)
ITEM NAME(AMTRULES) NUMBER(50)
/*
//
WLM couple data set
We created the WLM couple data set with this job:
//WLMDS JOB ('0'),FLEX,CLASS=Z,MSGCLASS=A
//S EXEC PGM=IXCL1DSU,REGION=30M
//STEPLIB DD DSN=SYS1.MIGLIB,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DEFINEDS SYSPLEX(ZPLEX)
DSN(SYS1.ZPLEX.WLM.CDS01) VOLSER(ZP4LOG)
CATALOG
DATA TYPE(WLM)
ITEM NAME(POLICY) NUMBER(10)
ITEM NAME(WORKLOAD) NUMBER(35)
ITEM NAME(SRVCLASS) NUMBER(30)
ITEM NAME(SVDEFEXT) NUMBER(5)
ITEM NAME(SVDCREXT) NUMBER(5)
ITEM NAME(APPLENV) NUMBER(100)
ITEM NAME(SVAEAEXT) NUMBER(5)
ITEM NAME(SCHENV) NUMBER(100)
ITEM NAME(SVSEAEXT) NUMBER(5)
DEFINEDS SYSPLEX(ZPLEX)
DSN(SYS1.ZPLEX.WLM.CDS02) VOLSER(ZP4SMS)
MAXSYSTEM(8)
CATALOG
DATA TYPE(WLM)
ITEM NAME(POLICY) NUMBER(10)
ITEM NAME(WORKLOAD) NUMBER(35)
ITEM NAME(SRVCLASS) NUMBER(30)
ITEM NAME(SVDEFEXT) NUMBER(5)
ITEM NAME(SVDCREXT) NUMBER(5)
ITEM NAME(APPLENV) NUMBER(100)
ITEM NAME(SVAEAEXT) NUMBER(5)
ITEM NAME(SCHENV) NUMBER(100)
ITEM NAME(SVSEAEXT) NUMBER(5)
/*

Get S/390 PartnerWorld for Developers, ITSO/EFS Project EFS Systems on a Linux Base: Additional Topics now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.