Put transaction and system dump tables in RDO (SHARE requirement SSCICS94012)

This RFE is satisfied by CICS Transaction Server for z/OS V5.6 which is Generally Available today 12th June 2020.
For more information see the CICS TS V5.6 Knowledge Center https://www.ibm.com/support/knowledgecenter/SSGMCP_5.6.0/whats-new/intro.html#intro__rdo-dumpcode

This RFE is satisfied by CICS Transaction Server for z/OS V5.6 which is announced today 7th April 2020 and which has a planned availability date of 12th June 2020.
For more information see the CICS TS V5.6 announcement letter
https://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/7/897/ENUS220-077/index.html&request_locale=en

This is something we would like to address. The RFE is being moved into 'Planned for Future release' status. Please note:
IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.

I agree to this RFE and also to some points mentioned by mikegia5. If the transaction and system dump options could be set by RDO, you could create definitions and add the RDO group to one or more CICS regions. To control whether the dump counters will be reset on COLD or WARM start an option like RESET(NO|COLD|WARM) migth help. NO means, that the counters will be reset by CEMT command only, and COLD or WARM, that the counters will be reset on COLD start or additionally on WARM starts.

I agree this would be nice. One consideration though is when adding a SYDUMP entry for a warm restart. This is rare, but I am currently working with the change team to gather doc for a CICS recovery issue, and we may not want a COLD start to bring in a new dump entry. We could define the SYDUMP entry in CICS before the recycle so that it will be there after a warm start, but I question whether RDO is the right spot? It will also change the dynamics of the dump counts. Would they be cleared on a cold start but not on a warm start? We currently have ours in the sequential terminal, and the problem we have is that capturing a dump early in the startup process is difficult because sequential terminal runs after CICS starts, so we miss any startup messages we want to trap.

Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Transaction Processing
Product - CICS Transaction Server

For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Transaction Processing
Product - CICS Transaction Server

The advantage of having a RDO defintions is that you can adress a scope of CICS. When you have multiple clone AORs it's easier to install a RDO defintion than logging on each CICS to set your dump table with the CEMT command

Raised as RFE 23735 (RTC RFE 53920) which is been closed as duplicate of this. Text from that RFE is:

Currently to manage entries in the system dump table of CICS Transaction Server we only have to use CEMT command to define/modify entries

It would be interesting to have an RDO object to define an entry in the system dump table

It would allow automatic definition since it could be installed from the grouplist

Instead of using CEMT, RDO definition could be changed and then reinstalled

RFE for Product: CICS Transaction Server
NOTE: Discussion is private to RTC unless the remark is prefixed with
Use Case
I want to have automatic entries defined for system dump codes SR0001 and SM0102 for example.I would define an RDO object SYSDUMPCODE where i would mention the name of the system dump code and the characteristics that are currently defined using CEMT S SYDUMPCODE commandThis object would be automatically installed (and the entry in the sytem dump table automatically created after installation) if the group is in the group listIf i want to change the characteristics of this SYSDUMPCODE RDO Object, i would alter it using CEDA and then make a discard/install