DSXchange

Gosh, that's how UniVerse table storage (and Unidata table storage) is handled too! Both of these, however, were invented in the 1980s. They were also Y2K compliant from day one.

Your diagnosis "with no luck" is not helpful. What actual command did you issue, did you also issue GRANT commands, and what error message (if any) was returned from the Open command?

I'm surprised you can still get version 5.1. It's been withdrawn by the vendor, and you won't get any support for it.

Version Control does not include a check-out/check-in capability.

Its replacement (IBM Information Server Manager) will do so in a near future release, according to the road map presentations at last year's IOD conference.

Will your client support work visa sponsorship, relocation expenses, etc.? Are there any other obstacles such as citizenship/residency requirements?

None of the above seems to be related to the Information Analyzer product. Have I missed something?

No changes should be necessary. The job(s) should have been upgraded automatically as the project was upgraded.

No such thing if you have to provide selective keys. The best you can do is to find the optimum balance between array size and transaction size. The first will be a function of your row size; the second should be an integer multiple of the first.

Technically you can trim a Char data type but it is padded before being transferred to the output link. The pad character is defined using the environment variable APT_STRING_PADCHAR. A Char field has a constant size on an output link.

Question: do detail design documents exist for the Informatica implementation? In that case option 2 might not be as costly as you believe.

Another possibility is that your Director log view is filtered (probably to the most recent 100 entries, which is the default filter). If the view is filtered, the word "Filtered" appears in the status bar. Press Ctrl-T or right-click in the log background to gain access to the Filter dial...

@ID is a column name within UNIVERSE.INCLUDE. You may need to enclose it in double quotes. Or you can use the RetrieVe query language.

It's even simpler than that. Any character over DEL (127) is represented as \nnn where nnn is the ASCII code point for the character.

kumarkb wrote:Are there any issues which might occur if i try to run 7.5.x jobs in 8.x ?

No.

Provided, of course, that all pathnames, database connections, etc., have been re-created.