Device definition files

Within a CPNDEF or NIDDEF definition file, a device's definition is grouped by consecutive records in the following order:

Record: Content
1: DEVICE ID
The DEVICE ID is either a CPNAME or a NODEID. The NODEID consists of the IDBLK and IDNUM.
2: PU NAME
PU NAME is the name you want the PU to have once the connection is established.
3: PU MODEL and a station address (the station address, ADDR, is optional).
PU MODEL is the PU label in the model major node.
4: LU NAME
This is the actual name that VTAM® uses to refer to this particular LU, a unique net name.
5: LU MODEL and a LOCADDR value
The LOCADDR field is optional and can be used to override the LOCADDR value specified in the subject model.

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:

000000000111111111122222222223333333333444444444455555555556 . . . 8
123456789012345678901234567890123456789012345678901234567890       0
 
deviceid                          line commentary (optional)
         puname                   .
         pumodel  xxx             .
         luname                   .
         lumodel  xxx             .
         luname                   .
         lumodel  xxx             .
         .                        .
         .                        .
         .                        .

Column
1–8: A left-adjusted alphanumeric CP name (1–8 bytes in length) in the CPNDEF file or, an EBCDIC representation of the hexadecimal NODEID (8 bytes in length) in the NIDDEF file
9: Blank
10–17: A left-adjusted PU NAME, PU MODEL, LU NAME, or LU MODEL
18: Blank
19–21: If the device's definition contains a LOCADDR value, these columns contain a right-adjusted LOCADDR (0—255).
22–34: Blanks
35–80: Optional line commentary

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

Shows example network with PUs, LUs; table following figure is a NIDDEF and CPNAME definition file for that network

Table 1. NIDDEF and CPNAME definition file example
Record	Content	NIDDEF	CPNAME
1	DEVICE ID	00100001
2	PU NAME	SWPUAI01
3	PU MODEL; there also can be an ADDR (station address)	SPUMOD01
4	LU NAME	SLIDAI01
5	LU MODEL; there also can be a LOCADDR	SLUMOD01 2
4	LU NAME	SLIDAI0A
5	LU MODEL; there also can be a LOCADDR	SLUMOD01
1	CPNAME		SWPNAME
2	PU NAME		SWPUAI02
3	PU MODEL; there also can be an ADDR (station address)		SPUMOD01
4	LU NAME		SLIDAI02

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.