1. Home
  2. Knowledge Base
  3. Adding Reusable Create Command Overrides via Command Maintenance

Adding Reusable Create Command Overrides via Command Maintenance

Create Command overrides allow you to enter commands directly into the override file without requiring RFP history or having to check out the object. This can assist in providing command overrides to a specific object or to numerous objects.

View/Manage Object-Level Create Command Overrides

Commands that have been processed during the installation of an RFP, and that have the Reuse Command flag set to Y, will automatically appear on this file.  Commands can also be created for objects that aren’t yet requested. Alternatively, you can use Option C on an existing Object Request to manage commands for that specific object.

To view from green screen:

  • MDCMS
  • Select option 1 – MDCMS Setup Menu
  • Select option 4 – Commands/Scripts
  • Press F7 – Object Commands

From the screen that’s shown below, you can filter to locate the object in question or press F6 to create a new override.

If adding a new override, level information should be a level from which a checkout can occur.  This is the lowest level(s) in your development path.

Mass Input of Object-Specific Create Commands

When moving from another CM vendor or an in-house CMS, existing Create Command special parameters may need to be captured specifically for the object.

Note: If you want the unique Create parameter to always be present, this can be done via the Attribute Level command.

You can populate the MDDRCMD file via your own process to pre-load all the objects that require a specific override. You will need to use the wildcard values, but you can easily identify what the syntax of the command should be by adding the appropriate overrides to one object.

HINT:  It’s easiest to checkout one of the objects, add the Create Command override to that object, then view how the command looks in the file and on the screen.  This is a great way to see what should be added to all the fields.

Below is the file layout for the Command Override file.

  File Name  . . . . . . .  MDDRCMD
      Library  . . . . . . .    MDCMSUS

 

Field Name Length Type Dec Pos Description Rec Format
MDAGP 4 A 1 Application RDDRCMD
MDLVL 2 P 5 Level RDDRCMD
MDOBJN 82 A 7 Object RDDRCMD
MDPATH 242 A 89 Path RDDRCMD
MDOBJA 10 A 331 Object Attribute RDDRCMD
MDRSN 1 A 341 Reason RDDRCMD
MDTSEQ 3 P 342 Type Sequence RDDRCMD
MDSEQ 3 P 344 Sequence RDDRCMD
MDTPCD 1 A 346 Command Type RDDRCMD
MDIGN 1 A 347 Ignore Errors RDDRCMD
MDKMDL 1 A 348 Keep MD in Libl RDDRCMD
MDWCIS 1 A 349 Wildcards in Source RDDRCMD
MDRLOC 10 A 350 Location RDDRCMD
MDUSER 10 A 360 User RDDRCMD
MDCMDS 642 A 370 Command String RDDRCMD
MDDATE 8 P 1012 Date RDDRCMD
MDTIME 6 P 1017 Time RDDRCMD

View/Manage Object Group Command

The Object Group command functions in much the same way as the Create command, but it can be used for pre/post compile and install commands and data.  

This feature allows you to list or manage all commands that are defined to be executed for specific objects. Commands that have been processed during the installation of an RFP, and that have the Reuse Command flag set to Y, will automatically show up in this list. Commands can also be created for objects that aren’t yet requested.