DSXchange

Stefan - I think the ConnectDirect or mainframe issue is that some files can have compressed spaces which are not interpreted/expanded correctly when doing such transfers. The compressed spaces binary ... what are all the connection details are need for transfer the fail from Mainfram to Unix/local...

How Can we connect and transfer data using the command-line FTP program? command line in the sense? The documentation for the FTP stage is sufficient to use the stage, but it doesn't explain the complexities of using FTP on mainframe; the assumption is that you will get that information elsewhere. C...

is it possible using FTP Plug-in Stage.

chulett wrote:Have you tried using the ODBC stage?

yup... ODBC stage dont have an option to exec Teradata SP's

We are trying to execute teradata stored procedure in datastage.
Can anyone suggest a way to do this.

The Teradata TPUMP utility expects the log table to be empty. It's not a DataStage requirement. ... thank you... is there is anyways to overcome this clearing statement..... what i mean to say is, inside TPUMP utility i am writing "delete from log_tablename", but few not agree for this.. ...

hi all, i am using TPUMP stage to load the teradata table.. whenever the jobs get aborted because of some error after rectifing the error if i rerun the job without clearing the contents of the log table whcih is created by TPUMP stage it will abort the job by throwing the following error ' log tabl...

JoshGeorge wrote:Do a search in this forum as well as google for 'SIGINT'. If someone has stopped this job also you can get this message.

no... for the very first time i run this job and noticed this fatal error...

hi,

can anyone pls help me in solving this fatal error.. when i run a job i am getting the follwing error.

"main_program: ORCHESTRATE step Execution termination due to SIGINT"

[quote="Cr.Cezon"]perhaps the problem is in the metadata of the column.
see then length of the columns char.

i saw it, the length of the datatype is same as in SQL server.. i dont know still why i date and few char column getting truncated..

ArndW wrote:I am sure that the truncation is coming from your job or table definitions and an implicit conversion and not from a bug. Just a thought - do you have NLS enabled (i.e. a double-byte or multi-byte sys ...

sorry i dint get.. i dont know about NLS.. where i'll get this info.. could u pls tell me?.

hi, In my project i am exporitng data from SQL server to DataSet using ODBC Stage. The problem is while extracting from SQLserver using ODBC, the data is getting truncated in some of the fields such as char and datetime. here is an example In SQL the value of Char column inst_month is '200601', but ...

I infer from your post that you have ensured that the actual data is 6 character - what if you put a SELECT '*' + cast(inst_month as varchar(5)) '*' as inst_month from YourTable[ ...[/quote] yup..thank you.. now it is possible to extract the data as it as. but i gave cast(inst_month as varchar(10))...

If you do a "view data" on your ODBC stage does the data show as truncated already? If not, then I would suggest you check your dataset schema to see if it really is CHAR(6) and not something smaller. ... yup it is char(6) in both the ODBC stage and Dataset stage.. it is truncated in the ...

ArndW wrote:What about your SQL SELECT clause, might you be usnig some conversion or CAST() in there? ...

no.. i am not using any conversion..