pub:fmc0459
Differences
This shows you the differences between two versions of the page.
— | pub:fmc0459 [2022/06/25 17:02] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | < | ||
+ | |||
+ | ====== FMC0459 - TFPRTAPI Engine ====== | ||
+ | |||
+ | FMC0459 operates by invoking all merges through the TFPRTAPI command. | ||
+ | There are additional options relating to the user profile under which the processing | ||
+ | occurs given below. | ||
+ | |||
+ | The unusual feature of this engine is the option to process under the userid of | ||
+ | the input spool file. The output of the engine is thus owned by this user profile. | ||
+ | |||
+ | To invoke, prompt the command FMC0459 and complete the parameters as follows: | ||
+ | |||
+ | < | ||
+ | Launch TFPRTAPI Engine (FMC0459) | ||
+ | | ||
+ | Type choices, press Enter. | ||
+ | | ||
+ | Name of iDocs Dtaq Engine | ||
+ | User Profile Process Option | ||
+ | | ||
+ | Job Queue Library | ||
+ | Jobq to Launch Engine | ||
+ | | ||
+ | | ||
+ | | ||
+ | </ | ||
+ | |||
+ | |||
+ | * **Name of iDocs Dtaq Engine **: FMC0459 uses a [[workwithmergeengine# | ||
+ | * **User Profile Process Option**: ***NONE** to process all jobs under the user profile running the engine. Specify ***SPLFOWNER** to process the jobs under the spool file owner userid. Caution - this userid must have adequate authority to all the products that the engine will invoke. Use of this option will cause the output of the process to be owned by the input spool file owner. | ||
+ | | ||
+ | * **Job Queue Library**: library containing the single threaded job queue. | ||
+ | * **Jobq to Launch Engine**: Job queue into which to launch the main engine process. Normally this would be FMGJOBQ. | ||
+ | * **Engine Jobq Library**: Library containing the engine job queue. | ||
+ | * **Profile To Run Engine**: User profile to run engine. Should have good authority. | ||
+ | * **Produce Merge JobLog**: Normally set to ***NO**. If using a single threaded job queue set to ***YES** | ||
+ | during setup to trap problems. *YES will produce a separate job log spool file for each merge job. | ||
+ | |||
+ | ---- | ||
+ | |||
+ | < | ||
+ | |||