Commands

The Attribute Command displays are used to define the command defaults that are used to compile and manage objects. Each Application Group/Level/Attribute that requires a default command should be defined here. Default commands may also be defined to run for each promotion of objects, regardless of the types of objects in the promotion package.

Option 4 Screen Definitions

Filters

Appl/Lvl

Enter a value here to limit the listing to a specific application or level.

Attribute

Enter part or all of an attribute to limit the listing. For example, enter C to list only commands with an attribute starting with C.

Type

Enter a value here to limit the listing to a specific command type. See the next section for detailed information about each type of command available within MDCMS.

Command

Enter a string here to limit the listing to commands containing that string. For example, enter SRC to list only commands containing the string SRC.

Description

Enter a string here to limit the listing to commands with a description containing that string.

Opt

2=Change - Change the text and run-time attributes for the selected Command

3=Copy - Copy a command

4=Delete - Delete a command

5=View - display a command

Function Keys:

F4=Browse - Browse the list of valid values for a filter field.

F6=Add - Add a new Attribute Command

F7=Obj Cmds - List/Manage all commands that are defined to be executed for objects with a specific or generic name. 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 from here for objects that are not yet requested. Alternatively, option C can be used on an existing Object Request to manage commands for that specific object. Navigate to the Commands/Scripts for Object section for help with the individual parameters.

Object Specific Scripts can be managed by pressing F10=Scripts from with the Object Specific Commands screen.

F8=Description/Command - Toggle the listing between the command to execute and the description of the command.

F9=Gen RFP Cmds - Generate *RFP commands in order to notify users by email when specific events occur. When F9 is pressed, the first screen allows you to select one or more application levels that should contain the commands. The second screen then allows you to select each command type, or exit point, for when the MDMAILF command should run. MDCMS then generates the commands for each selected exit point for each selected level.

Once the commands are generated, further customization can be performed on the commands from the command settings. This is particularly necessary for the Waiting for RFP Approval command type, since the group or user responsible for approving the RFP will need to be entered into the appropriate parameter.

F10=Scripts - Manage scripts that are defined for *IFS and *REMOTE attributes.

Add or Change display

Screen Definitions:

Appl/Lvl

The Application Group and Level that the attribute resides in.

Desc

An optional description of the command

Attribute

This field indicates which MDCMS Attribute(s) defined for the target level that the Command Definition should be applied to.

*RFP - the command will run once each time a promotion is run, regardless of the objects contained in the RFP.

Specific Attribute - The command definition is for a specifically defined MD Attribute, such as CLLE

Generic Attribute - The command definition is for any MD Attribute that matches the generic naming pattern. For example SQL*LE would mean that the command is applied to every attribute starting with SQL and ending with LE.

*ALL - all attributes for the target level are defined to use this command.

When a generic attribute value or the *ALL value is used, the Object Type can be set to a specific type. For example, if the command definition should be applied to every program attribute, then set Attribute to *ALL and Obj Type to *PGM.

Run for Modifications

Flag stating if the command should run for new or changed objects.

Run for Recompiles

Flag stating if the command should run for recompiled objects.

Run for Deletes

Flag stating if the command should run for deleted objects.

Run for Updates

Flag stating if the command should run for updated objects.

Type

The Type value designates when a command should run

Command Types A, E, F, G, H, I, J, L, R, V, W, S, T, X, CB, CC, CD, CE, TB, TC, TD, TE, 5, 6, 7, 8, and 9 are only valid at the RFP Level (Usage Attribute = *RFP).

Sequence

The sort sequence of the command at run time, in case multiple commands for command type are defined. The sequence is used across all levels of specificity such that less specific commands can run before or after more specific commands if the sequence number is lower or higher. See the Spec Def parameter for more information.

Frequency (Command Type 1, P, 2, 3 or 4 when for Attributes)

O - The command will run for every object in the RFP that is assigned to the given Attribute.

R - The command will run for the first object in the RFP that is assigned to the given Attribute and then ignored for any additional objects for the same Attribute.

Frequency (Command Type 5 or 6 when for *RFP)

B - The command will run each time an RFP is sent to a batch of target locations

L - The command will run for each target location that is sent to during a batch run.

User Prof

By default, commands executed during an RFP run under the profile of the user profile defined on the job description of the application level for the RFP. If a specific command should run under the authorities of a different user, that user ID can be entered here. As a safety precaution, the user placing a value in this field must have authority to use that entered user profile in order to save the command definition.

Ignore Errors

Y - Continue with RFP processing even if the command fails.

N - Cease and Rollback RFP processing if the command fails

Will always be ignored unless for 1, C, P, 2, D, U and 3

Obj Type

Only include the command for attributes of the given type (Ignored for *RFP commands)

*ANY - include for any object type

Keep MD Libs in Libl

N - The MD Libraries (MDCMS, MDSEC and MDXREF) are removed from the library list before the command is invoked. This assures that any MD Objects with the same name as your objects are not used.

Y - The MD Libraries are left in the library list. This is necessary when MD Objects, such as interface programs, MDMAIL or MDMAILF, are needed to process the command.

