inFORM Decisions Information Portal

User Tools

Site Tools

Trace:
pub:idocsapi

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
pub:idocsapi [2020/01/22 08:35] – [IFDUPSPLF] kkramerpub:idocsapi [2021/01/25 11:27] – [iDocs Programming API] kkramer
Line 3: Line 3:
  
  
-====== iDocs Programming API ======+====== iDocs Programming API's ======
  
 iDocs has various methods to automatically print forms that are deposited in output queues.  There are two different types of form overlay engines which are the processors that automatically search defined output queues for spooled files to merge with form applications or form sets.  iDocs also provides api's that can be embedded into a job stream that executes the merge for defined print jobs.  The simplest is TFPRT which is intended to be embedded in the job stream following the program that produced the spool file to be processed.  With the more complex TRPRTAPI api, you can provide the necessary parameters to process any spool file on the system.    iDocs has various methods to automatically print forms that are deposited in output queues.  There are two different types of form overlay engines which are the processors that automatically search defined output queues for spooled files to merge with form applications or form sets.  iDocs also provides api's that can be embedded into a job stream that executes the merge for defined print jobs.  The simplest is TFPRT which is intended to be embedded in the job stream following the program that produced the spool file to be processed.  With the more complex TRPRTAPI api, you can provide the necessary parameters to process any spool file on the system.   
Line 102: Line 102:
 </pre></html> </pre></html>
  
-**Parameters:** +**Parameters:** 
-Spooled file: input spool file name +
-Spooled file number: input spool file number +
-Job name/User Name/ Job Number: job ID of input spool file +
  
-Output Queue/Library: name and library of output queue +Spooled file: input spool file name \\ 
-New SPLF user data: enter user data of output spool file (*SAME to retain the same attribute of input spool file) +Spooled file number: input spool file number \\ 
-New SPLF form type: enter form type of output spool file  (*SAME to retain the same attribute of input spool file) +Job name/User Name/ Job Number: job ID of input spool \\ 
-New SPLF name: enter spool file name of output spool file  (*SAME to retain the same attribute of input spool file + 
-Hold new SPLF: Hold the output spool file name +Output Queue/Library: name and library of output queue \\ 
-Page range: enter the range of pages of input spool file name+New SPLF user data: enter user data of output spool file (*SAME to retain the same attribute of input spool file) \\ 
 +New SPLF form type: enter form type of output spool file  (*SAME to retain the same attribute of input spool file)\\ 
 +New SPLF name: enter spool file name of output spool file  (*SAME to retain the same attribute of input spool file\\ 
 +Hold new SPLF: Hold the output spool file name\\ 
 +Page range: enter the range of pages of input spool file name\\
  
 **Example:** **Example:**
 +
 IFDUPSPLF FILE(INV) SPLNBR(2) JOB(106730/ANGUYEN/ANGUYENA) OWNER(OFERRER) IFDUPSPLF FILE(INV) SPLNBR(2) JOB(106730/ANGUYEN/ANGUYENA) OWNER(OFERRER)
  
pub/idocsapi.txt · Last modified: 2023/07/25 13:08 by kkramer