Document revision date: 15 July 2002

Displays a list of software products installed on your system. Use the /FULL qualifier to display additional information such as kit type, maintenance activity, and software dependencies.

Format

PRODUCT SHOW PRODUCT product-name[,...] [/qualifiers]

Parameter

product-name

Names the product or list of products to include in the display. This is an optional parameter. If you omit it, the names of all installed products will be shown.

Qualifiers

/BASE_SYSTEM=(base-system-name[,...])

Selects software products whose base system matches the one specified. The base system name identifies both a hardware platform and an operating system. The base system name AXPVMS denotes an OpenVMS Alpha product, VAXVMS denotes an OpenVMS VAX product, and VMS denotes a product applicable to either OpenVMS Alpha or VAX.

Parentheses (()) are optional only when you specify a single base system name. They are required when you specify multiple base system names.

/FULL

/NOFULL (default)

Displays information in 132-column format. The /NOFULL qualifier displays a subset of available information in 80-column format.

/MAINTENANCE=(product-name[,...])

Displays the products to which the named maintenance products have been applied. A maintenance product is either a patch kit or a mandatory update kit.

Parentheses (()) are optional only when you specify a single product name. They are required when you specify multiple product names.

To list all maintenance products that have been applied to a particular product, use the following command:

PRODUCT SHOW PRODUCT product-name /FULL

/PRODUCER=(producer-name[,...])

Selects software products that the specified manufacturer produces.

Parentheses (()) are optional only when you specify a single producer name. They are required when you specify multiple producer names.

/REFERENCED_BY=(product-name[,...])

Displays products that are referenced by the named product. Use this qualifier to show if the product, specified in the /REFERENCED_BY qualifier, has a software dependency on the product or products specified in the product-name parameter of the SHOW PRODUCT command. If you specify an asterisk (*) as the product name, all referenced products are listed for the product named in the /REFERENCED_BY qualifier.

Parentheses (()) are optional only when you specify a single product name. They are required when you specify multiple product names.

To list all products that require a specified product to be installed, use the command:

PRODUCT SHOW PRODUCT product-name /FULL /REFERENCED_BY=*

To list all products that are referenced by (that is, required by) a particular product, use the command:

PRODUCT SHOW PRODUCT * /REFERENCED_BY=product-name

To list all products that are referenced by (that is, required by) other products, use the command:

PRODUCT SHOW PRODUCT * /REFERENCED_BY=*

/REMOTE

/NOREMOTE (default)

Uses the product database on a system other than the currently running system. This qualifier is primarily for use in command procedures that Compaq supplies. Incorrect use of this qualifier can corrupt the POLYCENTER Software Installation utility database, corrupt installed products, or cause other problems. In some cases, /REMOTE can be useful with the CONFIGURE and SHOW commands.

When you use /REMOTE, the following logical names must be defined:

• PCSI$SYSDEVICE must specify the physical disk name of the target system disk. This disk must be mounted and allocated to the process executing the PRODUCT command.
• PCSI$SPECIFIC must point to a system root on PCSI$SYSDEVICE. It must be defined in the following form, where x is a valid system root:

  PCSI$SYSDEVICE:[SYSx.]

Note that the definition of PCSI$SYSDEVICE and PCSI$SPECIFIC specify only where the utility will find or place its database.

/SPAN_VERSIONS=keyword([,...])

Selects software products whose versions match the specified version criteria. The keywords are:

ABOVE=version	Selects versions greater than the version specified
BELOW=version	Selects versions less than the version specified
MINIMUM=version	Selects versions greater than or equal to the version specified
MAXIMUM=version	Selects versions less than or equal to the version specified

The ABOVE, BELOW, MINIMUM, and MAXIMUM keywords can be used alone or in combination. For example, /SPAN_VERSIONS=(MINIMUM=V2.1,BELOW=V3.0) selects versions greater than or equal to V2.1 and less than (but not including) V3.0. Using the MAXIMUM keyword instead of BELOW would select versions that include V3.0.

/VERSION=(version-number[,...])

Selects software products that have the specified version.

Parentheses (()) are optional only when you specify one version number. They are required when you specify more than one version number.

Example

$ PRODUCT SHOW PRODUCT * /REFERENCED_BY=DECNET_OSI
 
      

The command in this example lists all products on which the DECnet-Plus product is dependent.

Displays the version of the POLYCENTER Software Installation utility that you are using.

Format

PRODUCT SHOW UTILITY

Parameters

None.

Qualifiers

None.

Example

$ PRODUCT SHOW UTILITY
POLYCENTER Software Installation utility version: V7.3-100
   .
   .
   .
 
      

The command in this example shows the version of the utility that is executing the command.

18.1 SCACP Description

SCA does the following:

