Differences

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

--- pub:workwithmergeengine [2021/09/13 20:37] – [Engine Troubleshooting Q & A] kkramer
+++ pub:workwithmergeengine [2023/09/19 13:35] (current) – [Detail Information] kkramer
@@ Line 25: / Line 25: @@
  Logging Status: *ON                                  Hold Archive Status: *ON
 =Select  3=Copy  4=Delete  5=View  7=Rename  8=Start 9=End  10=Thread 11=Group
+=Start (FMC0459)
              Opt Engine       Description                 Status
                  DCYTEST      DCY Test                    *NONE
@@ Line 106: / Line 106: @@
 **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 =====
@@ Line 200: / Line 202: @@
   * **Spool Attribute Value**: Value to use in the spool attribute test.
   * **Form App**: Form, check or form set to use in processing the spool file. Use F4 to select the form, check or form set from a list of these objects.
-  * **Resulting SpoolFile Name**: Optional spool file name for the *USERASCII output spool file. Since *USERASCII spool files can not be viewed through the greenscreen it can be helpful to give the *USERASCII spool file a name reflective of its contents.
+  * **Resulting SpoolFile Name**: The output PCL spooled file name from iDocs Engines is named “FMGLASER” reflective of its contents. You can specify a resulting spool file name here.  A new enhancement in iDOCS 8 (09/19/23) allows administrators to configure the iDocs Engine to use the originating spool file name as the output PCL spool file name's name. To configure the iDocs Engine to use the originating spool file’s name as the PCL’s spool file name use *SPLFNAME or *FILE as values in the Resulting SpoolFile Name field on the iDocs Engine line. See the below example where the first line in the iDocs Engine configuration below will use FMGLASER as the PCL File Name in the output. The second line in the iDocs Engine configuration will use the originating spool file’s name as the PCL File Name in the output.
+  {{:pub:idocs:splfname.png?600|}}
   * **Resulting Out Queue**: Outqueue to place the resulting *USERASCII spool file. This is the **electronic document**. Use F4 to specify the outqueue from a list.
@@ Line 501: / Line 504: @@
 **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't fix the problem, verify that the printer is HP4 compatible.
+**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't resolve the issue, verify that the printer is HP4 compatible.
-**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.\\ \\
+**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).