|
|
The tasks for installing NSPECHO are discussed in the following sections:
The uploaded data sets require no more than two cylinders of space.
 | Caution Using File Transfer Protocol (FTP) to upload the NSPECHO compressed files to an MVS host is not recommended because of possible complications with the file format. |
Perform the following steps to upload the NSPECHO files to an MVS host from OS/2 using Communications Manager/2:
Step 1 Start a 3270 emulation session and log in to TSO.
Step 2 Do one of the following:
Step 3 Insert the NSPECHO disk into your disk drive.
Step 4 At the OS/2 command prompt, enter the letter representing the drive in which the NSPECHO disk is located and press Enter.
Step 5 At the OS/2 command prompt, use the nspuload command, as shown below, to upload the files.
nspuload local_disk host_session prefix
Where:
local_disk is the drive in which the NSPECHO disk is located.
host_session is the host emulator session ID.
prefix is the file prefix, if your system requires a prefix. (The NSPECHO default prefix is your TSO ID.) If the TSO profile command prefix option is on, do not specify a value for this argument.
Step 6 When the upload process is complete, verify that the NSPECHO files were uploaded to the MVS host. Return to your TSO session. In the Select Option field of the ISPF main menu, type 3.4 and press Enter. The Data Set List Utility menu is displayed.
Step 7 In the DSNAME LEVEL field, type userid.nspecho* (where userid is your TSO ID or system prefix) and press Enter. The following NSPECHO data sets should be listed on the DSLIST panel:
If you are not installing from OS/2 using Communications Manager/2, use the upload utility available with your TN3270 emulation package and ensure that the NSPECHO files are uploaded with a FB, binary, and LRECL=80 file format. This is the required format in which the NSPECHO files must be uploaded to convert them to partition data sets during the NSPECHO installation.
Perform the following steps to convert the NSPECHO data sets to partitioned data sets:
Step 1 On the DSLIST panel, position the cursor in the Command column to the left of the first data set (NSPECHOL.SEQ).
Step 2 Type receive inds (/) and press Enter.
Step 3 When prompted, press Enter. The partitioned data set should be created.
If the receive command is terminated, type an S in the Command column to the left of the data set to display details about the data set. From the data set details, verify that the data set was uploaded to the MVS with an F or FB record format and a record size of 80.
If these values are correct, type a B in the Command column to the left of the data set to browse the NSPECHO data set. The data should be skewed but readable. If you cannot read the data, then an ASCII or CRLF format may have been used to upload the data set.
If one of these formats was used, repeat the upload procedure as described in the "Uploading the NSPECHO Files from IBM OS/2 Systems" section and ensure that the proper format is used.
Step 4 Press Tab to move to the next file (NSPECHOL.SEQ), type receive inds (/), and press Enter.
Step 5 When prompted, press Enter.
Step 6 When you have completed converting the NSPECHO data sets to partitioned data sets, press F3 to return to the Data Set List Utility and then press Enter. The DSLIST panel is displayed with a refreshed list of data sets.
In addition to the original two data sets, the list should now include the following data sets:
Step 1 Copy NSPECHO from the prefix.NSPV1R2.NSPRLOAD data set to your system LOADLIB library.
Step 2 Copy NSPIPM from the prefix.NSPV1R2.NSPRSAMP data set to your system PROCLIB library and change the DSN on the STEPLIB DD statement to your system LOADLIB library name. See "Adding the IPM Startup Procedure to PROCLIB" section.
Step 3 Copy the NSPAPPL member from the prefix.NSPV1R2.NSPRSAMP data set to your system VTAMLST libraries. See "Defining the NSPECHO Host Application" section.
Step 4 Copy NSPSWNET member from the prefix.NSPV1R2.NSPRSAMP data set to your VTAMLST libraries. See "Defining Router PUs and LUs" section.
Before you can use NSPECHO to measure SNA response times, you must complete the following tasks:
A sample startup procedure (NSPIPM) has been supplied in the prefix.NSPV1R2.NSPRSAMP data set. You must customize this procedure for your environment and place it in the PROCLIB data set.
The text of the sample procedure is as follows:
//NSPIPM PROC TRACE=NO,TEST=NO //* //* //* DOC: JOB TO RUN NSP VTAM ECHO PROGRAM. //* //NSPIPM EXEC PGM=NSPECHO,REGION=4M,TIME=10, // PARM=(`APPLID=NSPECHO', X // `TIMEZONE=MVS', X // `SERVERID=SERVER1', X // `TRACE=&TRACE', X // `TEST=&TEST') //STEPLIB DD DSN=prefix.NSPECHO.LOAD,DISP=SHR //SYSLST DD SYSOUT=* //SYSUDUMP DD SYSOUT=*
Add the following definition to your VTAMLST data set. A sample can be found in the NSPAPPL file, located in the prefix.NSPV1R2.NSPRSAMP data set.
NSPRAPPL VBUILD TYPE=APPL NSPECHO APPL
Before you can use IPM to measure SNA response times on your network, a link needs to be established for communication between the mainframe and the router. To establish this link, you need to configure both the mainframe and the router sides of the network. Configuring the mainframe-to-router link involves the following tasks:
A VTAM PU definition must be supplied for every router for which you want to measure MVS host-to-router performance.
For more information, see "Configuring the Mainframe-to-Router Link" section.
For further details including a sample network configuration and diagram for defining the mainframe-to-router link, see the "Configuring Service Point on the Host and Routers" appendix.
To ensure successful configuration of the mainframe-to-router link, the network engineer should coordinate setup of the router configuration with the MVS systems programmer responsible for configuring the router's VTAM connection on the mainframe.
Before you can use IPM to measure MVS host-to-router performance, the router must be connected to the VTAM host through a systems services control point-to-physical unit (SSCP-to-PU) session. This connection is established by defining a PU for each router and its associated LUs in the VTAM configuration file.
SWDRTRS VBUILD TYPE=SWNET | x | ||
SERVICE_POINT_NAME LU1_NAME LU2_NAME LU3_NAME LU4_NAME LU5_NAME LU6_NAME LU7_NAME LU8_NAME LU9_NAME LU10_NAME | PU LU LU LU LU LU LU LU LU LU LU | ADDR=01, LOCADDR=02 LOCADDR=03 LOCADDR=04 LOCADDR=05 LOCADDR=06 LOCADDR=07 LOCADDR=08 LOCADDR=09 LOCADDR=10 LOCADDR=11 | x |
Table 8-1 defines each of the VTAM arguments. For information about how these arguments correspond to the router configuration, see the "Correlating the Router and VTAM Configuration Information" section.
For detailed information about configuring and connecting Cisco routers, refer to the "Related Documentation" section in the preface "About This Guide" for other publications about Cisco routers.
To specify the name of your router, use the following command in global configuration mode:
hostname nameTo simplify correlation of the router with its VTAM definition, we recommend that you use the name that you specify for the router in the hostname command in the VTAM definition.
For more information about using this command, see the Cisco IOS Configuration Fundamentals Configuration Guide.
To configure SNA service point support on the router, you need to add Cisco IOS software sna host commands to the configuration file of your router. The specific commands that you add depend upon the type of connection that you wish to establish. For detailed information on configuring SNA service point support and the Cisco IOS software command for your interface type, refer to the Cisco IOS Bridging and IBM Networking Configuration Guide and Command Reference publications.
The following procedure shows the basic steps to define SNA service point support for Ethernet and Token Ring connections. Again, the actual commands that you use will depend upon the type of connection that you wish to establish. If you want to view some specific configuration examples, see the "Router Configuration Samples" section.
Step 1 Define a link to an SNA host in global configuration mode using the sna host command.
The following example shows the syntax of the sna host command for Token Ring, Ethernet, FDDI, RSRB, or virtual data-link control (VDLC) connections:
sna host host-name xid-snd xid rmac remote-mac rsap remote-sap lsap local-sap focalpoint
sna enable-host lsap lsap-address
Step 3 Start an outgoing connection when you are in interface configuration mode, using the command syntax:
sna start host-name
For more information about these commands and their options, see the Cisco IOS Bridging and IBM Networking Command Reference.
The following is an example of the lines that would appear in the configuration file of a router with an interface configured through a local ring to a Token Ring Interface on a network device:
! sna host CWBC02 xid-snd 05dcc002 rmac 4001.3745.1088 rsap 4 lsap 4 focalpoint ! interface TokenRing0/1 ip address 172.18.9.129 255.255.255.240 ring-speed 16 sna enable-host lsap 4 sna start CWBC02 !
The following example shows the lines that would appear in the configuration file of a router that contains a Cisco mainframe channel connection with an interface configured for RSRB:
! dspu rsrb 325 1 900 4000.7000.0001 dspu rsrb enable-host lsap 4 ! dspu host CWBC01 xid-snd 05dcc001 rmac 4000.3333.4444 rsap 4 lsap 4 focalpoint
! dspu rsrb start CWBC01 ! interface Channel4/1 no ip address no keepalive sna C010 C0 ! interface Channel4/2 ip address 172.18.9.145 255.255.255.240 no keepalive lan TokenRing 0 source-bridge 28 1 900 adapter 4 4000.3333.4444
The following example shows the lines that would appear in the configuration file of a router with RSRB and an interface configured with loopback:
! source-bridge ring-group 600 source-bridge remote-peer 600 tcp 172.18.10.97 source-bridge remote-peer 600 tcp 172.18.10.98 ! sna rsrb 1011 3 600 4000.ffff.00cb sna rsrb enable-host lsap 4 ! sna host CWBC0B xid-snd 05dcc00b rmac 4001.3745.1089 rsap 4 lsap 4 focalpoint sna rsrb start CWBC0B ! interface Loopback0 ip address 172.18.10.97 255.255.255.252 !
The following is an example of the lines that would appear in the configuration file of a router that uses virtual data-link control over DLSw+:
source-bridge ring-group 99 dlsw local-peer peer-id 150.10.16.2 dlsw remote-peer 0 tcp 150.10.16.1 ! sna vdlc 99 4000.4500.01f0 sna vdlc enable-host lsap 12 ! sna host HOST-B xid-snd 065bbbb0 rmac 4000.7000.01f1 rsap 4 lsap 12 focalpoint ! sna vdlc start HOST-B ! interface serial 3 description IP connection to dspu7k ip address 150.10.16.2 255.255.255.0 clockrate 4000000 !
The following example shows the format of a Cisco IOS software sna host command that you use to configure the router for SNA Service Point support:
sna host host_name xid-snd xid rmac remote_mac [rsap rsap_addr] [lsap local_sap] [focalpoint]The values for the host_name and xid in the router configuration correspond to the VTAM PU definition in the following way:
SWDRTRS VBUILD TYPE=SWNET | x | ||
GLENDUSK | PU | ADDR=01, | x |
The sna host command in the router configuration for the router should appear:
sna host glendusk xid-snd 05dbb000 rmac 4001.3745.1088 rsap= 4 lsap 4 focalpointFor more information about the sna host command, see the Cisco IOS Bridging and IBM Networking Command Reference.
Step 1 From a NetView command prompt, issue the following command for each router, where router_name is the hostname and service point name of the router that you are verifying:
DIS router_name
If properly configured and connected, the router status will display with an active (ACTIV) status. If the router does not display an active status, it is not successfully configured and attached to the network or the service point is not defined correctly in the configuration file of the router.
Step 2 Repeat Step 1 for each router from which you plan to measure host response times.
Step 1 From the MVS console, issue the following command for each router name, where router_name is the hostname and service point name of the router that you are verifying:
d net,ID=router_name,E
Step 2 Repeat Step 1 for each router from which you plan to measure host response times.
Posted: Fri Mar 12 10:58:30 PST 1999
Copyright 1989-1999©Cisco Systems Inc.