×
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.
Roger Mackie wrote on 04/03/2007 09:52:56 AM:
It was my understanding that IBM recommends the trigger be in the same
library. It caused us (more severe) problems when they weren't.
I am not suggesting that you change this design. I was only suggesting that
if the trigger program is in this library that, then a user will not be
authorized to call that trigger program if you have excluded them from that
library. If this is the case, then even if the trigger program adopts
authority from QSECOFR, it will not help because the not authorized problem
is occurring before the trigger program has a chance to run.
I still think the best advice I have give you today is to use the security
audit journal and the job log to determine the exact problem.
Ed Fishel,
edfishel@xxxxxxxxxx
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
