×
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.
I seem to remember copying the spool files using *FCFC, doing the FTP, and then when the files arrived on the mainframe using IEBGENER to copy them to SYSOUT=*. *FCFC on the AS/400 is the same as what the mainframe expected.
Scott Lindstrom
Reynolds Leveraged Services | HP-UX, Linux, and AS/400 Administrator
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Wednesday, January 30, 2013 11:21 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Sending Reports to Mainframe
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.
midrange.com
