Re: Aborting write with a trigger program

Rod,

Good question.  I really don't know, since we are not using any client based
programs here.  My guess would be their call would crash with an unknown SQL
error.  OS400 is not going to allow the record to be written with a blank
field.

I should probably do some reading on what would happen if someone did a CPYF
with a blank record to my triggered file.

Regards,

Jim Langston

rob@dekko.com wrote:
> 
> Jim,
> What happens if someone updates the file using a client based program such
> as Excel, ODBC or some other such animal?
> 
> 
>                     Jim Langston
>                     <jimlangston@conexfr        To:     RPG400-L@midrange.com
>                     eight.com>                  cc:
>                     Sent by:                    Subject:     Re: Aborting 
>write with a trigger program
>                     owner-rpg400-l@midra
>                     nge.com
> 
> 
>                     10/10/00 05:30 PM
>                     Please respond to
>                     RPG400-L
> 
> 
> 
> Thanks,
> 
> someone sent me some code for a trigger program that does exactly that,
> sends
> a program message using the QMHSNDPM API to abort the call.  It works like
> a
> charm.  The nice thing about it is I'm sending message CPF9898 which is
> pretty
> much a generic call.  In the message data I am sending the text: 'Can not
> have
> blank Equipment number - Not Written!'.  In the job log when the job
> crashes that
> message shows up, showing exactly what happened.
> 
> Thanks again, this is exactly what I wanted to do.  I wasn't aware that
> sending
> a program message would abort the write.
> 
> Regards,
> 
> Jim Langston
+---
| 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
+---