Known Issues
FORMagic/400 Forms Overlay Manager, V3 and V4:
- When using the AutoMerge command FMGMRG01: Some non-conforming parameter values will cause escape messages. Be certain that all values meet documented requirements, and that you have adequate authority for all operations, etc.
- See FMAGIC Library Cleanup below.
.
FORMagic/400 PDF File Creator and Forms Manager, V3 and V4:
- When using the PDF file command FMGPDF01: Some non-conforming parameter values will cause escape messages. Be certain that all values meet documented requirements, and that you have adequate authority for all operations, etc.
- See FMAGIC Library Cleanup below.
.
Other Versions of FORMagic Forms Overlay Manager: None
FontMagic/400 Font Manager, V3:
- When upgrading the AS/400 component: Upgrade installation will abort due to excessive message length. Fixed in version 3.2x.
- When using the MICF font: Character strings using the MICF font will not be placed on the page properly -or- erroneous characters may be printed on the page. Fixed in version 3.2x.
.
FontMagic/400 Font Manager, V4: None
ProSign/400 SignOn Display Manager, V3 and V4:
- Extended passwords: With OS/400 V5, IBM introduced extended password support (passwords greater than ten characters). No version of ProSign/400 is compatible with extended passwords.
- When using command PSGUPDDSP: Changes in OS/400 V5 also caused the command PSGUPDDSP to become inoperable in ProSign/400 versions 1 through 3. This issue has been eliminated in ProSign/400 v4.
.
- Other Products: None
FMAGIC Library Cleanup, V4:
- When upgrading from older versions, certain obsolete files may remain. These files occupy little space, but under certain conditions can cause commands FMGMRGxx and FMGPDFxx to fail with a MCH1202 decimal data error. Failure is only known to occur when the FMAGIC library precedes the QTEMP library in the library list. Either insure FMAGIC follows QTEMP, or perform this general file cleanup:
1. These files can always be deleted. They are created by OS/400 when files are restored. xx is any two numeric characters; the file text will be similar to that shown.FMFOLM00xx *FILE PF-DTA Old name FMFOLMST in FMAGIC owned by FMFSRC00xx *FILE PF-SRC Old name FMFSRC in FMAGIC owned by QP FORMSU00xx *FILE PF-DTA Old name FORMSUPLD in FMAGIC owned by FORMS00xx *FILE PF-DTA Old name FORMS in FMAGIC owned by QPG2. These files are obsolete or will be created if used again. Rename them by adding an X to the end. Keep them for a while, just in case. Then, if no issues arise, delete them.FMFPRMST *FILE PF-DTA FORMagic/400 Profile Master File FMSWPRF *FILE DSPF FORMagic/400 Work With Profiles Displ FMSWPR2 *FILE DSPF FORMagic/400 Work With Profiles Trans FMFPRTPRF *FILE PRTF FORMagic/400 AutoMerge Printer File FMFSPLTST *FILE PF-DTA FORMagic/400 AutoMerge Test File PCFSAVEF *FILE SAVF FMAGIC Installation Save File PCFWORKF *FILE PF-DTA FMAGIC Work File3. This file is the actual cause of the MCH1202 failure in the FMGMRGxx and FMGPDFxx commands. FMFSPL should be in QTEMP only. When it is found in FMAGIC (because FMAGIC is ahead of QTEMP), it does not contain the expected data and the MCH1202 occurs. Rename it by adding an X to the end. Rerun your job with QTEMP AFTER FMAGIC in the lib list. It should work. If so: Delete the renamed file. You can now use QTEMP either before OR after FMAGIC, but before is preferred.FMFSPL *FILE PF-DTA FORMagic/400 AutoMerge Work File