5.4.4 - Dependency Options and Limitations - Teradata Warehouse Miner

Teradata Warehouse Miner Model Manager User Guide

prodname
Teradata Warehouse Miner
vrm_release
5.4.4
created_date
July 2017
category
User Guide
featnum
B035-2303-077K
There are a number of options and limitations regarding dependency.
  • When the Depends Oncheckbox is selected, you must enter the external application ID or select a scheduled model ID from the dropdown list. Retry is optional.
  • The external application ID is a name assigned by the user and is not validated on this screen. In assigning this name, do not begin the name with "_MM_" or include a less-than '<' or greater-than '>' symbol in the name. To let the Model Manager know that the external application has completed, a row containing the external application ID must be inserted into the mm_app_status table in the Model Manager metadata database {MM_META_DATABASE} by the external job or script. In the example below, the Model Manager metadata resides in database {MM_META_DATABASE} and the application has been called App1.
    INSERT INTO {MM_META_DATABASE}.mm_app_status VALUES ('App1', CURRENT_TIMESTAMP, 1);INSERT INTO {MM_META_DATABASE}.mm_app_status VALUES ('App1', CURRENT_TIMESTAMP, 1);
  • The model ID must be an existing ID of the model already scheduled to run. The dropdown menu contains only the available models the current model can be dependent on.
  • When the Retrycheck box is selected, you must enter the length of the delay in minutes and the maximum number of attempts.
  • The delay in minutes must be less than or equal to 9999 and the max attempts must be less than or equal to 99.
  • Additional limitations are made on the valid values of these fields based on whether Repeat is checked and what the Repeat interval is.