| 
 | 
Hi
     I am having problems with a (seemingly) simple program to validate
ODBC
requests via the ODBC exit point
QIBM_QZDA_ROI1        ZDAR0100 format
I chose ZDAR0100 (object information) rather than ZDAQ01/200 as I don't
want to have
to parse the SQL statement.
The ZDAR0100 appears to have the file & library that in set positions.
My program checks through a data-base file for valid library/file names
before deciding
to accept/reject the request.
All seems to work ok in that the Reject message is sent to QSYSOPR,
but the request is allowed despite my program returning a parameter
of '0'. Dumping the program at ths point shows value '0' (reject).
I can only assume that something is over-writing the variable somewhere.
Someone suggested that when adding the exit program I should specify
the PGMDTA parameter to be the length I am expecting in my program
but this seems to make no difference.
We are on V4R5
Mike
Bits of the code
 *
C     *Entry        Plist
C                   Parm                    PM1exit           1
C     WK1format     Parm                    PM1format      1024
<snip>
 * Reject
C                   Eval      PM1exit = '0'
 *
C     CN1reject     Cat       WK1file:1     WK1msg
C                   Cat       '/':0         WK1msg
C                   Cat       WK1lib:0      WK1msg
C                   Cat       'by User':1   WK1msg
C                   Cat       WK1user:1     WK1msg
 *
C                   Exsr      SendMessage
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.