Enabling communication with BCPii

ZETALY Automated Capacity© architecture sample using BCPii

Figure 9 ZAC architecture with BCPii

Enable BCPii communication on the SE

SETMETHOD=BCPii is required in ZETALY Automated Capacity© PARMLIB.

To enable communication with the SE you must enable the “cross partition authority” on the HMC.

Perform the following steps on the HMC:

1. Select the CPC that is required;
2. Open Single Object Operations;
3. Open the CPC Operational Customization task list;
4. Highlight the CPC icon;
5. Open the Change LPAR Security task, and the Change Logical Partition Security window displays;
6. Check the “Cross Partition Authority” checkbox;

Figure 10 Cross partition authority setting on HMC

1. Select Save and Change.

Make the same updates to all the CPCs you want BCPii to communicate with and not just the CPC on which the BCPii application will execute.

Define BCPii community name on the SE

Perform the following steps on the HMC:

• Select the CPC that is required.
• Open Single Object Operations.
• Select the Console Actions view.
• Select Support Element Settings.
• Open Customize API Settings.

Figure 11 Customize API HMC window

• Check the Enable SNMP API checkbox.
• Make sure that the SNMP agent parameters are blank.
• Add a BCPii community name. Click on Add. When a window is prompted, fill in the following fields:
  • Name: BCPii community (uppercase only 1-16 alphanumeric character).
  • Address: Must be 127.0.0.1 (do not change).
  • Network mask: Must be 255.255.255.255 (do not change).
  • Access type: Read/Write.
• Save the changes.

Do the same updates to all the CPCs you want BCPii to communicate with.

Figure 12 Customize API settings sample

Repeat all previous steps on all the other SE associated with the CPCs with which you want to access BCPii.

Set BCPii permissions in HMC as of Z14

Starting from Z14, after an installation or machine upgrade, new BCPii access permission setting options are available on the HMC.

The factory default value of this option is set to ‘Disabled’ for each z14 LPAR.

Existing applications that use the BCPii transport cannot run on a z14 LPAR with this default setting. For these applications, BCPii access must be re-enabled on the z14 LPAR by changing the default value to ‘Send’ or ‘Receive’ or ‘Send & Receive’, depending on whether the LPAR is BCPii request origin, target, or both.

The new facility is part of the HMC LPAR Security Settings task. It allows to change BCPii permissions at run- time, in the image activation profile, or both.

Figure 13 Sample HCM panel showing BCPii permission settings

Define BCPII general SAF authority

A sample JCL (RACFBCPI/ACF2BCPI/TSSBCPI) is provided in the ZAC sample library to define SAF resources.

Customize the JCL with your parameters:

• BCPii community name (uppercase only);
• Your NetID;
• The ZAC STC user ID.

Submit this JCL for each CPC on which the LPARs managed by ZAC are installed.

Code sample 6 RACF definition sample

Startup and shutdown BCPii

The BCPii address space normally does not need to be started or shut down. BCPii initialization occurs during system IPL.

Start Command:

S HWISTART

Stop Command:

P HWIBCPII

Testing the BCPii communication

(This step is only required for SETMETHOD=BPCII.)

You can test the communication between the LPAR on which ZETALY Automated Capacity© runs and the HMC/SE. The test program will attempt to modify Define Capacity and/or the weight of LPAR. You must supply a correct Netid in PARM= on the EXEC card and set values in the SYSIN dataset.

This job requires a valid product authorization key. This key is the same as the product key delivered by ZETALY® and must be set in the KEYS dataset.

The output indicates if the modification(s) were successful. If they were, a Define Capacity and/or the Weight are modified. You may verify the success on the HMC. If the communication did not work, an explanation of the trouble is written into the SYSOUT dataset. The SYSOUT dataset will contain BCPii error messages and if available, additional standard BCPii diagnostic fields.

In case of failure of the job, refer to “MVS Programming: Callable Services for High-Level Languages” Part 6

(BCPii) for more information.

For more information about BCPii:

http://www.redbooks.ibm.com/redbooks/pdfs/sg247804.pdf http://publib.boulder.ibm.com/infocenter/zos/v1r11/index.jsp?topic=/com.ibm.zos.r11.ieac100/strshu.ht m