Last TRACKDEF statement in the JTDT member is ignored
search cancel

Last TRACKDEF statement in the JTDT member is ignored

book

Article ID: 55458

calendar_today

Updated On:

Products

ESP Workload Automation

Issue/Introduction

The last inserted TRACKDEF statement in the JTDT member is not being recognized.

Resolution

The most commonly known reasons are: 

1. Undefined special characters in the mask. Special characters must be predefined in the JTDT member using the WILDCARD statement. 
There is only one special character (-) known by ESP as a default masking character. All others must be predefined in JTDT as follows:

**********************************************************    
WILDCARD # 0-9 /* Numerics */    
WILDCARD $ A-Z /* Alphabetics */    
WILDCARD @ @#$ /* Nationals */    
WILDCARD + 0-9A-Z /* Alphanumerics */    
WILDCARD . ABCDEFG /* Fisrt 7 characters */
TRACKDEF TSU NOTRACK     
TRACKDEF ...    ..................
**********************************************************    

2. Wrong sequence for the TRACKDEF statement. The order of these statements are important. The most generic statement should be the last one in the table. For example:
    TRACKDEF JOB NAME(PROD-) MODEL(PROD1)    
    TRACKDEF JOB NAME(-) MODEL(MODEL1)

3. JTDT was not reloaded.  Reload the JTDT by issuing the command 'LOADJTDT dsname' from the Master and all proxies.

4. The job has not yet run after the JTDT table is reloaded so the change has not gone into effect.