• Governs the sharing of data between resources at the nodes
• Binds together System Applications (SYSAPs) that run on different Alpha and VAX computers

Historically, LAN cluster port information has been available only in the System Dump Analyzer (SDA) utility and by using the Availability Manager management tool. The ability to start and stop PEDRIVER on a LAN device was provided by SYS$EXAMPLES:SYS$LAVC_START_BUS.EXE and SYS$LAVC_STOP_BUS.EXE. No way existed to prioritize use of LAN devices or individual channels.

SCACP provides an alternative method of collecting cluster management data and exercising management control over cluster communications. OpenVMS Version 7.3 introduced SCACP's ability to manage SCA use of LAN paths. Beginning with OpenVMS Version 7.3-1, you can use SCACP to manage all OpenVMS Cluster interconnects.

18.1.1 Terminology Related to SCACP

Definitions of terms that are related to SCACP are in the following sections.

18.1.1.1 SCS Ports and Circuits

SCA communications mechanisms between nodes are defined in terms of System Communications Services (SCS) ports and circuits:

• An SCS port is any device that provides SCA communications services.
• An SCS circuit is an SCS port layer connection that provides a standardized set of services using a reliable port-to-port communication connection between OpenVMS Cluster nodes.

After a circuit is formed between two ports, communication using the SCS services can be established between SYSAPs in the nodes. In a cluster, each port maintains a circuit with every other remote port.

Circuits provide the SCS layer with the following standardized SCS services:

• Datagram delivery
• Message delivery
• Block data read and write operations

A virtual circuit (VC) is the interconnect-specific transport layer connection within a circuit that provides reliable port-to-port communication. In other words, VCs are the details of a circuit concerned with interconnect-specific reliable data delivery.

Circuits ensure the following:

• The delivery of messages without duplication or loss
• The sequential ordering of messages

The concepts of circuits and virtual circuits are so closely related that usually it has been unnecessary to differentiate between them because SHOW CLUSTER provides no visability into the internal operation of a circuit. SCACP, however, makes the differentiation necessary by providing this internal visability. Beginning with OpenVMS Version 7.3, SCACP can be used to manage and display information about the VCs underlying the circuits between LAN ports. Because SCACP displays different types of information about circuits and VCs, its commands must differentiate between them.

LAN cluster communications create virtual circuits using the NI-SCA Transport Protocol to communicate over LAN hardware, providing datagram services.

18.1.1.3 LAN Channels

A channel is a logical communication path between two LAN devices. Each channel between two nodes is determined by a local-remote pair of devices and the connecting network. For example, two nodes, each having two LAN devices, can establish up to four channels. The messages that a particular virtual circuit carries can be sent over any of the channels connecting the two nodes.

The LAN cluster driver, PEDRIVER, builds reliable virtual circuits using channels that the LAN adapters (devices) and the network connections define. It then uses these VCs to provide circuits to SCS.

18.1.1.4 Channels and Virtual Circuits

The differences between channels and virtual circuits are the following:

• Channels are LAN paths providing datagram service.
• NI-SCA port-to-port virtual circuits are layered on channels and provide error-free paths between nodes.

Multiple channels can exist between nodes in an OpenVMS Cluster system, but only one LAN-based virtual circuit can exist between any two nodes at a time.

18.1.2 New Cluster SCA Circuit and Port Functionality

The following sections explain new functionality available for SCA circuits and ports and new support for SCS dynamic load class. In addition, you can independently enable or disable checksumming on individual PEdriver virtual circuits (VCs).

18.1.2.1 Ability to Set Port and Circuit Priorities

Beginning with OpenVMS Version 7.3-1, you can exercise management control over the circuits chosen to be used for SCS connections. This control allows you to override the automatic selection of the circuit with the highest load class value.

To override automatic circuit selection, assign a management priority value to a specific circuit or SCA port. (A circuit's current priority value is the sum of the local port's management-assigned priority and the management priority value assigned to that circuit.)

Connections are assigned to a circuit with the highest priority. If multiple circuits have the highest priority value, then the circuit with the highest load class is selected.

A change in a circuit's current priority has one of the following effects:

• If a circuit's new current priority value is higher than another circuit's current priority, the connection is moved to the circuit with the higher current priority.
• Similarly, if a circuit's new current priority value is lower than another circuit's current priority, the connection moves to the circuit with the highest current priority.

You can use SCACP to enable or disable checksumming on a per-VC basis. For example, in a disaster tolerent cluster, you might want to enable only checksumming on VCs to nodes at the remote site to ensure that failure of a LAN device's checksumming function resulting in corrupted packets would not propagate to the remote site.

18.1.2.3 SCS Dynamic Load Class Support

