Re: Stored Procedures

At 10:02 07/23/1999 , Chanh Le wrote:
>I guess AS/400 is a database machine, therefore, all programs on AS/400 are
>stored procedures.  So AS/400 community simply call them as "programs"
>because there no other type of program.  Instead of storing applications in
>an application sever (a shared drived) and "stored procedures" on a
>database server (another shared drive).   Everything is stored in one place
>- AS/400.

An AS/400 stored procedure is a program that is registered in SYSPROCS. You
can store AS/400 applications and data in different libraries, different
ASPs, or even on different physical machines if you wish.

>For programs attached to table called as triggers, it seems not widely
>accepted.  I think it does not work correctly for mass I/O.   And for big
>tables shared by multiple departments, triggers will impact the perfommence
>of machine.  Finally, because of the static process of triggers, a table is
>no longer flexible for maintenance, unless maintaining it in weekend when
>no application running - dropping, modifying table, and put it back.
>Triggers would be perfect for personal or very small group database.

I can't speak for anyone else, but I use triggers quite a lot.  What do you
mean about not working correctly for mass I/O? I have not observed this. It
is true that you cannot do some maintenance functions on tables while they
are in use. Is this different than other systems? Can you normally drop an
open table? I would think this would be a bad thing to do, since it would
leave many invalid pointers and handles.
Pete Hall
pbhall@execpc.com
http://www.execpc.com/~pbhall
+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---