DSXchange

:? Maybe the PX stages don't log that like the Server stages do. What "row" is being logged? How are you getting from the "= 101,102" to an "in" clause inside your job's sql? You mentioned a stage variable earlier named svID - where is that being derived and how is the ...

The lock is internal to the DataStage engine. Have you tried using 'Cleanup Resources' from the Director to find and unlock your session?

Talked about that as well in the other conversation. Yes, you can copy the file to any other Project provided it has already been created there. Yes, that does mean you need to overwrite the existing file so back it up if you feel the need. And no, there's no other file that needs to be moved.

Didn't we already have this conversation?

Actually, in DOS it is 'move' while in UNIX it is 'mv'.

Go to a DOS / cmd prompt and type "move /?" for help on the command.

Right, it will be OK without them and just didn't want to overly complicate your troubleshooting needlessly if all of your values are numeric. In this case. However, your posted ORA error implied you are passing non-numeric data, hence the question. When it doesn't work for you and throws an error, ...

Why do you feel the need to quote these numeric values?

Classic problem as DataStage strips any quotes from parameters but it has no comma issue. Are all of the values numeric that you are passing in?

:idea: My biggest suggestion? Tell us your thoughts. Tell us what you've tried. Right now it just looks like you're coming here cap in hand looking for someone to hand you a solution on a silver platter, as they say. You could also have saved alot of thrashing in that other thread by putting togethe...

I don't see the connection but wondering if you change the T30FILE value back does the problem go away? Also, is it "job" or "jobs" that you have this problem with?

Can't speak to DB2, but the Oracle part depends on if you plan on installing an Oracle client on the DS server. Without the client there, you'll be relegated to only using ODBC wire drivers for Oracle access.

As noted, Sequence jobs can run both Server or Parallel jobs. However, that has nothing to do with 'getting good performance' which is all about the individual job designs, not the fact that they are being run by a Sequence.

New problem / question means you open a new post on the subject rather just switch subjects in an unrelated thread. If that was OK then we'd all just have one post assigned at birth, some of which would be virtual novels by now.

Error like? How can anyone help with so little information? Post the actual complete error and go into detail on your job design and the behaviour you are seeing.

It comes in as a varchar with what kind of data? A date? Timestamp? Something else? First use an appropriate 'StringToX' function and then go from there.