DSXchange

If you want it bad, you get it bad.

Just add a before-job or after-job subroutine that invokes ExecDOS to invoke any command to identify the user (for example id command).

Why not just pass a string consisting of the filename, an underscore, and the date with delimiters removed? How about you reveal just how you need to "pass" this value. For example, is it in an Execute Command activity in a sequence? Where is the filename coming from? Presumably the date i...

where

hostname is the host name or IP address of the machine on which the services tier is running.

Try leaving out the -wait option.

The -jobstatus option will force dsjob not to return until the job finishes, so that its final exit status can be reported.

Welcome aboard. Sort by key then in reverse order of StartDate. Use stage variables to "remember" the previous row, and perform the date arithmetic based on whether the key has changed and the previous row's start date. Don't forget to partition by key so that all rows for any one key are ...

If I recall correctly it gets created on the fly when needed. It is not created when the project is created.

1) Yes, though not those ones. Routines directly crafted as type "before/after subroutine".
2) Yes

A different source. Rather sparse.
https://docs.oracle.com/cd/E41507_01/ep ... index.html

Then maybe your credential password has expired. Somewhere ONE (or more) of your passwords has expired. Do the detective work and find out which one it is.

I have submitted a formal request for enhancement.

Did you know that there is a new mechanismfor this - you don't need to open a support case?

Workload management queues (version 9.1 and later) are defined globally in an Information Server engine. Anyone submitting a DataStage job run request may request that the job be submitted to any queue on the system. A project may have a default queue defined, but that does not submit a canny user f...

Did you try to Search DSXchange? At least one workaround is to be found.

In the longer term, you might do well to investigate the permissions in your project folder.

What exact version of Information Server are you running, and what exact URL did you use? The URL changes at different versions.

Either the XMETA or the XMETASR password has expired. Get a non-expiring password created then run AppServerAdmin.bat to emplace the new password into the database.