RE: Multi threading Data Queues

If you have different data on a queue being processed by different
application, you can key/fifo a data queue.  The key would identify the type
of entry and each processing program can read only its key and get its data
fifo.  Otherwise you are spending a lot of time reading / sending data queue
as the wrong processing program places stuff back on the queue.  And yes it
will be at the end of the queue, not back where it came from.

Data queues are not single threaded.  You can have as many jobs sending /
receiving from a queue as you want.  If the data MUST be processed serially,
I would recommend one job reading from the queue and handling all data types
by calling the necessary processing program.

Now if it does not matter what order thing are processed in, you can have
user entries use a lower key value than the over night batch processes.  By
reading a keyed data queue with a key value GE *Lowval you will get the
lower key entries from the user input screens before the over night batch
job entries.

What are you doing?

Christopher K. Bipes      mailto:Chris.Bipes@Cross-Check.com
Operations & Network Mgr  mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.          http://www.cross-check.com
6119 State Farm Drive     Phone: 707 586-0551 x 1102
Rohnert Park CA  94928    Fax: 707 586-1884


-----Original Message-----
From: Weatherly, Howard [mailto:Howard.Weatherly@dlis.dla.mil]

Folks,

I am trying to figure out something here, I have a cross platform
application using DRDA between the 400 and a mainframe, currently the jobs
are queued to a subsystem job queue which is set to only allow one job at a
time. The reason is that we used QM Queries and data queues to select nTuple
data that is needed to update the mainframe.

Part of this process runs early in the morning about 4am and loads up the
processing queue with perhaps 1500 to 2000 requests. This gets the normal
user entering things manually behind all of the n(k) transactions in the
queue.

I want to run more than one of these entries in the subsystem at a time but
I am drawing a blank on the best way to set the data queues to be multi
threaded.

What happens if a program reads a entry from the queue, decides it does not
belong to it and places it back on the queue, will the end-of-queue (entry
size) still be set at the proper place even though an entry has been
replaced on the queue? Or is there some other incantation I can use to
multithread the data queues?