Re: triggered file list problem

[dhandy@xxxxxxxxxxx (Douglas Handy)]

John/Booth,

>You can qualify the trigger program to a particular library.   However this
>is not your problem,   

Trigger programs never use the library list except during the actual
ADDPFTRG command.  When you add a trigger and specify *LIBL for the
program library, it gets resolved based on the then current library
list and the resolved library name is stored with the file
description.  In effect, triggers always get called as a qualified
name.

You can verify this by using ADDPFTRG with *LIBL, then using DSPFD to
look at the trigger information.  The library name will be a specific
library, not *LIBL.

According to IBM, this is by design and won't be changed.  They did it
this way to avoid security exposures by people inserting their own
trigger programs higher in the library list.

Booth --

>However if I use some program outside of the norm, say DFU or ODBC, and 
>start the job with a qualified name of "Library/FILEMaster" then I get 
>serious troubles. 

Please define "serious troubles".   

The trigger program itself should be correctly called regardless of
your current library list (see above).  If the trigger program itself
relies on the library list for other objects it uses (files, data
area/queues, etc) then that is where your problem is.

You can switch files to UsrOpn and perform an OVRDBF from within the
trigger program first.  But instead of qualifying the library name in
the program I'd recommend taking the triggered file's library name
(from the trigger buffer bytes 11-20) and using it to build your
OVRDBF string.

This can simplify test environments, etc.

Doug
+---
| 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
+---