Format the ARM couple data set for long symbol table support

Description

z/OS V2R2 systems require an ARM couple data set (CDS) that is formatted for long symbol table support. Otherwise, V2R2 systems can join the sysplex, but are not ARM-capable. You can establish this format level by using the z/OS V2R2 level of the IXCL1DSU format utility (either from a z/OS V2R2 system or with a STEPLIB to a z/OS V2R2 MIGLIB) to format the CDS.

Table 1 provides more details about the migration action. Use this information to plan your changes to the system.

Table 1. Information about this migration action
Element or feature: BCP.
When change was introduced: z/OS V2R2.
Applies to migration from: z/OS V2R1 and z/OS V1R13.
Timing: Before the first IPL of z/OS V2R2.
Is the migration action required? Yes, if systems are intended to use ARM functions.
Target system hardware requirements: None.
Target system software requirements: None.
Other system (coexistence or fallback) requirements: None required. Systems at lower-level releases can use an ARM CDS formatted for long symbol-table support. However, a DISPLAY XCF,COUPLE,TYPE=ARM command from a down-level system cannot indicate that the HBB77A0 level of symbol table is in use unless you apply the PTFs for OA46977. With the PTFs for OA46977 applied, the response message IXC358I contains the text HBB77A0 SYMBOL TABLE SUPPORT.
Restrictions: None.
System impacts: None.
Related IBM Health Checker for z/OS check: None.

Steps to take

Follow these steps:
  1. Use the IXCL1DSU (format couple data set utility) at the z/OS V2R2 level to obtain at least two ARM CDSs at the HBB77A0 format level, with:
    • ARM CDS primarydsname on volume primaryvolume
    • ARM CDS alternatedsname on volume alternatevolume
  2. After you create the HBB77A0 format-level ARM CDSs, you can dynamically bring them into your existing sysplex with these SETXCF commands:
    • SETXCF COUPLE,TYPE=ARM,ACOUPLE=(primarydsname,primaryvolume)
    • SETXCF COUPLE,TYPE=ARM,PSWITCH
    • SETXCF COUPLE,TYPE=ARM,ACOUPLE=(alternatedsname,alternatevolume)
  3. Remember to also specify, in your COUPLExx member of SYS1.PARMLIB, these two ARM CDSs as the primary and alternate for any future sysplex IPLs :
    DATA                               
  TYPE(ARM)                         
  PCOUPLE(primarydsname,primaryvolume)
  ACOUPLE(alternatedsname,alternatevolume)

Reference information

For more information, see the following references:
Parent topic: BCP actions to perform before the first IPL of z/OS V2R2