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
  • 1.  IPL Issue

    Posted Thu December 29, 2011 01:08 PM
    Hi All,

    We are currently using "0A82DC" parameter for IPL. We want to start Java and WAS on our system using different IPL options like WS, BC and BW. How can we use these options with IPL parameter.

    Thanks,
    Shajeel Ahmed
    RVXY_Shajeel_Khan


  • 2.  Re: IPL Issue

    Posted Thu December 29, 2011 01:44 PM
    0A82 is the ipl device, DC is the ipl parm. So, if you want to use WS, you'd specify 0A82WS. To use BC, 0A82BC. Etc.
    wilbert


  • 3.  Re: IPL Issue

    Posted Fri December 30, 2011 09:41 AM
    Hi,

    We want to use different parameters in started condition for eg. if we change "0A82DC" to "0A82WS" it will change all the system setting and we don't want that. We just want to use different ipl parm in started condition. So how can we do that?

    Thanks,
    Shajeel
    RVXY_Shajeel_Khan


  • 4.  Re: IPL Issue

    Posted Tue January 03, 2012 12:29 PM
    Hi Shajeel,

    I'm not sure I understand your question then. The different IPL parms can involve different settings because of different set of software being started. Can you elaborate or cite examples of what you're trying to do?

    Wilbert
    wilbert


  • 5.  Re: IPL Issue

    Posted Tue January 03, 2012 12:58 PM
    Hi Wilbert,

    My question is that now we are using 0a82dc as our IPL parameter. If we want to include WAS libraries how can we include those libraries? For eg.If we use 0a82ws as our IPL parm it will reset all the settings and our tools will be lost. We want to know that how can we use different parameter like ws, bc, bw in our current IPL parameter that is 0a82dc.

    Thanks,
    Shajeel
    RVXY_Shajeel_Khan


  • 6.  Re: IPL Issue

    Posted Wed January 04, 2012 08:03 AM
    You have two choices. You can create a completely new set of ipl parameters. RDz-UT uses SYS1.IPLPARM to store the LOADxx ipl parameters. If you want to create a new set of ipl parameters, you need to start here. The LOADxx points to a variety of things including the IEASYSxx member of parmlib. IEASYSxx points to all other system parameters. The second option is to modify an existing set of ipl parameters. This is definitely easier since mistakes in SYS1.IPLPARM can result in waitstates. We never recommend changing parmlib members in place. That is, all changes should be made in one of the concatenated libraries, eg. USER.PARMLIB. To add the WAS configuration (BC/ BW by default) to another configuration such as DC/DB, you will need to compare the system parameters specified in each case and resolve the differences between the two. In the case of WAS, I believe the major changes are in BPXPRMBB and VTAMBB.

    RDzJohn
    RDzJohn


  • 7.  Re: IPL Issue

    Posted Tue January 17, 2012 07:16 AM
    Hi John,

    As you told about the second option in which you told to modify an existing ipl parameter. Can you Elaborate that where to make changes and how we will compare the system parameters.
    Thanks,
    Shajeel
    RVXY_Shajeel_Khan


  • 8.  Re: IPL Issue

    Posted Tue January 17, 2012 09:33 AM
    The documentation supplied with UT lists various ipl options to use to bring up various subsystem functions. If you want to combine and/or expand your options, you can do this by looking at the PARMLIB members we have already setup for you and creating your own ipl options and PARMLIB members. You'll then add/ delete/ change system parameters as required. You can use an ISPF editor to make these edits. I suggest you familiarize yourself with these two books. They will certainly help you learn this process.

    MVS Initialization and Tuning Guide: SA22-7591
    MVS Initialization and Tuning Reference: SA22-7592

    RDzJohn
    RDzJohn