Wrong error message

gehlert · Post by **gehlert** » Wed Dec 07, 2005 11:37 am

Got the following error message:

java.lang.IllegalStateException: No mvsCallbackThread active - callback can be set

My mistake, I guess -- started the application not via the batch launcher but from a shell script. But, shouldn't the error message read "callback cannot be set"?

Not a big deal, I know... but anyway...

Post by **coz** » Wed Dec 07, 2005 5:29 pm

Thanks for catching this - we'll correct this in the next release

gehlert · Post by **gehlert** » Wed Dec 07, 2005 6:13 pm

Just to verify -- is it true that the callback thread can only be established when using the batch launcher? Or should it also work when running the app from USS? (If so, I must have done something else wrong.)

More generally, is batch launcher code ever invoked from the JVM, or only code that resides in shared libraries?

Post by **coz** » Wed Dec 07, 2005 6:24 pm

The batch launcher establishes the mvs console interaction thread when it initializes, shortly after it constructs the JVM. If you run with trace level logging (LOGLVL='+T') you'll see the call from the launcher to the JVM.

Post by **dovetail** » Thu Dec 08, 2005 7:57 am

I've not attempted it, but you should be able to use ZUtil.establishMvsCommandWaiter() yourself if not running under the batch launcher.

gehlert · Post by **gehlert** » Thu Dec 08, 2005 10:37 am

Tried that before but this causes an abend & LE dump when I am running under the batch launcher (see one of my previous posts), so, stuck betweeen a rock and a hard place...

Doesn't matter anyway since this was only a quick test, and I'll use the batch laucher from now on.

Post by **dovetail** » Thu Dec 08, 2005 5:08 pm

How about catching the IllegalStateException from setMvsCommandCallback() and in the catch block calling establishMvsCommandWaiter and retrying....