DSXchange

Right. We got that. As noted, you simply need to return a non-zero error code when the job fails. Post your code.

No, I meant fired. Firing is what neurons do, passing a small electrical charge... <snipped a rather lovely bit of brain science> Yeesh, I knew I should have used a different emoticon so the fact that I was joking would be more obvious. Nothing I didn't know, but I'm sure you've just started someon...

Huh... ok. Also saw one post with the error where the response was a possible permissions problem. Curious what the 'checker' turns up. Is it just a checker or is it a fixer as well?

Wait... you wrote a routine that runs a job and you run that job in the 'After Job' area of another job? Why would you want to do that? Seems like a Sequence job would be more appropriate to run the two jobs in a serial fashion... If you pursue this course, then yes - you'll need to detect errors i...

It may be this that's fired your neurons. Hopefully that's not a typo and you really meant to say 'fried'. Mostly meant the 'host' designation. Not having had the pleasure of a Windows Server to play with, I'm just guessing here. What do you put for the IP when everything is playing on the same box...

I would assume your repository indexes are blown. Make sure there are no other connections to the project in question and rebuild them. You can either do this directly using DS.REINDEX or using Option #2 - Rebuild Repository Indices - from the DS.TOOLS menu, both accessed from a TCL prompt. The cave...

1. 'Binary' executable for the Transformer stages, OSH scripts for the rest.

2. Internal product gobbledygook. Don't lose any sleep over it. As long as the 'another environment' is properly setup and at least the same version, you'll be fine.

The key word there is 'associated'. AFAIK, it just means to automatically include the source associated with any of the executables you select. Since you've already included '(All)' Job designs, enabling that option for the Job executables would be redundant. Since I explicitly extract what I need, ...

OConv with the MTS conversion code. You've already got 'seconds since midnight', which equates to internal format, so all you need to do is the appropriate 'output conversion'.

I inferred from the other post that started this that the Server install is on the same PC as the Client. Don't you need to connect in a slightly different fashion in that case?

Again, your step #3 is problematic. Setting the value of a job parameter before job is invalid and unsupported and only works if you have 'hacked' into the jobs to accomplish this. I've only seen one person posting here with a working methodology, and that from an Ascential consultant (from what I r...

DSguru2B wrote:

kamal kishore wrote:Hi Brian Kernighan,

Wow, he called me Brian Kernighan

Not the first time someone has looked at your sig and used whatever name was there. Who will you be next, I wonders?

What did you find when you searched the forum for that? Quite a number of conversations, I'd wager, as it's a popular topic.

Command line where? Client or Server? If 'on the TEST box' means you are looking for a UNIX solution, check to see if your version of dsjob has the -import option.

You should probably mention the name of your 'VC software' when posting about it. Saying Version Control implies the DataStage product. Since you are exporting and importing source only via the Manager and your third party versioning software, then yes you will have to compile as a final step. Use t...

If you are using the Manager for this, then your answer depends on what you are exporting from DEV and importing into TEST. If you include executables, then no, you should be all set to go. If you are just transfering source, then yes you'll need to recompile everything. Your mix of VC and Manager i...