DSXchange

The 'official' answer would be to make the project a Protected project via the Administrator. Another answer is to use Version Control to promote everything into it as it can set each individual component to 'read only' during the process.

Windows is not case-sensitive so that's not an issue here. One thing confusing me - you've now sometimes said you are using the "Execute Command" stage and here the "Command Activity" stage. Can you verify exactly which one we're talking about? Not sure it is an issue here, just ...

And welcome to E.F. Codd's world of three-valued logic: True, False and Who the Heck Knows.

Or "[Timed out while waiting for an event]" is another good search candidate. As noted, discussed here many many times.

Probably not going to make any difference since the parameters as passed are getting resolved. Are you certain there are "*.csv" files in that location and which are accessable to the DataStage job? The first (not totally conclusive) test to run is to start a "cmd" window so you ...

I second the use of "&&" as the command separator rather than a semi-colon. As noted, it requires the preceding step to complete successfully before allowing the next to execute, compare that to the semi-colon which blissfully passes execution down the line regardless of the mayhem...

$DS_LOGIN is a filename containing credentials: server, userid, password. And $DS_SERVER tells it which record in the file to use, looked up by matching server name. As noted, you may be able to leave them out but if not and you remove the "-file ${DS_LOGIN} ${DS_SERVER}" bit you'll need t...

Possibly the 'Windows only' Command stage which I've never seen. Can you post the log message that shows the actual command that was executed after the parameters were resolved? I assume this logs one like the Execute Command stage does. For Windows without any MKS Toolkit like functionality, rather...

Do we have to guess what's in the container?

Ah... didn't notice you had the arguments 'backwards'.

Short answer? Nope. :( Sometimes you can 'pre-count' the data and pass the number in as a parameter for use in a constraint or derivation. Some people will cat a known 'end of file' record onto the source or into the stream so you can tell when you've hit the end. Another thought relates to 'group c...

Now, that depends on how you read the 'IN' statement in the OP. As written, it is syntactically equivalent to if OKCSCD = 'DE' but if you read it as if OKCSCD like '*DE*' or that the field contains the substring 'DE' then the Index() is appropriate.

Post the unedited log message (copy/paste) that shows the 'executed command'. And answer the question about 'fil1'.

Yes. That guide was written pre-PX from what I recall.

You get this error when - compile time, run time, what? Also, is "fil1" a local variable you've built as well?