Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Device definition files z/OS Communications Server: SNA Customization SC27-3666-00 |
|||||||||||||||||||||||||||||||||||||||||||||||||
Within a CPNDEF or NIDDEF definition file, a device's
definition is grouped by consecutive records in the following order:
Any other records that follow within a particular device's definition group are either LU NAME or LU MODEL pairs as described in records 4 and 5 above. This is the model name on the LU definition in the model major node. Each record must be 80 bytes in length. Following is a
description of the format for each record:
All padding within the fields is done with blanks (X'40'). All byte positions up to and including column 34 that are not defined must contain blanks (X'40'). Figure 1 shows an example of a network with PUs and LUs. Following the figure is a table with an example NIDDEF and CPNAME definition file for that network. Figure 1. NIDDEF and CPNAME
example network
After a NIDDEF file is created, do a file definition so that VTAM will be able to locate the FILEDEF. See z/OS Communications Server: SNA Network Implementation Guide for more information about dynamically defining a switched connection in a single-domain environment. |
Copyright IBM Corporation 1990, 2014
|