Sample definitions
This appendix provides sample definitions to help you get your sysplex up and running in a timely manner and with minimal manual effort. Each sample is described in the relevant section in this book.
This appendix includes the following topics:
Sample devmap file
The devmap that is shown in Example A-1 contains definitions for the standard ADCD volumes (z/VM and z/OS) and the extra volumes that are provided or required by the zPDT 2017 Sysplex Extensions.
Example A-1 Sample devmap file
#Sample definitions for 2017 Sysplex Extensions package
[system]
memory 10000m
3270port 3270
processors 1
command 2 x3270 localhost:3270
command 2 x3270 localhost:3270
command 2 x3270 localhost:3270
command 2 x3270 localhost:3270
command 2 x3270 localhost:3270
command 2 x3270 localhost:3270
command 2 x3270 localhost:3270
[manager]
name aws3274 1
device 0700 3279 3174 L700
device 0701 3279 3174 L701
device 0702 3279 3174 L702
device 0703 3279 3174 L703
device 0704 3279 3174 L704
device 0705 3279 3174 L705
device 0706 3279 3174 L706
device 0707 3279 3174 L707
device 0708 3279 3174 L708
device 0709 3279 3174 L709
device 070A 3279 3174 L70A
device 070B 3279 3174 L70B
device 070C 3279 3174 L70C
device 070D 3279 3174 L70D
device 070E 3279 3174 L70E
device 070F 3279 3174 L70F
device 0710 3279 3174 L710
device 0711 3279 3174 L711
device 0712 3279 3174 L712
device 0713 3279 3174 L713
device 0714 3279 3174 L714
device 0715 3279 3174 L715
device 0716 3279 3174 L716
device 0717 3279 3174 L717
device 0718 3279 3174 L718
device 0719 3279 3174 L719
device 071A 3279 3174 L71A
device 071B 3279 3174 L71B
device 071C 3279 3174 L71C
device 071D 3279 3174 L71D
device 071E 3279 3174 L71E
device 071F 3279 3174 L71F
[manager]
name awsckd 27
device 0200 3390 3990 M01RES
device 0201 3390 3990 VMCOM1
device 0202 3390 3990 M01W01
device 0203 3390 3990 M01S01
device 0204 3390 3990 M01P01
device 0205 3390 3990 640RL1
[manager]
name awsckd 28
device 0a80 3390 3990 D2RES1
device 0a81 3390 3990 D2RES2
device 0a82 3390 3990 D2SYS1
device 0a83 3390 3990 D2CFG1
device 0a84 3390 3990 D2USS1
device 0a85 3390 3990 D2USS2
device 0a86 3390 3990 D2PAGA
device 0a87 3390 3990 D2PAGB
device 0a88 3390 3990 D2PAGC
device 0a89 3390 3990 D2PRD1
device 0a8a 3390 3990 D2PRD2
device 0a8b 3390 3990 D2PRD3
device 0a8c 3390 3990 D2C521
device 0a8d 3390 3990 D2DBB1
device 0a8e 3390 3990 D2DBB2
[manager]
name awsckd 29
device 0a9e 3390 3990 CF0001
device 0ab5 3390 3990 CICS01
device 0ab6 3390 3990 DB2001
device 0ab7 3390 3990 WORK01
device 0ab8 3390 3990 D2PAGX
device 0ab9 3390 3990 D2PAGY
device 0aba 3390 3990 D2PAGZ
device 0abb 3390 3990 D2SYS2
device 0abf 3390 3990 SARES1
[manager]
name awsosa 0023 --path=A0 --pathtype=OSD --tunnel_intf=y
device 400 osa osa
device 401 osa osa
device 402 osa osa
device 408 osa osa
device 409 osa osa
device 40A osa osa
[manager]
name awsosa 0024 --path=f2 --pathtype=OSD
device 404 osa osa
device 405 osa osa
device 406 osa osa
device 40C osa osa
device 40D osa osa
device 40E osa osa
[manager]
name awsctc 100
device e40 3088 3088 ctc://192.168.1.99:4000/e41
device e41 3088 3088 ctc://192.168.1.99:4001/e40
The numbers on the name awsckd statements are random. The only requirement is that they must be unique within that devmap file.
Use the zPDT find_io command to determine the value to specify on the path= statement on the awsosa definitions. The PATH for the tunnel interface always appears to be A0, but the PATH for the network interface is impossible to predict. Therefore, you must check which is the active network interface on your PC and insert that value here.
Sample z/VM Directory entries
The VM Directory statements in Example A-2, Example A-3 on page 118, Example A-4 on page 119, Example A-5 on page 121, Example A-6 on page 123, and Example A-7 on page 123 contain definitions for a VM user ID that acts as the owner of the z/OS volumes (MVSDUMMY), one non-sysplex guest (BASEAD), the two Parallel Sysplex systems (S0W1 and S0W2), and the two CFVMs (CFCC1 and CFCC2).
|
Note: All of these user IDs are defined in the ADCD-provided z/VM directory. They are not provided in the standard directory that is provided with z/VM.
|
Example A-2 The VM Directory statements for MVSDUMMY
USER MVSDUMMY MVSDUMMY 1024M 1024M G
*************************************************
*
* MVSDUMMY OWNS z/OS VOLUMES SO THEY CAN BE SHARED
* Addresses A9E and A9F are for coupling volumes
*
*************************************************
MDISK 0A80 3390 DEVNO 0A80 MWV
MDISK 0A81 3390 DEVNO 0A81 MWV
MDISK 0A82 3390 DEVNO 0A82 MWV
MDISK 0A83 3390 DEVNO 0A83 MWV
MDISK 0A84 3390 DEVNO 0A84 MWV
MDISK 0A85 3390 DEVNO 0A85 MWV
MDISK 0A86 3390 DEVNO 0A86 MWV
MDISK 0A87 3390 DEVNO 0A87 MWV
MDISK 0A88 3390 DEVNO 0A88 MWV
MDISK 0A89 3390 DEVNO 0A89 MWV
MDISK 0A8A 3390 DEVNO 0A8A MWV
MDISK 0A8B 3390 DEVNO 0A8B MWV
MDISK 0A8C 3390 DEVNO 0A8C MWV
MDISK 0A8D 3390 DEVNO 0A8D MWV
MDISK 0A8E 3390 DEVNO 0A8E MWV
MDISK 0A8F 3390 DEVNO 0A8F MWV
MDISK 0A90 3390 DEVNO 0A90 MWV
MDISK 0A91 3390 DEVNO 0A91 MWV
MDISK 0A92 3390 DEVNO 0A92 MWV
MDISK 0A93 3390 DEVNO 0A93 MWV
MDISK 0A94 3390 DEVNO 0A94 MWV
MDISK 0A95 3390 DEVNO 0A95 MWV
MDISK 0A96 3390 DEVNO 0A96 MWV
MDISK 0A97 3390 DEVNO 0A97 MWV
MDISK 0A98 3390 DEVNO 0A98 MWV
MDISK 0A99 3390 DEVNO 0A99 MWV
MDISK 0A9A 3390 DEVNO 0A9A MWV
MDISK 0A9B 3390 DEVNO 0A9B MWV
MDISK 0A9C 3390 DEVNO 0A9C MWV
MDISK 0A9D 3390 DEVNO 0A9D MWV
MDISK 0A9E 3390 DEVNO 0A9E MWV
DASDOPT WRKALLEG
MDISK 0A9F 3390 DEVNO 0A9F MWV
MDISK 0AA0 3390 DEVNO 0AA0 MWV
MDISK 0AA1 3390 DEVNO 0AA1 MWV
MDISK 0AA2 3390 DEVNO 0AA2 MWV
MDISK 0AA3 3390 DEVNO 0AA3 MWV
MDISK 0AA4 3390 DEVNO 0AA4 MWV
MDISK 0AA5 3390 DEVNO 0AA5 MWV
MDISK 0AA6 3390 DEVNO 0AA6 MWV
MDISK 0AA7 3390 DEVNO 0AA7 MWV
MDISK 0AA8 3390 DEVNO 0AA8 MWV
MDISK 0AA9 3390 DEVNO 0AA9 MWV
MDISK 0AAA 3390 DEVNO 0AAA MWV
MDISK 0AAB 3390 DEVNO 0AAB MWV
MDISK 0AAC 3390 DEVNO 0AAC MWV
MDISK 0AAD 3390 DEVNO 0AAD MWV
MDISK 0AAE 3390 DEVNO 0AAE MWV
MDISK 0AAF 3390 DEVNO 0AAF MWV
MDISK 0AB0 3390 DEVNO 0AB0 MWV
MDISK 0AB1 3390 DEVNO 0AB1 MWV
MDISK 0AB2 3390 DEVNO 0AB2 MWV
MDISK 0AB3 3390 DEVNO 0AB3 MWV
MDISK 0AB4 3390 DEVNO 0AB4 MWV
MDISK 0AB5 3390 DEVNO 0AB5 MWV
MDISK 0AB6 3390 DEVNO 0AB6 MWV
MDISK 0AB7 3390 DEVNO 0AB7 MWV
MDISK 0AB8 3390 DEVNO 0AB8 MWV
MDISK 0AB9 3390 DEVNO 0AB9 MWV
MDISK 0ABA 3390 DEVNO 0ABA MWV
MDISK 0ABB 3390 DEVNO 0ABB MWV
MDISK 0ABC 3390 DEVNO 0ABC MWV
MDISK 0ABD 3390 DEVNO 0ABD MWV
MDISK 0ABE 3390 DEVNO 0ABE MWV
MDISK 0ABF 3390 DEVNO 0ABF MWV
Example A-3 contains the definition for the monoplex z/OS system.
Example A-3 The VM Directory statements for BASEAD
USER BASEAD BASEAD 4000M 4000M G
*************************************************
*
* The BASEAD guest allows IPLing z/OS in non-sysplex mode
*
*
*****************************
CPU 0
MACH ESA
DEDICATE 0400 0400
DEDICATE 0401 0401
DEDICATE 0402 0402
CONSOLE 0700 3215 T
SPECIAL 0701 3270
SPECIAL 0702 3270
SPECIAL 0703 3270
SPECIAL 0704 3270
SPECIAL 0705 3270
SPECIAL 0706 3270
SPOOL 000C 2540 READER *
SPOOL 000D 2540 PUNCH A
SPOOL 000E 1403 A
LINK MAINT 0190 0190 RR
LINK MAINT 019D 019D RR
LINK MAINT 019E 019E RR
LINK MVSDUMMY 0A80 0A80 MW
LINK MVSDUMMY 0A81 0A81 MW
LINK MVSDUMMY 0A82 0A82 MW
LINK MVSDUMMY 0A83 0A83 MW
LINK MVSDUMMY 0A84 0A84 MW
LINK MVSDUMMY 0A85 0A85 MW
LINK MVSDUMMY 0A86 0A86 MW
LINK MVSDUMMY 0A87 0A87 MW
LINK MVSDUMMY 0A88 0A88 MW
LINK MVSDUMMY 0A89 0A89 MW
LINK MVSDUMMY 0A8A 0A8A MW
LINK MVSDUMMY 0A8B 0A8B MW
LINK MVSDUMMY 0A8C 0A8C MW
LINK MVSDUMMY 0A8D 0A8D MW
LINK MVSDUMMY 0A8E 0A8E MW
LINK MVSDUMMY 0A8F 0A8F MW
LINK MVSDUMMY 0A90 0A90 MW
LINK MVSDUMMY 0A91 0A91 MW
LINK MVSDUMMY 0A92 0A92 MW
LINK MVSDUMMY 0A93 0A93 MW
LINK MVSDUMMY 0A94 0A94 MW
LINK MVSDUMMY 0A95 0A95 MW
LINK MVSDUMMY 0A96 0A96 MW
LINK MVSDUMMY 0A97 0A97 MW
LINK MVSDUMMY 0A98 0A98 MW
LINK MVSDUMMY 0A99 0A99 MW
LINK MVSDUMMY 0A9A 0A9A MW
LINK MVSDUMMY 0A9B 0A9B MW
LINK MVSDUMMY 0A9C 0A9C MW
LINK MVSDUMMY 0A9D 0A9D MW
LINK MVSDUMMY 0A9E 0A9E MW
LINK MVSDUMMY 0A9F 0A9F MW
LINK MVSDUMMY 0AA0 0AA0 MW
LINK MVSDUMMY 0AA1 0AA1 MW
LINK MVSDUMMY 0AA2 0AA2 MW
LINK MVSDUMMY 0AA3 0AA3 MW
LINK MVSDUMMY 0AA4 0AA4 MW
LINK MVSDUMMY 0AA5 0AA5 MW
LINK MVSDUMMY 0AA6 0AA6 MW
LINK MVSDUMMY 0AA7 0AA7 MW
LINK MVSDUMMY 0AA8 0AA8 MW
LINK MVSDUMMY 0AA9 0AA9 MW
LINK MVSDUMMY 0AAA 0AAA MW
LINK MVSDUMMY 0AAB 0AAB MW
LINK MVSDUMMY 0AAC 0AAC MW
LINK MVSDUMMY 0AAD 0AAD MW
LINK MVSDUMMY 0AAE 0AAE MW
LINK MVSDUMMY 0AAF 0AAF MW
LINK MVSDUMMY 0AB0 0AB0 MW
LINK MVSDUMMY 0AB1 0AB1 MW
LINK MVSDUMMY 0AB2 0AB2 MW
LINK MVSDUMMY 0AB3 0AB3 MW
LINK MVSDUMMY 0AB4 0AB4 MW
LINK MVSDUMMY 0AB5 0AB5 MW
LINK MVSDUMMY 0AB6 0AB6 MW
LINK MVSDUMMY 0AB7 0AB7 MW
LINK MVSDUMMY 0AB8 0AB8 MW
LINK MVSDUMMY 0AB9 0AB9 MW
LINK MVSDUMMY 0ABA 0ABA MW
LINK MVSDUMMY 0ABB 0ABB MW
LINK MVSDUMMY 0ABC 0ABC MW
LINK MVSDUMMY 0ABD 0ABD MW
LINK MVSDUMMY 0ABE 0ABE MW
LINK MVSDUMMY 0ABF 0ABF MW
Example A-4 contains the definition for the first z/OS system in the sysplex.
Example A-4 The VM Directory statements for S0W1
USER S0W1 S0W1 5000M 5000M G 12051039
************************************************* 12051039
* 12051039
* The S0W1 guest is the "1" SYSPLEX z/OS 12051039
* 12051039
************************************************* 12051039
CPU 0 12051039
MACH ESA 12051039
OPTION CFUSER TODENABLE 12051039
DEDICATE 0400 0400 12051039
DEDICATE 0401 0401 12051039
DEDICATE 0402 0402 12051039
DEDICATE 0404 0404 12051039
DEDICATE 0405 0405 12051039
DEDICATE 0406 0406 12051039
CONSOLE 0700 3215 T 12051039
SPECIAL 1400 MSGP CFCC1 12051039
SPECIAL 1500 MSGP CFCC2 12051039
SPECIAL 0701 3270 12051039
SPECIAL 0702 3270 12051039
SPECIAL 0703 3270 12051039
SPECIAL 0704 3270 12051039
SPECIAL 0705 3270 12051039
SPECIAL 0706 3270 12051039
SPOOL 000C 2540 READER * 12051039
SPOOL 000D 2540 PUNCH A 12051039
SPOOL 000E 1403 A 12051039
LINK MAINT 0190 0190 RR 12051039
LINK MAINT 019D 019D RR 12051039
LINK MAINT 019E 019E RR 12051039
LINK MVSDUMMY 0A80 0A80 MW 12051039
LINK MVSDUMMY 0A81 0A81 MW 12051039
LINK MVSDUMMY 0A82 0A82 MW 12051039
LINK MVSDUMMY 0A83 0A83 MW 12051039
LINK MVSDUMMY 0A84 0A84 MW 12051039
LINK MVSDUMMY 0A85 0A85 MW 12051039
LINK MVSDUMMY 0A86 0A86 MW 12051039
LINK MVSDUMMY 0A87 0A87 MW 12051039
LINK MVSDUMMY 0A88 0A88 MW 12051039
LINK MVSDUMMY 0A89 0A89 MW 12051039
LINK MVSDUMMY 0A8A 0A8A MW 12051039
LINK MVSDUMMY 0A8B 0A8B MW 12051039
LINK MVSDUMMY 0A8C 0A8C MW 12051039
LINK MVSDUMMY 0A8D 0A8D MW 12051039
LINK MVSDUMMY 0A8E 0A8E MW 12051039
LINK MVSDUMMY 0A8F 0A8F MW 12051039
LINK MVSDUMMY 0A90 0A90 MW 12051039
LINK MVSDUMMY 0A91 0A91 MW 12051039
LINK MVSDUMMY 0A92 0A92 MW 12051039
LINK MVSDUMMY 0A93 0A93 MW 12051039
LINK MVSDUMMY 0A94 0A94 MW 12051039
LINK MVSDUMMY 0A95 0A95 MW 12051039
LINK MVSDUMMY 0A96 0A96 MW 12051039
LINK MVSDUMMY 0A97 0A97 MW 12051039
LINK MVSDUMMY 0A98 0A98 MW 12051039
LINK MVSDUMMY 0A99 0A99 MW 12051039
LINK MVSDUMMY 0A9A 0A9A MW 12051039
LINK MVSDUMMY 0A9B 0A9B MW 12051039
LINK MVSDUMMY 0A9C 0A9C MW 12051039
LINK MVSDUMMY 0A9D 0A9D MW 12051039
LINK MVSDUMMY 0A9E 0A9E MW 12051039
LINK MVSDUMMY 0A9F 0A9F MW 12051039
LINK MVSDUMMY 0AA0 0AA0 MW 12051039
LINK MVSDUMMY 0AA1 0AA1 MW 12051039
LINK MVSDUMMY 0AA2 0AA2 MW 12051039
LINK MVSDUMMY 0AA3 0AA3 MW 12051039
LINK MVSDUMMY 0AA4 0AA4 MW 12051039
LINK MVSDUMMY 0AA5 0AA5 MW 12051039
LINK MVSDUMMY 0AA6 0AA6 MW 12051039
LINK MVSDUMMY 0AA7 0AA7 MW 12051039
LINK MVSDUMMY 0AA8 0AA8 MW 12051039
LINK MVSDUMMY 0AA9 0AA9 MW 12051039
LINK MVSDUMMY 0AAA 0AAA MW 12051039
LINK MVSDUMMY 0AAB 0AAB MW 12051039
LINK MVSDUMMY 0AAC 0AAC MW 12051039
LINK MVSDUMMY 0AAD 0AAD MW 12051039
LINK MVSDUMMY 0AAE 0AAE MW 12051039
LINK MVSDUMMY 0AAF 0AAF MW 12051039
LINK MVSDUMMY 0AB0 0AB0 MW 12051039
LINK MVSDUMMY 0AB1 0AB1 MW 12051039
LINK MVSDUMMY 0AB2 0AB2 MW 12051039
LINK MVSDUMMY 0AB3 0AB3 MW 12051039
LINK MVSDUMMY 0AB4 0AB4 MW 12051039
LINK MVSDUMMY 0AB5 0AB5 MW 12051039
LINK MVSDUMMY 0AB6 0AB6 MW 12051039
LINK MVSDUMMY 0AB7 0AB7 MW 12051039
LINK MVSDUMMY 0AB8 0AB8 MW 12051039
LINK MVSDUMMY 0AB9 0AB9 MW 12051039
LINK MVSDUMMY 0ABA 0ABA MW 12051039
LINK MVSDUMMY 0ABB 0ABB MW 12051039
LINK MVSDUMMY 0ABC 0ABC MW 12051039
LINK MVSDUMMY 0ABD 0ABD MW 12051039
LINK MVSDUMMY 0ABE 0ABE MW 12051039
LINK MVSDUMMY 0ABF 0ABF MW 12051039
Example A-5 contains the definition for the second z/OS system in the sysplex.
Example A-5 The VM Directory statements for S0W2
UUSER S0W2 S0W2 5000M 5000M G 12051040
************************************************* 12051040
* 12051040
* The S0W2 guest is the sysplex "2" system 12051040
* 12051040
************************************************* 12051040
CPU 0 12051040
MACH ESA 12051040
OPTION CFUSER TODENABLE 12051040
DEDICATE 0408 0408 12051040
DEDICATE 0409 0408 12051040
DEDICATE 040A 040A 12051040
DEDICATE 040C 040C 12051040
DEDICATE 040D 040D 12051040
DEDICATE 040E 040E 12051040
CONSOLE 0700 3215 T 12051040
SPECIAL 1400 MSGP CFCC1 12051040
SPECIAL 1500 MSGP CFCC2 12051040
SPECIAL 0701 3270 12051040
SPECIAL 0702 3270 12051040
SPECIAL 0703 3270 12051040
SPECIAL 0704 3270 12051040
SPECIAL 0705 3270 12051040
SPECIAL 0706 3270 12051040
SPOOL 000C 2540 READER * 12051040
SPOOL 000D 2540 PUNCH A 12051040
SPOOL 000E 1403 A 12051040
LINK MAINT 0190 0190 RR 12051040
LINK MAINT 019D 019D RR 12051040
LINK MAINT 019E 019E RR 12051040
LINK MVSDUMMY 0A80 0A80 MW 12051040
LINK MVSDUMMY 0A81 0A81 MW 12051040
LINK MVSDUMMY 0A82 0A82 MW 12051040
LINK MVSDUMMY 0A83 0A83 MW 12051040
LINK MVSDUMMY 0A84 0A84 MW 12051040
LINK MVSDUMMY 0A85 0A85 MW 12051040
LINK MVSDUMMY 0A86 0A86 MW 12051040
LINK MVSDUMMY 0A87 0A87 MW 12051040
LINK MVSDUMMY 0A88 0A88 MW 12051040
LINK MVSDUMMY 0A89 0A89 MW 12051040
LINK MVSDUMMY 0A8A 0A8A MW 12051040
LINK MVSDUMMY 0A8B 0A8B MW 12051040
LINK MVSDUMMY 0A8C 0A8C MW 12051040
LINK MVSDUMMY 0A8D 0A8D MW 12051040
LINK MVSDUMMY 0A8E 0A8E MW 12051040
LINK MVSDUMMY 0A8F 0A8F MW 12051040
LINK MVSDUMMY 0A90 0A90 MW 12051040
LINK MVSDUMMY 0A91 0A91 MW 12051040
LINK MVSDUMMY 0A92 0A92 MW 12051040
LINK MVSDUMMY 0A93 0A93 MW 12051040
LINK MVSDUMMY 0A94 0A94 MW 12051040
LINK MVSDUMMY 0A95 0A95 MW 12051040
LINK MVSDUMMY 0A96 0A96 MW 12051040
LINK MVSDUMMY 0A97 0A97 MW 12051040
LINK MVSDUMMY 0A98 0A98 MW 12051040
LINK MVSDUMMY 0A99 0A99 MW 12051040
LINK MVSDUMMY 0A9A 0A9A MW 12051040
LINK MVSDUMMY 0A9B 0A9B MW 12051040
LINK MVSDUMMY 0A9C 0A9C MW 12051040
LINK MVSDUMMY 0A9D 0A9D MW 12051040
LINK MVSDUMMY 0A9E 0A9E MW 12051040
LINK MVSDUMMY 0A9F 0A9F MW 12051040
LINK MVSDUMMY 0AA0 0AA0 MW 12051040
LINK MVSDUMMY 0AA1 0AA1 MW 12051040
LINK MVSDUMMY 0AA2 0AA2 MW 12051040
LINK MVSDUMMY 0AA3 0AA3 MW 12051040
LINK MVSDUMMY 0AA4 0AA4 MW 12051040
LINK MVSDUMMY 0AA5 0AA5 MW 12051040
LINK MVSDUMMY 0AA6 0AA6 MW 12051040
LINK MVSDUMMY 0AA7 0AA7 MW 12051040
LINK MVSDUMMY 0AA8 0AA8 MW 12051040
LINK MVSDUMMY 0AA9 0AA9 MW 12051040
LINK MVSDUMMY 0AAA 0AAA MW 12051040
LINK MVSDUMMY 0AAB 0AAB MW 12051040
LINK MVSDUMMY 0AAC 0AAC MW 12051040
LINK MVSDUMMY 0AAD 0AAD MW 12051040
LINK MVSDUMMY 0AAE 0AAE MW 12051040
LINK MVSDUMMY 0AAF 0AAF MW 12051040
LINK MVSDUMMY 0AB0 0AB0 MW 12051040
LINK MVSDUMMY 0AB1 0AB1 MW 12051040
LINK MVSDUMMY 0AB2 0AB2 MW 12051040
LINK MVSDUMMY 0AB3 0AB3 MW 12051040
LINK MVSDUMMY 0AB4 0AB4 MW 12051040
LINK MVSDUMMY 0AB5 0AB5 MW 12051040
LINK MVSDUMMY 0AB6 0AB6 MW 12051040
LINK MVSDUMMY 0AB7 0AB7 MW 12051040
LINK MVSDUMMY 0AB8 0AB8 MW 12051040
LINK MVSDUMMY 0AB9 0AB9 MW 12051040
LINK MVSDUMMY 0ABA 0ABA MW 12051040
LINK MVSDUMMY 0ABB 0ABB MW 12051040
LINK MVSDUMMY 0ABC 0ABC MW 12051040
LINK MVSDUMMY 0ABD 0ABD MW 12051040
LINK MVSDUMMY 0ABE 0ABE MW 12051040
LINK MVSDUMMY 0ABF 0ABF MW 12051040
Example A-6 contains the definition for the first coupling facility (CF) virtual machine. The SPECIAL 1600 MSGP statement defines a virtual coupling link between CFCC1 and CFCC2. This link is required if you want to use System Managed Duplexing between the two CFs.
Example A-6 The VM Directory statements for CFCC1
USER CFCC1 CFCC1 5000M 5000M G
*************************************************
*
* CFCC1 is the first coupling facility
*
*************************************************
MACH ESA
OPTION CFVM TODENABLE
XAUTOLOG CFCONSOL
CONSOLE 0009 3215 T CFCONSOL
SPECIAL 1600 MSGP CFCC2
Example A-7 contains the definition for the second coupling facility virtual machine. The SPECIAL 1600 MSGP statement defines the CFCC2 end of the virtual coupling link to CFCC1.
Example A-7 The VM Directory statements for CFCC2
USER CFCC2 CFCC2 5000M 5000M G
*************************************************
*
* CFCC2 is the first coupling facility
*
*************************************************
MACH ESA
OPTION CFVM TODENABLE
XAUTOLOG CFCONSOL
CONSOLE 0009 3215 T CFCONSOL
SPECIAL 1600 MSGP CFCC1
|
Tip: When we added the CF-to-CF links to our CFs, we had to shut down the entire sysplex, including logging off the CF virtual machines, to get the virtual links between the two CFs to work. This issue might be unique to our environment, but performing a restart in this manner might be faster in the end than trying to add the links dynamically.
|
Devices that are defined in the ADCD-provided IODF
Table A-1 lists the device numbers and device types that are defined in the ADCD-provided input/output definition file (IODF).
Table A-1 Devices defined in z/OS IODF
|
Device number
|
Device type
|
|
00C
|
2540
|
|
00E
|
1403
|
|
00F
|
1403
|
|
0120-015F
|
3380
|
|
0300-0318
|
3390
|
|
0400-040F
|
OSA
|
|
0550-055F
|
3400
|
|
0560-056F
|
3480
|
|
0580-058F
|
3490
|
|
0590-059F
|
3590
|
|
0600-060F
|
3390
|
|
0700-073F
|
3277
|
|
0900-091F
|
3277
|
|
0A80-0AFF
|
3390
|
|
0E20-0E23
|
CTC
|
|
0E40-0E43
|
CTC
|
|
1A00-1AFF
|
3390
|
|
2A00-2AFF
|
3390
|
|
3A00-3AFF
|
3390
|
Sample IEASYMxx member for sysplex
The ADCD-provided IEASYM00 member is designed for a single-system environment. Because there are some values in a sysplex that are system-specific (such as the names of the page data sets), an IEASYMPS member was created that sets system-specific system symbols that are based on the virtual machine user ID as an example of how a single IEASYMxx member can support many systems. The 2017 Sysplex Extensions IEASYMPS member is shown in Example A-8.
Example A-8 2017 Sysplex Extensions provided IEASYMPS member
SYSDEF SYMDEF(&UNIXVER='Z22D')
SYMDEF(&CTSLEVEL='520')
SYMDEF(&SYSVER='Z22D')
SYMDEF(&SYSP1.='D2PRD1')
SYMDEF(&SYSP2.='D2PRD2')
SYMDEF(&SYSP3.='D2PRD3')
SYMDEF(&SYSR2.='D2RES2')
SYMDEF(&SYSS1.='D2SYS1')
SYMDEF(&SYSC1.='D2CFG1')
SYMDEF(&SYSNUM='&SYSNAME(4:1)')
SYMDEF(&TMPSIZE='500')
SYMDEF(&VTAMAPPL='VTAMPS')
SYMDEF(&VTAMID='&SYSNAME(4:1)')
SYMDEF(&TRLNAM='OSATRL&VTAMID.')
SYSPARM(PS) /* CONCATENATES IEASYSPS TO WHATEVER IS */
/* SPECIFIED ON SYSPARM IN LOADXX MEMBER */
SYSDEF VMUSERID(S0W1)
SYSNAME(S0W1)
SYSCLONE(1A)
SYMDEF(&VTAMSA='6')
SYSDEF VMUSERID(S0W2)
SYSNAME(S0W2)
SYSCLONE(1B)
SYMDEF(&VTAMSA='7') 
2017 Sysplex Extensions also provide two members for base sysplex mode:
•One member for running under z/VM (called IEASYMBS)
•One member for running the sysplex across two PCs (called IEASYMST)
The two base sysplex members are nearly identical to the Parallel Sysplex version, except that they concatenate another IEASYSxx member and the IEASYMST member filters on the Linux user ID rather than on the VM user name.
Sample JCL to allocate system-specific data sets
Although the design point of a sysplex is that as much as possible it should be shared, there are some data sets that must be unique to each system. The DEFPAGE member in the SYSPLEX.PARALLEL.CNTL data set allocates the system-specific data sets that are required by system S0W2. The JCL that is contained in DEFPAGE is shown in Example A-9.
Example A-9 Job DEFPAGE JCL
//DEFPAGE JOB CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID.
//S1 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//DD1 DD VOL=SER=D2PAGX,UNIT=3390,DISP=SHR
//DD2 DD VOL=SER=D2PAGY,UNIT=3390,DISP=SHR
//DD3 DD VOL=SER=D2PAGZ,UNIT=3390,DISP=SHR
//SYSIN DD *
DEFINE PGSPC(NAME(SYS1.S0W2.COMMON.PAGE) -
FILE(DD1) CYLINDERS(100) VOLUME(D2PAGX))
DEFINE PGSPC(NAME(SYS1.S0W2.PLPA.PAGE) -
FILE(DD1) CYLINDERS(150) VOLUME(D2PAGX))
DEFINE PGSPC(NAME(SYS1.S0W2.LOCALA.PAGE) -
FILE(DD1) CYLINDERS(9745) VOLUME(D2PAGX))
DEFINE PGSPC(NAME(SYS1.S0W2.LOCALB.PAGE) -
FILE(DD2) CYLINDERS(9995) VOLUME(D2PAGY))
DEFINE PGSPC(NAME(SYS1.S0W2.LOCALC.PAGE) -
FILE(DD3) CYLINDERS(9995) VOLUME(D2PAGZ))
/*
//S3 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//DD1 DD VOL=SER=D2SYS2,UNIT=3390,DISP=SHR
//SYSIN DD *
DEFINE CLUSTER(NAME(SYS1.S0W2.MAN1) REUSE NIXD SPND SPEED SHR(2) -
VOLUME(D2SYS2) CYLINDERS(40) RECSZ(4086,32767) CNVSZ(4096))
DEFINE CLUSTER(NAME(SYS1.S0W2.MAN2) REUSE NIXD SPND SPEED SHR(2) -
VOLUME(D2SYS2) CYLINDERS(10) RECSZ(4086,32767) CNVSZ(4096))
DEFINE CL(NAME(SYS1.S0W2.STGINDEX) VOLUME(D2SYS2) CYLINDERS(4) -
KEYS(12 8) BUFSPC(20480) RECSZ(2041 2041) FILE(DD1) REUSE) -
DATA (CNVSZ(2048)) INDEX (CNVSZ(4096))
/*
//S3 EXEC PGM=IFCDIP00
//SERERDS DD DSN=SYS1.S0W2.LOGREC,UNIT=3390,VOL=SER=D2SYS2,
// DISP=(NEW,CATLG),SPACE=(TRK,(90),,CONTIG)
//SYSPRINT DD SYSOUT=*
/* 
Note the use of the system name as the second qualifier in all of the data set names. By using this convention, you can have a single Parmlib member that is shared by all systems in the sysplex. For example, the following IEASYSxx statements define unique page data sets for each system:
PAGE=(SYS1.&SYSNAME..PLPA.PAGE,
SYS1.&SYSNAME..COMMON.PAGE,
SYS1.&SYSNAME..LOCALA.PAGE,
SYS1.&SYSNAME..LOCALB.PAGE,L),
The &SYSNAME is replaced by the system name when this member is read at IPL time. As a result, on system S0W1, these statements define page data sets that are called SYS1.S0W1,PLPA.PAGE, SYS1,S0W1.COMMON.PAGE, and so on. On system S0W2, the same statements define data sets SYS1.S0W2.PLPA.PAGE, SYS1.S0W2.COMMON.PAGE, and so on.
This configuration reduces the number of unique definitions that must be maintained, promotes good naming conventions, simplifies system operation, and reduces the time and effort that is required to add a system to the sysplex.
Job to create UNIX System Services data sets for second system
Certain UNIX System Services data sets can be shared by all systems in the sysplex. However, a subset of data sets must exist for each system. This job creates a copy of those data sets for the S0W2 system and places them on the D2SYS2 volume, as shown in Example A-10.
Example A-10 Cloning system-specific zFS data sets
//OMVSCLON JOB CLASS=A,MSGCLASS=X,REGION=0K,NOTIFY=&SYSUID.
//*****************************************************************
//*
//*
//* CREATEYSTEM-SPECIFIC ZFS DATASETS
//*
//*
//*****************************************************************
//********************************************************
//*
//* ALLOCATE A SYSTEM ROOT FOR THE S0W2 SYSTEM
//*
//********************************************************
//DEFINE EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//AMSDUMP DD SYSOUT=*
//SYSIN DD *
DEFINE CLUSTER (NAME(ZFS.S0W2.SYSTEM) -
LINEAR CYL(2 1) SHAREOPTIONS(3,3) -
VOLUMES(D2SYS2))
/*
//********************************************************
//*
//* NOW INITIALIZE THE NEW SYSTEM ROOT
//*
//********************************************************
//CREATE EXEC PGM=IOEFSUTL,REGION=0M,
// PARM=('format -aggregate ZFS.S0W2.SYSTEM')
//SYSPRINT DD SYSOUT=*
//STDOUT DD SYSOUT=*
//STDERR DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//CEEDUMP DD SYSOUT=*
//********************************************************
//*
//* NOW RUN BPXISYS2 AGAINST NEW SYSTEM ROOT
//*
//********************************************************
//IKJEFT1A EXEC PGM=IKJEFT1A,PARM='BPXISYS2 ZFS'
//SYSEXEC DD DSN=SYS1.SAMPLIB,DISP=SHR
//SYSTSPRT DD SYSOUT=*
//FSSYSTS DD DSNAME=ZFS.S0W2.SYSTEM,DISP=SHR
//SYSTSIN DD DUMMY
//********************************************************
//*
//* NOW USE DSS TO COPY THE SYSTEM-SPECIFIC ZFS FILES
//*
//********************************************************
//CLONE EXEC PGM=ADRDSSU,REGION=0M PARM='TYPRUN=NORUN'
//SYSPRINT DD SYSOUT=*
//FROMDASD DD UNIT=3390,DISP=SHR,VOL=SER=D2USS2
//TODASD DD UNIT=3390,DISP=SHR,VOL=SER=D2SYS2
//SYSIN DD *
COPY DATASET(INCLUDE( -
ZFS.S0W1.ETC, -
ZFS.S0W1.USR.MAIL, -
ZFS.S0W1.VAR, -
ZFS.S0W1.VARWBEM, -
ZFS.S0W1.WEB, -
ZFS.S0W1.WEB.CONFIG.ZFS)) -
LOGINDDNAME(FROMDASD) OUTDD(TODASD) -
TOLERATE(ENQF) -
RENAMEU( -
(ZFS.S0W1.ETC,ZFS.S0W2.ETC), -
(ZFS.S0W1.USR.MAIL,ZFS.S0W2.USR.MAIL), -
(ZFS.S0W1.VAR,ZFS.S0W2.VAR), -
(ZFS.S0W1.VARWBEM,ZFS.S0W2.VARWBEM), -
(ZFS.S0W1.WEB,ZFS.S0W2.WEB), -
(ZFS.S0W1.WEB.CONFIG.ZFS, -
ZFS.S0W2.WEB.CONFIG.ZFS)) -
SHARE ALLEXCP ALLDATA(*) CANCELERROR CATALOG
/* 
zPDT Disk versioning sample script
The sample Linux script that is shown in Example A-11 demonstrates how you enable disk versioning for your z/VM and z/OS disks. This example is only an example. You must customize it to include all of your z/OS and z/VM disks (or, at least, all those that you want to restore to a known restart point). Do not forget that you must run the chmod 755 command to grant yourself authority to run the script.
Example A-11 Script to enable zPDT disk versioning
#!/bin/bash
# Script to ENable disk versioning for ADCD volumes
alcckd D2C521 -ve
alcckd D2CFG1 -ve
alcckd D2DBB1 -ve
alcckd D2DBB2 -ve
alcckd D2DIS1 -ve
alcckd D2DIS2 -ve
alcckd D2PAGA -ve
alcckd D2PAGB -ve
alcckd D2PAGC -ve
alcckd D2PRD1 -ve
alcckd D2PRD2 -ve
alcckd D2PRD3 -ve
alcckd D2RES1 -ve
alcckd D2RES2 -ve
alcckd D2SYS1 -ve
alcckd D2USS1 -ve
alcckd D2USS2 -ve
alcckd CF0001 -ve
alcckd CICS01 -ve
alcckd DB2001 -ve
alcckd D2PAGX -ve
alcckd D2PAGY -ve
alcckd D2PAGZ -ve
alcckd D2SYS2 -ve
alcckd WORK01 -ve
alcckd M01P01 -ve
alcckd M01RES -ve
alcckd M01S01 -ve
alcckd M01W01 -ve
alcckd VMCOM1 -ve
alcckd 640RL1 -ve
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.