Skip to content

The RFP Installation Process

Once a request for promotion has been submitted, the actual process of installing the new or modified source and objects takes place. Listed below are the steps that this process goes through and the result of each step.

The Source/Object Preparation Steps

  • Temporary MDCMS libraries (naming based on system settings for temp libraries + the RFP number) are created to handle the entire process so that no permanent changes take place until MDCMS is certain that all is ready.
  • Pre-Steps:
  • Process Pre-Compile commands for *RFP attributes
  • Process Pre-Compile commands for this RFP
  • Object Steps processed in full for each object before continuing to next object:
  • The source or non-compiled object is checked for existence.
  • If new or modified source is to be compiled, the existing source is copied to a backup library and the new version of the source is copied to the target source file/ifs path
  • Process Pre-Compile commands for object or attribute
  • Process Compile commands for object or attribute
  • Process Post-Compile commands for object or attribute
  • Validate that object has been created into temporary packaging library
  • Apply object authority to the object in the temporary packaging library
  • Stamp the object with MDCMS Meta-Data
  • Delete any triggers and disable any referential constraints from new version of a file
  • Validate the Data Transformation for mapping existing records to new version of a file
  • Add Comments to the source in the packaging library, if requested for an attribute assigned to a Source Comment template
  • Post-Steps:
  • Process Post-Compile commands for this RFP
  • Process Post-Compile commands for *RFP attributes
  • Sign source and objects, if enabled for system, to ensure that manual changes are detected
  • Warn about any level check issues, if enabled for level
  • Warn and stop process if insufficient disk space is available to deploy file changes

If a failure occurs during these steps, a message will be sent to the user that submitted the job describing why the failure occurred and the Compile Error exit point will be triggered. For additional detail, the RFP log and the spooled files for the job should be reviewed. The RFP will remain at status 01 and can be re-requested from the RFP Manager. If the RFP is not in status 01, it will need to be reset using option 7 in the RFP Manager.

Source and Object Signing

MDCMS uses an SHA-1 encryption algorithm with a HMAC key unique to each distinct object migration chain to create a 1-way signature for each source member, IFS source file or IFS/Remote object files that have been prepared to be installed. The initial signature is applied when it is installed into the initial promotion level, and this signature is compared to the newly generated signature at higher levels.

If the System Settings parameter Sign Objects is set to true, and the signature does not match, then MDCMS will require that an authorized user approves the installation before the installation steps will be started.