I am having a problem while using dsexport. By using the parameter /JOB , i am able to export a individual job. But the problem is , it is not exporting the job executables.
We have to export certain jobs frequently. So i am trying to automate it by giving the jobnames as input.
I wrote a batch file , which will take jobnames as input and append to the the specified DSX. But my problem is, i am not able to get the job executables.
The export is done without any problem, But the dsx doesnt contain the job executables. I think we'll just have to agree that such is the current state of the technology. You might like to lodge an enhancement request. It's not a big problem - just means that you will need to re-compile jobs after importing them.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Sounds like your workaround needs to be a DSX "cutter". Export the entire project, then keep only the header, the job and the job executable. And, of course, any dependent objects, including routines and routine executables.
Layout of a DSX (or XML) export file is easily understood by inspection.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Here's a DSX-Cutter you can use, export the whole project and then fire this script at the .dsx file. It explodes every object into a stand-alone file. You're free to expand the functionality however you like.
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
Thanks Ray and Ken for Suggesting the Solutions. I wrote my own DSX splitter in VB long way back, but that doesnt solve my purpose. Because if we are posting a job to customer means we did some modifications on that job. So definetly we have to export the job from our development area only.
I posted this thread bcoz, in some of the earlier posts i have read that we have to do some modifications of manager settings in windows registry to make dsexport to work properly. so i thought that there woluld be some settings like that to achevie my solution.