pub:workwithmergeengine
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
pub:workwithmergeengine [2021/09/13 18:41] – [Directory Entry] kkramer | pub:workwithmergeengine [2021/09/28 11:45] – [Options] kkramer | ||
---|---|---|---|
Line 25: | Line 25: | ||
| | ||
| | ||
- | | + | |
Opt Engine | Opt Engine | ||
| | ||
Line 106: | Line 106: | ||
**Note:** If the Thread Engine is used, an archive output queue must be specified. | **Note:** If the Thread Engine is used, an archive output queue must be specified. | ||
+ | === Option 18=Start (FMC0459) === | ||
+ | This is fundamentally identical to selecting with Option 8, but provides the ability to retain the originating spool file user attributes for the resulting output. | ||
===== Add / Maintain Merge Engine ===== | ===== Add / Maintain Merge Engine ===== | ||
Line 491: | Line 493: | ||
===== Engine Troubleshooting Q & A ===== | ===== Engine Troubleshooting Q & A ===== | ||
- | This user profile should also have an entry in the system | + | **Q.** When I submit the engine it prompts me for the job queue. What is this?\\ |
- | **ADDDIRE USRID(IDOCS LCLSYSTM) USRD('iDocs user profile' | + | **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 60 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.**The engine runs and the original spool fie is successfully copied | ||
+ | **A.** The writer may not be responding correctly. Follow these steps to fix the writer: end the writer, vary off the device, vary on the device with a reset, restart the writer. If this doesn' | ||
+ | |||
+ | **Q.** After the engine is submitted, it ends several days later in error?\\ | ||
+ | **A.** There could be numerous reasons why the engine has ended in error after successfully running without interruption. Most common is that the engine has been running for many weeks accumulating system resources and job structures. **It is recommended that an engine be stopped and restarted weekly.** Other specific causes:\\ | ||
+ | * 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 the backup definition. | ||
+ | * An engine will end abnormally if the job's message queue has filled up. This could be the case if the engine has been running for weeks. To remedy this type of abnormal end change the system value QJOBMSGQFL value to *WRAP. This will prevent the job queue from filling up. CHGSYSVAL SYSVAL(QJOBMSGQFL) VALUE(*WRAP). | ||
+ | * If the engine has been running for weeks, it could end abnormally if it exceeds the maximum printer output files that can be created per job. Support was added to V5R1M0 to allow a job to create up to 999,999 spooled files. To remedy this type of abnormal end change the IBM i system value QMAXSPLF value from the default value of 9999 to the maximum of 999999. CHGSYSVAL SYSVAL(QMAXSPLF) VALUE(999999). | ||
+ | * If the engine is processing a large volume of spool files there could be an abend due to 'QSPOOL job not closing'. Keeping spooled files with jobs allows job commands such as Work with Submitted Jobs (WRKSBMJOB) to work with the spooled files even after the job has ended. Detaching spooled files from jobs reduces the use of system resources by allowing job structures to be recycled when the job ends. The default for QSPLFACN is *KEEP. CHGSYSVAL SYSVAL(QSPLFACN) VALUE(*DETACH): When the job ends, the spooled files are detached from the job and the job is removed from the system. | ||
+ | |||
+ | Note: You must have *ALLOBJ and *SECADM special authorities to change system values. A change to the system value takes effect immediately; | ||
+ | |||
< | < |
pub/workwithmergeengine.txt · Last modified: 2023/09/19 13:35 by kkramer