Greg, The IODF has two parts, the "Hardware" and the "Software". The hardware part of the IODF (IOCDS) is what is known to the CPC, what LPAR, if any, has access, etc. The software part of the IODF is what is defined and IPL at the LPAR or system level. This is where each I/O device is defined, device type, ESOTERICS, etc. You can build the new IODF and active the IOCP into the CPC and then actuall IPL using the old IODF without any problems as long as your devices are the same. The IOCP will tell the CPC what channels, control units and the devices (addresses) will be attached tot he CPC, where as the software part of the IODF will take care of the defining what type each device address is as well as take care of your esoterics. The option thing you must make sure is that the two IODFs have a different name.
Example, You build your new IODF for the new location: SYSH.IODF00 that defines the CPC, channels, switches, control units etc. You IPL with the old IODF from the target system SYSS.IODF00 which then defines your I/O device types, esoterics, etc. When you display your IOS,CONFIG you should see that you have a hardware of SYSH.IODF00 and an active IODF of SYSS.IODF00. You can then look at what is needed to merge the two IODFs together. Thanks, Craig Pace z/OS Systems Programmer Fruit of the Loom, Inc.® Office: (270) 781-6400 ext. 4397 Cell: (270) 991-7452 Fax: (270) 438-4430 E-mail: cp...@fruit.com One Fruit of the Loom Drive PO Box 90015 Bowling Green, KY 42102-9015 Greg Smith <r...@epaibm.rtpnc.epa.gov> Sent by: IBM Mainframe Discussion List <IBM-MAIN@bama.ua.edu> 08/19/2010 06:00 PM Please respond to IBM Mainframe Discussion List <IBM-MAIN@bama.ua.edu> To IBM-MAIN@bama.ua.edu cc Subject Esoterics We are in the process of migrating a smallish system from one location to another. The plan is to dump all the dasd to tape at the original location, ship the tapes to the new location, and restore the tapes to new dasd. The hardware at the new location is similar but not identical to the hardware at the old location. Therefore we are creating a new IODF and IOCP deck on a different system to use at the new location. I am thinking we are going to have a problem with the esoterics. The system does not use tokens for their esoterics. So I am thinking that we have to define the esoterics in the same order they were defined at the original location. But how do we find that out? The HCD report that was sent to us lists the esoterics in alphabetical order. To refresh my memory, I think this is how esoterics work. If tokens are not used then the order that the esoterics are defined is important. The catalog for a dataset cataloged with an esoteric unit type gets the sequence number of the particular esoteric in the list of esoterics. If tokens are used, then the token for an esoteric is a unique number that is stuffed into the catalog instead. The advantage using tokens is that you can delete an esoteric and not have the values of other esoterics possibly change? Is that right? What happens if you delete an esoteric with a token and that token is set in a catalog entry somewhere? Also, isn't there some kind of conversion job to convert catalog entries from sequence numbers to token numbers? Or was it a report job that listed catalog entries that were cataloged using esoterics? It's been so long ago that I last dealt with this stuff. But I don't want the system at the new location trying to mount tapes on dasd devices ... and vice versa!! Finally, a last question. If we substantially use the same device numbers, can we bring up the new system using the old system's IODF? The new system's IOCDS will be built with the new IOCP deck, so there may be mismatches on some chpids and control unit types between the IODF and the IOCDS. How much does MVS care what is correct in the IODF? After the initial IPL we can of course correct the IODF and get everything into sync. Thanks, Greg ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ********************************************************************** This communication contains information which is confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), please note that any distribution, copying or use of this communication or the information in it is strictly prohibited. If you have received this communication in error, please notify the sender immediately and then destroy any copies of it. ********************************************************************** ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
