Tim, Yes as part of initialisation there is a check for licensing. And that is
the result.
If it is wanted to act differently, a change would be needed.
I did not have those details about the specific situation, else would have
stated something a little differently first time.
Mike
Mike,
You said that when EDGSSSI is in the subsystem entry then DFRMM must be in
control but that's not what happened.
Following is the explanation from DFRMM level two;
When RMM failed to initialize the situation is similar to
when RMM is started with the following command 'S
Arthur,
You cannot take the snippets out of context. Each snippet is qualified.
Remember that rmm is always on your system (s/w delivered and installed as part
of z/os), you have to take steps to tell rmm that it turned on. Adding DFRM
susbsystem + EDGSSSI to IEFSSNxx turns it on fully. Adding
In the same post are these two snippets. The second seems
to contradict the first, and seems to be the problem that
the OP is complaining about:
On 14 Jul 2017 13:40:52 -0700, in bit.listserv.ibm-main
(Message-ID:<8306788698430144.wa.mikewwoodhotmail@listserv.ua.edu>)
I have no access to the RFE, but, if you follow the installation instructions
correctly you should not be able to write to a tape without rmm knowing about
it.
IFAPRDxx is simply a way to identify you have a license, it is not how you
ensure that rmm is in control for all tape activity.
On 7/14/2017 10:03 AM, Tim Deller wrote:
If you Run DFRMM ; Please consider voting for my RFE at:
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe_ID=106021
We used to run CA-1 and it had a zap to disallow tape creation until CA-1 was
recording.
Needless to say ; DFRMM is
If you Run DFRMM ; Please consider voting for my RFE at:
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe_ID=106021
We used to run CA-1 and it had a zap to disallow tape creation until CA-1 was
recording.
Needless to say ; DFRMM is different ; and we got stung.
