DSXchange

rafidwh wrote:But surprisingly there is no routine like "DateGenericToTimestamp"

Surprisingly, there is. Check under the 'sdk' portion of the repository.

Just a wild guess, but your third job in the Sequence is using the DateGenericToTimestamp routine and you are getting data (1994000) that cannot be converted.

I've found you can't rely on the NOTFOUND link variables for anything other than hashed file lookups. Using them with a database stage is asking for trouble. Fall back on the old fashioned 'check a key field for null' techinque to see if the lookup failed.

You can't compile anything 'checked into' a Version Control project, nor should you need to.

Or an Enterprise Scheduler like Ctrl-M could do a 'file watch' and trigger a specific job on the arrival of a specific file.

abhishekijain wrote:Suppose I have table already created in Oracle then can I import the table definition to Datastage. Please tell me the procedure if possible.

Manager / Import / Table Definitions / Plug-in Meta Data Definitions.

You have to do it as either the user that is holding the lock or as your administrative user - typically dsadm.

What I meant was while you can certainly validate Server jobs, I just don't recall ever even attempting it with a Sequence job. Sounds like it isn't even valid to do so. I'd say "deploy". Anyone else have some insight on this? I pretty much stopped validating things when it no longer became necessar...

If all you've done is pick the routine from the official list, I don't see how it is getting confused about the nature of it. It's been a long time since I've validated anything and I don't recall ever trying to validate a Sequence job... what happens when you run it? Do you get the same error?

The routine should be installed and you can check yourself via the Administrator. It lives under Routines / sdk / Utility unless you've done some rearranging. Found this in a older Ray post: Note, too, that SDK routines are not cataloged with a "DSU." prefix; most are cataloged with an all upper-cas...

There's no limit on the number of records in a sequential file. The total size of the file can be limited, however, depending on the O/S and settings like 'ulimit'...

Now, some tools or programs may have problems reading large files but that's a limit on their part, not on the file itself.

No problem. If the OP had asked for other ways to accomplish this, we could go there... or they could simply search, the whole head/tail/sed/awk thing has been posted quite a bit lately. However, since they've posted this technique and asked for help with it, seems to me that would be the best place...

Why wouldn't you have put this information in your first post? That's a pretty big clue as to what could be going on.

Have you done the whole RSA key generation thing to allow ssh to login without a password?

It doesn't... but then you knew that.

And posting "why bother" messages isn't really all that helpful, either.

The number will change from run to run, so no hard-coding. Yes, if the number is known beforehand it could be passed in as a job parameter and used directly in the constraint. However, this technique should work as well so trying to work thru why it doesn't.