Test 1 Common Communications Adapter (CCA) Log for BSC

This host attachment log format is returned to the request-ing 3278 in response to an AOll entry. The format detail assigned a specific meaning. See the following example for byte identification:

Byte 1 information does not pertain to a 500 series communica-tion check and is to be considered machine-check data.

The next byte to the right of NN is F F. This byte repre-sents the type of operation being attempted at the time of the failure. Refer to the CCA BSC Operation Attempted Chart (Figure 3-2) when FF is to be used.

The next two bytes to the right of F F are labeled CCCC.

These two bytes indicate how the attempted operation ended. See the CCA BSC Operation Ending Chart (Fig-ure 3-3) to determine if the operation was completed (1) normally, (2) with exception, or (3) with error.

The next five bytes to the right of CCCC are labeled SSSS. These five bytes contain sense information recorded at the time of the failure. After you have examined NN, FF, and CCCC, the SSSS bytes should give you some indi-cation as to why the nnn code was generated and why the operation attempted was not completed normally.

All bytes labeled XXXX are not used.

• Line 3 - This line displays the statistical counter infor-mation associated with this adapter. If no errors are recorded for this adapter, the coun-ters display as follows:

0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 The counters are not numbered when they are displayed.

They are, however, assigned counter position numbers. The leftmost two-digit position is counter number 01, and the rightmost counter position used is counter number 11. The remaining positions are not used. The value in each counter is given in hexadecimal. The maximum value for any coun-ter is FF.

Each counter is assigned a specific meaning, as follows:

Counter Meaning

01 NAK sent

02 NAK received

03 Enq received

04 Timeout invalid

05 15 NA Ks received

06 15 Wrong ACKs (ACK 0 instead of ACK 1, ^etc.) 07 Underruns/overruns

08 Write timeout

09 DCE error

10 Number of Available Buffers Exceeded

A complete log display for this adapter would appear as follows:

AO/1

0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000

FF FF

Code Operation Attempted Code Operation Attempted

00 Enable/Set Mode 14 Disable

01 Hardware Sense 16 STX/ETX Nonconversational

02 SOH/ETX Conversational Resp 18 Write WACK

03 Read Normal 1A STX/ETB Con v Response

06 SOH/ETX Nonconversational 1E STX/ETB Nonconversational

07 Read-Respond RVI 40 Monitor line

OA SOH/ETB Conv Response 46 SOH/ETX Expect Conv Resp OE SOH/ETB Nonconversational 56 STX/ETX Expect Conv Resp

10 Write EOT 58 Monitor line-Respond WACK

12 STX/ETX Conv Response

Figure 3-2. CCA BSC Operation Attempted Chart (Code FF)

Bits shown as 0 are not used unless specified otherwise.

Operation Attempted 00 Enable/Set Mode

Left CC Byte (Completion)

Right CC Byte (Detail)

Bit 0 2 3 4 5 6 7 Bit 0 2 3 4 5 6 7

Normal Completion

o

0 0 0 0 0 0 0 0 0

o

^{0 0 0}

RVI---~

Error Completion 0 0 0 0 1 1 0 0 0 1 0 0

Halted - - - '

I

^{I I}

Over/Underrun ---~

Invalid Basic Status ----~

DCE---~-Machine Check ---~

Exception Completion

o

0 0 0 0 0 1 0 o

o

0 0 0 0 0

Timeout ---~

01 Hardware Sense

Normal Completion 0 0 0 0 1 0 0 0

o

0 0 0 0 0 0 0

(No error or exception condition allowed) 02 SOH/ETX Conversational Response 03 Read Normal

06 SOH/ETX Nonconversational 07 Read and Respond RVI Normal Completion

STX=O

0 0 0 0 1 0 0 0

o o

0 0 0 0

SOH=1 ---~

ETX=O

ETB=1 ---~

Error Completion 0 0 0 0 1 1 0 0 0 1 1 0

Write=O _ _ _ _Read=1

---I1 I

^{I I}

Halted - - - ' Underrun/Overrun

Invalid Basic Status ---~

DCE ---~

Machine Check ---~

Timeout---~

Exception Completion 1 0 0 0 0 1 0 1 0

o

⁰

o

EOT R e c e i v e d - - - ' CountExceeded---~

o

⁰

Disc---~

