Hi All,
Our UAT and Prod datastage env are hosted on the same server. Unix flle system is maintained using separate directories.
Requirement is copying datasets and surrogate key stat files from UAT directiroy to Prod directoy (on same server).
Does this copy pose any threat? is there any possibility of datasets and and stat files get corrupted?
Copy datasets and stat files
Moderators: chulett, rschirm, roy
Copy datasets and stat files
Rumu
IT Consultant
IT Consultant
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Provided that you use the orchadmin command (or the Data Set Management tool in Designer) to copy the Data Sets you should be fine.
Copying just the descriptor file, however, is a Bad Idea.
Make sure that the state file is not in use when you copy it. Why do you want to copy the state file? Ought not you to be using a different set of generated keys in the new environment? The sets of keys from the separate state files will quickly cease to be synchronized.
Copying just the descriptor file, however, is a Bad Idea.
Make sure that the state file is not in use when you copy it. Why do you want to copy the state file? Ought not you to be using a different set of generated keys in the new environment? The sets of keys from the separate state files will quickly cease to be synchronized.
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.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Could you please get yourself a premium membership? You have posted 200 times, so are clearly deriving a benefit.
Premium membership is the mechanism through which DSXchange is funded. It pays for the hosting and bandwidth costs. (Perhaps you've noticed the lack of advertising on the site?)
Premium membership is the mechanism through which DSXchange is funded. It pays for the hosting and bandwidth costs. (Perhaps you've noticed the lack of advertising on the site?)
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.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
If you copy only the descriptor files, then both your prod and your non-prod jobs will be (over)writing the same Data Sets. Last one in wins. This is a Bad Idea.
The descriptor file contains (among other things) the pathnames of the segment (data) files making up the Data Set. A copy of the descriptor file only would point to those same pathnames.
Instead, create the Data Sets afresh in the production environment. That way, even if the resource disk is shared between prod and non-prod, the segment files will have different names. And have the directory pathname where the descriptor files are stored be specified through a job parameter, and different in the prod and non-prod environments.
The descriptor file contains (among other things) the pathnames of the segment (data) files making up the Data Set. A copy of the descriptor file only would point to those same pathnames.
Instead, create the Data Sets afresh in the production environment. That way, even if the resource disk is shared between prod and non-prod, the segment files will have different names. And have the directory pathname where the descriptor files are stored be specified through a job parameter, and different in the prod and non-prod environments.
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.