"Priority" designations do not seem to be respected within job execution (4 replies)
Hello,
I have the same problem, different client, different server.
It's only a hunch, but it seems to me that the priority setting is getting ignored and the sequence of the TRANSFORMs in the XLM where there is no parentid designated is what determines the sequence.
See screen shots: version 5, audit output & collapsed XLM content
I was able to secure expected priority sequence.
I've attached XML files to illustrate
Original - the XML geneated by IMan v5.0.
Revised - the XML that I edited, then re-imported to IMan. I placed all parent TRANSFORMS first and in order of Priority squence. Then job ran in the expected sequence.
(Files in next post)
XML Files
Hello all,
I recently added a few steps to an existing IMan job. These steps need to be executed PRIOR to the existing steps. Therefore, I changed the 'priority' field on each of the starting transformations. Even after saving, the XML didn't reflect those priority values. Then I edited the XML to explicitly declare the priority values. However, even after restarting services and bouncing the server, the job does NOT execute the steps in the designated priority order.
This is a problem because the steps that are meant to be priority 1 & 2 do the work of checking different network folders for rogue files and cleaning them up. These steps are a new pre-requisite from the customer, but each time I execute the job through the scheduler, the order of operations is not being respected.
Help?
Assembly Versions:
Product Update: Product Update 6
Config Version: 5.00
DB Version: 5.06