Handle Switch for QZDASOINIT

["Bill Freiberg" <bfreiberg@xxxxxxxxxxxx>]

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.