|
Touche'. Use of the data queue's does require api's. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin Evan Harris <spanner@xxxxxxxxxx> Sent by: security400-bounces@xxxxxxxxxxxx 09/25/2003 02:22 PM Please respond to Security Administration on the AS400 / iSeries <security400@xxxxxxxxxxxx> To Security Administration on the AS400 / iSeries <security400@xxxxxxxxxxxx> cc Subject Re: [Security400] Allowing Someone to Create User Profiles... Rob Would the API phobic use data queues ? Would they still used them if they looked at the API manual and subsequently discovered that the data queue calls were <gasp> API calls ? What about QCAEXEC. Seems to me that some of the mystery surrounding API's is the way IBM provided the documentation Just for the record I am neither API-phobic nor pointer phobic :) Regards Evan Harris >Evan, you're right about the group profile. That part of adopted >authority doesn't work and a profile swap is in order. Um, submit a batch >job which runs under QSECOFR and updates a data queue on the submitting >program that the process is done? Just another option for the API phobic. > >Rob Berendt >-- >"They that can give up essential liberty to obtain a little temporary >safety deserve neither liberty nor safety." >Benjamin Franklin _______________________________________________ This is the Security Administration on the AS400 / iSeries (Security400) mailing list To post a message email: Security400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/security400 or email: Security400-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/security400.
As an Amazon Associate we earn from qualifying purchases.
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.