RE: Costly PSDS

What about using the file function that creates a file with a random name,

then retrieve that name and use it as the name for the new data queue.

You have my ear, what's the specific function name? :-)

Also why not just create it in QTEMP so that it goes away with the job?

I need to have a program (Java) in another job write to this uniquely named
response data queue.  If it resides in QTEMP I don't think the other job has
access to it, correct?

Also Rob, you mentioned creating a UUID.  The only problem is that most will
not be able to fit into 9 characters (assuming first character will need to
be specified by me and be non-numeric).  That is why I am looking to use
something like JOB_NUM from PSDS (but it sounds like that might be
dangerous).

Aaron Bartell
http://mowyourlawn.com



-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Bob Cozzi
Sent: Wednesday, September 13, 2006 8:32 AM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: Costly PSDS

Aaron,
What about using the file function that creates a file with a random name,
then retrieve that name and use it as the name for the new data queue. Also
why not just create it in QTEMP so that it goes away with the job?

-Bob Cozzi
www.iSeriesTV.com
Ask your Manager to watch iSeriesTV.com


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of albartell
Sent: Wednesday, September 13, 2006 7:44 AM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: Costly PSDS


The data queue that is receiving the initial input will be "system wide"
because I will have a prestarted Java job out there waiting on that data
queue to pick them up and process them from any number of jobs.  So that can
be named DQIN for all intents and purposes.  The data queue the Java program
is responding to is the one that will need to be unique to the job.  

So that leaves me needing to create system wide uniquely named data queues.
Note though that it only has to be unique within the job because after it is
initially created (using the JOB_NUM as part of the name) I can reuse it and
not recreate it each time.  I can understand your concern about job numbers
going full circle, but I should be able to rely on the fact that the same
job number will never be active at the same time and based on that, as long
as I "initialize" the job number data queue at program startup time I should
be good to go.

This is where it would be nice to have a "destructor" routine in RPG that is
called when a program is ended because I am trying to figure out how to
cleanup the data queues unique to each job.  Sure I can code a routine that
the programming calling me can call when the user exits out of their
interactive app in a controlled fashion (i.e. hitting F3), but what is a
best method to cleanup when the user simply closes their 5250 emulation
window?

Thanks for your tangent Rob, it is helping me be sure of the direction I am
taking :-)

Aaron Bartell
http://mowyourlawn.com

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of rob@xxxxxxxxx
Sent: Monday, September 11, 2006 9:34 AM
To: RPG programming on the AS400 / iSeries
Subject: Re: Costly PSDS

Going off on a tangent.  But if the data queue is used ONLY by that job, why
not create it in QTEMP and not worry about the data queue name?

If it is used by multiple jobs (and unless you a thread coding animal I
suspect it is) then you need to consider "truly unique".  Being as a data
queue program can run until the next IPL, and if you fire off enough jobs
between IPLs then your job number could be reused.  Maybe use UUID instead?

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com




--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.