rerunning of installation CLIST?

william giannelli

rerunning of installation CLIST?

I am currently going thru alot of holddata for a maintenance apply. A number of the APARs suggest rerunning the installation clist in order to get all the updates. My question is after an installation or migration, how often do you rerun it for changes or maintenance? I have not rerun it. Also, while it may be bad practice, we have our own modified DSNTIJUZ job. Is it best to keep it updated via the install clist panels?

thanks

Bill

Javier Estrada Benavides

RE: rerunning of installation CLIST?
(in response to william giannelli)

Hey

   That used to be a controversial topic but not so anymore.

- If you keep modifying DSNTIJUZ then you have your own copy to modify which is the same copy you'll have to manually update each time you apply maintenance, otherwise you'll be using default values for new parameters you don't know you already have from new maintenance. Running the CLIST is the safe way to have an updated DSNTIJUZ.

- Now, having said that, when it hits you the hardest is if you do version migrations because you'll have to work longer on your updated DSNTIDXA clist member but you can generate values for it, so no big deal.

- Also, now that we're working on v12 and v13 won't show up or that's what we know.... then it's not quite a big issue for the previous point, or is it?

*** Last but not least, there's a stored proc to change zparms and generate a load module, which makes me wonder why IBM is supplying an easy way for something that in the long run will mean more work to have DSNTIDXA and DSNTIJUZ properly updated. (that's something to think about)

Hope that helps :)

 

Have a great day :)

 

Javier Estrada Benavides, Czech Republic / Mexico

IBM Champion for Analytics

IBM Certified System Administrator - Db2 12 for z/OS

IBM Db2 12 DBA for z/OS - 2018 (the ugly brown badge from IBM Open Badge Program)

IBM Certified System Administrator - DB2 11 for z/OS

IBM Certified Database Administrator - DB2 11 DBA for z/OS

Avram Friedman

RE: rerunning of installation CLIST?
(in response to william giannelli)


I agree it is best to go through the installation panels

for cm mode

migrate

previous DSNTDxx can be the current version

new  Parms will be picked up via DSNTIDXA

For ENFM or higher do an install

In both cases do the zparm job stores procedure job

if you are doing an install be sure you update the dataset size estimate  it’s only in an install that you are presented with the related panels  you will be happy that you did this for your next upgrade

 

 

 

 

 

 

Avram Friedman
DB2-L hall of fame contributor
DB2-L 'past' administrator

[login to unmask email]

Bob Jeandron

RE: rerunning of installation CLIST?
(in response to william giannelli)

We Usually run the install clist only one time unless there are a LOT of new parms in HOLDS.   Typically, we Edit DSNTIJUZ and document any changes in the job.  If you do run the CLIST, make sure you change the output SDSNSAMP--"SAMPLE LIBRARY".    Don't know if it still does this, but our SDSNSAMP was overwritten when we did ran the CLIST way back when......    

Peter Conlin

rerunning of installation CLIST?
(in response to Bob Jeandron)
Yes, the CLIST still overwrites members (with a warning enabling you to cancel minutes to hrs of work.)

We do the same as you for minor updates to DSNTIJUZ, but also try to update the output clist member from the original DSNTINST & compare the #code lines in the “maintenance” DSNTIDXA with a new copy of the installation clist output member (incrementing the member SSIDnn+1, starting at 00).

Increasingly with continuous delivery, maintaining an updated copy of the original output member from DSNTINST will be increasingly problematic whenever a “run the installation clist” ACTION item is mandated.

One problem is that the base parameters list (e.g. DSNTIDXA) as well as the output is not in sorted order (almost, but it’s not horseshoes, lawn bowling or my favorite, (especially in the shade with a jug of wine) bocce.)

DSNTIDXA input parameter member snippet:

DECPOINT
DEFAULT_INSERT_ALGORITHM
DEFCCSID
DEFDATE
DEFDATEL
DEFLANG
DEFMIXED
DEF_DECFLOAT_ROUND_MODE
DEFSQLVL

output parameter member snippet (different order):

DECPOINT
DEFAULT_INSERT_ALGORITHM
DEF_DECFLOAT_ROUND_MODE
DEFCCSID
DEFDATE
DEFDATEL
DEFLANG
DEFMIXED
DEFSQLVL

DSNTXAZP seems to perform output parameter ordering similar to the clist. (I confess I have yet to divine its utility.)

I suspect the sort order of the input lines to DSNTINST doesn’t really matter, but is there any reason why it’s not (as far as I can fathom) in a true sorted order (or why the default input & output order don’t match?)



From: Bob Jeandron [mailto:[login to unmask email]
Sent: Monday, July 08, 2019 9:28 AM
To: [login to unmask email]
Subject: [DB2-L] - RE: rerunning of installation CLIST?


We Usually run the install clist only one time unless there are a LOT of new parms in HOLDS. Typically, we Edit DSNTIJUZ and document any changes in the job. If you do run the CLIST, make sure you change the output SDSNSAMP--"SAMPLE LIBRARY". Don't know if it still does this, but our SDSNSAMP was overwritten when we did ran the CLIST way back when......

-----End Original Message-----

Russell Peters

RE: rerunning of installation CLIST?
(in response to william giannelli)

I never use the clist after the migration is complete. I've been working with db2 for about 18 years and have never used the clist after migration. We create our own zparm and decp jcl and use those for any needed changes. Now with v12 we don't even have to create the zparm and decp jcl, it's already done with the install.