Hi Prashant--
The put() command buffers output, so if you are writing small chunks of data each time, Arbortext may save it up in memory until it gets enough writes queued up to make it worth actually accessing the disk.
If you are just debugging, and wondering why the output file isn't updated when you call your function, I'd say don't worry about it. The buffering is usually a good thing, as it minimizes disk access and keeps things working efficiently. Just check the output file after the entire activity is done (i.e. you call close() on the output file you are creating) and you should find all the content you expect there (assuming there are no bugs, of course :-)).
If you really need to make sure the output file is updated in real time with each call to put(), you can use the flush() command to commit buffered writes. Doing this will increase frequency of disk access, so only do it if you really need it to work this way.
--Clay