Snacfg Mode

Purpose Allows you add, delete, modify, or view an APPC mode. Also allows you to view the command that would create a specified mode.

Note Configuration settings specified with snacfg mode correspond to APPC mode settings configured with SNA Server Manager. Syntax snacfg [#configpath] mode /list
snacfg [#configpath] mode modename
snacfg [#configpath] mode modename /add [options]
snacfg [#configpath] mode modename [options]
snacfg [#configpath] mode modename /delete
snacfg [#configpath] mode modename /print

where

#configpath: Specifies the path of the configuration file to view or change. If the configuration path is omitted, SNA Server will attempt to access the configuration file on the local system, using the path \SNAServerRoot\SYSTEM\CONFIG\COM.CFG, where SNAServerRoot is the SNA Server root directory.
/list: Generates a list of configured modes.
modename: Specifies the name of the mode on which to carry out actions. A mode name can be from one through eight characters long, and can contain alphanumeric characters and the special characters $, #, and @. Lowercase letters are converted to uppercase. The mode name cannot be the same as any other mode name in the subdomain of the server.
If no options are specified after modename, the configuration settings for the specified mode are displayed.
/add: Adds a mode called modename. To configure the mode, either specify other options after /add, or specify configuration options in additional snacfg mode commands (using the same modename).
/delete: Deletes modename.
/print: Causes the display of the snacfg command that would create the specified mode. The displayed command does not contain the word snacfg so that it can be redirected to a command file. See the information about command files earlier in this chapter.
options: Are as shown in the following list.

Options for APPC Modes

/comment:"text": Adds an optional comment for the mode. The comment can contain as many as 25 characters; enclose the comment in quotes.
/sessionlim:value: Specifies the parallel session limit.
The range is from 1 through 254. If no parallel session limit has been specified, the default is 1.
/conwin:value: Specifies the minimum contention winner limit.
The range is from 0 through the parallel session limit. If no minimum contention winner limit has been specified, the default is 0.
/conlose:value: Specifies the partner minimum contention winner limit.
The range is from 0 through the parallel session limit. If no partner minimum contention winner limit has been specified, the default is 0.
/autoact:value: Specifies the automatic activation limit.
The range is from 0 through the minimum contention winner limit.
/autopartner: { yes | no }: Specifies whether this mode will be used in automatic partnering of APPC LUs.
If automatic partnering is left unspecified, the default is yes.
/highpriority: { yes | no }: Specifies whether communication with this mode will be given preference over low-priority communication.
If the high-priority setting is left unspecified, the default is yes.
/pacesendcnt:value: Specifies the pacing send count. A value of 0 represents an unlimited number of frames.
The range is from 0 through 63. If no pacing send count has been specified, the default is 4.
/pacerecvcnt:value: Specifies the pacing receive count. A value of 0 represents an unlimited number of frames.
The range is from 0 through 63. If no pacing receive count has been specified, the default is 4.
/maxsendru:value: Specifies the maximum size for RUs sent by the TP(s) on the local system.
The range is from 256 through 16384. If no maximum send RU size has been specified, the default is 1024.
/maxrecvru:value: Specifies the maximum size for RUs received from the TP(s) on the remote system.
The range is from 256 through 16384. If no maximum receive RU size has been specified, the default is 1024.
/maxsendcomp: {none | RLE | LZ9}: These options offer progressively better compression, but at a progressively higher CPU usage cost.
/maxrecvcomp: {none | RLE | LZ9}: These options offer progressively better compression, but at a progressively higher CPU usage cost.
/allowcomp: {yes | no}: If LZ9 is used, this option controls whether data is compressed using RLE before being further compressed using LZ9.
/endpointcomp: {yes | no}: This option controls whether intermediate nodes may use compression if one of the endpoints does not support compression or does not wish to use it.