Batch interface to load CICS settings

I would like a means of loading a saved CICS settings record (from the AGGSCDS) into a CICS region (i.e. what HGSC does) from a batch job step, and a way of activating an ad-hoc setting for a user within a CICS region (i.e. what HGUC does) from a batch job step. This job step should provide a return code which indicates the success or otherwise of the application of the setting to the target CICS region. Just for good measure, it would be desirable to have a means of activating an ad-hoc global setting in a CICS region (ie. what HGCC options 1 thru 4 do) from a batch job step.
For the HGSC case, the batch interface should take as parameters, the target CICS region (APPLID?), the name of the settings record to be applied, and a G, U, or B to indicate whether the Global, User or Both settings from the nominated record should be installed.
For the HGUC case, the batch interface should take as parameters, the target CICS region, the user ID, the date, the time (with A,P,M,E,W prefix, as usual) and 0 to 6 4-character CICS transaction IDs (or prefixes*) to which the setting applies. If no transaction IDs are supplied, the setting applies to all transactions for the nominated user (as usual).
For the HGCC case, the batch interface should take as parameters, the target CICS region, the date, the time (with prefix, as usual), 0 to 42 8-character user IDs (or prefixes*) to which the setting applies, 0 to 42 4-character transaction IDs (or prefixes*) to which the setting applies and 0 to 42 4-character terminal IDs (or prefixes*) to which the setting applies.