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/14 09:07] – [Engine Troubleshooting Q & A] 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 501: | Line 503: | ||
**Q.**The engine runs and the original spool fie is successfully copied to the archive out queue, yet the merged spool file disappears.\\ | **Q.**The engine runs and the original spool fie is successfully copied to the archive out queue, yet the merged spool file disappears.\\ | ||
- | **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' | + | **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 runs for several days later in error?\\ | + | **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. It is recommended that an engine be stopped and restarted weekly.\\ | + | **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. | * 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). | * 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). |
pub/workwithmergeengine.txt · Last modified: 2023/09/19 13:35 by kkramer