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.

Description of the Symptom Record<br />

The queue handler and servers issue the symptom record if either of the following<br />

occurs:<br />

� An internal trace is performed<br />

� An abnormal termination occurs and a <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong> recovery<br />

routine gets scheduled by the recovery termination manager.<br />

<strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong> uses the IDUMP macroinstruction to issue the symptom<br />

record.<br />

The startup job or procedure for the queue handler or a server must have a DD<br />

statement with the name DVGSNAP.<br />

For more information about specifying the DD statement for the queue handler and<br />

a server refer to “DVGSNAP” on page 97.<br />

The symptom record for an internal trace is described in “The <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong><br />

<strong>MVS</strong> Symptom Record as Trace Output” on page 145.<br />

If there is an abnormal termination, <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong> can produce the<br />

symptom record only if the following conditions are met:<br />

� <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong> has reached a point in its processing where it has<br />

established its ESTAE recovery routines. This happens at the end of its initialization<br />

processing. Therefore, if an abnormal termination should occur during<br />

the initialization phase of the queue handler or a server, no symptom record is<br />

issued.<br />

� No error occurs that prevents the ESTAE recovery routines from working as<br />

designed. The following error situations can prevent a symptom record from<br />

being issued:<br />

– Another abnormal termination occurs during the processing of the ESTAE<br />

recovery routines<br />

– An I/O error on the SNAP dump data set occurs.<br />

Note: Some of the symptom record fields are not filled if <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong><br />

<strong>MVS</strong> cannot retrieve the related information during its error handling. This is true,<br />

for example, if the operating system’s recovery termination manager cannot set up<br />

a system diagnostic work area (SDWA).<br />

When you read a dump with the symptom record you only have to pay attention to<br />

the translated section of the dump. You can normally find this on the right-hand<br />

side of the hexadecimal dump. <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong> has already translated<br />

all addresses and binary variables, so that you can easily read them in the translated<br />

section.<br />

Refer to “The <strong>NetView</strong> <strong>FTP</strong> <strong>V2.2.1</strong> <strong>MVS</strong> Symptom Record as Trace Output” on<br />

page 145 for an example of a symptom record.<br />

174 <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!