We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
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.
Do not place IBM confidential, company confidential, or personal information into any field.