Version 8.1.3	SEARCH   INDEX   CONTENTS   |   PDF PAGE   PDF BOOKS   |   HOME   UP   PREV   NEXT

To communicate with other nodes, Entire Net-Work requires a definition of its own operating environment, access method information, and peer node characteristics. This is accomplished with the Entire Net-Work parameter statements: NODE, DRIVER, LINK.

The NODE statement specifies the global operating parameters for the Entire Net-Work node (note that all interregion communication information is specified by the ADARUN control statement described in the previous section).

Entire Net-Work control statements must always begin with the NODE statement, followed by one or more DRIVER statements (one for each driver type), and the related LINK statements. DRIVER and LINK statements may be in any order, as long as no LINK statement precedes its related DRIVER statement.

A DRIVER statement must be specified for each line driver. The DRIVER statement indicates the operational parameters for the line driver's access method and default values for the related links.

A LINK statement may be specified for each link to a remote node. The LINK statement specifies the driver-specific parameters to be used for the connection. Each LINK statement must be associated with a previously specified DRIVER statement.

This document covers the following topics:

• Conventions

• XCF NODE Statement

• XCF DRIVER Statement

• XCF LINK Statement

Conventions

This section covers the following topics:

• Syntax Conventions

• Syntax Rules

Syntax Conventions

The following table describes the conventions used in syntax diagrams of Entire Net-Work statements.

Syntax Rules

The following rules apply when specifying Entire Net-Work parameter statements:

• Each Entire Net-Work parameter statement occupies positions 1 - 72 of at least one line.

• The statement type (NODE, LINK, or DRIVER) must be specified as the first nonblank item on the statement.

• The node name, driver name, translation definition function, or link name follows the statement type, separated by at least one blank (space).

• Keyword parameters may be specified following either the node name on NODE statements or the driver name on DRIVER and LINK statements. Keyword parameters are separated from their arguments by an equal (=) sign, and from other keyword parameters by at least one blank (space) or a comma (,).

• When the acceptable values for a parameter are Y and N (yes and no), any other value is treated as an N, unless there is a documented default, and processing continues without any warning.

• When the acceptable values for a parameter fall within a range (e.g., 1 - 2147483647) and a value outside the range is specified, the value is automatically reset to the maximum value within the range, unless documented otherwise for the parameter. Processing continues without any warning.

• A statement can be continued beginning in any column of the next line by specifying a dash (-) as the last nonblank character in any column of the current line, before column 73.

• Comment lines begin with an asterisk (*) in position 1 and can be inserted anywhere in the statement sequence.

• Some keywords may require a list of subparameters separated by commas; the list must be enclosed in parentheses ( ) unless only the first subparameter is to be entered. Omitted ("defaulted") subparameters must be represented by placeholder commas if subsequent parameters are to be entered. The following are examples of correct subparameter strings:

  KEYWORD=(value1,value2,value3)
  KEYWORD=(value1,,value3)
  KEYWORD=(,,value3)
  KEYWORD=(,value2)
  KEYWORD=value1
  

• Hexadecimal keyword values can be entered by prefixing the value with an "X". For example:

  LINK . . . ADJID=X0064, . . .
  

XCF NODE Statement

Note:
This section describes the NODE statement and parameters for the XCF line driver. For detailed information see the sections XCF DRIVER Statement and XCF LINK Statement.

The NODE statement must be the first Entire Net-Work control statement. It defines the node's name and operating characteristics.

Format

The following is the format of the NODE statement:

Parameters

The NODE statement parameters along with a description of their function and their accepted values and defaults are described in the following sections.

Note:
The underlined portion of the parameter is the minimum abbreviation.

• nodename
• BUFFERS
• CQTIMER
• DEFINE
• DOMAIN
• DUMP
• LOG
• MAXPATH
• MSGFORM
• NID0
• NTRACE
• REPLYTIM
• START
• TIMER
• TRACE | TROFF | TRON
• UCMSG
• ULINK

nodename

A 1-8 character name for this node. The node name must be specified immediately after NODE, separated by at least one blank space. All Entire Net-Work nodes must have unique names. Choose a meaningful name. Entire Net-Work uses the node name when referring to the node for operator messages and when logging.

BUFFERS

