#1027 new thread problems

[Anthony Carter]

Hi,

This for either for Mark Hessling Or Mark Miesfield or maybe both.

When running samples\oodialog\userGuide\exercises\exercise 3a from the 4.2 dialog the bat file that kicks of the dialog runs rexxsql.exe – this is the 2.6b3 version – compiled for oracle.

The sample has been modified

Method okclicked now looks like

::method okClicked
expose wowPicker
newText = self~newStatic(902)
wow = wowPicker~pickWow
newText~setText(wow)

--new code for calling oracle – very simple query

userid = "qaresults"
password = "qaresults"
database = ""
host = "sample"

dbStream = .SQLStream~new(userID, password, database, host)~~Open

sql_string = "SELECT * FROM qaresults.platforms"
dbStream~Out('query', sql_string)

drop dbStream

return

--at the end of program

SQLException: call SQLError Condition("O")
return

::REQUIRES 'SQLError.rtn'
::REQUIRES 'SQLStream.cls'

The new thread appears not to be created correctly as it fails at line 1110 on rxpack.c – which is part of rexxsql
.
if ( GlobalData->RxRunFlags & MODE_VERBOSE )

GlobalData = 0 – not the address of the new thread

This example is meant to show that the Dialog is still running but a call is made to a new class –

If the Dialog is closed (the new code is moved to say line 53) and the above code executed then it works ok – this is the simplest example I could think of as its based on a sample you supply.

Thanks
Anthony

[Mark Miesfeld]

Hi Anthony,

On the face of it, this is not an ooDialog bug. It is a rexxSQL bug. If GlobalData is null, there is nothing ooDialog can do about it. And ooDialog doesn't have anything to do with it being null.

I submitted a patch to rexxSQL that fixes a bug in rexxSQL of a very similar nature. Quite likely the same rexxSQL bug you are seeing. See:

3408831 access violation -GlobalData = 0000000

in the bug tracker for rexxSQL. Mark H applied the patch, but it may not be in the code base you are using.

I don't use rexxSQL and know very little about it. But, it is my understanding that all calls to rexxSQL need to be made on the same thread that the connection is made on. So, if you wish to use rexxSQL with ooDialog, you will need to program accordingly. Again, this is not a bug in ooDialog, but simply the way it is.

I'll leave this bug open for a bit, but will most likely close it as invalid in a few days. I'll at least take a look at the example you've provided.

Please note that the ooRexx project and the rexxSQL project are independent projects.

[Mark Miesfeld]

Anthony,

I went to download your example, but you have not attached any example. If you have a simple example that demonstrates the problem, please attach it. If you don't attach it, I can't take a look at it and will close this as invalid. The information you have submitted so far clearly indicates it is a rexxSQL bug.

[Mark Miesfeld]

Anthony - I'm closing this, it is a rexxSQL problem, not an ooRexx problme