Setting up Guest Specialty Engines
Complete the following steps to define a virtual configuration that uses virtual zIIPs:
- If you want virtualization support, ensure that a real zIIP is available in the processor
configuration. From a user with privilege class A, B, C, or E, issue CP QUERY PROCESSORS EXPANDED to
view the types of real processors available and the logical partition mode. For example:
The logical partition mode must be either ESA/390, General, or z/VM®.query processors expanded PROCESSOR 00 MASTER CP PROCESSOR 01 ALTERNATE CP PROCESSOR 02 ALTERNATE CP PROCESSOR 03 ALTERNATE ZIIP PROCESSOR 04 ALTERNATE ZIIP PARTITION MODE ESA/390 - Log on the z/VM guest. The virtual configuration mode defaults to ESA390 (for an XA, ESA, or XC virtual machine) or GENERAL (for a Z virtual machine). Check this by issuing:
query vconfig MODE = ESA390 - Use the CP DEFINE CPU command to define the virtual specialty engines:
define cpu 2 type ziip define cpu 5 type ziip define cpu 8 type cp - Issue CP QUERY VIRTUAL CPUS to view the virtual CPUs that are defined and the CPUAFFINITY
status. For example:
query cpus CPU 00 ID FF319B9E20948000 (BASE) STOPPED CP CPUAFF ON CPU 02 ID FF319B9E20948000 STOPPED ZIIP CPUAFF ON CPU 05 ID FF319B9E20948000 STOPPED ZIIP CPUAFF ON CPU 08 ID FF319B9E20948000 STOPPED CP CPUAFF ON - IPL z/OS® or other guest operating system that will make use of the zIIPs.
- If you want to switch between simulation and virtualization,
issue CP SET CPUAFFINITY from a user with privilege class A. For example:
set cpuaffinity off for user test1 set cpuaffinity on for user test1
Complete the following steps to define a virtual configuration that uses virtual IFLs:
- If you want virtualization support, ensure that a real IFL is available in the processor
configuration. From a user with privilege class A, B, C, or E, issue CP QUERY PROCESSORS EXPANDED to
view the types of real processors available and the logical partition mode. For example:
query processors expanded PROCESSOR 00 MASTER CP PROCESSOR 01 ALTERNATE CP PROCESSOR 02 ALTERNATE ZIIP PROCESSOR 03 ALTERNATE IFL PROCESSOR 04 ALTERNATE ICF PARTITION MODE z/VM - Log on the z/VM guest.
The virtual configuration mode must be LINUX. Issue QUERY VCONFIG
to check the virtual configuration mode and SET VCONFIG MODE to change
it, if necessary. For example:
query vconfig MODE = ESA390 set vconfig mode linux MODE = LINUX Storage cleared - system reset. - Issue the CP DEFINE CPU command to define the virtual IFLs. If the base CPU is not type IFL, it
must be redefined to be type IFL. For example:
q cpus CPU 00 ID FF03233F20640000 (BASE) CP CPUAFF ON Ready; def cpu 0 type ifl CPU 00 redefined as TYPE IFL Storage cleared - system reset. def cpu 2 type ifl 00: CPU 02 defined 00: def cpu 4 type ifl 00: CPU 04 defined - Issue CP QUERY VIRTUAL CPUS to view the virtual CPUs that are defined and the CPUAFFINITY
status. For example:
00: q cpus 00: CPU 00 ID FF03233F20640000 (BASE) STOPPED IFL CPUAFF ON 00: CPU 02 ID FF03233F20640000 STOPPED IFL CPUAFF ON 00: CPU 04 ID FF03233F20640000 STOPPED IFL CPUAFF ON - Load (IPL) Linux® to make use of the IFLs.
Complete the following steps to define a virtual configuration for test purposes which simulates a z/VM mode logical partition:
- If you want virtualization support, ensure that real specialty engines are available in the
processor configuration. From a user with privilege class A, B, C, or E, issue CP QUERY PROCESSORS
EXPANDED to view the types of real processors available and the logical partition mode. For example:
query processors expanded PROCESSOR 00 MASTER CP PROCESSOR 01 ALTERNATE CP PROCESSOR 02 ALTERNATE ZIIP PROCESSOR 03 ALTERNATE IFL PROCESSOR 04 ALTERNATE ICF PARTITION MODE z/VM - Log on the z/VM guest.
The virtual configuration mode must be VM. Issue QUERY VCONFIG to
check the virtual configuration mode and issue SET VCONFIG MODE to
change it, if necessary. For example:
query vconfig MODE = ESA390 set vconfig mode vm MODE = VM Storage cleared - system reset. - Issue the CP DEFINE CPU command to define the desired virtual CPUs. For example:
00: def cpu 1 type ziip 00: CPU 01 defined 00: def cpu 2 type ifl 00: CPU 02 defined 00: def cpu 3 type icf 00: CPU 03 defined 00: def cpu 4 type ziip 00: CPU 04 defined - Issue CP QUERY VIRTUAL CPUS to view the virtual CPUs that are defined and the CPUAFFINITY
status. For example:
00: q cpus 00: CPU 00 ID FF046F5A20848000 (BASE) STOPPED CP CPUAFF ON 00: CPU 01 ID FF046F5A20848000 STOPPED ZIIP CPUAFF ON 00: CPU 02 ID FF046F5A20848000 STOPPED IFL CPUAFF ON 00: CPU 03 ID FF046F5A20848000 STOPPED ICF CPUAFF ON 00: CPU 04 ID FF046F5A20848000 STOPPED ZIIP CPUAFF ON - Load (IPL) z/VM from the guest virtual machine. You can then log on users of this z/VM image that can take advantage of the virtual specialty engines.
To define a guest coupling virtual configuration that uses virtual ICFs:
- If you want virtualization support, ensure that a real ICF is available in the processor
configuration. From a user with privilege class A, B, C, or E, issue CP QUERY PROCESSORS EXPANDED to
view the types of real processors available and the logical partition mode. For example:
The logical partition mode must be z/VM in order to run a Coupling Facility virtual machine with virtual ICFs.query processors expanded PROCESSOR 00 MASTER CP PROCESSOR 01 ALTERNATE CP PROCESSOR 02 ALTERNATE ZIIP PROCESSOR 03 ALTERNATE IFL PROCESSOR 04 ALTERNATE ICF PARTITION MODE z/VM - Autolog the CFVM guest. In a z/VM mode logical partition, the CPU type for all virtual CPUs defined for the CFVM virtual machine is changed to ICF automatically during autolog processing. This automatic change allows Coupling Facility workload to be dispatched on real ICFs, because CPUAFFINITY is set on by default for all users during logon.
- If you want the Coupling Facility workload to be dispatched on
real CP processors, issue CP SET CPUAFFINITY from a user with privilege
class A. For example:
set cpuaffinity off for user cfvm1