This website is no longer being maintained.
Please see the latest information at our new site.


Problem Determination



  1. If you experience a problem when using FORMagic/400 AutoMerge, please follow these steps for diagnosing it:

    1. We are not aware of any bugs in command FMGMRG01. Every failure reported so far has involved parameter values which are invalid or which, as a practical matter, cannot be edited as well as we would like. Be very certain all of your parameter values meet documented requirements, IFS paths are valid, you have adequate authority for all operations, etc.
    2. CHGJOB LOG(4 00 *SECLVL) LOGCLPGM(*YES) and rerun the failing command. If it still fails, check the low level messages in the joblog. This may expose the true cause of the failure. Make any corrections and retry the failing command.
    3. Duplicate the spool file, using FMGMRG01 with defaults where possible, and with no forms. If a failure occurs, check the joblog carefully. Make any corrections and retry.
    4. Please call to discuss the problem before proceeding further. If we ask you to continue, please complete all steps below as a package.
    5. Try FMGMRG01 exactly as needed for your application.
    6. If there is a program dump, take the option for a formatted CL or Cobol dump and send it to us.
    7. Send us file QTEMP/FMFSPL, captured immediately after running FMGMRG01 which produces the failure.
    8. Send us the complete Joblog.
    9. Send us your CL program which calls FMGMRG01. If you are executing the command interactively, copy it from the screen into your email directly.
    10. Be sure to include the following information:

      • Which step above produces the failure.
      • Any description you can provide for the failure.
      • All requested files (CL, Joblog, FMFSPL, Dump). FTP them to a PC with ASCII translation. For FMFSPL and the Dump, FTP them a second time as binary files with no translation. ZIP all files into one zip file to insure what we receive is what you sent! We cannot analyze large files; each file you send should be no larger than 50k. Please test with small data samples, if necessary, to provide us with manageable file sizes.


  2. If you experience a problem when using FORMagic/400 PDF, please follow these steps for diagnosing it:

    1. We are not aware of any bugs in command FMGPDF01. Most failures reported so far have involved parameter values which are invalid or which, as a practical matter, cannot be edited as well as we would like. Be very certain all of your parameter values meet documented requirements, IFS paths are valid, you have adequate authority for all operations, etc.
    2. CHGJOB LOG(4 00 *SECLVL) LOGCLPGM(*YES) and rerun the failing command. If it still fails, check the low level messages in the joblog. This may expose the true cause of the failure. Make any corrections and retry the failing command.
    3. Create a PDF file, using FMGPDF01 with defaults where possible, and with no forms. If a failure occurs, check the joblog carefully. Make any corrections and retry.
    4. Please call to discuss the problem before proceeding further. If we ask you to continue, please complete all steps below as a package.
    5. Try FMGPDF01 exactly as needed for your application.
    6. If there is a program dump, take the option for a formatted CL or Cobol dump and send it to us.
    7. Send us file QTEMP/FMFSPL, captured immediately after running FMGPDF01 which produces the failure.
    8. Send us the complete Joblog.
    9. Send us your CL program which calls FMPDFG01. If you are executing the command interactively, copy it from the screen into your email directly.
    10. Be sure to include the following information:

      • Which step above produces the failure.
      • Any description you can provide for the failure.
      • All requested files (CL, Joblog, FMFSPL, Dump). FTP them to a PC with ASCII translation. For FMFSPL and the Dump, FTP them a second time as binary files with no translation. ZIP all files into one zip file to insure what we receive is what you sent! We cannot analyze large files; each file you send should be no larger than 50k. Please test with small data samples, if necessary, to provide us with manageable file sizes.