Actions you can take before you order a zEC12 or zBC12 server
- Review the sysplex configuration in which the zEC12 or zBC12 server will participate. See Restrictions for a zEC12 or zBC12 server for the limitations of using zEC12 or zBC12 servers with certain earlier servers in a Parallel Sysplex®.
- Implement STP (or a Mixed-CTN) timing network. This action is necessitated because Sysplex Timers (9037-002) are not supported on zEC12 or zBC12 servers.
- Migrate from ICB-4 to InfiniBand coupling links. This action is necessitated because ICB-4 links are not supported on zEC12 or zBC12 servers. If desired, you can take this action after you order a zEC12 or zBC12 server, as you upgrade to the new server.
- Migrate from unsupported hardware features to newer technology. This action is necessitated because FICON® Express®, FICON Express2, Crypto Express2, and OSA-Express2 10 GbE LR are not supported on zEnterprise® servers. See Restrictions for a zEC12 or zBC12 server, Replace unsupported devices, and Provide for new device installations.
- Install the necessary z/OS® service,
as indicated in PSP buckets.
- For an IBM zEnterprise BC12 CPC, PTFs are identified in the in the 2828DEVICE PSP bucket (Subset 2828/ZOS).
- For an IBM zEnterprise EC12 CPC, PTFs are identified in the 2827DEVICE PSP bucket (Subset 2827/ZOS).
- For an IBM® zEnterprise BladeCenter Extension (zBX) attached to your zEC12 CPC or zBC12 CPC, the PTFs are identified in the 2458DEVICE PSP bucket (Subset 2458/ZOS).
- Acquire and RECEIVE the latest HOLDDATA onto your z/OS system(s). Use your normal service acquisition portals or download the two (2) year HOLDDATA directly from http://service.software.ibm.com/holdata/390holddata.html. Ensure you select Full from the Download NOW column (last 730 days) to receive the FIXCAT HOLDDATA, as the other files do not contain FIXCAT HOLDDATA.
- Run the SMP/E REPORT MISSINGFIX command on your z/OS systems and specify one or
more of the following Fix Categories (FIXCAT):
- IBM.Device.Server.zEC12-2827
- IBM.Device.Server.zEC12-2827.Exploitation
- IBM.Device.Server.zEC12-2827.ParallelSysplexInfiniBandCoupling
- IBM.Device.Server.zEC12-2827.ServerTimeProtocol
- IBM.Device.Server.zEC12-2827.zHighPerformanceFICON
- IBM.Device.Server.zEC12-2827.UnifiedResourceManager
- IBM.Function.zEDC
- IBM.Device.Server.zBC12-2828
- IBM.Device.Server.zEC12-2828.Exploitation
- IBM.Device.Server.zBC12-2828.ParallelSysplexInfiniBandCoupling
- IBM.Device.Server.zBC12-2828.ServerTimeProtocol
- IBM.Device.Server.zBC12-2828.zHighPerformanceFICON
- IBM.Device.Server.zBC12-2828.UnifiedResourceManager
The report will identify any missing coexistence and fallback PTFs for that system. For complete information about the REPORT MISSINGFIX command, see SMP/E for z/OS Commands.
- Periodically, you might want to acquire the latest HOLDDATA and rerun the REPORT MISSINGFIX command to find out if there are any new PTFs recommended for the zEnterprise servers.
Notes:- You can also use Service Link's PSP Service Extraction tool.
- Because the Enhanced PSP Tool (EPSPT) was removed the end of 2010, you can no longer use that tool to identify missing PSP bucket service. You should use SMP/E’s Fix Category support, which is fully integrated into SMP/E procedures and IBM product and service deliverables.
- Run the CFSIZER tool. If you are moving your coupling
facilities and the coupling facility structures will be on higher
CFCC levels than they were previously, run the Coupling Facility
Structure Sizer (CFSIZER) tool to find out if you have to increase
coupling facility structure sizes.
If ordered before September 2013, zEC12 servers initially ship with CFCC Level 18. For zEC12 and zBC12 servers ordered after September 2013, the servers ship with CFCC Level 19; prepare to make the necessary changes as indicated by the tool.
You can download the CFSIZER tool at Coupling Facility sizer. Also see Update your CFRM policy with coupling facility structure size changes.
Note: After you make a coupling facility available on the new hardware, you can run the Sizer utility, an authorized z/OS program, to evaluate structure size changes. The Sizer utility is distinct from CFSIZER, and should be run after the new hardware (CFLEVEL) is installed, but before any CF LPAR on the new hardware is populated with structures. You can download the Sizer utility at http://www.ibm.com/systems/support/z/cfsizer/altsize.html. - Decide on the steps you will take for
your migration to a zEC12 or zBC12 server. In addition to the
steps listed here in Actions you can take before you order a zEC12 or zBC12 server,
as a guide, also see Migration and exploitation considerations for zEC12 and zBC12 server functions. Also, note the following web
deliverables considerations.
The level of function provided for cryptographic support differs by z/OS release and the ICSF web deliverable that is installed. Toleration PTFs are also available for some cryptographic web deliverables:
Consider the following:- For z/OS V1R13 and z/OS V2R1, if you require the cryptographic enhancements support for CCA (including Export TDES key under AES transport key, Diversified Key Generation CBC, IPEK, RKX key wrapping method, and integration of UDX into CCA), you must install the web deliverable Cryptographic Support for z/OS V1R13-z/OS V2R1 (FMID HCR77A1). You must also perform the required ICSF migration actions.
- PTFs for coexistence: Coexistence PTFs
must be installed on older levels of ICSF. To assist in identifying
the coexistence service, you can use the following Fix Categories:
- IBM.Coexistence.ICSF.z/OS_V1R11-V1R13-HCR7790
- IBM.Coexistence.ICSF.z/OS_V1R12-V1R13-HCR77A0
- IBM.Coexistence.ICSF.z/OS_V1R13-V2R1-HCR77A1
If you plan to use the , then similar to what you might be doing today to enable other z/OS priced features, you must notify IBM that you are starting to use the feature, update the IFAPRDxx PARMLIB member to specify that the z/OS ZEDC software feature is enabled, and follow the z/OS V2R2 documentation to customize the exploiting functions. You should also ensure that all z/OS V1R13 systems that will access zEDC compressed data have the required toleration maintenance installed to enable software decompression.
- Review the new mnemonics introduced for the zEC12
or zBC12 server. The new mnemonics might collide with (be identical
to) the names of assembler macro instructions you use or provide.
In the event of such collisions, the HLASM’s default opcode
table (UNI) will treat specification of these names as instructions
when APAR PM49761 and PM86821 are installed. This will probably
cause assembler error messages and possibly cause generation of incorrect
object code. If you write programs in Assembler Language, you should compare the list provided in z/Architecture® Principles of Operation, SA22-7832, to the names of assembler macro instructions you use or provide, to identify any such conflicts or collisions that would occur following installation of HLASM APAR PM49761 and PM86821. If a conflict is identified, take one of the following actions:
- Change the name of your macro instruction.
- Specify PARM=’…OPTABLE(YOP)…’ (or some other earlier opcode table).
- Specify a separate ASMAOPT file containing assembler options, such as in the previous method (this method requires no changes to source code or JCL).
- Add, as the first statement of your source program, *PROCESS OPTABLE(YOP).
- Specify the PROFILE option either in JCL or the ASMAOPT file, and the specified or default member of the SYSLIB data set is copied into the front of the source program.
- If you must use both a new instruction and a macro with the same
name in an assembly, you can use the following technique (where XXX
is a sample mnemonic):
Assume the default OPTABLE(UNI) is in effect XXX a,b new instruction PUSH ACONTROL save current optable definition ACONTROL OPTABLE(YOP) switch optable dynamically XXX r,s,t macro invocation POP ACONTROL restore previous definition XXX c,d new instruction
For more information about HLASM opcode table, see HLASM Programmer's Guide.
- Plan for changes to your global resource serialization
complex with the zEC12 or zBC12 server. If you use a global resource
serialization ring complex that spans more systems than is part of
the sysplex or does not use sysplex signalling for communications
within the complex, you need to take migration actions. Instead of
using global resource serialization ring, consider using the global
resource serialization star configuration in a sysplex. You can take
the following actions before you install the zEC12 or zBC12 server:
- Migrate to a Parallel Sysplex that uses the recommended global resource serialization star complex.
- Convert to a basic sysplex that uses XCF sysplex signalling with global resource serialization ring instead of GRS-managed channel-to-channel (CTC) communications.