BATCHREP should support the creation and modification of CPSM Parameters.

SYSLINK MODEL to be specified as a CPSM BATCHREP attribute and
MODEL SYSTEM NAME to be displayable in EYUSTARTCSYSDEF.DETAILED view or retrieved with the CPSM API :

All the CSYSDEF parameters can be specified as an input to CPSM BATCHREP CREATE CSYSDEF NAME(xxxx) command but not the MODEL SYSTEM NAME parameter refering to the CICS region from which CPSM BAS will create the SYSLINKs for the new region.
Because of this, the process of creation of cloned regions into CPSM can't be totally made through batch jobs.
Going to the WUI interface to create the SYSLINK is still madatory and can be source of errors.

The CSYSDEF MODEL parameter should be an optional CPSM resource like the others.

By the way, the value of the CSYSDEF MODEL paramater should be available in the EYUSTARTCSYSDEF.DETAILED view in theWUI interface once it has been refered to by the SYSLINK creation process.
It can be worth to keep this information displayable when the number of CICS regions increases and the model of SYSLINK definitions defers between groups of CICS regions.

We got the following answer from the Change Team :
BATCHREP CREATE does not have support for CREATE parameters, so the MODEL value (which is a parameter not an attribute) cannot be specified. This is the same reason that you cannot specify the RESGROUP parameter on an xxxxxDEF CREATE.

Likewise, as MODEL is not an attribute on the CSYSDEF resource table, it cannot be shown on a CSYSDEF WUI view (it is not saved as part of the definition), it is only a parameter on the CREATE action.

The request should be extended to the support of the BAS RESGROUP parameter and to all the Fully Fonctionnal BAS definitions (RASGNDEF and RESDESC). A means of getting the full support of BAS in CICS Configuration Manager ?