|
Bill, You are correct. Those OCL brain cells haven't been used in quite a while. :) When we had a S/36 we would compile the programs as MRT-NEP with 1 user and use the multiple procedure approach. This made hopping between order entry, customer inquiry and item inquiry real fast. We did it for every interactive program, so in my brain it's "the way to do it". Bill Heinz wrote: > > 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. +--- | 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.