Figure 3-3 (Part 1 of 4). CCA SSC Operation Ending Chart (Code CCCC)

Operation Attempted

Left CC Byte Right CC Byte

(Completion) (Detail)

Bit 0 2 3 4 5 6 7 Bit 0 2 3 4 5 6 7

Exception Completion 2 0 0 0 0 0 0 0 0 1

N Timeouts Invalid

I I I I

ITB Attention EOH Attention Transparency NAK Sent TTD Received 15 ENOs Received

OA SDH/ETB Conversational Response OE SDH/ETB Nonconversational

10 Write EDT

Normal Completion 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Error Completion 0 0 0 0 0 0 0 0 1 0

Underrun

I I I

Invalid Basic Status DCE

Machine Check Timeout

(Exception completion not valid for Write EDT) 12 STX/ETX Conversational Response 14 Disable

Normal Completion 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Error Completion 0 0 0 0 0 0 0 0 0 0 0

Invalid Basic Status DCE

Machine Check

(Exception completion not valid for Disable) 16 ·STX/ETX Nonconversational

18 Write WACK

Normal Completion 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Error Completion 0 0 0 0 0 0 1 0

Write=O

I I I

Read=1 Halted

Underrun/Dverrun Invalid Basic Status DCE

Machine Check Timeout

Figure 3-3 (Part 2 of 4). CCA BSC Operation Ending Chart (Code CCCC)

Operation Attempted

Left CC Byte (Completion)

Right CC Byte (Detail)

Bit

o

2 3 4 5 6 7 Bit 0 2 3 4 5 6 7

Exception Completion

o

0 0 0

o o o

0

o

0 0 0

EOT Received - - - -_ _ _ _ _ _ _ _ _ _ _ _ _ ~

Disc - - - -_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ - - J

1 A STX/ETB Conversational Response 1 E STX/ETB Nonconversational 40 Monitor Line

Normal Completion PolI=1

Select=O

0 0 0 0 1 0 0 0

o

0 0 0 0 0 0

Error Completion 0 0 0 0 1 1 0 0 0 1 0

Halted

I III

Overrun - - - -_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ --J

~~~lidBasicStatus---MachineCheck---~.

Timeouts---~

46 SOH/ETX Expect Conversational Response 56 STX/ETX Expect Conversational Response

FF codes 02 through 56 listed above use the following completion/detail.

Normal Completion

o

0 0 0 1 0 0 0

o

STX=O _______________________________________________ ^~ SOH=1

ETX=O _________________________________________________ ^~ ETB=1

Error Completion 0 0 0 0 1 1 0 0 1

o

0 0 0 0

Write=O

I

^{I I}

Read=1 Halted _______________________________________ - - J

~~~~i~~n:S~cv;~~~:s

DCE

Machine Check - - - '

Timeout ---~

Invalid Data - - - '

Exception Completion 1 0 0 0 0 1 0 1 0 0 1

1 5 T i m e o u t s l n v a l i d - - - J I I I I

EOT Received

---...j

RV I Received - - - '

Count Received ---~

15 NAKs Received

15 Wrong AC Ks

---1

Disc

Figure 3-3 (Part 3 of 4). CCA BSC Operation Ending Chart (Code CCCC)

Operation Attempted

Left CC Byte (Completion)

Right CC Byte (Detail)

Bit 0 2 3 4 5 6 7 Bit 0 2 3 4 5 6 7

Exception Completion 2 WACK Received

o

0 0 0 0 0

o o

0 0 0 0

NAK Received - - - '

Exception Completion 3 0 0 0 0 0 0 1 0 0 1

15Timeoutslnv_alid ITB Attention _ _

---'1111

EOH Attention

Transparency - - - ' NAK Sent

TTD Received

o

15 ENOs R e c e i v e d - - - -...

58 Monitor Line Respond WACK

FF Codes 44 through 58 use the following completion detail.

Normal Completion PolI=l

Select=O Error Completion

0 0 0 0 1 0 0 0

o

0 0 0 1 1 0 0

o

0 0 0

Write=O

I

^{I I}

Read=l - - - ' Halted - - - ' Underrun/Overrun

Invalid Basic Status - - - ' . DCE---~

Machine Check

0 0 0

1 0

Timeout - - - -____ ~

Exception Completion 0 0 0 0 0 0 1 0

o o

0 0 0 0 0

One Timeout Invalid _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ - - - J

