DSXchange

Welcome aboard! :D You really haven't given enough information. The obvious question; what's different between development (where it works) and other environments (where it doesn't)? How many rows are processed before the job "freezes"? Do any of these get written into the sequential file? What stag...

Is the record terminator property set to UNIX-style when it should be set to DOS-style?

-3640 is not an error code; it's a process ID reported as a signed integer. "Phantom" simply means "background process" - all DataStage processes on the server are "phantom" processes. You need to reset the job after it aborts. Look in the log for a message "from previous run...". Check the braces i...

Of course the FILLER is different for different record types - that's what makes the total length the same (1000) in all record types.

'Tis really me, Arndo-san.

To clarify, the job sequence detects that the abort has been "handled" by the Exception Handler, and therefore removes the checkpoint and reports successful completion.

You can have one or the other, but not both.

Have you checked the TIME category for your NLS locale? It is in this category that date and time formats are specified. In the ODBC stage, if my memory serves me correctly, using a data element of Date will perform implicit conversion to and from internal format. Your statement that Transforms won'...

"Improper data type" is NOT from a data type mismatch in the data. These tend to generate messages of the form "non-numeric where numeric required" and so on. "Improper data type" indicates an illegal use of an opaque variable, such as a file handle or an indirect subroutine call variable. In DataSt...

Are they server jobs, job sequences or parallel jobs?

I don't believe the release mechanism will work for parallel jobs. Maybe it's been deprecated for all job types.

For some time, now, the Release mechanism has been deprecated in favour of the Version Control mechanism.

The reason this works, of course, is that dsenv is read (for example by dsrpcd) when DataStage is started. Not subsequently.

Yes. Read-only objects are those supplied with the product. There are some Routines and Transforms supplied with the product. The reason for omitting them is that they're unnecessary. They will exist in all projects (with the possible exception of plug-in stages, but these should not be transferred ...

The same range of choices that you currently have for MetaStage. This includes DB2, Oracle, Sybase, SQL Server and "UniVerse".

The intention of Hawk is to have a common repository for DataStage, QualityStage, ProfileStage and MetaStage (and AuditStage?).

Should be fun for the hackers!

What is the source - text file or database table or other?

What is the data type that contains 1234.5678 ?

Not sure where you're going with that, but without GSEMNUM they're not particularly useful. Surely if collisions on locks in the Repository were the problem, a report from SEMAPHORE.STATUS would be a useful thing? It might also be worth creating $DSHOME/errlog to capture any Engine errors. touch $DS...

Doesn't "null issues" mean that there's no problem? Or, at least, no known problem? .

(Sorry, couldn't resist.)