You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
When you specify PRINT(*EXCLD), the records print in the from-file format. All<br />
character data is in the CCSID specified in the from-file field. For TOFILE(*PRINT)<br />
and PRINT(*COPIED) listings, and when the to-file is a print file, character data is<br />
in the CCSID specified in the to-file fields.<br />
Example:<br />
In this example, all records that are not copied (or excluded records) are printed:<br />
CPYF FROMFILE(DKTIN) TOFILE(LIB1/PF) +<br />
MBROPT(*ADD) INCCHAR(*RCD 80 *EQ X) +<br />
PRINT(*EXCLD)<br />
The records print in character format.<br />
Creating an unformatted print listing<br />
If you want an unformatted print listing or if the from-file records should be<br />
formatted using first-character forms control (CTLCHAR(*FCFC), you must specify<br />
a program-described printer device file name. This file name can be QSYSPRT or<br />
user-defined (instead of *PRINT).<br />
To format the from-file records using first-character forms control, specify<br />
CTLCHAR(*FCFC) on the Create Printer <strong>File</strong> (CRTPRTF), Change Printer <strong>File</strong><br />
(CHGPRTF), or Override Printer <strong>File</strong> (OVRPRTF) command.<br />
For copy commands where TOFILE(*PRINT) is specified with a PRINT parameter<br />
value of *COPIED, *EXCLD, or *ERROR (or any combination), the following limits<br />
apply:<br />
v The QSYSPRT file must be spooled [SPOOL(*YES)]<br />
v You must specify the QSYSPRT in the device file or on the OVRPRTF command,<br />
because separate print files open for each file requested.<br />
All records are copied to a single spooled file, and the data for each member or<br />
label identifier copied begins on a new print page.<br />
Copying between different database record formats (FMTOPT<br />
parameter)<br />
106 <strong>File</strong> <strong>Management</strong> V4R5<br />
(CPYF and CPYFRMQRYF commands)<br />
When you copy from a database file to a database file, you must use the FMTOPT<br />
parameter if the record formats are not identical or if the files are different types<br />
(source or data). If either file is a device file or inline data file, the FMTOPT<br />
parameter does not apply. The records are truncated or padded with blanks or<br />
zeros when record lengths are different. A message is sent if the records are<br />
truncated.<br />
For database files, when either FMTOPT(*CVTSRC) or FMTOPT(*NOCHK) is<br />
specified and the record data copied from any from-file record is not long enough<br />
to fill a to-file record, the extra bytes in the to-file record are set to a default value.<br />
If a default value other than *NULL is specified in the DDS (DFT keyword) for a<br />
field, that field is initialized to the specified default; otherwise, all numeric fields<br />
are initialized to zeros, all character fields are initialized to blanks, all date, time,
Change language