Len's note brings up an interesting question for our OS/390 environment.
We're currently running OS/390 2.6 with plans to install 2.10 by end of 1st qtr.
'01. Our ADSM is currently 3.1.2.50. Our original plan was to upgrade to TSM
4.1.x by the end of the yr. However, if 2.10 ships with 3.7.? we definitely would
not want to overwrite TSM 4 with TSM 3.7.
It looks like we should hold off on the TSM upgrade until after we're up and
running of OS/390 2.10, and if that gets us to an acceptable version do we need
to pursue 4.1 anytime soon? Anyone out there had a similar situation? I'm curious
about what to expect during the OS implementation as it relates to taking *SM
from our current level to whatever version of 3.7 is shipping. Any differences
from a straight TSM upgrade?
Thanks for any input.
--
Jim Kirkman
Admin Info Services - Systems
UNC-Chapel Hill
966-5884
Len Boyle wrote:
> In article <[EMAIL PROTECTED]>, Larry Heath
> <[EMAIL PROTECTED]> says:
> >
> >While doing the apply-check for the TSM S/390 API and for the TSM S/390
> >Backup-Archive Client, I rec'd an error msg that fmid HOT1140 was missing.
> >We have fmid HOT6608 (we are on 2.8) in another CSI.
> >Has anyone been here and resolved this problem?? If yes, how did you
> >resolve it??
> >
> >TIA ......... Larry
>
> Hello Larry
>
> The problem is that this client is treated in a different way then
> all the other adsm/tsm clients. With any of the other clients if you
> have a problem and it is fixed in a new version of the client, you
> can fetch the new version and install it assuming that your adsm/tsm
> server is not too many versions back. A windows nt 4.1 client
> can be installed for use with a tsm 3.7 server. This works because
> The windows nt 4.1 client includes the full install package.
>
> In the case of the os/390 client, the client is only an incremental
> upgrade. So to install a 4.1 client ptf, you need to have the base
> tsm 4.1 client install materials, which you can only get thru your
> marketing folks. Unless things have changed in the last hour or so
> the tsm tech support can not help with this problem.
>
> The two interesting things about this are:
> 1) The latest os/390 release 2.10 which just became available ships
> with tsm 3.7 not tsm 4.1
> 2) Several apars are fixed in 4.1 that are not fixed in 3.7.
>
> PS It is even more fun if you are using the os/390 client with
> a server that is not os/390. We are having a hard time trying
> to get the tsm 4.1 client code with our tsm 3.7 to tsm 4.1 upgrade
> from Tivoli. They keep calling it an IBM product and not the
> Tivoli feature code as listed in the tsm 4.1 ann letter.
>
> Sigh!
>
> -------------------------------------------------------------------------
> Leonard Boyle [EMAIL PROTECTED]
> SAS Institute Inc. ussas4hs@ibmmail
> Room RB448 [EMAIL PROTECTED]
> 1 SAS Campus Drive (919) 677-8000 ext 6241
> Cary NC 27513
