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.

7. After the queue handler finds a request that it can pass to the server, it checks<br />

whether the request specifies the LU name of a single server or the name of a<br />

server group. If the request specifies the name of a server group, the queue<br />

handler retrieves the following information from the server group table and<br />

inserts it into the request:<br />

� The LU names of the first eight servers in the server group that have the<br />

running mode specified in the request.<br />

� The number of servers in the group whose LU names were not inserted.<br />

Note: Point 7 does not apply to OSI file transfers.<br />

8. The queue handler passes the request to the server. The request’s status is<br />

changed to active.<br />

Transferring a File<br />

The following describes how a file is transferred using an SNA server and an OSI<br />

server.<br />

SNA Server<br />

A file is transferred by an SNA server as follows:<br />

1. After the local server obtains a request from the queue handler, it attempts to<br />

allocate a conversation with the first server listed in the server group specified<br />

in the request.<br />

If an LU name is specified, the server tries to allocate a conversation only with<br />

the server represented by this LU name. (If the LU name of a single server<br />

was specified, then this server is the only one listed in the request.)<br />

Note that for <strong>NetView</strong> <strong>FTP</strong>/2 and <strong>NetView</strong> <strong>FTP</strong> AIX the server group must not<br />

contain more than one LU name, as a group of <strong>NetView</strong> <strong>FTP</strong> Client programs<br />

is represented by the LU name of the <strong>NetView</strong> <strong>FTP</strong> Server workstation to which<br />

they are attached.<br />

2. If the server at the remote location (the remote server) accepts the conversation<br />

parameters, the conversation is established and the server proceeds with<br />

step <strong>3.</strong><br />

If the remote server does not accept the conversation parameters, the local<br />

server tries to establish a conversation with the next server listed in the server<br />

group specified in the request. It continues trying until it either succeeds in<br />

establishing a conversation or has tried to establish a conversation with all the<br />

servers listed in the server group specified in the request.<br />

If there are more LUs in the server group than the ones already tried, the<br />

server tells the queue handler to retrieve the names of up to eight LUs. The<br />

server repeats this process until it either succeeds in establishing a conversation<br />

or has tried all the LU names associated with the server group.<br />

After it has tried all the servers in the group without success, the local server<br />

notifies the queue handler and tells it to place the request back into the queue,<br />

leave it in waiting status, and set its not-before time to the current time plus the<br />

time specified in the server’s REQDELAY initialization parameter. This parameter<br />

is described in “Specifying Values for the Server Initialization Parameters”<br />

on page 11<strong>3.</strong><br />

8 <strong>NetView</strong> <strong>FTP</strong> V2 <strong>MVS</strong> Installation, Operation, and Administration

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

Saved successfully!

Ooh no, something went wrong!