DSXchange

Items will have a range of difficulty and be presented as multiple choice, probably with four choices per item. The only feedback given will be whether the choice selected was correct or not. It is envisaged that a typical exam will contain 75 questions and have a time limit of 90 minutes. There was...

You can not do this with a Hashed File stage. Add "-64bit" to a mkdbfile command executed as a before-job or before-stage subroutine. The Hashed File Calculator will give you the correct command syntax, which you can copy via the Edit menu. Or use a UV stage with its DDL edited to include DATA, DICT...

It is not enough to add the user ID to /etc/group. The information must also be recorded in shadow files, which means you must use the correct utilities (such as useradd) to create the user ID and assign same to groups.

Check out the extended column properties in the Sequential File stage - you scroll right to find them. One of the properties is "contains line terminator".

Make it an SEP.

SOX requires that processes must be documented, and then that an audit proves that the processes are followed.

Surely it's the owner's (or the security people's) responsibility to document security access. Then you simply have to follow what they've documented.

Try creating a synonym for @ID in the UniData file dictionary, maybe called ID, and use that in the UniData stage.

Seems to me you need to work on your employer to get you some training! Shouldn't be too difficult, since your employer is the vendor!

The status (hashed) file records the status of the job, its active stages and its resources.
The log (hashed) file records events logged by the software.
They are independent of each other.

Use the Field function to extract everything up to the first delimiter. Indeed you could probably use the field function for all four output fields, since you've eliminated redundant delimiter characters using Trim(). svTrimmedLine is defined as Trim(InLink.SourceLine, ",", "A") F1 is defined as Fie...

This error usually means that the job is not compiled, or is not in a runnable state.

The installation guide is a complete and accurate reference. Follow its guidance precisely. All needed scripts are supplied on the media - you will not need to do any script creation. You may - depending on your UNIX - need to modify some kernel parameters. To do this you need administrative (superu...

The UNIX command man signal will inform you about signals. Here are the most common ones. An asterisk indicates that a core image is dumped. Value Description 1 (SIGHUP) hangup 2 (SIGINT) interrupt 3* (SIGQUIT) quit 4* (SIGILL) illegal instruction 5* (SIGTRAP)...

You don't need to create a before/after subroutine. Use ExecSH, which is supplied with DataStage. I believe that this is sufficiently generic a solution.

What do you mean by "missing"?
By "run time" do you mean when running on the development environment or in a test or production environment? If the latter, how do you move your jobs from development through test to production?

You CAN run the UNIX commands. Get MKS Toolkit or CygWin. You get MKS Toolkit for free with DataStage EE 7.5x2.