To submit and start a JCL job to Enterprise Server, you execute the CASSUB command with the appropriate parameters. However, by design CASSUB only provides notification on the proper submission of the job to Enterprise Server if the JCL job syntax contains no errors. CASSUB can also end with a return code and output only to standard output (STDOUT).
If no initiator is available in Enterprise Server, the job is never executed. If an initiator is available, the job may fail with a JCL error such as data set not found, or with a User, SYS, or RTS error in a program step execution.
Whether the job ends successfully of not, when using a scheduler to submit and control Enterprise Server/JCL job execution, there is no mechanism to provide communication or feedback between the job execution and Enterprise Server. You can submit and monitor JCL jobs activity using Enterprise Server, but this requires manual intervention.
The Micro Focus Batch Scheduler Integration (MFBSI) provides this functionality, allowing for submission, execution and communication between JCL job execution in Enterprise Server and the scheduler.