Previous Topic: Customize Activity Log Settings

Next Topic: SNA Groups


How to Customize SNA Resource Discovery

When you start the region, it automatically discovers the SNA resources controlled by the local VTAM domain. You can customize the discovery process as follows:

Warm and Cold Starts of SNA Resource Discovery

The SNA resource discovery component discovers SNA resources in the local VTAM domain and monitors their status. By customizing the AUTOSNACNTL parameter group, you can start the discovery process in one of the following ways:

Warm Start

Remembers the previous states of all previously discovered resources, compares these to the current conditions, and updates them accordingly. Newly discovered resources are also added.

If the filter criteria ignore resources that were previously discovered, then they are placed into an UNKNOWN state.

Cold Start

Discovers the network afresh. It clears all discovered resources and discovers them according to the filter criteria. The default value is NO.

Control Dynamic and Transient SNA Resources

During normal VTAM execution, dynamic network resources can be added and deleted. The region receives events when these resources are added by VTAM, and they are automatically discovered and added to the network database.

When resources are deleted by VTAM, you can specify that the resources be also deleted from the region network database. This can be specified to occur during the following:

You can also specify response and processing time limits for VTAM events.

These parameters are specified on the second panel of the AUTOSNACNTL parameter group.

Delete Unknown SNA Resources During a Warm Start

If you want to delete nonexistent SNA resources during a warm start, specify YES in the Delete Unknown Resources: During Warm Start Discovery? field. During the next warm start of your region, any resources that are unknown at that time are deleted. You can also specify NEXT which deletes unknown resources during the next warm start and the field is then set back to NO for subsequent warm starts.

Note: If you specify YES or NEXT, all resources are affected by the deletion regardless of their type.

If you anticipate that there are many network changes to discover, it may be more efficient to specify a cold start for the next discovery rather than specifying NEXT.

Delete Unknown SNA Resources During Normal Execution

If you want the resources that VTAM dynamically deletes to also be dynamically deleted from the network database, specify YES in the Delete Unknown Resource: During Normal Execution? field. When an event arrives specifying that a resource has been deleted, the resource and any child resources are deleted. This parameter is only effective on the following types of SNA resource:

Specify Response and Processing Time Limits for VTAM Events

The following wait intervals can be specified to control the response from and processing of VTAM events:

Display Response Wait Limit

Specifies how long the system waits for VTAM to respond to a display command. If exceeded, the command is timed out.

Delayed Event Processing Wait

Specifies how long the system waits before it processes IST590I events. This allows time for VTAM to update information before the region accesses it.

Control Discovery Based on the Status of PPO Message Flow

If PPO message flow stops, the region cannot detect changes in the status of currently discovered SNA resources. When the flow starts again, you can rediscover the resources. Use the Schedule Discovery on PPO Start field to control the rediscovery process.

Select Which SNA Resources Are Discovered

Through the AUTOSNACNTL parameter group, you can limit the discovered SNA resources.

By default, the region does not discover Rapid Transit Protocol (RTP) PUs for LU-LU sessions and dynamic applications. You can enable the discovery through the Discover LU-LU RTPs? and Discover Dynamic Appls? fields.

Note: If you enable the discovery of dynamic applications, we recommend that you define a filter using the NAME keyword to exclude virtual terminal LUs.

You can define an SNA filter to determine which SNA resources are discovered during startup. A supplied sample filter discovers all SNA resources to the PU level. However, by defining your own filter, you can specify which resources are included or excluded during discovery.

Note: The default filter does not discover LU, SWLU, and CDRSC resources. The default filter also does not discover any resources in the VTAM state RESET and RELSD.

You can monitor the status of the discovery process by accessing the Network Discovery panel (/SNADMIN.D). This panel shows a discovery log and a discovery status bar.

Define a Filter

You can define a filter by specifying filter criteria on the third page of the AUTOSNACNTL parameter group.

Note: By default, the sample filter appears.

To specify your own SNA network resource discovery filter

  1. Press F4 (Update) and move the cursor to the text editor.
  2. Specify your criteria using the following syntax:
    EXCLUDE [ TYPE={ type | ‘type1 type2 ...’ } 
              STATE={ state | ‘state1 state2 ...’ } 
              NAME={ mask | ‘mask1 mask2 ...’ } ]
    INCLUDE [ TYPE={ type | ‘type1 type2 ...’ } 
              STATE={ state | ‘state1 state2 ...’ } 
              NAME={ mask | ‘mask1 mask2 ...’ } ]
    WILDCHAR char
    
    EXCLUDE

    Excluded resources are not included in the network model. All identified resources are compared against the EXCLUDE specifications to find which resources are excluded.

    INCLUDE

    Included resources are included in the network model. All identified resources are compared against the INCLUDE specifications to find which resources are included.

    If used with EXCLUDE, INCLUDE only affects resources that are tagged for exclusion. An excluded resource is tested against the INCLUDE specifications. If any of its attributes match the criteria, then the resource’s EXCLUDE tag is removed and it is included in the network model.

    TYPE={ type | ’type1 type2 ...’ }

    Specifies the resource types to exclude or include.

    STATE={ state | ’state1 state2 ...’ }

    Specifies the VTAM states of the resources to exclude or include.

    Note: A list of VTAM states and their corresponding actual states can be accessed by entering the /SNADMIN.V path.

    NAME={ mask | ’mask1 mask2 ...’ }

    Specifies the names of the resources to exclude or include. The name can be a full name or a name mask using the wildcard character defined in the WILDCHAR statement.

    Note: At least one of the TYPE, STATE, and NAME keywords must be specified. If a NAME is specified, then an associated TYPE must also be specified.

    WILDCHAR char

    If no WILDCHAR statement is specified, then * is assumed as the wildcard character.

