Differences

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

--- pub:idocsapi [2022/08/25 19:22] – [SETPDFPWD] kkramer
+++ pub:idocsapi [2023/07/25 13:08] (current) – [ESENDFILE] kkramer
@@ Line 108: / Line 108: @@
 Charset: UTF-8 is default (F4 for options).\\
 [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.
+<html><pre>
+                   Send DB2 file to remote server (ESENDFILE)
+ Type choices, press Enter.
+ Remote hostname  . . . . . . . .   '172.16.1.55'
+ Username . . . . . . . . . . . .   USER
+ Password . . . . . . . . . . . .   password
+ iDocs lib name on remote servr     IDOCS800      Character value
+ DB2 file on source system  . . .   FRMTMULH      Name
+   Library  . . . . . . . . . . .     IDOCS6B     Name, *CURLIB
+ DB2 file on remote system  . . .   TESTCSV1      Name
+   Library  . . . . . . . . . . .     USERLIB     Name, *CURLIB
+ Overwrite file on remote servr     *NO           *YES, *NO, *YES, *NO
+ Restore file on remote server  .   *YES          *YES, *NO, *YES, *NO
+                                                                         Bottom
+ F3=Exit   F4=Prompt   F5=Refresh   F12=Cancel   F13=How to use this display
+ F24=More keys
+</pre></html>
+**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  (*YES/*NO) \\
+Restore file on remote server  (*YES/*NO) \\
+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: \\
 {{:pub:idocs:esndfile001.png?600|}}
+----
+===== ICOMDBMAP =====
+To evoke the merge process of one, two, or three Database Mapped Form Application(s), and aggregate the output to a desired out queue or trigger Smart Routing settings. The ICOMDBMAP command can be used interactively or submitted into a job (SEE EXAMPLE BELOW). (Added iDOCS 8.0 05/10/2023)
+<html><pre>
+                   Combine database map-File name (ICOMDBMAP)
+ Type choices, press Enter.
+ Main Application . . . . . . . .                 Name
+ Second Application . . . . . . .   *NONE         Name *NONE
+ Third Application  . . . . . . .                 NAME *NONE
+ Output Queue . . . . . . . . . .                 Name
+                                                                         Bottom
+ F3=Exit   F4=Prompt   F5=Refresh   F12=Cancel   F13=How to use this display
+ F24=More keys
+</pre></html>
+**Parameters:**
+**MAINAPP** = The first Form Application to be merged.  This Form Application will determine the output for all the Form Applications being used if using Smart Routing settings. \\
+**SECONDAPP** = The second Form Application to be merged.  If not using a second Form Application, then use *NONE as the value.\\
+**THIRDAPP** = The Third Form Application to be merged.  If not using a second Form Application, then use *NONE as the value.\\
+**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:**
+<html><pre>
+                               Submit Job (SBMJOB)
+ Type choices, press Enter.
+ Command to run . . . . . . . . .   ICOMDBMAP MAINAPP(CYBERLTR) SECONDAPP(*NONE)
+ THIRDAPP(*NONE) OUTQ(*FORMDEF)
+                                                                     ...
+ Job name . . . . . . . . . . . .   ICOMDBTEST    Name, *JOBD
+ Job description  . . . . . . . .   *USRPRF       Name, *USRPRF
+   Library  . . . . . . . . . . .                 Name, *LIBL, *CURLIB
+ Job queue  . . . . . . . . . . .   FMGJOBQ       Name, *JOBD
+   Library  . . . . . . . . . . .                 Name, *LIBL, *CURLIB
+ Job priority (on JOBQ) . . . . .   *JOBD         1-9, *JOBD
+ Output priority (on OUTQ)  . . .   *JOBD         1-9, *JOBD
+ Print device . . . . . . . . . .   *CURRENT      Name, *CURRENT, *USRPRF...
+                                                                        More...
+ F3=Exit   F4=Prompt   F5=Refresh   F10=Additional parameters   F12=Cancel
+ F13=How to use this display        F24=More keys
+ </pre></html>
 ----
@@ Line 362: / Line 479: @@
  F24=More keys
 </pre></html>
+**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.  The PDF file will retain the original file name.\\
 **'User Password:'** This parameter will set the User Password.\\
 **'Owner Password:'** This parameter will set the Owner Password.\\
-How the command works:\\
+**How the command works:**\\
-See the example table below for the different configuration options and the expected results.\\
+{{:pub:idocs:setpdfpwd_Password.jpg?600|}}
 //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.\\
 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.\\
 Example Table: \\
 {{:pub:idocs:setpdfpwd_results.jpg?600|}}
+{{:pub:idocs:setpdfpwd_Security.jpg?600|}}
-NOTE:\\
+**NOTE:**\\
 Need to install IFDJAVA.JAR file as of 08/12/2022 \\
 The SETPDFPWD API must be registered for use.