This table lists the return codes from MFBSIJCL:
| Return Code | Description |
|---|---|
| 200 | The
CASSUB parameters are missing.
The minimum parameters required to execute cassub are not specified or cannot be configured from mfbsi.cfg. (-r/-l/sTCP:... -j|-x) |
| 201 | Too many parameters on the command line.
More than 35 parameters have been found on the mfbsijcl command line. |
| 202 | Unknown command line parameter used. |
| 203 | Scheduler jobLog not assigned (SJobID). |
| 204 | The MFBSI_DIR environment variable not set. |
| 205 | The MFBSI_DIR specifies an invalid dir or folder. |
| 206 | Invalid numeric value for TimeOut. |
| 207 | JCL UserExit failed to execute / RC <> 00.
An mfbsi user exit returns with RC not equal to zero. |
| 208 | A JES/JCL error occurred.
The job has been submitted but JES encountered a JCL error. |
| 209 | Job submission failed. See the
JobLog output for details.
JCL member not found. See the message JCLSI0003I in the mfbsi jobLog for details. |
| 210 | JobConcluded signal event not returned.
Enterprise Server Event Manager user-exit (mfbsiemx) did not return the event "job concluded". |
| 211 | Job ended, no numeric RC returned.
Contact Micro Focus Support for assistance. |
| 212 | Command-line parameters missing.
No command-line parameters found when executing mfbsijcl. |
| 213 | Configuration parameter unknown.
Invalid or unknown command-line parameters found when executing mfbsijcl. |
| 214 | Unable to configure JCL to submit parameter.
The cassub parameter -j or -x cannot be determined. |
| 215 | TYPRUN=SCAN: scan successful. |
| 216 | TYPRUN=SCAN: scan failed. |
| 217 | JCL UserExit program is missing or not found.
The module name specified in JCLexit cannot be loaded. Windows: ???.int|???.gnt|???.dll UNIX: ???.int|???.gnt|???.so|???.sl |
| 218 | Terminate user-exit program missing or not found.
The module name specified in TerminateExit==??? cannot be loaded. |
| 219 | SEP execution process hard killed. |
| 220 | Restart for Job failed.
Job to restart not found in ES/JCL. ES_JES_RESTART=Y and/or MF_UCC11=Y missing in Enterprise Server Configuration Information |
| 221 | Unable to call module "MFBSIPRM".
Internal error. Contact Micro Focus Support for assistance. |
| 222 | Error during skeletal parameter(s) substitution.
Internal error. Contact Micro Focus Support for assistance. |
| 223 |
MFBSI.cfg error: "SkelProcessType" unknown.
Internal error. Contact Micro Focus Support for assistance. |
| 224 |
More than 10 ISPSLIB paths. Internal error. Contact Micro Focus Support for assistance. |
| 225 | Server crashed/killed when job was waiting for execution.
mfbsijcl is unable to correctly contact the JCL region to get the job state. |
| 226 | SYS/USR-ABEND-RC=nnn in MFBSI.cfg not numeric or greater than 199. |
| 227 | JESYSMSG-RC=Y(es) requires parameter JESYSMSG.
The parameter "JESYSMSG-RC=Y(es)" should no longer be used. |
| 228 | Server crashed/killed when job was running.
mfbsijcl is unable to correctly contact the JCL region to get the job state. |
| 229 | Job state unknown or inconsistent. Check Job status via SEE Web admin.
mfbsijcl is unable to correctly determine the job state. The information from the Event Manager user-exit is not in sync with the job state. |
| 230 | The maximum number of parameters to substitute has been reached.
When using parameter(s) substitution, a maximum of 500 parameters are permitted. On the command line, the maximum 15 pairs ParamName/ParamValue are permitted. |
| 231 | Parameter file used for variable substitution is not found.
A file to be used with parameter substitution cannot be found. |
| 232 |
mfbsijcl execution has been cancelled by a SIGTERM/Break signal.
The mfbsijcl has been interrupted by a soft kill, for example, Ctrl+C. |
| 233 | The submitted job has been cancelled before execution.
A job waiting for execution in enterprise server has been cancelled. |
| 234 | MFBSI Control-M Post-Processing Handler Error.
Internal error. Contact Micro Focus Support for assistance. |
| 235 | Invalid special file name for
mfbsi.cfg.
The alternate path of mfbsi.cfg (default in MFBSI_DIR) is incorrect. |
| 236 | The special file name for
mfbsi.cfg was not found.
The alternate mfbsi.cfg cannot be found. |
| 237 | Invalid EMX-Timout parameter value. See
mfbsi.cfg.
Internal error. Contact Micro Focus Support for assistance. |
| 241 | MFBSISEC user-exit module was not found. |
| 242 | Invalid MFBSIEMX version level. MFBSIEMX v3. is required
An old version of the Event Manager user-exit was used. |
| 243 | In
MFBSI_DIR,
regionName.Started was not found.
ES/JCL region not started or not configured for MFBSI. See the enterprise server Configuration Information field, MFBSI_DIR=… or ES_EMP_EXIT_#=mfbsiemx is missing. Note: # specifies the Event Manager user-exit sequence number, starting from 1 through 9 the max.
|
| 244 | Unexpected
Job Concluded signal received from enterprise server during job execution.
The semaphore file JOB?????.sem does not reflect the end of the job. The enterprise server JCL engine considers the job as ended. You need to check the console.log file for any messages relating to the Enterprise Server Event Manger and mfbsiemx. Ensure that the file system disk space used by MFBSI_DIR and any other enterprise server components is not full. |
| 245 | Unable to allocate job number for job. See JCLCM0164A message for more information. |
| 246 | The specified PAC cannot be accessed. Check the PAC name and Endpoint. |
| 247 | No enterprise server instance is running in the PAC. |