Automated Testing

Automated Testing

Automated Testing

Build an automated testing process to enable continuous integration of your hybrid cloud applications including z/OS

 View Only
Expand all | Collapse all

Create new IPLPARM Volume

  • 1.  Create new IPLPARM Volume

    Posted Wed December 20, 2017 08:39 AM

    I'm trying to totally separate my customizations from the ADCD distribution itself.

    I've added libraries to the PARMLIB concat list and PROCLIB concat list on new volumes, Moved away from the USER data sets since they (PARMLIB, PROCLIB) are initially stored on xxCFG1 volumes and would have to shuffle things around on an upgrade.  I've created a new IPLPARM.LOAD member.  Everything works as expected, I can IPL into my customizations, or into any of the ADCD predefined configurations.

    Since I want to update to the latest ADCD release, I'm trying to get my configuration in a state where I can just copy over the distribution volumes and not have to redo any re-customization.  And use that method for future releases.

    The last part is create a new volume to hold the IPLPARM.LOAD member and point to that in the runzpdt script.  This is where I'm having issues.  I created a SYS0.IPLPARM(LOAD01) member.  I created/initialized/copied the IODF datasets per the examples in the sample library using IBM documentation on-line.  I have my LOAD01 member pointing to that IODF dataset.  The out of the box config line is "99    SYS1", my version has "99   LISYS1", I also tried "99   SYS0". My IPL command is "ipl a80 parm 0AD301" where 0AD3 is the address of my new volume.

    When I IPL I get this message a couple seconds later "AWSEMI307I Warning! Disabled Wait CPU 0 = 00020000 00000000 00000000 00200088".  If I broke down the error correctly, it points to a configuration error.  I'm guessing I missed something when preparing the new volume.

    Any info would be appreciated.

    Thanks.

    jmal


  • 2.  Re: Create new IPLPARM Volume

    Posted Sat December 23, 2017 05:11 AM

    Hi

     

    I would look at the Stand-Alone IPL volume SARES1 and draw inspiration from that.

    Secondly I would single out RACF and DB2 as systems that probably would have to be unloaded and reloaded separately, depending on your requirements and version upgrades.

    Thirdly remember that your PROCLIBS have to be available at IPL time and for example cannot be PDSE's. There are many ways to burn your fingers here.

     

    Br Michael Erichsen

    Xact Consulting

    MichaelErichsen,Xact


  • 3.  Re: Create new IPLPARM Volume

    Posted Tue January 02, 2018 06:34 AM

    I'd like to add some more information to help you better on your plans.

    Please, learn more about IPL process at https://www.ibm.com/support/knowledgecenter/zosbasics/com.ibm.zos.zsysprog/zsysprogc_systemIPL.htm.

    Keep in mind that LOAD PARM field points to IODF volume and SYSn.IPLPARM will be searched also in this volume, but this is not the IPLPARM volume.

    AdilsonColombo