|
jt IIRC, one reason for having QSECOFR sign on is related to the transfer of ownership and authority when restoring things. Vern At 09:50 AM 10/30/2002 -0500, you wrote:
Booth, this is less of an issue than it might appear. Although I'm NOT necessarily contradicting what Leif has been saying. The 3rd party vendors that I've dealt with back in the days of yore (JDE, Lawson, Synon, and ProData too, probably) ALREADY took whatever authority they wanted. Almost EVERY package I've EVER loaded had the first instruction of the install state "Sign on as Security Officer". Never much cottoned to that, but it was "Generally Accepted Computer Practice", back 10 or 20 years ago... I'm guessing it still is these days.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.