Re: Sending Reports to Mainframe -- MIDRANGE-L

Subject: Re: Sending Reports to Mainframe
From: CRPence <CRPbottle@xxxxxxxxx>
Date: Wed, 30 Jan 2013 09:21:18 -0800
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 30 Jan 2013 07:25, Laine, Rogers wrote:

I would like to run some jobs that product reports that go the OUTQ
QPRINT.

After the jobs complete I would like to copy the reports from the
OUTQ to a PF file to FTP file to the mainframe system. (CPYSPLF)
<<SNIP>>

After the issue with the code finding the spooled file is resolved, there may be value in knowing that SNDNETSPLF enables sending of the spooled report as a spool file without the huge loss of information that would result from using CPYSPLF; i.e. may be better than copy and FTP. See the DTAFMT() parameter of the Send Network Spool File for its *ALLDATA and *RCDDATA special values. Of course for using TCP there is SNDTCPSPLF (LPR) which also maintains the report as a spool file.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Sending Reports to Mainframe , Lindstrom, Scott R.

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.