Skip to Content

Configuring BMC AMI mainframe products

Once the SMP/E installation of your BMC AMI mainframe products has completed, this section can be used to configure and customize them.

The BMC AMI Common Mainframe Services Controller (CMSC) provides storage and retrieval functions in relation to your BMC AMI mainframe product’s configuration parameters. BMC AMI mainframe products are configured using PARMLIB members. Using this method may be fundamentally different from the way you have configured your BMC AMI mainframe products in previous releases. Parameters are modified by editing human-readable PARMLIB members, then telling CMSC to store those modified PARMLIB members into the Common Memory Object by issuing a refresh (MODIFY) command. BMC AMI mainframe products receive parameter values stored in the Common Memory Object.

Warning

Important

The Common Memory Object containing your mainframe product parameters can be accessed regardless of whether the CMSC is active. When the CMSC is initialized all PARMLIB members are loaded into a Common Memory Object.

Related topic

Operational Consideration

General guidelines for PARMLIB members

Parameters used by your BMC AMI mainframe product or component are read from the common PARMLIB data set. Edit the sample parameters to your site’s requirements.

  •  If the PARMLIB member includes multiple groups of parameters, for example for the definition of multiple DB2 Subsystem, then only one occurrence of each of the parameters within each group is allowed.
  •  An asterisk * in column 1 causes the entire statement to be a comment.
  •  Line level comments are supported using the /* to start a comment and */ to end the comment. Embedded comments are supported.

Using system symbolics

The CMSC resolves system symbolics as product parameters are saved into storage, potentially allowing a single parameter member to be used across multiple LPARs. These symbols are defined by your installation in IEASYMxx. Issue the following display command to display the current symbols.

/DISPLAY SYMBOLS

PARMLIB member naming convention

PPPPnnnn

PPPP is the product prefix  (see BMC PARMLIB member parameters).

nnnn is the 1 to 4-character PARMLIB suffix, for example 00. 

The PARMLIB member name for each product or product component must start with the product prefix, for example FACM for File-AID Common Components. The 1 to 4-character suffixes can be used to replace the default name (FACM00). If the parameter for a given product is omitted, the default suffix will be 00.

Changing the default PARMLIB member

