Actions you can take before you order a z196 and z114 server

You can perform the following migration actions before you order or install a z196 or z114 server:

Review the sysplex configuration in which the zEnterprise® server will participate. See Restrictions for a z196 or z114 server for a description of the limitations when using IBM zEnterprise EC12 servers with zEnterprise z196 or z114 servers or with other earlier servers in a Parallel Sysplex®.
Implement STP (or a Mixed-CTN) timing network. This action is needed because Sysplex Timers (9037-002) are not supported on zEnterprise servers.
Migrate from ICB-4 to InfiniBand coupling links. This action is needed because ICB-4 links are not supported on zEnterprise servers. If desired, you can take this action after you order a zEnterprise server, as you upgrade to the new server.
Migrate from unsupported hardware features to newer technology. This action is needed because FICON® Express®, FICON Express2, Crypto Express2, and OSA-Express2 10 GbE LR are not supported on zEnterprise servers.
Install the necessary z/OS® service, as indicated in PSP buckets. For a zEnterprise 196 CPC, PTFs are identified in the 2817DEVICE PSP bucket (Subset 2817/ZOS). For a zEnterprise 114 CPC, PTFs are identified in the 2818DEVICE PSP bucket (Subset 2818/ZOS). For an IBM® zEnterprise BladeCenter Extension (zBX) attached to your z196 CPC or to your z114 CPC, the PTFs are identified in the 2458DEVICE PSP bucket (Subset 2458/ZOS). In each PSP bucket, the content is dependent on the z/OS release you will run on the zEnterprise server. If you reviewed the PSP buckets some time ago, review them again to ensure that any newly identified z/OS service has been installed. To assist you in determining if you have the recommended service (identified in these PSP buckets) installed on your system, you can use the SMP/E REPORT MISSINGFIX command in conjunction with the FIXCAT type of HOLDDATA, as follows:
1. 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.
2. 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.z196-2817
  - IBM.Device.Server.z196-2817.ParallelSysplexInfiniBandCoupling
  - IBM.Device.Server.z196-2817.ServerTimeProtocol
  - IBM.Device.Server.z196-2817.zHighPerformanceFICON
  - IBM.Device.Server.z114-2818
  - IBM.Device.Server.z114-2818.ParallelSysplexInfiniBandCoupling
  - IBM.Device.Server.z114-2818.ServerTimeProtocol
  - IBM.Device.Server.z114-2818.zHighPerformanceFICON
  - IBM.Device.Server.z114-2818.UnifiedResourceManager
  - IBM.Device.Server.zBX-2458
  - IBM.Device.Server.zBX-2458.ISAOPT
  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.
3. 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.
Note:
1. You can also use the Service Link PSP Service Extraction tool.
2. 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 and Sizer tools. 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. Run the Sizer utility, an authorized z/OS program that you can download, 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. z196 or z114 servers are initially shipped with CFCC Level 17; prepare to make the necessary changes as indicated by the tool. You can find the CFSIZER tool at Coupling Facility sizer.
Plan for the fixed HSA enhancement on a zEnterprise server. On zEnterprise (and z10™) servers, preplanning requirements are minimized by offering a fixed HSA and introduction of the ability to seamlessly include such events as creation of LPARs, inclusion of logical subsystems, changing logical processor definitions in an LPAR, and introduction of cryptography into an LPAR.
Decide on the steps to take for your migration to a z196 or z114 server. As a guide, see Recommended migration steps for a z196 and z114 server. Also, note the following:
- You should compare the cryptographic support you currently have installed with the support required for the functions you plan to use on the zEnterprise z196 and z114 server. Several cryptographic support web deliverables have been made available for various z/OS releases. The newer cryptographic web deliverables include the previous function (when applicable) for that particular z/OS level. Note that you can use the newer cryptographic web deliverables on servers before the zEnterprise servers, that is, on z10 and z9® (or earlier) servers.
- The level of function provided for cryptographic support differs by z/OS release and the ICSF web deliverable that is installed. For z/OS V1R12 and later, exploitation of zEnterprise z196 and z114 cryptographic support is provided by Cryptographic Support for z/OS V1R11-V1R13 (FMID HCR7790) web deliverable. Note that this level of ICSF is not integrated in z/OS V1R13 and must be downloaded and installed even after ordering a z/OS V1R13 ServerPac.
Review the new mnemonics introduced for the z196 or z114 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 PK97799 is installed. This will probably cause assembler error messages and possibly cause generation of incorrect object code. For a tool to help in identifying mnemonic conflicts, see Techdoc PRS5289 at the IBM Techdocs website.
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 PK97799. 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 the HLASM opcode table, see HLASM Programmer's Guide.