It also manages the I/O to data sets for BMC product registration, collectively called the REGISET. PACLOG does not use the REGISET but other BMC products such as DAC and the Application Enhancement Series (AES) product set require the REGISET.

More than one BCSS can be active on an OS/390 image. The AES product set and others can share a BCSS with PACLOG or use a separate BCSS. The BMCP ensures that each BCSS receives control at the proper time for the products that use that BCSS.

You must use the MODE parameter in the startup procedure to designate one (and only one) BCSS on an OS/390 image as the public BCSS. All others must be designated as private subsystems. The BMCP allows the public BCSS first access to an intercepted request. The BCSS that is used for PACLOG must be the public BCSS. For more information about sharing the BCSS with other BMC products, refer to the documentation for those products.

Data set for BCSS commands

The data set for BCSS commands contains BCSS and non-BCSS commands that need to be issued automatically after BCSS startup.

The data set must be a sequential data set or must be specified as a member of a partitioned data set. The name of this data set must appear on the COMMANDS DD statement in the BCSS startup JCL. When you install PACLOG with the recommended settings, a default data set for BCSS commands is created automatically.

You can edit the data set for BCSS commands to add or delete BCSS and non-BCSS commands. For information about the use of non-BCSS commands in that data set, see MVS-command-support.

When entering commands into the data set for BCSS commands, follow these guidelines:

• Omit the BCSS ID term (BCSSID) from each command.

  For example, the bcssId DAC NONVSAM CL LOCAL command must appear in the data set for BCSS commands as DAC NONVSAM CL LOCAL.

• Start the commands in column one; enter only one command per line.
• Place an asterisk (*) in column one for comment lines.