GsFileIn doesn't handle server file access errors in RPC environments
The class GsFileIn provides the ability to file topaz-format code into GemStone programmatically, from files on the client or server file systems. In v3.7 and later, it uses GsFile to open and read files. GsFile returns errors in accessing server files in serverErrorString and errors in accessing client files in lastErrorString; these are effectively the same in linked environments.
If an error occurs when opening a server file, the incorrect method (the client method lastErrorString) was used to fetch the error; this returned the error correctly in linked sessions, but returned nil in RPC sessions. Note that this only affects error reporting, such as file not found; GsFileIn works without problem for the normal case.
In a thread-safe environment, client GsFile operations such as lastErrorString are disallowed; the error returned was a less understandable GciTransportError.
Last updated: 3/18/25