DSXchange

I would like to get information on my system's datasets into a data file; right now I am issuing a "orchadmin describe -l {mydsfile}" but I am having to parse the output myself. Is there some other method or existing procedure to collect all this information in a compressed form?

It looks like you did not declare the #DTS_DIR_Param# the same way in your job properties as you did in the call, otherwise DS would have expanded that parameter to use the value. Most likely you have at least one letter with a different case.

Does anyone know what the official defining magic numbers for Dataset (and lookup file sets) are? I wanted to add them to the list so that we can put in an automated method of finding & potentially getting rid of datasets no matter where they have been written in the system. A quick look at some...

neeraj - lots of help available on this subject, use the search facility with keywords "checkpoint" and/or "restarting".

snassimr, each hash file and lookup combination has it's own special rules, so I tried using just a general explanation. The cardinality of your key is not important, it is the cardinality of your lookups. The paging mechanism will tend to choose pages to remove from physical memory that have not be...

vkalyan,

are you certain that you enabled NLS during the upgrade process? This verb is a standard part of an NLS installation - it might not exist in accounts that do not have NLS enabled and that would explain your error message.

snassimr, I am assuming that you are asking what happens when the hash file size is larger than the physical memory and is paged out. Unix is quite efficient with swapping while Windoze tends to be rather bad at it; meaning that I would avoid any planning for using the swapping/paging mechanism with...

snassimr,

what error does the FILEINFO command give you?

Ogmios, that statement from support scares the bejeesus out of me. Not only do the Americans generally not understand what NLS actually is but they have very little understanding of foreign characters and even what such things as collation and locales are. (Ask most people, including myself, where t...

Vinod,

the 2nd argument is optional as documented. At V7.5 I wrote a dummy routine which consisted of 1 line - Ans = LENDP(Arg1) and it compiles correctly also displays a length of 2 when I enter (through cut-and-paste) the 4 bytes/2 Characters that make up the name "Tokyo".

Ravi, I don't think that you will have much luck opening a ticket, didn't you get a warning message regarding an unsupported datatype - that would account for the length issue and as DataStage internally only works at byte boundaries it will not be easily solved. I think the earlier posts stated tha...

Ravi, you can change/override the conversion settings at a column level; so for the columns that are binary you just change the "import EBCDIC as ASCII". Just click on the column definition, right-mouse and "edit row" in the sequential file stage to get the screen where you can adjust the settings a...

Salman, I'm curious at to how did the problem got solved in the end - I'm not quite sure what you mean by "rectified automatically". The RT_STATUSnnn file contains information about the run state and history of job executions and the RT_CONFIGnnn file contains job design and configuration informatio...

Hello Vinod, let's say that you have a UTF-16 NLS enabled and you have a string with a single Japanese Kanji (let's just assume that it's the symbol for Chikara [which is my favorite Kanji]), if you were to do a LEN(KanjiString) you would get 2 (because it is 2 bytes long), if you were to do a LENDP...

Salman, something bad has happened to your DataStage account(s). After taking a backup, you could try going into the command line or into the administrator and in the DS.TOOLS menu issue the re-index; this might possible correct the problem. Can you say what might have happened to trigger this state...