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
Automizing parameter values with a concurrent architecture
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 503
- Joined: Wed Jun 29, 2005 8:14 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
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.
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.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.