z/OS MVS Setting Up a Sysplex
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Understanding the node descriptor

z/OS MVS Setting Up a Sysplex
SA23-1399-00

Because z/VM® Guest Coupling Simulation Support simulates a real coupling facility, the software must create a unique Node Descriptor (ND) for every CF Service Machine to be used. z/VM dynamically creates an architecturally correct unique ND when the message facility environment is created in the CF Service Machine. The method used to create the DN is documented so that the user can generate the administrative policy for CFRM in MVS™. This will allow MVS's CFRM policy generator to be used and there is no need for the user to specify an ND. This is exactly how it works with the real hardware.

Use the following information when defining a coupling facility in the CFRM Administrative Policy Utility, IXCMIAPU:
  • Type Number (TYPE) - SIMDEV specifies that this is a z/VM simulated message device type.
  • Manufacturer (MFG) - IBM® indicates IBM as the manufacturer.
  • Plant (PLANT) - EN indicates Endicott as the manufacturing plant.
  • Sequence # (SEQUENCE) - The 12-byte field will contain the CF Service Machine user ID right justified. Pad all leading unused characters with EBCDIC zeros. For example, if a CF Service Machine of CFCC1 is specified, SEQUENCE is 0000000CFCC1.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014