DSXchange

I have a vague memory that the tcp times reported by ndd are in microseconds (rather than milliseconds), but would be happy to be corrected.

Whilst what you ask can be done, it's unlikely we can provide an exact solution because we don't know enough about precisely what is locked. But rather than await interminable correspondence on this thread, why not Search DSXchange. You will need LIST.READU to determine the owner of the lock, and UN...

You could use a server routine, using ReadBlk and WriteBlk statements (which read/write blocks of N bytes) as well as the Status statement that can give things like the total size of the file. That the file is EBCDIC is neither here nor there when you are processing bytes.

DataStage is a bit brain dead on this one - it reports the alert whenever there's a mismatch, even where the target is larger than the source. Use a message handler to demote it to informational. Or force your metadata to match, perhaps via a Copy or Modify stage.

You also need to set PATH to include ${PXHOME}/bin or to specify the full pathname of the orchadmin command.

Yes, but done differently. In a server job use a Filter command cat file1 file2 in the Sequential File stage - the stage reads stdout of the cat command.

That's not how it works, folks. Irrespective of the degree of parallelism you only get one data set between each pair of operators. Remember that the Score is distributed separately to the section leader process on each node. What you need to look at here is the fact that DataStage has inserted some...

The original poster has removed the original questions and all his/her responses. It is not clear why.

From memory (once again I am in an airport lounge) the Exception Handler has a couple of activity variables accessible downstream of it, one of which identifies the failed activity that was caught.

Are you tracing a stage or debugging in the slow job and not in the fast job?

Not in DS.AUDIT, but in field #7 of UV.ACCOUNT record for the project. Also (from memory) in the UV_SCHEMA record for the project.

DataStage *can* work with IMS datasets and viewsets. But you will need to use a "mainframe" job (extra cost) to do so. As the name suggests, a mainframe job runs on the mainframe - DataStage generates COBOL source plus JCL to compile and run the same.

Welcome aboard.

Is this XP Pro or XP Home? The installer *should* take care of setting CLASSPATH but, it seems, has not done so in your case.

What EXACT version of DataStage client? (You can find out from Help > About.)

Through your support provider, probably the folks who sold DataStage to you. The variable names localVarxxx are generated names in the code, and should not have ^A (presumably Ctrl-A) instead of a. Ctrl-@ is one way to represent NUL (0x00); it's not clear from what you posted where this is occurring...