Configuration Errors

Filesystem Errors

All errors returned by the PRO/5 filesystem during its invocation and internal configuration are in the following form:

<error message>
fs load err=<val0> (val1)
pro5: unable to initialize file system
<val0> = PRO/5 Error number + 1
<val1> = Host file system error number X (-1)

Common fs load Errors

fs load error	PRO/5 Error	Description
5	4	PRO/5 cannot find the config.bbx file or cannot find your workstation driver as specified in config.bbx. This implies the absence of a "dsksyn" statement in config.bbx which disables a disk drive. The most common instance is not disabling a floppy drive A or B.
13	12	Cannot open config file <filename> pro5: unable to initialize filesystem This implies the absence of a file. Either config.bbx or the driver file indicated by the alias line in config.bbx. It can also indicate that the device to open for channel 0 is directly named with BBTERM= but the alias cannot be located in config.bbx.
17	16	Implies that the system does not have enough free memory. (The stblen value may be too low to hold the config.bbx file or the aliases= needs to be increased.)
30	29	The terminal type referenced by the alias of the TERM= environment variable cannot be found in the current termcap file. (The UNIX operating system tset command should not be used to set your termcap environment variable)
34	33	Implies a missing ":", "\", "co#", and/or "li#" in the terminal's termcap entry, or that the environment variable $TERM is set to "unknown" or "dialup." On MS-DOS systems this error implies that the system does not have enough free memory. STBLEN value may be too low to hold the config.bbx file or too many aliases are specified.
61	60	PRO/5 has encountered an error it was not designed to translate. Either the operating system has created a new error code or is using a pre-existing error code in a new and unexpected context. Under MS-DOS, this is typically seen for versions 5.x of the MS-DOS system where the SHARE command was not invoked.
70	69	This error is issued when PRO/5 detects an attempt to exceed the maximum user count for the installation or an unauthorized attempt is made to access PRO/5. An unauthorized access can occur on a UNIX operating system network where two or more systems having the same PRO/5 serial number installed attempt to connect to a PRO/5 Data Server. In these cases, one of the copies of PRO/5 must be removed from the server.