Previous | Contents | Index |
If $GETSYI returns the number 0 for SYI$_DAY_OVERRIDE, the number returned for SYI$_DAY_SECONDARY is meaningless.
Because this number is a Boolean value (1 or 0), the buffer length field in the item descriptor should specify 1 (byte).
Because the DECnet for OpenVMS full name of a node can contain up to 255 characters, the buffer length field in the item descriptor should specify 255 (bytes).
Because this number is a Boolean value (1 or 0), the buffer length field in the item descriptor should specify 1 (byte).
Because this number is a longword, the buffer length field in the item descriptor should specify 4 (bytes).
Because this number is a longword, the buffer length field in the item descriptor should specify 4 (bytes).
Because this number is a longword, the buffer length field in the item descriptor should specify 4 (bytes).
Because this number is a word in length, the buffer length field in the item descriptor should specify 2 (bytes).
Because this number is a Boolean value (1 or 0), the buffer length field in the item descriptor should specify 1 (byte).
Because the current number is a longword, the buffer length in the item descriptor should specify 4 (bytes).
Because the current number is a longword, the buffer length in the item descriptor should specify 4 (bytes).
Because this number is a Boolean value (1 or 0), the buffer length field in the item descriptor should specify 1 (byte).
Because this number is a longword, the buffer length field in the item descriptor should specify 4 (bytes).
Because this number is a Boolean value (1 or 0), the buffer length field in the item descriptor should specify 1 (byte).
An integer greater than 1023 indicates an Alpha and I64 node.
An integer less than or equal to 1023 indicates a VAX node.
The $ALPHADEF and $VAXDEF macros in SYS$LIBRARY:STARLET define the model type integers. See the tables under the SYI$_HW_NAME item code for the VAX processor names and the corresponding model types.
Because SYI$_HW_MODEL is a word, the buffer length field in the item descriptor should specify 2 (bytes).
Because SYI$_HW_NAME can include up to 60 characters plus one for the byte count, the buffer length field in the item descriptor should specify 61 (bytes). An example of an I64 processor follows:
HP rx4640 (1.10GHz/4.0MB) |
The following table lists the Alpha model processor names and the corresponding model types:
Alpha Model Processor Name | Alpha Model Type |
---|---|
DEC 3000 400 | ALPHA$K_A3000_400W |
DEC 3000 400S | ALPHA$K_A3000_400S |
DEC 3000 500 | ALPHA$K_A3000_500W |
DEC 3000 500S | ALPHA$K_A3000_500S |
DEC 4000 610 | ALPHA$K_A4000_610 |
DEC 4000 620 | ALPHA$K_A4000_620 |
DEC 4000 630 | ALPHA$K_A4000_630 |
DEC 4000 640 | ALPHA$K_A4000_640 |
DEC 7000 Model 610 | ALPHA$K_A7000_610 |
DEC 7000 Model 620 | ALPHA$K_A7000_620 |
DEC 7000 Model 630 | ALPHA$K_A7000_630 |
DEC 7000 Model 640 | ALPHA$K_A7000_640 |
DEC 10000 Model 610 | ALPHA$K_A10000_610 |
DEC 10000 Model 620 | ALPHA$K_A10000_620 |
DEC 10000 Model 630 | ALPHA$K_A10000_630 |
DEC 10000 Model 640 | ALPHA$K_A10000_640 |
The following table lists the VAX model processor names and the corresponding model types:
VAX Model Processor Name | VAX Model Type |
---|---|
VAX-11/730 | VAX$K_V730 |
VAX-11/750 | VAX$K_V750 |
VAX-11/780 | VAX$K_V780 |
VAX-11/785 | VAX$K_V785 |
MicroVAX II | VAX$K_VUV2 |
VAXstation II | VAX$K_VWS2 |
VAXstation II/GPX | VAX$K_VWSD |
VAXstation 2000 | VAX$K_VWS2000 |
MicroVAX 2000 | VAX$K_VUV2000 |
VAXstation 2000/GPX | VAX$K_VWSD2000 |
VAX 8200 | VAX$K_V8200 |
VAX 8250 | VAX$K_V8250 |
VAX 8300 | VAX$K_V8300 |
VAX 8350 | VAX$K_V8350 |
VAX 8530 | VAX$K_V8500 |
VAX 8550 | VAX$K_V8550 |
VAX 8600 | VAX$K_V8600 |
VAX 8650 | VAX$K_V8650 |
VAX 8810 (8700) | VAX$K_V8700 |
VAX 8820-N (8800) | VAX$K_V8800 |
VAX 8820, 8830, or 8840 with one CPU enabled | VAX$K_V8810 |
VAX 8820 | VAX$K_V8820 |
VAX 8830 | VAX$K_V8830 |
VAX 8840 | VAX$K_V8840 |
VAXft 3000 Model 310 | VAX$K_V520FT |
VAXstation 3520 | VAX$K_V3520L |
VAXstation 3540 | VAX$K_V3540L |
VAX 4000-300 timeshare | VAX$K_V670 |
VAX 4000-300 server | VAX$K_V670_S |
VAX 6000-210 timeshare | VAX$K_V6210_T |
VAX 6000-220 timeshare | VAX$K_V6220_T |
VAX 6000-230 timeshare | VAX$K_V6230_T |
VAX 6000-240 timeshare | VAX$K_V6240_T |
VAX 6000-250 timeshare | VAX$K_V6250_T |
VAX 6000-260 timeshare | VAX$K_V6260_T |
VAX 6000-210 server | VAX$K_V6210_S |
VAX 6000-220 server | VAX$K_V6220_S |
VAX 6000-310 timeshare | VAX$K_V6310_T |
VAX 6000-320 timeshare | VAX$K_V6320_T |
VAX 6000-330 timeshare | VAX$K_V6330_T |
VAX 6000-340 timeshare | VAX$K_V6340_T |
VAX 6000-350 timeshare | VAX$K_V6350_T |
VAX 6000-360 timeshare | VAX$K_V6360_T |
VAX 6000-310 server | VAX$K_V6310_S |
VAX 6000-320 server | VAX$K_V6320_S |
VAX 6000-410 timeshare | VAX$K_V9RR10_T |
VAX 6000-420 timeshare | VAX$K_V9RR20_T |
VAX 6000-430 timeshare | VAX$K_V9RR30_T |
VAX 6000-440 timeshare | VAX$K_V9RR40_T |
VAX 6000-450 timeshare | VAX$K_V9RR50_T |
VAX 6000-460 timeshare | VAX$K_V9RR60_T |
VAX 6000-410 server | VAX$K_V9RR10_S |
VAX 6000-420 server | VAX$K_V9RR20_S |
VAX 9000-210 | VAX$K_V9AR10 |
VAX 9000-410 | VAX$K_V9AQ10 |
VAX 9000-420 | VAX$K_V9AQ20 |
VAX 9000-430 | VAX$K_V9AQ30 |
VAX 9000-440 | VAX$K_V9AQ40 |
The size of the returned bitmap is determined by the number of supported CPUs on the system. You can compute the number of bytes needed for the bitmap as follows:
Use the $GETSYI system service with an item code of SYI$_MAX_CPUS to find the minimum number of bits needed, round this number up to a multiple of 64, and divide the result by 8.
On Alpha and I64 systems, returns the bit mask of CPUs available to be Fast Path preferred CPUs. The service continues to return the correct data for systems with up to 64 CPUs but fails for systems with more than 64 CPUs.
Because this number is a longword, the buffer length field in the item descriptor should specify 4 (bytes).
Because this number is a longword, the buffer length field in the item descriptor should specify 4 (bytes).
Because this number is a longword, the buffer length field in the item descriptor should specify 4 (bytes).
Because the DECnet area is a longword decimal number, the buffer length field in the item descriptor should specify 4 (bytes).
Because the CSID is a longword, the buffer length field in the item descriptor should specify 4 (bytes).
Because the number is a word in length, the buffer length field in the item descriptor should specify 2 (bytes).
Because the hardware version is a 12-byte hexadecimal number, the buffer length field in the item descriptor should specify 12 (bytes).
Because the DECnet for OpenVMS number is a longword decimal number, the buffer length field in the item descriptor should specify 4 (bytes).
Because this number is a word in length, the buffer length field in the item descriptor should specify 2 (bytes).
Because the software incarnation of the node is an 8-byte hexadecimal number, the buffer length field in the item descriptor should specify 8 (bytes).
Because the software type is a 4-byte ASCII string, the buffer length field in the item descriptor should specify 4 (bytes).
Because the software version is a 4-byte ASCII string, the buffer length field in the item descriptor should specify 4 (bytes).
The OpenVMS Cluster management software assigns this system identification to the node. You can obtain this information by using the DCL command SHOW CLUSTER. Because the system identification is a 6-byte hexadecimal number, the buffer length field in the item descriptor should specify 6 (bytes).
Because this number is a word in length, the buffer length field in the item descriptor should specify 2 (bytes).
Because this name can include up to 15 characters, the buffer length field in the item descriptor should specify 15 (bytes).
Because this number is a longword, the buffer length field in the item descriptor should specify 4 (bytes).
Because this number is a longword, the buffer length field in the item descriptor should specify 4 (bytes).
On VAX systems, $GETSYI always returns 512.
On Alpha and I64 systems, CPU page size varies from system to system.
On Alpha, and I64, and VAX systems, because this number is a longword, the buffer length field in the item descriptor should specify 4 (bytes).
Figure SYS-1 SYI$_PFN_MEMORY_MAP---Alpha Only
The first longword of the physical memory contains a count of descriptors. This number is equal to the value returned when the SYI$_PMD_COUNT item code is specified.
Each descriptor contains at least 3 longwords: a word containing the length of the descriptor (always use PMM$C_LENGTH when determining descriptor size); a flags word (whose bits are defined in the following table); and the starting PFN for that physical memory cluster and the number of PFNs in that cluster.
Bit | Meaning When Set |
---|---|
PMM$V_CONSOLE | The physical memory descriptor is in use by the console (hardware). |
PMM$V_OPENVMS | The physical memory descriptor is in use by OpenVMS. |
PMM$V_AVAILABLE | The physical descriptor is not in use by either the console (hardware) or OpenVMS. |
Remaining bits | The remaining bits in the PMM$W_FLAGS word are reserved for HP. |
The structure definition for the physical memory descriptor resides in PMMDEF.H.
Because the size of the physical memory map returned by $GETSYI can vary from system to system, HP recommends using the following steps when using this item code:
map_buffer_size = (PMM$C_LENGTH * ret-val) + 4 |
Figure SYS-2 SYI$_PFN_MEMORY_MAP---Alpha and I64
The first longword of the physical memory contains a count of descriptors. This number is equal to the value returned when the SYI$_PMD_COUNT item code is specified.
Each descriptor contains at least 3 longwords: a word containing the length of the descriptor (always use PMM64$C_LENGTH when determining descriptor size); a flags word (whose bits are defined in the following table); and the starting PFN for that physical memory cluster and the number of PFNs in that cluster.
Bit | Meaning When Set |
---|---|
PMM64$V_CONSOLE | The physical memory descriptor is in use by the console (hardware). |
PMM64$V_OPENVMS | The physical memory descriptor is in use by OpenVMS. |
PMM64$V_AVAILABLE | The physical descriptor is not in use by either the console (hardware) or OpenVMS. |
Remaining bits | The remaining bits in the PMM64$W_FLAGS word are reserved for HP. |
The structure definition for the physical memory descriptor resides in PMMDEF.H.
Because the size of the physical memory map returned by $GETSYI can vary from system to system, HP recommends using the following steps when using this item code:
map_buffer_size = (PMM64$C_LENGTH * ret-val) + 4 |
Because this number is a longword, the buffer length field in the item descriptor should specify 4 (bytes).
Because this number is a longword, the buffer length field in the item descriptor should specify 4 (bytes).
The size of the returned bitmap is determined by the number of supported CPUs on the system. You can compute the number of bytes needed for the bitmap as follows: Use the $GETSYI system service with an item code of SYI$_MAX_CPUS to find the minimum number of bits needed, round this number up to a multiple of 64, and divide the result by 8.
On Alpha and I64 systems, returns a value that represents a CPU-indexed bit vector. When a particular bit position is set, the processor with that CPU ID value is a member of the instance's potential set. A CPU in the potential set implies that it could actively join the OpenVMS active set for this instance if it is ever owned by it. To meet this rule, the CPU's characteristics must match hardware and software compatibility rules defined particularly for that instance.
Previous | Next | Contents | Index |