MSIR.0884 (classname): objects/VTBL/STBL - (numobj)/(vtbl)/(stbl) count/pages swapped (swaps)/(swap pages): Difference between revisions

From m204wiki
Jump to navigation Jump to search
mNo edit summary
(Automatically generated page update)
Line 7: Line 7:
The number of pages swapped will generally be identical to the number of swaps since most objects will be smaller than a single CCATEMP page. However, if there be unusually large objects in a request, and if these objects get swapped, the swapped page count could be larger than the swap count. Since no objects are instantiated at compilation time, no object swapping can happen at compilation time. So if this message is issued after compilation, the swap count and pages will always be 0.
The number of pages swapped will generally be identical to the number of swaps since most objects will be smaller than a single CCATEMP page. However, if there be unusually large objects in a request, and if these objects get swapped, the swapped page count could be larger than the swap count. Since no objects are instantiated at compilation time, no object swapping can happen at compilation time. So if this message is issued after compilation, the swap count and pages will always be 0.


[[Category:Sirius Mods messages]]
[[Category:Sirius Mods messages]] [[Category:MSIR.0800 - MSIR.0999]]

Revision as of 16:07, 13 August 2015

This informational message is issued to the terminal or audit trail when you set the appropriate OBJSTAT user parameter bits. It could be issued after compilation of a request, if either the X'01' or X'10' bit was set in OBJSTAT. It could be issued after evaluation of a request, if either the X'02' or X'20' bit was set in OBJSTAT.

This message indicates the number of objects for the indicated class (or, if *TOTAL*, for all classes) for which space was reserved in the server tables. It also indicates the amount of VTBL space (in 32-byte VTBL units) and STBL space used by these objects. For a given request, these three statistics will be identical after compilation and evaluation, since the space is reserved only at compilation time.

Also indicated is the number of object swaps required to move data from CCATEMP to/from one of the slots reserved for a class in the server. This swapping will occur if there are more objects instantiated in a request at a given time than slots reserved for the objects at compilation time. A single swap will also occur to bring in a global or session object the first time it is referenced in a request.

The number of pages swapped will generally be identical to the number of swaps since most objects will be smaller than a single CCATEMP page. However, if there be unusually large objects in a request, and if these objects get swapped, the swapped page count could be larger than the swap count. Since no objects are instantiated at compilation time, no object swapping can happen at compilation time. So if this message is issued after compilation, the swap count and pages will always be 0.