Ken
Good point. That is another good reason to use Parameter Manager. It can default a parameter in every job where that parameter appears. That way if you have to run one job manually then it points to the correct path.
Kim.
Using of '~' (Unix Home directory) instead of hardcoding
Moderators: chulett, rschirm, roy
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Just to clarify my original posting :
I have hardcoded a directory in my DS job parameter
/u01/ascential/DataStage/Projects/Data/dsdvstud/
The requirement is to remove the 'hardcoding'
by using something of the form
~/DataStage/Projects/Data/dsdvstud/
where ~ is the unix home directory for Datastage jobs;
Thank you for all response.
Regards
I have hardcoded a directory in my DS job parameter
/u01/ascential/DataStage/Projects/Data/dsdvstud/
The requirement is to remove the 'hardcoding'
by using something of the form
~/DataStage/Projects/Data/dsdvstud/
where ~ is the unix home directory for Datastage jobs;
Thank you for all response.
Regards
I was attempting to keep my mouth shut about the requirements, but I have to speak up on this:
In our company, we utilizes links. But to reach those links, we do not use the ~ signs. We reference all of our links under the following path:
/usr/users/dsadm/Ascential/DataStage/
We do not utilize the /usr path for ANY actual file storage (except configuration files, especially since DataStage is FAR pickier on 6.0.1 with regards to $APT_CONFIG_FILES path definitions). The /usr path is usually allocated far too little of space for actual data storage (whether it is read or write).
Instead of worrying about the ~ sign, just say "/usr/users" and supply the username. Of course, it's different for some unix boxes, such as Linux - "/home" comes to mind. Instead of mindlessly following what someone may say, seriously ask them what the benefits are of using "~" instead of "/usr/users". Sometimes even with good intentions, a careless requirement only lock you into a corner you don't want to be in.
-T.J.
P.S. I sure hope you are not storing data on the same mountpoint as your actual project folders. A careless mistake here and there could cause serious trouble to occurs. Best to use different mountpoint, and different path structure. Mistakes will happens. Minimize the risk of mistakes causing dangerous consequences.
In our company, we utilizes links. But to reach those links, we do not use the ~ signs. We reference all of our links under the following path:
/usr/users/dsadm/Ascential/DataStage/
We do not utilize the /usr path for ANY actual file storage (except configuration files, especially since DataStage is FAR pickier on 6.0.1 with regards to $APT_CONFIG_FILES path definitions). The /usr path is usually allocated far too little of space for actual data storage (whether it is read or write).
Instead of worrying about the ~ sign, just say "/usr/users" and supply the username. Of course, it's different for some unix boxes, such as Linux - "/home" comes to mind. Instead of mindlessly following what someone may say, seriously ask them what the benefits are of using "~" instead of "/usr/users". Sometimes even with good intentions, a careless requirement only lock you into a corner you don't want to be in.
-T.J.
P.S. I sure hope you are not storing data on the same mountpoint as your actual project folders. A careless mistake here and there could cause serious trouble to occurs. Best to use different mountpoint, and different path structure. Mistakes will happens. Minimize the risk of mistakes causing dangerous consequences.
Developer of DataStage Parallel Engine (Orchestrate).