When there are two or more entries with the same job name, in the execution list of the Deliver Job Name Translation Table (representing jobs with the same jobname but with different stepnames, procsteps or ddnames), the subsequent
similar entries are ignored and the report could be assigned a Report ID of UNDEF.
For example, if the Deliver Job Name Translation Table contains the following:
JOBNAME1 JOBNAM1
JOBNAME1 JOBNAM2
When a job starts, Deliver compares it to the list of execution jobs in the table, and it selects the first entry that matches the execution job name.
After the translation is done, Deliver checks the stepname, procstep and ddname from the job definition.
If all these fields match, then the Report ID is properly assigned and the data is processed.
Should another job start, with the same job name, Deliver compares it to the list of execution jobs in the Job Name Translation Table, and it again uses the first occurrence found for the job name in the table.
After the translation is done (and Deliver checks the stepname, procstep and ddname from the job definition), if some of these fields do not match, then the ID of UNDEF is assigned and the data is processed under that name.
Deliver reads the Job Name Translation Table from the top down.
The subsequent occurrences, having the same job name, will never be used.
In the below sample, from the Active Report List, note where the report ID of UNDEF was assigned for a job that would have otherwise gone by the name of JOBNAM2:
CA-Deliver - Active Report List (1) ------------------------------------------------
Command ===>
Job Def Exec Exec
Sel Report ID Name Jobname Jobid Status
==> * * * * *
STEP1-JOBNAME1 JOBNAM1 JOBNAME1 JOB14951 QUEUED
UNDEF JOBNAM1 JOBNAME1 JOB15031 QUEUED
************************************* Bottom of Data *******************************
To ensure that reports are not assigned an ID of UNDEF, change the name of the execution job so that there is no conflict in the Job Name Translation Table.