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

158 EFS Systems on a Linux Base: Additional Topics

#FLEX-ES resource definition extract for instance zsna on server x232.

cu devad(0x0e40,01) path(2) resource(X232.XCA2)

X232.XCA2:cu xcasna

interface local(1) options 'adapternumber=1'

device(00) xcasna eth2

end X232.XCA2

11.7 MVS device definitions

We used the HCD dialogs available under TSO ISPF to define the LAN devices to MVS. We

did not need to create any channel paths or control units; we only needed to define the

devices.

We first needed to know what IODF was used to IPL the system, since it is the proper starting

point when adding new devices. To determine which data set to use, we first used the MVS

operator command D IPLINFO:

00-ZOS1 d iplinfo

IEE254I 13.42.05 IPLINFO DISPLAY FRAME LAST F E SYS=ZOS1

SYSTEM IPLED AT 12.15.39 ON 06/28/2003

RELEASE z/OS 01.04.00 LICENSE =z/OS

USED LOAD01 IN SYS1.IPLPARM ON 0302

ARCHLVL =2 MTLSHARE =N

IEASYM LIST =01

IEASYS LIST =00 (OP)

IODF DEVICE 0302

IPL DEVICE 0300 VOLUME ZP4RS1

From this display, we learned that member LOAD01 of data set SYS1.IPLPARM on device

302 was used to IPL the system. We obtained the volume serial number of device 302 with

the MVS d u command:

00-ZOS1 d u,,,302,1

IEE457I 13.47.29 UNIT STATUS FRAME LAST F E SYS=ZOS1

UNIT TYPE STATUS VOLSER VOLSTATE

0302 3390 A ZP4SYS PRIV/RSDNT

We then used the ISPF browse command to view the LOAD01 member of SYS1.IPLPARM on

volume ZP4SYS, as shown in Figure 11-4 on page 159.

Chapter 11. SNA over Ethernet 159

Figure 11-4 Browse entry panel

The SYS1.IPLPARM(LOAD01) member displayed as follows:

000001 *---+----1----+----2----+----3----+----4----+----5----+----6----+----7-

000002 IODF 07 SYS1 ZOS 10

000003 SYSCAT ZP4SYS113CCATALOG.ZP4.MASTER

000004 SYSPARM 00

000005 IEASYM 01

000006 PARMLIB ZPLEX.PARMLIB ZP4RS1

000007 PARMLIB ADCD.ZOSV1R4.PARMLIB ZP4RS1

000008 PARMLIB SYS1.PARMLIB ZP4RS1

000009 NUCLEUS 1

000010 SYSPLEX ZPLEX

**************************************Bottom of Data********************************

The first three parameters of line 2 (line 1 is a comment) tell z/OS initialization which IODF to

use. The file must be cataloged in the master catalog. The third column is the first-level

qualifier of the data set. The first and second columns are combined to form the second-level

qualifier. The system was IPLed using SYS1.IODF07.

Armed with this information, we started the HCD dialog and selected option number 1,

specifying SYS1.IODF07 as the starting point, as shown in Figure 11-5 on page 160.

ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss

View Entry Panel

Command ===>

ISPF Library:

Project ...

Group .............

Type ....

Member ... (Blank or pattern for member selection list)

Other Partitioned,Sequential or VSAM Data Set:

Data Set Name ... SYS1.IPLPARM(LOAD01)

Volume Serial ... ZP4SYS (If not cataloged)

Workstation File:

File Name .....

Options

Initial Macro .... Confirm Cancel/Move/Replace

Profile Name ..... Browse Mode

Format Name ..... View on Workstation

Data Set Password .. / Warn on First Data Change

Mixed Mode

160 EFS Systems on a Linux Base: Additional Topics

Figure 11-5 The initial HCD screen

Since we wanted to add a new device, we selected option 5 from the Define, Modify, or View

Configuration Data menu, as shown in Figure 11-6.

Figure 11-6 Define, Modify or View Configuration Data dialog

We were then presented with the list of devices defined for this system. We pressed F11 to

add a new device. New information cannot be added to an existing IODF, however. HCD must

copy the existing IODF to a ‘work’ IODF before any changes can be made. As soon as we

pressed F11 for the first time, we were prompted to allow HCD to make the copy, as shown in

Figure 11-7 on page 161.

OS/390 Release 9 HCD

Command ===>________________________________________________________________

Hardware Configuration

Select one of the following.

_1 1. Define,modify,or view configuration data

2. Activate or process configuration data

3. Print or compare configuration data

4. Create or view graphical configuration report

5. Migrate configuration data

6. Maintain I/O definition files

7. Query supported hardware and installed UIMs

8. Getting started with this dialog

9. What's new in this release

For options 1 to 5,specify the name of the IODF to be used.

I/O definition file ...'SYS1.IODF07'+

Esssssssssssss Define,Modify,or View Configuration Data ssssssssssssssN

e e

e Select type of objects to define,modify,or view data. e

e e

e 5_ 1. Operating system configurations e

e consoles e

e system-defined generics e

e EDTs e

e esoterics e

e user-modified generics e

e 2. Switches e

e ports e

e switch configurations e

e port matrix e

e 3. Processors e

e partitions e

e channel paths e

e 4. Control units e

e 5. I/O devices e

e e

e F1=Help F2=Split F3=Exit F9=Swap F12=Cancel e

DsssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssM