For general MFBSI troubleshooting, perform the following steps to identify an issue:
Shutdown the
Enterprise Server.
Clean up the
MFBSI_DIR folder by deleting all files except
mfbsi.cfg.
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.
Check the console log for a correct initialization of
MFBSIEMX, and ensure that the
Enterprise Server Event Manager has not been stopped by
MFBSIEMX.
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.
In Windows, from an Enterprise Developer command prompt (32-bit or 64-bit), validate
MFBSIJCL by executing the command
[run] mfbsijcl /show. In UNIX/Linux, validate
MFBSIJCL in a user session that will submit JCL (UNIX), by executing the command
[cobrun] mfbsijcl /show.
The console output should be similar to:
Enter the
CASSUB command to validate that you can submit and execute a job in
Enterprise Server/MSS JCL. For example:
