When creating new replication configurations ASNCLP checks the existence of MQ Queues, qmaps, tables, etc. When deploying to production, we need to have pre-prepared and tested the implementation scripts. However, because ASNCLP validates that the required objects exists we need to make multiple changes in order to deploy a new qmap and subscriptions - the first to create the queues and the Qmap, and then another to create the subscriptions.
Being able to make a single change will reduce time to market and also the overheads associated with deploying a new subscriptions.
New Subscription definitions occur on a reasonably regular basis - maybe once or twice a month.
|Who would benefit from this IDEA?||Any user that is deploying subscriptions on a regular basis could benefit by implementing in a more efficient and agile manner.|
How should it work?
ASNCLP should support a VALIDATE NO option whereby it doesn't validate that the required objects exist. It should 'trust' that the requester knows what they are doing and that the prereqs will be in place by the time the resulting script is executed.
|Priority Justification||Making subscription definitions in production is time consuming and does not easily embrace the agile principles organisations are trying to adopt.|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions