gtpm3m0z | Multi-Processor Interconnect Facility Reference |
Detailed below are the MPIF commands required to initialize the sample MPIF
loosely coupled complex.
- Enter the following messages from Processor A in 1052 state:
- ZMPIF SET SYSTEM,NAME-SYSA,NUSER-10,NCONN-10,NDNT-10,NPAN-10,QDEPTH-15
- ZMPIF SET COMPLEX,NSYS-10,NUSER-10,CONTIME-10,PATHTIME-10,SYSTIME-10
- ZMPIF SET CLASS,CODE-A,RBUFF-4096,WBUFF-4096,PROTECT-Y,BLOCK-Y,LOADB-Y
- ZMPIF SET CLASS,CODE-B,RBUFF-4096,WBUFF-4096
- ZMPIF DEF DEVICE,NAME-$3088A1,SDA-32/0320,MODEL-2,CLASS-A
- ZMPIF DEF DEVICE,NAME-$3088A2,SDA-32/0340,MODEL-2,CLASS-AB
- ZMPIF DEF PATH,NAME-A1TOB1,SYSTEM-SYSB,CLASS-A
- ZMPIF DEF PATH,NAME-A2TOB2,SYSTEM-SYSB,CLASS-A
- ZMPIF DEF PATH,NAME-A3TOB3,SYSTEM-SYSB,CLASS-B
- Enter the following messages from Processor B in 1052 state:
- ZMPIF SET SYSTEM,NAME-SYSB,NUSER-10,NCONN-10,NDNT-10,NPAN-10,QDEPTH-15
- ZMPIF DEF PATH,NAME-B1TOA1,SYSTEM-SYSA,CLASS-A
- ZMPIF DEF PATH,NAME-B2TOA2,SYSTEM-SYSA,CLASS-A
- ZMPIF DEF PATH,NAME-B3TOA3,SYSTEM-SYSA,CLASS-B
- Re-IPL both processors for defined parameters to take effect.
Notes:
- The values of parameters that have been used here are for the example only
and you should review them and change them for your specific
configuration. See TPF Operations for
details.
- The SET COMPLEX, SET CLASS, and DEFINE
DEVICE commands need to be entered from only one of the processors in
the loosely coupled complex because the parameters are either in shared
records or are propagated through the loosely coupled complex.
- The only restriction on the sequence of commands entered is that the
SET CLASS command must be entered before any PATHs are defined for
that class. If you try to enter a DEF PATH command before
SET CLASS, the DEF PATH command is rejected.
- If more processors exist in the loosely coupled complex than is shown in
this example, only the SET SYSTEM and DEF PATH commands
need be entered on those processors.
- In this example, load balancing is requested for CLASS-A
paths. Load balancing is achieved because there is CTC support for 2
channels across which the load can be balanced. If there was one
physical 3088 communication unit that had two channels attached to each
processor, MPIF load balances across the channels.
- Note:
- This tuning is not true load balancing since there is only one physical 3088
communication unit through which all messages must pass.
- The MPIF IPC path should be defined first because the loosely coupled
complex will not be able to initialize if it is unable to start a path that
can be used for MPIF IPC. In this example, MPIF IPC should be assigned
to CLASS-A.
- The procedure defined here could be used for non-loosely coupled
complexes; in which case, the note on MPIF IPC would not apply.