Figure 3-3 (Part 4 of 4). CCA SSC Operation Ending Chart (Code CCCC)

Figure 3-4 explains the sense-byte breakdown for CCA BSC. These conditions are logged only for nnn codes 311, 501,530, 535, and 536, and the last error condition of that type. Select Half Speed New Sync

DCE Interrupt Disable Overrun

**Should always be zero

Figure 3-4. Sense Byte Breakdown Chart for CCA BSC (Code SSSS)

3.3.4 Test 1 Common Communications Adapter (CCA) Log and High-Performance Communi-cations Adapter (HPCA) Log for SDLC This host adapter log format is identical for both adapters

error conditions. These conditions are asso-ciated with nnn codes 501, 502, 529, 530, or 321 (see Appendix B for details). Code 321 will be indicated in this line as NN=OO and the remainder of Line 2 will be not equal to O.

Each byte is assigned a specific meaning. See the following example for byte identification:

Byte 24 0000 0000 0000 0000 0000 0000 0000 » 0000 NNFF CCCC SSSS SSSS SSSS SSXX

xxxx( (xxxx

NN - This code represents the two low-order digits of any 500 series nnn number in almost all cases.

FF - This byte represents the type of operation being attempted at the time of the failure. Refer to the

CCA/HPCA Operation Attempted Chart (Figure 3-5) when FF is to be used.

Figure 3-5. CCA/HPCA SDLC Operation Attempted Chart (Code FF)

CCCC - These two bytes indicate how the attempted operation ended. See the CCA/HPCA Operation Ending Chart (Figure 3-6) to determine if the operation was com-pleted (1) normally, (2) with error, or (3) with exception.

SSSS - These seven bytes contain sense information recorded at the time of the failure. After examining NN, FF, and CCCC, the SSSS bytes should give you some indi-cation as to why the nnn code was generated and why the operation attempted was not completed normally.

XXXX - All bytes labeled XXXX are not used in the CCA and should be ignored for the HPCA, since these bytes contain secondary levels of information, which are not associated with the problem.

• Line 3 - This line displays the statistical counter infor-mation associated with these adapters. If no errors are recorded for these adapters, the counters wi" display as follows:

0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 The counters are not numbered when they are displayed.

They are, however, assigned counter position numbers.

The leftmost two-digit position is counter number 01, and the rightmost counter position used is counter number 12.

The remaining positions are not used. The value in each counter is given in hexadecimal. The maximum value for any counter is F F.

Each counter is assigned a specific meaning, as follows:

Counter Meaning nnn Code (App B)

01 Nonproductive Timeout 520

02 Idle Timeout 521

The error to nnn code and counter relationship is shown below:

The following descriptions of conditions wi" help you analyze the logs: received from the host.

SNRM Received - A Set Normal Response Mode sequence has been received from the host. An existing session wi" be terminated, and a new session may be established.

Underrun - The 3274 controller was not ready to transmit a byte of data at the time the transmission line was ready to receive.

Connection Problem - 20 consecutive occurrences of any of the following: ROL, FRMR, XID, NSA.

FCS Error - The 3274 controller detected an SDLC frame with an invalid block check character (BCC) or a frame-check sequence.

Primary Abort - The 3274 detected an abort message from the primary station.

Lost Data - An I-frame received by the 3274 was larger than the allocated buffer.

Write Timeout - A transmission of data took longer than expected and is suspected to be a result of a hardware function.

Dump Message - Addition status is contained in the regis-ter space that will indicate one of the following:

• FCS Error primary station because the 3274 does not have sufficient buffers (receive). Disconnect command was received from the primary station. The 3274 will go to normal disconnect (NDM) detected on the host link for 20 seconds.

Ring Indicate Timeout - A switched connection has not been detected in a 3-second period.

Ring Indicate - A switched connection has been made.

Invalid Basic Status - An adapter hardware register con-tains data that was not meaningful.

DCE Error - A modem problem has been detected.

CNFG - A valid Configure command was received and the appropriate action is being taken by the adapter microcode.

No R LSD - R LSD has been inoperative for at least 3274 did not allow the adapter to cycle share.

A complete log display for this adapter would appear as shown below:

AO/1

0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000

Right CC Byte

I nvalid Basic Status

I _I

Im Dokument = == ';' == Maintenance Library (Seite 35-43)