PoC: /* VTAM Display commands */ hint

2023-01-03T13:54:52Z

VTAM Display commands: hint

← Nächstältere Version		Version vom 3. Januar 2023, 15:54 Uhr
Zeile 90:		Zeile 90:
	\|-		\|-
	\|D NET,NETSRVR		\|D NET,NETSRVR
	\|Display Network Node Server List		\|Display Network Node Server List, only valid if VTAM is in End-Node configuration.
	\|-		\|-
	\|D NET,ID=name		\|D NET,ID=name

PoC: Die Seite wurde neu angelegt: „'''VTAM''' is a complex piece of Software. But basically it's just a bit like the UNIX ''inetd'' plus network stack, allowing remote entities to access locally…“

2022-02-19T11:48:04Z

Die Seite wurde neu angelegt: „'''VTAM''' is a complex piece of Software. But basically it's just a bit like the UNIX ''inetd'' plus network stack, allowing remote entities to access locally…“

Neue Seite

'''VTAM''' is a complex piece of Software. But basically it's just a bit like the UNIX ''inetd'' plus network stack, allowing remote entities to access locally defined services.<ref>Yes, this is a daring generalization. But we need to start ''somewhere'' with explanations.</ref>

This article tries to help remembering things. It should serve as a quick reference for handling tasks.

== Configuration ==
Usually, configuration is stored in a partitioned data set with the partial name ''vtamlst''. To derive it's name, look into ''sys1.proclib(vtam)'' to see the ''dd'' statements. Usually, it's
* ''sys1.vtamlst'', or
* ''sys1.local.vtamlst''.

Notable members include:
;atcstr*
:Basic configuration. The ''CONFIG'' directive designates which ''atccon''-file to load as default.
;atccon*
:A comma separated list of ''major nodes'' to be handled at VTAM startup.<ref>''Major nodes'' can be activated manually, though.</ref>

Remaining members designate ''major nodes''. That is, textual definition files. This task is usually be done from a TSO session.

=== Concepts of Major and Minor Nodes ===
VTAM major nodes are roughly member names in the ''vtamlst'' PDS. The first non-comment line starts with a name, the literal ''VBUILD'', <code>TYPE=''node type''</code>, and optional parameters.

Major node types:
* ADJCP (Adjacent Control Point)
* APPL (Application Program)
* CA (Channel Attachment)
* CDRSRC (Cross-Domain Resources)
* CDRM (Cross-Domain Resource Manager)
* XCA (External Communications Adapter)
* LOCAL (Local SNA)
* LUGROUP (Logical Unit Group)
* MODEL (Model definition for dynamically created PU and LU; mostly for APPN)
* SWNET (Switched, this is the definition of a "real" node)
* DR (Dynamic Reconfiguration or Change)
* ADSSJCP (Adjacent Control Point Table)
* ADJCLUST (Adjacent cluster routing definitions)
* APPNTOSA (APPN-to-subarea Class of Service mapping table)
* SATOAPPN (Subarea-to-APPN Class of Service mapping table)
* BNCOSMAP (Border node CoS mapping definitions)
* NETSRVR (Network node server list)
* GRPREFS (Generic resources preferences table)
* SAMAP (Subarea mapping table)
* SNSFILTR (Session awareness sense filter)

== Administering VTAM ==
This is done from a system console.

VTAM is required by TCPIP, but TCPIP is smart enough to cope with VTAM being shut down and restarted without caring for TCPIP.

=== VTAM Start commands ===
VTAM is usually automatically started in the course of an IPL.

{|class="wikitable"
!Command
!Comment
|-
|S NET
|VTAM start with defaults
|-
|S NET,,,(LIST=00)
|VTAM start with atcstr''00''
|}

=== VTAM Display commands ===
{|class="wikitable"
!Command
!Comment
|-
|D NET,APING,ID=''REMNODE'',LOGMODE=#INTER
|Create an APPC "loopback" session
|-
|D NET,APPLS
|Display VTAM applications status
|-
|D NET,BFRUSE
|Display VTAM buffers in use
|-
|D NET,CDRMS
|Display VTAM cross domains status
|-
|D NET,CDRSCS
|Display VTAM cross domain resources
|-
|D NET,COS
|Display VTAM cos table in use
|-
|D NET,GROUPS
|Display VTAM groups status
|-
|D NET,MAJNODES
|Display a list of '''active''' major nodes
|-
|D NET,NETSRVR
|Display Network Node Server List
|-
|D NET,ID=name
|Display VTAM resource status
|-
|D NET,ID=*.name
|Display VTAM resource status in any net
|-
|D NET,ID=ISTADJCP,E
|Display dynamic list of adjacent CPs
|-
|D NET,RTPS
|Display Rapid Transfer Protocol sessions. RTP is part of HPR.
|-
|D NET,TGPS
|Display Transmission Groups
|-
|D NET,TOPO
|Display APPN Topology
|-
|D NET,TRL
|Display Transport Resource List
|-
|D NET,U,ID=userID
|Display VTAM user ID status
|-
|D NET,VTAMOPTS
|Display VTAM startup options currently set
|}

=== VTAM Vary commands ===
{|class="wikitable"
!Command
!Comment
|-
|V NET,ACT,ID=name
|Activate VTAM resource
|-
|V NET,INACT,ID=name
|Inactivate VTAM resource
|-
|V NET,DRDS,ID=name
|Activate VTAM dynamic reconfiguration
|}

=== VTAM Change commands ===
{|class="wikitable"
!Command
!Comment
|-
|F NET,''VTAMOPTS'',''startoption=option''
|Run-Time change VTAM configuration
|-
|F NET,VTAMOPTS,SORDER=APPNFRST<br>F NET,TRACE,ID=''resname'',TYPE=BUF<br>F NET,NOTRACE,ID=''resname'',TYPE=BUF
|valgni="top"|Examples
|}

=== VTAM Halt commands ===
VTAM won't halt QUICK when application programs are active. Stop with the given commands.
* NFS-Client<ref>If anyone knows how to prevent the NFS-Client from starting at startup, please drop [mailto:poc@pocnet.net me] a note.</ref>
P NFSC
* TSO
P TSO

{|class="wikitable"
!Command
!Comment
|-
|Z NET,CANCEL
|VTAM abnormal termination command
|-
|Z NET,QUICK
|VTAM somewhat faster termination command
|-
|Z NET
|VTAM normal termination command
|}

== Literature ==
* IBM z/OS Basic Skills Information Center: [https://www.ibm.com/docs/en/zos-basic-skills?topic=networking-zos ''Networking on z/OS'']
* IBM Redbook: ''P/390, R/390, S/390 Integrated Server: OS/390 New User′s Cookbook'', document number [https://ibmdocs.pocnet.net/SG24-4757-01.pdf SG24-4757-01]

== Footnotes ==
<references />

[[Category: MVS]]

VTAM Cheat Sheet - Versionsgeschichte

PoC: /* VTAM Display commands */ hint

PoC: Die Seite wurde neu angelegt: „'''VTAM''' is a complex piece of Software. But basically it's just a bit like the UNIX ''inetd'' plus network stack, allowing remote entities to access locally…“