Client Repository structure in DS server
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 75
- Joined: Mon Jul 12, 2010 4:11 am
- Location: Chennai
Client Repository structure in DS server
Can we get the Client Repository structure (Jobs folder structure) from DS server (unix)?
Ajitha S
If you are just looking for Locations for Jobs and subdirectories, the DataStage hashed file "DS_JOBS" contains that Information.
Code: Select all
LIST DS_JOBS CATEGORY WITH NAME LIKE \...
Last edited by ArndW on Wed Mar 14, 2018 9:06 am, edited 1 time in total.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 75
- Joined: Mon Jul 12, 2010 4:11 am
- Location: Chennai
You could script a line parsing script from the following output:
$DSHOME/../../Clients/istools/cli/istool.sh export -preview -domain $domain:9445 -v -u $user -p $passw -ar /tmp/$projectName.NeverCreatedProjectExportPreview.isx -ds "-incdep $server/$projectName/*/*.*";
That should list each asset in your project. That would include jobs, table def, stage types, build ops, routines, etc... The -preview is the trick you want. It will LIST the contents of the export, but not actually do the export.
You might also want to store those other objects into your external repository so that is why I did not filter them out with the above command.
And yes, I highly recommend storing those into your version control system as well. Routines are just as important as a job when you have to rebuild your environment from scratch.
$DSHOME/../../Clients/istools/cli/istool.sh export -preview -domain $domain:9445 -v -u $user -p $passw -ar /tmp/$projectName.NeverCreatedProjectExportPreview.isx -ds "-incdep $server/$projectName/*/*.*";
That should list each asset in your project. That would include jobs, table def, stage types, build ops, routines, etc... The -preview is the trick you want. It will LIST the contents of the export, but not actually do the export.
You might also want to store those other objects into your external repository so that is why I did not filter them out with the above command.
And yes, I highly recommend storing those into your version control system as well. Routines are just as important as a job when you have to rebuild your environment from scratch.
I'm a bit confused; The LIST command I provided gives exactly what the OP wanted. For example in my small test Project, with a bit of formatting in the LIST command:
I don't have any Folders in the original "Jobs", but created a subfolder under "1_Jobs".
Code: Select all
LIST DS_JOBS CATEGORY FMT 64L WITH NAME LIKE \... ID.SUP BY CATEGORY 10:22:07
03-15-18 PAGE 1
Category........................................................
\0_General
\0_General\01_Table Definitions
\0_General\01_Table Definitions\REGTEST
\1_Jobs
\1_Jobs\99_REGTEST
\Jobs
9 records listed.
>
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Not confused, just old. Like me. The command line interfaces such as dsjob are now to be the preferred mechanism, against the day that the "UniVerse" engine is dropped.
More on that shortly, once IBM Think 2018 finishes.
More on that shortly, once IBM Think 2018 finishes.
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.