First of all, thank you guys for the subfile help. I was able (with  your 
advice) to get the darn program up and running, so have a beer on  me 
(please...pick the dollar tap ones :o)).
  
  What is a quick, down and dirty way to prevent someone without  authority to 
run a program? I figure it would need to be a CL wrapped  around the actual 
program, but I dont know what to use. 
  
  Would I use CRTVLDL, which wouldnt be too feasible as this program  would be 
going out to multiple entities? Or is there already something  existing in the 
USRPRF that I could key in on?
  
  The program I need to lock out is a custom menu creation one. The  people we 
do the software for are looking for an inobtrusive way to  lock the temp help 
out from being able to snoop into other programs and  potentially senstive 
areas (thus, the properly authorized person would  create a custom menu that 
let the temp help only get into the allowed  programs). The create menu program 
I wrote has the ability to go into  any library and pull the commands to start 
virtually any program on the  as400. So after meeting with the application 
support people, it was  decided I better lock it down somehow (which I wanted 
to do in the  beginning, but getting it going first was the priority (I love 
trade  shows)).
  
  Thanks in advance,
  JenR
  

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.