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?
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.