System i: Programming Message Handling APIs - IBM
System i: Programming Message Handling APIs - IBM
System i: Programming Message Handling APIs - IBM
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
*PRINT Resets the job so the job log is written to a spooled file rather than an output file. When this<br />
special value is used the remaining parameters on this API are ignored.<br />
The API does not allow the primary file specification to be overridden by the use of the Override<br />
Database File (OVRDBF) command. The primary file also cannot be overridden at job log production<br />
time. The file object determined to be the primary file used by this API is the one used at job log<br />
production time. If the file does not exist at job log production time, the job log is redirected to a spooled<br />
file.<br />
The primary file must be a local physical file; it cannot be a DDM file.<br />
Qualified secondary file name. The name of the file into which the secondary job log information is<br />
written. The parameter consists of two parts. The first 10 positions to contain the file name and the<br />
second 10 positions contain the library name. A library name can be provided or the special values<br />
*CURLIB and *LIBL can be used. QTEMP cannot be used for the library name.<br />
If an output file by the specified name does not exist when the API is called, one is created by that name<br />
in the specified library. If the library was specified as *LIBL, the file is created in the current library. If<br />
*LIBL or *CURLIB was specified and there is no current library, the file is created in QGPL. The file<br />
attributes MAXRCDS and MAXMBRS are set to *NOMAX.<br />
The following special value can be used in this field:<br />
*NONE No secondary file is provided. This special value prevents the generation of the secondary job log<br />
information. When this special value is used, the secondary library and member names are<br />
ignored.<br />
The API does not allow the secondary file specification to be overridden by the use of the OVRDBF<br />
command. The secondary file also cannot be overridden at job log production time. The file object<br />
determined to be the secondary file by this API is used at job log production time. If the file does not<br />
exist at job log production time, the job log automatically redirects to a spooled file.<br />
The secondary file must be a local physical file; it cannot be a DDM file.<br />
Reserved. This field must be set to binary zeros.<br />
Secondary file member name. The name of the member within the secondary file used for the secondary<br />
job log information.<br />
If a member of the specified name does not exist, a member by that name is added to the secondary file.<br />
If a member by the specified name does exist, the member is cleared if the Member replace option field<br />
of this structure specifies replace. Otherwise, the member is not cleared. At job log production time, new<br />
records are added to the member and any existing records are left unchanged.<br />
The following special value can be used in this field:<br />
*FIRST The first member in the file receives the output. If a member does not exist, one is created with<br />
the same name as the file name.<br />
CCSID Considerations<br />
CCSID conversion is allowed on any field in the primary file with the exception of the field QMHMDT,<br />
which contains the message data or immediate message text. The QMHMDT field is defined with a<br />
<strong>Message</strong> <strong>Handling</strong> <strong>APIs</strong> 11