DSXchange

Hi,

We are getting some error in development box, Failed to Open RT_LogXXX error.

Raised a ticket with IBM guys, they have given the below work to do.

1) Log onto the D/S server machine as the dsadm user.
2) cd `cat /.dshome`
3) . ./dsenv
4) cd <to the project directory>
5) DSHOME/bin/uvsh
6) CT VOC RT_LOG4249
7) If the output is something like:
RT_LOG4249
0001 F
0002 RT_LOG4249
0003 D_RT_LOG

And if :
8) LIST RT_LOG4249 fails,
Then
>ED VOC RT_LOG4249
3 lines long.
Press the return key to display lines 1, and then again to display the second line. Type in the 'R/RT_LOG4249//' command as below and then

----:
0001: F
----:
0002: RT_LOG4249
----: R/RT_LOG4249//
0002:
----: FI
"RT_LOG4249" filed in file "VOC".

After you have executed the above command, you will be able to run the command:

9) CREATE.FILE DATA RT_LOG4249 30

My Questions

1. What is CT VOC RT_LOGXXX
2. What is ED VOC RT_LOGXXX
3. What is the use of ----: R/RT_LOG4249//
4. CREATE.FILE DATA RT_LOG4249 30, what is this 30 in this.

Thanks,

These are TCL commands. CT is copy to terminal. ED is a line editor. TCL commands are like sqlplus and talking directly to the Universe engine. In our case the DataStage engine.

... plus 'R' means Replace and the '30' is the numeric type of the hashed file to create, i.e. a dynamic hashed file.

They have given you an unnecessarily ugly series of steps to accomplish the same result as executing the command CLEAR.FILE RT_LOG4249 from TCL.

It's called "job security" if you make it seem really, really complex.

Thanks for the replies guys,

BTW, What is causing the RT_LOGXXX issue and how to avoid this.

Thanks,

Hard to say from so little information, but typically a 'blink' error from pushing too many messages into it and causing it to grow past the 32bit addressing boundary of ~2GB. Solution? Don't allow unlimited growth.