16.12.2012 Views

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

configstk<br />

Examples<br />

number specified is be distributed equally among the read and write<br />

flows. As new ESCON ®<br />

fibers are added to the configuration,<br />

additional IO buffers are required. Thruput decreases and overhead<br />

increases if the number specified is too restrictive. You should<br />

initially specify a value of 10 times the number of defined gateways<br />

for low-to-average use and increase it proportionally as the number<br />

of users increase). The maximum number of buffers allocated is the<br />

larger of six times the number of active gateways, or the number<br />

specified. A decrease in the number is not honored until the next<br />

IPL.<br />

blocking<br />

Indicates whether the internal blocking algorithm should be<br />

activated for outgoing packets. The default is BLOCKING.<br />

Specifying NOBLOCKING causes the internal optimization routines,<br />

which attempt to group multiple packets into a single blocked I/O, to<br />

be bypassed (such as single packet per block written on demand).<br />

Specifying BLOCKING minimizes the z/<strong>OS</strong> overhead and<br />

maximizes the ESCON channel bandwidth, but can delay the<br />

packet delivery slightly.<br />

GATEWAY device_number checksum<br />

At least one of these statements is required and up to 32 can be specified.<br />

The entire statement must be on a single line. This statement maps the<br />

target RS/6K IP addresses to the gateway that will process the request. The<br />

device number to define the gateway must be the first of an even-odd pair<br />

of subchannels (both configured thru a single ESCON fiber) between the<br />

z/<strong>OS</strong> image and the RS/6K gateway. Multiple target IP addresses can be<br />

mapped to a given gateway. A given target IP address can be mapped to at<br />

most one gateway.<br />

device_number<br />

Specifies the hex address of device to be configured. This number<br />

must be four hex digits and must be an even number.<br />

checksum<br />

Indicates whether a reliable communications path exists between<br />

the communicating applications. Specify CHECKSUM if any portion<br />

of the path between the communicating applications is unreliable<br />

(such as a LAN). Specify NOCHECKSUM if the entire path is<br />

reliable (such as a SP2 ®<br />

fast switch or ESCON).<br />

A list of IP addresses immediately follows this statement, one IP address<br />

per line. At least one IP address must be specified for each gateway<br />

device. Up to 256 IP addresses can be specified in the configuration file.<br />

Blank lines are permitted and lines beginning with /* are treated as<br />

comments.<br />

/* configure AF_UEINT sockets<br />

/* name the ip address for this node, default to blocking enabled<br />

home 10.32.166.20 buffers(20)<br />

/* configure device 324<br />

gateway 0324 nochecksum<br />

10.34.166.20<br />

10.34.166.24<br />

10.34.166.26<br />

148 z/<strong>OS</strong> <strong>V1R9.0</strong> <strong>UNIX</strong> <strong>System</strong> <strong>Services</strong> <strong>Command</strong> Reference

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!