No IPL is necessary to install or remove CA-1.
The SVC is dynamically added (or should have been since several version ago if
it wasn't), and, unless you intend to reuse it for RMM or something else right
now, dynamically removing it (which is what you are doing already) is pretty
much all you
] : Re: CA-1 Withdrawl from z/OS 2.5
Sent from Yahoo Mail on Android
On Thu, Sep 28, 2023 at 5:22 PM, Paul Gorlinsky
wrote: We are investigating what is necessary to remove CA-1 from the system
after turning on RMM in protect mode.
My original plan was to us TMSINIT to remove CA-1
Sent from Yahoo Mail on Android
On Thu, Sep 28, 2023 at 5:22 PM, Paul Gorlinsky
wrote: We are investigating what is necessary to remove CA-1 from the system
after turning on RMM in protect mode.
My original plan was to us TMSINIT to remove CA-1 and disable the PROC
(TMSINIT) p
This might sound odd, but since RMM has been around a VERY long time, your
chances of running into something that can't be fixed within RMM are pretty low
if not non-existent. You would most likely be better off just fixing the
problem and staying with RMM.
That's not to say that you shouldn't
Thanks for the additional information...
I will be removing the CAS9 parm entry for the CA-1 license and SVC init
The other question that came up was, how to reset to CA-1 if something is wrong
with the RMM processes. Hours or Days later.
This is a PLEX with three LPARs but only 8 tape dr
On Thu, 28 Sep 2023 16:22:24 -0500, Paul Gorlinsky
wrote:
>We are investigating what is necessary to remove CA-1 from the system after
>turning on RMM in protect mode.
>
>My original plan was to us TMSINIT to remove CA-1 and disable the PROC
>(TMSINIT) prior to starting DFRMM...
>
>Or do I ne
udit files
HTH,
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Paul Gorlinsky
Sent: Thursday, September 28, 2023 4:22 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: CA-1 Withdrawl from z/OS 2.5
[CAUTION: This Email is from outside the Organization. Unless you trust the
sen
You're close. You need to run tmsinit to disable CA-1 and also there are a
couple health checks that you need to disable. There is a section in the CA-1
manual on deactivating CA-1 right after the section on activating it, and in
fact I just did this two weeks ago at a site I manage that chang
We are investigating what is necessary to remove CA-1 from the system after
turning on RMM in protect mode.
My original plan was to us TMSINIT to remove CA-1 and disable the PROC
(TMSINIT) prior to starting DFRMM...
Or do I need to move it's SVC, re-IPL and not start TMSINIT and then start
DF
