I need a DSX-Cutter
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 483
- Joined: Thu Jun 12, 2003 4:47 pm
- Location: St. Louis, Missouri USA
OK. I looked at the bat file in the DataStageBackup.zip. It uses dsjob to get a list of projects to back up. I don't have dsjob loaded on my PC. I assume that is because I only have the DataStage client loaded on my PC, not the DataStage Server.
So is the best solution to 1) get a list of projects to backup another way, possibly just hard coding them? If so, how might I do this without dsjob? Or 2) load the DataStage Windows server on my PC? or 3) Something else?
Thanks for your help,
Tony
So is the best solution to 1) get a list of projects to backup another way, possibly just hard coding them? If so, how might I do this without dsjob? Or 2) load the DataStage Windows server on my PC? or 3) Something else?
Thanks for your help,
Tony
Forgot about that little conundrum. From the header of the file:
From what I recall, I took the 'dsjob' executable and the dll from the Client cdrom we had. I also seem to remember that they include it automatically nowadays when installing the 7.5 client.
What exact version do you have, Tony?
Code: Select all
:: Required Components:
:: dsjob.exe (Windows Version)
:: (also requires vmdsapi.dll)
:: Advised to place both files under Windows System directory.
What exact version do you have, Tony?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Premium Member
- Posts: 483
- Joined: Thu Jun 12, 2003 4:47 pm
- Location: St. Louis, Missouri USA
-
- Participant
- Posts: 5
- Joined: Mon Oct 11, 2004 6:39 am
-
- Premium Member
- Posts: 483
- Joined: Thu Jun 12, 2003 4:47 pm
- Location: St. Louis, Missouri USA
Dick,
You can extract them from the data1.cab file in the DataStage Windows Server install. I downloaded a InstallShield CAB file extractor utility and used it to extractthese files from the Data1.cab file.
You need to put these in the same directory as the dscmdexport.exe. FYI, you also require the DSRPC32.dll and DSCLNT32.dll files, but they're present in the directory with rest of the DataStage software...
Good Luck,
Tony
You can extract them from the data1.cab file in the DataStage Windows Server install. I downloaded a InstallShield CAB file extractor utility and used it to extractthese files from the Data1.cab file.
You need to put these in the same directory as the dscmdexport.exe. FYI, you also require the DSRPC32.dll and DSCLNT32.dll files, but they're present in the directory with rest of the DataStage software...
Good Luck,
Tony
-
- Participant
- Posts: 5
- Joined: Mon Oct 11, 2004 6:39 am
-
- Participant
- Posts: 5
- Joined: Mon Oct 11, 2004 6:39 am
Job executables
We are very :D about the ParseDSX and use it for the integration of Datastage and CCC Harvest (version control).
When we promote a package containing Datastage-components to a next stage (e.g. test) and want to import these components (jobs) into the test-environment, we face some problems.
Importing the whole project-file is of course no problem, but importing jobs will fail , because the job-file lacks the job executable.
How do I achieve that the job-export file does not only contain the job, but also the job-executable What do I have to change in the DSX-cutter
When we promote a package containing Datastage-components to a next stage (e.g. test) and want to import these components (jobs) into the test-environment, we face some problems.
Importing the whole project-file is of course no problem, but importing jobs will fail , because the job-file lacks the job executable.
How do I achieve that the job-export file does not only contain the job, but also the job-executable What do I have to change in the DSX-cutter
Why not use the Version Control utility that comes with DataStage to do the actual promotion in addition to what you are doing with CCC Harvest? Save you all those export/import hassles and will compile jobs in the project they are promoted to, along with marking the jobs Read Only outside of development. Can do dependencies checks, etc etc. Better all around. IMHO.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Re: Job executables
Steve posted the program to share with the global community. If you would like it customized, you can send an email to Steve. The reason we didn't put executables into the cutter is because sometimes you lose synchronisity between source code and executable. You can always mass-compile (we have a faster program than the Manager wizard, had it for years, that even does routines) after import. I don't know what your failure issue is on import, as executables are not required.dickspaans wrote:What do I have to change in the DSX-cutter
Kenneth Bland
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
How do I achieve that the job-export file does not only contain the job, but also the job-executable ?
Look about half way down the Export page. There is a selection check box for job executables.
Look about half way down the Export page. There is a selection check box for job executables.
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.
Re: I need a DSX-Cutter
I just tried the ParseDSX.pl script under Centos4.3 (RHEL) - Perl 5.8.5 and Cygwin - Perl 5.8.7 and here is what I get as the output under both platforms:
You'll notice that the permissions on the directory created are weird.. in fact I can't 'cd' into it until I do a 'chown'.. The contents of the directory is empty also..
My Perl foo is pretty weak.. so I tried the script on two different platforms before I harassed this forum.
thanks!
Code: Select all
mmarch@joberh0206 ~/DSXplay
$ ls -al
total 72
drwxr-xr-x+ 3 mmarch Users 0 Apr 4 08:49 .
drwx------+ 5 mmarch ???????? 0 Apr 4 08:21 ..
-rwxrwxrwx 1 mmarch Users 19676 Apr 4 08:21 CatDSX.pl
dr----x--t+ 2 mmarch Users 0 Apr 4 08:49 DF_FormatMsg
-rwxrwxrwx 1 mmarch Users 27433 Apr 4 08:21 DF_FormatMsg.dsx
-rwxrwxrwx 1 mmarch Users 21259 Apr 4 08:21 ParseDSX.pl
My Perl foo is pretty weak.. so I tried the script on two different platforms before I harassed this forum.
thanks!
No.. just the command and the dsx file name.
Code: Select all
$ ls
CatDSX.pl DF_FormatMsg.dsx ParseDSX.pl
mmarch@joberh0206 ~/DSXplay
$ ./ParseDSX.pl DF_FormatMsg.dsx
mmarch@joberh0206 ~/DSXplay
$ ls
CatDSX.pl DF_FormatMsg DF_FormatMsg.dsx ParseDSX.pl
mmarch@joberh0206 ~/DSXplay
$ cd DF_FormatMsg
bash: cd: DF_FormatMsg: Permission denied
mmarch@joberh0206 ~/DSXplay
$ chmod a+rwx DF_FormatMsg
mmarch@joberh0206 ~/DSXplay
$ cd DF_FormatMsg
mmarch@joberh0206 ~/DSXplay/DF_FormatMsg
$ ls
mmarch@joberh0206 ~/DSXplay/DF_FormatMsg
$
Use the correct syntax:
and put some jobs into the .dsx file. I'm assuming you've just got a function.
Code: Select all
Syntax: ParseDSX.pl -h -l<ListFile> -o<OutputDir> -s -v -y <DSXFile>
Kenneth Bland
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
Ok.. I had the boys in the lab give me a 176MB DSX file to play with. This time the ParseDSX.pl script dumped a bunch of stuff to the console as it parsed the file.. here is a snippet of that:
and here is an list of the root after that..
.. notice the perms on the two output directories..
..notice.. the DSX files that the script said would be there.. were not ..
This happens on RHEL and Cygwin.
Code: Select all
../ParseDSX.pl -o DUMP2 -s Project.dsx
*snip*
Writing File: DUMP2/jobs/Fbob_Jobs/Test01.dsx...
Writing File: DUMP2/jobs/Jim_Jobs/test1.dsx...
Writing File: DUMP2/jobs/Jim_Jobs/test2.dsx...
Writing File: DUMP2/jobs/Jim_Jobs/test3.dsx...
Code: Select all
mmarch@joberh0206 ~/BigDSX
$ ls -al
total 172525
drwxr-xr-x+ 5 mmarch Users 0 Apr 6 10:46 .
drwx------+ 6 mmarch ???????? 0 Apr 6 09:02 ..
dr----x--t+ 3 mmarch Users 0 Apr 6 10:46 DUMP2
dr----x--t+ 3 mmarch Users 0 Apr 6 10:45 Dump
Code: Select all
drwxrwxrwt+ 2 mmarch Users 0 Apr 6 09:22 Project
-rwxrwxrwx 1 mmarch Users 176662805 Apr 6 08:53 Project.dsx
-rwxrwxrwx 1 mmarch Users 160 Apr 6 08:53 Project2006_04_06_08_26_00.log
mmarch@joberh0206 ~/BigDSX
$ find .
.
./Dump
find: ./Dump: Permission denied
./DUMP2
find: ./DUMP2: Permission denied
./Project
./Project.dsx
./Project2006_04_06_08_26_00.log
mmarch@joberh0206 ~/BigDSX
$ chmod -R a+rwx DUMP2/
mmarch@joberh0206 ~/BigDSX
$ find DUMP2/
DUMP2/
DUMP2/jobs
DUMP2/jobs/Fbob_Jobs
DUMP2/jobs/Jim_Jobs
This happens on RHEL and Cygwin.