DSXchange

Have a chat with an SA, a UNIX System Admin. They can help you work through all that.

It means your call to DSGetJobInfo failed. Check $DSHOME/include/dsapi.h to check what the -1 means.

Do you really want to wait for U to help you? If not, first thing to try would be to put quotes around your Sequence name so it knows it is a string: "A_PK_SEQ".

Designer. And Ray is addressing the times when it isn't as simple as just closing the job in Designer.

No idea without more info - the difference in 'style' is line terminators. You'd need to provide details about the differences you are seeing before anyone could help.

wasimraja wrote:Can you please tell me how to run this "UTILSetDefaultParameters.bat"

I was referring to a DataStage job called "Batch::UTILSetDefaultParams", I have no idea what this Windows batch file would be all about.

ps. The utility comes in quite handy. You can 'inject' an entire set of parameters from a 'template' job into any other job(s). Or just individual parameters. And they can be added to any existing parameters or the whole parameter block can be replaced.

Nice, nice, very nice.

They stay in your Outbox until actually read. No move = no read.

Ken has a nice little utility that will do this.

Are you not ftp'ing these files somewhere else meaning some other server? If so, why try to telnet to the DataStage server?

You need the telnet prompts and credentials from the remote server.

Thanks for the reply. So if we happen to move code from one environment to another , the SDK values remain intact and start from the last_value +1 ? Yes, they will remain 'intact'. (depends on how you read the question) Simply moving jobs from dev to test will not reset the values in SDKSequences i...

pradkumar wrote:If NLS is enabled, the Data Format is set to NLS and is not editable. (NLS maps support EBCDIC data.)

Sounds like you have NLS enabled.

Try searching for something more like "Exporting nullable field without null handling properties".

Seconded.

Perhaps it would help to explain how your current 'reject counter' is implemented?