Re: Vendor wants an SST profile

[Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>]

Some offline discussions have led me to think that yes, they may need 
SST access if they're installing some MI software they've written that 
needs system state.  But I want to be told that, because if we ever need 
to restore a system that means we'll have to go through that same 
process.  It would really stink to restore your system after a DR event 
only to find you can't restore your HA software!!!


On 11/24/2019 8:54 AM, Roberto José Etcheverry Romero wrote:
> Wait, QEDD really needs sst access. IIRC it's due to the funky MI things
> that it does that are even above QSECOFR level (I mean that in the sense
> that not even QSECOFR has access to their objects and you cannot
> save/restore a QEDD installation properly, you need to reinstall from
> savf). Do remember that QEDD works with journals but instead of sending the
> entire journal it takes what it wants from the journal and sends only that
> and on the receiver system it also does funky things to take that data and
> apply it to the changed objects.
>
> I don't remember using D/A/D access during setup, but we did use the
> service QSECOFR to install. After that there was no more need to do
> anything SST related. At least on both of our customers running QEDD...
> Weird thing is the provider asking for multiple users and every last one of
> them with that access. Maybe it's for audit purposes?