The same keyword cannot be used more than once for each statement. If more than one keyword is specified on a statement then the condition specified is a logical AND of all the keywords specified.

Multiple values for a keyword indicate that any resource that satisfies one of the values is acceptable. For example, there are three names specified for the inclusion of a resource: A, B, and C. A resource with the name A is discovered because it satisfies one of the values. In other words, all resources of the name A, B, or C are discovered.

Example: Exclude

The following example specifies the exclusion of all LU or PU type SNA resources, and any SNA resources in the NEVAC state:

EXCLUDE STATE=NEVAC
EXCLUDE TYPE='LU PU'

Example: Include

The following example specifies the inclusion of all SNA resources with the name IBMCDRSC and of type CDRSC, or with a name that satisfies ASYD11* and of type PU:

INCLUDE NAME=IBMCDRSC TYPE=CDRSC
INCLUDE NAME=ASYD11* TYPE=PU

Example: Include

The following example specifies that all APPLs whose name starts with A, are excluded, but any that are in a VTAM state beginning with ACT are re-included. APPLS that are NOT in a state beginning with ACT, and have a name starting with A, are excluded. All other, non-APPL resource types and states are also included.

EXCLUDE TYPE='APPL' NAME='A*'
INCLUDE STATE='ACT'

Note: Always code EXCLUDE before INCLUDE.

Customize the Information About SNA Resources

You can customize the information about the SNA resources discovered in the local domain by using the network discovery exit, dsnpref.NMC1.CC18EXEC($RSUSRAX). dsnpref is the data set prefix that is specified during product installation. In this exit, you can specify the associated SNA resource model, another name or description for the resource to make it more identifiable, and user tags.

A sample of the exit is provided. To use this exit, you need an understanding of NCL. The code is commented; however, for more information, see the Network Control Language Programming Guide and the Network Control Language Reference Guide.

Important! If modifications are required, copy the distributed member to the TESTEXEC data set for the region for modification.

The following variables are available to the network discovery exit and let you identify the SNA resources.

ZRSNETID

Specifies the network identifier for a resource.

ZRSDOMAIN

Specifies the network domain for a resource.

ZRSRSNAME

Specifies the SNA resource name.

ZRSRSTYPE

Specifies the SNA resource type. Valid types are as follows:

ZRSRSNAMEC1...8

Specifies the first to eighth characters of a resource name.

ZRSRSNAMEN1...8

Specifies the first to eighth characters of the network qualifier portion of the resource name.

Note: These variables only apply when the resource is an ADJCP because ADJCPs are stored in the format network-qualifier.resource-name, for example, NETQUAL.ADJCPNME.

ZRSPRNAME

Specifies the parent resource name.

ZRSPRNAMEC1...8

Specifies the first to eighth characters of the parent resource name.

ZRSPRNAMEN1...8

Specifies the first to eighth characters of the network qualifier portion of the parent resource name.

Note: These variables only apply when the parent resource is an ADJCP because ADJCPs are stored in the format network-qualifier.resource-name, for example, NETQUAL.ADJCPNME.

ZRSDESC

Specifies the resource description.

ZRSMAJNODE

Specifies the name of the major node that owns the resource.

ZRSSTATUS

Specifies the current actual state.

ZRSDSTATUS

Specifies the current desired state.

ZRSVSTATUS

Specifies the last known VTAM status.

You can use the following variables to customize the information about SNA resources:

SYSMSG

Specifies the error message.

ZRSCOLDST

Specifies Cold start?—NO or YES.

ZRSDESC

Specifies the resource description.

Limits: 38 characters

ZRSMODEL

Specifies the model template name.

Limits: 12 characters

ZRSUSRTAG1...5

Specifies user-defined resource tags. You can use these tags to make the identification of a resource easier.

Limits: 52 characters

The following return codes must be returned to the caller:

0

Indicates that the request was successful.

1

Indicates that the resource is excluded or deleted.

8

Indicates that an error occurred (the exit is disabled from further calls during the current network discovery).

This exit is invoked only if one of the following conditions is satisfied:

Tune the Discovery Process

The Network Discovery Command Thresholds parameters of the AUTOSNACNTL parameter group let you throttle the CPU utilization of the discovery process.

In a large VTAM domain, the discovery process might issue a large number of commands in rapid succession and stress the system such that other functions cannot be performed. You can use these parameters to tune the number of commands that can be issued in a certain time.

Discover SNA Resources

The region automatically discovers the SNA resources on the system when the region starts.

To rediscover the resources at any other time

  1. Enter /PARMS at the prompt.

    The Customizer : Parameter Groups panel appears.

  2. Enter U beside the AUTOSNACNTL parameter group

    The AUTOSNACNTL - SNA Automation Specifications panel appears.

  3. (Optional) Update the discovery criteria.
  4. Press F6 (Action).

    The resources are rediscovered.