[an error occurred while processing this directive]
HP OpenVMS Systems Documentation |
HP OpenVMS System Services Reference Manual
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:
SYI$_PHYSICALPAGESReturns the total number of PFNs that exist between the first PFN (typically PFN 0) and the highest numbered PFN.Because this number is a longword, the buffer length field in the item descriptor should specify 4 (bytes). SYI$_PMD_COUNTReturns the total number of physical memory descriptors defined by the system. The return value of this parameter can be used to determine the buffer size to use when specifying the SYI$_PFN_MEMORY_MAP item code.Because this number is a longword, the buffer length field in the item descriptor should specify 4 (bytes). SYI$_POTENTIAL_CPU_BITMAPThe return argument is a bitmap with a bit indicating 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.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. SYI$_POTENTIAL_CPU_MASKNote that this item code is becoming obsolete; HP recommends that you not use it because it represents only up to 64 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. For greater flexibility, use item code SYI$_POTENTIAL_CPU_BITMAP instead.On Alpha and Integrity server 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. SYI$_POTENTIALCPU_CNTOn Alpha and Integrity server systems, returns the count of CPUs in the hard partition that are members of the potential set for this instance. 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.SYI$_POWERED_CPU_BITMAPThe return argument is a bitmap with a bit indicating a member of the instance's powered set---those CPUs physically existing within the hard partition and powered up for operation.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. SYI$_POWERED_CPU_MASKNote that this item code is becoming obsolete; HP recommends that you not use it because it represents only up to 64 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. For greater flexibility, use item code SYI$_POWERED_CPU_BITMAP instead.On Alpha and Integrity server systems, returns a value that represents a CPU-indexed bitvector. When a particular bit position is set, the processor with that CPU ID value is a member of the instance's powered set---those CPUs physically existing within the hard partition and powered up for operation. SYI$_POWEREDCPU_CNTOn Alpha and Integrity server systems, returns the count of CPUs in the hard partition that are physically powered up.SYI$_PRESENT_CPU_BITMAPThe return argument is a bitmap with a bit indicating a member of the instance's present set -- those CPUs physically existing within the hard partition. Being in the present set does not imply that it is part of the powered set.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. SYI$_PRESENT_CPU_MASKNote that this item code is becoming obsolete, and HP recommends that you not use it because it represents only up to 64 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. For greater flexibility, use item code SYI$_PRESENT_CPU_BITMAP instead.On Alpha and Integrity server systems, returns a value that represents a CPU-indexed bitvector. When a particular bit position is set, the processor with that CPU ID value is a member of the instance's present set -- those CPUs physically existing within the hard partition. Being in the present set does not imply that it is part of the powered set. SYI$_PRESENTCPU_CNTOn Alpha and Integrity server systems, returns the count of CPUs in the hard partition that physically reside in a hardware slot.SYI$_PRIMARY_CPUIDOn Alpha and Integrity server systems, returns the CPU ID of the primary processor for this OpenVMS instance.SYI$_PROCESS_SPACE_LIMITOn Alpha and Integrity server systems, this item code returns the 64-bit virtual address succeeding the last available process private address. The value returned is the upper bound on the process private address space. The value returned is the same for every process on the system.Because this number is a quadword, the buffer length field in the item descriptor should specify 8 (bytes). SYI$_PSXFIFO_PRIO_MAXOn Alpha and Integrity server systems, returns the maximum priority for the POSIX FIFO scheduling policy.Because this number is a longword, the buffer length field in the item descriptor should specify 4 (bytes). SYI$_PSXFIFO_PRIO_MINOn Alpha and Integrity server systems, returns the minimum priority for the POSIX FIFO scheduling policy.Because this number is a longword, the buffer length field in the item descriptor should specify 4 (bytes). SYI$_PSXRR_PRIO_MAXOn Alpha and Integrity server systems, returns the maximum priority for the POSIX round-robin scheduling policy.Because this number is a longword, the buffer length field in the item descriptor should specify 4 (bytes). SYI$_PSXRR_PRIO_MINOn Alpha and Integrity server systems, returns the minimum priority for the POSIX round-robin scheduling policy.Because this number is a longword, the buffer length field in the item descriptor should specify 4 (bytes). SYI$_PT_BASEOn Alpha and Integrity server systems, returns the 64-bit virtual address of the base of the page tables. The value returned is the same for every process on the system.Because this number is a quadword, the buffer length field in the item descriptor should specify 8 (bytes). SYI$_PTES_PER_PAGEOn Alpha and Integrity server systems, returns the maximum number of CPU-specific pages that can be mapped by one page table page.Because this number is a longword, the buffer length field in the item descriptor should specify 4 (bytes). SYI$_RAD_CPUSOn Alpha and Integrity server systems, returns a longword array of RAD/CPU pairs that can potentially be in this operating system instance. If there is no RAD support, all potential CPUs are in RAD 0. The array is terminated with a -1,-1 pair.RAD is supported on AlphaServer GS series systems and starting from OpenVMS Version 8.4, support is extended to NUMA capable Integrity servers. SYI$_RAD_MEMSIZEOn Alpha and Integrity server systems, returns a longword array of RAD/page count pairs. The number of pages of private memory is returned. If there is no RAD support, all memory is reported in RAD 0. The array is terminated with a -1,-1 pair.RAD is supported on AlphaServer GS series systems and starting from OpenVMS Version 8.4, support is extended to NUMA capable Integrity servers. SYI$_RAD_MAX_RADOn Alpha and Integrity server systems, returns the maximum number of RADs possible on this platform. If there is no RAD support, 1 is returned.RAD is supported on AlphaServer GS series systems and starting from OpenVMS Version 8.4, support is extended to NUMA capable Integrity servers. SYI$_RAD_SHMEMSIZEOn Alpha and Integrity server systems, returns a longword array of RAD/page count pairs. The number of pages of shared memory is returned. If th ere is no RAD support, all shared memory is reported in RAD 0. If the current instance is not a member of a Galaxy, no shared memory is reported. The array is terminated with a -1,-1 pair.RAD is supported on AlphaServer GS series systems and starting from OpenVMS Version 8.4, support is extended to NUMA capable Integrity servers. SYI$_REAL_CPUTYPEReturns the actual CPU type of the primary CPU of the system.See the SYI$_CPUTYPE item code for a list of symbols and processors. SYI$_SCSNODEReturns the Galaxy instance name. Supported only on AlphaServer systems that support partitioning.SYI$_SCS_EXISTSReturns a longword value that is interpreted as Boolean. If the value is 1, the System Communication Subsystem (SCS) is currently loaded on the node; if the value is 0, the SCS is not currently loaded.SYI$_SERIAL_NUMBERReturns the system serial number from out of the Hardware Restart Parameter Block (HWRPB).SYI$_SHARED_VA_PTESOn Alpha and Integrity server systems, returns the 64-bit virtual address of the PTE that marks the boundary between process-private PTEs and system-shared PTEs. The value returned is the same for every process on the system.Because this number is a quadword, the buffer length field in the item descriptor should specify 8 (bytes). SYI$_SIDReturns the contents of the system identification register of the node.On Alpha and Integrity server systems, SYI$_SID returns a value in which all fields are 0 except the CPU-type field, which always contains the value 256. Because the value of this register is a longword hexadecimal number, the buffer length field in the item descriptor should specify 4 (bytes). SYI$_SWAPFILE_FREEReturns the number of free pages in the currently installed swapping files.Because this number is a longword, the buffer length field in the item descriptor should specify 4 (bytes). SYI$_SWAPFILE_PAGEReturns the number of pages in the currently installed swapping files.Because this number is a longword, the buffer length field in the item descriptor should specify 4 (bytes). SYI$_SYSTEM_RIGHTSReturns the system rights list as an array of quadword identifiers. Each entry consists of a longword identifier value and the following longword identifier attributes:
Allocate a buffer that is sufficient to hold the system rights list, because $GETSYI returns only as much of the list as will fit in the buffer. SYI$_SYSTEM_UUIDOn Integrity server systems, returns the Universal Unique Identifier (UUID) for the system. If the UUID is not supported or is not available, a null UUID (all zeroes) is returned.Because SYI$_SYSTEM_UUID is 128 bits long, the buffer length field in the item descriptor must specify 16 bytes. SYI$_SYSTYPEOn Alpha and Integrity server systems, returns the name of the family or system hardware platform. For example, the integer 2 represents a DEC 4000 processor, the integer 3 represents a DEC 7000 or DEC 10000 processor, and the integer 4 represents a DEC 3000 processor.SYI$_VERSIONReturns, as a character string, the software version number of the OpenVMS operating system running on the node.Because the version number is 8-byte blank-filled, the buffer length field in the item descriptor should specify 8 (bytes). SYI$_VECTOR_EMULATORReturns a byte, the low-order bit of which, when set, indicates the presence of the Vector Instruction Emulator facility (VVIEF) in the system.SYI$_VP_MASKReturns a longword mask, the bits of which, when set, indicate which processors in the system have vector coprocessors.SYI$_VP_NUMBERReturns an unsigned longword containing the number of vector processors in the system.SYI$_XCPUReturns the extended CPU processor type of the node.You should obtain the general processor type value first by using the SYI$_CPU item code. For some of the general processor types, extended processor type information is provided by the item code, SYI$_XCPU. For other general processor types, the value returned by the SYI$_XCPU item code is currently undefined. Because the processor type is a longword decimal number, the buffer length field in the item descriptor should specify 4 (bytes). SYI$_XSIDReturns processor-specific information. For the MicroVAX II system, this information is the contents of the system type register of the node. The system type register contains the full extended information used in determining the extended system type codes. For other processors, the data returned by SYI$_XSID is currently undefined.Because the value of this register is a longword hexadecimal number, the buffer length field in the item descriptor should specify 4 (bytes). SYI$_xxxxReturns the current value of the system parameter named xxxx for the node.The buffer must specify a longword into which $GETSYI writes the value of the specified system parameter. For a list and description of all system parameters, see the HP OpenVMS System Management Utilities Reference Manual. DescriptionThe Get Systemwide Information service returns information about the local system or about other systems in an OpenVMS Cluster configuration. Condition Values Returned
Condition Values Returned in the I/O Status Block1Same as those returned in R0. Example
$GETSYIW
Returns information about the local system or about other systems in a cluster. FormatSYS$GETSYIW [efn] ,[csidadr] ,[nodename] ,itmlst [,iosb] [,astadr] [,astprm] C Prototypeint sys$getsyiw (unsigned int efn, unsigned int *csidadr, void *nodename, void *itmlst, struct _iosb *iosb, void (*astadr)(__unknown_params), int astprm);
You must specify either the csidadr or the nodename argument, but not both. For wildcard operations, however, you must use the csidadr argument. $GETTIM
Returns the current system time in a 64-bit format. FormatSYS$GETTIM timadr,[flags] C Prototypeint sys$gettim (struct _generic_64 *timadr,...); Arguments
DescriptionThe Get Time service returns time data in different formats depending on the flags parameter. If the flags parameter is not specified, or is specified as 0, the service returns the current system time in 64-bit format. The quadword is the number of 100-nanosecond intervals since November 17, 1858. Condition Values Returned
|