z/OS Communications Server: SNA Network Implementation Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Associations and using the directory definition file for CMIP services

z/OS Communications Server: SNA Network Implementation Guide
SC27-3672-01

To implement CMIP services and the VTAM® topology agent, you must have a directory definition file. The directory definition file controls:
  • The associations that CMIP services on this host has with other CMIP services and with itself
  • Whether security is to be used on each association
  • Name mapping
  • Address mapping

The directory definition file is read when CMIP services is started. Before an association is started, CMIP services checks the file to determine whether the association is allowed. The directory definition file is checked only at the time the association is established. It is not checked at every exchange between partners in an association.

If the directory definition file indicates that the association is allowed, it continues to be allowed until the association ends in one of the following ways:
  • Timing out
  • Being ended by the application program
  • CMIP services ending
  • VTAM ending

If you allow an association and then decide not to allow that association, you cannot stop the association until you restart CMIP services 1. Even if you change the directory definition file to indicate that the association is no longer allowed, issuing the MODIFY TABLE command does not stop the association.

1 You can also stop an association by writing a CMIP application to do so. For further information, see the z/OS Communications Server: CMIP Services and Topology Agent Guide .

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014