In the CMSC start-up parameters, specify the product parameter, followed by the equal sign, and the 1 to 4-character suffix (for example: FACM=01, which points to PARMLIB member FACM01. If you changed your PARMLIB member name from the default FACM00 to, for example FACM0005, update your CMSC PARMLIB member to point to the new PARMLIB member, FACM=0005.

General guidelines for PARMLIB data set

  •  The data set can be blocked.
  •  The data set can have multiple extents.
  •  The data set must be on a single volume.
  •  The CMSC must have READ access.

Changing a PARMLIB member

The following flowchart illustrates how an updated PARMLIB member is processed when a refresh command is issued.

 ECC_UpdatedPARMLIBmember.png

Using a non-default CMSC or parameter suffix value

To override the default CMSC or its default PARMLIB member suffix values, specify the following DDs in a given product’s JCL or started task.

//CWSCssss DD DUMMY

Used to override the CMSC from which the BMC AMI product will retrieve parameters, where ssss is the four-character CMSC_ID specified in the CMSC PARMLIB member.

//PMaaNNNN DD DUMMY

Optionally, used to override the default PARMLIB member specified in the CMSC configuration. Where aa is the two character product code and NNNN is the PARMLIB member suffix. The product codes are listed in BMC PARMLIB member parameters under the column “Two-Character Product Code Override”.

CMSC commands

Use the z/OS MODIFY command for the following commands.

Warning

Important

The verb MODIFY can be abbreviated, F.


PARMLIB commands

Use the following commands to control the Parameter Library Service of the CMSC:

  • Validate a Single Parameter Member:
F cmscname,PARMLIB VERIFY member_name
  • Displaying Information About a Single Parameter Member
F cmscname,PARMLIB DISPLAY member_name
Warning

Important

CMSCxxxx members can be checked for validity using the PARMLIB VERIFY command. The CMSC must be active in order to issue PARMLIB commands (thus, a valid CMSCxxxx PARMLIB member must already be present, which allowed the CMSC to initialize). With the PARMLIB VERIFY command, new or modified CMSCxxxx members can be validated before they are used, ensuring the CMSC initializes successfully.

In addition to the VERIFY command, the PARMLIB REFRESH, DISPLAY, and LIST commands can be used for CMSCxxxx members. Note that any refreshed CMSCxxxx PARMLIB member will not be used until the CMSC using that member is restarted.

  • Refreshing All Parameter Members:
F cmscname,PARMLIB REFRESH
  • Refreshing a Single Parameter Member:
F cmscname,PARMLIB REFRESH member_name
  • Displaying the Current Parameter Libraries:
F cmscname,PARMLIB DISPLAY
  • Displaying a Parameter Library Member:
F cmscname,PARMLIB LIST member_name
Success

Tip

This displays the member as it currently exists in the common memory object. It might be different from the current member in the CWPARM DD concatenation, if that member has been changed since the CMSC initiation and not refreshed using the PARMLIB REFRESH command. This command is only supported for PARMLIB V2 members.

  • Stopping the Parameter Library Service:

F cmscname,PARMLIB STOP

Warning

Important

The PARMLIB STOP command will stop the BMC Parameter Library Service. All requests for Parameter Library Services will result in a nonzero return code. It will not shut down the CMSC. In order to restart the Parameter Library Service the CMSC will have to be restarted. This command should only be used in emergency situations under direction of BMC Support.

  • Displaying CMSC Debugging Information:
F cmscname,DEBUG
Warning

Important

The DEBUG command displays debugging information for use by BMC Support personnel. The output of the command is redirected to a system assigned DD name and should be forwarded to BMC when requested by BMC Support.

Other CMSC commands

  • LMSHUT

Shutting down the BMC License Management Client or Server Task in the CMSC:

F cmscname,LMSHUT CLIENT

  • LMRESTRT

Restarting the BMC License Management Client or Server Task in the CMSC:

F cmscname,LMRESTRT CLIENT

  • RESTTRAC

Enabling HTTP verbose tracing:

F cmscname,RESTTRAC ON

Disabling HTTP verbose tracing:

F cmscname,RESTTRAC OFF
Warning

Important

The output will go to SYSOUT data sets with the DD name SYSnnnnn. Enabling verbose tracing will create a large amount of SYSnnnnn data sets and should be left on only as long as is required to gather debugging information.

  • STARTHCI

Restarting an HCI Address Space Controlled by the CMSC:

F cmscname,STARTHCI hci_procname
Warning

Important

This command only applies to HCI address spaces controlled by the CMSC  using the HCI_PROC CMSC startup parameter.

  • STOPHCI

Shutting Down an HCI Address Space Controlled by the CMSC:

F cmscname,STOPHCI hci_procname
Warning

Important

This command only applies to the HCI address spaces controlled by the CMSC  using the HCI_PROC CMSC startup parameter.

  • SHUTDOWN

Stopping the CMSC:

F cmscname,SHUTDOWN nnnn|IMMEDIATE

nnnn — A timer value that specifies the number of seconds to elapse before CMSC terminates. The default value is 60 seconds.

IMMEDIATE — A timer value that specifies that the CMSC is to stop immediately.

  • zIIP Commands

Restart or re-enable zIIP service:

F cmscname,ZIIP INIT

Stop zIIP service:

F cmscname,ZIIP DELETE

List zIIP service blocks:

F cmscname,ZIIP LIST

Determine if zIIP instance is active:

F cmscname,ZIIP QUERY

The zIIP instance will be the default unless a CXZPxxxx DD card was added to the CMSC procedure. The zIIP ID will be specified as the response to the command.

Implementing the zIIP Enablement Service

IBM has provided a mechanism for Independent Software Vendors (ISV), such as BMC, to execute portions of ISV product code on zIIP processors at your site. Work executed on a zIIP processor is not charged for usage as with general use processors. As a result, when portions of BMC AMI product code are offloaded to execute on a zIIP processor, it can result in reduced costs.

The CSS zIIP Enablement Service provides a common method to enable selected portions of BMC AMI product code to be eligible to run on a zIIP processor. If available on your system, performance of BMC software products can be enhanced by executing selected portions of the product on a zIIP processor. Execution on a zIIP processor can result in less billable CPU time used and significantly fewer I/O operations for normal product operation.

The CSS Cobol, PL/I, and Assembler language processors are particularly well-suited for zIIP processing. Executing the language processors with zIIP processing enabled can reduce CPU time used by 35 to 65% depending on the size and nature of the compiler listing being processed.

Enabling the service

Before the service can be used, it must be started to enable its API for use by other BMC AMI products. The service will be started when the CMSC is started, if ZIIP_ENABLEMENT=YES. It remains active as long as the system remains running. The service can optionally be stopped, if desired.

Upon successful initialization, the following message will appear in the job log:

CXZPIN010I Initialization successful for ID CPWR

For more information, see Messages-and-codes.

Disabling the service

This service can be temporarily disabled on a job-by-job basis, or completely disabled for the entire system.

Job disablement

To disable the service for a specific job, use the CXZPIGNR DD statement.

This statement will cause the job to execute without using the service. Note that the portions of the product that were designated for zIIP processing will still be executed normally, but not on a zIIP processor.

//CXZPIGNR DD DUMMY

System-wide disablement

If you want to disable the service for all jobs, issue the MVS command ZIIP DELETE to the CMSC as shown in the following example:

F cmscname,ZIIP DELETE

After running this command, the service will no longer be active in the system. Refer to the zIIP commands above to re-enable the service.

 

 

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

BMC AMI Enterprise Common Components 17.02