|
A third option might be to use a BINARY mode FTP with the PUTwith
subcommand being used send the file data to a Printer File defined
the attributes noted in the override used in the above example of how
the second option was coded; or the PrtF perhaps similarly overridden
with the proper scoping to effect those attributes.
As coded, both the cat utility [per -c] and the Rfile utility [per
-b] are being told to treat the data as binary. Those should be ableto
be tested together or separately, and if spooling then verified using
DEVTYPE(*SCS) to allow Display Spool File (DSPSPLF) or Copy SpoolFile
(CPYSPLF) to verify the content on the IBM i rather than deferring to
the recipient [e.g. the printer] to interpret the content.
What release? TR? Cumulative? I would first test separately,the
results of both the 'cat -c' and the 'Rfile -b' to verify thoseswitches
for those utilities perform as expected.
FWiW the usage shown quoted above seems quite near identical tothe
2nd Rfile example shown in the "Rfile - Read or write record files"instead
documentation, showing the /same/ activity for a .PS file type
of .PDF:<http://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzahz/rzahzrfile.htm>
"...
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.