Function: XEQCONT Purpose: Send a task start command to HERMES and continue. Category: SYSTEM, USER-INTERFACE File: srvreq.c Author: J.P. Terlouw Use: INTEGER XEQCONT( KEY, Input character COMMAND ) Input character XEQCONT Status return: 0 command executed -1 Hermes refused to execute command because of sytax error, too many tasks active, etc. KEY Keyword to which integer task exit status is written: 1 successful execution -2 task exited before calling INIT -3 fatal execution error (i.e. CALL ERROR with a level at or above current error level) -4 task crashed -5 user abort If keyword is specified as "*" (asterisk), the called task will run independently and no status will be written to the calling task. COMMAND Character variable containing the Hermes task start command. Description: XEQCONT allows a task to initiate another task without waiting for its completion. When the second task has exited, Hermes will write the task exit status to the keyword, which then can be read by the calling task. From this keyword also other keywords are derived which are used to report about the second task's status. N_ : provides the second task's taskname. S_ : provides any status message generated by or on behalf of the second task. When the second task needs input to a keyword, keywords with the following prefixes will be set for the calling task: K_ : the requested keyword M_ : the message associated with the input request T_ : the type of the requested input: 1 - USERINT 2 - USERLOG 3 - USERREAL 4 - USERDBLE 5 - USERCHAR 6 - USERCHAR 7 - USERCHARL 8 - USERTEXT R_ : the rejection message for a keyword that was rejected If the calling task exits before the called task, the latter will be aborted, except when it has been started as an independent task using "*" as the keyword argument. Related docs: deputy.dc2, xeq.dc2 Updates: Jan 17, 2001: JPT, Original document. Apr 16, 2011: JPT, Described prefixed keywords. May 18, 2012: JPT, Documented independent start-up.