RE: Handle Switch for QZDASOINIT

Bill,

This is a shameless plug I know, but the answer can solve your problem
quickly and easily.  You are finding out why purchasing a package like
The PowerTech Group's PowerLock NetworkSecurity product is advantageous.


The switch capability you are looking for has been built into it since
its inception.  All you have to do is install it, activate it, and
supply the profile to switch to.  Simple and easy.  

If there are things you wish to do above and beyond the functionality
provided by NetworkSecurity it is very easy to have NetworkSecurity run
the exit program you have written.  And there is no need to stop and
start servers when you do request an additional exit program run from
within NetworkSecurity.

If you have any questions regarding NetworkSecurity visit our web site,
or call 1-253-872-7788 to speak with a representative.

Gary Monnier
www.powertechgroup.com    gary.monnier@xxxxxxxxxxxxxxxxxx

The Powertech Group Inc.  Seattle, Washington 
Where the Security Experts Live!

Phone:  +1-253-872-7788
Fax  :  +1-253-872-7904



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bill Freiberg
Sent: Thursday, February 27, 2003 7:48 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Handle Switch for QZDASOINIT


I need to restrict file visibility to a user when that user comes in
using ODBC.  That the same user needs to have access to the files when
they come in through our green screen applications. The approach I have
taken is to write a handle switching program to switch from a known
group of current users (who have all file access), to a special user
profile that I can authorize as needed to block access. I then set this
up as an exit program in the following IBM supplied exit points:

QIBM_QZDA_INIT
QIBM_QZDA_NDB1
QIBM_QZDA_NDB1
 QIBM_QZDA_ROI1
 QIBM_QZDA_ROI1
 QIBM_QZDA_SQL1
 QIBM_QZDA_SQL2


When I run this on my development machine, I can see the exit point fire
.... when on my production machine, it does not. We have setup
differences for the QZDASOINIT jobs between the two machines:

   The development machine does not automatically start any QZDASOINIT
   jobs, and the jobs it does start run in QSERVER and are valid for one
   use, then shut down.
   On the production machine the QZDASOINIT jobs automatically start x
   jobs, are reused, and run in QUSRWRK.

Do I need to end and restart the SBS to get my new exit point to fire?
Will they not fire because they are not in QSERVER? Are there any other
exit points I should include this in to catch all ODBC traffic?

TIA,

Bill Freiberg
Hub Group, Inc.

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.