DSXchange

Re-posting as there was no answer on this since yesterday. Any solution response would be appreciated.
-------
We currently have an architecture where we will be running batch loads based on a RUNDATE on a daily basis.
There are three stages that the data batch needs to pass through.
Stage 1. Source - Standardization
Stage 2. Standardization - Cleansing
Stage 3. Cleansing - Target
In the first stage we extract based on a parameter RUNDATE.

Going forward from Stage 1-2, Stage 2-3 Im currently placing the RUNDATE, Batch_LoadID in a hash file for all the transformation required.
If another job is started at the sametime then it is possible that it would incorrectly refer to that hash file.
What is a good method to prevent this non-concurrent method in a DS architecture design? where no third party tool is used for scheduling and only Job sequence, DS designer is relied upon.
Thanks

May be u can try to use a SEQUENTIAL file which gets locked automatically if one job is using it. Or research on lockign the file till the frst job is complete.

You should create your job sequence such that operations can NOT occur in the wrong order.

You could also use any of the public semaphores (task synchronization locks) within your job design. These are described in the DataStage BASIC manual.

Neither your question nor this answer appear to have any relationship to the subject of this thread. Parameter values do not appear to have been mentioned.