Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see PACLOG for DB2 13.1.

MVS command support

You can insert non-BCSS commands, including OS/390 console commands, in the data set for BCSS commands.

After the BCSS has completely initialized and is prepared for processing, non-BCSS commands run sequentially.

You must prefix each OS/390 command in the data set for BCSS commands with MVS. For example, to issue an MVS start command after BCSS initialization is completed, add the following command to that data set:

MVS S PROC01

Subsystem naming conventions

The BMCP and BCSS subsystems use a four-character name to identify the subsystem to OS/390.

PACLOG installation uses the default names BMCP and BCSS. If either name conflicts with a non-BMC subsystem installed on your system, you can change that name during installation.

If you change the name of the BMCP or BCSS after the subsystem starts, you must perform an IPL.

Important

In the command examples in this manual, bmcpId and bcssId represent the one- to four-character BMCP or BCSS subsystem ID.


Related topic

XCA-subsystem-control

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*