On Wed, 13 Mar 2019 13:09:03 -0500, Bill Giannelli wrote: >Please excuse the rookie questions, but that means one global, clone the >target and dlib before apply. >then lets say I need a one-off ptf to the previous maintenance level....I >apply that to the clone target? >thanks
Yes, one global zone. When cloning the target zone, o ZONECOPY to copy the zone o ZONEEDIT to update DDDEFs o Use your favorite tool to copy the data sets. DSS, FDRCOPY, etc. If you are going to do it this way, I suggest a naming convention that will help you to keep it straight. For z/OS that might be o Target zone name is Tvolser or volserT o DLIB zone name Dvolser or volserD where "volser" is the name of the IPL volume. For other products, the target zone name can be one node of the DSNAME of the target data sets. You can use SYMBOLICRELATE to define data set aliases, then change to a different release by updating the symbol for that product. If the product has a started task, you will need to shut down the product, change the symbol, and bring the started task back up. For linklist data sets, specify the symbol in the data set name in your PRODxx for IPL time. For dynamic changes, define a new linklist set after shutting down any started tasks that use the product, then bring it back up. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