The values required depend on the number and types of line drivers and links, and on the message volume; these values can be adjusted according to usage statistics printed at the end of each Entire Net-Work session, or from issuing the operator command "D S" (display statistics).

Specify decimal values for the operands ranging from 0 to 2147483647 bytes; or, optionally, a value followed by either the multiplier "M" (multiply by 1048576) or "K" (multiply by 1024). If followed by "M", the specified value must range from 0 to 2048; if followed by "K", the value must range from 0 to 2097151. If a subparameter is omitted or zero is specified, no corresponding buffer pool will exist for this node. The requested storage space must be available; if the space is not available, Entire Net-Work ends with error message NET0013.

For OS/390 systems, the buffer pool manager initializes the common buffer pool with a subpool of 256K. Additional subpools can be created dynamically, and all subpools can be expanded or contracted as needed. The only size limitation for the buffer pool is the size of the region or partition. The BUFFERS specification on the NODE statement remains the same, even though the first three values (abufsize, ltbufsize, and stbufsize) are ignored by the new buffer pool manager. The fourth value (pfxbufsize) is used to set the size of the page-fixed buffer pool.

where

CQTIMER

Specify a practical decimal value, depending on the node system's environment. The maximum value is approximately 68 years: effectively, no timeout will occur. The default is approximately one minute.

The purpose of the CQTIMER= timeout is to prevent an Entire Net-Work request queue element (RQE) and the attached buffer from becoming irretrievable if the user has ended abnormally. This parameter performs the same function as the ADARUN CT parameter.

Note:
This parameter can be changed during Entire Net-Work operation by the SET CQTIMER= command.

DEFINE

If "Y" is specified, the DEFINE operator command is accepted and executed; "N" (the default) rejects the DEFINE operator command.

DOMAIN

This parameter allows you to subdivide the network into multiple domains. Using domains simplifies network management and limits administrative message traffic.

DUMP

The information is printed to the NETPRNT file if it is open. Otherwise, it is printed to the DDPRINT file. The DUMP parameter can be used to reduce the amount of output generated during an ABEND, especially on large Entire Net-Work systems. This parameter cannot be abbreviated.

where

In general, the default value of ALL should be used so that all diagnostic information is available to Software AG support.

Multiple values can be specified, separated by commas and surrounded by parentheses:

DUMP = (BLOCKS, TRACETAB, FORMAT)

If values conflict, the last value specified is used. 'NONE' is used in the following example:

DUMP = (BLOCKS, TRACETAB, NONE)

Note:
This parameter can be changed during Entire Net-Work operation by the SET DUMP command.

LOG

Normally, logging should not be used because of the extra system resources required. The LOG function is intended primarily as a diagnostic tool: use it only with the assistance of your Software AG technical support representative.

LOG is a test parameter for recording control flow and for logging selected data areas. The information is written to the NETPRNT file if it is open. Otherwise, it is written to the DDPRINT file. It can have the following values:

where

Note:
This parameter can be changed during Entire Net-Work operation by the SET LOG= command.

MAXPATH

The default (4) results in a stack large enough for four en route node IDs.

The Entire Net-Work communicator uses this optional value to build a list of two-byte entries for tracking each message. This list, called a 'node stack', is included in the message header. As the message passes through nodes on the way to its target, each node's ID is added to the stack.

If the specified MAXPATH value results in a node stack that is larger than needed, messages will be unnecessarily long. If the MAXPATH value is too small, Entire Net-Work automatically copies the message, increasing the node stack size; this causes unnecessary processor overhead.

Note:
This parameter can be changed during Entire Net-Work operation by the SET MAXPATH= command.

MSGFORM

where the valid values are

NET0090 BUFFER USAGE STATISTICS

NET0090I: BUFFER USAGE STATISTICS

NET0090I NODE2  : BUFFER USAGE STATISTICS

NET0090I NODE2: BUFFER USAGE STATISTICS

Notes:

1. Individual line drivers may not recognize this parameter.
2. Values between 5 and 255 will be accepted, but they have no meaning and are not valid.
3. This parameter can be changed during Entire Net-Work operation by the SET MSGFORM= command.

NID0

If NID0=Y is specified, all nodes that attempt to connect and are not explicitly defined are assigned a node ID of 0. No Adabas servers on those nodes are broadcast through the network.

NTRACE

