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?


On Sat, Nov 23, 2019 at 1:48 PM Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
wrote:

I have several customers that run that software, some even supported by
BCS, that do not allow that type of access, in fact none that I am ware of
do. They don't have a legitimate reason for it.

Absolutely denied.

Jim Oberholtzer
Agile Technology Architects



On Nov 23, 2019, at 9:36 AM, Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
wrote:

The vendor is QEDD, but the partner is BCS. And it's the partner who is
demanding the access. They want full access user profiles and SST access.
And its not like they just want a runtime profile with God access, they
want every one of their support accounts to have it as well. As in "As a
general warning, any changes to the profile from the documents
specifications may have unexpected results."

The more hear, the less I like.

On 11/23/2019 8:15 AM, Jim Oberholtzer wrote:
Who’s the vendor? I’ve not had that request before except from IBM
and
then only when we are on a support call together.

Sounds questionable to me.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.