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

Create successful ePaper yourself

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

The ESTAE Recovery Routine of a Queue Handler Service Subtask<br />

This recovery routine is implemented in module DVGMQFUN. It performs the following<br />

steps:<br />

1. The FSB is flagged so that this specific subtask remains nondispatchable for<br />

the rest of the queue handler’s processing. Another flag, which indicates that<br />

the queue handler has entered the state of immediate termination, is set.<br />

2. The <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong> symptom record is set up and dumped via a<br />

SNAP macroinstruction.<br />

<strong>3.</strong> The following storage areas are dumped via a SNAP macroinstruction:<br />

� FSB and FSBX<br />

� Queue handler global control block (QHCB)<br />

� Request vector table<br />

� Request queue directory<br />

� Server table<br />

� Server group table.<br />

4. A storage dump is produced via a SNAP macroinstruction using the following<br />

parameters:<br />

PDATA All<br />

SDATA LSQA, SWA, CB, TRT, DM, ERR, IO, Q.<br />

5. A message indicating the abnormal termination event is issued.<br />

6. The address space that waits for the completion of the queue handler<br />

command is told that the queue handler command has terminated.<br />

The return and reason code for the queue handler command reflects the<br />

abnormal termination situation.<br />

7. All held locks are released.<br />

8. The buffers for checkpoint data-set processing are released.<br />

9. If no SNAP dump can be issued, a system dump is requested with the<br />

DUMP=YES option of the SETRP macroinstruction. Otherwise, no system<br />

dump is requested.<br />

Note: The main task of the queue handler treats a termination of one of its subtasks<br />

as an error situation. It processes this situation as if the operator had<br />

stopped the queue handler using the operator interface routine.<br />

Abnormal Termination of a Server<br />

The processing in case of abnormal termination of an SNA server depends on<br />

whether the error occurred during the processing in the server’s main task or in one<br />

of its transferring subtasks. However, because the SVC routine is part of the<br />

server, its ESTAE routine may get control.<br />

Because of the restrictions placed on the SVC, its ESTAE does not attempt to<br />

recover the error. It performs basic cleanup functions and then passes control to<br />

the RTM. The server main task controls all processing of the server. It also processes<br />

the scheduling of file-transfer requests. The server subtasks perform the file<br />

transfer. What occurs in the case of an abnormal termination of an OSI server is<br />

described in “Recovery of an OSI Server” on page 160.<br />

<strong>Chapter</strong> 1<strong>3.</strong> Handling <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong> Abnormal Terminations 157

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

Saved successfully!

Ooh no, something went wrong!