Space announcement

   

This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Subsystem commands

This topic describes the BMCP and BCSS operator commands that are available with XCA.

It also includes those commands that apply only to the PACLOG compression subsystems. OS/390 operator commands lists the available commands, the access required, and the page number on which the command descriptions can be found.

When starting DB2, you must issue the commands in this order:

  1. Start the BMCP.

  2. Start the BCSS.

  3. Start DB2.

Conversely, when stopping DB2, you must issue the commands in this order:

  1. Stop DB2.

  2. Shut down the BCSS.

  3. Shut down the BMCP.

OS/390 operator commands

Command type

Command format

Security required

Action

See topic

BMCP operator commands

S BMCP,SUB=<MSTR | JES2 | JES3>

None

Start the BMCP

Starting the BMCP

bmcpId SHUTDOWN

Control

Stop the BMCP

Shutting down the BMCP

bmcpId STATUS

READ

Display the BMCP status

Displaying BMCP status

BCSS operator commands

S BMCBCSS, OPTION=<REFRESH | NREFRESH>

None

Start the BCSS

Starting the BCSS

bcssId SHUTDOWN

Control

Stop the BCSS

Shutting down the BCSS

bcssId STATUS

READ

Display BCSS status

Displaying BCSS status

bcssId REINIT DAC

Control

Start or reinitialize DAC

Reinitializing XCA compression

XCA operator commands

BCSS DAC NONVSAM [ENABLE | DISABLE]

None

Enable or disable compression

Enabling and disabling PACLOG compression components

BCSS DAC STATUS

None

Return the compression status

Displaying the status of PACLOG compression components

BCSS DAC NONVSAM CL LOCAL

None

Enable or disable Local Compression option

Enabling global or local compression

bcssId ELM value

Control

Set Engine Level Mask

Setting the PACLOG ELM

PPO mode commands

BCSS DAC PPO ON | OFF

None

Enable or disable PPO mode

Reinstating full compression services

BCSS DAC PPO SHUTDOWN

None

Stop BMCP and BCSS while allowing PACLOG archive log compression

Shutting down the started tasks

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:

Starting the BMCP

You must start the BMCP subsystem before starting any applications.

For normal operations, place the OS/390 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:

 START bmcp

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

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

       JOBS       M/S           TS USERS       SYSAS     INITS     ACTIVE/MAX VTAM
00004      00025         00150           00009     00013     00150/00250
  BMCBCSS  BMCBCSS SSAS           NSW S BMCP       BMCP13    BPSMDSPO NSW S

Note

After an IPL, the BMCP subsystem name is not defined to OS/390. The OS/390 START command will wait until the primary subsystem has initialized, then proceed as normal. However, after the subsystem has been started, the subsystem name for BMCP is defined to OS/390.

If the procedure name and the subsystem name are the same, special considerations are necessary to avoid the PROC NOT FOUND message from OS/390. To avoid the PROC NOT FOUND message, either ensure the BMCP procedure is in the system SYS1.PROCLIB data set or include the SUB=JES x parameter on the OS/390 START command.

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 OS/390 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:

 bmcpId SHUTDOWN

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

For more information on 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:

  bmcpId  STATUS

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.

    Note

    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 OS/390 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 OS/390 commands, where the variable bmcBcss is the name of the member that contains the BCSS procedure:

START bmcBcss,OPTION=REFRESH

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

START bmcBcss,OPTION=NREFRESH

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

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

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

   JOBS      M/S      TS USERS       SYSAS      INITS     ACTIVE/MAX VTAM
00004      00025    00150          00009      00013     00150/00250
 LLA       LLA      LLA        NSW S RMF      A         IEFPROC     NSW S
 NET       NET      NETNCP     OWT S TSO      TSO       STEP1       NSW S
 BMCBCSS   BMCBCSS  SSAS       NSW S BMCP     BMCP13    BPSMDSPO    NSW S

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 OS/390 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:

 bcssId SHUTDOWN

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.

Warning

Do not cancel the BCSS started task. Many cross-memory links are set between BCSS and other address spaces. Cancelling BCSS may abnormally terminate other jobs that are running.

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:

 bcssId STATUS

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:

 bcssId REINIT DAC

BCSS responds with messages that indicate that initialization 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:

 bcssId DAC NONVSAM ENABLE

Warning

This command has changed from previous releases of PACLOG. Using the old syntax, DAC ENABLE, can have a negative impact on your system.

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

 bcssId DAC NONVSAM DISABLE

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:

 bcssId DAC STATUS

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 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:

 bcssId DAC NONVSAM CL LOCAL

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:

 bcssId DAC NONVSAM ELM 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.

Related topic

Was this page helpful? Yes No Submitting... Thank you

Comments