×
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.
On 23-Dec-2011 09:13 , Bryan Dietz wrote:
I think others have had luck FTPing the file to the QPRINT printer
file.
I can confirm that. The FTP allows naming a .FILE without a .MBR
which even makes the request seem more intuitive since the device file
type PRTF can have no members. Last I recall, CPYFRMSTMF neither
allowed that naming nor any capability to write to a printer file even
with overrides to the file name being opened :-(
Both the FTP subcommands PUT and GET allow a target name of a program
described printer file, such as:
PUT mydata.txt /qsys.lib/qgpl.lib/qprint.file
When the client and server are the same, the GET is "nicer" IMO, for
producing the spool file in the local job. For a PUT [e.g. as required
when the client is not the IBM i] I would typically first issue an
override to the printer file, to ensure desired SplF ownership [and\or
possibly other attributes] like with either [or both like-scoped] of:
QUOTE RCMD OVRPRTF *PRTF HOLD(*YES) SPLFOWN(*CURUSRPRF)
OVRSCOPE(*JOB) OUTQ(MyOutQ)
QUOTE RCMD OVRPRTF QPRINT SPLFOWN(*CURUSRPRF) SPLFNAME(mydata) /*
OVRSCOPE(*JOB) */
Regards, Chuck
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.
midrange.com
