DSXchange

Try also trusted third-party root certificates store.

The parameter values entered when a job is (re-)scheduled are stored in one of the hashed files in the local DataStage repository.

It could be that the exit status of the call is set to that of the DataStage job, where 0 is "running", 1 is "finished", 2 is "finished with warning", etc. Your caller may be interpreting the non-zero code as an error.

kduke wrote:Why use a parameter set if you are not going to load the values into it?

Parameter Sets are cool for setting up different sets of default values for different environments, even if you don't want to update them dynamically.

May the 4th be with you.

You are correct that there is no Sybase Connector stage. For general purpose work the Sybase Enterprise stage should be preferred. This supports parallel processing. The Sybase OC stage uses the old plug-in architecture, and is less efficient than the Sybase Enterprise stage (and has slightly less f...

That definitely sounds like one for a support call, and ultimately for a patch (since this is "their" Java code, not yours).

... or a routine activity or even a job activity. (I'd prefer to use a server job here.)

You probably need to add the certificate to the trusted root certificates store and/or the trusted third party root certificates store, and to be a local Administrator of the client machine when you're doing it.

Please check the job log of the sequence job. Report back the detail of the first Fatal message. Also report back the content of the first Fatal mesage in the log of the job itself when run under control of the sequence.

Can you read the files if you are explicitly naming them (that is, not using wildcards of any kind)? We also need to understand exactly what you are trying to achieve here - I'm presuming there are two Sequential File stages (possibly in two jobs) looking for files matching the given pattern. Does t...

and i guess shared container have to insert the records into database table rather than DS file right? Only one writer at a time is supported for any one file, but you could use a different file for each like (parameterize the file path for the shared container), and post-process them. You can also...

Definitely can achieve this with a sequence. Do you want one email per file, or one email to which all files are attached?

The -status option should not be available with the -ljobs option in version 8.5 (or any version). The -status option reports a job status once a job run request has been fulfilled.

You could script something (probably using awk or sed) to parse the output of dsjob -ljobs command.

That pattern does not match the Control file.

Any reason you can't use the asterisk?

I presume you have changed the Read Mode property of the Sequential File stage to "File Pattern".