I always feel foolish when I reply to my own posts, but here goes.

For those of you playing the home game and watching the gladiatorial combat 
between "Software Management" and the "Grizzled Veteran"  here is todays battle.

I think I see where I have not toed the line with the 'new' method of 
Installing things.     I went "old school" and modified my dataset names to 
prepend a HLQ of CB (I still do not know where that came from - me or z/OSMF).  
 What I did not know is that my worthy opponent (which I will now call the 
Lion) had secret strategies that it was going to deploy.   The Lion took my 
well crafted and meaningful dataset names and suffixed them with '.#'.

The old ServerPac dialogs generated jobs would remove the HLQ on the physical 
volume and make the names match what was indirectly cataloged in the system 
being upgraded.   For example  HLQ.SYS1.LINKLIB cataloged on the newly created 
SYSRES would be 'zapped' to the name SYS1.LINKLIB which has been indirectly 
cataloged to ****** for many many years and will NOT be changed.   A HLQ.xxx 
catalog entry would be created so that JCL could be used to select which one 
you were trying to modify.     My review of these new jobs is not showing me 
where any catalog ALIAS entries are being created (but I could have missed 
them).
This left us with the option of IPLing the old release,  then new release for 
testing, then back to old release to get on with our work.


To adopt this new suffixing approach, I now have to lose a week of work in 
order to rename the data sets in such a way that the suffixing process 'might' 
work.
Then back to my local usermods again for re-APPLY.

This sort of thing has been happening to me for years.  I make a choice for 
local needs  (like software upgrade vs software replacement in the old 
ServerPacs)  only to find out that two days later the generated jobs will not 
do what I wanted to do or what I thought they would do.   Square One!!!
Like an Abbot and Costello routing,   THIRD BASE!!!.   All convoluted 
difficulties mean Square One.   I just have not taking to drinking the IBM 
Cool-Aid and will stray into the world of independent thought.

What I would love to do is 'Copy' my current Deployment as a baseline from 
which to start over.    I cannot find a 'Copy Deployment' under z/OSMF --- Only 
'Add'.    Welcome to the next battle trying to tame this Lion.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to