Re: Database Triggers

Well, I figured out the problem.  Our programmer had copied code out of an IBM
manual.  The DB2 for OS/400 Database Programming manual, in Chapter 17 specifies
in the example written in RPG to identify the *entry parm as the following:

0169.00      C           *ENTRY    PLIST
0170.00      C           PARM1     PARM           PARM1
0171.00      C           PARM2     PARM           PARM2

Parm1 is defined as a data structure.  It has a problem moving the field into
itself.  It works successfully without any entry in Factor 1 or a different 
field
Factor 1.  I wasn't aware that this would cause a problem.  I've seen people 
move
a field into itself before without it blowing up.

Thanks for the input

Steve Faist
World Book Consulting Group
sfaist@earthlink.net

Steve Faist wrote:

> I have a question relating to Database trigger programs.  We are at
> level 50 security on V4R1.
>
> At execution time of the trigger program, I'm getting an Object domain
> or hardware storage protection violation message.  (MCH6801).  The
> trigger program was just created and is in RPG/400.
>
> Any suggestions???
>
> Steve Faist
> World Book Consulting Group
> sfaist@earthlink.net
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@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
> +---
> uucp



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@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
+---