RE: QRCVDTAQ

Hi:

Several people who have responded to my question (thank you!) mentioned 
asynch processing as a benefit of data queues. However, at least one of 
the eight data queues we have is processing data that comes from programs 
submitted in batch by interactive programs. That is,

   - RPG green screen app A prompts the user for data and passes that data 
to

   - CL program B which submits a job in a single-threaded job queue to 
run RPG program C

   - RPG program C passes data (I'm not clear on the mechanism) to the 
data queue in which RPG program D is running (or "which is running program 
D" ... I'm not clear on that either).

All of the instances of program C that process through this data queue are 
submitted to the same single-threaded job queue. Am I wrong in wondering 
about the point of doing it this way? The question arises because we 
occasionally bottleneck at the job queue, but nobody wants to mess with 
the structure of the processing (12 year old code and configuration, in 
this area).

Darrell

Darrell A. Martin  -  754-2187
Manager, Computer Operations
dmartin@xxxxxxxxxxxxx



This e-mail, including attachments, may contain information that is 
confidential and/or proprietary, and may only be used by the person to 
whom this email is addressed. If the recipient of this e-mail is not the 
intended recipient or an authorized agent, the reader is hereby notified 
that any dissemination, distribution, or copying of this e-mail is 
prohibited. If this e-mail has been delivered to you in error, please 
notify the sender by replying to this message and deleting this e-mail 
immediately.