DSXchange

C. I would assume so, yes.

The Sybase OC (Open Client) stage is a native stage for Sybase, probably more suitable to Server. Me, I'm not suggesting anything. You and yours need to decide what is appropriate to use.

Works fine for me without any need to log in. However, the link to the "full article" has gone 404 it seems.

Does the stage have an Input or Output link connected to it? Without at least one of those there's no place for columns.

So do you have a single or double quote inside your quoted string? Guessing the latter even though your example shows the former.

So, yes if you then take that byte stream and use the Sequence stage to write it to disk. However, with all of the possible complications with metadata and inadvertent transformations that entails, I second Ray's advise to script something via traditional command line ftp. You'll need a script regar...

But of course!

I thought from postings here, having no direct experience, that the DB2 stage wanted dates (and thus perhaps timestamps as well) in internal format.

Directly in a Trigger expression? Not as far as I know. You'd need to use a RoutineActivity to run it and then check the results in a downstream trigger.

The Help page for that "Automatically handle" option explains what you need to do. Basically, you need to make the Sequence understand that you are handling any errors so it doesn't do it for you. Typically, that involves either a specific "Failure" trigger or after checking for "Success" include an...

Typically, one would post the results of the query rather than just declaring it good. However, it seems to me you are rapidly moving to a state where you need support. Have you opened a case with your official provider yet?

So, when you said "Batch" you literally meant "Batch colon colon" as in hand-coded job control code maintained via the Director? Huh. No wonder the checkpoints question didn't make sense, I was specifically referring to a Sequence job. As noted (and regardless) I saw the same behaviour you did. Now,...

SEQ? Do you mean Sequence job? If so, there are known crash bugs when editing a Sequence job and there is a specific client patch to resolve them. Ask your official support provider to... well, provide it.

Ray Wurlod [genuflect] has provided some date routines here that might be illuminating. Save the file to your PC and "Import" the resulting .dsx file via the Manager into your dev project.

Once loaded, double-click on them to see the source.

Only bit of fun with the fix is that it is a client-side patch that affects the code generated when the Sequence is compiled. That means if someone that doesn't have the patch ever compiles the job, it will go right back to being broken.