Troubleshooting
Problem
Issuing NetView commands from a console or SDSF Syslog using the NetView command designator character is not working.
No command response is received.
The command is not sent to NetView and does not appear in the netlog or Canzlog.
This variation of the problem is typically seen after a NetView upgrade/migration to a newer version.
Symptom
NetView commands are not sent to NetView for execution.
No response is seen after the command is issued.
Diagnosing The Problem
This variation of the problem occurs because NetView is running with both v6.3 and v6.4 libraries.
These steps will verify that the correct command designator is coded and is being used.
If this shows that the correct Command Designator is installed and being used, then a mixed code environment
is causing the problem.
Start reviewing NetView configuration beginning with what is configured in CNMSTYLE.
Issue NetView command NVINFO. This will dump out the CNMSTYLE statements NetView uses into the netlog.
Search for 'MVSPARM.Cmd.Designator' to see what is being used.
In this example, my designator character is set to %
Next check what Designator character the NetView SSI is using.
Issue NetView command: revise debug scanssi
The response shows the NetView SSI is using % as the command designator
Check if the Designator character is active or not by issuing NetView command: REVISE DEBUG DUMPSST.
The response shows that % is Active. If it shows Inactive then the Command designator is not working.
Inactive status occurs when the wrong NetView SUBSYS SUBNAME is coded in IEFSSNxx
Finally, we can see what MVS thinks the NetView command designator is active by issuing MVS command: D OPDATA
If all of these checks show the correct Designator character is defined and Active, then NetView is running in a mixed release environment
is the reason the things are not working.
Resolving The Problem
If everything checks out as shown in the Diagnosing the Problem section,
then the problem is most likely caused by a mixed release NetView environment.
In this example, the customer has mixed NetView 6.3 into the Netview 6.4 environment.
This can be checked by issuing the following NetView commands:
DISPMOD DSIIPCLM ALL
DISPMOD DSI4LCUI ALL
And comparing CSECT dates as this shows output shows.
CNMCMSGR under DSIIPCLM shows a compile date of 19.287 (base 6.3) while
CNMCMSGR under DSI4LCUI shows a compile date of 22.110 (base 6.4).
The compile dates should be the same.
The compile dates should be the same.
Same thing with DSI4LGBL - the compile dates should be this same.
This is a indication of a mixed code environment is is causing the problem where the
NetView Command Designator does not work.
Once the modules were compiled with the correct code levels, the NetView Command designator
worked.
Or the mixed releases could be caused when the wrong level of a NetView library such as SCNMLPA1 is used in LPALST00.
Once the LPAR was IPL'ed with the correct level SCNMLPA1 library, the Designator character started working again.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJDU","label":"IBM Z NetView"},"ARM Category":[{"code":"a8m0z0000000AlwAAE","label":"Netview-\u003ECommands"}],"ARM Case Number":"TS014728757","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
05 December 2023
UID
ibm17086076