Suprtool Issues and Solutions
:run suprtool.pub.robelle
>base store,5 {open for read access}
>get d-sales {scan the d-sales dataset}
>if sales-tot > 1000000 {note implied decimal}
>output dsales {output to an MPE file}
>exit
You would modify your application program to read the dsales MPE file:
10-read-and-report section.
read sales-file into buffer-d-sales at end
move true to end-of-sales-flag.
if not end-of-sales then
perform 20-report-d-sales
thru 20-report-d-sales-exit.
10-read-and-report. exit.
TurboIMAGE Compatibility
Suprtool is compatible with TurboIMAGE and TurboIMAGE/XL. Suprtool automatically adjusts for a Turbo database; you do not need different versions of
Suprtool for different versions of IMAGE. Suprtool handles all of the limits introduced with TurboIMAGE.
Locking of IMAGE Datasets
Suprtool calls DBDELETE, DBPUT, and DBUPDATE for the Delete, Put, and
Update commands. If the database is not open in mode-3 or mode-4, Suprtool must lock the dataset when adding or deleting dataset records. The locking strategy is determined by the value of Set Lock.
Locking for the Entire Task
Specifying Set Lock 0 forces Suprtool to lock either the Put and Delete datasets or the Update dataset for the entire task. The lock is done after the Xeq command.
Suprtool uses a lock descriptor and one call to DBLOCK to lock two datasets in the same database. If both a Delete and a Put were specified to different databases,
Suprtool locks them both, first the input dataset in one database, and then the output dataset in the second base. After the task finishes, the Put and Delete datasets or the
Update dataset are unlocked.
Set Lock 0 provides the best performance, but other users cannot change the database during the entire Suprtool task. The reason for improved performance is twofold:
1. The database only needs to be locked once.
2. If Suprtool is reading the database with DBGET, it does not have to reget records and ensure that they have not changed with each lock.
Locking for Each Transaction
Set Lock 1 (the default), causes Suprtool to lock and unlock around every
DBDELETE, DBPUT, and DBUPDATE transaction. This provides the least contention with other users of the database, but may not be the best choice for large overnight runs where exclusive access to the database is available.
Suprtool 5.7 for MPE• 59
