pub:idocsapi
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
pub:idocsapi [2022/08/25 19:17] – kkramer | pub:idocsapi [2025/03/10 19:15] (current) – [ICOMDBMAP] kkramer | ||
---|---|---|---|
Line 108: | Line 108: | ||
Charset: UTF-8 is default (F4 for options).\\ | Charset: UTF-8 is default (F4 for options).\\ | ||
[Enter] to execute. | [Enter] to execute. | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ===== ESENDFILE ===== | ||
+ | |||
+ | A new command ESENDFILE is introduced in iDocs 8.00 to send a DB2 file from AS/400 server to a remote AS400 server. | ||
+ | < | ||
+ | Send DB2 file to remote server (ESENDFILE) | ||
+ | | ||
+ | Type choices, press Enter. | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | iDocs lib name on remote servr | ||
+ | DB2 file on source system | ||
+ | | ||
+ | DB2 file on remote system | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | </ | ||
+ | |||
+ | **Parameters: | ||
+ | Remote hostname\\ | ||
+ | User ID \\ | ||
+ | Authentication Password \\ | ||
+ | iDocs lib name on remote server | ||
+ | DB2 file on source system library \\ | ||
+ | DB2 file on remote system library \\ | ||
+ | Overwrite file on remote server | ||
+ | Restore file on remote server | ||
+ | |||
+ | |||
+ | Command ESENDFILE will perform the following steps: | ||
+ | * Executes iDocs command CNVDB2XML to convert DB2 to a temporary .xml file on source server | ||
+ | * Sends this .xml file to remote server | ||
+ | * Calls remote command CNVXML2DB on remote server to restore .xml file to DB2 file. (The command CNVXML2DB is stored on ‘iDocs lib name on remote server’) | ||
+ | * User can input the name of DB2 file on remote server. | ||
+ | * User can overwrite existing data or append them into remote DB2 file | ||
---- | ---- | ||
Line 160: | Line 210: | ||
Result on SFTP Server: \\ | Result on SFTP Server: \\ | ||
{{: | {{: | ||
+ | |||
+ | ---- | ||
+ | ===== ICOMDBMAP ===== | ||
+ | |||
+ | To evoke the merge process of one, two, or three Database Mapped Form Application(s), | ||
+ | < | ||
+ | | ||
+ | | ||
+ | Type choices, press Enter. | ||
+ | | ||
+ | Main Application . . . . . . . . | ||
+ | | ||
+ | Third Application | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | </ | ||
+ | |||
+ | **Parameters: | ||
+ | |||
+ | **MAINAPP** = The first Form Application to be merged. | ||
+ | **SECONDAPP** = The second Form Application to be merged. | ||
+ | **THIRDAPP** = The Third Form Application to be merged. | ||
+ | **OUTQ** = This will be the value for the destination of the output into an out queue or the triggering for Smart Routing by using *FORMDEF as the value. \\ | ||
+ | |||
+ | |||
+ | **Example: | ||
+ | < | ||
+ | | ||
+ | | ||
+ | Type choices, press Enter. | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | Job name . . . . . . . . . . . . | ||
+ | Job description | ||
+ | | ||
+ | Job queue . . . . . . . . . . . | ||
+ | | ||
+ | Job priority (on JOBQ) . . . . . | ||
+ | | ||
+ | Print device . . . . . . . . . . | ||
+ | | ||
+ | More... | ||
+ | | ||
+ | | ||
+ | </ | ||
+ | |||
+ | **NOTE: ** | ||
+ | (iDOCS 8.0 02/26/2025) With this enhancement you can control the aggregation sequence of merging multiple spool files. | ||
+ | * If the newly added IFDSPLDESC Data Area is set to ‘Y’, the aggregation process is identical to the older (pre-V8.0) logic merging multiple spool files in descending order. | ||
+ | * If the IFDSPLDESC Data Area is set to blank (default) or ‘N’, the aggregation process will merge the spool files in ascending order. | ||
+ | |||
---- | ---- | ||
Line 362: | Line 484: | ||
| | ||
</ | </ | ||
- | + | **Parameters: | |
- | **Path to PDF file:** This is the location where the PDF file is located on the IFS. It is also the location where the PDF file will be placed after being processed. | + | **Path to PDF file:** This is the location where the PDF file is located on the IFS. It is also the location where the PDF file will be placed after being processed. |
- | **' | + | **' |
- | **' | + | **' |
+ | |||
+ | **How the command works: | ||
+ | {{: | ||
- | How the command works:\\ | ||
- | See the example table below for the different configuration options and the expected results.\\ | ||
//User Password// will restrict the PDF to be open with the //User Password// value and will restrict the PDF’s security.\\ | //User Password// will restrict the PDF to be open with the //User Password// value and will restrict the PDF’s security.\\ | ||
//Owner Password// will restrict the PDF to be open with the //Owner Password// value and will NOT restrict the PDF’s security.\\ | //Owner Password// will restrict the PDF to be open with the //Owner Password// value and will NOT restrict the PDF’s security.\\ | ||
When both //User Password// and //Owner Password// are used both options will apply. | When both //User Password// and //Owner Password// are used both options will apply. | ||
- | + | See the example table below for the different configuration options and the expected results.\\ | |
- | Results: \\ | + | Example Table: \\ |
{{: | {{: | ||
+ | {{: | ||
- | NOTE:\\ | + | **NOTE:**\\ |
Need to install IFDJAVA.JAR file as of 08/12/2022 \\ | Need to install IFDJAVA.JAR file as of 08/12/2022 \\ | ||
- | API must be registered for use. | + | The SETPDFPWD |
===== SPLCOMBINE ===== | ===== SPLCOMBINE ===== |
pub/idocsapi.1661480260.txt.gz · Last modified: 2022/08/25 19:17 by kkramer