Adjust parameters to start IOSHMCTL in TPC-R Basic Hyperswap environment

Description: With APAR OA40866 applied (with one of the following PTFs: UA71220 for z/OS V2R1, or UA71219 for z/OS V1R13), parameters supplied in the JCL to start PGM=IOSHMCTL may be rejected. APAR OA40866 introduced new function which caused JCL parameter checking to now be enforced. As a result, unsupported parameters will be rejected and IOSHMCTL will not start due to JCL failures.

For example:

ASA101I SYNTAX ERROR: MODE=EXT, WAS SEEN, WHERE ONE OF 
(SOCKPORT=) 
WOULD BE CORRECT. 
DETECTING MODULE IS IOSHMCTL

Prior to APAR OA40866, unsupported parameters would be ignored and IOSHMCTL would start without any JCL failures.

Note: This problem is a documentation error where some examples of JCL to start the Basic HyperSwap address space used incorrect parameters. At this time with Basic HyperSwap Sockets Server APAR OA40866 applied, the only parameter allowed to the IOSHMCTL program is 'SOCKPORT=port_num'. Any other parameters are rejected.

Element or feature:

BCP.

When change was introduced:

z/OS V2R1 and z/OS V1R13, both with APAR OA40866 applied.

Applies to migration from:

z/OS V1R13 without APAR OA40866 applied, and z/OS V1R12.

Timing:

Before the first IPL of z/OS V2R1.

Is the migration action required?

Yes, if you have unsupported parameters specified to start the Basic HyperSwap address space.

Target system hardware requirements:

None.

Target system software requirements:

None.

Other system (coexistence or fallback) requirements:

None.

Restrictions:

None.

System impacts:

None.

Related IBM® Health Checker for z/OS® check:

None.

Steps to take: When applying the PTF for APAR OA40866, make sure that any HSIB procedures to start IOSHMCTL do not include unsupported parameters. For example, the following JCL may be used:

//HSIB JOB MSGLEVEL=(1,1),TIME=NOLIMIT,REGION=0M 
//IEFPROC EXEC PGM=IOSHMCTL

Tip: Some older publications, including Redpapers, may have documented incorrect parameters on the PARM statement used in the examples of suggested procedures for starting IOSHMCTL. It is best to refer to the latest TPC-R publications for current supported parameters.

Reference information: APAR OA46189, which describes the potential JCL failures after installing PTFs for APAR OA40866.