Yup! -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Jesse 1 Robinson Sent: Friday, May 29, 2020 5:25 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IODF/IOCDS questions
[CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.] We have never defined any installation userids on any SE. The only users defined are the standard IBM supplied one. Are you saying, if we defined at least a few of our own, we could have multiple 'sysprogs' logged on simultaneously? . . 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 robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of R.S. Sent: Friday, May 29, 2020 5:10 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: IODF/IOCDS questions CAUTION EXTERNAL EMAIL W dniu 28.05.2020 o 16:04, Edgington, Jerry pisze: > We currently have 3 CECs with multiple different IODFs. > > Question #1) How can I do combine/move all the CECs into a single IODF? > Question #2) How can I update the CEC's IOCDS from a different CEC? What > steps are needed to run a batch job from one CEC to update another CEC? 1. Yes and this is recommended way. Note: you may keep completely unrelated CECs in single IODF. 2. There are many ways to update IOCDS. One of them is to update IOCDS in CEC #1 when working on LPAR under CEC #2. However for this scenario you need to set up your "CEC plex" or rather "SE plex" (SE=Support element). First step is to connect internal networks. Internal network is the LAN between HMC and SE. Usually it is three node network: SE, Alternate SE and HMC. Recommended way is to connect all the SEs and HMCs in one LAN (excluding optional remote HMC). You need to change SE and HMC adresses and change HMC name. Defaults are the same causing conflict. Next you have to add CPCs (objects) to HMCs - the best way is every HMC manage every CPC. BTW: It is also good idea to set up domain security now. Otherwise someone with illegal CPC (grin) or illegal HMC would be able to connect to your SE plex. Note: everything I described can be done remotely, however that require proper planning and order of changes. A mistake could cause a trip to datacenter to fix it. And be sure you have valid userids and passwords on each SE and HMC. -- Radoslaw Skorupka Lodz, Poland ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: ________________________________ The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ________________________________ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
