DSXchange

The length of each and every column, specified in the length section of the columns tab in sequential file properties.

What do you mean by 'all the rows exhausted out'. Do as i advised. That will convert your entire input to your desired output. You need a transformer because you need to add three more columns which will be the column names, which your going to hard code in the transformer. I just tested it out with...

Guys, thats not a vertical pivot. Thats horizontal pivoting. Thats exactly what the pivot stage does. But you need to tweak the source file a bit. Do this:- Feed your souce file to a transformer where you will add three more columns. Those columns will be hardcoded with the column names. So for the ...

Thats not an integer, its decimal, or maybe float. Is it in ebcidic format. Is it PicS(9).V99 ???
If its in ebcidic format then you can use the transform DataTypePicS9(). If all you need to do is get the trailing sign and bring it to the front you can do a substring and concatenate it to the front.

Sure you can. Build the script. Make sure its working from command line. Then provide its fully qualified path in ExecSH. Your done.

Do an exact search on 'No conductor nodes found in export node pool'

I know, just having a little fun

chulett wrote:No, it just means you killed yourself.

Craig, your gonna scare the poor fellow. He means, killed it yourself.

Avoid Delete. It will take for ever. Plus all that logging. Dba will scream too. Make a stored procedure out of it.

As i suspected. Now give your dba a call and ask him if there are any alive threads from your id, or whatever id is accessing the database. If he says yes then they must be hung. Ask him to kill it at the database level. This will cause your job to abort. Never stop a job that is accessing a databas...

I see a space before the trailing semicolon. Is that the case even in the your actual job ???

What is the job doing. Is it accessing a database. Give a call to your dba and ask him to kill the thread that was generated by that id. Some jobs can be a pain when it comes to stopping them. OR maybe it stopped and the status is not updated. How do you know its still running ???

You can mark it resolved then.

I did a quick search and you were using the correct syntax. Forget the exec and lets put call back. So now your OPEN statement should be call schemaname.storedprocedurename(). Try getting rid of the trailing semicolon. If that doesnt work get your dba involved, ask him to monitor if the stored proce...

ray.wurlod wrote:The space is for the sign. For example, -3.3 and +3.5 are valid decimal numbers, as is 3.2.

Many people are unaware of this fact. Maybe someone should put up a FAQ for this.