Prior to OpenVMS Version 7.3-1, the load class of SCS circuits was determined only by the port's hard-coded load class value. As a result, CI or DSSI circuits were chosen over a GigaBit Ethernet circuit. Beginning with OpenVMS Version 7.3-1, PEdriver dynamically updates the load class value of its SCS circuits to reflect the performance of the underlying LAN path or paths currently in use.

If the circuits have the same priority, a change in a circuit's load class has one of the following effects:

• If a circuit's new load class value is higher than another circuit's current load class, the connection is moved to the higher load class circuit.
• Similarly, if a circuit's new load class value is lower than another circuit's load class, the connection moves to the circuit with the highest load class.

Beginning with V7.3-1, SCACP provides the ability to display information about one cluster interconnect's local ports and their circuits with remote ports.

SCACP port and circuit data is intended to provide the information necessary to exercise management control over ports and circuits. SCACP is not intended to replace the wealth of data that SHOW CLUSTER provides about ports and circuits. The SHOW CLUSTER and SCACP utilities are intended to be used together to manage cluster communications.

SCACP port and circuit data show the following:

• SCACP port data shows an overview of a particular port's characteristics.
• SCACP circuit data shows the characteristics and the status of SCS communications with other nodes in the cluster.

You can also manage cluster communications by assigning a priority value to individual ports or circuits. See the SET CIRCUIT and SET PORT command descriptions.

18.1.4 Managing LAN Cluster Ports

To manage LAN cluster ports, you can use common port and circuit commands. Additional commands exist for LAN port VCs, channels, and LAN devices on nodes in the cluster:

• VC data shows detailed internal information about the characteristcs and operation of the NI-SCA transport layer connection underlying the circuit between the local and remote PEDRIVER ports.
• Channel data shows the characteristics of each LAN communications path and shows how suitable each channel is for use by the virtual circuit.
• LAN device data shows low-level local LAN device characteristics, counters, and errors.

SCACP allows you to set channel and LAN device priority. SCACP also allows you to start and stop PEDRIVER on LAN devices.

Using the PEDRIVER Event-Tracing Facility

The LAN cluster port driver, PEDRIVER, includes an event-tracing facility that collects a small amount of information for each defined event and saves it in a buffer associated with the virtual circuit or channel. (Any event not associated with a particular virtual circuit or channel is saved in a global PEDRIVER trace buffer.)

The event trace data is used when debugging, performing dump analysis, and looking at detailed aspects of PEDRIVER operation.

You can use SCACP to diagnose cluster communications problems. The appendix "Troubleshooting the NISCA Protocol" in OpenVMS Cluster Systems provides troubleshooting strategies to help cluster or network managers use SCACP and other tools to pinpoint network-related cluster communications problems.

18.1.6 Related Documents

For additional information on the topics covered in this chapter, refer to the following documents:

• OpenVMS Cluster Systems
• Guidelines for OpenVMS Cluster Configurations

SCACP commands are provided for the following types of functions:

• Display
• Port selection
• Circuit selection
• Channel operation and selection
• LAN device operation and selection
• Trace
• Miscellaneous: Help, Spawn, Execute, and Exit

The SCACP commands are shown in Table 18-1.

`

Table 18-1 SCACP Commands

Command	Function
SCACP Display Commands Qualifiers
SHOW CHANNEL	Displays PEDRIVER channel information.
SHOW CIRCUIT (nodename)	Shows information about all circuits between this node and other cluster nodes, including LAN circuit information.
SHOW LAN_DEVICE	Displays PEDRIVER LAN device information.
SHOW PORT	Displays information about all SCA ports on the node, including the LAN port, PEA0.
SHOW VC	Displays PEDRIVER virtual circuit information.
SCACP Operation Commands
SET CHANNEL	Allows a user to set PEDRIVER channel management options.
SET CIRCUIT	Allows a user to set a management priority value for the selected circuit or circuits.
SET PORT	Allows a user to set a management priority value for the selected port or ports.
SET VC	Allows a user to set PEDRIVER virtual channel options.
SCACP LAN Device Operation Commands
SET LAN_DEVICE	Sets PEDRIVER LAN device management options.
START LAN_DEVICE	Starts PEDRIVER on the specified LAN devices.
STOP LAN_DEVICE	Stops PEDRIVER on the specified LAN devices.
SCACP Trace Commands
These commands are reserved for COMPAQ use only.
SET TRACE	Sets PEDRIVER event tracing options.
SHOW TRACE	Displays PEDRIVER event tracing information.
START TRACE	Displays PEDRIVER event tracing.
STOP TRACE	Stops PEDRIVER event tracing.
SCACP Miscellaneous Commands
HELP	Displays help data.
SPAWN [command]	Spawns and executes a DCL command.
@filename	Executes command file.
EXIT	Exits SCACP.

	privacy and legal statement
6048PRO_054.HTML