10.3 002: activate "OS".command returns -50
Author: email@example.com (ulrich-merkel)
as a test, i just use the following line (10.3 002) activate "OS".command("cmd.com /c echo.1234 > ABC.TXT") but (no matter what I put in as a command text) i got a $status of -50 with a $procerrorcontext of "ERROR=-50·; MNEM=<UACTERR_NO_SIGNATURE>·; DESCRIPTION=Signature not found·; COMPONENT=TEST_OS·; PROCNAME=3\DETAIL·; TRIGGER=DTLF·; LINE=2·; ADDITIONAL=INSTANCENAME=OS·!·; OPERATIONNAME=COMMAND" This test was started in the original project created during the U10.3 installation to reduce any customizing effects. Have I overlooked some necessities? And where (in which UAR) should this signature be located?