Troubleshooting

For general MFBSI troubleshooting, perform the following steps to identify an issue:
  1. Shutdown the Enterprise Server.
  2. Clean up the MFBSI_DIR folder by deleting all files except your mfbsi.cfg file.
  3. Start Enterprise Server JCL from a command line. In Windows, from an Enterprise Developer command prompt (32-bit or 64-bit), enter casstart -rES_name. In UNIX/Linux, start a session for the defined Enterprise Server user by entering casstart -rES_name.
  4. Check the console log for a correct initialization of MFBSIEMX, and ensure that the Enterprise Server Event Manager has not been stopped by MFBSIEMX.
  5. Verify that a file named ES_name.Started exists in the folder specified by the MFBSI_DIR environment variable (where ES_name is the name of the Enterprise Server started with CASSTART). If this file does not exist, verify that you can create a file in the MFBSI_DIR folder.
  6. In Windows, from an Enterprise Developer command prompt (32-bit or 64-bit), validate MFBSIJCL by executing the command mfbsijcl /show. In UNIX/Linux, validate MFBSIJCL in a user session that will submit JCL (UNIX), by executing the command mfbsijcl /show. The console output should be similar to:

    GUID-78D65983-FBA0-42AC-A90B-3DFE717A020A-low.png

  7. Enter the CASSUB command to validate that you can submit and execute a job in Enterprise Server/MSS JCL. For example:
    • cassub -rES-name -jC:\...\JCL\rc00.jcl (Windows).
    • cassub -rES-name -j/.../JCL/rc00.jcl (UNIX/Linux).
    This creates a file named JOBnnnnn.sem in the MFBSI_DIR folder, where nnnnn is the job number assigned by the Enterprise Server/MSS JCL.
  8. Execute MFBSIJCL from the command line using the same parameters, using STDOUT to output to the console. For example:
    • mfbsijcl -rES-name -jC:\...\JCL\rc00.jcl SJOBID=StdOut (Windows).
    • mfbsijcl -rES-name -j/.../JCL\rc00.jcl SJOBID=StdOut (UNIX/Linux).
    Verify successful execution. The file JOB#####.sem is deleted when MFBSIJCL completes execution.
  9. Execute MFBSIJCL again from the command line using the same parameters, only specify a file for the output. For example:
    • mfbsijcl -rES-name -jC:\...\JCL\rc00.jcl SJOBID=SJOB01 (Windows).
    • mfbsijcl -rES-name -j/.../JCL\rc00.jcl SJOBID=SJOB01 (UNIX/Linux).
    Verify successful execution. Review the log file SJOB01.log in the MFBSI_DIR folder to help troubleshoot your issue.
    Tip: Most issues in UNIX/Linux are the result of access denied, case sensitivity or authorization errors.
Parent topic: Additional Notes