z/OS JES2 Commands
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


$D PATH - Display paths from node to node

z/OS JES2 Commands
SA32-0990-00

Function

To display the path from one node to another in a network.

One or more parameters on this command accepts wild cards. Parameter descriptions will note that.

Syntax

Read syntax diagramSkip visual syntax diagram
>>-$D----------------------------------------------------------->

>--PATH--+------------------------------------+--+-------+-----><
         +-n--+-----------+-------------------+  '-,LONG-'   
         |    '- ---+-n-+-'                   |              
         |          '-*-'                     |              
         +-'--nodename--'---------------------+              
         |    .-,------------------------.    |              
         |    V                          |    |              
         '-(----+-+-n-+--+-----------+-+-+--)-'              
                | '-*-'  '- ---+-n-+-' |                     
                |              '-*-'   |                     
                +-nodename-------------+                     
                '-'--nodename--'-------'                     

Parameters

PATH
Displays the path from the node at which the command is entered to the node specified in the command.
(nodename|n|*)
Specifies the target node. You can use nodename or node number or an asterisk ( * ) to obtain information for all nodes. You can also specify wild cards for the path name. See Using wildcards for additional information.
LONG
Displays information about secondary lines.

Authority Required

This command requires display authority. The description of the $T RDRnn command explains how to ensure that the authority of the appropriate MVS™ system command group is assigned.

This command requires read security access authority. For a description of assigning command input authority, see z/OS JES2 Initialization and Tuning Guide, SA32-0991.

Scope

MAS-wide. This command displays information about the entire MAS.

Messages

The $HASP231 message displays the nodes in the path from the node on which the command is entered to the node named in the command.

The STATUS parameter will be displayed; however, this parameter cannot be specified (it is display-only). A STATUS=SIGNON VIA LINE will be displayed whenever the primary line displayed in the message is currently in the process of a sign-on.

Note: If there are multiple paths through the same adjacent node, only the primary trunk is displayed.

Examples

 1 
 $dpath(vmx02)                                                    
 $hasp231 path(vmx02) 634                                         
 $hasp231 path(vmx02)     status=(through member d3x0),rest=100,  
 $hasp231                 path=(isof1,vmx02)
The path from local node isof1 to target node vmx02 is made through MAS member d3x0 and consists of only these two nodes.
 2 
$DPATH001                                                         
$HASP231 PATH(BATEST) 856                                         
$HASP231 PATH(BATEST)    STATUS=(THROUGH MEMBER ST37),REST=400,   
$HASP231                 PATH=(S2324,AB2JES,BATEST),              
$HASP231                 STATUS=(THROUGH LNE1101),REST=400,       
$HASP231                 PATH=(S2324,JSYSTEM,BATEST),             
$HASP231                 STATUS=(AWAITING RESET WITH AHFJES),     
$HASP231                 REST=400,PATH=(S2324,AHFJES,BATEST)
The path from local node S2324 to target node BATEST occurs through MAS members ST37/LNE1101, causes the installation a resistance of 400, and consists of three nodes.
 3 
$dpath(node1)
$HASP231 PATH(NODE1)                                    
$HASP231 PATH(NODE1)     STATUS=(THROUGH LNE1),REST=200,
$HASP231                 PATH=(NODE2,NODE1)
 4 
$dpath(node1),long
$HASP231 PATH(NODE1)                                         
$HASP231 PATH(NODE1)     STATUS=(THROUGH LNE1,THROUGH LNE11),
$HASP231                 REST=200,PATH=(NODE2,NODE1)

The LONG parameter displays information about secondary lines.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014