DSXchange

Check that your license is not expired.

How did you "test the SET file" and what happened?

DataStage does not keep log files - it keeps logs in database tables.

Craig would assume correctly.

Does any error message appear when you try to open the log view?

You have not provided a pathname so expect the audit file to have been created in the project directory on the server. Probably not the best place for it; next time you change the code build a pathname for the file.

Another possibility, particularly if you need to call row by row, is to create a function in C++ that is callable as a DataStage parallel routine. Compile and link the function appropriately. Then create a "parallel routine" entry in DataStage to specify the location of the object/library ...

8.7 is GA tomorrow. At least in the USA. Australian support tend to run their own tests before releasing it locally for you.

I think karthik_gana is after a complete solution from DSXchange. svSign <-- Left(InLink.TheNumber,1) svNumber <-- Right(InLink.TheNumber,Len(InLink.TheNumber)-1) svSign : Right(Str("0",20):Field(InLink.TheNumber,".",1,1),15) : Left(Field(InLink.TheNumber,".",2,1):Str(&...

Use the Rule Set management tool and look at the CLS file.

Get version 8.7 and there's a delightful new toy called the Operations Console that will give you this history.

There are several ways you could achieve this. For example list_readu is available as an operating system command. You do, however, need to invoke the DataStage engine environment (dssh) to execute UNLOCK.

You obviously have to be a bit more careful. Process the sign character (" " or "-") explicitly. Left pad your zeros to a 19-character string then append that to the sign you removed from the original number.

1) APT_STRING_PADCHAR is set to 0x00.
2) There is no CHR() function. You must use CHAR(0).

Do exactly the same steps.

The form LIST.READU INTERNAL may be useful since it returns the output of the command as a dynamic array. You code would search this using the same logic that your brain currently uses. Under the covers (behind the DS.TOOLS command) an UNLOCK command is issued.