Adding the Batch job name in the message CECZ0993E when Batch Job has DBRC=N

We are having problem when in Dev/PROD regions DBRC is not enforced. Whenever any Batch JOB submitted with DBRC=N, it hanged entire subscription and lot other problem appeared. e.g. Subscription failures, OLD logs to be looked for whenever CDC task started.

In Development it is very usual that DBRC is not taken into consideration and Developers submit the job with DBRC=N, so this should be considered as a valid option and we should have proper handling of DBRC=N as far as CDC for IMS is concerned.

Also we don't have BATCH job name in the message CECZ0993E  (It shows IMS subsystem name). Due to that we are not able to identify which Batch has been causing the issue and has been submitted with DBRC=N. We need the Batch job name in this message ID to identify the JOB.

Please consider this idea to handle the DBRC=N situation for CDC for IMS.

There are 4 PMRs going on for this and we request IBM to take it forward with the solution like allow DBRC=N so that DL/I start-end notification exit can work without causing any issue to subscriptions.

PMRs are as follows

34026,004,000 RR - CDC for IMS looking for old IMS log though          

subscription was up and running all last week                          

34091,004,000 RR - CECZ0993E The IMS change-capture interface received

a DL/I notification for job IMT1                                      

34188,004,000 RR - CDC for IMS - SUBSCRIPTION STOPS IN ERROR          

34194,004,000 RR - SUBSCRIPTION is up but not publishing the data to MQ

after some time                                                        

it has huge impact in our environment. Request you to please incorporate the idea and work towards the solution.

Thanks

Amit