User Tools

Site Tools


pub:workwithmergeengine

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
pub:workwithmergeengine [2020/04/22 10:03] – [Aggregation options] kkramerpub:workwithmergeengine [2021/04/27 10:04] – [Starting Engines at IPL] kkramer
Line 412: 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.   * 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.   * **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 **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.   * The **job name** should be the engine name in upper case.
pub/workwithmergeengine.txt · Last modified: 2023/09/19 13:35 by kkramer