Spec Def

N - The command will not run if a more specific command of the same command type is defined.

Y - The command will run even if a more specific command of the same command type is defined.

Order of Specificity (from most specific to least specific)

• A command defined for a specific object
• A command defined for objects of a generic naming pattern
• A command defined for a specific attribute
• A command defined for attributes of a generic naming pattern
• A command defined for attribute *ALL

Example 1 - A compile command defined at the attribute level will typically be set to N, so that if a compile command is defined at the object level, the attribute level command will not run.

Example 2 - A post-compile command may be set to Y when it is needed for all program attributes, including those with post-compile commands defined for specific objects or attributes.

Placeholders in SQL

N - The SQL member or IFS file used by a RUNSQLSTM command does not contain MDCMS placeholders - no conversion will occur

Y - The SQL member or IFS file used by a RUNSQLSTM command contains MDCMS placeholders - MDCMS will create a temporary copy of the script and convert the placeholders in the copy to the actual runtime values. This flag should also be set to Y when a script is used for any of the MDCMS *SQL type attributes to create those objects, even if a placeholder isn't present, so that MDCMS can automatically qualify the object.

This flag is only relevant for object-related command types using the RUNSQLSTM command. The placeholders embedded in the SQL script may be delimited by ++ instead of ## to avoid code page issues.

Wait before Usage

If the command type is L (Lock Wait for Object), the number of seconds to wait before an object lock condition causes the command to be executed can be defined.

If multiple L commands are defined, each command waits the number of seconds defined for that command after the prior command has completed.

For example:

Command 1 waits 15 seconds before sending an email to the user that submitted the RFP.

Command 2 waits 300 seconds before sending an email to the entire operations group (plus the 15 seconds wait for command 1)

Command 3 waits 3600 seconds before rolling back the RFP (plus the 315 seconds from commands 1 and 2).

Command

The IBM i or user-defined command to be performed. Enter the name of the command and then press F4 to fill in the keywords.

Some placeholder parameter values may be used and are substituted by MDCMS at run-time. The placeholder value may be typed directly into the command or the cursor may be positioned in the command and F7 pressed to insert the value from a list.

For Lock Wait command types, special value *ROLLBACK can be used to automatically roll back an RFP if an Object Lock condition occurs.

Function Keys:

F4=Browse - Browse for values.

F7=Insert Placeholder - Insert placeholder value into command string at the location of the cursor. A list of all fixed placeholder values followed by all placeholders for custom fields will be displayed to select from.

Attribute Command Considerations

This function is directly related to the Source/Object Attribute Maintenance. The commands are used during the RFP compile and Installation processes and the defaults entered for a command will affect the object's attributes.

It is essential that the generic ## names are used within the compilation commands for the object library and name, and source library and name. Otherwise, the installation process will not work properly.

If a command is to run for every RFP for an Application/level and is not based on the installation of a specific object-type, use the attribute *RFP.

If a command is intended to be used only for a specific object or for a specific RFP, then define the command within the Command Override function in the Object Manager or RFP manager.

Fixed Command Placeholder Values

The fixed placeholder parameters are:

Special Placeholder Operators

For any placeholder, including custom level or project placeholders, special operators can be included in the placeholder string just before the trailing ## or ++ characters. The following special operators are available to use only a portion of the runtime value for the placeholder:

(position, length) can be used to use only the substring of a value.
For example, placeholder ++PROJID(1,6)++ will result in a value containing only the first 6 characters of the project ID. Or, ++PROLVL(3,1)++ will result in a value containing the 3rd digit of a promotion level.

(TLZ) can be used to trim any leading zeroes from a value.
For example, placeholder ++RFPNBR(TLZ)++ will result in a value containing the RFP number without any leading zeroes.

MDCHKOBJ - Validate Object Request command

The Validate MDCMS Object Request command provides the parameters necessary for MDCMS to invoke a custom validation program prior to the completion of an Object Request.

A custom validation program can be used to provide an info, warning or error message to the developer when attempting to check out an object. To do so, this command must be defined for a specific Object command or for an attribute command using command type B=Pre-Object

Request Validation.

Command MDCHKOBJ doesn't directly invoke a program. Instead, it uses the command parameters to know the name and location of a custom program to be directly called by MDCMS when an object request is performed.

The B command type can be repeated if more than one custom program should be called.

The custom program must contain exactly the following calling parameters with each parameter individually defined:

MDCHKRFP - Validate RFP prior to Submission command

The Validate MDCMS RFP (MDCHKRFP) command provides the parameters necessary for MDCMS to invoke a custom validation program prior to the submission of an RFP.

A custom validation program can be used to provide an info, warning or error message to the developer when attempting to submit a specific RFP. To do so, this command must be defined for a specific RFP or for a *RFP attribute command using command type V=Pre-Submit Validation.

Command MDCHKRFP doesn't directly invoke a program. Instead, it uses the command parameters to know the name and location of a custom program to be directly called by MDCMS when an RFP is selected for submission.

The V command type can be repeated if more than one custom program should be called.

The custom program must contain exactly the following calling parameters with each parameter individually defined: