Differences

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

--- pub:workwithmergeengine [2020/04/21 18:26] – [Aggregation options] kkramer
+++ pub:workwithmergeengine [2021/09/13 19:12] – R kkramer
@@ Line 288: / Line 288: @@
 </pre></html>
- In the Aggregate Setting screen shown above, the user can either specify a custom program (IDOCS 6.95) to handle the business logic of Aggregation or define “Sweep the outputs when”. The custom program will override the definition in “Sweep the outputs when”.
+ In the Aggregate Setting screen shown above, the user can either specify a custom program (IDOCS 6.95) to handle the business logic of Aggregation __or__ define “Sweep the outputs when”. The custom program will override the definition in “Sweep the outputs when”.
-**F13** will assist the user in creating a CL program along with the parameters that the iDocs engine will utilize when calling the the custom program.
+**F13** will assist the user in creating a program along with the parameters that the iDocs engine will utilize when calling the the custom program. A sample CL program is shown below.
+<html><pre>
+/*¹iDocs sample user program for Aggregate engine·                             +
+  ¹Once this program is specified in iDocs aggregate engine,                   +
+  ¹iDocs will call it to check if the aggregate criteria is matched or not,    +
+  ¹if TRUE then &RETURN is 'Y' else &RETURN is blank.                          +
+  ¹                                                                            +
+  ¹Input parameters:                                                           +
+  ¹  - &SPLNAME : SCS spool file name which is being processed by iDocs engine +
+  ¹  - &SPLNBR  : SCS spool file number                                        +
+  ¹  - &JOBNAM  : SCS spool file job name                                      +
+  ¹  - &JOBUSR  : SCS spool file job user                                      +
+  ¹  - &JOBNBR  : SCS spool file job number                                    +
+  ¹                                                                            +
+  ¹Output parameters:                                                          +
+  ¹  - &RETURN  : If this parameter is Y then iDocs will complete the group    +
+ ¹                and aggregate all PCLs in group into 1 PCL                   +
+*/
+             PGM        PARM(&SPLNAME &SPLNBR &JOBNAME &JOBUSER +
+                          &JOBNBR &RETURN)
+             DCL        VAR(&SPLNAME) TYPE(*CHAR) LEN(10)
+             DCL        VAR(&SPLNBR) TYPE(*DEC) LEN(6 0)
+             DCL        VAR(&JOBNAME) TYPE(*CHAR) LEN(10)
+             DCL        VAR(&JOBUSER) TYPE(*CHAR) LEN(10)
+             DCL        VAR(&JOBNBR) TYPE(*CHAR) LEN(6)
+             DCL        VAR(&RETURN) TYPE(*CHAR) LEN(1)
+/*¹If &RETURN is 'Y' then it's end of the spool files group, +
+¹  and iDocs will aggregate the PCL files into 1 PCL·*/
+             ENDPGM
+</pre></html>
 ===== Daisy Chaining Engines  =====
@@ Line 379: / Line 412: @@
   * The **FMGBATCH** subsystem can be created from menu FMGUTILITY, option 1. The default configuration is limited and the configuration should be reviewed by a qualified system administrator.
   * **Never call** the iDocs engine from the startup program, instead submit it with SBMJOB. If you call it the startup program will never progress beyond the call statement and thus never complete. Additionally CALLing the engine will cause it to run under the user profile running the startup program (user QSYS) which causes problems. iDocs engines will run in any properly configured batch subsystem.
-  * Program **FMC0462** is a dataqueue engine; use **FMC0460** for a polling engine. (**FRM0471** ends either one).
+  * Program **FMC0462** is a data queue engine; use **FMC0460** for a polling engine. (**FMR0471** ends either one).
   * The **one parameter** to the FMC0462 or FMC0460 call should be the name of the engine in upper case.
   * The **job name** should be the engine name in upper case.
@@ Line 456: / Line 489: @@
  <html><br/></html>
+===== Engine Troubleshooting Q & A =====
+**Q.** When I submit the engine it prompts me for the job queue. What is this?\\
+**A.** A job queue is an IBM i object that contains entries for jobs that are waiting to be processed by the system.
+**Q.** When I submit the engine it runs normally, but afterwards no one else can process their jobs submitted to batch?\\
+**A.** In this case the engine has been submitted to a single thread job queue that can only process a single job at a time. The solution to this bottleneck is to submit the engine to a multi thread job queue. Create one or use a pre-configured multi thread job queue such as QS36EVOKE.
+**Q.** Polling Engine starts for 660 seconds and ends normally without processing any entries?\\
+**A.** Check each originating output queue and insure that they all still exist on the system.
+**Q.** After the engine is submitted, it runs for several days later in error?\\
+**A.** There could be numerous reasons why the engine has ended in error after successfully running without interruption.\\
+A lock on the engine record has occurred from a backup routine. Its best to make a single backup of the iDocs library whenever the definitions have been added or altered and set it aside. then remove the iDocs library from any daily, weekly or monthly backup definitions.
+ <html><br/></html>
 ----