TreeGetRecord() returns a misleading error code about mdsplus HOT 4 OPEN

It would likely be useful to add a new error code for zero. This would have to be added to the Ss facility section of the mdsshr_messages.xml file. Perhaps it should be as follows:

<status name="ZERO"  value="0"  severity="Warning" text="Zero is an invalid error code"/>

Note that the resulting error code, SsZERO (= 0) differs from SsSUCCESS (= 1) only in the severity field.

However, this would likely be problematic -- because then both "SsSUCCESS" and "SsZERO" would have the same "value" field (the message system likely doesn't allow duplicates). And furthermore, the MdsGetStdMsg.c file of the mdsshr library would need to be modified to handle the special SsZERO error code.

from mdsplus.

The reported bug is probably related to the broken (especially python) thread safety (especially mdsip)

Regardless:

Off the top of my head, it should not return zero. The bits are encoded, with the last two bits holding the severity. The only reason Success has no other bits set is that we did not want to call out a particular kind of success.

from mdsplus.

It may or may not do what you need but I think that: ProcessPoolExecutor will be more likely to succeed.

from mdsplus.

looks like it should simply returrn status instead of 0.

from mdsplus.