RE: Fastest access: user space, data area, data queue

Thanks.

The data is 1000 bytes but there will be more than one occurrance. It will only 
be used within the same job and I don't need it after the job ends.

Albert

----- Original Message -----
From: "Chris Bipes" <chris.bipes@xxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Subject: RE: Fastest access: user space, data area, data queue
Date: Tue, 13 Jun 2006 11:06:12 -0700


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.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.