|
Table Of Contents
Mainframe-to-Router Link Configuration Problems
Router Service Point is Disabled
VSAM Data Set Not Available to NetView
Troubleshooting
This chapter describes the procedures for troubleshooting problems you may encounter when installing ISM:
• Mainframe-to-Router Link Configuration Problems
Mainframe-to-Router Link Configuration Problems
This section describes procedures to determine the following router configuration problems:
• Router is Not Defined to VTAM
• Router Service Point is Disabled
Router is Not Defined to VTAM
Problem
If the router is not defined to VTAM, then you may see the following conditions when you execute a runcmd command for the router or try to display it from VTAM:
•Executing runcmd sp=router_name,appl=console,show ? produces the following message:
- CNM01 DSI358I RUNCMD FAILED. ID'router_name' IS INVALID, SENSE CODES = X'08060000'
•Executing d net,id=router_name produces the following message:
CNM01 IST453I ID PARAMETER VALUE INVALID
These messages indicate that an SSCP-to-PU session has not been established between VTAM and the router. Another possible cause for the error is that the uservarname command has been specified on the ID operand of the display ncpstor command.
Action
To define the router in VTAM, see the "Configuring a VTAM Connection" section.
Router is Not Active
Problem
If the router is defined to VTAM, but a connection has never been established, you may see the following conditions when you execute a runcmd command for the router or try to display the router from VTAM:
•Executing runcmd sp=router_name,appl=console,show ? produces the following message:
- CNM01 DSI264I RUNCMD FAILED FOR router_name - RTNCD=X'04',FDBK2=X'04',
SYSTEM SENSE=X'0807',USER SENSE=X'0000'
•Executing d net,id=router_name produces the following message:
CNM01 IST097I DISPLAY ACCEPTED
` CNM01
IST075I NAME=router_name , TYPE=PU_T2
IST486I STATUS=CONCT , DESIRED STATE=CONCT
IST1043I CP NAME=***NA***,CP NETID=NETA ,DYNAMIC LU=YES
IST136I SWITCHED SNA MAJOR NODE=SWDRTRS
IST654I I/0 TRACE=OFF,BUFFER TRACE=OFF
IST1500I STATE TRACE=OFF
IST314I END
Action
Verify that the configuration arguments for the router's VTAM definition correspond to the SNA service point configuration by completing the following steps:
Step 1 Telnet to the router and run the show sna command.
•If the PU STATUS=ACTIVE, then the router probably has a session to VTAM but is using the wrong XID.
•If the PU STATUS=XID, then the router is attempting to contact VTAM but has not had a response. This can indicate any of the following problems:
–No path to VTAM
–XID mismatch
–rmac argument in the router's SNA host configuration does not match the mac_address argument on the MVS system
Step 2 From VTAM, execute the debug sna packet command to verify that the router is sending an XID request every 30 seconds.
If the XID does not exist on the MVS system, the MVS log shows a VTAM message indicating a mismatch. VTAM writes a message to the log whenever it receives an XID that it does not recognize.
For more information on verifying your configuration, see the "Correlating the Router and VTAM Configuration Information" section.
Router Service Point is Disabled
Problem
If the router is active, but the service point is disabled, you may see the following conditions when you execute a runcmd command for the router or try to display the router from VTAM:
•Executing runcmd sp=router_name,appl=console,show ? produces the following message:
- CNM01 DW0614E RUNCMD REQUEST NOT PERFORMED BY ID router_name FOR APPL='CONSOLE',SENSE CODE=X'080C005' FUNCTION INACTIVE
•Executing d net,id=router_name produces the following message:
CNM01 IST097I DISPLAY ACCEPTED
` CNM01
IST075I NAME= router_name , TYPE=PU_T2.1
IST486I STATUS=ACTIV , DESIRED STATE=ACTIV
IST1043I CP NAME=router_name, CP NETID=NETA ,DYNAMIC LU=YES
IST136I SWITCHED SNA MAJOR NODE=SWDLURSJ
IST654I I/O TRACE=OFF,BUFFER TRACE=OFF
IST1500I STATE TRACE=OFF
IST314I END
Action
If the service point has not been enabled, see the "Configuring the Router" section.
If you need further information on configuring the router service point, see the Cisco IOS software Bridging and IBM Networking Configuration Guide and Bridging and IBM Networking Command Reference.
ISM Installation Problems
This section describes the procedures for diagnosing problems which may be found during verification of the ISM installation:
• ISM Task Not Known to NetView
• VSAM Data Set Not Available to NetView
ISM Task Not Known to NetView
Problem
If you receive the error message "DSI077A `NSPDSR' STATION NAME UNKNOWN" after issuing the list taskname command from NetView, then the ISM task has not been included in the DSIDMN member of the NetView DSIPARM data set.
Action
You can start the task manually for the current system, and then update the DSIPARM data set to fix the problem permanently.
Step 1 To manually start the unknown task, enter the following command from a NetView console (where taskname is the name of the unknown task, and membername is the DD name in the DSIDMN member of NetView's DSIPARM data set):
START TASK=taskname,MOD=DSIZDST,MEM=membername,PRI=6
Step 2 Verify that the corresponding display is similar to the following for your taskname:
DSI166I NSPDSR IS ACTIVATED BY HAL2
DSI556I NSPDSR : VSAM DATASET `OPEN' COMPLETED, DDNAME = `NSPHISTR'
RETURN CODE = X'00', ACB ERROR FIELD = X'00'
DSI530I `NSPDSR ` ; `DST' IS READY AND WAITING FOR WORK
Step 3 To update NetView permanently, complete the tasks described in the " Updating the DSIPARM Members" section in Chapter 3, "Installing ISM."
ISM Task Not Started
Problem
If you receive the message "STATUS: NOT ACTIVE" after issuing the list taskname command from NetView, then the ISM task has not been started by NetView.
Action
You can start the task manually for the current system, and then update the DSIPARM data set to fix the problem permanently.
Step 1 To manually start the task, enter the following command from a NetView console:
START TASK=taskname
Step 2 Verify that the corresponding display is similar to the following for your taskname:
DSI166I NSPDSR IS ACTIVATED BY HAL2
DSI556I NSPDSR : VSAM DATASET `OPEN' COMPLETED, DDNAME = `NSPHISTR'
RETURN CODE = X'00', ACB ERROR FIELD = X'00'
DSI530I `NSPDSR ` ; `DST' IS READY AND WAITING FOR WORK
Step 3 To update NetView permanently, complete the tasks described in the " Updating the DSIPARM Members" section in Chapter 3, "Installing ISM."
VSAM Data Set Not Available to NetView
Problem
If you receive the messages "DSI553I taskname: ERROR OCCURRED DURING VSAM `OPEN' PROCESSING IN `PRIMARY'" and "DSI554I taskname: DST VSAM SERVICES INITIALIZATION HAS FAILED" after issuing the list taskname command from NetView, then the corresponding VSAM data set for the task is not available to NetView.
Action
You can dynamically allocate the data set to NetView for the current system, and then update the DSIPARM data set to fix the problem permanently by completing the following tasks:
Step 1 To dynamically allocate the VSAM data set, enter the following command from a NetView console:
ALLOCATE DS(vsam.dataset) F1(ddname) SHR
Where vsam.dataset is the name of the unavailable VSAM data set, and ddname is the DD name in the DSIDMN member of NetView's DSIPARM data set.
Step 2 Verify that the corresponding display is similar to the following for your VSAM DD name:
CNM272I NSPHISTR IS NOW ALLOCATED
Step 3 To start the task associated with the VSAM data set manually, enter the following command from a NetView console:
START TASK=taskname
Step 4 Verify that the corresponding display is similar to the following for your taskname:
DSI166I NSPDSR IS ACTIVATED BY HAL2
DSI556I NSPDSR : VSAM DATASET `OPEN' COMPLETED, DDNAME = `NSPHISTR'
RETURN CODE = X'00', ACB ERROR FIELD = X'00'
DSI530I `NSPDSR ` ; `DST' IS READY AND WAITING FOR WORK
Step 5 To update NetView permanently, complete the tasks described in the " Updating NetView" section in Chapter 3, "Installing ISM." Be sure that the corresponding DD statement for this data set has been added to your NetView procedure.
Posted: Fri Aug 6 09:41:47 PDT 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.