The CiscoWorks Blue mainframe application acts solely as a server to provide Systems Network Architecture (SNA) resource information to the CiscoWorks Blue Maps and SNA View applications on workstations. There are no end-user functions provided. For information about how the SNA information is used at the workstation, see the CiscoWorks Blue Maps and SNA View Workstation Installation and Administration Guide or the CiscoWorks Blue Maps and SNA View User Guide.
The mainframe component provides the SNA PU and LU information to the workstation program. It runs as a started task under OS/390 (MVS/Enterprise Systems Architecture).
The workstation component obtains the PU and LU information from the mainframe and stores it in a database at the workstation.
Note PUs connected using the remote source route bridging (RSRB) protocol and a CIP or 3172 connection to the mainframe will not benefit from the correlation feature. This means that the Maps and SNA View applications will not be able to determine which routers these PUs are dependent on for connectivity to the mainframe.
The workstation program provides the user with PU and LU information. To provide these services to the workstation user, the mainframe application uses the interfaces described in the following sections.
When you install the mainframe application, you get a fully functional Virtual Telecommunications Access Method (VTAM) exchange identification (XID) configuration services exit routine. For more information, read the section "Updating MVS and VTAM" in the "Updating the Mainframe Application Software" chapter.
The mainframe application provides a set of mainframe commands with which you configure and monitor the mainframe environment. You can start, stop, and display status for the mainframe subtasks. For more information, read the section "Issuing Mainframe Commands" in the "Using the Mainframe Application" chapter.
The mainframe application includes a series of subtasks that run on the mainframe. These subtasks provide connections to the workstations and PU/LU discovery and monitoring. For more information, read the section "Mainframe Subtasks" in the "Using the Mainframe Application" chapter.
The following major changes have been made in CiscoWorks Blue Maps and SNA View release 2.1:
In addition to the CISCO MIBs, Maps and SNA View support the following standard APPN, DLSw, and DLUR MIBs:
IETF draft standard DLSw MIB (RFC 2024)
IETF draft standard APPN MIB (RFC 2455)
IETF draft standard DLUR MIB (RFC 2232)
Maps and SNA View support the SNA Switching Services feature of the Cisco IOS software. This addition includes a new Degraded TG status and a new branch extender network node type (BrNN), as well as a new APPN stack in the Cisco IOS software and a new APPN MIB. As part of this change, the APPN Motif application no longer prompts you to designate a network topology agent.
A new set of APPN and DLSw MIB variables are used during polling and discovery.
SNA View provides dependency views for PU 4-PU 4 sessions running over DLSw. You can select PU4/Node on the Basic Search or Advanced Search page to view PU 4-PU 4 dependency views. PU 4-PU 4 support includes new Basic Search and Advanced Search options, a new PU 4 Session Connectivity display, and the new INCLUDE_PU4 mainframe parameter card that lets you specify PU 4 connections to be monitored. For the mainframe application to be able to discover PU 4-PU 4 connections, the VTAM DD statement must be specified in the NSPOPEN procedure.
The Process Manager and Message Logger are upgraded with the following changes:
Exit buttons let you quit each window.
The title bar displays the host name.
Status colors are simplified.
You can use the Session Field Suppression variables in the cwbinit file to configure fields to be suppressed from the SNA View web Sessions tables and Dependency views.
You can enable DNS lookup to be used when Maps or SNA View add a device to the data base or query the database. You can select DNS lookup in the following ways:
Select DNS lookup during installation.
Select DNS lookup with the doDNSSearch variable in the cwbinit file.
Router discovery is improved both for performance and usability. Each router is queried once for its base MIB variables and then for each applicable set of protocol-specific MIB variables.
There are many mainframe improvements in release 2.1:
Solaris workstations can now connect to the mainframe using LU 6.2.
LU 6.2 connection reliability is improved for all workstation platforms.
If you are running Tivoli NetView for OS/390 version 1.1 or later, SNA View and Maps will use the NetView automation facilities rather than the PPI task. This change improves performance of status updates.
All mainframe dataset member names are changed from the format NSP200*.* and NSPS200*.* to NSP210*.* and NSPS210*.*.
There are new mainframe messages: NSP030, NSP049, NSP050, and NSP051.
You can use the mainframe TRACE command inside the NSPPARM member.
You can link the ISTEXCCS exit routine in 24-bit or 31-bit mode.
Maps and SNA View no longer ship member NSPSCMD, so you do not copy the NSPSCMD member to a NetView CLIST data set.
The following workstation commands are improved:
The cwb show status command displays the process ID for each CiscoWorks Blue process.
The cwb clear db command clears the data base and the appnfile file.
After installation, you can use the cwbupgrade.sh command to apply the Maps and SNA View license keys.
The cwb tac command lets you specify the name of a directory in which to save the command output.
During installation, the CiscoWorks Blue products save the host name of the workstation in a set of files for use during processing. If you later change the host name of the workstation, you must also change the host name in those files.
The configuration part of the installation procedure, and the cwb config command, let you select the ports to be used for the CiscoWorks Blue web server, the Open Server Gateway, and the Name server.
A change to the Cisco IOS software deletes inactive dynamic TGs from the router database. If you want to keep those inactive TGs in the Maps and SNA View cache, set the keep_deleted_tgs option in the cwbinit file to on.
This section lists the major changes for CiscoWorks Blue Maps and SNA View release 2.0.
The features of the Maps 1.2 and SNA View release 1. 2 applications are combined into one application called CiscoWorks Blue Maps release 2.0. The SNA host functions are incorporated into the Maps application and the old SNA View task manager is gone.
The CiscoWorks Blue Maps release 2.0 applications include the original DLSw, APPN, and RSRB Motif and web-based applications and the following new applications:
The Administration application lets you discover the network, add, delete, and modify devices in the database, and select DLSw key devices using a Motif interface independent of the protocol maps.
The Process Manager application starts and stops all Maps and SNA View processes.
The Message Log Viewer displays messages generated by the Maps and SNA View processes.
A new, separately licensed program, CiscoWorks Blue SNA View release 2.0 provides a web-based method for displaying session lists and session paths for all SNA PUs and LUs, including traditional subarea SNA, DLSw, RSRB, APPN, APPN/DLUR with DLSw, and TN3270. The CiscoWorks Blue SNA View release 2.0 application uses the same discovery and polling processes and SNA host connection to keep the common database current, whether you are running Maps, SNA View, or both.
A new cwb command interface lets you start and stop processes, servers, and user interfaces.
You can now install and use CiscoWorks Blue Maps and SNA View without CiscoWorks, CiscoWorks 2000, or a Network Management System.
The CiscoWorks Blue release 2.0 applications now use the SQL Anywhere database.
CiscoWorks Blue SNA View will integrate with the Device Center component of CiscoWorks 2000, if installed on the system.
CiscoWorks Blue SNA View will integrate with the UNIX-based version of CiscoView, if installed on the system.
Some Maps release 1.2 interfaces are no longer applicable in release 2.0. Table 1-1 shows you how the interfaces from release 1.2 are used in release 2.0:
The Maps and SNA View applications no longer provide their own operator interface to the mainframe. The message and command clients no longer exist. Instead, you can use the NetView operator console or the NetView for OS/390 or SOLVE:NetMaster web pages.
A new command, cwb tac, collects and compresses the files and database information when you need to call Cisco TAC for service.
A new command, cwb verify, checks that you have completely installed the product, completed the configuration files, and started the appropriate servers and processes before your users start their applications.
The APPN Poller process has been removed. APPN polling is now done by the cwbsnamapsd daemon and the AppnPollerServer.
The cwbsyncd, cwbdlswdiscoverd, and cwbrsrbdiscoverd daemons are removed. To implement automatic discovery, use the cwb start command to start the discover processes as a UNIX cron job in the cron table (crontab).
