OFS single transaction and EXIT

I have a requirement to run a single OFS transaction and immeditely exit TSS, how do I do this?

eg

TSS XYZ where XYZ initiates (and completes a transaction)

and auto feeds an EXIT

I've tried a basic program feeding DATA statements which works but remains in TSS. I've tried CLEARDATA and CLEARINPUT upfront. I've tried DATA 'EXIT' statements.

What's interesting is that it hangs inside TSS the first time, but any subsequent calls take the EXIT from the DATA statement and exit TSS happily, but the first one hangs

Some more information on the requirement can help suggesting the best possible solution.

Regards,
Shanthi

Hi Shanthi

We have a Java package that needs to effect changes in T24, an internet based, ATM / transfers system. Some of our clients can better make use of internet based ATM connections, than the possibilities of fixed line, never stable, connections.

We have several options, all of which bottleneck at the TSS stage. Funnily enough this problem only occurs the first time TSS is called after the machine has been rebooted. In some countries electricity is not a guaranteed, and running a generator for four days without problems can be challenging, so power downs are possible.

As clients can be Globus G12, and/or pre-JBase 5.x, we need to keep the system outside of the TAG style interaction. Above this, a lot of the routines we work with have no source code, so modifying them is impossible.

We could have a looping poll routine checking for input - we currently looking at a port listener polling routine running from within T24/G12.

We need some means of entering TSS the first time, executing the commands, and exiting - this needs to be guaranteed to work every time.

thanks

Hi,

Your suggestion of a polling routine in a loop can work.

However, please be aware of TSS. If I remember correctly, this is not available in G12.

Regards,
Shanthi

Hi,
Iam facing a similar problem with tcs (using the tSS). when Iam using the file or batch listener,
allways the first record is refused, all the next records work successfully.
Solving this, I put allways a dummy line at the beginning, like test :-)
We have the same problem connecting to T24. The first request (in the morning) via Browser gives no answer. It seems the process sleeps... crasy