We recently upgraded to ESM from TMSM in our dev / test environment.  It looks like the 'job' in the ESM explorer corresponds with the resourceid and not the JobName.  For example, an application "general ledger" (gl-prod) runs a data load that has multiple jobs.  The very first 'load' step has a job name like 'glload'.  Subsequent jobnames for the 'gl-pr