Dimensions Build Configuration Symbols

This appendix describes the symbols in the Dimensions configuration file that affect the Primary Build Execution Monitor (PBEM). The configuration file, dm.cfg, is located in:

- Windows: %DM_ROOT%

- UNIX: $DM_ROOT

- MVS: MDH.V1031.MDHPARM(MDHTDCFG)

DM_MAX_PBEM_RETRIES

Specifies the maximum number of times the PBEM tries to send a message to the build server. This symbol is useful when a build server is heavily loaded.

Value Type | Integer
Default value | 5
Example | DM_MAX_PBEM_RETRIES 5

DM_BUILD_OPTIMIZE

Use this symbol to perform optimization. The PBEM optimizes the build by omitting steps that are not required. If you do not need optimization, comment out this symbol.

Possible Values | Y (Yes) N (No)
Default value | Y (set during installation)
Example | DM_BUILD_OPTIMIZE Y

DM_BUILD_OPTIMIZE_EARLY_TEST

Defining this symbol on MVS may improve performance. If you encounter templating problems try removing this symbol while you debug the template.

Possible Values | Y (Yes): enables optimization. Undefined: disables optimization.
Default value | Undefined
Example | DM_BUILD_OPTIMIZE_EARLY_TEST Y

DM_BUILD_MSGQ_SIZE

Sets the maximum queue size for messages. When more messages than the specified value are collected, the queue is flushed and sent to the build server.

Value Type | Positive whole number
Default value | 200
Example | DM_BUILD_MSGQ_INTERVAL 100

DM_BUILD_MSGQ_INTERVAL

Specifies the number of seconds before a flush is performed. If this time is reached before the queue fills up, it is flushed anyway. If you specify zero there is no interval checking and only the value of DM_BUILD_MSGQ_SIZE (see above) is important. If this symbol is not zero, the first message is always sent immediately.

Value Type | Positive whole number
Default value | 0
Example | DM_BUILD_MSGQ_SIZE 5

DM_BUILD_MSGQ_STEP

Causes the queue to be flushed on the last message for every step.

Possible values | 0: off 1: on
Default value | 0
Example | DM_BUILD_MSGQ_STEP 1

DM_BUILDERWS_URL

Specifies the URL of a primary build server that is different from the default web server specified by the configuration symbol DM_WEB_URL. The build GUI is still invoked using DM_WEB_URL. This allows the build server to exist on a web server that is different from the regular server hosting the Dimensions clients and Administration Console.

Example | DM_BUILDERWS_URL http://buildserver:8080/bws

DM_MVS_REXEC_DELETE_JCL

Deletes temporary files related to JCL generation and submission.

Possible Values | Y (Yes): delete. Undefined: does not delete.
Default value | Undefined
Example | DM_MVS_REXEC_DELETE_JCL Y

DM_BUILD_CLEAN_TEMP_FILES

Deletes listing files and the BOM after they are sent to the build server (user and system generated files).

If you set this variable to No, temporary files used for a build are preserved and output files created by DMSAVESTDOUT and DMOSTDOUT are not affected.

Possible Values | Y (Yes) N (No)
Default value | Y
Example | DM_BUILD_CLEAN_TEMP_FILES Y

DM_DELIVER_RETRY_TIMEOUT

Specifies the timeout period (in minutes) for attempting to deliver files back to a stream.

Default value | 0
Example | DM_DELIVER_RETRY_TIMEOUT 5

DM_BLD_ERROR_INVALID_REVISIONS

When an item revision is not at the current stage that is being built, use this symbol to control whether the message that is issued is an error or a warning. If it is an error, the build is stopped before it is launched. For details, see Checking Item Revisions are at the Requested Deployment Level.

Possible Values | N (No): warnings are displayed and the build is launched. Y (Yes): error messages are displayed and the build is stopped before it is launched.
Default Value | N
Example | DM_BLD_ERROR_INVALID_REVISIONS Y

DM_BUILD_DMORDERING

Globally enables or disables build ordering. For details, see Build Ordering.

Possible Values | Y (Yes) N (No)
Default Value | Y (YES)
Example | DM_BUILD_DMORDERING YES