Differences

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

--- pub:iview8be [2018/09/06 10:21] – [Select an iView Archive Application with option 1:] kkramer
+++ pub:iview8be [2025/10/09 12:31] (current) – [Menu IVIEW, option 10:iView Servers (Engines)] kkramer
@@ Line 260: / Line 260: @@
 <html><pre>
-/04/18                iView FTP Interface Definition               IV1100D7
+/04/25                iView FTP Interface Definition               IV1100D7
 :11:54                   Add/Maintain FTP Target                   KKRAMER
@@ Line 273: / Line 273: @@
    Directory:
-   System Type:              *UNIX, *AS400, *WINDOWS
+   System Type:              *UNIX, *AS400, *WINDOWS FTP Type:       *FTP, *SFTP
    AS/400 Namefmt Type:       0, 1
-   Log Lib/File:            /
+   Export Index File:        *TXT, CSV   Sep. Char    Include Field Name:    Y/N
-   Log Level:                *SUMMARY, *DETAIL, *NONE
+   FLD Separator:   Y/N One Line per Field   Y/N Include File Path:   Y/N
-   Job Queue:                Export Index File:       *YES *NO Sep. Char
+   Output To .ZIP file  Y/N  .ZIP Name                            *DEFAULT, Name
-   Include Field Name:   Y/N FLD Separator:   Y/N One Line per Field   Y/N
-   Include File Path:   Y/N
    Post FTP Cmd:
@@ Line 289: / Line 289: @@
   * **Directory**: Directory into which to upload the file.
   * **System Type**:  O/S type of remote system.
+  * **FTP Type**: FTP connections can be done using *FTP or *SFTP protocols.
   * **AS/400 Namefmt**: 0 for the DB2/400 file system and 1 for the Integrated File System format.
-  * **Log Lib/File**:  If logging specify a library and file name for a log file. This file must either be FTPLOG or a duplicate of it. If logging you must specify a log file and library.
+  * **Export Index File**: Export file for index field values can now the in *TXT and *CSV formats.
-  * **Log Level**:  Logging level. If *NONE the log file need not be entered. This logging is separate from iView engine logging, which is into the job log.
+  * **Sep. Char**:  Configure index field value separator for your Export Index File.
-  * **Job Queue**:  System i job queue. If entered iView will submit to this job queue all of the ftp commands and the Post FTP Command specified below it. If not specified it will simply run these commands as part of the archive engine job stream.
+  * **Include Field Name**:  Option to include or exclude the Index Field Name in the Export Index File.
-  * **Export Index File**: If *YES specified iView will create a text file containing the iView archive fields and their values for the document separated by a space, and will ftp this file to the same target with the archived document. The file name is the same as the archived document except that the file extension is **.txt**. This file is not retained on the System i.
+  * **FLD Separator**:  Option to include or exclude Field Separator.
+  * **One Line Per Field**:  Option to have a one line per field or multiple lines.
+  * **Include File Path**:  Option to include the PDF file’s path in the Export Index File.
+  * **Output To .ZIP file**:  Option to wrap the output being sent to the FTP site in a ZIP file.
+  * **.ZIP Name**: Option to use the *DEFAULT name or use a unique static name for the ZIP file.
   * **Post FTP Cmd**:  Optionally specify a command to execute upon completion of the ftp transactions. Remember that this job will have to manage its own library list.
+**Note:** 08/04/2025,  New options to control the maximum number of files per ZIP file, and interval time to ZIP up files to send to the FTP site.
+Below are the new Data Areas to control these values for the enhancements of iView FTP settings.
+on.
+**WRKDTAARA IVIEWLOOP**
+IVIEWLOOP	Used to configure the maximum number of files to be processed with iView's FTP ZIP file option.
+**WRKDTAARA IVIEWINTV**
+IVIEWINTV	Used to set the interval parameters to close a ZIP file with iView's FTP ZIP file option.
+The logic for how these two parameters work the iView Application’s FTP:
+  *	The engine then checks the two parameters: IVIEWINTV and IVIEWLOOP.
+  *	Example: if IVIEWINTV = 3, then one interval is 3 minutes.
+  *	If IVIEWLOOP = 5, this means the system will count the number of merge operations.
+  *	If the number of merges ≥ IVIEWLOOP, the engine will create the ZIP file and send it via FTP.
+  *	If the number of merges is < IVIEWLOOP (e.g., only 4 merges), but the elapsed time has already exceeded the interval (3 minutes in this example), the engine will still create the ZIP file and send it.
@@ Line 378: / Line 401: @@
   * **6**: Reprocess
