|
|
This chapter contains instructions for updating VTAM and MVS resources 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 refer to different sections of this chapter depending on whether your connection to the workstation is via LU6.2 or TCP/IP. The following topics are discussed in this chapter:
You must configure the mainframe to communicate with the CiscoWorks Blue Maps workstation by one of the following protocols:
This section describes modifications to the VTAM datasets of a mainframe that is connected to the SNA View workstation via LU6.2. If your workstation connection uses a TCP/IP connection, refer to "Configuring TCP/IP Connectivity."
To configure LU6.2 connectivity, you perform the following steps:
Step 1 Update the MODETAB Entry.
The MODETAB entry used in the new APPL and LU definitions must contain the following LOGMODE entries. If your MODETAB table in VTAMLST lacks these entries, add them before you re-assemble and link-edit the MODETAB. The text for these table entries is available in prefix.SNAVIEW.NSPSAMP(MODEENT). A sample assembly and link-edit JCL is available in prefix.SNAVIEW.NSPSAMP(MODEJCL).
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'
*
DSIL6MOD MODEENT LOGMODE=DSIL6MOD,FMPROF=X'13',TSPROF=X'07', X
PRIPROT=X'B0',SECPROT=X'B0',COMPROT=X'50B1',TYPE=X'00', X
SSNDPAC=X'00',SRCVPAC=X'03',PSNDPAC=X'03', X
RUSIZES=X'8585',PSERVIC=X'060200000000000000002C00'
The changes to the MODETAB take effect when VTAM is restarted, but can also be loaded dynamically with the following system console command:
Step 2 Define the Physical Unit.
The PU definition for the SNA View workstation must:
Additionally, if the PU is defined under an NCP major node, the NCP definition must contain a 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.SNAVIEW.NSPSAMP(SWMNILU).
Step 3 Define the Logical Unit.
Define an independent LU under a Cross-Domain Resource major node, associating the LU to an existing PU. A sample CDRSC definition is available in prefix.SNAVIEW.NSPSAMP(). Alternatively, you may define an independent LU under an existing PU definition by coding LOCADDR=0.
You may modify the resource names in the sample major node members to your site's naming conventions for network resources, but changes to these default names must be appended to the parameter cards as well (refer to "Customizing SNA View Parameter Cards").
This section provides modifications to your mainframe TCP/IP installation required for SNA View. If your workstation connection is via LU6.2, go to "Performing MVS and VTAM Updates." TCP/IP connectivity can be one of the following types:
The following steps are for systems that use IBM TCP/IP for MVS.
Step 1 Reserve port numbers in the PROFILE.TCPIP file.
Choose two available port numbers and add the following two lines to your list of PORT values in your PROFILE.TCPIP file (the default values used are 6106 and 6107):
This step is optional. If you do not reserve specific port numbers for SNA View to use, 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.
Step 2 Identify TCP/IP high level qualifier.
If your TCP/IP installation did not use the default high-level qualifier (that is, the DATASETPREFIX parameter was needed in your PROFILE.TCPIP file), then add a PARM statement to your SNA View startup job with the parameter TCPIP_PREFIX. The startup sample for a batch job is located in prefix.SNAVIEW.NSPSAMP(NSPJCL) and the started task sample is in prefix.SNAVIEW.NSPSAMP(NSPOPEN). For example, if your TCP/IP high-level qualifier is TCPIPX, modify the EXEC card in your startup job to reflect the following:
If your system uses Interlink SNS/TCP access, copy the LSCNCOM Load Module.
Interlink provides an LSCNCOM load module that must be used in place of the LSCNCOM that is provided in prefix.SNAVIEW.NSPLOAD. Either replace the module in prefix.NSPOPEN.NSPLOAD, or name the Interlink TCP/IP load library in the STEPLIB of the SNA View startup job ahead of prefix.SNAVIEW.NSPLOAD.
This section presents the modifications required in your system's MVS and VTAM datasets. These changes are necessary regardless of the method used to connect the workstation. Notify your system programmer of the changes to be made to the SYS1.PARMLIB members.
Step 1 Authorize prefix.SNAVIEW.NSPLOAD.
Add the dataset prefix.SNAVIEW.NSPLOAD and its DASD volume name to your list of APF authorized datasets in SYS1.PARMLIB(IEAAPFxx). This dataset is needed to allow SNA View to process certain authorized commands and perform security checks.
If you have a software utility available to dynamically authorize new datasets, use it to add prefix.SNAVIEW.NSPLOAD; otherwise, an IPL must be performed to authorize this dataset.
Step 2 Set the performance group.
Add a TRXNAME parameter for SNA View to the 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 under VTAM to ensure that SNA View receives enough CPU time to avoid a backlog of network information processing. The default name for SNA View startup jobs is NSPOPEN. For example, if NetView is running in performance group 8, specify the addition for SNA View as:
After a new entry is added, the ICS file can be dynamically reloaded by entering the MVS command:
where xx is the two-digit suffix of the member that was edited.
Step 3 Add an entry to to the program properties table.
Add a PPT entry to your SYS1.PARMLIB(SCHEDxx) for SNA View:
After the new entry is added, the PPT can be dynamically reloaded by entering the MVS command:
where xx is the two-digit suffix of the member that was edited.
Step 4 Add the VTAM parameter PPOLOG.
Add PPOLOG=YES to your VTAM startup options in 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 prefix.SNAVIEW.NSPSAMP(NSPAPPL) dataset.
This section lists and describes the initialization parameter cards that you must customize to match the mainframe resources with the workstation configuration. The cards listed in Table 2-1 are located in prefix.SNAVIEW.NSPSAMP(NSPPARM).
Valid Values: VTAM APPL Definition
Sample Syntax: PPO NSPPO1
Description: The ID of the APPL definition coded with AUTH=PPO. This identifies the Primary Program Operator application which will receive unsolicited VTAM messages.
Valid Values: VTAM APPL Definition
Sample Syntax: CNM DSICRTR
Description: The ID of the APPL definition coded with AUTH=CNM. This identifies the application program which receives unsolicited network services requests (alerts) that require further processing. The default alerts application name used by VTAM is DSICRTR (defined in the CNM routing table ISTMGC01).
Valid Values: none
Sample Syntax: PPI
Description: Add this card to connect SNA View to the NetView or Netmaster PPI for the receipt of VTAM messages and alerts. The program-to-program interface must be active in accordance with the NetView or Netmaster documentation.
Valid Values: VTAM APPL Definition
Sample Syntax: SPO NSPSPO1
Description: The ID of an APPL definition card coded with AUTH=SPO. This identifies a Secondary Program Operator application which will receive solicited messages generated by commands issued from the workstation. Multiple SPO cards are allowed.
Valid Values: Load module
Sample Syntax: SEC NSPRACF
Description: This card identifies the load module in prefix.SNAVIEW.NSPLOAD called to process calls to the mainframe security software.
Valid Values: plu slu logmode TPM TPC
Sample Syntax: SERVER NSPAPL1 NSPLU01 PARALLEL NSPENMS NSPPENCS
Description: This card identifies the necessary values needed to establish a parallel LU6.2 connection to the workstation. Multiple SERVER cards are allowed. The positional parameters are as follows:
Valid Values: hciport cmdport
Sample Syntax: TCP 6106 6107
Description: This card identifies the TCP/IP ports that are used on the SNA View workstation for the HCI Server and the Command Server. Multiple TCP cards are allowed. The positional parameters are as follows:
Valid Values: Console Name
Sample Syntax: MVS NSPCONS1
Description: The MVS parameter card specifies 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.
Valid Values: Console Name
Sample Syntax: CMD NSPCONS2
Description: The CMD parameter card specifies 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.
This section explains the updates necessary for SNA View to work in conjunction with NetView. The following topics are described in this section:
Verify that the NetView subsystem address space is active, as defined in the NetView Installation and Administration Guide. The NetView subsystem interface is necessary for cross-memory communications between NetView and SNA View. The subsystem application should be initiated before NetView is engaged.
Follow the procedure in this section to change the NetView dataset for SNA View collection.
Step 1 Define the SNA View mainframe collector optional task by adding the following definition to the DSIDMN member of your NetView's DSIPARM dataset:
Verify that the two NetView tasks CNMCSSIR and CNMCALRT are defined with INIT=Y. These tasks provide command and message forwarding services for SNA View.
Step 2 Define the mainframe alert collection exit by adding the following definition to the DSICRTTD member of your NetView's DSIPARM dataset:
Step 3 Define a command model for the NSPMQS load module by adding the following definition to the DSICMD member of your NetView's DSIPARM dataset:
Step 4 Define an additional NetView autotask by adding the following definition to the DSIOPF member of your NetView's DSIPARM dataset:
The Operator ID (NSPAUTO1) may be changed to conform to your site requirements, but it must match the NSPCMD_OPERATOR configuration parameter on the workstation. Refer to the CiscoWorks Blue Maps Installation Guide for further information on SNA View configuration parameters.
The PROFILEN name (NSPPROF) may be changed to conform to your site requirements. The profile will be defined in Step 5.
Step 5 Define a profile for the operator ID, defined in Step 4, by adding a member named NSPPROF to your NetView's DSIPRF dataset. NSPPROF must contain the following three lines:
The member name may be changed to conform to your site requirements, but it must match the PROFILEN statement that was coded in Step 4.
Step 6 Add the following line to your initial command list to ensure that the autotask defined in Step 4 is started each time NetView is brought up:
Follow this procedure to copy members to NetView libraries.
Step 1 Copy the following two members from prefix.SNAVIEW.CLIST into a NetView DSICLD dataset:
Step 2 Copy the NSPXIDA member from prefix.SNAVIEW.NSPSAMP into a NetView DISPARM dataset.
SNA View requires three exits, a DST, and a command processor to run in NetView's address space. The load modules for these processes are provided in prefix.SNAVIEW.NSPLOAD for NetView Version 2.2.
If your system is running NetView 2.2, copy the following load modules from prefix.SNAVIEW.NSPLOAD into a NetView STEPLIB dataset:
If you are using a version of NetView other than Version 2.2, modify and submit the JCL in prefix.SNAVIEW.NSPSAMP(ASMJCL) according to the instructions in that member to create the five load modules.
Routing Information Data is retrieved from the VSAM database by NetView Command Processors invoked by SNA View over the program-to-program interface provided by NetView.
Follow this procedure to install the NetView Command Processor.
Step 1 Add the following NetView task statement to the DSIDMN member of NetView.
Step 2 Add the NetView CMDMDL statements to the DSICMD member of NetView.
Step 3 Add member NSPXIDA to the NETVIEW DSIPARM dataset.
Step 4 Add a DD statement to the NETVIEW start procedure to include the dataset allocated previously. The DD statement, DDNAME, must be, XIDDATA.
Restart NetView to activate the changes to NetView.
This section describes how to allow CiscoWorks Blue SNA View to interact with Netmaster. The dataset members listed in Table 2-2 are located in prefix.SNAVIEW.NSPCLIST and are used to facilitate the following changes:
You do not have to restart Netmaster for the changes to take effect.
Step 1 Verify subsystem interface installation.
Verify that the Netmaster subsystem interface (SSI) address space is active, as defined in the Netmaster Implementation and Administration Guide. The SSI is necessary for cross-memory communications between Netmaster and SNA View.
Step 2 Make changes to CNMPROC.
For SNA View to receive alert information from Netmaster, the NCL code in prefix.SNAVIEW.NSPCLIST(NSPKCNM) must be added into the production CNMPROC at a point where all CNM flow will be seen. The recommended point for this code addition is immediately following the mainline &CNMREAD.
In the distributed CNMPROC ($NWCNMPR), the label .READOK is the point determining the &CNMREAD to be successful. Therefore, the NCL must be inserted immediately after the .READOK label.
Step 3 Make changes to PPOPROC.
For SNA View to receive system message information from Netmaster, the NCL code in prefix.SNAVIEW.NSPCLIST(NSPKPPO) must be added into the production PPOPROC at a point where all messages will be seen. The recommended point for this code addition is immediately following the mainline &PPOREAD.
Step 4 Copy members to Netmaster libraries.
Copy the following members from prefix.SNAVIEW.NSPCLIST into a Netmaster COMMAND DD dataset:
Step 5 Start the procs.
Procs NSPKPPI and NSPKCMD are the primary PPI procs that either send CNM and PPO data through the PPI or await commands coming from SNA View through the PPI. As such, they must be active at all times and must run in a background environment within Netmaster. To accomplish this, add the following statements to your NMINIT or NMREADY initialization procs:
You can also issue these commands from the OCS console.
Step 6 Verify the correctness of Netmaster updates.
When you complete all updates to Netmaster, you can issue the following command to verify correct installation:
The result of this command will display two receivers, SNAVIEW and NSPNETV. This command will indicate the number of messages queued so you can monitor the number of messages that have been sent to SNA View
|
|