RE: Capture spool file name created in a job stream

[Rob Berendt <rob@xxxxxxxxx>]

I agree with you that WRKOUTQ should have a *OUTFILE option.  IBM does 
give you an API to process this though.





DRF@HeiligMeyers.com on 11/18/98 02:39:22 PM
Please respond to MIDRANGE-L@midrange.com@Internet
To:     MIDRANGE-L@midrange.com@Internet
cc:      

Subject:        RE: Capture spool file name created in a job stream

I happen to have done something like this a while back.  In the first CL
program called, execute OVRPRTF *PRTF OUTQ(<an outq>).  This command will
force all print files created by any called programs to reside in the output
queue specified.  You can then use the WRKOUTQ command to create a list of
the output queue (question for IBM:  When will we be able to send this
information to an output file?), copy the spool file to a physical file and
use the CL program to loop through the physical file and do the SNDNETSPLF
on each one.  

The output queue could even be created on the fly based on the job number.

Note, however, that this method has certain hazards.  If  IBM changes the
spool file format in the next release, this doesn't work.  You also need to
have the program delete the output queue listing when it's finished.

Donald R. Fisher, III
Senior Programmer/Analyst
Heilig-Meyers Furniture Company
(804) 784-7500 ext. 2124
Don.Fisher@HeiligMeyers.com
> -----Original Message-----
> From: Ravi [SMTP:ravi@spacestar.com]
> Sent: Wednesday, November 18, 1998 1:02 PM
> To:   MIDRANGE-L@midrange.com
> Subject:      Capture spool file name created in a job stream
> 
> Hello,
> 
> Scenario : A CL calls many,many RPG programs. A programmer who is
> somewhat familiar with the app. says atleast 40 - 50 programs are called
> within the jobstream !!!! Programs were written many years ago. Almost
> all the RPG programs have 5 or more print files defined in each program.
> There are CL's involved in the job stream which may be overriding the
> spool file names. No naming convention has been followed. All print file
> opens are user controlled. Not all the print files are opened/created
> all the time. Apparently there are times when no spool files are created
> in the job stream.  
> 
> Problem: Any/all spool file(s)  created in the job stream needs to be
> sent to a remote system. SNDNETSPLF has to be used, which requires a
> spool file name. I can trace the job stream, note down all print files
> used in the programs, enter a SNDNETSPLF command in the master CL for
> each print file followed by MONMSG CPF3303 (file not found in job). 
>                  (or)
> Take the easier way out.....SOMEHOW dynamically capture all spool file
> names created in the job stream and send the files to the remote system. 
> Is this possible ? Any suggestions will be appreciated....
> 
> Thanx
> 
> Ravi
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---