Re: Old 36 Display Files

["Bill Heinz" <weheinz@xxxxxxxxx>]

> Multiple people can run the same program, they just can't run the same
> procedure.  So let's say you have program RPGPGM and you have procedure
> OCLPROC that calls RPGPGM.  Each user must have their own, uniquely
> named OCLPROC.
>
> Change OCLPROC to contain this single entry:
> RPGPGM?WS?
>
> Now take whatever you had in the original OCLPROC and propagate it into
> new procedures for all occurrences of RPGPGM?WS? that might appear.

You don't need multiple procedures.  A procedure can be run by multiple
people at the same time.  This sounds like a file or record lock problem.
I've had some thing similar happen when the program had a file open for
update.  Because the last record read was still locked by the first
occurance of the program the second occourance had to wait when it tried to
read the record until the record was released by the first occourance (read
loop).  Solution was simple for me,  the program did not need to update the
record in the read loop, so I released the record after the read.  Problem
solved.


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

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