pub:ipdf
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
pub:ipdf [2019/08/08 15:29] – [Monitoring an OutQueue with iPDFMon] kkramer | pub:ipdf [2019/08/08 20:19] – [iPDFMon SBMJOB] kkramer | ||
---|---|---|---|
Line 125: | Line 125: | ||
===== Monitoring an OutQueue with iPDFMon ===== | ===== Monitoring an OutQueue with iPDFMon ===== | ||
- | For a product demonstration of how to use the iPDF Monitor use the link below: | + | For a product demonstration of how to use the iPDF Monitor |
< | < | ||
Line 157: | Line 157: | ||
* **Outqueue Name**: Enter the name of the output queue to be monitored. One instance of iPDFMon per outqueue. Don't run iPDFMon on outqueues monitored by iDocs, iMail, or iView engines, or any dataqueue process. | * **Outqueue Name**: Enter the name of the output queue to be monitored. One instance of iPDFMon per outqueue. Don't run iPDFMon on outqueues monitored by iDocs, iMail, or iView engines, or any dataqueue process. | ||
* **Outqueue Library**: Enter the library where the output queue resides. | * **Outqueue Library**: Enter the library where the output queue resides. | ||
- | * **Output PDF Path**: Path for the IFS or Network output should be directed. Note that you can specify a **remote networked directory** as the output path using the QNTC file system. QNTC is a function of IBM i/OS and is documented here: [[http://publib.boulder.ibm.com/infocenter/ | + | * **Output PDF Path**: Path for the IFS or Network output should be directed. Note that you can specify a **remote networked directory** as the output path using the QNTC file system. QNTC is a function of IBM i/OS and is documented here: [[https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/rzahg/welcome.htm|IBM Knowledge Center]] |
* **DataQueue Name**: Specify a unique library/ | * **DataQueue Name**: Specify a unique library/ | ||
* **DataQueue Library**: Specify the Data Queue library to be used. | * **DataQueue Library**: Specify the Data Queue library to be used. | ||
Line 180: | Line 180: | ||
SBMJOB < | SBMJOB < | ||
- | CMD(IPDFMON OUTQ(QPRINT) OUTQLIB(QGPL) OUTPATH('/ | + | CMD(IPDFMON OUTQ(HANDOFF) OUTQLIB(OFERRER) OUTPATH('/ |
- | JOB(INVOICES)< | + | JOB(IPDFMONTQ)< |
LOG(0 0 *NOLIST) LOGCLPGM(*NO)< | LOG(0 0 *NOLIST) LOGCLPGM(*NO)< | ||
< | < | ||
- | This invocation monitors outqueue | + | This invocation monitors outqueue |
- | This invocation creates dataqueue | + | This invocation creates dataqueue |
- | All *SCS and *USERASCII spool files are converted to PDF and saved into the /home/files directory in the IFS. < | + | All *SCS and *USERASCII spool files are converted to PDF and saved into the /iview/dantest |
- | All file names are prefixed with ACCTG.< | + | All file names are prefixed with YOURNEWPDF.< |
No logging is done.< | No logging is done.< | ||
- | The statement | + | The JOB(IPDFMONTQ) names the batch job, names it IPDFMONTQ |
- | Note that iPDFMON does not archive or delete spool files from the monitored outqueue. It leaves them there.< | ||
Note that iPDFMON distinguishes between *SCS and *USERASCII spool files and invokes the correct conversion. | Note that iPDFMON distinguishes between *SCS and *USERASCII spool files and invokes the correct conversion. | ||
Also Note:< | Also Note:< | ||
- | You may have as many jobs of iPDFMOn | + | You may have as many jobs of iPDFMon |
You can only have 1 instance of iPDFMon attached to an outqueue, but you may have an unlimited number of instances outputting to a particular directory.< | You can only have 1 instance of iPDFMon attached to an outqueue, but you may have an unlimited number of instances outputting to a particular directory.< | ||
iPDFMon creates a data queue and attaches the dataqueue to the outqueue. < | iPDFMon creates a data queue and attaches the dataqueue to the outqueue. < |
pub/ipdf.txt · Last modified: 2022/06/25 17:02 by 127.0.0.1