×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hello all you purveyors of iSeries "hackish amusements," with your self-replicating RPG programs... (Sorry, I couldn't resist ;-)...
Is anyone out there using Robot/SCHEDULE application security vs. just using the default *PUBLIC access that is used when the "Do you want to use ROBOT security system" parameter is set to "N" on the General System Defaults screen? If so, are you using the profile-level controls found within the "Maintain Secured Objects" screens or are you using an authorization list (or lists)? Are you using the "Authorized Objects" screens to control objects referenced when users setup/manage Robot jobs?
I am working on closing some exposures for my current client and I don't have the luxury of a separate test system for Robot. I am curious to know what other's experiences have been.
TIA for any input!
Best regards,
Steve
Steven W. Martinson, CISA, CISM, CISSP
Security Consultant
Cypress, Texas
This mailing list archive is Copyright 1997-2024 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.
midrange.com
