Specifications

38 IBM System z Personal Development Tool: Volume 3 Additional Topics

(ignore progress messages such as NEXT TRACK TO WRITE)

(wait for FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0)

IPL z/OS

We started another 3270 session (for TSO):

$ x3270 -port 3270 localhost &

And then we IPLed the one-volume z/OS system that we just restored:

$ ipl 0a8f parm 0a8fsa (use the indicated IPL parameter)

3.9 IODF Changes with zPDT

For a larger System z, IODF and IOCDS creation are almost always done at the same time,

working with HCD. This typically starts as follows:

HCD (usually started from an ISPF panel)

1. Define, modify, or view configuration data

3. Processors

4. Control Units

5. I/O Devices

The HCD functions verify that an allowable configuration is specified. That is, the processor

(type and model), CHPIDs, and I/O devices must all be mutually allowable. This is a useful

check for a larger System z, but it creates problems for zPDT.

A zPDT system does not use an IOCDS and does not understand many hardware CHPID

details. Furthermore, typical zPDT configurations are simply not compatible with the normal

HCD verification and processing we would use with a larger System z. At the time of writing,

I/O device configuration for a z/OS system on zPDT consists of a software only IODF

generation, followed by the creation of a matching devmap. Many z/OS users are not

immediately familiar with a software only IODF and we provide an overview of the topic here.

Once started, it is considerably simpler than a “normal” IODF.

Assume we want to add 15 OSA devices starting at address 410 and an OSAD device at

address 41F. Using the IODF99 that is provided with the current z/OS AD-CD system

, we

would proceed as follows:

HCD (started via ISPF menu item M.4)

1. Define, modify, or view configuration data

I/O DEFINITION FILE 'SYS1.IODF99'

1. Operating System Characteristics

/ OS390 (select configuration named 'OS390')

7. Work with attached devices

(This should produce a list of current devices)

F11 - Add

At this point you should have a panel that wants you to enter a new work IODF name. We

entered the name SYS1.IODF77.WORK and volser ZCSYS1 in this panel. The data set name

should follow this pattern (although the 77 portion of the name is arbitrary) and the volser

should be the volume that is specified in the IPL parameter (ZCSYS1 in the z/OS 1.12 AD

system).

This is followed by a panel to add devices to the new work IODF. We entered the following:

This example is based on the z/OS 1.12 AD-CD system, but later releases should be similar.