DSXchange

We use a mailto hyperlink from the short description of the Glossary Feedback term. This does not use the IBM template - it opens an ordinary (OutLook) email with only the recipient and subject filled in (users quite often change the subject - because they can - which rather thwarts any filtering we...

No elaboration is possible.

You have a string that matches "%yy%mm%dd" so use that format string to change its data type to Date.

IBM does not ship Oracle libraries.

IBM does ship third party ODBC drivers, including for Oracle.

Oracle libraries themselves are installed when you install Oracle client software on your DataStage Engine.

Does your file have a byte order mark? (There is a property in the Sequential File stage that instructs it to ignore the BOM.)

Basically it runs out of memory looking for the first comma, because there isn't one when the file is delimited by caret characters.

The Information Services Manager entries in Information Center or the manuals. Not sure which manuals (not on site at the moment), probably the Administration manual would be a good start.

That's pretty much the approach we've taken, though we allow direct email to the BG address because users complain that you have to select an existing term to use the Feedback button and don't want to do this for a new term. We then have two levels of stewards, the first examine and recommend propos...

Why not just convert the original string using a format string of "%yy%mm%dd" (with no delimiters, just like the data)?

What changed on or before "one fine morning"? Note that "nothing" is not the correct answer.

(The change may be exterrnal to DataStage.)

What Craig said.

"cc" represents the century component of a four digit year.

The first two "yy" characters in "yyyy" represent the century component of a four digit year.

I agree with how it's currently implemented.

You are concentrating on the last day of the month only. There is scope for a different function to do what you do.

(A thought - I wonder if these functions work with other calendars, such as lunar calendars?)

I have never had a problem. Obviously you can connect OK, therefore presumably the problem is no in .odbc.ini or uvodbc.ini). The most likely culprits are incorrect settings either of the metadata (for example CHAR instead of WCHAR or NCHAR) or of the NLS character map.

State the (full) requirement in words. This is called a specification, and may serve as a useful mind-focussing exercise - you may even be able to come up with your own best solution.

Use the various -log options for dsjob to identify and display the "summary of sequence run" event from the sequence's job log.

Thank you for sharing that. It doesn't happen to everyone.

Have you contacted your offical support provider?

Are you logging in as a user with sufficient role privileges and credentials?