× 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.


  • Subject: Batch job S/36 OCL access to secured QS36F
  • From: "Gerald Kern" <gkern@xxxxxxxxxx>
  • Date: Fri, 30 Jun 2000 12:24:58 -0400

I'm attempting to implement security on QS36F so that the public access is
*EXCLUDE and QPGMR access is *ALL. The S/36 programs have been changed so
that the user profile parm is *OWNER, and adopted authority is *YES. All of
the programs have been changed so that the owner of each is QPGMR. The
problem is that since the files are being accessed from the 36 environment
via S/36 OCL, the adopted authority is not passed along since there is no
compiled object that the adopted authority can 'attach' itself to. When a
S/36 environment OCL procedure gets submitted to batch I get an error
message stating that the user doesn't have access to QS36F. Is there a
secure way to accomplish this without re-writing the OCL into CL programs?

Thanks, Jerry Kern, GKERN@aktion.com

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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.