The GDE @ command reports success after executing good command files. In r1.20, it would issue a YDB-E-IOEOF error even after sucessfully executing the commands in the file specfied. A workaround was to set the environment variable ydb_msgprefix to "GTM" for the GDE process. (#193)
Description
This is an issue I noticed in r1.20 GDE when using the @ syntax.
> gde @tmp.com
%GDE-I-GDUSEDEFS, Using defaults for Global Directory
/extra1/testarea1/nars/test/temp/tmp/tmp/mumps.gld
%GDE-I-EXECOM, Executing command file /extra1/testarea1/nars/test/temp/tmp/tmp/tmp.com
**%YDB-E-IOEOF, Attempt to read past an end-of-file**
%GDE-I-VERIFY, Verification OK
%GDE-I-GDCREATE, Creating Global Directory file
/extra1/testarea1/nars/test/temp/tmp/tmp/mumps.gld
Draft Release Note
GDE @ syntax works correctly. In r1.20, it used to issue a YDB-E-IOEOF error even though it executed the file pointed to by the @. A workaround for this was to set the environment variable ydb_msgprefix to "GTM" for the duration of the GDE @ usage. (#193)
Final Release Note
The GDE @ command reports success after executing good command files. In r1.20, it would issue a YDB-E-IOEOF error even after sucessfully executing the commands in the file specfied. A workaround was to set the environment variable
ydb_msgprefixto"GTM"for the GDE process. (#193)Description
This is an issue I noticed in r1.20 GDE when using the @ syntax.
Draft Release Note
GDE @ syntax works correctly. In r1.20, it used to issue a YDB-E-IOEOF error even though it executed the file pointed to by the @. A workaround for this was to set the environment variable ydb_msgprefix to "GTM" for the duration of the GDE @ usage. (#193)