Skip to content

Create Config Deployment Settings

Setup Menu option 20 provides command MDCRTSET to generate an Application to manage the MDCMS product, including the deployment of new versions, patches, license keys and settings.

The command has the following parameters:

Option / Field Description
Application Code (APPL) The Application code to use for MDCMS product administration.
Defaults to value MD
If the application code already exists, any existing settings will not be updated, but any new attributes will be added.
If the code doesn't exist yet, MDCRTSET creates it.
Level (LVL) The Application level number to use for MDCMS product administration.
Defaults to value 90. Typically, only one level is necessary per instance of
MDCMS on a specific system.
If the level already exists, any existing settings will not be updated, but any new attributes will be added.
If the level doesn't exist yet, MDCRTSET creates it and sets the flags to allow checkout and receipt and to automatically process an RFP. The flag values can be modified as necessary afterwards.
Job Description (JOBD) Specifies the name of the job description to be applied to the level definition, if the level doesn't yet exist.
Defaults to value MD90
If the job description doesn't exist, MDCMS will create it automatically and set the parameters to commonly used values.
Job Description Library (JBDL) Specifies the library of the job description to be applied to the level definition, if the level doesn't yet exist.
Defaults to value QGPL
The library must already exist on the system.
Job Queue (JOBQ) Specifies the name of the job queue to be defined in the job description, if the job description doesn't yet exist.
Defaults to value QBATCH
The job queue must already exist
Job Queue Library (JBQL) Specifies the library of the job queue to be applied to the job description, if the job description doesn't yet exist.
Defaults to value QGPL
The library must already exist on the system.

MDCRTSET generates the following attributes:

Column 1 Column 2 Column 3
Type Attribute Description
*DTAGRP APP Deploy a specific application code. Only the code itself is deployed - use the other attributes to deploy the contents of an application
*DTAGRP APPLVL Deploy a specific level by specifying , as the object name. The level settings and MDXREF library list are deployed - use the other attributes to deploy the contents of the level
*DTAGRP ATR Deploy a specific attribute by specifying , , as the object name. The attribute settings, commands and scripts are deployed for that attribute.
*DTAGRP ATRALL Deploy all attributes for a level by specifying , as the object name. The attribute settings, commands and scripts are deployed for all attributes for the level.
*DTAGRP CMDRFP Deploy all *RFP commands for a level by specifying , as the object name.
*DTAGRP LOG Deploy the Log Cleanup settings for a specific Log File
*DTAGRP RPTDEF Deploy a specific report definition
*DTAGRP SECALL Deploy all User Roles, Users and user authority defined in MDSEC. Any value can be used for the object name, since all records are included automatically.
*DTAGRP SECROLE Deploy the authorities for a specific User Role by specifying the role id as the object name. The users assigned to the role are not deployed.
*DTAGRP SECUSR Deploy the authorities for a specific User by specifying the user id as the object name. The roles that the user belongs to are not deployed.
*DTAGRP SECUSERS Deploy all users. Only new users are added on the target locations - any existing users aren't overwritten. Role MD_USER will also be applied to all users, if the job description user for the target level has been granted permission to execute command MDUPDUSR in MDSEC.
*DTAGRP SERVICE Deploy the Service Runtime settings for a specific service by specifying the service name as the object name.
*DTAGRP TMPDTACPY Deploy a Data Copy template by specifying the template ID
*DTAGRP TMPOBJAUT Deploy an Object Authority template by specifying the template ID
*DTAGRP TMPOBJDEL Deploy an Object Delete template by specifying the template ID
*DTAGRP TMPOBJREP Deploy an Object Replication template by specifying the template ID
*DTAGRP TMPOBJSEA Deploy an Object Search template by specifying the template ID
*DTAGRP TMPRAPID Deploy an MDRapid template by specifying the template ID
*DTAGRP TMPSRCDEL Deploy a Source Delete template by specifying the template ID
*DTAGRP TMPSRCREP Deploy a Source Replication template by specifying the template ID
*DTAGRP TMPSRCSEA Deploy a Source Search template by specifying the template ID
*IFS INSTALL Deploy a new build of the MDCMS products and then automatically install that build.
Each of the 4 IFS save files (MDCMS.savf, MDREP.savf, MDSEC.savf and MDXREF.savf) should be requested using this attribute. The easiest way to do so is in MDOpen using the Import Local Objects option.
If the install (MDINSSAVF) shouldn't be automatic, then disable the post-install command or create a copy of the attribute that doesn't contain the post-install command.
*IFS LICENSE Deploy the MDLICENSE.savf to update the license keys and execute the update
*IFS MAIL Deploy an email body template file
*IFS PATCH Deploy a patch (mdupd_vv.rr_yyyymmddx.savf) and then automatically apply the patch
*IFS SCRIPT Deploy a script template file