We ensure we code either -- or ++ as the last 2 values in the IODF name to allow the finding of the IODF that has the matching token that is in HSA.
Jerry Whitteridge Manager Mainframe Systems & Storage Albertsons - Safeway Inc. 623 869 5523 Corporate Tieline - 85523 If you feel in control you just aren't going fast enough. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jesse 1 Robinson Sent: Thursday, July 27, 2017 2:20 PM To: [email protected] Subject: EXTERNAL: Re: Questions about IPL with package IODF A couple of assumptions. OP has only one CEC with multiple LPARs, right? IODF 'package' just means the (linear) VSAM cluster IODFxx, right? First off, I have to say that this is an unusual way to manage IODFs. We have three CECs in the enterprise, but we use (multiple copies of) a *single* IODF for all LPARs on all CECs. OTOH we own all the LPARs, so we have no motivation to hide any of them from any of the others. The immediate cause of the problem seems to be this: IEA246I LOAD ID A1 SELECTED IEA246I NUCLST ID 01 SELECTED IEA519I IODF DSN = MPLX.IODF00 <=============================================== does not match HSA IEA520I CONFIGURATION ID = EALB . IODF DEVICE NUMBER = 8318 IEA528I IPL IODF NAME DOES NOT MATCH IODF NAME IN HARDWARE TOKEN MPLX.IODF01 ------> Last iodf active in dynamic activation In other words, at IPL time, IOS is using a different IODF than the one dynamically activated. The (dynamically activated) IODF in HSA is IODF01, but the system is IPLing with IODF00. Hence the token mismatch. For IPL to work, several steps must be taken for a new IODF. -- Write the IODF-derived IOCDS to one of the slots in the CEC. Our CECs have (forever had) 4 slots labelled A0 - A3. -- Set the 'next active' IOCDS to match the slot containing the new IOCDS. We always use the same slot for IPL/POR, so that slot gets overwritten with each new IOCDS. -- Use the appropriate designation in LOADxx (LOADA1 in this case) to find the IODF 'package' that matches HSA. If you hardcode an IODF value, that's the one he will use whether it matches HSA or not. Although the OP's methodology is unusual, I don't see why it would not work as long as all these steps are taken. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Matthew Stitt Sent: Thursday, July 27, 2017 12:20 PM To: [email protected] Subject: (External):Re: Questions about IPL with package IODF I copy the production IODF(s) to the outside system(s). There is a hardware token in the HSA that must match the token in the IODF. The OP received a message stating the token does not match. This is a result of the installation creating a separate IODF for usage with certain LPARs. You should have one IODF that contains each processor in your installation. Through the Operating System configuration you can ensure devices are online/offline to certain configurations. Also you can configure CHPIDs to be accessible to certain LPARs only. In this manner you can separated Control Units and Devices by having those resources accessible only through the isolated CHPIDs. The copying of the production IODF can be accomplished through several methods. Matthew ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ________________________________ Warning: All e-mail sent to this address will be received by the corporate e-mail system, and is subject to archival and review by someone other than the recipient. This e-mail may contain proprietary information and is intended only for the use of the intended recipient(s). If the reader of this message is not the intended recipient(s), you are notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately. ________________________________ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
