This problem is due in part to some settings in the job description.

FMGLASER files are merged spool and overlay files. Some people might want to save them for archive purposes so they create an archive outqueue for this. This can work in conjuction with the automatic merge engine. So every time a form is merged it can be

Whenever this happenned, there might come from one of the following causes:

1. Printer problems - printer memory

2. Network problem -

3. Hold outq then release it again Move to different outq, hold and release it; then move it back then again

1. Clear library FMGCUST

2. To save mapped data, use OPTION 9 in the FORM DEFINITION MAINTENANCE screen. This step saves the data to library FMGCUST. NOTE: OPTION 9 does not appear on the menu screen.

3. Add library FMGCUST to the top of the library list using command “addlible fmgcust”

4. Call to start program CUSTSAVE to save the library FMGCUST as a PC document file ‘FMGSAVF’ in folder FORMFMG.

CALL PGM(FMG/CUSTSAVE)

5. Copy the file FMGSAVF from folder FORMFMG to a PC diskette or save to your computer to e-mail as an attachment

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If the above sequence of commands do not work, then the following should be done prior to the steps above.

1. CRTLIB FMGSAVF 2. CRTLIB LIB(FMGSAVF)TEXT('Application Save library') 3. CRTSAVF FILE(FMGSAVF/SAVED) 4. CRTPF FILE(FMGSAVF/FMGSAVF) RCDLEN(528)OPTION(*NOSRC *NOLIST)

In the Form Definition Maintenance setup, 1st overlay is set to the name of the mac overlay file, Seq#=““1””, Drawer=““1””, Merge=““Y””, Form Prompt=““*STD””. The 2nd overlay=““*NONE””, everything else is as same as 1st overlay settings.

If you added or deleted or moved fields in your OFM make sure those changes are reflected in your datamap screen. In some cases if fields are deleted or new ones are added, it could shift the field map numbers and cause mismapping. If you get strange printouts after uploading a new macro and field file, try regenerating the FLD and MAC file and reupload them.

On your AS/400 do a DSPDTAARA DSU300 (display data area for DSU300). If the value is set to 'N' change it to 'Y' by doing a CHGDTAARA DSU300 (change data area dsu300) and entering Y for new value.

Please check your sort options in the data map field. Even numbers 1,3,5 are ascending. 2,4,6 are desceding. If you don't want sort to be enabled do not enter anything for the sort option.

Make sure to generate the *PRN & *MAC files with rasterized graphic by setup printer graphics in RASTERIZE mode, instead of VECTORIZE or AUTOMATIC mode. Also make sure insert graphics using Graphic icon not Fill Graphic icon in the tool bar (with Scale Proportionally option).

When create *mac file from *ofm file for your form, make sure your printer properties are set to have send graphics as raster not vector (usually by default). Your PDF view (Acrobat Reader Viewer) should be the latest version 3.1, 4.0 or higher. You will have problem viewing lines and text boxes with Acrobat Reader View version 3.0 and lower which doesn't show lines, text boxes as printed even it was rasterized graphic overlay

Either the user profile that initiated the merge does not have *SPLCTL as one of their authorities, or the OUTQ attribute AUTCHK is not set to *DTAAUT.

If problem continues issue these commands to insure that data prints to the overlay.

CHGPF FILE(FMG/CXPOUTX) FRCRATIO(1)
CHGPF FILE(FMG/CXPOUT3) FRCRATIO(1)
CHGPF FILE(FMG/CXP0128) FRCRATIO(1)
CHGPF FILE(FMG/CXP0132) FRCRATIO(1)

1. Update to the new version of the software using the CD and the normal update instructions.

2. Go to the FMG menu and select work with engine definitions. View all of the outstanding definitions, take note of the data queue names and libraries.

3. Go to the command line and delete these data queues as shown below: DLTDTAQ DTAQ(FMG/FMGDTAQ)

4. Recreate the data queues using the command below:

CRTDTAQ DTAQ(FMG/FMGDTAQ) MAXLEN(256)

First, a queue is just another name for a line. Like a line of people waiting in a bank for an open teller, the engine waits in line for an open entry in a memory subsystem.

Submit the engine to the associated jobQ —> FMGJOBQ

The answer is YES.

There are three types of engine options available. They are:

The Polling Engine - searches outq on a pre-defined interval for defined spool files A polling engine proactively inspects all spool files in a defined output queue at a predetermined interval of every sixty seconds. The interval can be modified depending on print job inter-activity.

The Data Queue Engine -triggered to execute merge when spool file hits outq. A dataqueue engine reacts to a new spool file in the originating output queue only when the spool file meets specified form type criteria in the engine definition. If the defined criterion is met, then the spool file is processed. If the criterion is not met, then the spool file is not re-inspected. In most print environments, data queue engines will conserve system resources.

In one circumstance would you need to define and run more than one engine. In the instance where you need to have multiple archive out queues for security purposes would you need to define more than an single engine definition. In a future release, inFORM Decisions will enable multiple archive out queues for a single definition.

In this case, the engine had been submitted to a single thread job queue that can only process a single job at a time rather than multiple jobs. While continuously processing the current job the next job in the queue never gets an open opportunity to be processed in the subsystem. The solution to this bottleneck is to submit the engine to a multi thread job queue. The AS/400 system comes pre-configured with several multi thread job queues, such as QS36EVOKE. Use one of these job queues.

The engine name more than likely has an embedded space in the name. Simply rename the engine definition to exclude any embedded spaces and resubmit the engine.

Print Immediate- Command embedded in job stream executes the merge for defined print jobs.

[ Questions and Answers Main Page ]