Skip to Content

AD (F) – Flags

Flags are used to control ISPW processing for all Component Types within an Application at each level. The setting of these Flags determines the following:

  • How the component is promoted (that is, Source only or with all its Associations)
  • Whether strict version control is adhered to
  • At what level the component is generated
  • Whether a successful generate is required before promotion to the next level
  • Whether the component is implemented
  • Whether a successful implement is required before promotion to the next level
  • Whether the source is packed
  • Whether the component should be retained in the physical library when promoted to the next level.

Flags Screen

The following figure is an example of the Flags Definition screen. It is displayed when the F (Flags) command is entered against an Application Level. The flag option fields can be edited directly from this screen.

Flags Screen

image2021-1-29_17-15-49.png

Field Descriptions

The following table describes each field for a Flag:

Field Descriptions

Field Name

Description

Promote Method

The style of promote.

Valid values:

  • A – ‘P’ style promote. All of the components’ associations are promoted from this level. Any exits for operation P will be performed.
  • R – ‘R’ style promote. Only the source component will be promoted. Normally, the Generate Option flag would be set to R. Any exits for operation R will be performed.

Version Control

Determines whether to perform version checking when a task is set In Process to promote to any HOLD environment level. The Version Control flag should be configured at the levels from which promotes are initiated. For example, if your lifecycle looks like the following figure and you want to do version checking on promotes to QA, set the Version Control flag at levels STG1 and STG2.

image2021-1-29_17-18-6.png

Valid values:

  • Blank or Y – strict version checking. If rVer or bVer is greater than target version, set default warning flag on the SetProc warning screen to N. Also, if rVer and bVer are both less than the target version, do not allow an overlay to occur.
  • A – Assignment. In addition to “strict version checking,” target version can only be replaced by a task in the same assignment.
  • B – Block all overlays. No overlay can be done from this level. Users with the SERVER ADMIN permission can bypass this restriction.
  • N – None. Don’t perform version checking, and set the default warning flag on the SetProc warning screen to be N.
  • U – User. In addition to “strict version checking,” target version can only be replaced by the same user, irrespective of rVer.
  • W – Warning. Do not perform version checking and set the default warning flag on the SetProc warning screen to be Y.

Generate Opt

Specifies the generate option for components at this level.

Valid values:

  • R – Required. Generate is required at this level. If promoting to a level with this value, a “G” operation will be initiated.
  • O – Optional. Generate is optional at this level.
  • Blank – generate is not allowed.

Check for Generate

Determines whether a Promote operation can be performed, by first verifying that a successful Generate operation has completed for the task. 

Valid values:

  • Y – Verify that generated components exist before promotion.
  • Blank or N – Do not verify that generated components exist before promotion.

Implement Opt

Specifies that components at this level are to be Implemented (I operation).

Valid values:

  • Y – Components can be Implemented. If promoting to a level with this value, an “I” operation will be initiated.
  • Blank – Components cannot be Implemented.

Check for Implement

Determines whether a Promote operation can be performed, by first checking if a successful Implement operation has completed for the task. Note: This flag is only valid for primary components, not generated parts (load, list, etc.).

Valid values:

  • Y – The task is checked to ensure that a successful Implement has completed before a Promote is allowed.
  • Blank – No check is made for a successful Implement of the component on a Promote.

Pack Prod Source

Should be input for PROD source datasets only.

Valid values:

  • blank or N – Do not do any packing at all.
  • Y – Pack the new production source.

Keep Memb (retain flag)

Should only be used for generated components.

Valid values:

  • blank or N – Do not retain the module on a promote.
  • Y – Retain the module when the module is promoted to the next level. Useful for Component Types where you can’t concatenate PROD/TEST/HOLD to do testing.

Build Map

This flag specifies whether or not ISPW is to store the build map for a generate at this level.

Valid values:

  • blank or N – Do not store a build map.
  • Y – Store a build map.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Compuware ISPW 18.02