You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, the YAML input to the queue_manager module provides only the capability to create and manage QMGRs directly, and input MQSC for further configuration.
For a test system, creating a few simple queues would require writing out MQSC to create them.
Describe the solution you'd like
It would be good if we could specify a queue object in the YAML input to be created on a queue manager. Our module will recognise this and run the appropriate MQSC to create the queue (as well as the QMGR according to the situation).
Describe alternatives you've considered
N/A
Additional context
Further extensions would allow for other objects (channels, etc) to be created, along with appropriate attributes, reducing the need for MQSC files - helpful if the user has less understanding of MQSC.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, the YAML input to the queue_manager module provides only the capability to create and manage QMGRs directly, and input MQSC for further configuration.
For a test system, creating a few simple queues would require writing out MQSC to create them.
Describe the solution you'd like
It would be good if we could specify a queue object in the YAML input to be created on a queue manager. Our module will recognise this and run the appropriate MQSC to create the queue (as well as the QMGR according to the situation).
Describe alternatives you've considered
N/A
Additional context
Further extensions would allow for other objects (channels, etc) to be created, along with appropriate attributes, reducing the need for MQSC files - helpful if the user has less understanding of MQSC.
The text was updated successfully, but these errors were encountered: