× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Capture spool file name created in a job stream
  • From: Michael Calabro/commsoft<mcalabro@xxxxxxxxxxxx>
  • Date: Wed, 18 Nov 1998 13:54:24 -0500




>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....

There may be several answers to this one.
Create a remote outq (one that points to the remote 
system), then in the main CL program, OVRPRTF 
*PRTF OUTQ(rmtsysoutq).

Or use a special outq, or USRDTA or user profile
and the spooled file APIs to pick them out of all 
the other spooled files.

Buck Calabro
CommSoft, Albany, NY
mailto:mcalabro@commsoft.net



+---
| 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
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.