DSXchange

Short answers are: 1) concatenate. 2) Intelligent job control or a 'file watch' process that kicks off the job and passes in the found filename.

Ravi, see the most recent Newsletter for details on membership. That being said, are we not still in the 'Trial period' or has that expired? It's impossible for me to tell as we don't see that button - does it still say 'Continue trial' under it? I should know this, but...

Ray's point is not that your syntax is incorrect, but that you are not correctly using it. Meaning, as he noted, that you need to check and verify that the DSAttchJob was successful and actually able to attach to the job in question before going on and using the job handle. He even provided the 'pro...

yatin.mittal wrote:Actually the key element to be specified in XML stage is for generating the output files on its basis. This will be the repetition element of the XML records.

Too late, but - yup, that is correct.

As Ken notes, the answer depends on your exact version of DataStage. Only the 7.5.x versions are certified for use with 10g and thus have an 'OCI' stage that speaks both. Before that what you have is an 'OCI9' stage that you will need to leave around and still leverage a 9i client to communicate wit...

Read up on the Folder stage and add it to the front of your job. It needs to bring the XML file(s) in and stream them into the XML Input stage so that it can parse them. Other than that, your basic job design is fine. Make sure you import the metadata from your source XML file just like you would an...

somu_june wrote:Please correct me if Iam wrong.

Oh, don't worry - people will without you having to ask.

That means $DSHOME isn't set for you. Try this instead:

Nothing else it could be, Eric. And Mr Box-o-Doughnuts has nailed it, I would think.

If the job itself didn't actual start in 60/90 seconds, it would throw a timeout error of -14. It *is* actually starting and the 12 minute "delay" you are seeing before the monitor kicks in is the amount of time it is taking your before job routine to run. Simple and small as it may be, it is the cu...

Way too much work. Convert the two dates into Internal format and subtract them - that will give you the number of days between the two dates. You can then adjust from there if you need the diff in some other 'unit'.

The other post is specific to the problem of attempting to read and write to a sequential file at the same time - not in the same job, which isn't the same thing. Your design as posted is fine, the writer link will create / write to the sequential file, finish and close it before the reader link ope...

People didn't give you much guidance in it's use, pretty much just said to use it - hence part of the confusion. I'm curious if you checked it out in the Manager - it lives under the Routines/sdk/KeyMgt branch and has a big brother called 'KeyMgtGetNextValueConcurrent'. Double-clink on each to read ...

In spite of Ray's misgivings around warnings versus aborts, Sequence jobs must be aborted in order for the Checkpoint Restarting to function as expected. Warnings don't cut the mustard.

If you don't have 7.5.x and all that fancy new Sequence job stuff, then a Warning is ok.

Not sure how much help you would need with this, but you could use USER STATUS to pass that. You'd need to store the job start time there in the first job and then the Sequence can automatically pick that up in any downstream job as $UserStatus and pass it in as a parameter. Search the forum for USE...

Simply moving them from one Category to another won't cause them to need to be recompiled. Renaming them will, but not moving them.

If you use Version Control, things there will get a little... confusing, but not something you can't handle I'm sure.