On Wed, 14 Dec 2011 15:28:18 -0500, Lizette Koehler <[email protected]>
wrote:
>We just completed the upgrade to CA MSM 4.1. So far not bad. However, we no
>longer have our SMP/E output because that was in TEMP files in MSM. So the
>task history is empty and any information I had from the last couple of weeks
>of maintenance I installed to various CA Products is MIA.
>
>Apparently CA decided it was a good thing to purge all temp files.
>
>This is a heads up if you are not at MSM 4.1 yet. You may want to offload
>your SMP/E output to presever the maint info.
>
>I am going to see if the SMP/E Logs can provide me with some of the
>information I need for my upgrades.
>
>Lizette
>
I've just completed my upgrade from CA MSM 3.0 to CA MSM 4.1. I skipped 3.1
as I
didn't think it changed enough at the time to bother. Didn't have time to
look at 4.x
until now, and 4.1 is current. The one thing I really need (and am not sure
that
4.1 can do it yet) is support of indirect cataloging for deployment. See past
posts in
IBM-MAIN, but basically I need to create data sets on a target sysres set
volume
without trying to catalog them since they are indirectly cataloged. When I
tested
deployment before, I wanted to update my cataloged version on the live sysres
set.
So below is my experience with the upgrade, which was mostly painless. CA had
a "migration to 4.1 checklist" document on their web site and that was very
helpful and made the process quicker. It took my about a day to upgrade. That
would have been quicker, but I like to document in detail everything I'm
doing. :-)
1) I didn't lose any old task history nor SMP/E output, so I'm not sure what
Lizette may
have done differently. I even moved the "msmtmp" file from a local
download
directory that we use for other things into its own "standard" location /
zFS
file system per install documentation.
2) Even though I created all the zFS files (was the owner) and I should have
had
permission to them, I ran into a problem during the install scripts with a
copy
command:
/bin/sh, -c, cp -F nl "//'hlq.SAMPLIB(INS04S31)'" ./SAMPLIB/MSMINS04] could
not be executed.
Even though the pre-install verification utility does warn about not being
UID 0, I still saw
nothing in the migration checklist, the installation checklist (another
doc) or install
manual that said to "su" prior to executing the install script. I ran
into the same
exact problem with MSM R3.
My advice: "su" prior to executing the install script.
3) The Datacom R12 SVC load failed because I chose the same number as the R11
SVC
that was in use for MSM R3. I thought, "no problem re-run the load job
with the
CAIRIM "REINIT" parm since MSM was the only user and MSM was not active".
However
when I did this it crashed CA-11 - which is using a different Datacom SVC
talking
remotely to a different Datacom MUF on a different LPAR. (ouch!)
I double checked everything to make sure this wasn't "operator error" and
as far
as I can tell, I did nothing wrong. To fix the problem I did a reinit
for CA-11's
(and Jobtrac's) Datacom SVC and a reinit of the MSM R3 Datacom SVC and
restarted
CA-11. As far as I can tell this is a bug of some sort, but I won't say
so for sure
until CA gets back to me. I have an open ticket and they have all the
doc.
As far as MSM upgrade was concerned, I just chose a different Datacom SVC
to
go along with the MSM upgrade from Datacom AD R11 to R12.
My advice: Pick a new SVC number for Datacom if upgrading MSM from Pre-V4.
So I am now up under 4.1 level 640 (I also applied current maintenance) and
everything
looks fine and seems to be working fine as well. Time to read more about
what's changed
from 3.0 and to see if I can use deployment now.
Regards,
Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
mailto:[email protected]
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
Systems Programming expert at http://expertanswercenter.techtarget.com/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
