|
|
This chapter is intended to provide the minimum configuration changes that you will need to make to get the basic functionality of Cisco IOS for S/390 up and running. At the completion of this chapter, you should be able to ping your MVS host and test Telnet and FTP.
For complete information on setting up and installing Cisco IOS for S/390, read the Cisco IOS for S/390 Planning Guide.
This chapter contains the following sections.
This chapter assumes that you are already familiar with and have completed:
To start Cisco IOS for S/390, you will first need to set your software key in the IJTCFGxx member.
You must set your customer number and component authorization key correctly or Cisco IOS for S/390 will not operate. If you have not received these numbers, contact Customer Support.
Set the key in the AUTH statement in IJTCFGxx:
AUTH CUSTNUM (cust_num)| CUSTNUM (cust_num) | Specifies your Cisco IOS for S/390 customer number for component authorization use. |
| KEY (auth_key) | Specifies the component authorization key. This key must be obtained from Customer Support. The key is case-insensitive and may be entered with spaces to improve readability. |
The statements required to define Cisco IOS for S/390 on your network are in the TCPCFGxx member of the PARM data set. Read Network Configuration for detailed information.
The MEDIA statement defines the first physical medium to which Cisco IOS for S/390 is physically attached. Most of the parameters in the MEDIA statement can be left at the default for startup, but you will need to set MEDIA NAME.
Here is an example:
MEDIA NAME(ETHER)
The full MEDIA statement is described in Defining Physical Medium in the chapter called Network Configuration.
The NETWORK statement describes the interface between the network and the MVS host running Cisco IOS for S/390. At a minimum, you will need to specify your MVS host IP address in the IPADDRESS parameter. If your site supports subnets, you will need to specify that as well. Both must be specified in dot notation.
NETWORK IPADDRESS(a.b.c.d) SUBNET(a.b.c.d)
For more information on the NETWORK statement, read NETWORK Statement in the chapter called Network Configuration.
The driver statements follow the NETWORK statements and allow you to specify the hardware driver that you will be using.
Drivers statements include CETI, CLAW, CDLC, HYPER and LINK.
This table summarizes the parameters that will have to be changed for each driver statement.
| Driver | Parameter |
|---|---|
| CETI | CUTYPE
DEVADDR |
| CLAW | DEVADDR
WSNAME HOSTNAME |
| CDLC | DEVADDR |
| HYPER | DEVADDR |
| LINK | LCSNAME
LCS DEVADDR |
For more information on these parameters, read Driver Statements in the chapter titled Network Configuration.
You will need to set your routing with the ROUTE statement. Here is an example:
ROUTE DEST(DEFAULT) ROUTER (a.b.c.d) MASK(a.b.c.d)
For more information on these parameters, read ROUTE Statement in the chapter titled Internet Route Configuration.
You will need to make a change to the APPCFGxx. Edit the GLOBAL statement to specify ACBNAME, JES type (if not JES2). The default configuration sets DNR in local mode. If you do not want name resolution to be local, you'll need to change the default. Here is an example:
GLOBAL ACBNAME(acbname) JES(3 JES3 JES3 *) DNR(* 30)
For more information on these parameters, read GLOBAL Parameters (APPCFGxx) in the chapter titled Global Application Parameters and the Domain Name Resolver (DNR) Configuration chapter.
The Domain Name Resolver provides information about network objects by answering queries. If you want to reach other hosts on your network, you will need to configure DNR for your host. For detailed information about DNR, read Domain Name Resolver (DNR) Configuration.
At a minimum, you will need to edit two DNR members.
You will need to set the subsystem name in the DNRALCxx member. Here is an example:
ACSS YOUR.NET.COM OUR TCP/IP SUBSYSTEM NAME
You will need to set your root name servers in DNRNSCxx. Here is an example:
OUR.COM.SERVER A.OUR.COM 192.16.43.4<== Set server for your domain
You will not need to make any changes to the JCL to run Cisco IOS for S/390.
You will not need to make any changes to the STARTxx command member.
Start Cisco IOS for S/390 using the STARTxx member.
Once Cisco IOS for S/390 is started on your host, verify that the host can be reached from the network.
The ping command can be used to determine if your host is reachable from another host on your network.
From a host on the network, execute the ping command, first giving the IP address (in dotted decimal notation. If you receive a reply (host is alive), then ping your host with the host name.
At this point, if you have successfully completed the verification procedures, the basic TCP/IP services have been configured and are running in a basic mode. Now you are ready to add Telnet and FTP services.
This section describes the minimum configuration changes you will need to make to use the Telnet and FTP applications.
To tailor the applications to your specific site requirements, read chapters Telnet and TN3270 Configuration and Configuring FTP.
To test Server Telnet, use a tn3270 emulator and connect to the Cisco IOS for S/390 host. You should get a response of "Enter Command or Help".
To test User Telnet, use the TSO interface described in the Cisco IOS for S/390 User's Guide.
To test FTP, enter the command ftp hostname from a host on the network where hostname is the Cisco IOS for S/390 hostname. The host should reply with:
Connected to hostname.yourcompany.com. 220 HOSTNAME.YOURCOMPANY.COM -- FTP Server, Enter command or HELP Name (hostname:yourid):
|
|