TurboIMAGE/XL Database Management System Reference Manual (30391-90012)

220 Chapter5
TurboIMAGE/XL Library Procedures
DBOPEN
If DBRECOV roll-back recovery is enabled, the first DBOPEN checks if the user logging file and
the database are attached to the same Transaction Management (XM) user log set. The
database and the user logging file must be kept synchronized at the XM level in order for
DBRECOV roll-back recovery to work.
DBOPEN initiates recovery of the incomplete dynamic transactions, if necessary; then
DBRECOV rolls back the incomplete static transactions.
Dynamic transactions are not allowed with DBOPEN mode 2.
If the batabase is enabled for logging and user wants to record session name or job name
instead of user identifer in the password parameter part into DBOPEN log record, then the
user should use DBUTIL to enable the database for ‘FORCE SESSION’ (see DBUTIL in
Chaper 8) and leave the user identifier in the password parameter blank.
Table 5-19. DBOPEN Return Status Values
File System,
Memory
Management,
and
Transaction
Management
Failures:
-1 HPFOPEN or FOPEN failure.
-2 FCLOSE failure.
-3 FREADDIR failure.
-4 FREADLABEL failure.
-5 FWRITEDIR error.
-6 FWRITELABEL error.
-8 FUNLOCK failure.
-9 Cannot create a control block.
-10 FFILEINFO failure.
-168 Cannot attach n to MPE XL XM: file system error nn .
-169 Invalid mode for XM attach options.
-175 Cannot attach n to MPE XL XM: XM error nn .
-176 Cannot detach n from MPE XL XM: XM error nn .
-177 User log file is not in the same volume set as database.
-178 Cannot detach n from MPE XL XM: file system error nn .
-179 Cannot begin MPE XL XM transaction for attach.
-198 Total DBOPEN count/user exceeds limit.
-208 FLABELINFO failure.
-209 Invalid mode for XM detach.
-210 MPE error decimal integer while getting log file name.
-211 Invalid or no userlabel.