DSXchange

Hi, Thanks for your reply, Here i am referring to sequencer job, not the individual job. can you please tell me a way of differentiating sequencer job status as "Aborted/Restartable" (Restartable sequencer) to "Aborted"(Normal Sequencer) If the sequences that are not Restartable...

I believe it is the Sequence that is re-startable, not the job. The job will typically get re-set anyway.

I don't think a job can abort half way through processing records and then on restart finish off the records that it hasn't processed.

On restart the job starts from the begining again.

It looks like the XSD is not where TX is expecting it to be.

I am guessing that there would be no issue if the RunTime XSD validation was switched off.

I haven't got version 8 to play about with. My only suggestion is to raise a support call.

Had a problem with this once.

StringToTimestamp('20100101',"%yyyy%mm%dd") Does not work, although I think it should

StringToTimestamp('20100101',"%yyyymmdd") Works

for me : -WTX version 8.3.0.2 -right click-> validation on XML in WTX is ok -import from XSDs with Xerces Not sure that your issue is the same, for instance you have version 8 and you are using Xerces. I'm not sure this functionality is there in the version the original issue was posted. Post your ...

Could not connect with OBDC Stage or Sybase Stage or both?

I someone could explain me this error and how to correct this, I would be gratefull... It just looks like the XML file does not match the type tree. How did you generate the type tree, from XSD or DTD? Does the XML file validate against the XSD? Are you using the ability to do XSD validation at run...

I have some PX jobs that use a buildop as part of their reconciliation and error handling in conjunction with before and after job subroutines. Get the BuildOp to output to a link only if the condition is met. The link could do nothing, possibly connected to a peek. Then from the after job routines...

blewip wrote:Are you using the Oracle connector?

Did you clarify that you were using the Connector, not the Enterprise / Other Stage?

VijayDS wrote:I hope you understand the logic.

I understand your logic but it's flawed.

If a copy of record 5 appeared at record 10; you would want records 2,5 and 10 to be kept. Your logic would only keep 2 and 10.

paultechm wrote:Sort the input data based on the column B and enable the key change column

This is far too complex and we cannot sort the data for starters

SamYamKrishna is correct, you will need svOldCol1, svOldCol2 etc.

Should be fairly straightforward.

From your requirements I don't think any suggestion given so far will work. I believe you want any duplicates that are together to be removed yet if they come later on (after a new key) they should be kept. First of all the processing should all be done in sequential mode, or else partitioning could...

I think what you want to do will be fine.

Just select * from tablename and use RCP.

The database doesn't need a schema file. The sequential file doesn't require a schema file.

You can set the job to RCP and then only use it when you need to.

Therefore you could explicitly define some columns at the start (but you could use RCP to pick up the rest / all of them). Then you can pick up extra columns as you go through the job, either explicitly defined or by RCP.

Second option wouldn't work if there were two commas in a field.

If it were free text and they allowed commas why wouldn't there be two.