|
Adager Questions and Answers | (Section 7 of 13) | |
| First | Prev | Table of Contents | Next | Last | |
Your Adager Guide is also available online
Possible NM stack overflow and system abort 1458 under IMAGE C.09.02 (and newer)
If you do not use HP B-Trees, this note does not apply to you.
Under certain circumstances, there is a problem during Adager's B-Tree rebuilding on IMAGE C.09.02 (and newer).
Version background
- IMAGE (C.09.02 and newer) supports larger limits (1200 data items, 240 datasets and 64 paths on a master). Adager (000604 and newer) supports these new IMAGE limits.
- MPE/iX 6.5 PowerPatch (Express) 2 comes with IMAGE C.09.02.
- MPE/iX 7.0 PP1 will also include IMAGE C.09.02 (or newer). Interestingly, MPE/iX 7.0 (base release) comes with an older version of IMAGE.
IMAGE C.09.02 (and newer)
For a few years now, Adager has been happily rebuilding a master dataset's B-Trees automatically (when changing the capacity of a B-Tree indexed master, for example).
Enter IMAGE C.09.02 (and newer)...
IMAGE C.09.02 (and newer) requires a larger NM stack for B-Tree rebuilding. If your computer's default NM stack value is at least 2 million, you are in good shape. (This value is part of the "misc" parameters in sysgen.)
With a smaller NM stack value, Adager versions older than 010516 terminate with an NM stack overflow. Unfortunately, MPE/iX adds insult to injury by halting with a system abort 1458 (SA 1458).
Temporary Adager work-around
If your computer's default NM stack value is less than 2 million, please run Adager versions older than 010516 with this explicit NM stack value:
If you have Adager JobStreams, modify the "run Adager" line to include this "nmstack" parameter.
:run adager.pub.rego; nmstack=2000000
Permanent Adager fix
Adager (010516 and newer) automatically handles this larger nmstack requirement, regardless of your computer's default value.
Please email
to request expedited delivery of this Adager version (please specify physical tape or Internet download).
How do you find out your IMAGE version?
You can use Query's "version" command to verify your IMAGE version.
Please note that you want to pay attention to the "TurboIMAGE Overall VUF" ("version, update, fix") value. In my case, for example, this value is "C.09.05" (i.e., it is newer than C.09.02), even though the value for DBOPEN is "C.09.00".
:query.pub.sys HP32216N.03.17 QUERY/NM THU, DEC 29, 2011, 7:41 AM COPYRIGHT HEWLETT-PACKARD CO. 1976 >version QUERY N.03.17 TurboIMAGE Overall VUF: HP30391C.09.05 TurboIMAGE/XL <===== This is what counts TurboIMAGE Procedures: DBOPEN C.09.00 DBINFO C.09.01 DBCLOSE C.07.26 DBFIND C.09.00 DBGET C.09.00 DBUPDATE C.09.04 DBPUT C.09.04 DBDELETE C.09.04 DBLOCK C.09.04 DBUNLOCK C.09.04 BIMAGE C.09.04 DBCONTROL C.09.02 DBBEGIN C.07.24 DBMEMO C.07.24 DBEND C.07.24 DBXBEGIN C.09.05 DBXEND C.09.05 DBXUNDO C.09.05 ...
|
|
Adager Questions and Answers | (Section 7 of 13) | |
| First | Prev | Table of Contents | Next | Last | |
Your Adager Guide is also available online