Specify a practical decimal value, depending on the node's system configuration. The maximum may be limited by the system. If the default (0) is used, no trace table is allocated for this node and no tracing takes place, whether TRACE= or TRON= is specified or not.

REPLYTIM

A request is considered complete when the originating node receives a reply.

Specify a practical decimal value, depending on the node system's operation. The maximum value is approximately 68 years: effectively, no timeout will occur. The default is approximately one minute.

In the event that a message is "stranded" (that is, a reply cannot be returned to the originating node), REPLYTIM= specifies a time after which a response code 224 is returned to the user.

Note:
This parameter can be changed during Entire Net-Work operation by the SET REPLYTIM= command.

START

The values for START are interpreted as follows:

TIMER

Each time the specified interval expires, Entire Net-Work scans its tables for any time-dependent action that needs to be taken. The TIMER= value determines the precision of all time-dependent Entire Net-Work services.

Specify a practical decimal value depending on the node operation. The maximum value is approximately 68 years: effectively, no timing supervision will occur, even if other timing parameters, such as REPLYTIM, CQTIMER, or ADARUN CT are set.

There is an interaction between TIMER= and other timing parameters. If the TIMER interval is greater than the individual CQTIMER= and REPLYTIM= intervals, the specified action may not be started until the TIMER= interval has expired.

TRACE | TROFF | TRON

Tracing should not be active during normal operation. Tracing is intended as a diagnostic tool; it is recommended that you use tracing only with the assistance of your Software AG technical support representative.

TRACE= and TRON= are synonyms to either start or resume tracing of the specified events. TROFF= stops tracing. If this parameter is not specified, no tracing will occur.

Note that the NTRACE parameter must specify a nonzero value in order to permit tracing.

One or more trace values can be specified. If more than one value is specified, the values must be enclosed in parentheses and separated by commas:

(trace,trace,... )

The value 'trace' can be one or more of the following:

An XCF line driver trace can be requested for installed line drivers on the local node only.

Note:
Values set by this parameter can be changed during Entire Net-Work operation by the SET TRACE=, TROFF=, or TRON=... commands.

UCMSG

Notes:

1. Individual line drivers may not recognize this parameter.
2. This parameter can be changed during Entire Net-Work operation by the SET UCMSG command.

ULINK

The values for ULINK are interpreted as follows:

In networks with many PCs, two PCs may be assigned the same node name and ID by mistake. If both PCs are simultaneously connected to Entire Net-Work, they are perceived as one Entire Net-Work node that is connected by two different links. As a result, one of the PCs may receive a reply to a call that originated on the other PC.

To avoid this type of situation, specify ULINK=YES. When the second PC tries to connect, it is rejected. The integrity of the network is maintained and the duplicate node name and ID can be identified.

Note:
This parameter can be changed during Entire Net-Work operation by the SET ULINK command.

XCF DRIVER Statement

The Entire Net-Work DRIVER control statement defines the line driver type (that is, XCF) to be loaded. Only one DRIVER statement may be specified for a given line driver type.

DRIVER statement parameters are read from a sequential file during system startup, and can be modified after startup using the ALTER operator command. Some parameters can be modified when the line driver is open or closed; others can be modified only when the line driver is closed. See the operator commands ALTER and CLOSE in XCF Line Driver Commands. The open/closed requirement for each parameter is included in its description.

The XCF DRIVER statement and its parameters are used to activate and define the characteristics of the local sysplex node. The access method name 'XCF' or 'XCFD' instructs Entire Net-Work to load the line driver module NETXCF, which must exist in the libraries defined for the related job step.

Note:
The software accepts both XCF and XCFD as the access method name. However, the name used in the DRIVER statement must also be used for the LINK statements.

This section covers the following topics:

• Format

• Parameters

Format

The XCF DRIVER statement has the following format:

where 'XCFD' is the four-character access method name for the XCF driver type:

Parameters

Note:
The underlined portion of the parameter is the minimum abbreviation.

• ACCEPTUI
• GROUP
• LARGEMSG
• PSTATS
• RSTATS
• SMALLMSG
• STATINT
• TRACESIZ

ACCEPTUI

The ACCEPTUI parameter can be modified when the driver is open or closed.

GROUP

