05.02.2013 Views

Chapter 3. Operating NetView FTP V2.2.1 MVS - IBM

Chapter 3. Operating NetView FTP V2.2.1 MVS - IBM

Chapter 3. Operating NetView FTP V2.2.1 MVS - IBM

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Modifying the Maximum Number of Simultaneous Sessions That a<br />

Server Can Handle<br />

You can tell the queue handler to modify the maximum number of simultaneous<br />

sessions that a server can hold, using the MODIFY command. The syntax of the<br />

command is:<br />

►►──┬─MODIFY ─┬──id──┬─,MODIFY<br />

─┬──┬─suffix──┬──,──SRV──=──(avlsess,avllrh,avlrrh)<br />

──►◄<br />

└─F ──────┘<br />

└─,F ──────┘<br />

└─jobname─┘ id The identifier that you used in the START command to start the queue handler.<br />

suffix<br />

The suffix of the server to be modified.<br />

jobname<br />

The job name of the server. This format must be used if the server has not<br />

been started via the queue handler.<br />

avlsess<br />

For SNA file transfers, the maximum number of concurrently active sessions on<br />

the specified server. It can be any numerical value from 0 up to the value<br />

specified in the server MAXSESS initialization parameter. When 0 is specified,<br />

the specified server no longer serves any file-transfer request.<br />

For OSI file transfers, the maximum number of active transfer requests the OSI<br />

server can handle. If the number of available server sessions (that is, FTAM<br />

requests) is less than the maximum number of parallel FTAM sessions, the<br />

request for a file-transfer session from a remote system is handled at the same<br />

time as, and is not blocked by, a locally initiated file transfer.<br />

avllrh<br />

The maximum number of concurrently active local file-transfer requests the<br />

specified server can handle. It can be any numerical value from 0 up to the<br />

value specified by the AVLSESS parameter.<br />

When 0 is specified, this server no longer serves any local file-transfer request.<br />

When the value is equal to the AVLSESS value, the situation could arise where<br />

the server serves only local file-transfer requests and no remote file-transfer<br />

requests.<br />

For an OSI server, this number must be equal to the AVLSESS value because<br />

an OSI server can only handle local transfer requests.<br />

avlrrh<br />

The maximum number of concurrently active remote file-transfer requests that<br />

the specified server can handle. It can be any numerical value from 0 up to the<br />

value specified by the AVLSESS parameter.<br />

When 0 is specified, this server no longer serves any remote file-transfer<br />

request. When the value is equal to the AVLSESS value, the situation could<br />

arise that the server serves only remote file-transfer requests and no local filetransfer<br />

requests.<br />

For an OSI server, this number must be set to zero because an OSI server can<br />

only handle local transfer requests.<br />

<strong>Chapter</strong> <strong>3.</strong> <strong>Operating</strong> <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong> 57

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

Saved successfully!

Ooh no, something went wrong!