Joined: 15 Dec 2002 Posts: 637 Topics: 43 Location: Bengaluru, INDIA
Posted: Tue Dec 31, 2002 9:00 am Post subject: TDQ Vs SPOOL files
It is a well-known fact that for submission of a batch job (FTP, mail, printing et al) from a transaction can be done by either TDQ or a SPOOLFILE. For a TDQ, we give some value of TRIGLEV. (I do not know what should be the TRANSID value though.) For a SPOOLFILE, we specify INTRDR for USERID. What I want to know, is the relative merits and demerits of TDQ vs SPOOLFILE?
Now, I am not asking this question, because I am designing some application. I am asking this purely out of curiosity. _________________ ALL opinions are welcome.
Debugging tip:
When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
-- Sherlock Holmes.
Joined: 29 Nov 2002 Posts: 382 Topics: 27 Location: Chennai, India
Posted: Thu Jan 02, 2003 12:20 am Post subject:
Hi Cogito-Ergo-Sum,
For submission of a batch job from a CICS application program, we have to use an output extra partitioned TDQ. The TRIGLEV and TRANSID options (DCT Options) that you are talking about perhaps apply to only intrapartitioned TDQ. Please correct me if I am wrong.
Joined: 15 Dec 2002 Posts: 637 Topics: 43 Location: Bengaluru, INDIA
Posted: Thu Jan 02, 2003 1:52 am Post subject:
Manas,
TRIGLEVEL and TRANSID are needed for Intra TDQs. You are right.
For Extra TDQs, we need to have a DESTID. Is this the parameter that directs the TDQ to INTRDR? BTW, I looked into our RDO (Resource Definition Online). But, I could not locate the DESTID. So, how should I ensure that a given TDQ is to be directed to INTRDR? _________________ ALL opinions are welcome.
Debugging tip:
When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
-- Sherlock Holmes.
Joined: 26 Nov 2002 Posts: 12376 Topics: 75 Location: San Jose
Posted: Thu Jan 02, 2003 4:54 am Post subject:
Cogito,
Well you all know the advantages of TDQ's. However Spool files are mostly used to buffer output directed to low-speed peripheral devices (printers, punches, and plotters) between the job that creates them and actual processing by the device.
The advantages of the spool commands:
Create an (output) file for printing or other processing by JES. JES
manages most of the "unit record" facilities of the operating system,
including high-speed printers, and card readers. In order to use
these facilities, you pass the data to be processed to JES in a spool
file.
Submit a batch job to MVS. Spool files directed to the JES "internal
reader" are treated as complete jobs and executed.
Create an (output) file to pass data to another job (outside of your
CICS), that runs under MVS.
Retrieve data passed from such a job.
Create a file to pass data to another operating system, such as VM,
VSE/ESA, or an MVS system other than the one under which your CICS is
executing.
Retrieve a file sent from such a remote system.
Now the limitations of spool files:
creating very large numbers of spool files can stress JES resources; you should consult
your system programmer before designing such an application.
Spool files require other resources (buffers, queue elements, disk
space) until they are processed. You need to consult your systems
staff if you are producing very large files or files that may wait a
long time for processing at their destinations.
Code NODE('*') and USERID('*') to specify the local spool file and to
enable the OUTDESCR operand to override the NODE and USERID operands.
Do not use NODE('*') with any other userid. If the NODE and USERID
operands specify explicit identifiers, the OUTDESCR operands cannot
override them.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
