0BA

Explanation
Started task control was processing a START, MOUNT,
or LOGON command and issued a request to a subsystem. The subsystem
or subsystem interface (SSI) returned an incorrect return code, which
is contained in Register 15.
Valid return codes are: 0 - Request processed by a subsystem.
4 - Subsystem does not support the requested function.
8 - Subsystem exists, but is not up.
C - Subsystem does not exist.

Invalid return codes are: 10 - Function not completed - disastrous error SSOB unavailable (for example, SSOB pointer invalid)
SSIB unavailable (for example, SSIB pointer invalid)
The JES detected an abend or other major error
Note:  In most cases, the 0BA abend with return code 10 will
have been preceded by  another error - usually an abend. If this is
the case, then the 0BA should be ignored and the preceding error (or
abend) should be researched and resolved. If no preceding abend is
found, check to see if anything was written to the logrec data set.

14 - Logical error SSOB block identifier not = "SSOB"
SSOB length invalid
SSIB block identifier not = "SSIB"
SSIB length invalid

Any value other than those previously listed.

Note: In certain cases in which the subsystem must be
available to process the request, '0' will be considered to be the
only valid return code.

System action
In started task control, if the command is START,
MOUNT, or LOGON the system issues message IEE824I and ends the START,
MOUNT, or LOGON task.  In the initiator, the system issues message
IEF187I and ends the job. The system writes a logrec data set error
record. The system may write an SVC dump.

Operator response
Enter the command again. If it fails again,
contact the system programmer.

System programmer response
Search problem reporting data bases
for a fix for the problem. If no fix exists, contact the IBM® Support Center. Provide the SVC dump, if
available, and the logrec data set error record.

Source
Master scheduler or initiator/terminator