All Entire Net-Work nodes in the SYSPLEX must use the same unique XCF group name. The group name must be the same on all Entire Net-Work nodes; it must also be different from the name of any other product or system using XCF. Results are unpredictable if Entire Net-Work nodes are assigned to the same group as other types of systems such as DB2 or CICS. The GROUP parameter specifies the Entire Net-Work group name, which may be defined in the COUPLExx member in SYS1.PARMLIB (see step Modify COUPLExx and the CFRM Policy in the Installation documentation). The GROUP parameter can be modified only when the driver is closed.

LARGEMSG

Any data messages larger than this size are counted as large messages. Any data messages smaller than this size are counted as medium or small messages, depending on the value specified by the SMALLMSG parameter described below.

For example, using the default values for SMALLMSG and LARGEMSG:

• Data messages between 1 and 1024 bytes long are reported as small messages.

• Data messages between 1025 and 8192 bytes long are reported as medium messages.

• Data messages larger than 8192 bytes long are reported as large messages.

PSTATS

This parameter is only used to set the default for all links.

RSTATS

This parameter is only used to set the default for all links.

SMALLMSG

Any data messages smaller than or equal this size are counted as small messages. Any data messages larger than this size are counted as medium or large messages, depending on the value specified by the LARGEMSG parameter described above.

STATINT

This parameter is only used to set the default for all links.

TRACESIZ

The TRACESIZ parameter can be modified when the driver is open or closed.

XCF LINK Statement

The LINK statement is currently not required for the XCF DRIVER statement. During the initialization process, the XCF line driver requests a list of all other members in its XCF group and then, if the DRIVER statement parameter ACCEPTUI=Y is set, logically connects to each member.

Although the LINK statement is optional, it can be added for documentation or security purposes.

Note:
If two or more Entire Net-Work nodes are active in the sysplex within the same group, the Entire Net-Work operator command D L (display links) can be used to display the list of dynamically added links and parameter-defined links.

Each link to another node can be defined with a LINK statement. Each link uses the XCF communications access method as defined on an XCF DRIVER statement. LINK statements specify the XCF driver by name, and follow the XCF DRIVER statement in the Entire Net-Work statement order.

Note:
The software accepts both XCF and XCFD as driver names. However, the name used in the DRIVER statement must also be used for the LINK statements.

The LINK statement parameters are read from a sequential file during system startup, and can be modified after startup using the ALTER operator command. Some parameters can be modified when the link is open or closed; others can be modified only when the link is closed. See the operator commands ALTER and CLOSE in XCF Line Driver Commands. The open/closed requirement for each parameter is included in its description.

• Format

• Parameters

Format

The XCF LINK statement has the following format:

where 'XCFD' is the four-character name of the XCF line driver. The XCF DRIVER statement must precede the LINK statement.

Parameters

Note:
The underlined portion of the parameter is the minimum abbreviation.

• linkname
• PSTATS
• RSTATS
• SAF
• STATINT
• WEIGHT

linkname

This required parameter specifies the name by which this link is to be known; it is a one- to eight-character name identifying the link and must be unique on the node. It is positional and must be specified immediately after the LINK keyword and immediately before the driver name (XCFD).

Note:
If more than 8 characters are entered for linkname, only the first 8 characters are used. The connection is issued correctly and no error message is generated.

PSTATS

The default value is the value of the PSTATS parameter on the DRIVER statement (see XCF DRIVER Statement parameter PSTATS).

RSTATS

The default value is the value of the PSTATS parameter on the DRIVER statement (see XCF DRIVER Statement parameter RSTATS).

SAF

Failure to load the Interface is considered a security violation and Entire Net-Work will shut down. If SAF=L, the calls are traced and the output directed to DDPRINT. An error code is transmitted to the user if access to SAF is denied. The SAF parameter can be modified when the link is open or closed.

STATINT

The default value is the value of the STATINT parameter on the DRIVER statement (XCF DRIVER Statement parameter STATINT).

WEIGHT

If a given target can be reached by more than one path (chain of connected links), the path with the lowest weight is used. Slow or expensive links should be given a higher value than fast or inexpensive links. The WEIGHT parameter can be modified only when the link is closed.

www.softwareag.com

Copyright © 2014 Software AG, Darmstadt, Germany.

SEARCH   INDEX   CONTENTS   |   PDF PAGE   PDF BOOKS   |   HOME   UP   PREV   NEXT