-==== Menu IVIEW, option 10:====
+==== Menu IVIEW, option 10:iView Servers (Engines) ====
- Work with iView Servers
+iView servers are defined from menu IVIEW, option 10.
+iView engines are architected similarly to iDocs engines in that they are single threaded, and you can define and run an unlimited number of them in any subsystem.
+  * **1**: Select
+  * **2**: Copy
+  * **4**: Delete
+  * **7**: Rename
+  * **8**: Start Server
+  * **9**: End Server
 <html><pre>
-/05/18                          iView                              IV2000C1
+/30/18                          iView                              IV2000C1
-:42:56                      Engine Maintenance                     KKRAMER
+:38:24                      Engine Maintenance                     KKRAMER
  Type options, press Enter.
@@ Line 405: / Line 436: @@
   F3=Exit   F5=Refresh   F6=Add
 </pre></html>
-  * **1**: Select
+Select the appropriate engine with option 1:
-  * **2**: Copy
+<html><pre>
-  * **4**: Delete
+/30/18                          iView                              IV2000C2
-  * **7**: Rename
+:39:58                    Engine Maintenance                       KKRAMER
-  * **8**: Start Server
-  * **9**: End Server
+ Edit Engine . . . . . . . . . : BOYDIVWENG Boyd Check iView Engine
+ Spool File Endpoint . . . . . : OFERRER    / ARCHIVIEW  Name
+ Data Queue. . . . . . . . . . : QUSRSYS    / BOYDIVWDTQ
+ Engine processing log : N Y/N
+ Process SPLF in Separate Job: N Y/N
+   Job Queue / Library:            / *LIBL       Job Priority: *JOBD
+    AND   ----- Originating -----   Spool        Spool        Archive
+    OR    Library      Queue Name   Attribute    Value        Application
+          OFERRER      ARCHIVE2     *SPLFILE     AP290A#      BOYDCHECK
+                                                                        More...
+  F3=Exit   F10=Save   F12=Cancel
+</pre></html>
+  * **Archive Original Spool File To**: This is the endpoint for the original spool file.
+  * ** Data Queue**: Provide a name and library for the engine's data queue. This must be unique. The engine will create it if it is not present at engine startup. A data queue is a filesystem object.
+  * **Originating Outqueue and Library**: This is the monitored output queue. Note that you can not have multiple data queue engines monitoring one output queue. A **9/26/25 enhancement** allows the iView Engine to also perform like a Polling Engine. When a spool file is already in the originating out queue that is being monitored by the iView Engine in RDY (Ready) status, the spool file will be picked up automatically and processed by the iView Engine without having to refresh (Hold/Release) the spool file. \\ This field determines whether the engine will operate as a Polling or Data Queue Engine.
+      * To use the iView Engine as a **Data Queue Engine**, insert a value in the Data Queue Fields for Library and Data Queue.
+      * To use the iView Engine as a **Polling Engine**, leave the values for the Data Queue Fields blank.
+  * **Spool Attribute**: Specify the external spool file attribute to test to recognize the spool file and select the correct archive application. Specify one of:
+| *FORM    |   Original Spool Form Type   |
+| *USRPRF  |   User Profile of Spool      |
+| *JOBNAME |   Job Name of the Spool      |
+| *SPLFILE |   Print File Name            |
+| *USRDTA  |   User data Value in Spool   |
+  * **Spool Value**: Specify the specific value to test the selected external spool file attribute against.
+  * **Archive Application**: Prompt for and select the archive application to process the spool file for which the specified external spool file attribute matches the provided value.
+You can have an unlimited number of engines in iView. You may define up to 9,999 engines in this dialog.
+Use option 8 and 9 to start and stop the engines:
+<html><pre>
+                         Start iView Server (STRIVWSRV)
+ Type choices, press Enter.
+ iView Server Name  . . . . . . . > IVIEWSEVER    Value, or F4 for list
+ User . . . . . . . . . . . . . .   *CURRENT      Name, IVIEW, *CURRENT
+ Job queue  . . . . . . . . . . .   *JOBD         Name, *JOBD
+ Save job log . . . . . . . . . .   *NO           *YES, *NO
+                                                                         Bottom
+ F3=Exit   F4=Prompt   F5=Refresh   F12=Cancel   F13=How to use this display
+ F24=More keys
+</pre></html>
+  * **User**: user profile to run the engine. This profile must have ***JOBCTL** and ***SPLCTL** authority, and if it is running iDocs merges must also have a profile define in the system directory.
+  * **Job Queue**: Job queue to which the engine is submitted. This can be any queue leading to a batch subsystem.
+  * **Save Job Log**: If you want the log saved, enter *YES. In normal production this would not be necessary.
 ===== Menu IVIEWADM: =====