Remove requirement for ZPARMs assembly skills Merged

Convert the MQ ZPARMs from an (assembled) macros (to a (non-assembled) set of options that are contained in a parameter dataset, like other IBM products (for example: RACF and SDSF). 

It is useful because it will increase productivity, eliminate the need for assembler skills, and improve the overall accuracy of settings that are currently coded in assembler. 

The people that would benefit from it include: Product installers and product administrators (changing parameters, etc.).  Other benefits would be providing simpler “risk” control to the parameters in ZPARM. 

It should work like this: 

-        Provide a dataset where ZPARMs reside (that does NOT need assembly)

-        The “dataset” should be opened, read and used by the appropriate MQ task (Queue Manager, Channel Initiator, etc.) when the MQ task starts.

-        (longer term), provide a method to dynamically update the new ZPARMs values (using the “dataset”) without restarting the appropriate MQ tasks.  (perhaps, something like this: REFRESH QMGR TYPE(ZPARMs))

-        Documentation should be added for how to protect the new dataset, so that only MQ tasks and product support has access to update the options.

Examples of other IBM products (that have converted away from assembled parameters) include: 

SDSF:

https://www.ibm.com/docs/en/zos/2.3.0?topic=v2r3-sdsf-use-dynamic-statements-isfparms-avoid-reassembly

RACF:

https://www.ibm.com/docs/en/zos/2.3.0?topic=sys1parmlib-irrprmxx-racf-parameters (which were previously defined by assembled parts) ICHRDSNT and ICHRRNG 

note: This would eliminate the sample JCL (SCSQPROC(CSQ4ZPRM)) and the steps required to assemble/link edit.