Phase 7: Expanding the configuration
We now have a usable z/OS system, although the system is simple and restrictive.
More resources must be added to the driver system so that it can be used as an installation platform for the ServerPac.
This chapter includes the following topics:
10.1 Goals
Phase 7 features the following goals:
•Make more disk volumes available on DS8000 DASD subsystem
•Create and load new IOCDS for z13 CPU
•Make more local 3270 devices available on z13 and z/OS
•Make TCP/IP connectivity available via TN3270 and TCP/IP
•Add extra SPOOL and Paging space
Phase 7 is required to achieve Milestone 3: Use COD to Expand Configuration to New IOCDS ready for ServerPacs. Where this phase is positioned in the overall process is shown in Figure 10-1.
Figure 10-1 Phase 7 Milestone 3
10.2 Tasks overview
We must add some Count Key Data (CKD) volumes on a second Logical Control Unit (LCU) of the DS8800. This addition provides volumes for transferring the data from the ServerPac DVDs to z/OS. We also add various volumes of other 3390 capacity models in preparation of the final disk layout.
As we need better connectivity to allow more Time Sharing Option (TSO) users and for the ServerPac upload, we define more 3270 devices on the OSA-Express Integrated Console Controller (OSC) channel and also define an Open Systems Adapter (OSA) channel in queued direct I/O (QDIO) mode for TCP/IP.
In addition, the driver system requires more disk space for SPOOL and Paging to have sufficient capacity for the ServerPac process.
We complete these tasks through the following methods:
•Using the DS8000 GUI to define new LCU and volumes
•Creating IOCDs by using the ICPIOCP program from z/OS
•Defining more 3270 sessions in the TN3270 server by using the OSC channel advanced facilities
•Connecting another network cable
•Setting up TCP/IP, VTAM, and IOS parameters
•Applying changed parameters and starting communications procedures
•Running disk initialization, SPOOL allocation, and page data set definition jobs
•Starting the extra spool disk and adding the extra page data set
10.2.1 Defining DS8800 volumes
As with the first volume definition step, we use the DS8000 GUI; however, the command-line interface (CLI) also can be used. All of the required steps for this process are not described here. For more information, see 6.7, “Creating CKD LCUs with volumes” on page 98.
In addition to the 128 model 9 volumes and 32 model 27 volumes that were originally defined, we define a second LCU (numbered 01) with 16 model 54 volumes, and 32 each of model 3 and model 1 volumes. This new LCU also contains 64 aliases.
It is suggested to have a selection of volume sizes to physically separate data sets that do not belong on the same volume without wasting space and to allow large data sets to not have to span volumes.
The capacity of the volume models is listed in Table 10-1.
Table 10-1 3390 Model capacity
|
3390 Model
|
Cylinders
|
|
1
|
1113
|
|
3
|
3339
|
|
9
|
10017
|
|
27
|
30051/32760 *1
|
|
54
|
60102/65520 *1
|
|
Note: Some users prefer to specify 32760 cylinders for model 27 and 65520 for model 54. Other users prefer multiples of 1113 cylinders, which are equivalent to a DS8000 CKD extent.
|
10.2.2 New IOCDS
We increase the number of 3270 devices in the 00A0 range and add Parallel Access Volumes (PAV) on the disk LCU. We then add a second disk LCU (01) with 192 base and 64 PAVs that are connected to the same channels as LCU 00. This configuration corresponds with the configuration that we used for the DS8800.
An extra channel with a control unit and devices is defined to map a driver system QDIO OSA device range to a real OSA in the z13 channel subsystem. Although our z13 has many fiber OSAs, we use another copper (1000BaseT) adapter to be compatible with the network in the lab area.
Because we now have an operating system, the IOCDS can be built on z/OS and written from there, which eliminates the need to build it again by using the stand-alone IOCP.
The job that is used to create the IOCDS is included in Example 10-1.
Example 10-1 Job that is used to create IOCDS
//DRVUSERC JOB (0101),B,MSGCLASS=X,CLASS=A,NOTIFY=&SYSUID 00010000
//******** * 00020000
//IOCDS EXEC PGM=ICPIOCP,REGION=00M, 00030001
// PARM='WRTCDS=A1,LINECOUNT=55' ,CHECKCPC=NO' 00040001
//SYSPRINT DD SYSOUT=* 00050000
* 00060000
ID MSG1='COD IOCP' 00070000
* 00080000
* LPAR DEFINITION 00090000
* 00100000
RESOURCE PARTITION=((CSS(0),(COD,1),(COSP,2))) 00110001
* 00120000
* CHANNEL PATH DEFINITION 00130000
* 00140000
* FICON PATH SECTION FOR DS8000 DISKS 00150000
CHPID PATH=(CSS(0),01),PCHID=1E0, X00160000
TYPE=FC,SHARED 00170000
CHPID PATH=(CSS(0),02),PCHID=1E1, X00180000
TYPE=FC,SHARED 00190000
CHPID PATH=(CSS(0),03),PCHID=260, X00200000
TYPE=FC,SHARED 00210000
CHPID PATH=(CSS(0),04),PCHID=261, X00220000
TYPE=FC,SHARED 00230000
* OSA ICC PATH SECTION FOR CONSOLES 00240000
CHPID PATH=(CSS(0),05),PCHID=1BC, X00250000
TYPE=OSC,SHARED 00260000
* OSA QDIO PATH SECTION FOR TCP/IP 00270000
CHPID PATH=(CSS(0),06),PCHID=240, X00280000
TYPE=OSD,SHARED 00290000
* 00300000
* CONTROL UNIT DEFINITION 00310000
* 00320000
* OSA ICC CNTLUNIT SECTION 00330000
CNTLUNIT CUNUMBR=0500,PATH=((CSS(0),05)), X00340000
UNIT=OSC 00350001
* OSA QDIO CNTLUNIT SECTION 00351001
CNTLUNIT CUNUMBR=0600,PATH=((CSS(0),06)), X00360000
UNIT=OSA 00370001
* DS8000 CNTLUNIT SECTION 00380000
CNTLUNIT CUNUMBR=1200,PATH=((CSS(0),01,02,03,04)),CUADD=0, X00390000
UNIT=2107,UNITADD=((00,256)) 00400000
CNTLUNIT CUNUMBR=2000,PATH=((CSS(0),01,02,03,04)),CUADD=1, X00410000
UNIT=2107,UNITADD=((00,256)) 00420000
* 00430000
* I/O DEVICE DEFINITION 00440000
* 00450000
* 3270-X TERMINALS 00460000
IODEVICE ADDRESS=(00A0,32),CUNUMBR=(0500),MODEL=X,UNIT=3270 00470000
* TCP/IP OSA QDIO 00480000
IODEVICE ADDRESS=(0040,16),CUNUMBR=(0600),UNIT=OSA 00490000
IODEVICE ADDRESS=(06FE,001),CUNUMBR=(0600),UNIT=OSAD 00500000
* DASD IODEVICES 00501001
IODEVICE ADDRESS=(1200,192),CUNUMBR=(1200),UNIT=3390B 00510000
IODEVICE ADDRESS=(12C0,064),CUNUMBR=(1200),UNIT=3390A 00520000
IODEVICE ADDRESS=(2000,192),CUNUMBR=(2000),UNIT=3390B 00530000
IODEVICE ADDRESS=(20C0,064),CUNUMBR=(2000),UNIT=3390A 00540000
//
The input of the job that is shown in Example 10-1 on page 164 can be referred to as the IOCS or IOCP input deck.
Ensure that the IOCDS selected (A1 in the sample job) is available for use and not write-protected. When the job requests, reply to allow it to write the new IOCDS.
Now the system must be shut down and a power on-reset (POR) done by using the selected IOCDS. This process is similar to the process that is described in 4.5.2, “POR by using IOCDS D0” on page 35. However, we are performing a POR from IOCDS A1 in this instance.
10.2.3 Adding 3270 sessions
Because the OSC channel is now aware of many more 3270 devices, sessions for more terminals can be added. We added only one until now for TSO on the driver system.
After obtaining an available IPV4 address in the lab LAN, we edit the sample TCP/IP profile in TCPIP.SEZAINST(PROFILE). We uncomment and modify the INTERFACE statement for OSAQDIO24, uncomment the start statement for it, and define routing options for it.
In addition, a Transport Resource LIST Element (TRLE) member is created in SYS1.VTAMLST called TRL0040. The PORTNAME in this member must match the PORTNAME in the profile. The devices that are specified here must have Missing Interrupt Handler (MIH) time outs disabled in IECIOS00 member of SYS1.PARMLIB.
To automate activation, the new TRL0040 member is added to the SYS1.VTAMLST configuration member (ATCCON00), as is the local console member (D0A00BF). The automatic IPL time commands in SYS1.PARMLIB member COMMND00 are also changed to include a start for VTAM, TCP/IP, and TN3270.
TRLE
|
TRL0040 VBUILD TYPE=TRL
TRL004A TRLE LNCTL=MPC, X
READ=(0040), X
WRITE=(0041), X
DATAPATH=(0042), X
PORTNAME=OSAQDIO2, X
MPCLEVEL=QDIO
|
Figure 10-2 VTAM TRLE
MIH
|
MIH DEVICE=(0040-0042),TIME=00:00
|
Figure 10-3 IOS parameters
ATCCON00
|
TSOAPPL,TCPAPPL,TRL0040,D0A00BF
/* LIB: SYS1.VTAMLST(ATCCON00) */
|
Figure 10-4 VTAM configuration
TCP/IP PROFILE
|
....................SNIP........................
INTERFACE OSAQDIO24 ; IPv4 OSA-Express QDIO ethernet
DEFINE IPAQENET
PORTNAME OSAQDIO2
INBPERF DYNAMIC
VMAC
; SOURCEVIPAINT VLINK1
IPADDR 9.56.195.20/24
..................SNIP..........................
ROUTE 9.56.195.0 255.255.255.0 = OSAQDIO24 MTU 2000
ROUTE DEFAULT 9.56.195.1 OSAQDIO24 MTU DEFAULTSIZE
..................SNIP..........................
START OSAQDIO24
|
Figure 10-5 TCP/IP profile
Activating changes
The TRLE is activated dynamically by varying the OSA devices online (by using the V 0040-0042,ONLINE command) and then issuing the V NET,ACT,ID=TRL0040 command.
Input/output Supervisor (IOS) parameters are updated by issuing the following command:
SETIOS MIH,DEV=(0040,0041,0042),TIME=00:00
TCP/IP and TN3270 are started by using the S TCPIP and S TN3270 commands in sequence.
10.2.4 Ready to communicate
Our configuration is shown in Figure 10-6.
Figure 10-6 Expanded configuration
10.2.5 Adding system volumes
As shipped, the driver system features limited spool and paging space. We initialize two more volumes (D9ESY3 and D9EPAG) to alleviate this problem.
Two disk units are initialized in offline status by first issuing the V 1203-1204 OFFLINE command and then submitting the JCL, as shown in Figure 10-7.
|
//DRVUSERI JOB (0000),INIT,CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID
//INITDISK EXEC PGM=ICKDSF,PARM=NOREPLYU,REGION=100M
//SYSPRINT DD SYSOUT=*
INIT UNIT(1203) NOVALIDATE VERIFY(*NONE*) OWNER(DRIVER) VOLID(D9ESY3) -
VTOC(3,0,90) INDEX(0,1,44)
INIT UNIT(1204) NOVALIDATE VERIFY(*NONE*) OWNER(DRIVER) VOLID(D9EPAG) -
VTOC(3,0,90) INDEX(0,1,44)
//
|
Figure 10-7 Initialize volumes D9ESYS3 and D9EPAG
After the drives are back online (by issuing the V 1203-1204,ONLINE command), the disks are ready to be used.
On D9ESY3, we define a large spool data set SYS1.HASPACE by submitting the job that is shown in Figure 10-8 and adding it by using the $SSPL command.
|
//DRVUSERS JOB (0000),SPOOL,CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID
//ALLOCSPL EXEC PGM=IEFBR14
//SYSUT1 DD DSN=SYS1.HASPPACE,DISP=(,KEEP),UNIT=3390,VOL=SER=D9ESY3,
// SPACE=(CYL,(3000),,CONTIG),DSNTYPE=LARGE,BLKSIZE=3992,RECFM=U,
// LRECL=3992,DSORG=PS
//
|
Figure 10-8 Creating another spool data set
On D9EPAG, we define a page data set PAGE.CPAC.LOCAL3 and use the PAGEADD command to activate it. The job that is shown in Figure 10-9 is used.
|
//DRVUSERP JOB (0000),PAGE,CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID
//DEFPGSPC EXEC PGM=IDCAMS,REGION=100M
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DISP=OLD,UNIT=3390,VOL=SER=D9EPAG
DEFINE PAGESPACE (FILE(SYSUT1) NAME(PAGE.CPAC.LOCAL3) CYLINDERS(3000) -
VOLUME(D9EPAG)
//
|
Figure 10-9 Creating pagespace
To make these new data sets available, we run the following commands:
PA PAGE=PAGE.CPAC.LOCAL3
$SSPL (D9ESY3)
We also update SYS1.PARMLIB member IEASYS00 to permanently add the extra page data set, taking care to maintain the syntax of the commas and parentheses, as shown in Figure 10-10.
|
PAGE=(PAGE.CPAC.COMMON,
PAGE.CPAC.LOCAL1,
PAGE.CPAC.LOCAL2,
PAGE.CPAC.LOCAL3,L),
|
Figure 10-10 Expanded page configuration in IEASYS00
10.3 Ready to fully use driver system
A new Personal Communications session is set up to connect through TN3270. The standard Telnet port (23 Port) number to connect to is used.
We are now ready to use the driver system as the vehicle for installing the ServerPac.
|
Note: Although TN3270 and console Personal Communications sessions work fine, the OSA ICC sometimes issues a write control character for local non-SNA sessions that causes a printer pop-up window to open.
To avoid this issue, add the following lines to the Personal Communications session profile:
(<sessionname>.WS)
[LT]
IgnoreWCCStartPrint=Y
|
We now move on to Phase 8.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.