ALLBASE/SQL Message Manual (36216-90213)

248 Chapter8
ALLBASE/SQL Error Messages: 8221-10999
application should be modified to use less. If the heap
allocation has previously worked on the system, first check
the number of users on the system, then use SQLMON to
see global swap space utilization plus heap usage for
individual user processes. If numerous scans are open on
the same DBE, the problem could be alleviated if the open
scans are combined into one open scan (and thus only one
set of scan control blocks).
10057 MESSAGE Invalid exception number. (DBERR 10057)
CAUSE You specified an invalid exception number when
requesting diagnostic information.
ACTION Specify a valid exception number.
10058 MESSAGE Invalid DBEnvironment or connection name
length. (DBERR 10058)
CAUSE You specified a DBEnvironment or connection name
length which is less than or equal to 0, or greater than
128.
ACTION Specify a valid DBEnvironment or connection name.
10059 MESSAGE Invalid BEGIN WORK setting. (DBERR 10059)
CAUSE You specified a bad transaction priority or isolation level
when starting a transaction.
ACTION Specify a valid transaction priority or isolation level in the
BEGIN WORK statement.
10060 MESSAGE Invalid format node data type encountered.
(DBERR 10060)
CAUSE The data type you specified in one of the format array
elements is not a valid SQL data type.
ACTION Specify a valid SQL data type.
10061 MESSAGE Invalid format string specified. (DBERR
10061)
CAUSE The format string you specified is invalid.
ACTION Specify a valid format string.
10062 MESSAGE Invalid setting in PARMCB.CURSOR_NUM. (DBERR
10062)
CAUSE The cursor number you specified in
PARMCB.CURSOR_NUM is either 0, less then -32767, or
greater than 32767.
ACTION Specify a valid cursor number in
PARMCB.CURSOR_NUM.
10063 MESSAGE Invalid format node type encountered. (DBERR