This time, we will see how to manually configure an OSA device in the IBM Z Development & Test Environment emulator and the TCPIP communication with the z/OS system. It is very easy to configure and, this way, we will be able to access applications like z/OSMF, ZOWE, etc.

 

As a reference we will use the zPDT Redbook.

 

In Chapter 7 - LANs, different scenarios are shown according to the type of configuration we want. In my case, I will follow the steps of scenario 4 because it allows connection to the z/OS system from other systems in the LAN. This configuration requires a fixed IP for the z/OS system.

We start by configuring the Devmap file.

NOTE: If we generated this file with the utility "create_devmap.pl", at the end of the file we will have configuration examples.

 

We are going to add a new emulated OSA (emulates a real OSA card used in the mainframe). In this case, it will be an OSA QDIO (OSD).

More information about OSA QDIO:

Queued Direct I/O (QDIO)

 

Add the following configuration in the Devmap file:

 

 

The number "0022" can be any hexadecimal that we do not repeat in other devices in the file.

For devices 404 (READ), 405 (WRITE) and 406 (DATAPATH), we must choose some channels that are not in use and correspond to the type "OSA" in the IODF.

 

Once we start the z/OS system, we will check the VTAM configuration to define this new OSA. In the case of this ADCD version, the OSA is already defined.

Go to the corresponding VTAMLST library. In this case, the definition we were going to include already exists in the OSATRL2 member.

 

For this version of ADCD, the default list of VTAM is loaded (the 00 list). If we check the ATCCON00 member of the same VTAMLST library, we will see that the configuration of the OSATRL2 member is already activated during the startup of VTAM.

 

If we want a confirmation that it is active, we can use the following command from SDSF:

 

Now let's set up TCPIP.

To know the "PROFILE" and "SYSTCPD" you use, we must look at the TCPIP task. In my case, it is:

PROFILE - ADCD.Z24A.TCPPARMS(PROF2)

SYSTCPD - ADCD.Z24A.TCPPARMS(TCPDATA)

 

The setting I will use in the PROFILE parameters is:

IMPORTANT: The PORTA configuration should not be deleted.

 

Now let's change the parameters of the SYSTCPD. In my case, I will change the following (adjust it according to your requirements):

HOSTNAME is the name of the system.

DOMAINORIGIN is the domain name (for example, we will access this system with the address s0w1.emuzos.com).

 

Finally, it would be necessary to assign the IP that we have configured in the system to the domain name that we have put, so that it can resolve this name, and add the DNS servers.

This is done in the "RESOLVER" task. To find out which configuration files we are using, we go to SDSF and use the command:

Check the parameter GLOBALTCPIPDATA and GLOBALIPNODES. 

 

We start by editing the file“/etc/hosts”.

 

 

Add the IP that we have put in the TCPIP PROFILE and the name that we configure in the TCPDATA member. In addition, we modify the name in the internal IP (10.1.1.2).

 

In the file "/etc/resolv.conf" we are going to configure the DNS. In my case, I will use Google's DNS servers.

Modify the parameter NSINTERADDR with the Google DNS to resolve names (in case we need it).

 

 

Finally, stop and start TCPIP. We must also refresh the RESOLVER configuration.

Stopping and starting TCPIP

Refresh RESOLVER settings.

 

Check that everything works.

Ping to router.

 

Ping to the system name. To check that it returns the correct IP.

 

Ping to external address. To check that it resolves domains.

 

Finally, we can connect a terminal to the system IP z/OS (port 23) to confirm that it connects.

 

We already have the TCPIP connection configured and running on z/OS. I hope you found it easy.