IODFs and addresses

Three IODFs are included with the release 10 AD system. These are SYS1.IODF00, SYS1.IODF01, and SYS1.IODF99. We refer to these as the 00, 01, and 99 IODFs. Your IPL parameter, via a value in the LOADxx member, selects which IODF is used for a given IPL. No “work” IODFs are included.6

As far as we could determine, the only differences between 00 and 01 were differences in esoteric device definitions that added the 3390s starting at address A80. Based on this, SYS1.IODF00 can be considered obsolete and you can ignore it.

2.6.1 SYS1.IODF01

All of the LOADxx members are set to use SYS1.IODF01. This IODF defines the following devices and addresses:

00C 2540R Card reader. Useful as am emulated device 00E 1403-N1 Line printer. Useful as an emulated device 00F 3203 Line printer. Not clear why this is included. 010 3277 Terminal. Relic of system used to create AD releases 063 3277 Terminal. Relic of system used to create AD releases

120-15F 3380 Disks

240-25F 3380 Disks

260-27F 3390 Disks

560-57F 3480 No COMPACT option is defined on any drive 580-59F 3420-8 “Round” tapes. For AWSTAPE emulated drives. 5A0-5AF 3422 “Round” tapes. For AWSTAPE or OMA emulation 700 3270 Terminal. AD systems use as NIP & OS/390 master 701-73F 3270-X Terminal. Normally for VTAM (TSO, CICS, etc) 900-91F 3270-X Terminal. Normally for VTAM (TSO, CICS, etc) A80-ABF 3390 Disks. Can be for system volumes, etc

E20-E27 CTC Typically for 3172s that appear as CTC devices E40-E47 CTC Typically for 3172s that appear as CTC devices

As far as we know, all the devices in this IODF are defined correctly. The most common change needed to is add the COMPACT feature to one (or more) 3480 definitions. The COMPACT feature is needed to process a compressed tape. For 3480 drives, this is known as an IDRC hardware feature and is enabled by selecting the COMPACT feature in the IODF definition. The COMPACT function is standard for 3490 drives.

You will probably use this IODF for your initial system operation. Many AD users never need to change this IODF and use it for all their system operations. See “Changing your I/O configuration” on page 18 for comments about matching your hardware to this IODF. However, you are not required to use the IODFs that are distributed with the AD system. If you have the necessary skills, you can create any IODF you require by using the HCD utility.

2.6.2 SYS1.IODF99

SYS1.IODF99 is also provided with the AD release. This is intended to be an expanded version of IODF01, with more devices that might be needed for an MP3000 machine. Unfortunately, IODF99 contains a number of errors. Moreover, there is no particular need to use it with an MP3000 unless you want device addresses that match particular

documentation you may have.7 None of the supplied LOADxx members point to IODF99. Member LOAD99, included in SYS1.IPLPARM but not documented in “Detailed IPL parameter controls” on page 29, is intended to point to IODF99 but points to IODF01 by mistake.

One way to use IODF99 is as follows:

򐂰 Correct LOAD99 to point to IODF99.

򐂰 IPL with parameter 0A8299T (using the correct address for the OS39M1 volume)

򐂰 The T parameter (seventh character in the IPL parameter field) causes the system to issue the SPECIFY SYSTEM PARAMETERS message. The reply should be:

REPLY 00,SYSP=CS

or any of the other two-character parameters that are possible suffixes for the IEASYSxx name, as listed in 2.4.1, “Detailed IPL parameter controls” on page 29.

This technique provides the same effect obtained from IPLPARM 0A82CS (in the sample here), but with a different starting point (LOAD99 instead of LOADCS). Another way to use IODF99 would be to change all the LOADxx members to refer to 99 instead of 01, or to create a whole new set of LOADxx members containing 99.

Again, we repeat that all the examples in this book were with a mixture of P/390 and MP3000 systems, all using IODF01. There is no requirement to use IODF99 with MP3000 systems. The IODF99 definitions are quite similar to the IODF01 definitions. IODF99 has the following:

00C 2540R Card reader. Useful as am emulated device. 00E -00F 1403-N1 Line printer. Useful as an emulated device.

010 3277 Terminal. Relic of system used to create AD releases. 063 3277 Terminal. Relic of system used to create AD releases.

120-15F 3380 Disks

1C0-1FF 3390 Disks. Not defined correctly (no OS defined in HCD). 240-25F 3380 Disks. No OS defined in HCD.

260-27F 3390 Disks. No OS defined in HCD.

300-3BF 3390 Disks.

550-55F 3420-8 “Round” tape. No OS defined.

560-56F 3480 No COMPACT option is defined on any drive.

570-57F 3480X Has COMPACT feature

580-58F 3490 Tape. No OS defined.

590 3490 Tape.

591-59F 3490E Tape. Invalid definition; no OS defined. 700 3270 Terminal. AD systems use as NIP & OS/390 master 701-73F 3270-X Terminal. Normally for VTAM (TSO, CICS, etc)

7 _{This is most common with the DaVinci package. Associated documentation assumes you are using addresses in the 300 range for your}

900-91F 3270-X Terminal. Normally for VTAM (TSO, CICS, etc) A80-ABF 3390 Disks. Can be for system volumes, etc

E20-E23 CTC Typically for 3172s that appear as CTC devices E40-E43 CTC Typically for 3172s that appear as CTC devices