Subsystem commands

z/OS operator commands

BMCP commands

This section provides information about BMCP operator commands that start the BMCP subsystem, shut it down, and display its status. You can issue the commands as needed from the operator console.

For more information, see the following topics:

• • BMCP commands
  • BCSS commands
  • XCA commands

Starting the BMCP

You must start the BMCP subsystem before starting any applications.

For normal operations, place the z/OS START command in a COMMND xx member of SYS1.PARMLIB so that the BMCP subsystem starts automatically during an IPL.

To start a BMCP subsystem manually after you have stopped it, issue the START command from the operator console. Start the BMCP by issuing the following command, where the variable bmcp is the name of the member that contains the BMCP procedure:

Check the system log to ensure that the command is completed successfully. The BMCP responds with messages that indicate its availability.

Optionally, you can issue the z/OS DISPLAY ACTIVE LIST (D A, L) command. z/OS responds with the following information. An active BMCP appears in this display.

Shutting down the BMCP

If you are not running in PACLOG Processing Only (PPO) mode, you should leave the BMCP subsystem running at all times.

However, you must shut it down when you need to install maintenance modules. You must also shut down the BMCP subsystem as part of an orderly shutdown of z/OS before an IPL. Shut down the BMCP subsystem after shutting down the BCSS subsystem and after Db2 has terminated.

To shut down the BMCP subsystem, issue the following command, where the variable bmcpid is the one- to four-character BMCP subsystem ID:

The BMCP subsystem responds with messages that indicate the progress of the shutdown. You need DELETE authority to use this command.

For more information about PPO mode, see PACLOG-processing-only-PPO-mode. 

Displaying BMCP status

You can display the status of BMCP to determine whether it is active.

To display the status, issue the following command, where the variable bmcpId is the one- to four-character BMCP subsystem ID:

BMCP responds with messages that indicate the status of the address space. You need READ authority to use this command.

You can also include the STATUS command in a COMMND xx member of SYS1.PARMLIB so that the BMCP status is displayed automatically during an IPL.

BCSS commands

This section provides information about BCSS operator commands that start the BCSS subsystem, shut it down, display its status, and reinitialize PACLOG.

You can use the BCSS operator commands as follows:

• Place them in a COMMND xx member of SYS1.PARMLIB so that they are issued automatically during an IPL.
• Place them in a data set for BCSS commands so that they are issued at BCSS start-up.

• Issue them as needed from the operator console.

  Important

  Commands issued from the operator console remain active until the next IPL, at which time the values in the data set for BCSS commands are reinstated.

 Starting the BCSS

You must start the BCSS before starting any applications.

For normal operations, include the z/OS START command in a COMMND xx member of SYS1.PARMLIB so that the BCSS starts automatically during an IPL. To start the BCSS manually after a shutdown, issue the START command from the operator console. To start the BCSS, issue one of the following z/OS commands, where the variable bmcBcss is the name of the member that contains the BCSS procedure:

This command starts the BCSS subsystem with new copies of resident BCSS modules. OPTION=REFRESH is the default for BCSS startup.

This command starts the BCSS subsystem with existing copies of resident BCSS modules.

Check the system log to ensure that the command is completed successfully. The BCSS responds with messages that indicate its availability.

Optionally, you can issue the z/OS DISPLAY ACTIVE LIST (D A, L) command. z/OS responds with the following information. An active BCSS appears in this display.

Shutting down the BCSS

If you are not running in PPO mode, you should leave the BCSS subsystem running at all times.

However, you must shut it down when you need to install maintenance modules. You must also shut down the BCSS subsystem as part of an orderly shutdown of z/OS before an IPL.

Shut down the BCSS subsystem after Db2 subsystems have been stopped and before you shut down the BMCP. To shut down the BCSS subsystem and terminate its address space, issue the following command, where the variable bcssid is the one- to four-character BCSS subsystem ID:

The BCSS responds with messages that indicate the progress of the shutdown. The shutdown may take several minutes. BCSS will remain active until all SVCs intercepted by BCSS have completed processing. You need DELETE authority to use this command.

For more information on PPO mode, see PACLOG-processing-only-PPO-mode. 

Displaying BCSS status

You can display BCSS status to determine the status of the address space.

To display the status, issue the following command, where the variable bcssId is the one- to four-character BCSS subsystem ID:

The BCSS responds with messages that indicate the status of the address space. You need READ authority to use this command.  

Reinitializing XCA compression

You must reinitialize the XCA compression modules after an IPL or after the XCA components have been upgraded.

When you reinitialize, XCA initializes only those components that are licensed. To reinitialize PACLOG, issue the following command, where the variable bcssId is the one- to four-character BCSS subsystem ID:

BCSS responds with messages that indicate that initialization is completed. You need DELETE authority to use this command.

XCA commands

This section describes commands that you issue through the BCSS that apply only to PACLOG compression components. These commands specify the BCSS ID and the compression component name (DAC). 

Enabling and disabling PACLOG compression components

You can enable or disable the PACLOG compression components on any BCSS.

When a component is disabled, compression is not available and PACLOG jobs cannot run.

To enable the PACLOG compression component, issue the following command, where the variable bcssId is the one- to four-character BCSS subsystem ID:

To disable the PACLOG compression component, issue the following command, where the variable bcssId is the one- to four-character BCSS subsystem ID:

The named BCSS responds with messages indicating which components have been enabled or disabled.  

Displaying the status of PACLOG compression components

You can display status information about the compression components (DAC).

To display status information, issue the following command, where the variable bcssId is the one- to four-character BCSS subsystem ID:

This command displays general status information about the compression components, such as the engine level mask value, version and release information, and the date on which the DAC tape was generated.

Optionally, check the system log to ensure that the command is completed successfully. BCSS responds with messages indicating the status of the selected components.  

Enabling global or local compression

You can use local or global compression.

The compression default is local compression. Global compression uses cross-memory services and requires more CPU resources. To set local compression, issue the following command, where the variable bcssId is the one- to four-character BCSS subsystem ID:

The named BCSS subsystem responds with messages indicating the status of the local compression option.  

Setting the PACLOG ELM

You can specify the compression engine-level mask (ELM) for PACLOG.

The ELM value that is specified overrides all other specifications of the ELM, including those set at the BCSS level. When you do not specify a product-level engine-level mask, the BCSS-level ELM is used.

To specify the required ELM, issue the following command, where the variable bcssId is the one- to four-character BCSS subsystem ID and the variable value is the required ELM mask value:

This command sets the product-level ELM to value for the non-VSAM component.

The ELM command that you use to specify the engine level mask has been removed from the BCSSCMDS data set. When the ELM is not specified, DATA ACCELERATOR defaults to the highest level that is available. The current ELM mask is documented in member DACELM in the .CNTL data set.