|
|
This chapter contains instructions for updating VTAM and MVS on the mainframe, as well as updating the SNA View input parameter cards to customize SNA View for your site's particular needs. You will use different sections of this chapter depending on whether your connection to the workstation uses LU 6.2 or TCP/IP.
This chapter contains the following major sections:
Use the installation checklist provided in the appendix "Mainframe/Workstation Installation Checklist" to coordinate the configuration of the SNA View mainframe and workstation components.
You must configure the mainframe to communicate with the CiscoWorks Blue SNA View workstation using either LU 6.2 or TCP/IP. See the section that pertains to your protocol.
This section describes how to modify VTAM data sets on a mainframe that is connected to the SNA View workstation using LU 6.2. (If your workstation uses a TCP/IP connection, see the section "Configuring TCP/IP Connectivity.")
Before you start the steps that will allow SNA View on the workstation to communicate with SNA View on the mainframe, you must first do all the necessary configuration to allow an LU 6.2 session to flow from the workstation to the mainframe. You may need to change both VTAM and the workstation application that supports LU 6.2 sessions (for example, SNAplus2 or Communication Server for AIX). If the SNA View workstation will not be directly connected to the mainframe running SNA View, but the session will instead pass through one or more VTAMs before reaching the destination VTAM, then the correct configuration may require changes to all VTAMs (and possibly the NCPs) in the path. It is not the intent of this book to document all the steps necessary to set up the network. See the relevant VTAM and NCP publications instead.
If this LU 6.2 setup has not yet been done, the SNA View installation should be delayed until the LU 6.2 configuration is complete. One way to determine whether there is LU 6.2 connectivity between the SNA View workstation and the mainframe is to issue the VTAM command D net,aping,id=netid.resource, where the netid.resource is the fully qualified name of the SNA workstation. Until the aping command returns a positive response, SNA View will not be able to connect to the workstation.
After the initial LU 6.2 configuration is complete, you can use the procedures in the following section to complete the configuration for SNA View.
To configure LU 6.2 connectivity, perform the following steps:
Step 1 Ensure that your MODETAB table entry contains the MODENT entries (SNASVCMG and PARALLEL) shown in this example.
SNA View LU 6.2 uses the following LOGMODE entries:
SNASVCMG MODEENT LOGMODE=SNASVCMG,FMPROF=X'13',TSPROF=X'07', X
PRIPROT=X'B0',SECPROT=X'B0',COMPROT=X'D0B1', X
RUSIZES=X'8585',PSERVIC=X'060200000000000000000300', X
ENCR=B'0000'
*
PARALLEL MODEENT LOGMODE=PARALLEL,FMPROF=X'13',TSPROF=X'07', X
PRIPROT=X'B0',SECPROT=X'B0',COMPROT=X'50B1',TYPE=X'00', X
RUSIZES=X'8787',PSERVIC=X'060200000000000000002F00'
*
If your MODETAB table lacks these entries, use a text editor to add them before you reassemble and link-edit the MODETAB table. The text for these table entries is available in prefix.NSPS120I.NSPSSAMP(MODEENT). A sample of assembly and link-edit JCL is available in prefix.NSPS120I.NSPSSAMP(MODEJCL).
The changes to the MODETAB table take effect when VTAM is restarted. You can load the changes immediately with the following system console command:
Step 2 Create a PU definition for the SNA View workstation that meets the following requirements:
Additionally, if the PU is defined under an NCP major node, the NCP definition must contain the LUDRPOOL statement for the configuration of at least three independent LUs.
A sample PU definition (defined under a switched major node) is available in prefix.NSPS120I.NSPSSAMP(SWMNILU).
Step 3 Define an independent LU under a cross-domain resource (CDRSC) major node, associating the LU with an existing PU. A sample CDRSC definition is available in prefix.NSPS120I.NSPSSAMP(NSPCDRSC). Alternatively, you may define an independent LU under an existing PU definition by coding LOCADDR=0.
You can modify the resource names in the sample major node members to your site's naming conventions for network resources, but any changes to these default names must also be made to the parameter cards (see the section "Updating the SNA View Configuration File (NSPPARM)").
This section tells you how to modify your mainframe TCP/IP installation for use with SNA View. TCP/IP connectivity can be made through Cisco IOS for S/390, IBM TCP/IP, or Interlink TCP/IP. Each method is discussed below.
The following steps are for systems that use IBM TCP/IP for MVS.
Step 1 Reserve port numbers in the PROFILE.TCPIP file.
This step is optional. If you do not reserve specific port numbers for SNA View, the workstation connection will still be successful. This reservation simply flags the chosen port numbers for exclusive use by SNA View so that other products on the mainframe will not use them.
For each SNA View workstation, choose two available port numbers and add the following two lines to the list of PORT values in your PROFILE.TCPIP file. The default port values are 6106 and 6107, as shown in the following sample TCP lines. If you use other port numbers, change the TCP lines in the PROFILE.TCPIP file.
Step 2 Identify the TCP/IP high-level qualifier.
If your TCP/IP installation did not use the default high-level qualifier for its data sets, copy the hlq.TCPIP.DATA data set and name it TCPIP.TCPIP.DATA to ensure that SNA View can read your system's TCP/IP configuration.
Step 3 If the TCP/IP address space is not named TCPIP, edit the TCPIP.TCPIP.DATA data set (see Step 2) and verify that the TCPIPJOBNAME or TCPIPUSERID parameter is correctly set to the name of the TCP/IP address space.
Step 4 If the parameter in your TCPIP.TCPIP.DATA data set is TCPIPJOBNAME, change it to TCPIPUSERID. (Older versions of the TCP/IP connection software do not recognize TCPIPJOBNAME.)
Step 5 Ensure that the TCPIP prefix is set correctly in the NSPOPEN procedure (located in prefix.NSPS120I.NSPSSAMP). Change the characters TCPHLL in PARM='=TCPIP_PREFIX=TCPHLL', to your installation-defined high level qualifier for TCP/IP. For example, if the profile DD statement in the TCP/IP PROC is TCPMVS2.TCPIP1.PROFILE.TCPIP, then the high-level qualifier is TCPMVS2.TCPIP1, and the PARM would be specified as follows:
If you configure TCP/IP connectivity to multiple mainframe domains from UNIX workstations, each set of SVMF_HCI_AGENT_PORT and SVMF_CMDS_AGENT_PORT parameters for each domain must have corresponding TCP parameter cards in the mainframe. (TCP parameter cards are described in the section "Updating the SNA View Configuration File (NSPPARM).") For example, you would set the workstation parameters for a domain named NORTH as follows in the file
/etc/svopen_config_NORTH:
SVMF_HCI_AGENT_PORT 6106
SVMF_CMDS_AGENT_PORT 6107
You would set the workstation parameters for a domain named SOUTH as follows in
/etc/svopen_config_SOUTH:
SVMF_HCI_AGENT_PORT 6126
SVMF_CMDS_AGENT_PORT 6127
The host configuration files for the NORTH and SOUTH domains must each have a TCP card that specifies the correct port configurations.
For domain NORTH:
TCP 6106 6107
For domain SOUTH:
TCP 6126 6127
The data that is transferred between the SNA View mainframe and workstation components is not encrypted, but it will probably be secure if the data is transferred over a private intranet. If the workstation-to-host connection traverses the Internet, or if additional security is desired over an intranet, you can use the Network Data Encryption with Router Authentication feature provided with Cisco routers to encrypt the data that flows between the router nearest to the workstation and the router nearest to the host.
More information about encrypted connections can be found in the Cisco IOS Release 11.2 Security Configuration Guide.
If your system uses Interlink TCP/IP Access, you must use the copy of LSCNCOM that is provided by Interlink in place of the LSCNCOM that is provided by SNA View in prefix.NSPS120I.NSPSLOAD. Either replace the module in prefix.NSPOPEN.NSPSLOAD or add the Interlink TCP/IP load library to the STEPLIB DD (data definition) card of the SNA View startup job ahead of prefix.NSPS120I.NSPSLOAD.
This section describes changes that you must make in your system's MVS and VTAM data sets. These changes are necessary regardless of the method used to connect the workstation to the mainframe. Notify your system programmer of the changes to be made to the members in the SYS1.PARMLIB data set.
Step 1 Authorize SNA View LOADLIB (prefix.NSPS120I.NSPSLOAD) by adding the data set prefix.NSPS120I.NSPSLOAD and its DASD (direct access storage device) volume name to your list of authorized program facility (APF) authorized data sets in SYS1.PARMLIB(IEAAPFxx) or SYS1.PARMLIB(PROGxx). Doing this lets SNA View process some authorized commands and perform security checks.
Reload (re-IPL) MVS if necessary. If your system is set up to use dynamic APF services, you can avoid reloading MVS by using the SETPROG command to dynamically update the APF list. See the Initialization and Tuning Reference manual for your MVS/ESA system for more information about authorizing data sets.
Step 2 Set the performance group by adding a TRXNAME parameter for SNA View to the started task control (STC) subsystem definition of SYS1.PARMLIB(IEAICSxx). In the TRXNAME line, specify the same performance group used by NetView or other high-priority application programs to ensure that SNA View receives enough CPU time to avoid a backlog of network information processing. The default application name for SNA View startup job is NSPOPEN.
If NetView is running in performance group 8, and you want SNA View to also run in performance group 8, specify the following TRXNAME parameter:
After you add a new entry, you can use the following MVS command to dynamically reload the installation control specification (ICS) file:
Where xx is the two-digit suffix of the member that was edited.
Step 3 Add an SNA View entry to the program properties table in SYS1.PARMLIB(SCHEDxx):
After you add the new entry, you can immediately reload the program properties table with the following MVS command:
xx
Where xx is the two-digit suffix of the member that was edited.
Step 4 Add the VTAM parameter PPOLOG=YES to your VTAM startup options in the SYS1.VTAMLST(ATCSTRxx) file to ensure that messages issued by VTAM in response to console commands are sent to the primary program operator.
If the PPOLOG parameter has not been set in the currently running VTAM, you can add it dynamically with the following command:
Step 5 Copy and modify the prefix.NSPS120I.NSPSSAMP(NSPAPPL) data set.
Step 6 Activate the major node and verify that the APPL definitions are active.
You can modify the APPL resource names in the definition to suit your site's naming conventions for network resources, but any changes to these default names must also be made to the parameter cards described in the "Updating the SNA View Configuration File (NSPPARM)" section.
Step 7 Install the VTAM exit routine, and allocate the VSAM database, as described below in the section "Using the ISTEXCCS XID Exit Routine."
CiscoWorks Blue SNA View provides a functional VTAM XID Configuration Services exit routine called NSPEXCCS. The NSPEXCCS routine calls a service routine, provided by CiscoWorks Blue Maps, that logs MAC, SAP, and RIF data to a VSAM file each time a switched PU connects into the network.
If you are not currently using your own ISTEXCCS exit routine, install the CiscoWorks Blue Maps version, as described in the section "Installing the VTAM XID Exit Routine."
If you have your own ISTEXCCS exit routine, please call the Cisco TAC for instructions on modifying it.
CiscoWorks Blue SNA View provides a functional VTAM XID Configuration Services exit routine called NSPEXCCS. This section describes how to install NSPEXCCS.
Step 1 Using the sample member provided in the
prefix.NSPS120I.NSPSSAMP( ASMIST) data set, assemble and link-edit the exit routine in prefix.NSPS120I.NSPSSAMP(NSPEXCCS) into an appropriate VTAM library as described in the manualVTAM Customization.
Step 2 Use the sample member provided in
prefix.NSPS120I.NSPSSAMP( NSPDBVSM) to allocate two VSAM databases used by the NSPEXCCS exit routine. Use the following formula to calculate the size of the PRIMARY and BACKUP databases in NSPDBVSM:
(a) Estimate the total number of switched PUs that will be discovered by SNA View (those PUs that will not be filtered out by the EXCLUDE_SW_MAJNODES, INCLUDE_SW_MAJNODES, and PULU_FILTER parameter cards). _____________
(b) Multiply the number in (a) by 230. _____________
(c) Add a contingency factor (20% is suggested). _____________
(d) The result is the minimum number of bytes to
allocate for each VSAM database in
NSPDBVSM (PRIMARY and BACKUP). _____________
Step 3 Prime the VSAM databases using the sample JCL in the prefix.NSPS120I.NSPSSAMP (PRIMEJCL) data set.
Step 4 Add two DD statements to the VTAM startup procedure to include the data sets allocated in Step 2. The DDNAMEs must be XIDDATA and XIDBACK. Here are sample DD statements:
NSP.XIDDATA1,DISP=SHARE
NSP.XIDBACK1,DISP=SHARE
Step 5 Replace NSP.XIDDATA1 and NSP.XIDBACK1 with the actual names of the VSAM data sets.
Step 6 Restart VTAM with the VSAM data sets allocated and primed.
This section describes the purpose and content of the SNA View configuration file (NSPPARM). A sample configuration file is provided in prefix.NSPS120I.NSPSSAMP. The SNA View configuration file contains a sequence of parameter cards that control the way the SNA View mainframe program runs. The SNA View configuration file contains three sections; each section contains a sequence of parameter cards. Code all parameter cards in uppercase characters.
Section 1 of the configuration file contains required control parameter cards that specify which PUs and LUs should be discovered and monitored from the mainframe. Section 2 contains a set of required parameter cards that govern the operation of SNA View mainframe subtasks to discover and monitor PUs and LUs. Section 3 contains a set of optional parameter cards that let SNA View workstation users issue MVS and VTAM commands.
The SNA View configuration file is described in the following subsections:
Section 1 of the SNA View configuration file contains a set of control parameter cards that specify the PU and LU names that the SNA View mainframe program should send to the SNA View workstation during discovery and status monitoring. Table 4-1 lists the parameter cards for Section 1.
| Parameter Card | Valid Values | Purpose |
|---|---|---|
| EXCLUDE_SW_MAJNODES | SNA switched major node names | Specifies a list of SNA switched major nodes whose PUs and LUs will not be discovered or monitored |
| FILTER | Mainframe message IDs | Specifies mainframe messages to be passed to the SNA View workstation |
| INCLUDE_SW_MAJNODES | SNA switched major node names | Specifies a list of SNA switched major nodes whose PUs and LUs will be discovered and monitored |
| LU_CONTROL | OPTION | Specifies how LU names should be selected for discovery and monitoring |
| MESSAGES | OPTION | Specifies whether VTAM and MVS messages are sent to the SNA View workstation for viewing |
| ONLY_SWITCHED_PUS | YES or NO | Specifies whether SNA View will discover and monitor all PUs and LUs, or just those associated with SNA switched major nodes |
| PULU_FILTER | [-] PULU_NAME | Specifies, by name, which PUs and LUs SNA View will (or will not) discover and monitor |
Use the EXCLUDE_SW_MAJNODES parameter card to specify a list of SNA switched major nodes whose PUs and LUs will be excluded from discovery and monitoring.
If you also use the ONLY_SWITCHED_PUS parameter card with the YES option, then SNA View discovers and monitors only the switched PUs and LUs that are not associated with the switched major nodes specified on this EXCLUDE_SW_MAJNODES parameter card.
If you also use the PULU_FILTER parameter card, then the filters specified in the PULU_FILTER parameter card are applied after the PUs and LUs are filtered by the EXCLUDE_SW_MAJNODES parameter card.
Default: If you do not include an EXCLUDE_SW_MAJNODES parameter card, all PUs and LUs are discovered, for all SNA switched major nodes, that are not otherwise filtered out by another parameter card.
Occurrences: You can include more than one EXCLUDE_SW_MAJNODES parameter card.
Card Syntax: EXCLUDE_SW_MAJNODES NODE1 ... NODEn
Syntax Description:
| NODE1 ... NODEn | Specify the names of one or more SNA switched major nodes, separated by spaces, whose PUs and LUs will be excluded from discovery. You must use the complete node name; wildcard characters are not allowed. |
Example
To have SNA View exclude all PUs and LUs associated with the SNA switched major nodes SWDOM1 and SWDOM2, code this parameter card:
EXCLUDE_SW_MAJNODES SWDOM1 SWDOM2
Use the FILTER parameter card to specify the message IDs of MVS and VTAM messages that are to be passed to the SNA View workstation. If you use FILTER cards, only those messages named on the FILTER cards are forwarded to the SNA View workstations. All other messages are blocked.
If you do not include the FILTER parameter card, then all messages are sent to the workstation unless they are filtered out by the FILTER ADD and FILTER DEL commands. You can use the FILTER ADD and FILTER DEL commands to further control message filtering. These command are described in the "Issuing SNA View Commands" section of the "Using the SNA View Mainframe Application" chapter.
Default: If you do not supply a FILTER parameter card, all messages are passed to the SNA View workstation.
Occurrences: You can include several FILTER parameter cards.
Card Syntax: FILTER MESSAGEID1 ... MESSAGEIDn
Syntax Description:
| MESSAGEID1 MESSAGEIDn | Specifies from 1 to n VTAM and/or MVS message IDs, separated by spaces, that identify mainframe messages to be passed to the SNA View workstation. Wildcard characters are not allowed. |
Example
To pass all occurrences of VTAM messages IST555I and IST666E to the SNA View workstation, code this parameter card:
FILTER IST555I IST666E
Use the INCLUDE_SW_MAJNODES parameter card to specify one or more SNA switched major node names whose PUs and LUs will be included in the discovery and monitoring.
If you also use the ONLY_SWITCHED_PUS parameter card with the YES option, then SNA View discovers and monitors only the PUs and LUs that are associated with the switched major nodes specified on the INCLUDE_SW_MAJNODES parameter card.
If you also use the PULU_FILTER parameter card, then the filters specified in the PULU_FILTER parameter card are applied after the PUs and LUs are filtered by the INCLUDE_SW_MAJNODES parameter card.
Default: If you do not include an INCLUDE_SW_MAJNODES parameter card, all PUs and LUs are discovered, for all SNA switched major nodes, that are not otherwise filtered out by other parameter cards.
Occurrences: You can include more than one INCLUDE_SW_MAJNODES parameter card.
Card Syntax: INCLUDE_SW_MAJNODES NODE1 ... NODEn
Syntax Description:
| NODE1 ... NODEn | Specify the names of one or more SNA switched major nodes, separated by spaces, whose PUs and LUs will be included in discovery. You must use the complete node name; wildcard characters are not allowed. |
Example
To have SNA View include all PUs and LUs associated with the SWDOM1 and SWDOM2 switched major nodes, code this parameter card:
INCLUDE_SW_MAJNODES SWDOM1 SWDOM2
Use the LU_CONTROL parameter card to specify how LUs should be discovered and monitored.
Default: If you do not include an LU_CONTROL parameter card, the CONSISTENT option is the default.
Occurrences: You can include only one LU_CONTROL parameter card.
Card Syntax: LU_CONTROL OPTION
Syntax Description:
| OPTION | Specifies how LU names are selected for discovery and monitoring. The following options are available.
CONSISTENT--LUs are discovered and monitored based on a consistent naming convention of the associated PUs and LUs. When a PU name meets the requirements of a PULU_FILTER parameter card, all LUs associated with that PU are also discovered and monitored. As an example of consistent PU and LU naming conventions, if the PU name is WOMPU1, then all LU names under WOMPU1 might begin with the characters WOM1 (for example, WOM1LU1 and WOM1LU2). Note that some apparently consistent naming conventions actually are not consistent. For example, SNA View considers it an inconsistent naming convention if the PU name is IBUPC1 but the LUs are PC1LU01 and PC1LU02. UNIQUE--LUs are discovered and monitored using different naming conventions than their associated PUs. During discovery, only LU names that satisfy the PULU_FILTER parameter card are discovered. This option takes more system resources than either the CONSISTENT or IGNORE options. IGNORE--SNA View does not discover or monitor LUs. |
Examples
LU_CONTROL CONSISTENT
LU_CONTROL UNIQUE
PULU_FILTER IBU* PC1*
The user at the SNA View workstation can start MVS and VTAM message clients to display only the VTAM and MVS messages that are sent by SNA View on the mainframe. Use the MESSAGES parameter card to specify whether VTAM and/or MVS messages are sent to the SNA Workstation for display.
Default: If you do not supply a MESSAGES parameter card, the ON option is the default and both MVS and VTAM messages are sent to the workstation.
Occurrences: You can include only one MESSAGES parameter card.
Card Syntax: MESSAGES OPTION
Syntax Description:
| OPTION | Specifies whether VTAM and MVS messages are sent to the SNA View workstation for viewing. Use one of the following options:
ON--Both VTAM and MVS messages are sent to the SNA View workstation where the user can view them. OFF--Neither VTAM nor MVS messages are sent to the SNA View workstation. The workstation user cannot view them. VTAM--Only VTAM messages are sent to the SNA View workstation where the user can view them. MVS messages are not sent. MVS--Only MVS messages are sent to the SNA View workstation where the user can view them. VTAM messages are not sent. |
Example
To send only MVS messages to the workstation, code this parameter card:
MESSAGES MVS
Use the ONLY_SWITCHED_PUS parameter card to specify whether SNA View will discover all PUs and LUs, or just the PUs and LUs associated with SNA switched major nodes.
Default: YES is the default: SNA View will discover and monitor only PUs and LUs that are associated with an SNA switched major node.
Occurrences: You can include only one ONLY_SWITCHED_LUS parameter card.
Card Syntax: ONLY_SWITCHED_PUS [{YES|NO}]
Syntax Description:
| {YES|NO} | Specifies whether SNA View will discover and monitor only PUs and LUs associated with an SNA switched major node.
· YES--SNA View will discover and monitor only PUs and LUs associated with an SNA switched major node. YES is the default value. · NO--SNA View will discover and monitor all PUs and LUs. |
Example
To have SNA View discover and monitor only PUs and LUs associated with an SNA switched major node, code the following parameter card:
ONLY_SWITCHED_PUS YES
Use the PULU_FILTER parameter card to specify, by name, which PUs and LUs will be discovered and monitored, and which PUs and LUs will not be discovered or monitored. Because this card filters PUs and LUs by name, it is most useful when you name your PUs and LUs with a common naming convention. You can include a series of PULU_FILTER parameter cards.
Each PULU_FILTER parameter card contains one or more filter tokens to be applied to the PU and LU names. Each filter token is a portion of an PU or LU name, and includes asterisks (*) as wildcards at the beginning of the name, at the end of the name, or both. For example, to specify all PUs and LUs with names beginning with ABC, you would code a filter token as ABC*.
If you precede a filter token with a hyphen (-), PUs and LUs that match that filter token are not discovered.
Default: If you do not supply a PULU_FILTER parameter card, all PUs and LUs will be discovered and monitored regardless of naming conventions, unless filtered out by other parameter cards.
Occurrences: You can include several PULU_FILTER parameter cards.
Card Syntax: PULU_FILTER [-]FILTER_TOKEN1 . . . [-]FILTER_TOKENn
Syntax Description:
| [-] | Specifies that PU and LU names that satisfy the following FILTER_TOKEN values will be ignored (not discovered).
If you omit the - character, then PU and LU names that satisfy the following FILTER_TOKEN values will be discovered. |
| FILTER_TOKEN1 ... FILTER_TOKENn | Specifies one or more filter tokens, each consisting of a portion of a PU or LU name with asterisks to be used as wildcards. You can code a series of filters on the same PULU_FILTER parameter card.
Each filter token must contain at least one asterisk at the beginning or end of the token. Each filter token can contain two asterisks, one at each end. The following are valid tokens: PUNAM* *NAME *NAME* |
Examples
To discover and monitor only those PUs and LUs that begin with the characters VPU, but to ignore PUs and LUs that begin with the characters VPU5, code the following parameter card:
PULU_FILTER VPU* -VPU5*
To discover and monitor all PUs and LUs that begin with the characters ABC or end with the characters DEF, or contain the characters GHI, code the following parameter card:
PULU_FILTER ABC* *DEF *GHI*
Section 2 of the configuration file contains a set of parameter cards that govern the operation of the SNA View mainframe subtasks that discover and monitor PUs and LUs. Table 4-2 lists the parameter cards you can use in Section 2.
| Parameter Card | Valid Values | Purpose |
|---|---|---|
| DISCOVER | VTAM APPL definition and retry count | Specifies a VTAM APPL definition for SNA PU and LU discovery |
| MVS | Console name | Provides SNA View with MVS console support |
| PPI | None | Requests setup of the program-to-program interface (PPI) to NetView or SOLVE:Netmaster |
| PPO | VTAM APPL definition | Specifies a VTAM APPL definition for a primary program operator (PPO) application; allows SNA View to act as VTAM primary program operator |
| SEC | BLOCK, NO, YES, NSPRACF | Specifies the security method for workstation users when issuing mainframe commands |
| SERVER | APPL, LU, mode, message server, command server | Identifies VTAM resources for LU 6.2 workstation connection |
| STATUS | VTAM APPL definition | Specifies a VTAM APPL definition for SNA PU and LU status updates |
| TCP | Host connection interface port, host command server port | Identifies port numbers for TCP/IP workstation connection |
Use the DISCOVER parameter card to specify the name of a VTAM APPL definition to be used for the discover subtask.
Default: If you do not supply a DISCOVER parameter card, no SNA discovery can take place.
Occurrences: You can include only one DISCOVER parameter card.
Card Syntax: DISCOVER VTAM_applid
Syntax Description:
Example
If the ID of the discover subtask's APPL definition, coded with AUTH=SPO, is NSPDSC1, you would code the following DISCOVER parameter card:
DISCOVER NSPDSC1
Use the MVS parameter card to specify the name of the extended MCS console to be defined for receipt of MVS messages. You define this name so that the SNA View workstation can receive MVS messages. The MVS parameter card is required for SNA View status monitoring.
Default: If you do not supply an MVS parameter card, the SNA View workstation cannot receive MVS messages.
Occurrences: You can include only one MVS parameter card.
Card Syntax: MVS console_name
Syntax Description:
| console_name | The name of the extended MCS console to be defined for receipt of MVS messages. If this name is defined in RACF, the OPERPARM values for this name will be used for the console definition. Otherwise, a console will be defined with default parameters AUTH=INFO and ROUTCDE=ALL. |
Example
To specify NSPCONS1 as the extended MCS console, use the following MVS parameter card:
MVS NSPCONS1
Use the PPI parameter card to connect SNA View to the NetView or SOLVE:Netmaster PPI for the receipt of VTAM messages. The PPI card tells SNA View to establish a
program-to-program interface with NetView or SOLVE:Netmaster so that SNA View can receive solicited and unsolicited VTAM messages. The PPI must be active in accordance with the NetView or SOLVE:Netmaster documentation.
Default: If you do not supply a PPI or PPO parameter card, the SNA View workstation cannot receive VTAM messages, which is required for status monitoring.
Occurrences: You can include only one PPI parameter card.
Card Syntax: PPI
Syntax Description: There are no operands on the PPI card.
Example
To connect SNA View to the NetView or SOLVE:Netmaster PPI for receiving VTAM messages at the SNA View workstation, code the following PPI parameter card:
PPI
Use the PPO parameter card to specify the name of a VTAM APPL definition that will act as a primary program operator application program (PPO) to receive solicited and unsolicited VTAM messages.
Default: If you do not supply a PPO or PPI parameter card, the SNA View workstation cannot receive VTAM messages as the primary program operator, which is required for status monitoring.
Occurrences: You can include only one PPO parameter card.
Card Syntax: PPO VTAM_applid
Syntax Description:
| VTAM_applid | The ID of the APPL definition coded with AUTH=PPO. This identifies the primary program operator application program that will receive unsolicited VTAM messages. |
Example
If the ID of the APPL definition coded with AUTH=PPO is NSPPPO1, code the following PPO parameter card:
PPO NSPPPO1
Use the SEC parameter card to specify the level of security clearance needed to issue mainframe commands from the SNA View workstation. Users are normally verified using the IBM Resource Access Control Facility (RACF) or Computer Associates' CA-ACF2.
Default: If you do not supply an SEC parameter card, BLOCK is used.
Occurrences: You can include only one SEC parameter card.
Card Syntax: SEC option
Syntax Description:
| option | BLOCK--Workstation users cannot issue mainframe commands. This is the default.
NO--No security measures are used. Any workstation user can issue mainframe commands without entering a user ID and password. YES--Security is enforced. A workstation user must enter a valid user ID and password to issue mainframe commands. (This is the same as the NSPRACF option.) NSPRACF--Security is enforced. A workstation user must enter a valid user ID and password to issue mainframe commands. (This option is for compatibility with previous software releases.) |
Example
If RACF or CA-ACF2 is installed and you want to use the security feature of SNA View, then use this parameter card:
SEC YES
Use the SERVER parameter card to provide the values needed to establish an LU 6.2 connection between SNA View mainframe application and an SNA View workstation application.
Default: If you do not supply a SERVER parameter card, no LU 6.2 sessions are established. Code a TCP card to configure a TCP/IP connection instead.
Occurrences: You can include up to ten SERVER parameter cards, one for each SNA View workstation attached using LU 6.2.
Card Syntax: SERVER plu slu PARALLEL NSPOPNMS NSPOPNCS
Syntax Description:
Example
To define an LU 6.2 session between primary logical unit NSPAPL1 and secondary logical unit NSPLU01 using the logmode PARALLEL, code the SERVER parameter card:
SERVER NSPAPL1 NSPLU01 PARALLEL NSPOPNMS NSPOPNCS
Use the STATUS parameter card to specify a VTAM APPL definition that will update the status of SNA PUs and LUs.
Default: If you do not supply a STATUS parameter card, PU and LU status is not monitored.
Occurrences: You can include one STATUS parameter card.
Card Syntax: STATUS VTAM_applid delay_time
Syntax Description:
Example
If the ID of the status program's APPL definition, coded with AUTH=SPO, is NSPSTA1, code the following parameter card:
STATUS NSPSTA1
Use the TCP parameter card to configure a TCP/IP connection between the SNA View mainframe application and an SNA View workstation. You specify the TCP/IP ports on the mainframe that are used for the host connection interface and the host command server.
Default: If you do not supply a TCP parameter card, no TCP/IP connections are available. Code a SERVER card to establish an LU 6.2 session instead.
Occurrences: You can include up to 20 TCP parameter cards, 1 for each SNA View workstation attached using TCP/IP.
Card Syntax: TCP hciport cmdport
Syntax Description:
Example
To reserve ports 6106 and 6107 on the mainframe for the SNA View workstation host connection interface and host command server, code the TCP parameter card:
TCP 6106 6107
Section 3 of the configuration file contains a set of optional parameter cards that let SNA View workstation users issue MVS and VTAM commands. Table 4-3 lists the parameter cards in Section 3.
| Parameter Card | Valid Values | Purpose |
|---|---|---|
| CMD | console name | Defines an SNA View console to allow the SNA View workstation to issue MVS commands. |
| SPO | VTAM APPL definition | Defines a secondary program operator (SPO) application to allow the SNA View workstation to issue VTAM. |
Use the CMD parameter card to specify the name of the extended multiple console support (MCS) console to be defined for issuing MVS commands from a SNA View workstation.
In the default NSPPARM file, this card has a comment delimiter so that it is not read as a parameter card. If you leave this card commented out in the NSPPARM file, workstation users cannot issue MVS commands. If you need this card at a later time, you can remove the comment delimiter.
Default: If you do not supply a CMD parameter card, users cannot issue MVS commands from an SNA View workstation.
Occurrences: You can include only one CMD parameter card.
Card Syntax: CMD console_name
Syntax Description:
| console_name | The name of the extended MCS console to be defined for issuing MVS commands from SNA View. If this name is defined in RACF, the OPERPARM values for this name will be used for the console definition; otherwise, a console will be defined with default parameters AUTH=ALL and ROUTCDE=NONE. |
Example
To specify NSPCONS2 as the extended MCS console for issuing MVS commands from SNA View workstation, code the following CMD parameter card:
CMD NSPCONS2
Use the SPO parameter card to define a secondary program operator application program. You can provide multiple SPO cards, but you must provide at least one SPO card to be able to issue VTAM commands from the SNA View workstation.
In the default NSPPARM file, this card has a comment delimiter so that it is not read as a parameter card. If you leave this card commented out in the NSPPARM file, workstation users cannot issue VTAM commands. If you need this card at a later time, you can remove the comment delimiter.
Default: If you do not supply an SPO parameter card, users cannot issue VTAM commands from an SNA View workstation.
Occurrences: You can include only one SPO parameter card.
Card Syntax: SPO VTAM_applid
Syntax Description:
Example
If the ID of the APPL definition coded with AUTH=SPO is NSPSPO1, code the SPO parameter card:
SPO NSPSPO1
This section explains the steps that are required for SNA View to work with NetView. The following subsections are included in this section:
Verify that the NetView subsystem address space is active and that the NetView PPI is enabled, as defined in the NetView Installation and Administration Guide. The NetView program-to-program interface is necessary for cross-memory communications between NetView and SNA View. Before starting NetView, start the subsystem application.
Follow these steps to change the NetView DSIPARM data set for SNA View.
Step 1 Define the SNA View mainframe optional task by adding the following definition to the DSIDMN member of your NetView's DSIPARM data set:
Verify that the NetView task (CNMCSSIR) is defined with INIT=N, and that CNMCSSIR is started in command list CNME1035 during NetView initialization. This task provides command and message forwarding services for SNA View.
Step 2 Define a command model for the NSPMQS load module by adding the following definition to the DSICMD member of your NetView's DSIPARM data set:
Step 3 Define an additional NetView autotask, here named NSPAUTO1, by adding the following definition to the DSIOPF member of your NetView's DSIPARM data set:
You can change the Operator ID (NSPAUTO1) to conform to your site requirements, but it must match the NSPCMD_OPERATOR configuration parameter on the workstation.
You can change the PROFILEN name (NSPPROF) to conform to your site requirements. The profile will be defined in Step 4.
You might also need to define the Operator ID to the security product.
Step 4 Define a profile for the new NetView autotask (defined as NSPAUTO1 in Step 3) by adding a member named NSPPROF to your NetView's DSIPRF data set. NSPPROF must contain the following three lines:
You can change the member name to conform to your site requirements, but it must match the PROFILEN statement that was coded in Step 3.
Step 5 Add the following line to your initial command list to ensure that the new NetView autotask (NSPAUTO1) is started each time NetView is started:
Copy the NSPSCMD member from prefix.NSPS120I.NSPSCLST to a NetView DSICLD data set.
The SNA View sample library (prefix.NSPS120I.NSPSSAMP) contains the following programs that you add to customize NetView:
Create the load modules (DSIEX06, DSIEX11, NSPLU62, NSPMQS) by modifying and submitting the JCL in prefix.NSPS120I.NSPSSAMP(ASMJCL), according to the instructions in the member. After the load modules are created, copy them to a NetView STEPLIB data set.
Restart NetView to activate the changes that you made to NetView.
This section describes how you can enable CiscoWorks Blue SNA View to interact with SOLVE:Netmaster. You do not have to restart SOLVE:Netmaster for the changes to take effect. To enable SOLVE:Netmaster to work with SNA View, perform the steps listed in the following sections:
The data set members listed in Table 4-4 are located in prefix.NSPS120I.NSPSCLST and are used to change SOLVE:Netmaster for SNA View.
| Member | Description |
|---|---|
| NSPKDOC | Describes the PROCs and how to implement SNA View |
| NSPKPPO | Contains SNA View modifications to the SOLVE:Netmaster PPO procedure |
| NSPKPPI | Contains the SNA View PROC, which receives solicited and unsolicited VTAM messages and sends them to SNA View mainframe |
| NSPKCMD | Contains the SNA View PROC, which is the command PPI receiver (NSPNETV) and starts NSPKCM1 |
| NSPKCM1 | Contains the SNA View PROC, which is the command sender and receiver |
Verify that the SOLVE:Netmaster PPI address space is active, as defined in the SOLVE:Netmaster Implementation and Administration Guide. The PPI is necessary for cross-memory communications between SOLVE:Netmaster and SNA View.
For SNA View to receive system message information from SOLVE:Netmaster, the network control language (NCL) code in prefix.NSPS120I.NSPSCLST(NSPKPPO) must be added to the production PPO procedure (PPOPROC) at a point where all messages will be seen; the recommended point for this code addition is immediately following the mainline &PPOREAD.
For the PPO procedure to receive solicited and unsolicted VTAM messages, those messages must be sent to the PPO procedure by SOLVE:Netmaster. You can use the DEFMSG command to control which messages are sent to the PPO procedure. See the SOLVE:Netmaster documentation for more information.
Copy the following members from prefix.NSPS120I.NSPSCLST to a SOLVE:Netmaster Command data set (the COMMAND DD card): NSPKCMD, NSPKCM1, and NSPKPPI.
The NSPKPPI and NSPKCMD PROCs are the principal SNA View PPI procedures that send PPO data through the PPI and wait for commands coming from SNA View through the PPI. The NSPKPPI and NSPKCMD PROCs must be active at all times and must run in a background environment within SOLVE:Netmaster. To accomplish this, add the following statements to your NMINIT or NMREADY initialization PROCs:
Sub BSYS NSPKPPI
Sub BSYS NSPKCMD
When you complete all updates to SOLVE:Netmaster, you can issue the following command to verify correct installation:
SH PPIUSERS
The command displays two receivers, SNAVIEW and NSPNETV, and indicates the number of messages queued so you can monitor the number of messages that have been sent to SNA View.
|
|