content_image/987017.jpg
<img src='content_image/987017.jpg'>

Note that the name LCL701 in the sample V NET  command is the VTAM name of the terminal. 

This name is not  related to the LUname specified in the zPDT devmap. A 3270 session has both an aws3274 LUname (specified in the zPDT devmap) and a VTAM name (specified in VTAMLST). Also, MVS operator consoles are not specified in VTAM and have no VTAM name. This terminology is unfortunate because the aws3274 LUname (used to link a TN3270e session to an aws3274 definition) is not necessarily the same LUname associated with a VTAM operation. 

Also, note that zPDT does not support the VMAC function from z/OS. The only virtual mac supported is generated on z/VM with the layer-2 vswitch. 

## 7.11 Non-QDIO operation 

Important:  Starting with z/OS 2.3, the OSA/SF program (used to help configure non-QDIO OSAs) is not available and the replacement function is not supported by zPDT. 

When using the non-QDIO interface to the emulated OSA-Express2 function, the key parameters might look like the following example: 

Devmap [manager] name awsosa 22 --path=F0 --pathtype=OSE device E20 osa osa --unitadd=0 device E21 osa osa --unitadd=1 z/OS TCP/IP Profile DEVICE LCS1 LCS E20 AUTORESTART LINK ETH1 ETHERNET 0 LCS1 HOME 192.168.1.81 ETH1 ... BEGINRoutes ; Destination Subnet Mask FirstHop Link Size ROUTE 192.168.1.0 255.255.255.0 = ETH1 MTU 1492 ROUTE DEFAULT 192.168.1.1 ETH1 MTU DEFAULTSIZE ENDRoutes ... START LCS1 

This example assumes that z/OS contains an appropriate CTC or OSA definition for addresses E20 and E21.$^{33}$ Different addresses can be used, of course, but they must match 

