×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




It really depends on the amount of data.  Do you need other jobs to
access the data?  Since you are putting in QTEMP I suspect you don't
really need the data to be accessible by other jobs or after the job
ends, even if it end before completion.  If the data is a small amount,
I would use a data area.  If less than 1024 bytes, use the *LDA.  No
create / allocate / deal locate / delete to worry about.  It is just
there when the job starts and goes away when done.  Accessible by RPG
and CL.


Christopher Bipes
Information Services Director
CrossCheck, Inc.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Albert York
Sent: Tuesday, June 13, 2006 10:55 AM
To: Midrange Systems Technical Discussion
Subject: Re: Fastest access: user space, data area, data queue

Thanks Dave.

Actually, I am putting the object in QTEMP for later processes in the
job to read and modify. Typically I would use a data area but I was just
wondering if this is the most efficient. As I said, it probably doesn't
make much difference but I was just curious.


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-2026 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.