You are not alone, John. That is exactly how I do it.
Cliff McNeill
> Date: Thu, 30 Sep 2010 09:17:02 -0500
> From: [email protected]
> Subject: Re: IPLTEXT and NUCLEUS dates
> To: [email protected]
>
> OK. I guess our maintenance is very old fashioned. I take down my sandbox,
> back its volumes, then APPLY to them. IPL it with the maintenanced volumes
> and do all my initial testing. I then clone those volumes to replace the
> other system's RES and UNIX volumes using __new__ volsers. I then IPL the
> system's LPAR with the new RES volumes and go. Wash, rinse, repeat for each
> system (we only have two "production" systems).
>
>
> ________________________________________
> From: IBM Mainframe Discussion List [[email protected]] On Behalf Of Rob
> Scott [[email protected]]
> Sent: Thursday, September 30, 2010 8:50 AM
> To: [email protected]
> Subject: Re: IPLTEXT and NUCLEUS dates
>
> John,
>
> >> Why can't SMP/E do the ICKDSF PUTIPL command as well? It should know the
> >> volser to update - it is the one containing the updated SYS1.NUCLEUS.
>
> Surely most sites do not IPL their system from the SMP/E volumes and datasets
> - there is normally some sort of propagation JCL to copy to "real" runtime
> SYSRES volumes - and as stated previously there is no harm to suffix that
> copy JCL with a PUTIPL.
>
>
> Rob Scott
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: GET IBM-MAIN INFO
> Search the archives at http://bama.ua.edu/archives/ibm-main.html
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
