DSXchange

There are utilities for migrating Table Definitions as other DataStage components, including Version Control and export/import. And if you take this route, Version Control would give you the ability to maintain all table metadata in one specific project and then easily migrate (i.e. 'promote') it t...

The package installer is a manual process and not what I was suggesting you use. It will work, but I would think rerunning the Server installation would be infinitely less painful.

They are optional plug-ins and it doesn't really matter if they are installed in the VERSION project. They will need to be in your promotion target project(s), however. If they are missing, easiest thing to do to fix it is to rerun your Server installation and choose the option to install additional...

nag0143 wrote:Thanks, true we can only see add/delete options from administrator, but is there any way we can rename the project.??

In other words, what people are saying is 'no'.

As long as they are converted to delimited files first...

What I need to do is to concatenate these two fixed length files into one big variable length file. Well, you can't. The only time I can recall seeing 'variable length fixed width files' was where the first x bytes noted the record size... and even then you need special magic to read the darn thing...

For the record, we are using a modified version of Ken Bland's KBA Job Control Utilities. As noted - very powerful, and I'm not sure how we'd ever replicate some of the functionality in a Sequencer. For example, I just recently added a new methodology to exit from a running batch stream with all run...

The biggest difference nowadays with the BASIC job control code that we use is it does... well, 'process parallelism' for lack of a better term.

From a list of jobs and their dependant predecessors, it will (if at all possible) keep X of them running at the same time - with X being a job parameter.

No help on this, eh?

I've scoured the header files and all of the 'documented' dsapi status codes seem to only go up to 99. At least the ones I could find. Dang.

What could be the reason? It's right there in the message - someone was shutting down the database your job was connected to. Talk to your DBA.

Nope, not over 2GB. And I really don't think there was anything funky in the data or keys for that matter. From what I recall, ran twice with the same data set and it cratered twice. Deleted the hash and ran a third time and all was golden.

How long did you wait between 'stop' and 'start'? FIN_WAIT_2 statuses should eventually release themselves on their own. Eventually.

There are several posts here on using the 'debug flag' when starting dsrpcd so that it will tell you why it can't start rather than just not starting.

Yes, it's called Destructive Overwrite. Last one in wins.

Found a couple of references to this issue in the forum but no resolution. We are running a series of jobs under the control of a large amount of BASIC job control. The Batch itself is launched with a command line script from ^M that uses (among other things) 'dsjob -jobstatus' so that $? coming bac...

I'll keep that in mind, Mr Duke.