DSXchange

No, because all of these can easily be found in UniVerse technical manuals (to which others have linked in the past).

I'm sure these have been listed before. Did you Search DSXchange?

Without administrator access, you won't be able to.

Let's start with the mechanism by which a job can "return" anything. How do you propose to have this happen?

There are several techniques, and the one you use will affect how that value might be detected in a sequence.

Over to you.

You should be able to manage this with the Java Pack.

It does run, even though slowly. DSGetJob() actually does a lot of work.
Attach and Detach are also not without their overheads.

To implement Craig's suggestion, simply test that the selected job name is not the same as that of the calling job.

So, you're trying to break the security that your administrator has set up?

Administration tab, Log Management menu, Log View option.

DSXchange is not, in general, a forum for Cognos questions unless in relation to interaction between Information Servers suite products and Cognos, for example importing Cognos assets or having Business Glossary also query Cognos Go!.

Version 8.7. Not version 8.1.

Lucky you don't work for me. That lazy approach would not be tolerated.

HA_STATUS isn't a temporary file, though the records in it should be transient unless your high availability (HA) system decrees that a failover is necessary.

Explore the "drop on import" property for the other fields.

No. Surrogate keys are always generated as uint64. But you could change this downstream of the Surrogate Key Generator stage using, perhaps, a Modify or Transformer stage.

Create a routine to get the start and end timestamps from a job. Call this routine from a Transformer stage. Have your job process job names from DS_JOBS (filtering out "category" entries, for example NAME MATCHES "1A0X").