NonStop Server for Java Programmer's Reference (NSJ 4.2+)

1-> status segment $ZM00, detail.
QIO Detailed Status SEGMENT \NAVAE1.$ZM00
State.................. DEFINED
Segment State.......... STARTED
Segment Type........... FLAT_UA
Segment Size........... 536870912
MDs in Use............. 1258
Max MDs Used........... 1589
Last Fail Size......... 0
Current Pool Size...... 16774788 Initial Pool Size...... 16776992
Max Pool Size.......... 16776992 Min Pool Size.......... 16776992
Current Pool Alloc..... 5039616 Max Pool Alloc......... 5128320
Current Pool Frags..... 12 Max Pool Frags......... 18
The maximum pool size used in this case is 16 MB, which is well below the 128 MB limit, so QIO can be moved
to KSEG2.
Example: QIO Segment Moved to KSEG2
The following SCF output shows the QIO segment as moved to KSEG2.
TACL> scf
SCF - T9082G02 - (30APR03) (01APR03) - 03/19/2004 02:20:00 System \GOBLIN
(C) 1986 Tandem (C) 2003 Hewlett Packard Development Company, L.P.
(Invoking \GOBLIN.$DATA11.RAMR.SCFCSTM)
1-> status segment $ZM00, detail
QIO Detailed Status SEGMENT \GOBLIN.$ZM00
State.................. DEFINED
Segment State.......... STARTED
Segment Type........... RESIDENT
Segment Size........... 134217728
MDs in Use............. 1248
Max MDs Used........... 2357
Last Fail Size......... 0
Current Pool Size...... 16774788 Initial Pool Size...... 16776992
Max Pool Size.......... 16776992 Min Pool Size.......... 16776992
Current Pool Alloc..... 4516992 Max Pool Alloc......... 4715520
Current Pool Frags..... 375 Max Pool Frags......... 382
The QIO segments on this system (\GOBLIN) have been moved to KSEG2 based on the value of the segment type.
The value is RESIDENT if QIO is moved to KSEG2.
The first SCF output for \NAVAE1 shows QIO to be in FLAT_UA, which means that QIO has not been moved to
KSEG2.
Determining the Heap Manager
The C Runtime Heap manager (T1269) offers a substantial performance boost over the older heap manager
(T8431). While this performance boost might not affect any pure Java code, the JVM contains native (C and C++)
code; therefore, using the T1269 heap manager will boost the JVM performance.
To find the C Runtime Heap Manager being used on your NonStop system, use the vproc command output from
the ZCRESRL library; at the TACL prompt, type.