GDSX Manual

Design and Development
Extended General Device Support (GDSX) Manual–134303
2-72
Notes on Specific Codes
fenodata = 187 ,
feownership = 200 , feownabort = 210 ,
fecpupon = 230 , feiopon = 231 ,
fescerror = 233 ,
fepathdown = 201 , fenetdown = 250 ,
fefatpin = 560 ;
The DEBUGFLAGS and TRAPERROR configuration parameters are used to indicate
file error numbers, which when detected by TSCODE cause TSCODE to invoke
DEBUG or send a warning message with the file error number to the home terminal.
See the descriptions of these configuration parameters earlier in this section.
Notes on Specific Codes
Following are descriptions for some of the file-system error codes returned by
TSCODE:
Feinuse, Error 12
This error is returned in response to an OPEN request when there are no available user
tasks.
Febadname, Error 13
This error is returned in response to an OPEN request for one of the following reasons:
•
The subdevice name is the same as the GDSX process name.
•
The open specifies only two levels of qualification for a subdevice under a line.
•
The open specifies no subdevice and the DYNAMIC configuration parameter is
OFF.
Fenosuchdevice, Error 14
This error is returned in response to an OPEN where the subdevice named in the OPEN
message does not exist.
Fenoprimary, Error 17
When GDSX does not have a current open of the backup by the primary, this error is
returned in response to an OPEN request for the backup by a process other than GDSX.
Febadcount, Error 21
This error is returned when the size of an external process’s request exceeds the smaller
value of RECEIVESIZE and the task’s READUPDATE on $RECEIVE.
Femissparm, Error 29
If GDSX is run converted, only the GDSX pseudo Guardian procedures that correspond
to the D-series Guardian procedures are available to USCODE (except for ^OPEN,