CUZ#INEX batch processing should wait on end result from processing in started task.

CUZ#INEX batch processing ends with RC=0 while CTC rejects processing.

Example 1:
There is a connection problem between CTC and S3. 

The STC shows for a backup attempt: 
CUZS035E CUZSTCPY-Jobname CLOUD.CONNECTOR DCB CUZDDNAM-Cloud Write Function has Abended-Abend Code: 00000008 
CUZS043E CUZSTCPY-Jobname CLOUD.CONNECTOR DCB CUZDDNAM-cldmsg C122-Not establish socket conn to cloud.Initial 
However, the job ends with RC=0 giving no indication that backup failed

Example 2
CTC does not support all record formats. For instance DSORG=PO.
When using the batch interface with PGM=CUZ#INEX and the INCLUDE option contains a PDS, the job ends with RC=0, implying backup was ok. 
STC shows CUZS126W CUZSTCPY-Dataset SPOS.BAKKERO.CTC.DSN8.RET.PERIOD.DAYS2 contains a DSORG of PO which is not supported.

We need proper RC handling so automation can be set up for incident registration.
Batch job should reflect succesfull/unsuccesfull processing so (ZWS) batch scheduling can act accordingly, i.e. do or do not start the next batchjob. 

CTC Batch interface(s) handle fire-and-forget processing, where it should (optionally) wait for succesfull completion. 

This is descibed in TS021323312 and also a bit similar to TS021252556. For end-users proper return code handling is vital in fully automated (batch) processing / error handling.