× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Jeff Young
> Sent: Thursday, August 25, 2005 10:45 AM
> To: rpg400-l@xxxxxxxxxxxx
> Subject: Service Program DB Output
> 
> 
> I have the following questions regarding DB I/O in a service program.
>  
> 1. Can all of the I/O functions (Open, Close / Read / Write) 
> be done in separate procedures?

Sure.

> 2. If so, given that the Write function will be passed a data 
> buffer, and an OVRDBF command issued prior to calling the 
> program that called the Service Program that pointed the DB 
> file to a file in the users QTEMP library, will I have a 
> confilct in the Service Program with multiple users accessing 
> it concurrently?

Having trouble following that description.  But if I understand it correctly, 
the answer is no.
Remember that the activation of a service program is unique within a job.  
Multiple users will each have their own copies of file buffers and variables.

> 3. What special considerations must I be aware of if I attempt this.
>  

Only thing I can think of is how the service program will handle being called 
by multiple other programs within a single user job.  Are your entry programs 
running in a *NEW activation group or a named activation group?


HTH,

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.