Copyright: Reference
Citation: Reference


Microsoft SNA Server Master Table of Contents
Microsoft SNA Server

Master Table of Contents

	SNA Server Enhancements Guide
	SNA Server Installation Guide
	SNA Server Administration Guide
	Managing Microsoft SNA Server
	SNA Server Planning Guide
	SNA Server TN3270 Service
	3270/5250 Applet User's Guide
	SNA Server Reference
	SNA Server Glossary
	APPC Programmer's Guide
	CPI-C Programmer's Guide
	LUA Programmer's Guide
	SNA Device Interface Specification
	3270 Emulator Interface Specification
	Comprehensive Index


Reference Contents
Microsoft SNA Server

Reference

Contents

Before You Begin

Chapter 1	SNA Support

Chapter 2	Network Management

Chapter 3	Error Messages

Appendix A	Sample Host Definitions

Appendix B	Program Check Codes and Sense Codes

Appendix C	Registry and Environment Variables for SNA Server

Appendix D	Details of the Installation Process

List of Tables


Reference Contents
Microsoft SNA Server

Reference

Contents

Before You Begin

How to Use This Guide

Document Conventions

Common Abbreviations

Finding Further Information

Chapter 1	SNA Support

Chapter 2	Network Management

Chapter 3	Error Messages

Appendix A	Sample Host Definitions

Appendix B	Program Check Codes and Sense Codes

Appendix C	Registry and Environment Variables for SNA Server

Appendix D	Details of the Installation Process

List of Tables


Reference Contents
Microsoft SNA Server

Reference

Contents

Before You Begin

Chapter 1	SNA Support

SNA Session Support

LU Support

Session Support

Command Request Support

Transmission Service and Function Management Profiles

TS Profile 1

TS Profile 2

TS Profile 3

TS Profile 4

TS Profile 7

FM Profile 0

FM Profile 2

FM Profile 3

FM Profile 4

FM Profile 7

FM Profile 18

FM Profile 19

Option Set Support

SNA Sense Codes

Request Reject (Category X'08')

Request Errors (Category X'10')

State Errors (Category X'20')

RH Usage Errors (Category X'40')

Path Errors (Category X'80')

LUSTAT Sense Codes

Sense Data Specific to LU Type 6.2

Chapter 2	Network Management

Chapter 3	Error Messages

Appendix A	Sample Host Definitions

Appendix B	Program Check Codes and Sense Codes

Appendix C	Registry and Environment Variables for SNA Server

Appendix D	Details of the Installation Process

List of Tables


Reference Contents
Microsoft SNA Server

Reference

Contents

Before You Begin

Chapter 1	SNA Support

Chapter 2	Network Management

Connections Used for NetView and RTM

Link Alerts for SDLC and Token Ring

Link Alert Format and Common Subvectors

SDLC Failure Alerts

SDLC Alert Local Logging

Identifying Alerts from Local Logs Only

Token Ring Failure Alerts

Link Statistics

Format for Link Statistics

SDLC Link Statistics

Token Ring Link Statistics

Alerts Used by Applications, NVAlert, and NVRunCmd

Format for Alerts Used by Applications, NVAlert, and NVRunCmd

Added Headers and Subvectors

Response Time Monitor

Collecting RTM Data and Sending it to the Host

Boundaries and Measurement Definition

Local Display

Reuse of LUs by Different Users

Host Modification of RTM Parameters

Lost-Data Indicator

Local Logging of Network Management Data

Chapter 3	Error Messages

Appendix A	Sample Host Definitions

Appendix B	Program Check Codes and Sense Codes

Appendix C	Registry and Environment Variables for SNA Server

Appendix D	Details of the Installation Process

List of Tables


Reference Contents
Microsoft SNA Server

Reference

Contents

Before You Begin

Chapter 1	SNA Support

Chapter 2	Network Management

Chapter 3	Error Messages

Appendix A	Sample Host Definitions

VTAM Sample Definitions for 3270

Token Ring Definition

SDLC Definition (for Switched and Leased Lines)

X.25 Definition

CICS and VTAM Sample Definitions for LU 6.2

CICS Tables

Terminal Control Table

Program Control Table

Program Processing Table

VTAM Definitions

TP Coding Requirements

Appendix B	Program Check Codes and Sense Codes

Appendix C	Registry and Environment Variables for SNA Server

Appendix D	Details of the Installation Process

List of Tables


Reference Contents
Microsoft SNA Server

Reference

Contents

Before You Begin

Chapter 1	SNA Support

Chapter 2	Network Management

Chapter 3	Error Messages

Appendix A	Sample Host Definitions

Appendix B	Program Check Codes and Sense Codes

Program Check Codes

Sense Codes

Appendix C	Registry and Environment Variables for SNA Server

Appendix D	Details of the Installation Process

List of Tables


Reference Contents
Microsoft SNA Server

Reference

Contents

Before You Begin

Chapter 1	SNA Support

Chapter 2	Network Management

Chapter 3	Error Messages

Appendix A	Sample Host Definitions

Appendix B	Program Check Codes and Sense Codes

Appendix C	Registry and Environment Variables for SNA Server

Setting Variables on Different Operating Systems

Lists of Available Variables

Registry Variables Used Only on an SNA Server

SnaServer Service: Location and Names of Variables

SnaBase Service: Location and Name of Variables

DLC (802.2) Link Service: Location and Name of Variable

X.25 Link Service: Location and Name of Variable

Registry Variables Used on an SNA Server or a Windows NT-Based Client

TraceWithTime and Milliseconds

APPC API: Location and Name of Variable

CPI-C API: Location and Names of Variables

CSV API: Location and Names of Variables

LUA API: Location and Name of Variable

SnaBase: Location and Names of Variables

Lan Manager Workstation: Location and Name of Variable

Environment Variables Used on Clients Running Windows Version 3.x, MS-DOS, or OS/2

APPC API

CPI-C API

CSV API

LUA API

SnaBase

Variables for Clients Not Running Microsoft Networking

For Clients Running Windows version 3.x

For Clients Running MS-DOS

Variable for Windows-Based Clients Running the 3270 Applet

Appendix D	Details of the Installation Process

List of Tables


Reference Contents
Microsoft SNA Server

Reference

Contents

Before You Begin

Chapter 1	SNA Support

Chapter 2	Network Management

Chapter 3	Error Messages

Appendix A	Sample Host Definitions

Appendix B	Program Check Codes and Sense Codes

Appendix C	Registry and Environment Variables for SNA Server

Appendix D	Details of the Installation Process

Directory Tree Created by Setup

Shares Created by Setup

Registry Keys Created by Setup

Keys Created for Core Software Components

Keys Created for Link Services

List of Tables


Reference Contents
Microsoft SNA Server

Reference

Contents

Before You Begin

Chapter 1	SNA Support

Chapter 2	Network Management

Chapter 3	Error Messages

Appendix A	Sample Host Definitions

Appendix B	Program Check Codes and Sense Codes

Appendix C	Registry and Environment Variables for SNA Server

Appendix D	Details of the Installation Process

List of Tables

SNA Request Support for Session Control Requests

SNA Request Support for Function Management Data Requests

SNA Request Support for Data Flow Control Requests

TS and FM Profiles Supported in SNA Server Sessions

Supported Options for Bind Requests from Primary LUs

Supported Options for Bind Requests from Secondary LUs

Supported Common Protocol Values for Bind Requests from Any LU

SNA Server Option Set Support

Link Alert Subvectors

Hierarchy/Resource List Subvector

Hierarchy/Name List Subvector

Date/Time Subvector Alerts

Product Set ID Subvector

LAN Link Connection Subsystem Data Subvector

Link Connection Subsystem Configuration Data Subvector

Link Station Data Subvector

Basic Alert Subvector

Generic Alert Subvector

Probable Cause Subvector

User Causes Subvector

Install Cause Subvector

Failure Cause Subvector

Detail Qualifier (Hexadecimal) Subvector

Write Timeout Alert

Abnormal Modem Response Alert

DSR Failure Alert

DCD Failure Alert

Invalid Frame Received: I-Field Not Permitted Alert

Invalid Frame Received: Invalid/Unsupported CMD/RSP Alert

Invalid Frame Received: Invalid N(R) Received Alert

RIM/RD Received Alert

Invalid Frame Received: Max I-Field Length Exceeded Alert

FRMR Received: No Reason Given Alert

FRMR Received: I-Field Received When Not Permitted

FRMR Received: Invalid/Unsupported Command or Response Alert

FRMR Received: Max I-Field Length Exceeded Alert

FRMR Received: Invalid N(R) Sent Alert

DISK/SNRM Received: SNRM Received in NRM Alert

CTS Failure Alert

Connection Problem: XID Retransmission Alert

Idle Timeout Alert

Poll Count Exhausted Alert

Remote Busy Retry Alert

DM Received in Information Transfer Alert

Nonproductive Receive Timeout Alert

DISK/SNRM Received: Disk Received Alert

Connection Problem: I-Frame Retransmission Alert

SDLC Outage Codes

Adapter Check Error: Adapter Error Alert

DLC Status Error: FRMR Sent-Invalid N(R) Received

DLC Status Error: FRMR Sent-Received I-Field Exceeded Maximum Length Alert

DLC Status Error: FRMR Sent-Invalid/Unsupported Command/Response Received Alert

DLC Status Error: FRMR Sent-I-Field Received When Not Permitted Alert

Adapter Command Error: Software Alert

DLC Status Error: DM or Disk Received Alert

DLC Status Error: FRMR Received-Invalid N(R) Sent Alert

DLC Status Error: FRMR Received-Max I-Field Length

DLC Status Error: FRMR Received-Invalid/Unsupported Commands/Response Sent Alert

DLC Status Error: FRMR Received-I-Field Sent When Not Permitted Alert

Software Program Error: Adapter Interface Alert

DLC Status Error: SABME Received for Open Link Station Alert

Bring-Up Error Alert

Adapter Open Error: Open Failure Alert

Adapter Open Error: Remove Command Received Alert

Adapter Open Error: Problem on Local Lobe Alert

Adapter Open Error: Beaconing Detected Alert

Adapter Open Error: Duplicate Address Alert

System Action: Operator Caused LAN Adapter to Be Reset Alert

Network Status Error: Lobe Wire Fault Alert

Network Status Error: Auto-Removal Alert

Network Status Error: Token Ring Remove Adapter Command Received Alert

Network Status Error: LLC Remove Adapter Command Received Alert

DLC Status Error: Link Lost Alert

DLC Error: Remote Station Not On Local or Attached Rings Alert

Adapter Command Error: Storage Capacity Exceeded Alert

Adapter Check Error: Receive Queue Overrun Alert

Adapter Check Error: Microcode Program Abnormally Terminated Alert

Adapter Command Error: Configuration Alert

VTAM Token Ring Definitions

VTAM Parameter Descriptions for Token Ring

VTAM Definition for Four SDLC Lines

VTAM Switched Definition for SNAGROUP

VTAM Parameter Descriptions for SDLC

VTAM Definition for X.25 Connection

VTAM Switched Definition for X25GROUP

VTAM Parameter Descriptions for X.25

Sample CICS Terminal Control Table Entries

Sample CICS Program Control Table Entries

Sample CICS Program Processing Table Entries

Sample VTAM Network Control Program (NCP) Definition for LU 6.2

Sample NCP Mode Table Entries for LU 6.2

Program Check Codes

Negative Response Sense Codes

LUSTAT Sense Codes

Registry Variables for an SNA Server

Registry Variables for an SNA Server Client Running Windows NT

Environment Variables: Windows version 3.x, MS-DOS, or OS/2

Environment Variable for a Windows-Based Client Running the 3270 Applet


Before You Begin
Before You Begin	1 of 5

Before You Begin

The Microsoft SNA Server Reference contains error messages you may encounter while using SNA Server. A glossary of frequently used terms is also included.

To use this manual effectively, you should be familiar with:

Microsoft [image] SNA Server (SNA Server)

Microsoft Windows NT [image] operating system

Systems Network Architecture (SNA) concepts


How to Use This Guide
Before You Begin	2 of 5

How to Use This Guide

This manual covers the following topics:

Chapter 1, "SNA Support"

Explains how SNA Server works within SNA networks.

Chapter 2, "Network Management"

Describes the support that SNA Server provides for centralized network management.

Chapter 3, "Error Messages"

Lists the audit and error messages.

Appendix A, "Sample Host Definitions"

Presents samples for SNA Server connections to IBM host systems.

Appendix B, "Program Check Codes and Sense Codes"

Lists program check codes and sense codes used by SNA Server.

Appendix C, "Registry and Environment Variables for SNA Server"

Describes the Registry variables and environment variables that can be set for SNA Server.

Appendix D, "Details of the Installation Process"

Describes the directory tree, network shares, and Registry keys created by SNA Server Setup during the installation of an SNA server.

Glossary

Defines terms relevant to SNA Server.


Document Conventions
Before You Begin	3 of 5

Document Conventions

Throughout this manual, the following conventions distinguish elements of text.

Convention	Purpose

bold	Indicates syntax items that must be typed exactly as shown.

italic	Indicates variables.

monospace	Represents examples and program code.

SMALL CAPS	Represent return values and key names, such as CTRL.

UPPERCASE	Represents filenames, paths, volumes, array and structure names, values, and conversation states.

[brackets]	Enclose optional items in syntax statements.

{braces}	Enclose required items in syntax statements.

| (vertical bar)	Stands for OR and separates items in syntax statements.

... (ellipsis)	Indicates that the preceding syntax item can be repeated.
If a punctuation mark precedes the ellipsis, you must include the punctuation when repeating the item.

X'nnnn'	Indicates hexadecimal digits.


Common Abbreviations
Before You Begin	4 of 5

Common Abbreviations

The following is an alphabetical list of common abbreviations used in this manual.

Abbreviation	Meaning

API	application programming interface

APPC	Advanced Program-to-Program Communications

ASCII	American Standard Code for Information Interchange

BB RQE	Begin Bracket, Exception Response

BTU	basic transmission unit

CD	Change Direction

CEB	Conditional End Bracket

CICS	Customer Information Control System

CPI-C	Common Programming Interface for Communications

CSV	Common Service Verb

DAF	destination address field

DFC	data flow control

DFT	distributed function terminal

DLC	data link control

DSC	data stream compatible

EB	End Bracket

EBCDIC	Extended Binary Coded Decimal Interchange Code

FM	function management

K	kilobyte

LAN	local area network

LL	record length field

LU	logical unit

LUA	conventional Logical Unit Application programming interface

MB	megabyte

NAU	Network Addressable Unit

NCP	Network Control Program

NMVT	network management vector transport

PCT	Program Control Table

PIP	program initialization parameter

PLU	primary logical unit

PPT	Program Processing Table

PU	physical unit

PVC	permanent virtual circuit

QLLC	qualified logical link control

RH	request/response header

RTM	Response Time Monitor

RU	request/response unit

RUI	Request Unit Interface

SCS	3270 SNA Character String

SDLC	Synchronous Data Link Control

SLI	Session Level Interface

SLU	secondary logical unit

SNA	Systems Network Architecture

SSCP	system services control point

SVC	switched virtual circuit

TCT	Terminal Control Table

TH	transmission header

TP	transaction program

TS	transmission service

VTAM	Virtual Telecommunications Access Method

WAN	wide area network


Finding Further Information
Before You Begin	5 of 5

Finding Further Information

For more information about SNA Server, see the following manuals:

Microsoft SNA Server Installation Guide

Microsoft SNA Server Administration Guide

Microsoft SNA Server 3270/5250 Applet User's Guide

Microsoft SNA Server APPC Programmer's Guide

Microsoft SNA Server CPI-C Programmer's Guide

Microsoft SNA Server LUA Programmer's Guide

For more information about SNA and about 3270 information display systems, see the following manuals:

IBM 3270 Information Display System: 3274 Control Unit Description and Programmer's Guide

IBM 3270 Information Display System: Color and Programmed Symbols

IBM 3270 Information Display System: 3274 Control Unit Display Station: Operator's Guide

IBM Systems Network Architecture: Technical Overview

IBM Systems Network Architecture: Concepts and Products

IBM Advanced Communications Function Products Installation Guide

IBM Installation and Resource Definition

IBM 9370 LAN Token Ring Support

IBM SNA Format and Protocol Reference Manual: Architectural Logic

For background information about logical unit 6.2 (LU 6.2), Advanced Program-to-Program Communication (APPC), and/or the Common Programming Interface for Communications (CPI-C), see the following manuals:

IBM Systems Network Architecture: Introduction to APPC

IBM Systems Network Architecture: Transaction Programmer's Reference Manual for LU Type 6.2

IBM SNA: Format and Protocol Reference Manual: Architecture Logic for LU Type 6.2

IBM SNA: Formats

IBM SNA: Technical Overview

IBM SNA: ACF/VTAM Programming for LU Type 6.2


SNA Support
Chapter 1	1 of 27

SNA Support

This chapter explains how SNA Server works within SNA networks. The following information is included:

A summary of the types and number of SNA sessions supported by SNA Server.

A list of the SNA commands supported by SNA Server. This section also shows the type of SNA sessions in which the commands flow.

The transmission service (TS) and function management (FM) profiles supported by SNA Server.

A list and explanation of the five categories of SNA sense codes generated by SNA Server. This section also describes logical unit (LU) type 6.2-specific sense data.

For specific information about an application programming interface (API) supported by SNA Server, see the programmer's guide for that API:

Microsoft SNA Server APPC Programmer's Guide

Microsoft SNA Server CPI-C Programmer's Guide

Microsoft SNA Server LUA Programmer's Guide


SNA Session Support
SNA Support	2 of 27

SNA Session Support

This section lists and explains the types and numbers of SNA sessions supported by SNA Server. For more information about the capacities of SNA Server, see the Microsoft SNA Server Administration Guide.


LU Support
SNA Support	3 of 27

SNA Session Support

LU Support

The SNA Server node can support as many as 10,000 sessions, depending on license limits. For more information about the capacities of SNA Server, see the Microsoft SNA Server Administration Guide.

When using LU type 6.2, an SNA Server LU can be either the primary logical unit (PLU), or the secondary logical unit (SLU). The partner LU can reside in a type 2.1 node, within an upstream type 5 node, or within the SNA Server node itself.

When using LU type 0, 1, 2, or 3, an SNA Server LU is always an SLU, and the partner LU in an upstream type 5 node is always the PLU. With LU type 0, session-level cryptography is supported, within certain limits, on the Request Unit Interface (RUI). Session-level cryptography is implemented through CRV requests; the RUI application(s) must perform all necessary processing. For details about the limits to session-level cryptography and about the processing to be carried out by the RUI application(s), see the Microsoft SNA Server LUA Programmer's Guide. With all interfaces other than RUI, CRV requests are rejected with a negative response.


Session Support
SNA Support	4 of 27

SNA Session Support

Session Support

SNA Server supports three types of SNA communications sessions:

SSCP-PU

The SNA Server PU Services Manager communicating with a host systems services control point (SSCP).

SSCP-LU

An SNA Server LU communicating with a host SSCP.

PLU-SLU

SNA Server LUs communicating with host or peer LUs.


Command Request Support
SNA Support	5 of 27

Command Request Support

Tables1.1 through 1.3 list the SNA command requests supported by SNA Server. Note that not all commands are supported for every LU-to-LU session type. For example, BIS is only supported for use by an APPC LU.

The tables list requests according to the following categories:

Session control requests

Function management data requests: network services (maintenance) and network services (session)

Data flow control requests

The category of each request is denoted by the setting of the request/response unit (RU) category bits in the request/response header (RH) and by the function of the request. SNA Server does not support commands that fall in the network control request category.

For more information about command requests, see your IBM documentation.

Table 1.1    SNA Request Support for Session Control Requests

Session	Request	Direction
SSCP-PU	ACTPU	SSCP to PU
	DACTPU	SSCP to PU
SSCP-LU	ACTLU	SSCP to SLU
	DACTLU	SLU to SSCP
PLU-SLU	BIND	PLU to SLU
	UNBIND	PLU to/from SLU
	CLEAR	PLU to SLU
	SDT	PLU to SLU

Table 1.2    SNA Request Support for Function Management Data Requests

Session	Request	Direction
SSCP-PU	NMVT¹	SSCP to/from PU
	INIT-SELF²	SLU to SSCP
	TERM-SELF²	SLU to SSCP
	NOTIFY²	SLU to SSCP
	NSPE²	SSCP to SLU
¹  Network services, maintenance services

²  Network services, session services

Table 1.3    SNA Request Support for Data Flow Control Requests

Session	Request	Direction
PLU-SLU	BID	PLU to/from SLU
	BIS	PLU to/from SLU
	CANCEL	PLU to/from SLU
	CHASE	PLU to SLU
	LUSTAT	PLU to/from SLU
	RTR	PLU to/from SLU
	SHUTC	PLU from SLU
	SHUTD	PLU to SLU
	SIGNAL	PLU to/from SLU


Transmission Service and Function Management Profiles
SNA Support	6 of 27

Transmission Service and Function Management Profiles

SNA Server enforces the rules that govern active sessions between communicating partners on an SNA network.

The computer running SNA Server can select some of these session protocols — such as request/response control modes, bracket usage, and pacing — when you activate a session. Specific combinations of these selectable protocol options are called profiles.

TS profiles refer to transmission control options, while FM profiles refer to data flow control and function management data options.

When a session is activated, its TS and FM profiles are specified by using parameters in the appropriate session activation request and response (ACTPU, ACTLU, BIND).

Table 1.4 specifies the TS and FM profiles supported by each of the SNA Server session types.

Table 1.4    TS and FM Profiles Supported in SNA Server Sessions

Session type	TS Profiles	FM Profiles
SSCP-LU session	1	0
SSCP-PU session	1	0
3270 display and printer PLU-SLU session	3	3
LU 6.2 PLU-SLU session	7	19
LUA PLU-SLU session	2, 3, 4	2, 3, 4, 7, 18
The following sections describe the TS and FM profiles that SNA Server supports.


TS Profile 1
SNA Support	7 of 27

Transmission Service and Function Management Profiles

TS Profile 1

TS Profile 1 is supported on SSCP-PU (physical unit) and SSCP-SLU sessions; the profile does not require the use of a TS Usage field. This profile specifies the following session rules:

No pacing.

Identifiers rather than sequence numbers are used on the normal flows.

ACTPU, DACTPU, ACTLU, and DACTLU are supported.

Maximum outbound RU size of 256 bytes.

Maximum inbound RU size of 512 bytes.


TS Profile 2
SNA Support	8 of 27

Transmission Service and Function Management Profiles

TS Profile 2

TS Profile 2 is supported on PLU-SLU sessions using LU type 0. This profile specifies the following session rules:

PLU-SLU and SLU-PLU normal flows are paced.

Sequence numbers are used on the normal flows (whenever the transmission header (TH) format used includes a sequence number field).

CLEAR is supported.

SDT, RQR, STSN, and CRV are not supported.

The TS Usage subfields defining the options for this profile are as follows:

Pacing window counts.

Maximum RU sizes on the normal flows.


TS Profile 3
SNA Support	9 of 27

Transmission Service and Function Management Profiles

TS Profile 3

TS Profile 3 is supported on PLU-SLU sessions using LU type 0, 1, 2, or 3. Selection is a BIND option. This profile specifies the following session rules:

PLU-SLU and SLU-PLU normal flows are paced.

Sequence numbers are used on the normal flows.

BIND, UNBIND, CLEAR and SDT are supported.

The TS Usage subfields defining the options for this profile are as follows:

Pacing counts.

Maximum RU sizes on the normal flows.


TS Profile 4
SNA Support	10 of 27

Transmission Service and Function Management Profiles

TS Profile 4

TS Profile 4 is supported on LU-LU sessions using LU type 0 or 1. This profile specifies the following session rules:

PLU-SLU and SLU-PLU normal flows are paced.

Sequence numbers are used on the normal flows (whenever the TH format used includes a sequence number field).

SDT, CLEAR, RQR, and STSN are supported.

CRV is supported when session-level cryptography is selected (via a BIND parameter).

The TS Usage subfields defining the options for this profile are as follows:

Pacing window counts.

Maximum RU sizes on the normal flows.


TS Profile 7
SNA Support	11 of 27

Transmission Service and Function Management Profiles

TS Profile 7

TS Profile 7 is supported on PLU-SLU sessions using LU type 6.2. This profile specifies the following session rules:

PLU-SLU and SLU-PLU normal flows are paced.

Sequence numbers are used on the normal flows.

BIND and UNBIND are supported.

The TS Usage subfields defining the options for this profile are as follows:

Pacing counts.

Maximum RU sizes on the normal flows.


FM Profile 0
SNA Support	12 of 27

Transmission Service and Function Management Profiles

FM Profile 0

FM Profile 0 is supported on SSCP-PU and SSCP-SLU sessions. This profile specifies the following session rules:

SSCP, PU, and SLU use immediate request mode and immediate response mode.

Only single-RU chains are allowed.

All chains require definite response.

No compression.

No data flow control (DFC) RUs.

No FM headers.

No brackets.

No alternate code.

Normal flow send/receive mode is half-duplex contention.

Secondary wins contention.

SSCP is responsible for recovery.


FM Profile 2
SNA Support	13 of 27

Transmission Service and Function Management Profiles

FM Profile 2

FM Profile 2 is supported on PLU-SLU sessions using LU type 0. This profile uses the following session rules:

SLU uses delayed request mode.

SLU uses immediate response mode.

Only single-RU chains are allowed.

SLU requests indicate no-response.

No FMH-1 SCB Compression.

Length-checked compression allowed.

No DFC RUs.

No FM headers.

SLU is first speaker if brackets are used.

Bracket termination rule 2 is used if brackets are used.

PLU will send End Bracket (EB).

SLU will not send EB.

Normal-flow send/receive mode is FDX.

PLU is responsible for recovery.

The following FM Usage fields define the options for Profile 2:

Primary request control mode selection.

Primary chain response protocol (no-response cannot be used).

Brackets usage and reset state.

Alternate code.


FM Profile 3
SNA Support	14 of 27

Transmission Service and Function Management Profiles

FM Profile 3

FM Profile 3 is supported on PLU-SLU sessions using LU type 0, 1, 2, or 3. This profile specifies the following session rules:

PLU and SLU use immediate response mode.

PLU and SLU support the following DFC commands (an asterisk [*] indicates commands permitted by the FM profile that are never sent by SNA Server):

CANCEL

SIGNAL

LUSTAT (SLU-PLU only)

CHASE*

SHUTD

SHUTC

RSHUTD*

BID and RTR

The following FM Usage fields define the options for Profile 3:

Chaining use (PLU and SLU).

Request control mode selection (PLU and SLU).

Chain response protocol (PLU and SLU).

Compression indicator (PLU and SLU).

Send EB indicator (PLU and SLU).

FM header usage.

Bracket usage.

Bracket termination rule.

Alternate Code Set Allowed indicator.

Normal-flow send/receive mode.

Tables 1.5 through 1.7 list the FM Profile 3 options that SNA Server supports. SNA Server rejects any bind that specifies an option value not listed in these tables.

Table 1.5    Supported Options for Bind Requests from Primary LUs

Usage Option	Value	Meaning
Chaining use element	0	Can send only single-element chains
	1	Can send single- or multiple-chains
Request control mode	0	Immediate request mode used
Chain response protocol	01	Can request only exception-only responses
	10	Can request only definite responses
	11	Can request definite or exception-only responses
Compression indicator	0	Cannot send compressed data
	1	Can send compressed data (LU type 1 only)
Send EB indicator	1	Can send End Bracket

Table 1.6    Supported Options for Bind Requests from Secondary LUs

Usage Option	Value	Meaning
Chaining use element	0	Can only send single-element chains (not LU type 2)
	1	Can send single- or multiple-chains
Request control mode	0	Immediate request mode used
Chain response protocol	01	Can request only exception-only responses
	10	Can request only definite responses
	11	Can request definite or exception-only responses
Compression indicator	0	Cannot send compressed data
Send EB indicator	1	Cannot send End Bracket

Table 1.7    Supported Common Protocol Values for Bind Requests from Any LU

Usage Option	Value	Meaning
FM header usage	0	Cannot exchange FM headers
	1	Can exchange FM headers
Bracket usage	1	Bracket protocols must be used
Bracket termination rule	1	Bracket termination rule 1 is used
Alternate code set allowed	0	Must use EBCDIC
Normal flow send/receive mode	10	Half-duplex flip-flop


FM Profile 4
SNA Support	15 of 27

Transmission Service and Function Management Profiles

FM Profile 4

FM Profile 4 is supported on PLU-SLU sessions using LU type 0 or 1. This profile uses the following session rules:

PLU and SLU use immediate response mode.

PLU and SLU support the following DFC commands (an asterisk [*] indicates commands permitted by the FM profile that are never sent by SNA Server):

CANCEL

SIGNAL

LUSTAT

QEC

QC

RELQ

CHASE*

SHUTD

SHUTC

RSHUTD*

BID and RTR (allowed only if brackets are used)

Length-checked compression allowed.

The following FM Usage fields define the options for Profile 4:

Chaining use (PLU and SLU).

Request control mode selection (PLU and SLU).

Chain response protocol (PLU and SLU).

FMH-1 SCB Compression indicator (PLU and SLU).

Send EB indicator (PLU and SLU).

FM header usage.

Brackets usage and reset state.

Bracket termination rule.

Alternate Code Set Allowed indicator.

Normal-flow send/receive mode.

Recovery responsibility.

Contention winner/loser.

Half-duplex flip-flop reset states.


FM Profile 7
SNA Support	16 of 27

Transmission Service and Function Management Profiles

FM Profile 7

FM Profile 7 is supported on PLU-SLU sessions using LU type 0. This profile uses the following session rules:

PLU and SLU use immediate response mode.

PLU and SLU support the following DFC commands (an asterisk [*] indicates commands permitted by the FM profile that are never sent by SNA Server):

CANCEL

SIGNAL

LUSTAT

RSHUTD*

Length-checked compression is allowed on LU 0 only.

The following FM Usage fields define the options for Profile 7:

Chaining use (PLU and SLU).

Request control mode selection (PLU and SLU).

Chain response protocol (PLU and SLU).

FMH-1 SCB Compression indicator (PLU and SLU).

Send EB indicator (PLU and SLU).

FM header usage.

Brackets usage and reset state.

Bracket termination rule.

Alternate Code Set Allowed indicator.

Normal-flow send/receive mode.

Recovery responsibility.

Contention winner/loser.

Half-duplex flip-flop reset states.


FM Profile 18
SNA Support	17 of 27

Transmission Service and Function Management Profiles

FM Profile 18

FM Profile 18 is supported on PLU-SLU sessions using LU type 0. This profile uses the following session rules:

PLU and SLU use immediate response mode.

PLU and SLU support the following DFC commands (an asterisk [*] indicates commands permitted by the FM profile that are never sent by SNA Server):

CANCEL

SIGNAL

LUSTAT

BIS and SBI (allowed only if brackets are used)

CHASE*

BID and RTR (allowed only if brackets are used)

Length-checked compression allowed.

The following FM Usage fields define the options for Profile 18:

Chaining use (PLU and SLU).

Request control mode selection (PLU and SLU).

Chain response protocol (PLU and SLU).

FMH-1 SCB Compression indicator (PLU and SLU).

Send EB indicator (PLU and SLU).

FM header usage.

Brackets usage and reset state.

Bracket termination rule.

Alternate Code Set Allowed indicator.

Normal-flow send/receive mode.

Recovery responsibility.

Contention winner/loser.

Half-duplex flip-flop reset states.


FM Profile 19
SNA Support	18 of 27

Transmission Service and Function Management Profiles

FM Profile 19

FM Profile 19 is supported on PLU-SLU sessions using LU type 6.2. This profile specifies the following session rules:

PLU and SLU use immediate request mode.

PLU and SLU use immediate response mode.

Multiple RU chains are allowed.

PLU and SLU requests indicate definite or exception response.

No compression.

Brackets are used.

FM headers (types 5, 7, and 12 only) are allowed.

Conditional termination for brackets (specified by Conditional End Bracket [CEB]) is used.

PLU and SLU may send CEB.

Normal-flow send/receive mode is half-duplex flip-flop.

Half-duplex flip-flop reset state is SEND for PLU.

Symmetric error responsibility.

Contention winner/loser negotiated at BIND time.

PLU and SLU support the following DFC commands:

SIGNAL

LUSTAT

BIS

RTR

The following combinations of RQE, RQD, CEB, and CD are allowed on end-chain RUs:

RQE	CD	CEB

RQD2	CD	CEB

RQD3	CD	CEB

RQE1	CD	CEB

RQD	CD	CEB

The only option for Profile 19 is contention winner/loser.


Option Set Support
SNA Support	19 of 27

Option Set Support

Table 1.8 lists the option sets supported by SNA Server. The reference numbers are those specified in IBM documentation.

Table 1.8    SNA Server Option Set Support

Ref No.	Option Set

101	Flush the send buffer of the LU

102	Get attributes

103	Post on receipt with test for posting (supported by asynchronous APPC verbs)

104	Post on receipt with wait (supported by asynchronous APPC verbs)

105	Prepare to receive

106	Receive immediate

109	Get TP name and instance identifier

110	Get conversation type

201	Queued allocation of a contention winner session

203	Immediate allocation of a session

204	Conversations between programs located at the same LU

205	Queued allocation for when session free

211	Session-level LU-LU verification

212	User ID verification

213	Program-supplied user ID and password

214	User ID authorization

241	Send program initialization parameter (PIP) data

243	Accounting

244	Long locks

245	Test for request-to-send received

246	Data mapping

251	Extract transaction and conversation identification information

290	Logging of data in a system log

291	Mapped conversation LU services component

505	LU definition verbs (operator only)

601	MIN_CONWINNERS_TARGET parameter

602	RESPONSIBLE(TARGET) parameter

603	DRAIN_TARGET(NO) parameter

605	LU-LU session limit

606	Locally known LU names

607	Uninterpreted LU names

610	Maximum RU size bounds

612	Automatic activation limit for contention winner


SNA Sense Codes
SNA Support	20 of 27

SNA Sense Codes

If there is a communication problem during an SNA session, SNA Server can generate sense codes that notify the remote system of the type of problem. The sense codes fall into five distinct categories, corresponding to the type of problem that occurred:

Value	Category

X'08'	Request Reject

X'10'	Request Error

X'20'	State Error

X'40'	RH Usage Error

X'80'	Path Error

The following sections list the sense codes by category, and include two additional categories of sense codes:

Sense codes sent by a 3270 emulator on LUSTAT requests

Sense codes that can only flow on LU type 6.2 sessions


Request Reject (Category X'08')
SNA Support	21 of 27

SNA Sense Codes

Request Reject (Category X'08')

This category indicates that the request was delivered to the intended half session, and was understood and supported, but not executed. The following codes are in this category:

Code	Meaning

0801	Resource not available

0802	Intervention required (LU1/LU3 printer soft error)

0805	Session limit exceeded

0809	Mode inconsistency

080A	Permission rejected, NOTIFY will not be sent

080B	Bracket race error

080C	Procedure not supported

0812	Insufficient resources

0814	Bracket bid reject-RTR forthcoming

0815	Function active

081B	Contention race condition

081C	Request not executable (hard error)

0821	Invalid session parameters

0829	Change direction required

082B	Presentation space integrity lost

082D	LU busy (usually local copy print in progress)

082E	Intervention required (local copy print soft error)

082F	Request not executable (local copy print hard error)

0831	LU component disconnected

0843	WCC print command not sent (RQD or RQE, CD, EB)

0845	Permission rejected, NOTIFY will be sent

0863	Referenced character set does not exist

0871	Read partition state error (SLU in retry state)


Request Errors (Category X'10')
SNA Support	22 of 27

SNA Sense Codes

Request Errors (Category X'10')

Sense codes in this category represent an imbalance in half-session capabilities. They indicate that the RU was delivered to the intended half-session but could not be processed. The following codes are in this category:

Code	Meaning

1003	Function not supported (also used instead of X'0826', which is not supported by SNA Server).

1005	Parameter modifying a control function is invalid.

1007	Category not supported (SSCP data for host printer).


State Errors (Category X'20')
SNA Support	23 of 27

SNA Sense Codes

State Errors (Category X'20')

Sense codes in this category indicate a sequence number error, or an RH or RU that is not allowed in the receiver's current state. This condition prevents delivery of the request to the intended half-session. The following codes are in this category:

Code	Meaning

2001	Sequence number error

2002	Chaining error

2003	Bracket error

2004	Direction error

2005	Data traffic reset

2006	Data traffic quiesced

2007	Data traffic not quiesced


RH Usage Errors (Category X'40')
SNA Support	24 of 27

SNA Sense Codes

RH Usage Errors (Category X'40')

These sense codes indicate that fields in the RH are contrary to SNA rules or previously selected BIND options and prevent the intended half-session from receiving the request.

Also, the checks 400A and 4012 are performed. These do not permit negative responses, because they apply to no-response sessions and responses, respectively.

The following codes are in this category:

Code	Meaning

4006	Exception response not allowed.

4007	Definite response not allowed.

400F	Incorrect use of format indicator.

4011	Incorrect specification of RU category.

4014	Incorrect use of DR1, DR2, ER.


Path Errors (Category X'80')
SNA Support	25 of 27

SNA Sense Codes

Path Errors (Category X'80')

Sense codes in this category indicate that the request could not be delivered to the required half-session because of path errors. The following codes are in this category:

Code	Meaning

8004	Unrecognized destination field address (DAF).

8005	No session.

8006	Invalid FID: Error detected and logged; negative response not sent.

8007	Segmentation error RH not present or too short: negative response sent only for segmentation error.

8008	PU not active: SSCP-PU was not active and request was not ACTPU or DACTPU.

8009	LU not active: DAF specified an LU for which the SSCP-SLU session has not been activated, and request was not ACTLU or DACTLU.

800F	Invalid address combination.


LUSTAT Sense Codes
SNA Support	26 of 27

SNA Sense Codes

LUSTAT Sense Codes

The following sense codes are sent by a 3270 emulator on LUSTAT requests.

Code	Meaning

0001 B000	Host initialized local copy soft error recovery.

081C 0000	Soft error changed to hard error (LU1/LU3).

081C B000	Soft error changed to hard error (local copy).

082B 0000	SLU session changed from SSCP to PLU (SYSREQ).


Sense Data Specific to LU Type 6.2
SNA Support	27 of 27

SNA Sense Codes

Sense Data Specific to LU Type 6.2

The LU type 6.2 sense codes are specified and interpreted by SNA components within SNA Server, and, in general, are presented as return codes and as parameters to specific verbs.

The following sense codes are carried on responses flowing on LU type 6.2 sessions.

Code	Meaning

0814	Bracket bid reject — RTR forthcoming.

0819	RTR not required — receiver of RTR request has nothing to send.

0835	Invalid parameter — request contained a fixed or variable field which is invalid. Bytes 2 and 3 contain a 2-byte binary count which indexes the field error (zero origin).

0846	ERP message forthcoming: The received request was rejected for a reason to be specified in a forthcoming FMH-7 request — which itself carries SNA sense data (see the following table for a list of these codes).

088B	BB not accepted — BIS reply requested.

2010	BIS protocol error —receiver detected a BIS error; for example, two BIS replies received.

The following data is carried on an FMH-7 request, flowing after the flow of a negative response X'0846'.

Code	Meaning

1008 600B	Resource failure no retry

1008 6021	Allocation error TPN not recognized

1008 6031	Allocation error PIP not allowed

1008 6032	Allocation error PIP not specified correctly

1008 6034	Allocation error conversation type mismatch

1008 6041	Allocation error sync level not supported by pgm

080F 6051	Allocation error security not valid

084B 6031	Allocation error trans pgm not available retry

084C 0000	Allocation error trans pgm not available no retry

0864 0000	Deallocate abend prog

0864 0001	Deallocate abend svc

0846 0002	Deallocate abend timer

0889 0000	Prog error no trunc or prog error purging

0889 0001	Prog error trunc

0889 0100	Svc error no trunc or svc error purging

0889 1001	Svc error trunc


Network Management
Chapter 2	1 of 19

Network Management

This chapter describes the support that SNA Server provides for centralized network management. The following topics are discussed:

Connections used for the NetView [image] and Response Time Monitor (RTM) facilities

Link alerts

Link statistics

Application-generated alerts, and alerts generated through the NVAlert and NVRunCmd services

RTM statistics

Local logging of network management data

For information about configuring the SNA Server to work with NetView and/or RTM, and information about configuring the NVAlert and NVRunCmd services, see the Microsoft SNA Server Administration Guide.


Connections Used for NetView and RTM
Network Management	2 of 19

Connections Used for NetView and RTM

SNA Server can make use of NetView, a reporting system that runs on an IBM host (mainframe). NetView sends alerts between the host and the PCs that connect to it. SNA Server can also receive information from RTM, a 3270 and NetView facility that monitors the amount of time it takes for a host to respond during 3270 display sessions.

To send link alerts, link statistics, and application-generated alerts to the NetView program at the host, you must specify the connection on which the alerts will be sent.

To specify the connection on which NetView data should be sent

1.	Using the SNA Server Administration program (SNA Server Admin), from the Options menu, choose NetView.

2.	Under Send NetView Management Data to Connection, select a connection.

The connection must be a host connection (not peer or downstream), and must not be a distributed function terminal (DFT) connection.

3.	Choose the OK button.

RTM data and NetView alerts sent to the host by 3270 users are not necessarily sent via the NetView connection. RTM data is sent on the connection for the session to which it refers, while 3270 user alerts are sent on the connection for the currently selected 3270 session.

For information about configuring the SNA server to work with NetView and/or RTM, and information about configuring the NVAlert and NVRunCmd services, see the Microsoft SNA Server Administration Guide.


Link Alerts for SDLC and Token Ring
Network Management	3 of 19

Link Alerts for SDLC and Token Ring

When a Synchronous Data Link Control (SDLC) or token ring connection fails, SNA Server logs diagnostic information, called link alerts, about the connection failure. The alerts are logged in a log file that can be viewed using the Windows NT Event Viewer. To find an SNA log, in the Event Viewer, from the Log menu, make sure Application is selected. Under the "Source" heading, the application log file will have a name starting with "SNA."

The link alerts are also used to build a network management vector transport (NMVT) alert, which includes probable causes and suggested actions for the alert. If a connection on the server running SNA Server has been designated for NetView, and the connection is active, the NMVT alert will be sent on that connection.

This section contains the following information:

An explanation of the general format of link alerts, common to both SDLC and token ring.

Descriptions of individual alerts produced by the SDLC link service.

Detailed information about the local logging of SDLC alerts.

Descriptions of individual alerts produced by the token ring link service.

Details of the local logging of token ring alerts.

For information about the NetView vectors supported by the NVAlert and NVRunCmd services, see "Alerts Used by Applications, NVAlert, and NVRunCmd" later in this chapter.


Link Alert Format and Common Subvectors
Network Management	4 of 19

Link Alerts for SDLC and Token Ring

Link Alert Format and Common Subvectors

The general format of link alerts is as follows:

NMVT HEADER

41 03 8D 00 00 00 00 00     NMVT Header

Major Vector Header

LL LL     Length of Major Vector

00 00     Alert major vector

The specific alert is identified by the alert description and alert ID (part of the generic alert subvector). Common subvectors are listed later in this section. SDLC and token ring failure alerts are described in the "SDLC Failure Alerts" and "Token Ring Failure Alerts" sections, respectively, later in this chapter.

Each subvector or subfield begins with a 1-byte length field and a 1-byte key identifying the subvector or subfield. The length field contains the length in bytes of the entire subvector or subfield, including the length and key bytes. Where the length byte is shown as LL, this indicates that the length is not fixed because different alerts require different data to be included.

Table 2.1 lists all the possible subvectors used in the alert, with their subvector keys (identifiers).

Table 2.1    Link Alert Subvectors

Subvector key(identifier)	Subvector

05	Hierarchy/Resource List Subvector.

03	Hierarchy Name List Subvector.

01	Date/Time Subvector.

10	Product Set ID Subvector (this appears twice, as Alert Sender PSID and Indicated Resource PSID).

51	LAN LCS Data Subvector.

52	LCS Configuration Data Subvector.

8C	Link Station Data Subvector.

91	Basic Alert Subvector.

92	Generic Alert Subvector.

93	Probable Cause Subvector.

94	User Causes Subvector.

95	Install Causes Subvector.

96	Failure Causes Subvector.

A1	Detail Qualifier Subvector.

The following tables describe the formats of link alert subvectors. Additional tables, later in this chapter, describe the individual link alerts.

Hierarchy/Resource List Subvector

Format and contents	Description

LL 05	Hierarchy/Resource List Subvector.

LL 10	Hierarchy/Resource List Subfield.

hh 	Flags:80 (1-User)00 (Server).

LL	Name field length: name length plus this length byte.

hh...hh	Adapter name in EBCDIC, 8 bytes.

00	Flags byte: always 0.

3F	Resource type: port.

Optional second name	Remote host name. For token ring, local ring name. See individual alert descriptions.

LL	Name field length: name length plus this length byte.

hh...hh	Name in EBCDIC, up to 8 bytes.

00 	Flags byte: always 0.

F4 or 2E 	Resource type: control point or token ring.

Hierarchy/Name List Subvector

Format and contents	Description

LL 03	Hierarchy Name List subvector.

00 or 03	Reserved byte.

hh	Number of names in the hierarchy name list.

LL	Length of each name, including this length byte.

hh...hh 	Name of resource for each name.

D3 C3 D6 D5	Resource type identifier: LCON (logical link connection not known to SNA).

Date/Time Subvector Alerts

Format and contents	Description

0A 01	Date/Time Subvector.

08 10	Local Date/Time subfield.

hh	Year — two digits.

hh	Month.

hh	Date.

hh	Hours.

hh	Minutes.

hh	Seconds (binary).

Product Set ID Subvector

Format and contents	Description
2A 10	Product Set ID subvector.
00	(unused field).
27 11	Product ID subvector.
0C	Product classification: non-IBM software.
08 04	Software product common level subfield.
F0 F2	Version identifier: 02.
F0 F0	Release identifier: 00.
F0 F0	Modification identifier: 00.
13 06	Software product common name subfield.
C4 C3 C1 61 D4 E2 40C3 D6 D4 D4 40E2 C5 D9 E5 D9	Product name:  MS [image]  SNA Server
09 08	Software product program number subfield.
F0 F0 F0 F0 F0 F0 F0	Product program number: zeros.

LAN Link Connection Subsystem Data Subvector*

Format and contents	Description

LL 51	LAN LCS Data Subvector.

04 02	Ring Identifier subfield.

hh hh	Ring number.

08 03	Local Individual MAC Address subfield.

hh...hh	Local individual MAC address.

08 04	Remote Individual MAC Address subfield.

hh...hh	Remote individual MAC address.

LL 05	LAN Routing Information subfield.

hh...hh	LAN routing information

* Token ring only.

Link Connection Subsystem Configuration Data Subvector

Format and contents	Description

LL 52	LCS Configuration Data Subvector.

04 01	Port Address subfield.

hh hh	Port address.

03 02	Remote Device Address subfield.

hh	Remote device address.

03 04	Local Device Address subfield.

hh	Local device address.

04 06	Link Station Attributes subfield.

01 or 02 or 03	Link station role: Primary, Secondary, or Negotiable.

03 or 04	Remote node type: Type 4 or Type 2.1.

06 07	Link Attributes subfield.

01 or 02	Link connection type: nonswitched or switched.

01 or 02	Half-duplex or full-duplex.

01	Protocol: SDLC.

01 or 02	Point-to-point or multipoint.

Link Station Data Subvector

Format and contents	Description

LL 8C	Link Station Data Subvector.

04 01	N(s) and N(r) counts subfield.

hh	N(s) count.

hh 	N(r) count.

03 02	Outstanding frame count subfield.

hh	Outstanding frame count.

04 03	Last SDLC Control Field Received subfield.

hh hh	Last control field received.

04 04	Last SDLC Control Field Sent subfield.

hh hh	Last control field sent.

03 05	Sequence Number Modulus subfield.

80	Sequence number modulus.

03 06	Link Station State subfield.

80 or 40	Link station state: local or remote station sending RNR.

04 07	LLC Reply Timer Expiration Count subfield.

hh hh	Reply timer expiration count.

03 08	Last Received N(r) Count subfield.

hh	Last received N(r) (binary).

Basic Alert Subvector

Format and contents	Description

0E 91	Basic Alert subvector.

00	Not operator initiated.

01	Alert type: permanent.

0E	General cause code: link-level protocol error.

00 80 or 00 34	Specific component code: token ring LAN or SDLC data link control.

00 00	Alert description code.

00 00	User action code.

00 00	Detail text reference code.

00	Unused field.

Generic Alert Subvector

Format and contents	Description

0B 92	Generic Alert subvector.

00 00	Flags: not operator initiated, not a held alert.

01	Alert type: permanent.

hh hh 	Alert description: See alert descriptions.

hh hh hh hh	Alert ID number (unique to a particular alert).

Probable Cause Subvector

Format and contents	Description

LL 93	Probable cause subvector.

hh hh	Probable cause: See individual alert descriptions. This alert may include more than one entry.

User Causes Subvector

Format and contents	Description

LL 94	User Causes Subvector.

LL 01	User causes subfield.

hh hh	User cause: See individual alert descriptions. More than one entry may appear here.

LL 81	Recommended actions subfield.

hh hh	Recommended action: See individual alert descriptions. More than one entry may appear here.

03 83	Product set ID index subfield.

99 	Product Set ID index.

LL 82	Detailed data subfield. This subfield may appear more than once.

99 	Product Set ID code.

hh	Data ID: See individual alert descriptions.

00	Data encoding: hexadecimal.

hh...hh	Detailed data: See individual alert descriptions.

Install Cause Subvector

Format and contents	Description

LL 95	Install Causes Subvector.

LL 01	Install causes subfield.

hh hh	Install cause: See individual alert descriptions. More than one entry may appear here.

LL 81	Recommended actions subfield.

hh hh	Recommended action: See individual alert descriptions. More than one entry may appear here.

03 83	Product set ID index subfield.

99	Product Set ID index.

LL 82	Detailed data subfield. This subfield may occur more than once.

99	Product Set ID code.

hh	Data ID: See individual alert descriptions.

00	Data encoding: hexadecimal.

hh...hh	Detailed data: See individual alert descriptions.

Failure Cause Subvector

Format and contents	Description

LL 96	Failure Causes Subvector.

LL 01	Failure causes subfield.

hh hh	Failure cause: See individual alert descriptions. More than one entry may appear here.

LL 81	Recommended actions subfield.

hh hh	Recommended action: See individual alert descriptions. More than one entry may appear here.

03 83	Product set ID index subfield.

99	Product Set ID index.

LL 82	Detailed data subfield. This subfield may occur more than once.

99	Product Set ID code.

hh	Data ID: See individual alert descriptions.

00	Data encoding: hexadecimal.

hh...hh	Detailed data: See individual alert descriptions.

Detail Qualifier (Hexadecimal) Subvector

Format and contents	Description

06 A1	Detail Qualifier subvector.

hh hh hh hh	Detail Qualifier subfield — four bytes as follows:

Token ring: adapter number

Alert number

Two-byte error code SDLC: link ID

Station address, outage


SDLC Failure Alerts
Network Management	5 of 19

Link Alerts for SDLC and Token Ring

SDLC Failure Alerts

The tables in this section describe the alerts generated by the SDLC link service provided with SNA Server. The alerts are listed in numerical order by alert description and within each description in numerical order by alert ID.

Write Timeout Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		1000		Equipment malfunction
Alert ID:		61D0 2E7B
Probable causes:		2031		Line
		3601		Local modem
		2200		Remote node
		3603		Remote modem
Failure causes:		3511		Line
		3601		Local modem
		2200		Remote node
		3603		Remote modem
		F034		CTS failed to rise
Recommended actions:		0403		Run modem tests
		2011		Review hexadecimal display of alert
		32A0		Report the following detail qualifier:Outage qualifier
Detail qualifier:		2E		Write timeout retry exceeded

Abnormal Modem Response Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		1000		Equipment malfunction
Alert ID:		70A1 5CB0
Probable causes:		3601		Local modem
		3401		Local cable
		3302		Communications adapter
User causes:		3401		Cabling installed incorrectly
Recommended actions:		0301		Check cable and its connections
Failure causes:		3601		Local modem
		3401		Local cable
		3302		Communications adapter
		F035		DSR dropped
Recommended actions:		0403		Run modem tests
		2011		Review hexadecimal display of alert
		32A0		Report the following detail qualifier:Outage qualifier
Detail qualifier:		2D		Abnormal response

DSR Failure Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		1000		Equipment malfunction
Alert ID:		83BB 6EC8
Probable causes:		3601		Local modem
		3401		Local cable
		3302		Communications adapter
User causes:		3400		Cable loose
		0205		Local modem power off
Failure causes:		3601		Local modem
		3401		Local cable
		3302		Communications adapter
		F035		DSR dropped
Recommended actions:		0403		Run modem tests
		2011		Review hexadecimal display of alert
		32A0		Report the following detail qualifier:Outage qualifier
Detail qualifier:		11		DSR failure

DCD Failure Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		1000		Equipment malfunction
Alert ID:		C3BB 504A
Probable causes:		2031		Line
		3601		Local modem
Failure causes:		3511		Line
		3601		Local modem
		F038		Carrier detect lost
Recommended actions:		0403		Run modem tests
		2011		Review hexadecimal display of alert
		32A0		Report the following detail qualifier:Outage qualifier
Detail qualifier:		14		DCD failure

Invalid Frame Received: I-Field Not Permitted Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		2100		Software program error
Alert ID:		1103 D152
Probable causes:		2004		SDLC communications
		1023		Communications program in remote node
Failure causes:		1023		Communications program in remote node
		F021		I-field received when not permitted
Recommended actions:		2011		Review hexadecimal display of alert report
		32A0		Report the following detail qualifier:Outage qualifier
Detail qualifier:		87		Invalid frame received

Invalid Frame Received: Invalid/Unsupported CMD/RSP Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		2100		Software program error
Alert ID:		15C2 CCE5
Probable causes:		2004		SDLC communications
		1023		Communications program in remote node
Failure causes:		1023		Communications program in remote node
		F020		Invalid/unsupported command or response received
Recommended actions:		2011		Review hexadecimal display of alert
		32A0		Report the following detail qualifier:Outage qualifier
Detail qualifier:		87		Invalid frame received

Invalid Frame Received: Invalid N(R) Received Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		2100		Software program error
Alert ID:		1C40F78B
Probable causes:		2004		SDLC communications
		1023		Communications program in remote node
Failure causes:		1023		Communications program in remote node
		F022		Invalid N(R) received
Recommended actions:		2011		Review hexadecimal display of alert
		32A0		Report the following detail qualifier:Outage qualifier
Detail qualifier:		87		Invalid frame received

RIM/RD Received Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		2100		Software program error
Alert ID:		29BF 0032
Probable causes:		2104		SDLC communications/remote node
		1023		Communications program in remote node
Failure causes:		2104		SDLC communications/remote node
		3511		Line
Recommended actions:		2011		Review hexadecimal display of alert
		32A0		Report the following detail qualifier:Outage qualifier
Detail qualifier:		88		RIM received
		89		RD received

Invalid Frame Received: Max I-Field Length Exceeded Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		2100		Software program error
Alert ID:		5F76 24FD
Probable causes:		2104		SDLC communications/remote node
		1023		Communications program in remote node
Failure causes:		1023		Communications program in remote node
		F023		Received I-field exceeded maximum length
Recommended actions:		2011		Review hexadecimal display of alert
		32A0		Report the following detail qualifier:Outage qualifier
Detail qualifier:		87		Invalid frame received

FRMR Received: No Reason Given Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		2100		Software program error
Alert ID:		A472 BC48
Probable causes:		2004		SDLC communications
		1000		Software program
Failure causes:		1000		Software program
		F014		FRMR received: no reason specified
Recommended actions:		2011		Review hexadecimal display of alert
		32A0		Report the following detail qualifier:Outage qualifier
Detail qualifier:		86		FRMR received

FRMR Received: I-Field Received When Not Permitted

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		2100		Software program error
Alert ID:		B3B7 D723
Probable causes:		2004		SDLC communications
		1000		Software program
Failure causes:		1000		Software program
		F011		FRMR received: I-field sent when not permitted
Recommended actions:		2011		Review hexadecimal display of alert
		32A0		Report the following detail qualifier:Outage qualifier
Detail qualifier:		86		FRMR received

FRMR Received: Invalid/Unsupported Command or Response Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		2100		Software program error
Alert ID:		B776 CA94
Probable causes:		2004		SDLC communications
		1000		Software program
Failure causes:		1000		Software program
		F010		FRMR received: invalid/unsupported command or response sent
Recommended actions:		2011		Review hexadecimal display of alert
		32A0		Report the following detail qualifier:Outage qualifier
Detail qualifier:		86		FRMR received

FRMR Received: Max I-Field Length Exceeded Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		2100		Software program error
Alert ID:		BA35 EC4D
Probable causes:		2004		SDLC communications
		1000		Software program
Failure causes:		1000		Software program
		F013		FRMR received: maximum I-field length exceeded
Recommended actions:		2011		Review hexadecimal display of alert
		32A0		Report the following detail qualifier:Outage qualifier
Detail qualifier:		86		FRMR received
FRMR Received: Invalid N(R) Sent Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		2100		Software program error
Alert ID:		BEF4 F1FA
Probable causes:		2004		SDLC communications
		1000		Software program
Failure causes:		1000		Software program
		F012		FRMR received: invalid N(R) sent
Recommended actions:		2011		Review hexadecimal display of alert
		32A0		Report the following detail qualifier:Outage qualifier
Detail qualifier:		86		FRMR received
DISK/SNRM Received: SNRM Received in NRM Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		2100		Software program error
Alert ID:		D635 CA1E
Probable causes:		2004		SDLC communications
		1023		Communications program in remote node
Failure causes:		1023		Communications program in remote node
		F015		SNRM received while in NRM
Recommended actions:		2011		Review hexadecimal display of alert
		32A0		Report the following detail qualifier:Outage qualifier
Detail qualifier:		15		Connection terminated by host

CTS Failure Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		3300		Link error
Alert ID:		0231 CF0A
Probable causes:		2031		Line
		3601		Local modem
Failure causes:		3511		Line
		3601		Local modem
		F030		CTS dropped
Recommended actions:		0403		Run modem tests
		2011		Review hexadecimal display of alert
		32A0		Report the following detail qualifier:Outage qualifier
Detail qualifier:		12		CTS failure

Connection Problem: XID Retransmission Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		3300		Link error
Alert ID:		0AEC C2A6
Probable causes:		2104		SDLC communications/remote node
		2031		Line
User causes:		0209		Remote device power off
Recommended action:		0200		Check power
Failure causes:		2104		SDLC communications/remote node
		3511		Line
		F018		XID poll count exhausted

Idle Timeout Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		3300		Link error
Alert ID:		0E2D DF11
Probable causes:		2104		SDLC communications/remote node
		2031		Line
User causes:		0209		Remote device power off
Recommended action:		0200		Check power
Failure causes:		2104		SDLC communications/remote node
		3511		Line
		F019		Inactivity timer expired
Recommended actions:		2011		Review hexadecimal display of alert
		32A0		Report the following detail qualifier:Outage qualifier
Detail qualifier:		25		Idle timeout retry exceeded

Poll Count Exhausted Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		3300		Link error
Alert ID:		32A3 7F1B
Probable causes:		2104		SDLC communications/remote node
		2031		Line
User causes:		0209		Remote device power off
Recommended action:		0200		Check power
Failure causes:		2104		SDLC communications/remote node
		3511		Line
		F017		Poll count exhausted
Recommended actions:		2011		Review hexadecimal display of alert
		32A0		Report the following detail qualifier:Outage qualifier
Detail qualifier:		81		Disconnect retry limit
		82		Contact retry limit
		83		Poll retry limit
		84		No response retry limit

Remote Busy Retry Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		3300		Link error
Alert ID:		66D6 DA74
Probable causes:		2104		SDLC communications/remote node
User causes:		0209		Remote device power off
Recommended actions:		0200		Check power
Failure causes:		2104		SDLC communications/remote node
		3511		Line
		F00F		RNR received threshold reached
Recommended actions:		2011		Review hexadecimal display of alert
		32A0		Report the following detail qualifier:Outage qualifier
Detail qualifier:		85		Remote busy retry limit

DM Received in Information Transfer Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		3300		Link error
Alert ID:		BD84 C4C9
Probable causes:		2004		SDLC communications
Failure causes:		2004		SDLC communications
		F01A		DM received
Recommended actions:		2011		Review hexadecimal display of alert
		32A0		Report the following detail qualifier:Outage qualifier
Detail qualifier:		80		DM received

Nonproductive Receive Timeout Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		3300		Link error
Alert ID:		C458 E284
Probable causes:		2104		SDLC communications/remote node
		2031		Line
User causes:		0209		Remote device power off
Recommended action:		0200		Check power
Failure causes:		2104		SDLC communications/remote node
		3511		Line
		F00E		NPR timeout retry limit reached
Recommended actions:		2011		Review hexadecimal display of alert
		32A0		Report the following detail qualifier:Outage qualifier
Detail qualifier:		24		Nonproductive receive retry exceeded

DISK/SNRM Received: Disk Received Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		3300		Link error
Alert ID:		D9C4 172B
Probable causes:		2004		SDLC communications
Failure causes:		2004		SDLC communications
Recommended actions:		2011		Review hexadecimal display of alert
		32A0		Report the following detail qualifier:Outage qualifier
Detail qualifier:		15		Connection terminated by host

Connection Problem: I-Frame Retransmission Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		3300		Link error
Alert ID:		E3DA E42F
Probable causes:		2104		SDLC communications/remote node
		2031		Line
User causes:		0209		Remote device power off
Recommended action:		0200		Check power
Failure causes:		2104		SDLC communications/remote node
		3511		Line
		F06A		Transmit retry limit reached
Recommended actions:		2011		Review hexadecimal display of alert
		32A0		Report the following detail qualifier:Outage qualifier
Detail qualifier:		29		Connection problem


SDLC Alert Local Logging
Network Management	6 of 19

Link Alerts for SDLC and Token Ring

SDLC Alert Local Logging

Before SNA Server attempts to build and send an SDLC Link Alert, information about the outage that caused the alert is logged in a log file that can be viewed using the Windows NT Event Viewer. Message 182 will always be logged, as follows:

182I:  Connection failure, code = (outagecode)

Cause Data	= hh...hh

Link Role	= hh

Remote Node Type	= hh

The Outage Code (outagecode) is also reported on a 23 message. For a complete list of these codes, the conditions they represent, and the specific Link Alerts on which they are used, see the next section.

Cause Data is a list of the failure causes from the Failure causes subvector in the alert. Link Role and Remote Node type are as described in the Link Connection Subsystem Configuration Data subvector in the alert.

A connection failure can be due to a station outage, rather than a link outage. If it is due to a station outage — which can be recognized by outage code values of X'80' or higher — then message 183, formatted as follows, will also be logged:

183I:

Detailed diagnostic data for station (stationaddress):

SBSY	CFTX	CFRX	V(S)	V(R)	N(R)	OSFC	T1CT
hh	hhhh	hhhh	hh	hh	hh	hh	hhhh
The value (stationaddress) is the station address as given in the Detail qualifier subvector in the alert.

The other fields are all data from the Link Station Data subvector, as follows:

Field		Description
SBSY		Link station state: 80 or 40
		(local or remote station sending RNR)
CFTX		Last SDLC control field sent
CRX		Last SDLC control field received
V(S)		N(S) count
V(R)		N(R) count
N(R)		Last received N(R)
OSFC		Outstanding frame count
T1CT		Reply timer expiration count
Identifying Alerts from Local Logs Only

When only the local log of an alert is available, you can still obtain the information that would have been supplied on the alert. To do this, check the outage code given on the 182 message against the following list to find the alert that uses this outage code, and then check the alert data in "SDLC Failure Alerts" earlier in this chapter. Some Outage Codes are used for more than one alert; in these cases, you can find the appropriate alert by comparing the failure causes codes given on the 182 message with those given in the alert data.

SDLC Outage Codes

Outage code		Condition		Alert description/ID
11		DSR failure		1000 : 83BB6EC8
12		CTS failure		3300 : 0231CF0A
14		DCD failure		1000 : C3BB504A
15		Connection terminated by host		2100 : D635CA1E 2100 : D9C4172B
24		Nonproductive receive retry exceeded		3300 : C458E284
25		Idle timeout retry exceeded		3300 : 0E2DDF11
29		Connection problem		3300 : 0AECC2A6 3300 : E3DAE42F
2D		Abnormal response		1000 : 70A15CB0
2E		Write timeout retry exceeded		1000 : 61D02E7B
80		DM received		3300 : BD84C4C9
81		Disconnect retry limit		3300 : 32A37F1B
82		Contact retry limit		3300 : 32A37F1B
83		Poll retry limit		3300 : 32A37F1B
84		No response retry limit		3300 : 32A37F1B
85		Remote busy retry limit		3300 : 66D6DA74
86		FRMR received		2100 : A472BC48
				2100 : B3B7D723
				2100 : B776CA94
				2100 : BA35EC4D
				2100 : BEF4F1FA
87		Invalid frame received		2100 : 1103D152
				2100 : 15C2CCE5
				2100 : 1C40F78B
				2100 : 5F7624FD
88, 89		RIM received or RD received		2100 : 29BF0032


Token Ring Failure Alerts
Network Management	7 of 19

Link Alerts for SDLC and Token Ring

Token Ring Failure Alerts

The tables in this section describe the alerts generated by the token ring link service provided with SNA Server. The alerts are listed in numerical order by alert description and within each description in numerical order by alert ID.

Adapter Check Error: Adapter Error Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		1010		Adapter error
Alert ID:		3BA0 3B6D
Probable causes:		3320		Local token ring adapter
Failure causes:		3320		Local token ring adapter
Recommended actions:		2010		Review link detailed data
		3101		Contact token ring administrator for this LAN
		32C0		Report the following detail qualifier:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
Detailed Data:		02		Data ID: adapter check status
		hh hh		Adapter check status
LAN LCS:				Ring identifierLocal individual MAC address

DLC Status Error: FRMR Sent-Invalid N(R) Received

Name of subvector		Hexadecimal value in subvector		Description
Hierarchy/ resource list:				Second name is remote node CP name
Alert description:		2100		Software program error
Alert ID:		216D 1033
Probable causes:		2007		LAN LLC communications
		1023		Communications program in remote node
Failure causes:		1023		Communications program in remote node
		F012		Invalid N(r) received
Recommended actions:		3301		If problem persists do the following:
		2010		Review link detailed data
		3103		Contact LAN administrator responsible for this LAN
		32A0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
LAN LCS:				Ring identifierLocal individual MAC addressRemote individual MAC addressLAN routing information
LCS configuration:				Remote device addressLocal device address
Link Station Datasubvector included

DLC Status Error: FRMR Sent-Received I-Field Exceeded Maximum Length Alert

Name of subvector		Hexadecimal value in subvector		Description
Hierarchy/ resource list:				Second name is remote node CP name
Alert description:		2100		Software program error
Alert ID:		25AC 0D84
Probable causes:		2007		LAN LLC communications
		1023		Communications program in remote node
Failure causes:		1023		Communications program in remote node
		F023		Received I-field exceeded maximum length
Recommended actions:		3301		If problem persists do the following:
		2010		Review link detailed data
		3103		Contact LAN administrator responsible for this LAN
		32A0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
LAN LCS:				Ring identifierLocal individual MAC addressRemote individual MAC addressLAN routing information
LCS configuration:				Remote device addressLocal device address
Link Station Datasubvector included

DLC Status Error: FRMR Sent-Invalid/Unsupported Command/Response Received Alert

Name of subvector		Hexadecimal value in subvector		Description
Hierarchy/ resource list:				Second name is remote node CP name
Alert description:		2100		Software program error
Alert ID:		28EF 2B5D
Probable causes:		2007		LAN LLC communications
		1023		Communications program in remote node
Failure causes:		1023		Communications program in remote node
		F020		Invalid/unsupported command or response received
Recommended actions:		3301		If problem persists do the following:
		2010		Review link detailed data
		3103		Contact LAN administrator responsible for this LAN
		32A0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
LAN LCS:				Ring identifierLocal individual MAC addressRemote individual MAC addressLAN routing information
LCS configuration:				Remote device addressLocal device address
Link Station Datasubvector included

DLC Status Error: FRMR Sent-I-Field Received When Not

Permitted Alert

Name of subvector		Hexadecimal value in subvector		Description
Hierarchy/ resource list:				Second name is remote node CP name
Alert description:		2100		Software program error
Alert ID:		2C2E 36EA
Probable causes:		2007		LAN LLC communications
		1023		Communications program in remote node
Failure causes:		1023		Communications program in remote node
		F021		I-field received when not permitted
Recommended actions:		3301		If problem persists do the following:
		2010		Review link detailed data
		3103		Contact LAN administrator responsible for this LAN
		32A0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
LAN LCS:				Ring identifierLocal individual MAC addressRemote individual MAC addressLAN routing information
LCS configuration:				Remote device addressLocal device address
Link Station Datasubvector included

Adapter Command Error: Software Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		2100		Software program error
Alert ID:		3EF7 89B7
Probable causes:		1000		Software program
Failure causes:		1000		Software program
Recommended actions:		30E1		Contact service representative
		32C0		Report the following data:
				Product Set ID index subfield included
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
Detailed data:		03		Data ID: adapter return code
		hh		Adapter return code

DLC Status Error: DM or Disk Received Alert

Name of subvector		Hexadecimal value in subvector		Description
Hierarchy/ resource list:				Second name is remote node CP name
Alert description:		2100		Software program error
Alert ID:		4B74 26FB
Probable causes:		2007		LAN LLC communications
		1023		Communications program in remote node
Failure causes:		1023		Communications program in remote node
		F01A		DM received
Recommended actions:		3301		If problem persists do the following:
		2010		Review link detailed data
		3101		Contact token ring administrator for this LAN
		32A0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
LAN LCS:				Ring identifierLocal individual MAC addressRemote individual MAC addressLAN routing information
LCS configuration:				Remote device addressLocal device address
Link Station Data subvector included

DLC Status Error: FRMR Received-Invalid N(R) Sent Alert

Name of subvector		Hexadecimal value in subvector		Description
Hierarchy/ resource list				Second name is remote node CP name
Alert description:		2100		Software program error
Alert ID:		83D9 1642
Probable causes:		2007		LAN LLC communications
		1000		Software program
Failure causes:		1000F012		Software programFrame reject received:Invalid N(r) sent
Recommended actions:		3301		If problem persists do the following:
		2010		Review link detailed data
		3103		Contact LAN administrator responsible for this LAN
		32A0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
LAN LCS:				Ring identifierLocal individual MAC addressRemote individual MAC addressLAN routing information
LCS configuration:				Remote device addressLocal device address
Link Station Datasubvector included

DLC Status Error: FRMR Received-Max I-Field Length

Name of subvector		Hexadecimal value in subvector		Description
Hierarchy/ resource list:				Second name is remote node CP name
Alert description:		2100		Software program error
Alert ID:		8718 0BF5
Probable causes:		2007		LAN LLC communications
		1000		Software program
Failure causes:		1000		Software program
		F013		Frame reject received: maximum Ifield length exceeded
Recommended actions:		3301		If problem persists do the following:
		2010		Review link detailed data
		3103		Contact LAN administrator responsible for this LAN
		32A0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
LAN LCS:				Ring identifierLocal individual MAC addressRemote individual MAC addressLAN routing information
LCS configuration:				Remote device addressLocal device address
Link Station Datasubvector included

DLC Status Error: FRMR Received-Invalid/Unsupported Commands/Response Sent Alert

Name of subvector		Hexadecimal value in subvector		Description
Hierarchy/ resource list:				Second name is remote node CP name
Alert description:		2100		Software program error
Alert ID:		8A5B 2D2C
Probable causes:		2007		LAN LLC communications
		1000		Software program
Failure causes:		1000		Software program
		F010		Frame reject received:Invalid/unsupported command or response sent
Recommended actions:		3301		If problem persists do the following:
		2010		Review link detailed data
		3103		Contact LAN administrator responsible for this LAN
		32A0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
LAN LCS:				Ring identifierLocal individual MAC addressRemote individual MAC addressLAN routing information
LCS configuration:				Remote device addressLocal device address
Link Station Datasubvector included

DLC Status Error: FRMR Received-I-Field Sent When Not Permitted Alert

Name of subvector		Hexadecimal value in subvector		Description
Hierarchy/ resource list:				Second name is remote node CP name
Alert description:		2100		Software program error
Alert ID:		8E9A 309B
Probable causes:		2007		LAN LLC communications
		1000		Software program
Failure causes:		1000		Software program
		F011		Frame reject received: I-field sent when not permitted
Recommended actions:		3301		If problem persists do the following:
		2010		Review link detailed data
		3103		Contact LAN administrator responsible for this LAN
		32A0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
LAN LCS:				Ring identifierLocal individual MAC addressRemote individual MAC addressLAN routing information
LCS configuration:				Remote device addressLocal device address
Link Station Datasubvector included

Software Program Error: Adapter Interface Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		2100		Software program error
Alert ID:		DA7B C09D
Probable causes:		3220		Token ring adapter interface
Install causes:		1600		Mismatch between software and microcode
		1601		Incorrect customization image
Recommended actions:		1500		Correct installation problem
		1502		Correct customization parameters
Failure causes:		3220		Token ring adapter interface
Recommended actions:		2010		Review link detailed data
		3101		Contact token ring administrator for this LAN
		32C0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
Detailed data:		07		Data ID: error code
		hh hh		Error code
LAN LCS:				Ring identifierLocal individual MAC address

DLC Status Error: SABME Received for Open Link Station Alert

Name of subvector		Hexadecimal value in subvector		Description
Hierarchy/ resource list:				Second name is remote node CP name
Alert description:		2100		Software program error
Alert ID:		E65B 0B7F
Probable causes:		2007		LAN LLC communications
		1023		Communications program in remote node
Failure causes:		1023		Communications program in remote node
		F016		SABME received while in ABME
Recommended actions:		3301		If problem persists do the following:
		2010		Review link detailed data
		3103		Contact LAN administrator responsible for this LAN
		32A0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
LAN LCS:				Ring identifierLocal individual MAC addressRemote individual MAC addressLAN routing information
LCS configuration:				Remote device addressLocal device address
Link Station Datasubvector included

Bring-Up Error Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		3210		Initialization failure
Alert ID:		AB86 8B0B
Probable causes:		3320		Local token ring adapter
Install causes:		1200		Incorrect hardware configuration
		1402		Mismatch between hardware and software configurations
Recommended actions:		1503		Correct configuration
Failure causes:		3320		Local token ring adapter
Recommended actions:		30E1		Contact service representative
		32C0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
Detailed data:		07		Data ID: error code
		hh hh		Error code
LAN LCS:				Local individual MAC address

Adapter Open Error: Open Failure Alert

Name of subvector		Hexadecimal value in subvector		Description
Hierarchy/ resource list:				Second name is ring name
Alert description:		3211		Open failure
Alert ID:		016E 5F4E
Probable causes:		3702		Token ring lobe
		3701		Token ring LAN component
Failure causes:		3712		Local token ring lobe
		3701		Token ring LAN component
		2600		Interference
Recommended actions:		2010		Review link detailed data
		3101		Contact token ring administrator for this LAN
		32C0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
Detailed data:		07		Data ID: error code
		hh hh		Error code
LAN LCS:				Local individual MAC address

Adapter Open Error: Remove Command Received Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		3211		Open failure
Alert ID:		44D1 AD86
Probable causes:		3705		Token ring remove command received
User causes:		3320		Token ring remove adapter command received
Recommended actions:		2010		Review link detailed data
		3101		Contact token ring administrator for this LAN
		32C0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
Detailed data:		07		Data ID: error code
		hh hh		Error code
LAN LCS:				Local individual MAC address

Adapter Open Error: Problem on Local Lobe Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		3211		Open failure
Alert ID:		55BF 3E1C
Probable causes:		3702		Token ring lobe
Failure causes:		3320		Local token ring adapter
		3711		Local token ring lobe
		3434		Local lobe cables
Recommended actions:		1009		Try reopening adapter after 30 seconds
		3301		If problem persists do the following:
		2010		Review link detailed data
		3101		Contact token ring administrator for this LAN
		32C0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
Detailed data:		07		Data ID: error code
		hh hh		Error code
LAN LCS:				Local individual MAC address

Adapter Open Error: Beaconing Detected Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		3211		Open failure
Alert ID:		CAF3 C58A
Hierarchy/ resource list:				Second name is ring name
Probable causes:		3703		Token ring fault domain
Failure causes:		3703		Token ring fault domain
Recommended actions:		1009		Try reopening adapter after 30 seconds
		3301		If problem persists do the following:
		2010		Review link detailed data
		3101		Contact token ring administrator for this LAN
		32C0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
Detailed data:		07		Data ID: error code
		hh hh		Error code

Adapter Open Error: Duplicate Address Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		3211		Open failure
Alert ID:		D615 A61E
Probable causes:		3704		Token ring duplicate station address
Install causes:		3704		Token ring duplicate station address assigned
Recommended actions:		2010		Review link detailed data
		3101		Contact token ring administrator for this LAN
		32C0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
Detailed data:		07		Data ID: error code
		hh hh		Error code
LAN LCS:				Local individual MAC address

System Action: Operator Caused LAN Adapter to Be Reset Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		3211		Open failure
Alert ID:		F7A6 2F59
Probable causes:		7001		Resources not active
User causes:		3300		Adapter not ready
Recommended actions:		1300		Correct then retry
		2010		Review link detailed data
		3101		Contact token ring administrator for this LAN
		32A0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
LAN LCS:				Ring identifier local individual MAC address

Network Status Error: Lobe Wire Fault Alert

Name of subvector		Hexadecimal value in subvector		Description
Hierarchy/ resource list:				Second name is ring name
Alert description:		3212		Wire fault
Alert ID:		A676 B230
Probable causes:		3702		Token ring lobe
Failure causes:		3711		Local access unit
		3434		Local lobe cables
		3320		Local token ring adapter
Recommended actions:		2010		Review link detailed data
		3101		Contact token ring administrator for this LAN
		32C0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
Detailed data:		17		Data ID: ring status code
		hh hh		Ring status code
LAN LCS:				Local individual MAC address

Network Status Error: Auto-Removal Alert

Name of subvector		Hexadecimal value in subvector		Description
Hierarchy/ resource list:				Second name is ring name
Alert description:		3213		Auto-removal
Alert ID:		EB61 E14F
Probable causes:		3702		Token ring lobe
Failure causes:		3320		Local token ring adapter
		3711		Local access unit
		3434		Local lobe cables
Recommended actions:		2010		Review link detailed data
		3101		Contact token ring administrator for this LAN
		32C0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
Detailed data:		17		Data ID: ring status code
		hh hh		Ring status code
LAN LCS:				Local individual MAC address
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
Detailed data:		17		Data ID: ring status code
		hh hh		Ring status code
LAN LCS:				Local individual MAC address

Network Status Error: Token Ring Remove Adapter Command Received Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		3214		Remove adapter command received
Alert ID:		59F3 2622
Probable causes:		7013		LAN Manager operator
User causes:		7101		Token ring remove adapter command received
Recommended actions:		2010		Review link detailed data
		3101		Contact token ring administrator for this LAN
		32C0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
Detailed data:		17		Data ID: ring status code
		hh hh		Ring status code
LAN LCS:				Ring identifierLocal individual MAC address

Network Status Error: LLC Remove Adapter Command Received Alert

Name of subvector		Hexadecimal value in subvector		Description
Hierarchy/ resource list:				Second name is remote node CP name
Alert description:		3300		Link error
Alert ID:		5B8F 5BA7
Probable causes:		2017		LAN LLC communications/remote node
Failure causes:		2107		LAN LLC communications/remote node
		F017		Poll count exhausted
Recommended actions:		3301		If problem persists do the following:
		2010		Review link detailed data
		3103		Contact LAN administrator responsible for this LAN
		32A0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
LAN LCS:				Ring identifierLocal individual MAC addressRemote individual MAC addressLAN routing information
LCS configuration:				Remote device addressLocal device address
Link Station Datasubvector included

DLC Status Error: Link Lost Alert

Name of subvector		Hexadecimal value in subvector		Description
Hierarchy/ resource list:				Second name is remote node CP name
Alert description:		3300		Link error
Alert ID:		9921 0A2B
Probable causes:		3321		Remote token ring adapter
Failure causes:		3321		Remote token ring adapter
Recommended actions:		2010		Review link detailed data
		3101		Contact token ring administrator for this LAN
		32A0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
LAN LCS:				Ring identifierLocal individual MAC addressRemote individual MAC addressLAN routing information
LCS configuration:				Remote device addressLocal device address

DLC Error: Remote Station Not On Local or Attached Rings Alert

Name of subvector		Hexadecimal value in subvector		Description
Hierarchy/ resource list:				Second name is remote node CP name
Alert description:		3305		Unable to communicate with remote node
Alert ID:		D91B 9E2D
Probable causes:		2007		LAN LLC communications
		1023		Communications program in remote node
User causes:		0209		Remote device power off
Recommended actions:		0200		Check power
Failure causes:		1023		Communications program in remote node
Recommended actions:		3301		If problem persists do the following:
		2010		Review link detailed data
		3101		Contact token ring administrator for this LAN
		32A0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
LAN LCS:				Ring identifierLocal individual MAC addressRemote individual MAC addressLAN routing information
LCS configuration:				Remote device addressLocal device address

Adapter Command Error: Storage Capacity Exceeded Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		5003		Capacity exceeded
Alert ID:		9C35 13D5
Probable causes:		0101		Main storage
Failure causes:		0110		Storage control
Recommended actions:		2010		Review link detailed data
		3103		Contact LAN administrator responsible for this LAN
		32C0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
Detailed data:		03		Data ID: adapter return code
		hh		Adapter return code
LAN LCS:				Ring identifierLocal individual MAC address

Adapter Check Error: Receive Queue Overrun Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		5012		Receive queue overrun
Alert ID:		14D5 3710
Probable causes:		1000		Software program
Failure causes:		1000		Software program
Recommended actions:		2010		Review link detailed data
		3101		Contact token ring administrator for this LAN
		32A0		Report the following data:
				Product Set ID index subfield included
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
LAN LCS:				Ring identifierLocal individual MAC address

Adapter Check Error: Microcode Program Abnormally Terminated Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		6000		Microcode program abnormally terminated
Alert ID:		E1EC 74A7
Probable causes:		3320		Local token ring adapter
Failure causes:		3320		Local token ring adapter
Recommended actions:		2010		Review link detailed data
		3101		Contact token ring administrator for this LAN
		32C0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
Detailed data:		07		Data ID: error code
		hh hh		Error code
LAN LCS:				Ring identifierLocal individual MAC address

Adapter Command Error: Configuration Alert

Name of subvector		Hexadecimal value in subvector		Description
Alert description:		8000		Configuration error
Alert ID:		B8AB EF98
Probable causes:		7001		Local system operator
Install causes:		1501		Incorrect customization parameters
		1400		Mismatch between hardware and software
Recommended actions:		3110		Contact communications systems programmer
		32C0		Report the following data:
Detailed data:		61		Data ID: adapter number
		hh		Adapter number
Detailed data:		03		Data ID: adapter return code
		hh		Adapter return code


Link Statistics
Network Management	8 of 19

Link Statistics

For SDLC and token ring connections, SNA Server maintains statistics on link usage and errors. This information is logged when a connection ends or when the counter for a particular error or time-out reaches its maximum value.


Format for Link Statistics
Network Management	9 of 19

Link Statistics

Format for Link Statistics

When an SDLC or token ring connection ends, or when an error counter reaches its maximum value, statistics on link usage are recorded. These statistics include information such as the adapter number, the date and time the link was established, and counts of errors and time-outs. This data is also logged in NMVT format if a connection has been specified for carrying NetView data, and is then sent if that connection and the server that owns that connection are both active.

SDLC Link Statistics

Link statistics are generated when a link is closed or when one of the wrap counters listed later in this section is about to wrap. Whenever a link statistics message is built, all the wrap counters are reset to 0. The cumulative counters are not reset, and provide statistics from the point at which the particular link service was started.

The NMVT generated has the following format:

NMVT Header

41 03 8D 00 00 00 00 00	NMVT Header

Major Vector Header

00 69	Length of major vector

00 25	Link Statistics major vector

Data Link Traffic Counters Subvector

65 9A	Data Link Traffic Counters subvector

03	DLC type: SDLC

hh	Adapter number (01+04)

Date/Time Link Established

hh	Date

hh	Month

hh hh	Year

hh	Hour

hh	Minute

hh	Second

hh	Hundredths of a second

hh	Counter

Wrap Counters

hh	Transmit I-frames OK

hh	Transmit I-frames not OK

hh	Retransmit I-frames

hh	Received I-FCS OK

hh	Received I-FCS not OK

hh	Total frames sent

00	Reserved

hh	Lost data frames received

hh	FRMR conditions sent

00	Reserved

hh	CTS drop

00	Reserved

00	Reserved

hh	DSR drop out

hh	Inactivity timeouts

00	Reserved

hh	DMA underruns

00	Reserved

hh	Transmit fail timeouts

00	Reserved

Cumulative Counters

The cumulative counters are the same counters as the wrap counters, with reserved bytes in the same positions.

Token Ring Link Statistics

Link statistics are generated when a link is closed or when one of the following counters is about to wrap. Whenever a link statistics message is built, all the counters are reset to 0.

The NMVT generated has the following format:

NMVT Header

41 03 8D 00 00 00 00 00	NMVT Header

Major Vector Header

00 32	Length of major vector

00 25	Link Statistics major vector

Data Link Traffic Counters Subvector

2E9A	Data Link Traffic Counters subvector

04	DLC type: token ring

01 or 02	Statistics type: link counter overflow or adapter counter overflow

Token Ring Adapter Log Information and Counters

hh	Adapter number (01+04)

00	Reserved

hh	Line error

hh	Internal error

hh	Burst error

hh	ARI/FCI error

hh	End delimiter

00	Reserved

hh	Lost frame

hh	Receive congestion

hh	Frame copied error

hh	Frequency error

hh	Token error

00 00 00	Reserved

DLC SAP Station Information

hh hh hh hh	Count of frames transmitted OK

hh hh hh hh	Count of frames received OK

hh hh hh hh	Count of frames discarded

hh hh hh hh	Lost data

hh hh	Buffer available in SAP

DLC Link Station Information

hh hh	Count of I-frames transmitted

hh hh	Count of I-frames received

hh	Received I-frames error count

hh	Transmitted I-frames error count

hh hh	T1 timer expired count


Alerts Used by Applications, NVAlert, and NVRunCmd
Network Management	10 of 19

Alerts Used by Applications, NVAlert, and NVRunCmd

Application programs and the NVAlert and NVRunCmd services can generate alerts using the Common Service Verb (CSV) TRANSFER_MS_DATA. An application or service can supply subvectors, which are required to build an NMVT, or it can supply the complete NMVT; in both cases the completed NMVT will be logged locally, and may also be sent on the connection designated for NetView if one is configured and is active. An application or service can also supply user-defined alert data, in which case the data will be logged locally but cannot be sent.

For information about how the NVAlert and NVRunCmd services work, see the Microsoft SNA Server Administration Guide.


Format for Alerts Used by Applications, NVAlert, and NVRunCmd
Network Management	11 of 19

Alerts Used by Applications, NVAlert, and NVRunCmd

Format for Alerts Used by Applications, NVAlert, and NVRunCmd

An application program or the NVAlert and NVRunCmd services can use the CSV TRANSFER_MS_DATA to issue alerts. The alerts are logged in a log file that can be viewed using the Windows NT Event Viewer, and may also be sent on the NetView connection.

The data supplied to TRANSFER_MS_DATA may be in any of the following formats.

NMVT

The application or service supplies a complete NMVT, including the header information.

ALERT_SUBVECTORS

The application or service supplies the subvectors required for an alert, but without the NMVT header or major vector header. SNA Server adds the header information, as described in the next section.

PDSTATS_SUBVECTORS

The application or service supplies the subvectors required for a Problem Determination Statistics NMVT, but without the NMVT header or major vector header. SNA Server adds the header information, as described in the next section.

USER_DEFINED

The application or service supplies data in its own format. This data cannot be sent on the connection designated for NetView, but is logged in the same way as the other data formats.

The application or service can also request SNA Server to add the Product Set ID subvector (for all data types except user_defined), the Date/Time subvector, or both to the supplied data. The format of these added subvectors is described in the next section.

For all data types, the data (with added headers and subvectors, if appropriate) is logged locally in NMVT format, whether or not a connection has been specified for NetView.

Added Headers and Subvectors

NMVT Header

41 03 8D 00 00 00 00 00	NMVT Header

Major Vector Header

LL LL	Length of Major Vector

00 00 or 00 25	Alert major vector (for data type alert_subvectors), or Problem Determination Statistics major vector (for data type pstats_subvectors)

Product Set ID Subvector
4D 10		Product Set ID subvector
00		Unused field
34 11		Product ID subvector
0C		Product classification: non-IBM software
08 04		Software product common level subfield
F0 F2		Version identifier: 02
F0 F0		Release identifier: 00
F0 F0		Modification identifier: 00
20 06		Software product common name subfield
C4 C3 C1 61 D4 E2 40C3 D6 D4 D4 40E2 C5 D9 E5 D9		Product name:MSSNA Server
00 .. 00		Name padded with nulls to 30 characters
09 08		Software product program number subfield
F0 F0 F0 F0 F0 F0 F0		Product program number: zeros
16 11		Product ID subvector
03		Product classification: hardware
13 00		Hardware Product ID subfield
00		Format type: undefined
hh...hh		Server: Windows NTbased computer name
Date/Time Subvector
0A 01		Date/Time Subvector
08 10		Local Date/Time subfield
hh		Year — two digits
hh		Month
hh		Date
hh		Hours
hh		Minutes
hh		Seconds


Response Time Monitor
Network Management	12 of 19

Response Time Monitor

During 3270 emulation, statistics are maintained on the time taken for the host to respond to 3270 client requests. RTM data can be sent to the host for collection and analysis; the 3270 user can also view a graphical display of the spread of response times on a particular 3270 emulation session. The time for the last transaction executed can also be displayed on the status line.

Use the SNA Server Admin program to choose the way in which response times are measured and classified. RTM statistics for a particular LU are sent to the host that owns that LU rather than being sent on the connection designated for NetView data.


Collecting RTM Data and Sending it to the Host
Network Management	13 of 19

Response Time Monitor

Collecting RTM Data and Sending it to the Host

SNA Server always collects RTM data while 3270 emulation is active. The data for each 3270 LU will then be sent to the host to which the LU is connected under various criteria.

You configure the initial criteria for SNA Server to send RTM data to the host when any of the RTM counters reaches its maximum value, and/or each time a 3270 session ends. (For instructions on configuring the RTM function, see the Microsoft SNA Server Administration Guide.) The RTM counters are reset each time the RTM data is sent in this way.

Although initial criteria apply to all SNA Server LUs, any host can change the criteria for any LU or all LUs it owns, and solicit or reset any LU counters.


Boundaries and Measurement Definition
Network Management	14 of 19

Response Time Monitor

Boundaries and Measurement Definition

RTM data is collected by comparing host response times against a series of four boundary values. Each time a host transaction occurs, the response time is compared with the boundary values, and the appropriate counter is incremented. There is a counter for each of the four intervals defined by the boundary values, and an overflow counter for response times above the largest boundary value.

You can change the default boundaries — 0.5, 1, 2, and 5 seconds — using the SNA Server Admin program. You also can select which of three response time definitions to set as default. For instructions, see the Microsoft SNA Server Administration Guide.

The response time is measured from the time the user presses Enter until one of the following events occurs:

The first character of host data reaches the 3270 display.

The keyboard is unlocked.

The user is allowed to send data.

Again, a host can override the default boundaries and other host response time settings for any LU or all LUs it controls. (For more information, see "Host Modification of RTM Parameters" later in this chapter.)


Local Display
Network Management	15 of 19

Response Time Monitor

Local Display

You can use the SNA Server Admin program to allow a 3270 user to view the last transaction time on the status line and a graphical display of the response times for each 3270 display session. For instructions, see the Microsoft SNA Server Administration Guide. Again, the host can override this ability to view the RTM data locally.


Reuse of LUs by Different Users
Network Management	16 of 19

Response Time Monitor

Reuse of LUs by Different Users

Response times are recorded for a specific LU rather than for a specific 3270 session. This means that if a 3270 session ends and another session (of the same or a different 3270 user) then uses the same LU, the response time counters will include responses from the previous session as well as those from the new session. This does not happen, however, if the RTM counters were reset before the new session began to use the LU (the counters are reset when the host requests that they be reset or when RTM data is sent unsolicited by SNA Server). When hosts request RTM data they typically also request that the counters be reset.

If you want to ensure that the RTM data displayed relates only to the current 3270 session, you should select the RTM Data Sent at End-of-Session checkbox when configuring RTM parameters for SNA Server. This will ensure that the RTM counters are reset at the end of each 3270 session and will therefore be 0 at the start of each 3270 session. The host can, of course, override this setting.


Host Modification of RTM Parameters
Network Management	17 of 19

Response Time Monitor

Host Modification of RTM Parameters

Although you can configure the RTM boundaries and definition that you want to use on your SNA server, the host can override these configured values, either for an individual 3270 LU or for all LUs it controls. The host can also specify whether to permit local display of RTM data, and, when SNA Server sends RTM data, it can disable collection of RTM statistics completely.


Lost-Data Indicator
Network Management	18 of 19

Response Time Monitor

Lost-Data Indicator

When SNA Server sends RTM data to the host, it can indicate to the host that RTM data may have been lost (that is, some host response times were not included in the RTM data sent to the host). This indication is sent in the following cases:

One of the RTM counters reaches its maximum value, and SNA Server is not configured to send RTM data unsolicited at counter overflow. When this occurs, SNA Server stops recording response times until the host requests the data (or until end-of-session, if unsolicited sending at end-of-session is configured); the data is sent with an indication that data may have been lost due to counter overflow.

When the local server terminates abnormally, RTM data obviously is lost and any connection to the host is terminated. When the connection to the host is started, there is no way of knowing whether the connection was previously terminated by a server failure; therefore, the first RTM data sent to the host after the connection is established includes the lost-data indicator, to indicate that data may have been lost due to failure of the local server.

When SNA Server is configured to send RTM data at end-of-session, and a new 3270 session is started before the RTM data for the previous 3270 session on the same LU can be sent, response times for the new session are discarded until the RTM data from the previous session is sent and the counters are reset. When RTM data is next sent on the new session, it includes the lost data indicator to indicate this condition.


Local Logging of Network Management Data
Network Management	19 of 19

Local Logging of Network Management Data

Data is logged in a Windows NT Event Viewer log file in two ways. First, the data from the alert is logged in a more readable format, using standard log messages. The format is specific to the alert type; for the message numbers used and explanations of the data, see the section in this chapter that relates specifically to that type of alert.

If a connection has been designated for carrying NetView data and the server that owns the connection is active, the alert NMVT containing the data is also logged in NMVT format as it would be sent. The NMVT appears as message 540 followed by message 541. Note that this logging occurs before SNA Server attempts to send the NMVT; the log is therefore no guarantee that the NMVT is sent successfully.

Additional information about local logging of alert information is presented in the section of this chapter that relates specifically to that type of alert.


Error Messages
Chapter 3	1 of 1

Error Messages

This chapter lists the messages that are logged in the event log for SNA Server.

Message 1

(value) Protocol Violation

EXPLANATION: A remote node generated an SNA protocol violation on an SNA network. The remote system may have a configuration or internal logic error.

SUBCODE INFORMATION:

X'1120'  The node received an SNA message that contains only a Transmission Header (TH).  No request header or request unit is present.

X'1121'  The node received an SNA message with an invalid TH.

X'1122'  Segmentation error: the first segment of a received SNA message did not contain a Request Header (RH).

X'1131'  The node received a Network Control request.  This is an invalid request category; Network Control requests are not supported.

X'1134'  The node received an SNA message containing an unsupported Session Control request.

X'1135'  The node received an SNA message containing an unsupported Session Control response.

X'1175'  The node received an SNA message containing an unsupported Change Number of Sessions (CNOS) request.

X'1185'  The node received an SNA message containing an unsupported network management request or subvector.

X'118D'  The node received an SNA message containing an error in BIND request unit from partner LU.

X'11D0'  The node received an error in an LU 6.2 SNA request message from a partner LU.  A SEND indication (CD) was expected but not received by the node.

X'11D1'  The node received an error in an LU 6.2 SNA error data GDS variable from a partner LU.

X'11D2'  The node received an error in an LU 6.2 SNA message from a partner LU (unexpected reporting of mapping error).

X'11D3'  The node received an error in an LU 6.2 message from a partner LU (an invalid return code was generated from an FMH-7).

ACTION: Provide network support personnel with the event log file(s) related to SNA, SNA trace file(s), and the number and description of the displayed subcode. For information about SNA log and trace files, see the Microsoft SNA Server Administration Guide.

Message 2

(value) Internal Error

EXPLANATION: An internal logic error occurred. These subcodes should never occur during normal operation.

SUBCODE INFORMATION:

X'1'  An invalid message was sent by the SNA Server Admin program to a local SNA server on the internal administration connection.

X'2'  An unknown component has attempted to log an error.

X'6'  The administration connection between the SNA Server Admin program and the local SNA server (node) was lost while processing a command from the SNA Server Admin program.

X'7'  Error in the format of the message sent from the SNA Server Admin program to the local SNA server (node).

X'8'  Buffer shortage or queue length exceeded. The administration connection between the SNA Server Admin program and the node has been damaged.

X'11E0'  The local SNA server (node) has found an error in its internal count of the number of messages in transit internally.

ACTION: Provide network support personnel with the event log file(s) related to SNA, SNA trace file(s), and the number and description of the displayed subcode. For information about SNA log and trace files, see the Microsoft SNA Server Administration Guide.

Message 3

(value) Node Configuration Error

EXPLANATION: The SNA server (node) detected a configuration file problem caused by a logic error in the configuration program. These subcodes should not occur during normal operation.

SUBCODE INFORMATION:

X'1100'  Incorrect Record Reference Number.

X'1101'  Invalid length of product data record.

X'1102'  Number of configured control blocks is valid.

X'1103'  Error detected while resetting a control block.

X'1106'  Configuration file is corrupted.

X'1107'  Operator interface queue thresholds invalid.

X'1173'  The SNA Server Admin program is not configured to allow permission to change session limits.

X'117A'  Not enough room in configuration table.

ACTION: Provide network support personnel with the SNA Server configuration file. For information about the configuration file, see the Microsoft SNA Server Administration Guide.

Message 4

(value) Message Sequence Error

EXPLANATION: The SNA server (node) received an invalid or unexpected message from a remote node on an SNA session. The remote system has a possible configuration or internal logic error.

SUBCODE INFORMATION:

X'1130'  SNA pacing count error. The pacing count held exceeds the receive pacing window specified in the BIND, caused by a remote LU sending more than one pacing request within the window.

X'1132'  The node received an FMD or DFC request when the data traffic state was not active.

X'1133'  The node received a request with an invalid sequence number.

X'1139'  The node received an STSN session control request while there was active data traffic on the session.

X'1182'  The node received a BIND response when no BIND request was outstanding.

X'1183'  The node received an UNBIND request for an inactive session, or an UNBIND response when no UNBIND request was outstanding.

X'11B2'  The node received an unexpected BIS reply from a partner LU.

X'11B3'  The node received an unexpected BIS request from a partner LU.

X'11B5'  The node received an unexpected RTR from a partner LU.

ACTION: Provide network support personnel with the event log file(s) related to SNA, SNA trace file(s), and the number and description of the displayed subcode. For information about SNA log and trace files, see the Microsoft SNA Server Administration Guide.

Message 5

(value) Unsupported Session Control Request

EXPLANATION: The SNA server (node) received an unexpected session control request. This is a protocol violation by the remote system. The remote system has a serious configuration or internal logic problem.

SUBCODE INFORMATION:

X'1137'  The node received an SDT session control request.

X'1138'  The node received an STSN session control request.

X'113A'  The node received an RQR session control request.

ACTION: Provide network support personnel with the event log file(s) related to SNA, SNA trace file(s), and the number and description of the displayed subcode. For information about SNA log and trace files, see the Microsoft SNA Server Administration Guide.

Message 6

(value) Internal Network Management Logic Error (rc = value)

EXPLANATION: The SNA server (node) detected a run-time error or resource shortage caused by internal logic errors in the SNA Server Admin program, the Common Service Verbs, or the 3270 emulator.

SUBCODE INFORMATION:

X'1184'  Insufficient resources for concurrent network management activity. This is probably an SNA Server Admin program logic error, but can be caused by a large number of applications simultaneously issuing TRANSFER_MS_DATA.

X'118A'  LU name specified by SNA Server Admin not found.

X'118B'  Unexpected message.

ACTION: Provide network support personnel with the event log file(s) related to SNA, SNA trace file(s), and the number and description of the displayed subcode. For information about SNA log and trace files, see the Microsoft SNA Server Administration Guide.

Message 7

APPC session activation failure: LU inactive

Connection  = value

LU alias  = value

PLU alias  = value

Mode name  = value

LU address  = value

EXPLANATION: The SNA server (node) failed to activate an APPC session because the host has not sent an ACTLU request to the local dependent APPC LU. This error usually happens as the result of a mismatch between the host configuration and the SNA Server configuration.

Message 8

(value) Internal Protocol Violation

EXPLANATION: A protocol violation has occurred at the interface between the SNA server (node) and another SNA component (for example, the emulator or link service).

SUBCODE INFORMATION:

X'1105'  Insufficient space to copy data into node buffer.

X'1112'  Received unknown message type at the node interface.

X'1144'  Received illegal message at the node interface.

X'1151'  Received unrecognized message from the link service component.

X'1174'  Received invalid session limits message from the SNA Server Admin program.

X'1175'  Received invalid CNOS command.

X'1188'  Received invalid CNMS message.

ACTION: Provide network support personnel with the event log file(s) related to SNA, SNA trace file(s), and the number and description of the displayed subcode. For information about SNA log and trace files, see the Microsoft SNA Server Administration Guide.

Message 9

(value) Internal Message Sequence Error

EXPLANATION: Invalid or unexpected message received by the SNA server (node) from another SNA Server component (for example, the emulator or link service).

SUBCODE INFORMATION:

X'1111'  Received message from unrecognized component.

X'1117'  Received an invalid message from a 3270 emulator.

X'1160'  Unexpected response from link service.

X'1161'  Unexpected message from link service.

X'1180'  Unexpected message from emulator.

X'1181'  Mode inconsistency: close received when not expected.

ACTION: Provide network support personnel with the event log file(s) related to SNA, SNA trace file(s), and the number and description of the displayed subcode. For information about SNA log and trace files, see the Microsoft SNA Server Administration Guide.

Message 10

(value) Resource Allocation Error

SUBCODE INFORMATION:

X'1179'  An APPC session activation request from an unknown remote LU or an unknown mode (which would normally have been accepted using an implicit incoming remote LU or mode) could not be accepted. Either there was insufficient Windows NT memory available (system RAM or hard disk), or the maximum number of active APPC modes or remote LUs has already been reached.

ACTION: Try to free up Windows NT system memory and then retry. If the problem persists, provide network support personnel with the event log file(s) related to SNA, SNA trace file(s), and a description of how many sessions and services were running when the problem occurred. For information about SNA log and trace files, see the Microsoft SNA Server Administration Guide.

Message 11

(value) Initialization Failure

EXPLANATION: This is an internal logic error in SNA Server, related to the configuration.

SUBCODE INFORMATION:

X'1177'  Operator queues are full — messages have been lost.

X'1178'  Insufficient resources for automatic session limit negotiation.

ACTION: Provide network support personnel with the event log file(s) related to SNA, SNA trace file(s), and the number and description of the displayed subcode. For information about SNA log and trace files, see the Microsoft SNA Server Administration Guide.

Message 12

(value) Negative Response from Remote System (SENSE = value)

SUBCODE INFORMATION:

X'1118'  The local SNA server (node) received an SNA negative response on an SNA session from a remote system, which indicates a protocol violation by the 3270 emulator. The SNA sense code shown gives details of the type of error. See IBM Systems Network Architecture: Formats for an explanation of the sense code.

ACTION: If the error is accompanied by functional problems, use internal tracing to determine the cause of the problem. If the problem is associated with use of a user application (HLLAPI or APPC), report it to the application developer. Otherwise, check the SNA Server configuration, especially the configuration of the 3270 LU, and see that it corresponds to the configuration of the remote system.

If the problem persists, provide network support personnel with the event log file(s) related to SNA, SNA trace file(s), and the number and description of the displayed subcode. For information about SNA log and trace files, see the Microsoft SNA Server Administration Guide.

Message 13

(value) Message Sequence Error (SENSE = value)

EXPLANATION: The SNA server (node) received an invalid or unexpected message from a remote node during an SNA session. The cause is probably a logic error in the remote system. The SNA sense data shown gives details of the type of error.

SUBCODE INFORMATION:

X'1141'  Session-level protocol violation in an SNA message from the partner LU.

X'1142'  Session-level protocol violation on host SSCP-to-LU session.

X'11B1'  A BID request has failed the SNA receive request checks.

X'11C2'  A partner LU has violated LU 6.2 protocols.

ACTION: See IBM Systems Network Architecture: Formats for an explanation of the SNA codes. Provide network support personnel with the event log file(s) related to SNA, SNA trace file(s), and the number and description of the displayed subcode. For information about SNA log and trace files, see the Microsoft SNA Server Administration Guide.

Message 14

APPC session activation failure: INITSELF negative response received

Sense data  = value

Connection  = value

LU alias  = value

PLU alias  = value

Mode name  = value

LU address  = value

EXPLANATION: An APPC session has failed to activate because the host has rejected the SNA INITSELF request sent to initiate the session. The sense data contains more information about the reason for the rejection.

This error is usually caused by a mismatch between the host configuration and the SNA Server configuration. It may  also be caused by some temporary error at the host (for example, the partner LU may be temporarily unavailable).

Message 15

APPC session activation failure: host session set-up error

Sense data  = value

Connection  = value

LU alias  = value

PLU alias  = value

Mode name  = value

LU address  = value

TH  = value

RH  = value

RU  = value

EXPLANATION: An APPC session has failed to activate because the host has sent an SNA NOTIFY request indicating a problem connecting to the partner LU. The sense data contains more information about the reason for the failure.

This error is usually caused by a temporary error at the host (for example, in a multi-domain SNA network, the connection between the SSCP host and the host containing the partner LU may have failed). This error may also be caused by a mismatched configuration.

ACTION: Provide network support personnel with the information contained in this message.

Message 16

Invalid NOTIFY received on APPC LU-SSCP session

Sense data  = value

Connection  = value

LU name  = value

LU address  = value

Mode name  = value

TH  = value

RH  = value

RU  = value

EXPLANATION: An SNA NOTIFY request containing an invalid key, status field, or procedure correlator has been received from the host.

ACTION: Stop the session and restart with tracing on. Use entries in the trace file to help you and the host administrator determine the problem. For information about trace files, see the Microsoft SNA Server Administration Guide.

Message 17

APPC session activation failure: BIND negative response sent

Sense data  = value

Connection  = value

Session ID  = value

LFSID  = value

TH  = value

RH  = value

RU  = value

EXPLANATION: An APPC session has failed to activate because an error was detected in the SNA BIND request sent by the partner LU. The sense data gives more information about the nature of the error.

This error is usually caused by a mismatch between the SNA Server configuration and the configuration of the partner LU's system (for example, the mode name specified in the SNA BIND request may not be configured in SNA Server).

ACTION: Provide network support personnel with the information contained in this message.

Message 18

APPC session activation failure: BIND negative response or UNBIND request received

Sense data  = value

Connection  = value

LU alias  = value

PLU alias  = value

Mode name  = value

EXPLANATION: An APPC session has failed to activate because the partner LU rejected the SNA BIND request sent to initiate the session. The sense data gives more information on the reason for the rejection.

This error is usually caused by a mismatch between the SNA Server configuration and the configuration of the partner LU's system (for example, the mode name sent in the SNA BIND request was not acceptable to the partner LU).

ACTION: Provide network support personnel with the information contained in this message.

Message 19

(value) Security Violation: local LU = value, remote LU = value

EXPLANATION: This message may indicate that an unauthorized remote user is attempting to access your programs from a remote LU that imitates the remote LU that you configured.

SUBCODE INFORMATION:

X'11B4'  The remote LU sent incomplete security key data for session-level security or has used the wrong key.

ACTION: Check that the remote LU is configured to use session-level security and is using the correct security key, that is, the same session-level security password that is configured for the remote APPC LU in the local SNA Server configuration.

Message 20

(value) Negative Response Received on Connection value (SENSE = value)

SUBCODE INFORMATION:

X'1123'  Received and logged a negative response. This error is usually followed by a more specific error message from the SNA Server component processing the negative response.

ACTION: Look up the sense code in IBM Systems Network Architecture: Formats. If the sense code indicates a serious problem, contact support personnel for your network.

Message 21

(value) Negative Response Sent on Connection value (SENSE = value)

SUBCODE INFORMATION:

X'1124'  A negative response was sent and logged. This error normally follows a more specific error message, depending on the type of negative response sent and its cause. The SNA sense data provides details about the type of error.

ACTION: See IBM Systems Network Architecture: Formats for an explanation of the sense data.

Message 22

APPC session activation failure: BIND negotiated parameters unacceptable

Sense data  = value

Connection  = value

LU alias  = value

PLU alias  = value

Mode name  = value

LFSID  = value

TH  = value

RH  = value

RU  = value

EXPLANATION: An APPC session has failed to activate because the partner LU negotiated some parameters in the BIND, and the resulting values were unacceptable to the local LU. The sense data gives more information about which field was in error.

This error is usually caused by a mismatch between the SNA Server configuration and the configuration of the partner LU's system (for example, the maximum RU size requested by the partner LU may be smaller than the minimum RU size allowed by SNA Server).

ACTION: Provide network support personnel with the information contained in this message.

Message 23

Connection value using Link Service value failed

Qualifier = value

SUBCODE INFORMATION:

X'1152'

A link service reported a connection failure to the node.

When this error continues to occur during connection establishment, it is due to a mismatch between the parameters specified in the SNA Server Admin program and either the local hardware, the physical connection, or the remote system configuration.

If the problem occurs during data transfer, it can be due to an unreliable physical connection (such as noise on an SDLC line) or faulty hardware.

Return codes for different link service types are shown in the following sections.

SDLC Connections

The following are return codes for SDLC connections.

X'10'

All the link services configured for use by the connection were inactive.

X'16'

The link service has been terminated, either by a failure or by an operator action. If the termination is due to a failure, there should be other messages logged giving reasons for the failure. Check the actions for these messages.

X'87'

An invalid SDLC frame was received. This is a protocol error generated by the remote system.

X'89'

RD received. The remote system requested disconnection.

The next three codes indicate that the modem is disconnected or the remote system dropped the line.

X'11'

Data Set Ready (DSR) failure.

X'12'

Clear To Send (CTS) failure.

X'14'

Data Carrier Detect (DCD) failure.

The next three codes indicate that the remote end is inactive but has not broken the modem connection or that there is a very poor-quality line.

X'24'

Non-productive receive retry exceeded.

X'25'

Idle time-out retry exceeded.

X'29'

Connection problem.

The next two codes indicate a local hardware problem. Check the modem and adapter.

X'2D'

Abnormal response.

X'2E'

Write time-out retry exceeded.

The next three codes indicate that the remote end returned to initialization state.

X'15'

Connection terminated by host.

X'80'

DM received in Information Transfer state.

X'88'

RIM received.

The next four codes indicate that the remote end did not reply during a contact or disconnect attempt.

X'81'

Disconnect retry limit.

X'82'

Contact retry limit.

X'84'

No response retry limit. The remote end is not answering polls.

X'85'

Remote busy retry limit. The remote end failed to come out of "receiver not ready" (RNR) state.

X.25 Connections

The following are return codes for X.25 connections.

X'37'

Loss of a virtual circuit.

X'60'

The switched virtual circuit to the host has been cleared down (broken) either by the host or by the X.25 network itself.

X'61'

The permanent virtual circuit to the host has been reset (broken) either by the host or by the X.25 network itself.

X'62'

An attempt to connect to the host through a switched virtual circuit has failed.

Token Ring Connections

The next three codes indicate a problem with the remote node (contact support personnel for your network).

X'29'

Remote node not active.

X'AE'

DISC/DM received.

X'AF'

Link lost.

The next three codes indicate a protocol violation on the LAN.

X'AB'

SABME received while connection active.

X'AC'

FRMR sent.

X'AD'

FRMR received.

DFT Connections

The DFT outage codes are derived from the line check codes generated by the 3X74 control unit. The line check code will have been logged on a previous #261 message. Take the outage code from the message, convert it to decimal, and add 484 to it. The result is the line check code. Here is an example: an outage code of 11 converts to 17 in decimal. 484 + 17 = 501, which is the line check code. Look up the line check code in the maintenance information manual for your control unit and follow the actions indicated there.

X'11'

Data Set Ready (DSR) failure.

X'14'

Data Carrier Detect (DCD) failure.

X'15'

Connection terminated by host.

ACTION: Check the return code shown, any events logged by the link service, and the local configuration and hardware to determine what the problem is. If the frequency of the problem is unacceptable, contact network support personnel.

Message 24

APPC session activation failure: connection failed

Connection  = value

LU alias  = value

PLU alias  = value

Mode name  = value

EXPLANATION: An APPC session has failed to activate because the connection has failed.

ACTION: Check event log entries for the reason for the connection failure, correct the errors, and retry the session activation.

Message 25

APPC session activation failure: connection disabled

Connection  = value

LU alias  = value

PLU alias  = value

Mode name  = value

EXPLANATION: An APPC session has failed to activate because the connection was configured to be started "By Administrator," and it has not been started.

ACTION: If the session is required, activate the connection and retry the session.

Message 26

APPC session activation failure: session limit error

Connection  = value

LU alias  = value

PLU alias  = value

Mode name  = value

EXPLANATION: An APPC session has failed to activate because the session limits for the mode have not been negotiated correctly. This error is usually caused by a mismatch between the SNA Server configuration and the configuration of the partner LU's system (for example, the requested mode's session limits may not be configured to correspond to the local mode's limits).

ACTION: Correct the configuration error or contact support personnel for your network.

Message 27

Connection activated successfully

Connection = value

EXPLANATION: The connection was activated, either because an administrator activated it, or because it was needed for activating a session. No action is necessary.

Message 28

Connection deactivated normally

Connection = value

EXPLANATION: The connection was deactivated, either because an administrator deactivated it, or because no more sessions were using it. No action is necessary.

Message 29

Internal Gateway error

Sense code = value

Parameter 1 = value

Parameter 2 = value

Parameter 3 = value

Parameter 4 = value

Parameter 5 = value

Parameter 6 = value

EXPLANATION: An internal error has occurred in the SNA Server gateway function.

ACTION: Provide network support personnel with the information contained in this message.

Message 30

(value) Conversation Error

SUBCODE INFORMATION:

X'1172'  An LU conversation being used by SNA Server Admin to establish session limits with a partner LU has failed. Messages following this message will indicate the reasons for the failure.

ACTION: Check the other error messages and follow the actions specified for them.

Message 31

(value) SNA Server Admin command failure, rc = value

EXPLANATION: A command issued by SNA Server Admin failed.

SUBCODE INFORMATION:

X'06'

COMMAND_IN_PROGRESS: This code should not normally occur.

X'07'

COMMAND_NOT_RECOGNIZED: This code should not normally occur.

X'09'

SESSION_ACTIVATION_FAILED: An attempt to start an APPC session via SNA Server Admin failed. This log is accompanied by one of the APPC session activation failure messages (message 7, 14, 15, 17, 18, 22, 24, 25, or 26). These messages provide more information about the failure.

X'0A'

COMMAND_RACE_REJECT: A change number of sessions (CNOS) request (either Activate or Deactivate APPC sessions) made through SNA Server Admin failed because the partner LU was also trying to change the session limit for the specified mode. Retry the command.

X'0B'

SESSION_LIMIT_CLOSED: A CNOS request made through SNA Server Admin failed because the partner LU will not allow the session limit for the specified mode to be raised above zero. This may not be a permanent condition; try the CNOS request later. If the problem persists, contact support personnel for your network.

X'0C'

SESSION_LIMIT_NOT_ZERO: An activate session request made through SNA Server Admin has failed because the session limit was not zero. This may occur because the partner LU initialized the session limit immediately before SNA Server Admin attempted to do so. No action is required.

X'0D'

LU_SESSION_LIMIT_EXCEEDED: SNA Server Admin issued an activate session request that violates the session limit for the LU.

In most cases, the LU session limit should be larger than the sum of the session limits of all the modes associated with the LU (remembering to allow for SNASVCMG modes). If this is not the case, some modes may not available, or may only allow a reduced number of sessions.

X'0E'

REQUEST_EXCEEDED_MAXIMUM_ALLOWED: This code should not normally occur.

X'0F'

RESOURCE_FAILURE_NO_RETRY: A CNOS request failed to complete because of a permanent resource failure. This error is caused by the partner LU violating the CNOS protocol. Obtain a trace of the error, and contact your network support personnel with the trace file and the event log file(s) related to SNA.

X'10'

ALLOCATION_ERROR: A CNOS request failed because no SNASVCMG session could be allocated to perform the CNOS exchange. This may occur because the connection required has not been activated, or the partner LU rejected the BIND request. If the error occurred because the connection was not active, activate it and retry the request. If the BIND was rejected, contact your network support personnel with the event log file(s) related to SNA.

X'11'

UNRECOGNIZED_MODE_NAME: A CNOS request failed because the partner LU does not recognize the specified mode name. This error signifies a configuration mismatch between the local LU and the partner LU.

X'12'

PARAMETER_ERROR_BAD_LU_NAME: This code should not normally occur.

X'13'

PARAMETER_ERROR_BAD_RESOURCE NAME: This code should not normally occur.

X'14'

PARAMETER_ERROR_MISSING_PARAMETERS: This code should not normally occur.

X'16'

PARAMETER_ERROR_BAD_ADDRESS: This code should not normally occur.

X'17'

PARAMETER_ERROR_SECURITY_ERROR: This code should not normally occur.

X'18'

PARAMETER_ERROR_MIN_GT_MAX: This code should not normally occur.

X'1A'

RESOURCE_ACTIVE: SNA Server Admin tried to activate a connection when it was already active. This may occur as part of normal operation, for example, if an application activates the connection immediately before SNA Server Admin issues the command. No action is required.

X'1C'

RESOURCE_INACTIVE: SNA Server Admin tried to deactivate a connection when it was already inactive. This may occur as part of normal operation, for example, if the connection is deactivated because of an outage immediately before SNA Server Admin issues the command. No action is required.

X'1D'

NO_LINK: SNA Server Admin tried to activate a switched connection, but all the appropriate link services are being fully used. Deactivate unused connections using the appropriate link services and retry the command.

X'1E'

NO_PRIVILEGE: This code should not normally occur.

X'1F'

PARAMETER_ERROR_FORCE_ERROR: This code should not normally occur.

X'22'

ABEND_PROG_ERROR: This code should not normally occur.

ACTION: Provide network support personnel with the event log file(s) related to SNA, the SNA Server configuration file, SNA internal trace file(s), and the number and description of the displayed return code. For information about SNA log files, configuration files, and trace files, see the Microsoft SNA Server Administration Guide.

Message 32

SSCP-PU session activated

Connection = value

EXPLANATION: The host has successfully activated the SSCP-to-PU session with an SNA server (node) on the specified connection. No action is required.

Message 33

SSCP-PU session deactivated

Connection = value

EXPLANATION: This is a status message. The host has shut down the SSCP-to-PU session with an SNA server (node) on the specified connection. No action is required.

Message 34

SSCP-LU session activated

Connection  = value

LU name  = value

LU address  = value

EXPLANATION: The host has successfully activated the SSCP-to-LU session with an SNA server (node) on the specified connection. No action is required.

Message 35

SSCP-LU session deactivated

Connection  = value

LU name  = value

LU address  = value

EXPLANATION: This is a status message. The host has shut down the SSCP-to-LU session with an SNA server (node) on the specified connection. No action is required.

Message 36

APPC session activated

Connection  = value

LU alias  = value

PLU alias  = value

Mode name  = value

Session ID  = value

LFSID  = value

EXPLANATION: The host has successfully activated the LU-to-LU session with an SNA server (node) on the specified connection. No action is required.

Message 37

APPC session deactivated normally

Connection  = value

LU alias  = value

PLU alias  = value

Mode name  = value

Session ID  = value

LFSID  = value

EXPLANATION: This is a status message. The host has deactivated the LU-to-LU session with an SNA server (node) on the specified connection. No action is required.

Message 38

APPC session deactivated abnormally

Qualifier  = value

Connection  = value

LU alias  = value

PLU alias  = value

Mode name  = value

Session ID  = value

LFSID  = value

EXPLANATION: An APPC session has been deactivated abnormally. The qualifier listed above corresponds to one of the following:

0002  The session was deactivated because of a temporary (Retry) error, and may be retried.

0003  The session was deactivated because of a permanent (No retry) error, such as a parameter mismatch. Contact the administrator of the partner LU's system to determine which parameters are mismatched.

Message 39

Connection value failed: No link service available

Message 40

value not configured in value

EXPLANATION: The administrator attempted to start an SNA server (node) but supplied an SNA server name that was not in the configuration.

ACTION: Use the SNA Server Admin program to check for the correct SNA server (node) name in the configuration, and retry.

Message 41

NetView Management Connection information not found in value

EXPLANATION: In the configuration file, there was no connection specified for sending and receiving NetView management data.

The connection to use for NetView management data can be specified using SNA Server Admin. To specify the connection, from the Options menu, choose NetView, and then, in the NetView Options dialog box, select a connection name. For more information, see the Microsoft SNA Server Administration Guide.

ACTION: This message probably indicates an internal error in SNA Server Admin. Provide network support personnel with a copy of the SNA Server configuration file. For information about the configuration file, see the Microsoft SNA Server Administration Guide.

Message 42

value record in value is too short

EXPLANATION: The configuration file information about the SNA server (node) was invalid. This indicates an internal error in SNA Server Admin.

ACTION: Provide network support personnel with a copy of the SNA Server configuration file. For information about the configuration file, see the Microsoft SNA Server Administration Guide.

Message 43

Network management record in value is too short

EXPLANATION: In the configuration file, the listing for the connection for sending and receiving NetView management data was invalid. This indicates an internal error in the SNA Server Admin program.

ACTION: Provide network support personnel with a copy of the SNA Server configuration file. For information about the configuration file, see the Microsoft SNA Server Administration Guide.

Message 44

Session limit exceeded for local LU value: session limit for mode value is zero

EXPLANATION: The node failed to set the session limits for an APPC mode because it would cause the local LU session limit to be exceeded.

ACTION: Decrease the mode session limit, or increase the local LU session limit.

Message 45

value Initially active connection value can't be activated because the number of connections exceeds the maximum for the link

Message 46

Connection value failed: the link role is the same as the link role of the remote computer

Message 47

Connection value failed: Node ID rejected by remote computer

Message 48

Incorrect parameters on starting the local SNA server

EXPLANATION: An internal error occurred during an attempt to start the local SNA server (node). This error should not occur in normal operation.

Message 49

Connection value failed: Node ID from remote computer was rejected

(value value value value)

Message 50

Security Violation: Local LU = value, Partner LU = value

EXPLANATION: A remote TP caused a violation of APPC TP security. The LU names are given here for information. This message will be followed by another message which will give more details about the security violation.

Message 51

User ID value not found

EXPLANATION: A remote APPC TP supplied a user ID not recognized by SNA Server. This error occurs when a remote APPC TP attempts to establish a conversation with an SNA Server TP configured to use conversation-level security.

ACTION: Check the user ID against the configured IDs.

This message may indicate that an unauthorized remote user is attempting to access your programs from a remote LU that imitates the remote LU that you configured.

Message 52

Password not supplied

EXPLANATION: A remote APPC TP did not supply a password during an attempt to establish a conversation with an SNA Server TP configured to use conversation-level security. A TP configured to use conversation-level security does not accept an "already verified" indication from the remote LU.

An error in the remote TP or in the SNA Server configuration can cause this error to occur.

ACTION: Check whether the remote TP is configured to use conversation-level security.

This message may indicate that an unauthorized remote user is attempting to access your programs from a remote LU that imitates the remote LU that you configured.

Message 53

Password mismatch, User ID = value

EXPLANATION: An invalid password was sent by a remote APPC TP during an attempt to establish a conversation with an SNA Server TP configured to use conversation-level security. The user ID supplied by the remote TP is shown. An error in the remote TP or in the SNA Server configuration can cause this error to occur.

ACTION: Check with the remote user whose user ID is shown on this message.

This message may indicate that an unauthorized remote user is attempting to access your programs from a remote LU that imitates the remote LU that you configured.

Message 54

User ID not supplied

EXPLANATION: A remote APPC TP has not supplied a user ID when attempting to establish a conversation with an SNA Server TP configured to use conversation-level security. An error in the remote TP or in the SNA Server configuration can cause this error to occur.

ACTION: Check whether the remote LU is configured to use conversation-level security.

This message may indicate that an unauthorized remote user is attempting to access your programs from a remote LU that imitates the remote LU that you configured.

Message 55

No incoming connection matched info in XID from remote MAC address value.

Message 56

Connection value failed: XID rejected by remote computer

Message 57

Internal timer error. Incorrect number of timing control blocks

Timer type value

Expected number of control blocks value

Overrun value

EXPLANATION: An internal error was detected processing timers within SNA Server.  This error should not occur in normal operation

Message 58

Internal timer error.  Incorrect number of timed out control blocks

Timer type value

Overrun value

EXPLANATION: An internal error was detected processing timers within SNA Server.  This error should not occur in normal operation

Message 60

Failed to invoke APPC TP value (value), sense data = value

EXPLANATION: An attempt to invoke the APPC TP shown has failed. The error will be reported to the invoking TP on the remote system with the following primary return code:

AP_ALLOCATION_ERROR. The sense data shown is the secondary return code, which will be one of the following hexadecimal values:

X'084B6031' AP_TRANS_PGM_NOT_AVAIL_RETRY

X'084C0000' AP_TRANS_PGM_NOT_AVAIL_NO_RETRY

X'10086021' AP_TP_NAME_NOT_RECOGNIZED

X'10086031' AP_PIP_NOT_ALLOWED

X'10086032' AP_PIP_NOT_SPECIFIED_CORRECTLY

X'10086034' AP_CONVERSATION_TYPE_MISMATCH

X'10086041' AP_SYNC_LEVEL_NOT_SUPPORTED

ACTION: Refer to the Microsoft SNA Server APPC Programmer's Guide for explanations of these error codes.

Message 70

APPC TP started locally:

TP_ID  = value

TP name  = value

EXPLANATION: The APPC TP shown has started. The TP_ID that appears is used to identify later events for this TP. If the TP ends abnormally, there will be other error messages indicating the nature of the problem.

Message 71

APPC TP ended:

TP_ID  = value

EXPLANATION: An APPC TP has ended. The TP_ID that appears was displayed on a previous message providing the TP name. No action is necessary.

Message 72

APPC conversation started locally:

TP_ID  = value

Conv_ID  = value

Dest TP name = value

LU alias  = value

PLU alias  = value

Mode name  = value

EXPLANATION: A local APPC TP started a conversation with a partner LU. The TP_ID that appears was displayed on a previous message. The TP_ID and Conv_ID are used to identify later events for this conversation. No action is necessary.

Message 73

APPC TP and conversation started remotely:

TP_ID  = value

Conv_ID  = value

TP name  = value

LU alias  = value

PLU alias  = value

Mode name  = value

User ID  = value

EXPLANATION: A remote APPC TP started a conversation with a local TP. The TP_ID and Conv_ID that appear are used to identify later events for this conversation. No action is necessary.

Message 74

APPC conversation ended:

TP_ID  = value

Conv_ID  = value

EXPLANATION: An APPC conversation has ended. The TP_ID and Conv_ID were shown on a previous message.

ACTION: If an abnormal termination occurs, review the previous messages that indicated errors in this conversation.

Message 75

APPC error sent:

Sense data  = value

TP_ID  = value

Conv_ID  = value

Log data value

EXPLANATION: A local APPC TP sent an error to the partner TP by issuing an [MC_]SEND_ERROR or [MC_]DEALLOCATE (ABEND) verb. The TP_ID and Conv_ID in this message were shown on a previous message. This message is followed by one or more messages containing log data supplied by the TP. The SNA sense data provides details about the error type.

ACTION: See IBM Systems Network Architecture: Formats for an explanation of the sense data.

Message 76

APPC error received:

Sense data  = value

TP_ID  = value

Conv_ID  = value

Log data value

EXPLANATION: The partner APPC TP sent an error to the local TP by issuing an [MC_]SEND_ERROR or [MC_]DEALLOCATE (ABEND) verb. The message is also logged if the partner TP failed to start. The TP_ID and Conv_ID in this message were shown in a previous message. This message is followed by one or more messages containing log data supplied by the TP. The SNA sense data provides details about the error type.

ACTION: See IBM Systems Network Architecture: Formats for an explanation of the sense data.

Message 79

TP Aborted:

TP_ID  = value

Message 90

APPC protocol violation:

Sense data  = value

TP_ID  = value

Conv_ID  = value

EXPLANATION: A protocol violation was detected on an APPC conversation. The TP_ID and Conv_ID in this message were shown on a previous message. The conversation failure is reported to the local TP with a return code of AP_CONV_FAILURE_NO_RETRY. The SNA sense data provides detail about the error type.

ACTION: See IBM Systems Network Architecture: Formats for an explanation of the sense data.

Message 91

APPC conversation failure:

TP_ID  = value

Conv_ID  = value

EXPLANATION: APPC conversation failed because of a connection failure. The connection failure is reported to the local TP with a return code of AP_CONV_FAILURE_RETRY.

One possible cause of this error is that the partner TP issued a TP_ENDED(HARD).

ACTION: Other logged messages will indicate the reasons for the connection failure; follow the actions in those messages.

Message 92

APPC TP detected abend of SNA subsystem

TP_ID  = value

Conv_ID  = value

EXPLANATION: A connection was lost or has been broken between an APPC TP, the local APPC LU it was using, and the local node. The connection failure is reported to the TP with a return code of AP_COMM_SUBSYSTEM_ABENDED.

ACTION: Check for failure indications in the event log and follow the recommended actions.

Message 93

APPC local conversation start failed:

Primary_rc  = value

Secondary_rc = value

TP_ID  = value

Dest TP name = value

LU alias  = value

PLU alias  = value

Mode name  = value

EXPLANATION: An attempt to start an APPC conversation locally using the verb [MC_]ALLOCATE failed.

ACTION: Refer to the Microsoft SNA Server APPC Programmer's Guide for information about the displayed primary_rc and secondary_rc values.

Message 94

APPC remote conversation start failed:

Primary_rc  = value

Secondary_rc = value

TP name  = value

EXPLANATION: An invokable APPC TP configured on SNA Server has issued a RECEIVE_ALLOCATE verb that failed.

ACTION: Refer to the Microsoft SNA Server APPC Programmer's Guide for information about the displayed primary_rc and secondary_rc values.

Message 95

APPC given bad event handle or callback address value

Message 96

Local APPC TP start failed:

Primary_rc  = value

Secondary_rc = value

TP name  = value

Message 101

(value) Internal Protocol Violation

EXPLANATION: The component logging this error received an invalid message from another SNA Server component. This is an internal error and should not occur during normal operation.

SUBCODE INFORMATION:

0B49   Wrong length for Locality Data.

0A08   Invalid message discarded.

0A40   Unrecognized Open request type.

ACTION: Provide network support personnel with the event log file(s) related to SNA, SNA internal trace file(s), the SNA dump file, and the number and description of the displayed subcode. For information about SNA log and trace files, see the Microsoft SNA Server Administration Guide.

Message 102

(value) Internal Error

SUBCODE INFORMATION:

X'0B02' A dynamic storage allocation request has failed.

X'0BC1' Buffer header pointer is corrupted.

X'0BC3' Corruption of internal free buffer pool.

X'0BC5' Free ready pool is empty.

X'0BC6' Free active pool is empty.

ACTION: Provide network support personnel with the event log file(s) related to SNA, SNA internal trace file(s), the SNA dump file, and the number and description of the displayed subcode. For information about SNA log, trace, and dump files, see the Microsoft SNA Server Administration Guide.

Message 103

(value) Configuration File Format Error

EXPLANATION: The node configuration data read from the configuration file is invalid.

SUBCODE INFORMATION:

X'0A00' The record was not found in the configuration file, COM.CFG.

X'0A06' The destination name was not found in the configuration file.

X'0A09' The resource ID was incorrect.

X'0A43' The Record Reference Number was repeated in the configuration file.

X'0A44' The Reference Number in the configuration file was too big.

X'0A45' The record was not found in the configuration file.

ACTION: Provide network support personnel with the event log file(s) related to SNA, the SNA Server configuration file, and the number and description of the displayed subcode. For information about SNA log files and the configuration file, see the Microsoft SNA Server Administration Guide.

Message 104

(value) Message Sequence Error

EXPLANATION: This is an internal logic error. An SNA Server component received an unexpected message from another SNA Server component.

SUBCODE INFORMATION:

X'0B43'  Invalid or unexpected message received.

ACTION: Provide network support personnel with the event log file(s) related to SNA, SNA internal trace file(s), and the number and description of the displayed subcode. For information about SNA log and trace files, see the Microsoft SNA Server Administration Guide.

Message 108

(value) Message Routing Error

EXPLANATION: This is an SNA Server internal logic error.

SUBCODE INFORMATION:

X'0B41'  Path error during initialization.

X'0B42'  Path error after initialization.

X'0B45'  Error in internal addressing.

X'0B47'  Illegal internal address.

ACTION: Provide network support personnel with the event log file(s) related to SNA, SNA internal trace file(s), and the number and description of the displayed subcode. For information about SNA log and trace files, see the Microsoft SNA Server Administration Guide.

Message 110

(value) Resource Allocation Error

EXPLANATION: This is an internal logic error.

SUBCODE INFORMATION:

X'0B00   There were insufficient buffers during run-time code processing of the configuration file.

ACTION: Provide network support personnel with the event log file(s) related to SNA. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 120

(value) Shortage Of Buffers

EXPLANATION: There are insufficient buffers for the component to continue processing.

ACTION: Use the COMBUF Registry variable to allocate more buffers to the component. If increasing the size of the buffer pool does not solve the problem, it may indicate an internal error. Provide network support personnel with the event log file(s) related to SNA, as well as the SNA dump file.

For information about SNA log and dump files, see the Microsoft SNA Server Administration Guide. For information about COMBUF, see the Appendix C, "Registry and Environment Variables for SNA Server."

Message 121

Fatal error occurred, product ID = value, error code = value

EXPLANATION: This is an internal error that should never occur during normal operation.

ACTION: Make a note of the product ID and error code displayed, and provide network support personnel with the event log file(s) related to SNA. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 127

Link protocol DLL does not contain expected entry points

Message 128

Can't locate IHV DLL value

Message 129

Configuration information for SNALink value is not present

Message 151

(value) Internal Protocol Violation

EXPLANATION: An internal protocol violation occurred. This is due to an internal logic error in SNA Server.

SUBCODE INFORMATION:

X'0140'  Invalid message type.

X'0141'  Invalid open type.

X'0142'  Invalid close type.

X'0143'  Invalid DLC status message.

X'0144'  Invalid destination routing information.

X'0145'  Illegal DLC message for a link.

X'014C'  Invalid type qualifier.

X'014D'  No element on DLCDATA message.

X'014E'  Invalid routing information on message.

ACTION: Provide network support personnel with the event log file(s) related to SNA, the SNA dump file, and the number and description of the displayed subcode. For information about SNA log and dump files, see the Microsoft SNA Server Administration Guide.

Message 152

(value) Open from node rejected, rc = value

SUBCODE INFORMATION:

X'0100'  The SDLC link service rejected an Open request from the local SNA server (node), which indicates an internal error in SNA Server.

ACTION: Provide network support personnel with the event log file(s) related to SNA, as well as the return code displayed with this error. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 154

(value) Internal Message Sequence Error

EXPLANATION: The node received an invalid or unexpected message. This is an internal logic error in the node component detected by the link service.

SUBCODE INFORMATION:

X'0147'  Link not open — cannot receive messages.

X'0148'  Station not open — cannot receive messages.

ACTION: Provide network support personnel with the event log file(s) related to SNA, SNA internal trace file(s), the SNA dump file, and the number and description of the displayed subcode. For information about SNA log, trace, and dump files, see the Microsoft SNA Server Administration Guide.

Message 160

(value) Resource Allocation Error

EXPLANATION: Severity 16.

SUBCODE INFORMATION:

X'014B'  SNA Server is unable to send a message to the node due to a buffer shortage. This is an internal error that should not occur during normal operation.

ACTION: Provide network support personnel with the event log file(s) related to SNA, SNA internal trace file(s), and the SNA dump file. For information about SNA log, trace, and dump files, see the Microsoft SNA Server Administration Guide.

Message 162

(value) Protocol Violation

EXPLANATION: The adjacent SDLC link station caused a protocol violation. This is probably a configuration or internal logic error in the remote system.

SUBCODE INFORMATION:

X'0146'  The SDLC frame was too short — there is no address or control.

X'014A'  Received NR value is invalid.

ACTION: Provide network support personnel with the event log file(s) related to SNA, SNA trace file(s), and the number and description of the displayed subcode. For information about SNA log and trace files, see the Microsoft SNA Server Administration Guide.

Message 165

Establishing connection value through SDLC link service value
Please dial value within value s.

EXPLANATION: A switched, manual-dial connection was activated using the specified link service. Dial the specified number within the specified time, so that communication can be established over the connection.

Message 166

The SNA Server software is dialing connection value through SDLC link service value

EXPLANATION: A switched connection that is configured for automatic dialing by SNA Server was started. The pop-up will disappear after approximately 10 seconds. No action is necessary.

Message 167

Initializing connection value from value through link service value

EXPLANATION: An SDLC connection is being started. No action is necessary.

Message 168

Link device driver value error on function value, rc = value

EXPLANATION: An internal error has been reported to the SDLC device driver.

ACTION: Provide network support personnel with the function number and return code shown on this message.

Message 169

Failed to Open device driver value. Windows NT rc = value

EXPLANATION: An error occurred during an attempt to open the SDLC device driver. The return code from the OpenFile call is shown.

ACTION: Check the OpenFile return code.

Message 170

Initialization failed for link service value, used by connection value

EXPLANATION: The SDLC link service could not be initialized. A previous message gives the reason for failure.

ACTION: Refer to the previous message.

Message 171

Initialization for driver value OK, trying to connect

EXPLANATION: The indicated SDLC driver has been initialized and the SDLC link service is attempting to establish a connection.

ACTION: No action is necessary.

Message 173

Unknown modem type: value

EXPLANATION: This is an SNA Server internal error.

ACTION: Provide network support personnel with the event log file(s) related to SNA, and also the modem number included in this message. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 174

Failed to initiate connection value through link service value

EXPLANATION: Failed to establish an autodial connection.

ACTION: Check the modem connections, internal functions, and dial data. See the Microsoft SNA Server Administration Guide for more information on the use of modems.

Message 175

Modem shows DSR BEFORE dialing, for connection value through link service value

EXPLANATION: The DSR signal from the modem, normally low until dialing is started, was already high before dialing. The modem may not be functioning correctly.

ACTION: Check the modem documentation. See the Microsoft SNA Server Administration Guide for more information on the use of modems.

Message 176

No DSR for modem used by connection value through link service value. Check modem power and cabling

EXPLANATION: The DSR signal from the modem has not come up, indicating that the modem is not functioning correctly.

ACTION: Check the modem connections and the modem's documentation for correct settings. See the Microsoft SNA Server Administration GuideModem_Requirements_for_Accepting_a_Phone_Number_from_SNA_Server@admin.hlp for more information on the use of modems.

Message 177

The sending of the phone number from SNA Server to the modem failed: no CTS. Check modem state, power, and cabling, for the modem used by connection value through link service value.

EXPLANATION: The dialing process failed and there is no CTS signal from the modem.

ACTION: Check the modem connections and the modem. See the Microsoft SNA Server Administration Guide for more information on the use of modems.

Message 178

The sending of the phone number from SNA Server to the modem failed; DSR steady. Check state of modem used by connection value through link service value.

EXPLANATION: The dialing process initiated by SNA Server failed; the modem is not dialing when the dial command is sent by SNA Server.

ACTION: Check the modem connections and the dial string sent to the modem. If the connections and dial string are OK, then the modem may not be functioning correctly. See the Microsoft SNA Server Administration Guide for more information on the use of modems.

Message 179

Connection value through link service value has been closed

EXPLANATION: The SDLC connection through the indicated link service has been closed. No action is necessary.

Message 180

DSR up. Modem OK for connection value through link service value

EXPLANATION: The modem initialization for the connection shown has completed. No action is necessary.

Message 181

DSR dropped: connection value through link service value ended

EXPLANATION: The DSR signal from the modem has been dropped, which indicates that the connection shown has ended.

ACTION: If the connection failed while in use, other messages should be logged giving reasons for the failure. If this message is unexpected, refer to any messages that may have occurred prior to this message.

Message 182

Connection failure, code = value

Cause Data  = value

Link Role  = value

Remote Node Type  = value

EXPLANATION: Cause data is a list of the failure causes from the Failure subvector in the alert. Link role and remote node type are as described in the Link Connection Subsystem Configuration Data subvector in the alert.

A connection failure can be due to a station outage, rather than a link outage. If it is due to a station outage — which can be recognized by outage code values of X'80' or higher — then message #183 will also be logged.

ACTION: No action is necessary.

Message 183

Detailed diagnostic data for station value:

SBSY  CFTX  CFRX  V(S)  V(R)  N(R)  OSFC  T1CT

value

EXPLANATION: The value following "station" is the station address as given in the Detail Qualifier subvector in the alert.

The other fields are all data from the Link Station Data subvector, as follows:

SBSY  Link station state:  80 or 40 (Local or remote station sending RNR)

CFTX  Last SDLC control field sent

CFRX  Last SDLC control field received

V(S)  N(S) count

V(R)  N(R) count

N(R)  Last received N(R)

OSFC  Outstanding frame count

T1CT  Reply timer expiration count

ACTION: No action is necessary.

Message 184

Link statistics:

TXIOK TXIER RETXI RXIOK RXIER

Current 	value

Accumulated	value

RXINV RXFRM TXFRM RXLST FRMRT

Current 	value

Accumulated	value

CTSER DSRUP DSRDN DSRER IDLTO

Current	value

Accumulated	value

FRMRR DMAUR DMAOR TXERR RXOVR

Current	value

Accumulated	value

EXPLANATION: SDLC link services maintain counts of data traffic and error events that are logged whenever a counter "wraps," or whenever a connection through the link service terminates. There are counters for each of 20 types of event. Current counters show the values since the statistics were last logged. They are reset to zero after being logged. Accumulated counters are total counts kept from the time the SDLC link service was started.

The counters have the maximum value of 32,767. When any "current" counter reaches this value, the counters are logged and reset. "Accumulated" counters are frozen when they reach the maximum.

The individual counters are as follows:

TXIOK  Information frames successfully transmitted

TXIER  Information frames not successfully transmitted

RETXI  Re-transmitted information frames

RXIOK  Information frames successfully received

RXIER  Frames not successfully received

RXINV  Invalid frames received

RXFRM  Total number of frames received

TXFRM  Total number of frames sent

RXLST  Frames received and then discarded

FRMRT  'FRMR' frames transmitted

CTSER  Clear to Send drops during transmission

DSRUP  DSR up before switched connection attempted

DSRDN  No DSR before switched connection timeout

DSRER  DSR lost before connection established

IDLTO  Link inactivity timeout

FRMRR  'FRMR' or 'DM' received

DMAUR  Transmitter interrupts missed

DMAOR  Frames received longer than the configured max

TXFRR  Failed to transmit a frame

RXOVR  Receiver interrupts missed

The counts are also sent as an alert NMVT (subtype 0x0025) on the NetView management connection, if it is active. See message #540.

ACTION: No action is necessary.

Message 187

Unable to initiate connection value through link service value because the modem is already showing DSR ON. Reset the modem and retry.

EXPLANATION: This message is displayed at the same time that message #175 is logged.

ACTION: Check the modem documentation. See the Microsoft SNA Server Administration Guide for more information on the use of modems.

Message 188

Warning: Non-productive receive timeout on connection value through driver value. Contact with the host may have been lost.

EXPLANATION: The indicated connection, using the indicated SDLC driver, has not received anything from the host for 1 minute. The connection may have been lost. If the connection has been lost, after 3 minutes, it fails and message #23 is logged. If the host is very slow at polling its remote nodes, it is possible that the connection is not lost.

ACTION: If the message persists, contact your host administrator.

Message 189

SNA Server could not open value to use for auto-dialling on connection value.

EXPLANATION: Another application is probably using the requested COM port. You must stop that application before this connection will start.

ACTION: Stop the application and retry this connection.

Message 197

SDLC link service value not configured in value

EXPLANATION: You tried to start an SDLC link service with a name that was not in the configuration file.

ACTION: Use the SNA Server Admin program to check the correct service name, and retry.

Message 198

Incorrect parameters on starting SDLC link service

EXPLANATION: This internal error should never occur during normal operation.

ACTION: Contact network support personnel at your site.

Message 199

Secondary return code = value

Message 206

Incoming call discarded as value inactive

EXPLANATION: An incoming call to the node shown was discarded.

ACTION: Refer to information on configuring local SNA Servers, and link services usage parameters.

Message 210

Failed to get required memory resources

EXPLANATION: There is not enough memory to start the DLC (802.2) link service.

ACTION: Stop any unnecessary programs running on your computer and retry.

Message 211

Internal Error (value)

EXPLANATION: An internal logic error has been encountered. This error should not occur during normal operation.

ACTION: Provide network support personnel with the event log file(s) related to SNA, SNA internal trace file(s), and the error code included in this message. For information about SNA log and trace files, see the Microsoft SNA Server Administration Guide.

Message 217

Adapter initialization error

local MAC address  = value

EXPLANATION AND ACTION: The DLC (802.2) link service detected an error while trying to initialize the NDIS adapter.  This error can be caused by one of the following conditions:

Token ring cable or MAU fault.  Check the cable from the PC to the MAU and try again.  If the problem persists, replace the cable and/or the MAU and try again.

Duplicate network address on ring.  Check the address of this adapter against the addresses of all the other adapters on the same ring.  If there is a duplicate, change one of the addresses and try again.

Temporary contention condition on ring.  These errors are only temporary and should clear themselves.  The token ring service will attempt to initialize the adapter after a delay, and initialization should then be successful.

Adapter speed mismatch.  Check that the token ring adapter is set for the same speed as the rest of the adapters on the ring.  If not, change the speed and try again.

Token ring adapter hardware fault.  Replace the token ring adapter and retry.

If none of these actions solves the problem, contact support personnel for your network.

Message 218

Adapter check: microcode abnormally terminated

local MAC address  = value

local ring number  = value

EXPLANATION: The token ring adapter microcode has terminated abnormally. All connections will fail.

ACTION: Run any diagnostics provided with the token ring adapter, then contact the vendor of the token ring adapter.

Message 219

Adapter check: receive queue overrun

local MAC address  = value

local ring number  = value

EXPLANATION: The NDIS adapter was unable to receive an incoming frame due to a shortage of buffer space. All connections will fail.

ACTION: Run any diagnostics provided with the NDIS adapter, then contact the vendor of the NDIS adapter.

Message 220

Adapter check (value)

local MAC address  = value

local ring number  = value

EXPLANATION: The NDIS adapter has detected a hardware or microcode error.

ACTION: Run any diagnostics provided with the NDIS adapter, then contact the vendor of the NDIS adapter.

Message 221

Network status: lobe wire fault

local MAC address  = value

EXPLANATION: The NDIS adapter has detected an open or short circuit on the lobe wire circuit. The adapter will be closed and all connections will fail.

ACTION: Check all cables between the adapter and the MAU, and retry. If the error persists, contact support personnel for your network.

Message 222

Network status: auto-removal error

local MAC address  = value

EXPLANATION: The NDIS adapter has detected a hardware fault and removed itself from the ring. All connections will fail.

ACTION: Check all cables between the adapter and the MAU, and retry. If the error persists, contact support personnel for your network.

Message 223

Network status: remove command received

local MAC address  = value

local ring number  = value

EXPLANATION: A command was received forcing the NDIS adapter to remove itself from the ring. All connections will fail.

ACTION: Contact support personnel for your network to find the reason for the remove command.

Message 224

System action exception

EXPLANATION: A user application has made a call to the DLC driver with the SYSTEM_ACTION_FLAG set.

ACTION: Contact your support personnel for help.

Message 225

PC detected error (value)

local MAC address  = value

local ring number  = value

EXPLANATION: The DLC device driver has detected an unacceptable error (such as an unexpected return code from Windows NT). The adapter will be closed, and all connections will fail.

ACTION: If the error persists, contact support personnel for your network.

Message 226

Connection lost

Connection  = value

Local MAC address  = value

Local ring number  = value

Remote MAC address = value

Routing data  = value

Source SAP  = value

Destination SAP  = value

Connection data  = N(S) N(R) PFRC LRNR FRMD CRCV CSND LKST

                             value

EXPLANATION: The specified connection was lost, either because of some problem with the local NDIS adapter, a problem at the remote adapter, or a problem in the network itself (for example, a bridge failure).

The connection data fields are as follows:

N(S)  N(S) value of last transmitted frame

N(R)  N(R) value of last transmitted frame

PFRC  Number of I-frames that have not been acknowledged

LRNR  N(R) value of last received frame

FRMD  Frame modulus (should be 128)

CRCV  Last command/response received

CSND  Last command/response sent

LKST  Link state

   Bit 6 — local busy

   Bit 4 — remote busy

ACTION: If another error message signifies a local adapter fault, perform the action recommended in that message. If no error message signifies a problem with the local adapter, contact support personnel for your network.

Message 227

FRMR received (value)

Connection  = value

Local MAC address  = value

Local ring number  = value

Remote MAC address = value

Routing data  = value

Source SAP  = value

Destination SAP  = value

Connection data  = N(S) N(R) PFRC LRNR FRMD CRCV CSND LKST

                             value

EXPLANATION: A FRMR frame was received on this connection indicating that the local station sent a frame containing an error. The connection will be deactivated.

The FRMR code takes the following values:

01  Invalid N(R) value sent

02  Maximum I-field length exceeded

03  Invalid or unsupported command/response sent

04  I-frame sent when not permitted

ACTION: See message #226 for details of the connection data.

If this problem persists, contact support personnel for your network.

Message 228

FRMR sent (value)

Connection  = value

Local MAC address  = value

Local ring number  = value

Remote MAC address = value

Routing data  = value

Source SAP  = value

Destination SAP  = value

Connection data  = N(S) N(R) PFRC LRNR FRMD CRCV CSND LKST

                             value

EXPLANATION: A FRMR frame was sent on this connection indicating that the remote station sent a frame containing an error. The connection will be deactivated.

The FRMR code takes the following values:

01  Invalid N(R) value received

02  Maximum I-field length exceeded

03  Invalid or unsupported command/response received

04  I-frame received when not permitted

ACTION: See message #226 for details of the connection data.

If this problem persists, contact support personnel for your network.

Message 229

SABME received when connection active

Connection  = value

Local MAC address  = value

Local ring number  = value

Remote MAC address = value

Routing data  = value

Source SAP  = value

Destination SAP  = value

Connection data  = N(S) N(R) PFRC LRNR FRMD CRCV CSND LKST

                             value

EXPLANATION: A SABME frame was received from the remote station while the connection was activated. The connection will be deactivated. This may be caused by an error at the remote station causing it to reset.

ACTION: See message #226 for details of the connection data.

If this problem persists, contact support personnel for your network.

Message 230

Remote station not responding to value commands

Connection  = value

Local MAC address  = value

Local ring number  = value

Remote MAC address = value

Routing data  = value

Source SAP  = value

Destination SAP  = value

EXPLANATION: The remote station could not be contacted because it is not answering TEST or XID frames. This could be caused either by an incorrectly configured remote MAC address or remote SAP address, or by a fault in the intervening network (for example, a bridge fault).

ACTION: Check the configuration details, then contact support personnel for your network

Message 231

Configuration or installation error (value)

EXPLANATION: This error should not normally occur.

ACTION: Contact network support personnel, and supply the reported error code.

Message 232

Storage capacity exceeded

local MAC address  = value

local ring number  = value

EXPLANATION: The storage capacity of the DLC (802.2) link service has been exceeded. Frames have been rejected and the connection will stop receiving data. The connection will start receiving data again when some storage has been freed.

ACTION: No action is necessary.

Message 233

A DLC command failed, error code value

EXPLANATION: An error code which is not explicitly handled by SNA Server has been returned by the DLC driver.

This could be due to network card misconfiguration or hardware problems.

ACTION: Contact network support personnel, and supply the reported error code.

Message 234

Failed to open SAP value, error (value)

Some connections may now be unavailable

EXPLANATION: The DLC (802.2) link service failed to open a service access point (SAP) during initialization. If error code 43 is displayed, the SAP has already been opened by another link process.

ACTION: If other errors occur, contact network support personnel with the reported error code.

Message 235

All SAPs failed to open, no connection is usable

EXPLANATION: The DLC (802.2) link service failed to open any service access points (SAPs). This error can occur when two nodes have the same SAP addresses configured.

ACTION: Check that the DLC (802.2) link service is properly installed and that SAPs are available.

Message 236

DM or DISC received

Message 237

Protocol timer Ti has expired

EXPLANATION: Ti is an activity timer for DLC (802.2) traffic between two remote computers. When an SNA server fails to receive a DLC (802.2) frame within the activity timer (Ti) from a remote computer with which it is communicating, the activity timer (Ti) elapses and this error message is logged. This may occur because the LAN is heavily loaded or because the remote computer has been turned off.

ACTION: Check that the remote computer is still functioning correctly. If the LAN is heavily used, the activity timer (Ti) may need to be reconfigured by changing your LAN operating system configuration.

Message 238

Connection value statistics

Station log	IFTX	IFRX	ERTX	ERRX	T1EX

value

SAP log	FRTX	FRRX	FDSC	DLST	NBUF

value

Adapter log LNER INER BTER ACER ABDL LFRM RXCG FCER  FQER TKER

value

EXPLANATION: This message logs the LAN LLC statistics when a connection is terminated. This information is provided to help evaluate the performance of the LAN or isolate problems in the operation of the LAN. Descriptions of the fields are as follows:

Station log:

IFTX  Number of I-frames transmitted

IFRX  Number of I-frames received

ERTX  Number of I-frames transmitted with an error resulting

ERRX  Number of I-frames received with an error resulting

T1EX  Number of times T1 timer expired

SAP log:

FRTX  Number of frames transmitted

FRRX  Number of frames received

FDSC  Number of frames discarded

DLST  Number of times data lost

NBUF  Number of buffers available in buffer pool

Adapter log:

LNER  Number of line errors

INER  Number of internal errors

BTER  Number of burst errors

ACER  Number of A/C errors

ABDL  Number of times abort delimiter transmitted

LFRM  Number of lost frames

RXCG  Number of times receiver congested

FCER  Number of frame copied errors

FQER  Number of frequency errors

TKER  Number of token errors

ACTION: Refer to the IBM Token Ring Network Architecture Reference for descriptions and explanations of the fields. No action is necessary.

Message 239

Adapter initialized successfully

EXPLANATION: The adapter initialization is complete with no errors.

ACTION: No action is necessary.

Message 240

Connection value started

EXPLANATION: The DLC (802.2) connection shown has been started.

ACTION: No action is necessary.

Message 241

Connection value stopped

EXPLANATION: The DLC (802.2) connection shown has been stopped.

ACTION: No action is necessary.

Message 242

Invalid adapter value configured

EXPLANATION: The DLC (802.2) link service is configured to use an NDIS adapter that is not installed.

ACTION: Refer to the installation manual for details on installing the DLC drivers. Check that the setting of the adapter (primary or secondary) corresponds to the link service configuration.

Message 243

Permanent error occurred during initialization (subcode value)

EXPLANATION: A permanent error occurred while the DLC (802.2) link service attempted to initialize the adapter. This error should not normally occur.

ACTION: Provide network support personnel with the reported subcode.

Message 244

DLC Protocol service has not been started

EXPLANATION: The DLC.SYS process is not running.

ACTION: Refer to the Windows NT installation manual for details on installing the DLC driver.

Message 246

Terminating unused DLC (802.2) service

EXPLANATION: No connections are configured to use this DLC (802.2) link service, so it has terminated.

ACTION: No action is necessary.

Message 247

DLC (802.2) link service value not configured in value

EXPLANATION: The operator attempted to start an SNA Server DLC (802.2) link service but supplied a service name that was not in the configuration file.

ACTION: Start the link service with the correct link service name from the configuration file.

Message 248

Incorrect parameters on starting DLC (802.2) link service

EXPLANATION: This is an internal error that should not occur during normal operation.

ACTION: Provide network support personnel with the event log file(s) related to SNA, and a trace file for the DLC (802.2) link service. For information about SNA log and trace files, see the Microsoft SNA Server Administration Guide.

Message 249

An error occurred when accessing the DLC Protocol service.

EXPLANATION: The DLCAPI.DLL file either does not exist or is corrupt. This error can occur if you attempt to start a primary, backup, or member SNA server on a computer that is only set up to be a client.

Message 251

No Connection for Message

EXPLANATION: SNA Server received a message from the host, but the link service does not have a node connection for the message. This error should not occur during normal operation.

ACTION: Provide network support personnel with the event log file(s) related to SNA, and a trace file for the DFT link service. For information about SNA log and trace files, see the Microsoft SNA Server Administration Guide.

Message 252

Error during initialization, rc = value

EXPLANATION: An error was returned from a Windows NT function during an attempt to initialize the DFT connection.

ACTION: See your Windows NT documentation for information on return codes. Check the return code. Check that the device name of the DFT driver specified in the link service dialog matches the name specified in the Registry. If the problem persists, contact network support personnel.

Message 253

Connection Activation Failed, rc = value

EXPLANATION: This error is caused by failure of the first DFT driver initialization message. The return code from the DeviceIoControl call is shown on the screen.

ACTION: See your Windows NT documentation for information on return codes. Check the return code and the hardware configuration. If the problem persists, contact network support personnel.

Message 254

Unknown Internal Message

EXPLANATION: An SNA Server internal message is received but not recognized. This error should not occur during normal operation.

ACTION: Provide network support personnel with the event log file(s) related to SNA, and SNA trace file(s), including Data Link Control traces for the SnaServer. For information about SNA log and trace files, see the Microsoft SNA Server Administration Guide.

Message 255

Buffer Shortage

EXPLANATION: There are insufficient buffers for the component to continue processing.

ACTION: Use the COMBUF Registry variable to allocate more buffers to the component.

If increasing the size of the buffer pool does not solve the problem, an internal error may be occurring. Provide network support personnel with the event log file(s) related to SNA, SNA trace file(s) such as Data Link Control traces of the SnaServer or the affected link service, and the SNA dump file.

For information about SNA log, trace, and dump files, see the Microsoft SNA Server Administration Guide. For information about COMBUF, see Appendix C, "Registry and Environment Variables for SNA Server."

Message 256

Lost Connection

EXPLANATION: The connection to the SNA server (node) is lost. Possible causes are the failure of the node process, or the stopping of the node by an administrator.

ACTION: If the node failed, check other messages logged to indicate this failure, follow any action specified for them, and then retry.

Message 257

Bad Enqueue Type

EXPLANATION: This is an internal error and should not occur during normal operation.

ACTION: Provide network support personnel with the event log file(s) related to SNA, and the SNA dump file. For information about SNA log and dump files, see the Microsoft SNA Server Administration Guide.

Message 258

Station Contacted

EXPLANATION: The host is communicating with the control unit.

ACTION: No action is necessary.

Message 259

Unexpected Message on PU Session: value value value value value value

EXPLANATION: An unexpected message was received on the SSCP-to-PU session indicating an internal error in SNA Server. The text of the received message is shown.

ACTION: Provide network support personnel with the event log file(s) related to SNA, and one or more SNA trace file(s). For information about SNA log and trace files, see the Microsoft SNA Server Administration Guide.

Message 260

Open Link/Station Failed

EXPLANATION: There has been a failure to open the link adapter. This error should not occur during normal operation.

ACTION: Provide network support personnel with the event log file(s) related to SNA, and one or more SNA trace file(s). For information about SNA log and trace files, see the Microsoft SNA Server Administration Guide.

Message 261

Line Check (value) on adapter value. Its LUs will be unavailable.

EXPLANATION: The DFT link service detected a line check. The line check value shown corresponds to one of the Operator Information Area (OIA) indicators that appear in the status line of a 3270 emulator.

ACTION: Look up the OIA indicator in the Microsoft SNA Server 3270/5250 Applet User's Guide.

Message 263

The controller has reported a non-productive receive timeout

Your host system may have gone down

EXPLANATION: The DFT controller has not received anything from the host for some time. The connection may have been lost with the host. If the connection has been lost, eventually the controller will report it as failed. It is possible that the connection has not been lost if the host is very slow at polling its remote nodes. The values for these timeouts are configured on the controller.

ACTION: If this message persists, contact your host administrator.

Message 264

The controller has reported a machine check (value) on adapter value

Refer to the controller diagnostics manual for more information

EXPLANATION: The DFT link service reported a machine check, indicating a serious problem in the controller.

ACTION: Check the machine check number in the controller diagnostics manual, and take the recommended action.

Message 265

The controller is not SNA attached

EXPLANATION: The DFT link service detected that it is attached to a non-SNA controller. SNA Server does not support non-SNA controllers. The connection is not activated and it remains in the Pending state.

ACTION: Stop the link service, attach the DFT link service to an SNA controller, and then restart the link service.

Message 297

DFT link service value not configured in value

EXPLANATION: The service name entered while starting an SNA Server DFT link service is not in the configuration file.

ACTION: Start the link service with the correct link service name as it appears in the configuration file.

Message 298

Incorrect parameters on starting the DFT link service

EXPLANATION: This is an internal error that should not occur during normal operation.

ACTION: Contact network support personnel.

Message 300

(value) Internal Error

EXPLANATION: SNA Server detected an invalid message between different layers of the X.25 link service protocol stack (identified here as L2, L3, and QLLC). This is an internal logic error and should not occur during normal operation.

SUBCODE INFORMATION:

X'2540'  L2 received illegal reset request from L3.

X'2541'  L2 received illegal reset confirm from L3.

X'2542'  L2 received illegal restart request from L3.

X'2543'  L2 received illegal restart confirm from L3.

X'2544'  L2 received illegal data packet from L3.

X'2545'  L2 received illegal call request from L3.

X'2546'  L2 received illegal call accept from L3.

X'2547'  L2 received illegal clear request from L3.

X'2548'  L2 received illegal clear confirm from L3.

X'2549'  L2 received unidentified packet from L3.

X'25AF'  L3 received illegal reset request from QLLC.

X'25B0'  L3 received illegal reset confirm from QLLC.

X'25B2'  L3 received illegal restart request from QLLC.

X'25B3'  L3 received illegal call request from QLLC.

X'25B4'  L3 received illegal call accept from QLLC.

X'25B5'  L3 received illegal clear request from QLLC.

X'25B6'  L3 received illegal clear confirm from QLLC.

X'25B7'  L3 received unidentified packet from QLLC.

ACTION: Provide network support personnel with the event log file(s) related to SNA and the SNA dump file. For information about SNA log and dump files, see the Microsoft SNA Server Administration Guide.

Message 301

(value) Network Packet Sequence Error

EXPLANATION: The node received an unexpected message from the X.25 network.

SUBCODE INFORMATION:

X'2512'  A Clear or Reset confirm was received in an invalid state.

X'2513'  A call indication was received in an invalid state.

X'2514'  A Call Accept was received in an invalid state

ACTION: Provide network support personnel with the number and description of the displayed subcode.

Message 302

(value) Failed to initiate outgoing call

EXPLANATION: An outgoing call could not be established.

Note:  This condition may occur if connections are started while the X.25 service is still initializing its connection to the X.25 network.

SUBCODE INFORMATION:

X'2510'  An outgoing call could not be established due to a network failure.

ACTION: Check the above conditions, then retry.

Message 303

(value) Resource Allocation Error

EXPLANATION: This is an internal error and should not occur during normal operation.

SUBCODE INFORMATION:

X'2505'  L3 clock handler has run out of QCBs.

X'2506'  Run out of QCBs on clock initialization.

X'2521'  Buffer manager cannot allocate a QCB.

X'2522'  Buffer manager cannot provide an RX buffer.

X'2523'  Buffer manager cannot release an RX buffer.

X'2524'  Buffer manager cannot release a TX buffer.

ACTION: Provide network support personnel with the event log file(s) related to SNA, the SNA Server configuration file, and the number and description of the displayed subcode. For information about SNA log files and the configuration file, see the Microsoft SNA Server Administration Guide.

Message 304

(value) Initialization Failure

EXPLANATION: This internal error should not occur during normal operation.

SUBCODE INFORMATION:

X'2500'  Failed to initialize the X.25 RECEIVE handler.

X'2501'  Failed to initialize the X.25 TRANSMIT handler.

X'2502'  Failed to initialize the X.25 L3 handler.

X'2503'  Failed to initialize the X.25 L3 clock handler.

X'2504'  Failed to initialize the X.25 L2 clock handler.

ACTION: Provide network support personnel with the event log file(s) related to SNA. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 305

(value) Initialization Failure: configuration error

EXPLANATION: This is an internal error in SNA Server (but it may be caused by a corrupted configuration file).

SUBCODE INFORMATION:

X'250D'  Failure in configuration initialization.

X'250E'  Failure to access a configuration record.

ACTION: Check that the configuration file can be opened using the SNA Server Admin program, and that the X.25 link service configuration appears to be correct. If it does, provide network support personnel with the event log file(s) related to SNA, and the SNA Server configuration file. For information about SNA log files and the configuration file, see the Microsoft SNA Server Administration Guide.

Message 306

(value) Unexpected request from node service

EXPLANATION: Severity 12.

SUBCODE INFORMATION:

X'250F'  This is an SNA Server internal error.

ACTION: Provide network support personnel with the event log file(s) related to SNA. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 308

EICON call/listen failed to connect (rc = value)

Message 309

Error returned from EICON toolkit (value)

Message 310

(value) Illegal packet received from network

EXPLANATION: An unexpected or invalid packet was received from the network.

SUBCODE INFORMATION:

X'2511'  Unrecognized qualified data packet.

X'2555'  Illegal Reset Indication packet.

X'2556'  Illegal Reset Confirm packet.

X'2557'  Illegal Restart Indication packet.

X'2558'  Illegal Incoming Call packet.

X'2559'  Illegal Call Connected packet.

X'255A'  Illegal Clear Indication packet.

X'255B'  Illegal Clear Confirm packet.

X'255C'  Unrecognized packet type.

X'255E'  Received an unexpected or invalid packet on a PVC.

ACTION: Provide network support personnel with the event log file(s) related to SNA and SNA trace file(s) such as Data Link Control trace files for the SnaServer. For information about SNA log and trace files, see the Microsoft SNA Server Administration Guide.

Message 311

INTERRUPT packet (invalid for SNA) received on connection value.

EXPLANATION: An INTERRUPT packet has been received over an X.25 connection. This results in a link outage being created and the connection being brought down.

ACTION: Contact support services at your site if this problem persists.

Message 312

Data received on connection value before QLLC in information transfer

EXPLANATION: X.25 NORMAL data (with the Q bit clear) has been received over a Virtual Circuit (VC) before a QLLC connection has been activated.

ACTION: Retry the procedure; if it continues to fail, contact support services.

Message 313

QLLC contact procedures for connection value have timed out

EXPLANATION: A link time-out has occurred while trying to establish a QLLC connection over X.25.

ACTION: Retry the procedure; if it continues to fail, contact support services.

Message 314

EICON initialization failed

Message 315

The port for this link service is not valid

Message 319

Call Cleared due to local buffer shortage

EXPLANATION: Abandoned an attempt to initiate a call because of a buffer shortage.

ACTION: Retry the operation that initiated the connection.

Message 320

Device driver value error on function value, rc = value

EXPLANATION: An internal error has been reported by the X.25 device driver.

ACTION: Provide support services at your site with details of the function number and return code shown on this message.

Message 321

Open failed for device driver. Windows NT rc = value

EXPLANATION: An attempt to open the X.25 device driver caused an error. The return code from the OpenFile call is shown.

ACTION: See your Windows NT documentation for information on return codes. Check the return code. This probably indicates that the driver is not installed or is already in use.

Message 322

Driver value DSR is OFF at initialization

EXPLANATION: The DSR signal from the modem has not come up, which indicates that the modem is not functioning correctly.

ACTION: Check the modem connections and make sure the modem is functioning correctly. See the Microsoft SNA Server Administration Guide for more information.

Message 324

Driver value DSR has come ON

EXPLANATION: The DSR signal from the modem has come up. This message follows message #322 or #325 when the modem becomes operational.

ACTION: No action is necessary.

Message 325

Driver value DSR has gone OFF: probable modem failure

EXPLANATION: The DSR signal from the modem has gone down during communications, which indicates that the modem is not functioning correctly.

ACTION: Check the modem connections and functions. See the Microsoft SNA Server Administration Guide for more information.

Message 326

Driver value unable to use DMA

EXPLANATION: SNA Server cannot use Direct Memory Access (DMA) for this driver either because the adapter card does not support DMA or DMA is already being used on another card. SNA Server will operate with the driver in character interrupt mode. This could affect performance.

ACTION: No action is necessary.

Message 327

Switched Virtual Circuit established for connection value

EXPLANATION: A Call Connected packet has been received from the network in response to a Call request for the indicated connection.

ACTION: No action is necessary.

Message 328

Virtual Circuit lost for connection value

EXPLANATION: An X.25 virtual circuit for connection conname has ended. If the connection failed, this message is accompanied by other messages indicating the reason for the failure.

Message 329

Outgoing Call Request has been timed out.

Check that the configured channel ranges are valid.

EXPLANATION: An attempt to initiate a connection over a switched virtual circuit has timed out. A common reason for this is that the channel number ranges for the X.25 link service were configured incorrectly.

Message 331

Invalid packet received (header = value)

Channel number = value

Packet type  = value

EXPLANATION: A packet has been received with an invalid header format or channel number. The packet header is displayed (3 bytes shown in hexadecimal), along with the channel number (decimal) extracted from the header, and the packet type identifier (hexadecimal) with protocol information removed.

Message 332

RESTART packet received from network.

Cause  = value

Diagnostic = value

EXPLANATION: A RESTART packet has been received from the X.25 network. All virtual circuits are cleared and reset, and any active connections will be lost. The displayed Cause and Diagnostic are the cause and diagnostic fields (shown in decimal) from the RESTART packet.

A RESTART packet is normal whenever communication between the X.25 link service and the X.25 network is first established.

Message 333

CLEAR packet received from network on channel value

Cause  = value

Diagnostic = value

EXPLANATION: A CLEAR packet has been received from the X.25 network. The connection using the indicated channel of the switched virtual circuit is broken. The displayed Cause and Diagnostic are the cause and diagnostic fields (shown in decimal) from the CLEAR packet.

A CLEAR may also be the response to a CALL packet indicating that the switched virtual circuit could not be completed. A cause code value of zero indicates that the CLEAR originated from the host.

Message 334

RESET packet received from network on channel value

Cause  = value

Diagnostic = value

EXPLANATION: A RESET packet has been received from the X.25 network. The connection using the indicated channel of the switched virtual circuit is broken. The displayed Cause and Diagnostic are the cause and diagnostic fields (shown in decimal) from the RESET packet.

A value of zero for the Diagnostic indicates that the RESET originated from the host.

ACTION: If the RESET was unexpected, restart the link service with tracing on, and try to reproduce the error. Contact the host administrator if the problem occurs again.

Message 335

Incoming CALL packet received on channel value

Remote (calling) NUA = value

Local (called) NUA  = value

Facility data  = value

EXPLANATION: An incoming CALL packet indicates that a remote computer is attempting to establish an X.25 connection with a local SNA Server. This will be rejected unless an active local SNA Server has been configured to receive incoming calls to address locNUA and has an X.25 connection configured with address remNUA.

The "Facility data" is a hexadecimal representation of the facility data on the CALL packet. If the requested facilities are invalid or not supported by the X.25 link service, the CALL is rejected.

No action is necessary.

Message 336

CALL CONNECTED response received on channel value

Remote (called) NUA = value

Local (calling) NUA = value

Facility data  = value

EXPLANATION: A switched virtual circuit has been connected successfully on the specified channel. This packet is an "OK" response to a previous CALL request packet sent by the X.25 link service.

The returned facility data is displayed in hexadecimal. The values may have been negotiated (altered) by either the remote host or the X.25 network itself.

Note:  The locNUA may be filled in by the X.25 network itself, even if it has not been configured and was not present on the initial CALL packet.

No action is necessary.

Message 337

RESTART packet sent. Diagnostic = value

EXPLANATION: The X.25 link service has sent a RESTART request to the X.25 network. Any active connections are lost.

A RESTART packet is normal whenever communication between the X.25 link service and the X.25 network is first established, but otherwise may indicate that a serious failure has occurred.

ACTION: If the RESTART was unexpected, restart the link service with tracing on, and try to reproduce the error. Contact the host administrator if the problem occurs again.

Message 338

CLEAR packet sent on channel value. Diagnostic = value

EXPLANATION: The X.25 link service has sent a CLEAR request to the X.25 network, breaking the switched virtual circuit on the indicated channel.

A diagnostic code of zero is sent when the virtual circuit is being cleared because the connection using it is no longer active. Non-zero values are sent when the X.25 link service detects an incorrect or unexpected packet from the host or the X.25 network.

ACTION: If the CLEAR was unexpected, restart the link service with tracing on, and try to reproduce the error. Contact the host administrator if the problem occurs again.

Message 339

RESET packet sent on channel value. Diagnostic = value

EXPLANATION: The X.25 link service has sent a RESET request to the X.25 network on the indicated permanent virtual circuit channel. The connection using the circuit was lost.

A diagnostic code of zero is sent when the virtual circuit is being reset because the connection using it is no longer active. Non-zero values are sent when the X.25 link service detects an incorrect or unexpected packet from the host or the X.25 network.

ACTION: If the RESET was unexpected, restart the link service with tracing on, and try to reproduce the error. Contact the host administrator if the problem occurs again.

Message 340

Outgoing CALL packet sent to NUA value on channel value

Local (calling) NUA = value

Facility data  = value

User data  = value

EXPLANATION: This is a log of the CALL packet sent when attempting to initiate a connection to the host configured with NUA remNUA. The X.25 link service used the first available channel (channel number indicated) on which to send the CALL. Any subsequent CLEAR should be received on the same channel. No action is necessary.

Message 341

CALL ACCEPTED response sent on channel value

Facility data = value

EXPLANATION: An incoming CALL on the indicated channel number has been accepted. The facility data values may have been negotiated (altered) by the X.25 link service. No action is necessary.

Message 342

Unexpected packet type (value) received on connection value

EXPLANATION: The indicated connection has been lost. The "packet type" value is the packet type identifier field (hexadecimal) with protocol information removed from the erroneous packet's header.

ACTION: Restart the link service with tracing on, and try to reproduce the error. Contact the host administrator if the problem occurs again.

Message 343

Unexpected QLLC control field (value) received on connection value

EXPLANATION: The indicated connection has been lost. The "control field" value is a hexadecimal representation of the QLLC (qualified logical link control) control field from the packet causing the problem. QLLC is one of the protocols commonly used for transporting SNA data over X.25 virtual circuits.

ACTION: Restart the link service with tracing on, and try to reproduce the error. Contact the host administrator if the problem occurs again.

Message 344

Invalid QLLC control field (value) received on connection value

EXPLANATION: A packet has been received from the X.25 network which has the Q bit set, but does not contain a valid QLLC command.

ACTION: Contact support services.

Message 345

Invalid QLLC i-field (cfld value, len value) on connection value

EXPLANATION: A recognized QLLC packet has been received from the X.25 network, but the packet has an illegal i-field (data) attached.

ACTION: Contact support services for the service being accessed.

Message 346

Q Frame Reject received on connection value: info = value

EXPLANATION: A Frame Reject from the X.25 network has been received.

ACTION: No action is necessary.

Message 347

X.25 link service value not configured in value

EXPLANATION: An attempt was made to start an SNA Server X.25 link service with a service name that is not in the configuration file.

ACTION: Use SNAX25.DLL with the link service name used in the configuration file.

Message 348

Incorrect parameters on starting X.25 link service

EXPLANATION: This is an internal error that should not occur during normal operation.

ACTION: Contact support services at your site.

Message 350

Run out of memory

EXPLANATION: The SNA Server component that logged this message is unable to continue due to a memory shortage.

ACTION: If you continue the file transfer process, the system may or may not complete the procedure. If possible, stop any programs that are unnecessary, and then retry.

Message 351

Error trying to read from value (rc = value)

EXPLANATION: A Windows NT error occurred during an attempt to read configuration information from the file shown for the component that logged this message.

ACTION: Check the Windows NT return code shown on this message. See your Windows NT documentation for information on return codes.

Message 352

Unable to open the configuration file, rc = value

EXPLANATION: A Windows NT error occurred while attempting to open the configuration file to obtain configuration information for the component that logged this message.

This error could be due to one of the following:

You have not configured the server using the SNA Server Admin program

The configuration file is corrupt

This is a member server and the primary/backup servers are not available

ACTION: Check the Windows NT return code shown on this message. See your Windows NT documentation for information on return codes.

Message 353

Link service record for value in value is too short

EXPLANATION: The configuration file information on a link service is invalid, indicating an internal error in the configuration program.

ACTION: Provide network support personnel with a copy of the SNA Server configuration file. For information about the configuration file, see the Microsoft SNA Server Administration Guide.

Message 360

(value) Unexpected error logged

EXPLANATION: An internal error. An SNA Server component has used an internal message that does not appear in SNA Server. Although logged at level 12 to ensure that it is not ignored, this does not necessarily indicate a level 12 problem.

ACTION: Provide network support personnel with the event log file(s) related to SNA, SNA internal trace file(s), and any information displayed in this message. For information about SNA log and trace files, see the Microsoft SNA Server Administration Guide.

Message 361

Failed to open help file value, rc = value

EXPLANATION: The help file shown could not be opened. The return codes generated are listed here.

SUBCODE INFORMATION:

1	OpenFileOnPath failed. Check that the file exists in a directory in the PATH environment variable, and that you have permission to access the file.

2	Could not read file header. The help file may have been corrupted.

3	Too many open help files. This error should not occur during normal use. Contact support services at your site.

4	Bad appended file. This error should not occur during normal use. Contact support services at your site.

5	The file accessed was not a help file. You may have copied another file to this file by mistake.

6	Incompatible version. The version of the help file is incompatible with the version of the program you are using. Make sure you are using the help file that was provided with the program.

7	Memory allocation failed. There was not enough memory available to open the help file. Try to clear more memory and then retry.

ACTION: Check the return code and take the indicated action.

Message 362

Could not find help ID value in help file value

EXPLANATION: This is an internal error. The help text for a particular dialog or menu item could not be found in the help file.

ACTION: Make a note of the help ID and file name reported on this message, and contact support services at your site.

Message 390

The following alert was sent on session value

Title: value

EXPLANATION: A 3270 user sent a NetView user alert via a 3270 emulator. The title of the user alert is shown, along with any user-supplied parameters. No action is necessary.

NetView user alerts are configured using the NetView command from the Options menu in the SNA Server Admin program.

Message 391

value: value value

Message 392

Warning: User Alert was not accepted by the host

EXPLANATION: A 3270 user sent a user alert, but the host sent a negative response. Either the host does not accept this particular alert number or the NetView program is not running at the host.

ACTION: Check with the host administrator to determine whether the alert is invalid or NetView is not running.

Message 393

Audit message logged by value : value

Message 394

Error message logged by value : value

Message 397

Cannot support any further client applications

Message 540

NMVT type value logged by value, data:

value

EXPLANATION: An alert is logged by an SNA Server component to indicate an error condition, or by an application program using the TRANSFER_MS_DATA verb.

ACTION: See Chapter 2, "Network Management," for explanations of alert formats.

Message 543

Can't switch focus: background thread has not terminated

Message 544

The connection to the network has been established.

Message 545

This type of SnaBase service must run on a system which is not sharing COMCFG

Message 546

Cannot establish connection with sponsor box value.

Message 547

The connection to the sponsor box value has been lost.

Message 548

The SnaBase service was already started in another MS-DOS session

Message 549

Cannot start SNA Server Admin on remote client.

Message 550

Previous attempts to log failed, value messages lost

Message 551

Memory allocation failure, rc = value

EXPLANATION: A resource error occurred during initialization. The return code from GlobalAlloc is shown.

ACTION: Check the return code. Check that there is enough memory for the new process.

Message 552

Failed to create receive thread, rc = value

EXPLANATION: A CreateThread call has failed. The return code is shown.

ACTION: Check the return code. Provide support services at your site with the log file and return code.

Message 553

Could not create mailslot, rc = value

EXPLANATION: A CreateMailslot call failed. The return code is shown.

ACTION: Check the return code. Provide support services at your site with the log files.

Message 554

Unknown OPEN, type = value

EXPLANATION: This is an internal error. An application supplied an invalid OPEN message.

ACTION: Provide support services at your site with the log files.

Message 555

Local routing table full: too many clients using the service

EXPLANATION: The system is limited to 1024 processes using any one service. This limit should not be reached in normal operation.

ACTION: Contact support services at your site.

Message 556

A system error occurred while making a pipe connection, rc = value

EXPLANATION: An internal error occurred during an attempt to open a connection.

ACTION: Provide network support personnel with the event log file(s) related to SNA, and the return code included in this message. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 557

DLOAD has timed out

EXPLANATION: The node requested dynamic loading of an APPC TP, but did not receive a response from the TP within the specified time. This could be caused by the following conditions:

The TP started but failed before issuing a Receive_Allocate (check for messages logged by the TP).

The "Timeout for Starting TPs" for the local APPC LU used by this TP is too short.

The TP is operator-started, and the operator did not start it.

Message 558

Could not create service table semaphore, rc = value

EXPLANATION: A CreateSemaphore call failed. The return code is shown.

ACTION: Provide network support personnel with the event log file(s) related to SNA, and the return code included in this message. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 559

The SnaBase service is already active

EXPLANATION: An attempt was made to start the SnaBase after it was already running. Each computer can run only one copy of the SnaBase at a time.

ACTION: No action is necessary.

Message 560

Read from mailslot failed, rc = value

EXPLANATION: A ReadFile call failed. The return code is shown.

ACTION: Provide network support personnel with the event log file(s) related to SNA, and the return code included in this message. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 561

Write to mailslot failed, rc = value

EXPLANATION: A WriteFile call failed. The return code is shown.

ACTION: Provide network support personnel with the event log file(s) related to SNA, and the return code included in this message. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 562

Failed to obtain workstation information, rc = value

EXPLANATION: A NetWkstaGetInfo call failed. The return code is shown.

ACTION: Check that the workstation service has been started. Provide network support personnel with the event log file(s) related to SNA, and the return code included in this message. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 563

The service table is full: too many network resources active

EXPLANATION: The system limit of 254 active services is reached and another service cannot be activated.

ACTION: Remove any services that are no longer required. Contact support services at your site.

Message 564

Failed to initialize exit list processing, rc = value

EXPLANATION: A DosExitList call on an OS/2-based client failed. The return code is shown.

ACTION: Provide network support personnel with the event log file(s) related to SNA, and the return code included in this message. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 565

Failed to access shared memory, rc = value

EXPLANATION: A CreateFileMapping call failed. The return code is shown.

ACTION: Provide network support personnel with the event log file(s) related to SNA, and the return code included in this message. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 566

Write to a named pipe failed, rc = value

EXPLANATION: A WriteFile call failed. The return code is shown.

ACTION: Provide network support personnel with the event log file(s) related to SNA, and the return code included in this message. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 567

Creation of a named pipe failed, rc = value, pipe = value

EXPLANATION: A CreateFile call failed. The return code is shown.

ACTION: Provide network support personnel with the event log file(s) related to SNA, and the return code included in this message. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 568

Failed to associate pipe with semaphore, rc = value

EXPLANATION: A DosSetNmPipeSem call on an OS/2-based client failed. The return code is shown.

ACTION: Provide network support personnel with the event log file(s) related to SNA, and the return code included in this message. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 569

Error when querying pipe semaphore, rc = value

EXPLANATION: A DosQNmPipeSemState call on an OS/2-based client failed. The return code is shown.

ACTION: Provide network support personnel with the event log file(s) related to SNA, and the return code included in this message. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 570

Dynamic load failed

EXPLANATION: The node requested dynamic loading of an APPC TP but the TP cannot be started. This message is usually accompanied by message #575, giving the TP name and the reason for failure.

ACTION: See the accompanying message (#575).

Message 571

Unable to read from Named Pipe, rc = value

EXPLANATION: An Asynchronous read on a connection failed. The return code is shown.

ACTION: Provide network support personnel with the event log file(s) related to SNA, and the return code included in this message. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 572

Premature timeout of a DLOAD request

EXPLANATION: Received a response to a dynamic load request that already timed out. The invokable TP was not started within the specified time, so the request has been canceled.

ACTION: The timeout may be too short — try increasing it.

Message 573

Process has ended abnormally

EXPLANATION: A service or a client ended abnormally due to an exception condition. There may be other messages preceding this one that indicate the nature of the error. Also, a dump file was created. A message with number 624 gives the name of the dump file.

ACTION: Check other messages.

Message 574

Unexpected message type value

EXPLANATION: This is an internal error in SNA Server.

ACTION: Provide network support personnel with the event log file(s) related to SNA, and SNA internal trace file(s). For information about SNA log and trace files, see the Microsoft SNA Server Administration Guide.

Message 575

Failed to execute a program, rc = value, name = value

EXPLANATION: A CreateProcess call for a dynamically loaded TP failed. The return code is shown.

ACTION: Provide network support personnel with the event log file(s) related to SNA, and the return code included in this message. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 576

No more DLOAD queue entries available

EXPLANATION: A TP reached the limit of 256 queued allocates. The TP cannot process requests quickly enough to keep up with the requests coming in.

ACTION: If possible, speed up the processing of the TP (for example, it may be slow due to memory shortage), or redistribute the load by setting up another TP.

Message 577

Dynamic load request received for non-existent TP

EXPLANATION: This is an internal error in SNA Server.

ACTION: Provide network support personnel with the event log file(s) related to SNA. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 578

SnaBase service cannot be run on an SNA Server 1-User system

EXPLANATION: You attempted to start the SNA Server SnaBase service, but SNA Server 1-User components were already running. SNA Server and SNA Server 1-User cannot run on the same computer.

ACTION: Stop the SNA Server 1-User components before trying to start the SNA Server SnaBase service.

Message 579

Source and dest incompatibility, msg = value,value, parms = value,value

EXPLANATION: This is an internal error in SNA Server.

ACTION: Provide network support personnel with the event log file(s) related to SNA, and SNA internal trace file(s). For information about SNA log and trace files, see the Microsoft SNA Server Administration Guide.

Message 580

Sending a message to inactive destination id value

EXPLANATION: A message is routed to an inactive process. This is generally caused by abnormal termination of an SNA Server component.

ACTION: Check for previous messages indicating abnormal termination. Follow the actions suggested for them.

Message 581

3270 Emulation (value) started

EXPLANATION: This message is for informational purposes.

No action is necessary.

Message 582

No name supplied in the parameter list for this component

EXPLANATION: SNA Server started the component without supplying a name. This is an SNA Server internal error.

ACTION: Provide network support personnel with the event log file(s) related to SNA. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 583

Failed to address a buffer pool, rc = value

EXPLANATION: A CreateFileMapping call failed. The return code is shown.

ACTION: Provide network support personnel with the event log file(s) related to SNA, and the return code included in this message. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 584

Routing table entry value is no longer required

EXPLANATION: This message indicates that an internal routing table entry between components is no longer required because the association between the components has ended (for example, the end of a conversation).

ACTION: No action is necessary.

Message 585

Please load TP : value

Program: value

Parameters: value

Time limit: value seconds

EXPLANATION: This is a request to load an operator-started TP.

ACTION: Load the program shown using the parameters listed.

Message 586

The workstation service must be started before the SnaBase service can be started

ACTION: Use the NET START WORKSTATION command (for a client) or NET START SERVER (for a server) before starting the SnaBase service. Or use the Windows NT Control Panel to start the appropriate services in order. For a client, start the workstation service, and then the SnaBase service. For an SNA server, start the workstation service, then the Server service, and then the SnaBase service.

Message 587

Message did not have value elements as indicated in the header

EXPLANATION: This is an internal error in SNA Server.

ACTION: Provide network support personnel with the event log file(s) related to SNA, and SNA internal trace file(s). For information about SNA log and trace files, see the Microsoft SNA Server Administration Guide.

Message 588

Failed to add SnaBase exit list, rc = value

EXPLANATION: A DosExitList call failed. The return code is shown.

ACTION: Provide network support personnel with the event log file(s) related to SNA, and the return code included in this message. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 589

Failed to display a pop-up, rc = value

EXPLANATION: A CreateProcess call for the pop-up process failed. The return code is shown.

ACTION: Check the return code and attempt to free more memory. A return code of 999 indicates that a pop-up could not be displayed on an MS-DOS-based system because an application was already using the foreground screen.

This error is caused by a resource shortage on the system.

Also, provide network support personnel with the event log file(s) related to SNA. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 590

This service terminated by administrator

EXPLANATION: The process was terminated by the administrator, using either the SNA Server Admin program or the SNA Server command-line interface.

ACTION: No action is necessary.

Message 591

TP has not been configured

EXPLANATION: A TP issued the RECEIVE_ALLOCATE verb with a TP name that is not known to the system.

ACTION: Check the TP name against the configuration. The TP should supply a name that matches the Full TP Name field in an Invokable TP record. For information about TPs, see the Microsoft SNA Server APPC Programmer's Guide or the Microsoft SNA Server CPI-C Programmer's Guide.

Message 592

Receive Allocate has timed out

EXPLANATION: Receive_Allocate timed out. No incoming allocate was accepted within the configured timeout period.

ACTION: Increase the configured timeout period if the timeout was not due to an error. This timeout is specified for the local APPC LU in the APPC LU Properties dialog box of the SNA Server Admin program.

Message 593

Too many routing entries attempted

EXPLANATION: This is an SNA Server internal error.

ACTION: Provide network support personnel with the event log file(s) related to SNA. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 594

DLOAD free queue contention is relieved

EXPLANATION: The SNA subsystem succeeded in queuing an ALLOCATE request to the TP. This means that the condition indicated by the previous message #576 (no more DLOAD queue entries available) cleared. This is not an error condition, but is logged at the same level as

#576 to ensure that both messages will appear.

ACTION: Refer to message #576.

Message 595

Buffer pool has been extended to value kilobytes

EXPLANATION: The buffer pool emptied and had to be extended. This condition is caused by heavy usage of the node. If it occurs too frequently it may cause performance problems. The pool size will be increased in increments of 16 K until it reaches 128 K.

ACTION: The 128 K limit can be increased by using the COMBUF Registry variable. For information about COMBUF, see Appendix C, "Registry and Environment Variables for SNA Server."

Message 596

Attempt to start duplicate service value

EXPLANATION: An attempt was made to start a network service when a service of the same name is already started. The service name must be unique.

ACTION: Use unique service names.

Message 597

User limit of value exceeded: client connection rejected

EXPLANATION: The maximum number of licensed users (shown) has been reached and another cannot be added.

ACTION: Upgrade to a larger version of the system or install another server.

Message 598

No LAN user ID found: perform NET LOGON

EXPLANATION: A user attempted to start the SnaBase service on a client without first logging on to the LAN.

ACTION: Use the NET LOGON command to log on to the LAN, then restart the SnaBase service.

Message 599

Routing error on RAM pipe

EXPLANATION: This is an SNA Server internal error.

ACTION: Provide network support personnel with the event log file(s) related to SNA. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 600

Open pipe failed as all available manage connections are in use

Message 601

Open pipe failed as all available pipes are in use

Message 602

value client executables already connected to value.

Unable to connect any more

Message 603

The queued transaction program is already started

EXPLANATION: You attempted to start a queued TP that had already been started. Only one copy of a queued TP may be run at a time. (Incoming [MC_]ALLOCATEs are queued until the program is available.)

ACTION: If multiple concurrent copies of the TP are required, it must be configured as non-queued.

Message 604

Bad client type value

EXPLANATION: A client has called the DMOD initialization for Windows (SBPWINIT) with an invalid client type.

Message 605

SNA Server version mismatch: Version value detected on type value mailslot from computer value

Message 606

SNA Server version mismatch: Version value client value initiating communication with server value

Message 607

SNA Server version mismatch: Client value opening connection to version value server value

Message 608

Configuration file version is value: expected 2.1

Message 609

No valid version record found in configuration file

Message 610

Not authorized to access pipes on server value

EXPLANATION: A user tried to access the server without having the necessary access permissions.

ACTION: If access to this server is required by a particular user, update the LAN access permissions.

Message 611

The following event log entry has been written:

value

EXPLANATION: The warning (level 12) or error (level 16) shown in this message has been logged.

Message 612

The following log entry could not be written:

value

Logging has been disabled

EXPLANATION: The event log entry could not be recorded in the event log.

ACTION: Adjust the parameters that control the length of time that entries are retained in the Windows NT Event Log, or the parameters that control the size of Windows NT Event Log. For more information, see your Microsoft Windows NT documentation.

Message 613

Invalid computername or type of SnaBase service

EXPLANATION: An attempt was made to start an invalid type of SNA server software or SNA client software for the specified computername. The possible types are as follows:

The primary SNA server, on which the primary configuration file is stored. There can be only one primary SNA server in a domain.

Backup SNA server(s), on which extra copies of the latest configuration file should be stored. There can be more than one backup SNA server in a domain.

Member SNA servers, on which there is no SNA configuration file. There can be more than one member SNA server in a domain.

Client computers, which run client software, not SNA server software.

ACTION: To change the role of the SNA server or SNA client, use the SNA Setup program. For information about Setup, see the Microsoft SNA Server Installation Guide.

Message 614

Network Server service must be started before SnaBase can be started for an SNA server

EXPLANATION: Before starting a primary, backup, or member SNA server, the network Server service must be started.

ACTION: Use the NET START SERVER command before starting the SnaBase service for a primary, backup, or member SNA server. Or use the Windows NT Control Panel to start the Server service before starting the SnaBase service.

Message 615

Invalid MS-DOS version

EXPLANATION: You attempted to start the SnaBase service on a computer running a version of MS-DOS before 3.2. MS-DOS version 3.2 or later is required for an MS-DOS-based client.

ACTION: Upgrade the operating system software.

Message 616

Failed to open configuration file value

EXPLANATION: SNA Server failed to open the specified configuration file. This is usually caused when you do not have permission to access the configuration file.

ACTION: Make sure access permissions are set up for your LAN operating environment and that you are logged on to the LAN with the correct user ID and password.

Message 617

Cannot have two nodes running on one server

EXPLANATION: You attempted to start two nodes on the same server. You cannot run two nodes on one server.

Message 618

Failed to access configuration file value, rc = value

EXPLANATION: The process cannot read the configuration file. The file name shown should be COM.CFG. If anything else appears here, it indicates an internal error. Normally the Windows NT return code is shown. However, three additional values can also be returned here:

612      No configuration file is available at present.

616      Failed to obtain name of configuration file.

618      Invalid or corrupted configuration file.

ACTION: Contact support services at your site. For return codes 616 and 618, check that the file COM.CFG exists in the SYSTEM\CONFIG subdirectory of the SNA Server root directory, and that it is a valid configuration file (try opening it using the SNA Server Admin program). If you still have a problem, contact support services at your site.

Message 619

Failed to open pipe for DLOAD error response

EXPLANATION: This is an SNA Server internal error.

ACTION: Provide network support personnel with the event log file(s) related to SNA. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 620

System shutdown requested

EXPLANATION: A shutdown is requested when a new version of the system is installed. This message is logged when a shutdown request is received. All SNA Server processes are terminated. No action is necessary.

Message 621

Invalid parameter to SnaBase. Must be:

[\\servername1 [\\servername2]]

Message 622

No dump file available

ACTION: Remove the dump files that are no longer needed.

Message 623

Maximum SNA Server errors reached

EXPLANATION: This is an SNA Server internal error.

ACTION: Provide network support personnel with the event log file(s) related to SNA. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 624

Creating dump file value for value

EXPLANATION: A process (value) ended abnormally due to a protection violation or similar condition and a dump file value has been created that contains information about the state of the process at the time of the exception. Register information is contained in your Windows NT root directory in the file DRWTSN32.LOG.

ACTION: For more information on diagnostics, refer to the Microsoft SNA Server Administration Guide. Provide network support personnel with the event log file(s) related to SNA, the SNA dump file, and the Dr. Watson log file.

Message 625

The SnaBase service must be running before anything else

EXPLANATION: You attempted to start an SNA Server process on a computer where the SnaBase service was not running.

ACTION: Start the SnaBase service before any other SNA Server process.

Message 626

Service started

EXPLANATION: The service shown in the message header started successfully.

ACTION: No action is necessary.

Message 627

Internal routing call failed

EXPLANATION: This is an internal error in SNA Server.

ACTION: Provide network support personnel with the event log file(s) related to SNA. For information about SNA log files, see the Microsoft SNA Server Administration Guide.

Message 629

No SNA Server configuration broadcast received

A server must be available before you can use 3270 or APPC

EXPLANATION: You attempted to start an application when there is no SNA Server on the LAN or the SNA Server did not broadcast information before the application was started.

Message 630

Failed to get SNA Server path from base driver on an OS/2-based client.

ACTION: On the OS/2-based client, check that the device driver line for COMBASE.SYS is correct in the CONFIG.SYS file. This line should have been added by the installation program, and should have the following form:

DEVICE=C:\COMMSRV\DEV\COMBASE.SYS C:\COMMSRV

In this line, both instances of C:\ should be replaced by the actual path of the COMMSRV home directory.

For SNA Server 1-User, this line should be in the following form:

DEVICE=C:\COMMWS\DEV\COMBASE.SYS C:\COMMWS

In this line, both instances of C:\ should be replaced by the actual path of the COMMWS home directory.

Message 631

Invalid message received across the LAN

EXPLANATION: This is an internal error.

ACTION: Contact support services at your site.

Message 632

Error scanning CONFIG.SYS, rc = value

EXPLANATION: A Windows NT error occurred during a scan of the CONFIG.SYS file for driver information on starting the SnaBase.

ACTION: Check the Windows NT return code shown.

Message 633

The sharename COMCFG does not exist, or the SNA Server configuration file COM.CFG does not exist.

EXPLANATION: When a primary or backup SNA server is started, it must be sharing the configuration file on a share called \\servername\COMCFG, where servername is the name of the server. This is checked by the SnaBase at startup.

A SnaBase started as a backup SNA server will also check the file replication information and may log message #634 as well.

Message 634

The SnaBase for a backup SNA server has been started on a system with no file replication active.

EXPLANATION: File replication is recommended for keeping a current copy of the configuration file on each backup SNA server. These copies of the configuration file should always kept current, so that incorrect or divergent copies are never loaded or saved.

Message 635

Error: Primary SNA server already running in value

EXPLANATION: You tried to start two primary SNA servers in the domain. Only one server in the domain can be the primary SNA server.

ACTION: Use the Setup program to change one of the primary SNA servers to a backup or member server.

Message 636

An SNA server (node) can be started only if SNA server software (primary, backup, or member) has been installed.

EXPLANATION: The SNA server (node) cannot be started if the installed SnaBase is for clients.

ACTION: Start the SNA server (node) on a computer on which the software for a primary, member, or backup SNA server has been installed.

Message 637

There is no driver in CONFIG.SYS to support link service value

EXPLANATION: You tried to start a link service using a device driver that is not loaded.

ACTION: Do one of the following:

Load the device driver using the DEVICE= statement from  the command line.

Upgrade CONFIG.SYS to include the DEVICE= statement for the device driver, and then reboot the PC.

Message 638

Possible Replication problem: the primary SNA server was started on a system with file replication active but not replicating the SNA configuration file.

EXPLANATION: Check to see if this computer is supposed to support replication of SNA Server files. If not, ignore the message. If SNA Server file replication is intended, set up file replication with Windows NT.

ACTION: For information about setting up file replication, see your Windows NT documentation.

Message 639

Failed to open pipe to service value, rc = value

EXPLANATION: This message can be produced by any of the SNA Server components:  3270, APPC, or link services. The return code is either from the LAN or from Windows NT.

ACTION: Refer to your LAN or Windows NT documentation for explanations of the return codes, and then take the recommended actions.

Message 643

Invokable TPs can only be executed in the background when LAN Manager local security is active

EXPLANATION: You can execute invokable TPs only in the background when local security is active on the network. This message only applies to OS/2-based clients.

ACTION: Reconfigure the TP to run without a screen group, if it can run in that mode. Otherwise, load the TP on a server that is not running local security.

Message 644

Failed to open the primary trace file value, rc = value

EXPLANATION: There was a problem opening the primary trace file. The name may have been entered incorrectly.

ACTION: Check the Windows NT return code shown on this message. See your Windows NT documentation for more information on return codes and take the recommended action.

Message 645

Failed to open the secondary trace file value, rc = value

Tracing will proceed to the primary file without flip-flop

EXPLANATION: There was a problem opening the secondary trace file. Tracing will continue using the primary trace file.

ACTION: Check the Windows NT return code shown on this message. See your Windows NT documentation for information on return codes and take the recommended action.

Message 646

Failed to access configuration file value on this server, rc = value

EXPLANATION: This server is configured as a primary or backup SNA server but a local SNA Server component has failed to open COM.CFG.

ACTION: Check access permissions and make sure the file exists.

Message 647

SNA Server could not initiate LAN communications due to a LAN connection failure.

EXPLANATION: The first mailslot broadcast issued a return code 2136 — NERR_NetworkError. This means that although the primary or backup SNA server (node) started, the LAN is down. Any services started on the SNA server cannot communicate with clients or with other nodes, but you can work locally on the SNA server.

ACTION: Contact the LAN administrator at your site to get the LAN working.

Message 648

Connection to client computer value taken down: too much data queued to the client.

EXPLANATION: A server-client connection to an MS-DOS-based client or Windows-based client has been lost because the client has been switched out for a considerable amount of time and the server has run out of space for queuing the data it needs to send to the client.

ACTION: Contact support personnel at your site.

Message 649

Unable to create another connection: reached limit on number of processes.

Message 650

ConnectNmPipe returned error rc = value.

Message 651

Failed to load value

EXPLANATION: The COMM START command failed because the file shown cannot be loaded. If the file is listed with an extension of .EXE, the file is executable. If the file is listed with no extension, it is a .DLL file.

ACTION: Check to see that the file exists and that the PATH environment variable for an executable file, or LIBPATH for a .DLL file, is set up to point to the directory containing the file. Also, make certain that there is enough memory to load the executable files.

Message 652

value is already started

EXPLANATION: Service specified by the COMM START command is already started. No action is necessary.

Message 653

value is not a valid service name

EXPLANATION: The service name supplied to COMM START was not found in the configuration file.

ACTION: Check the correct name in the configuration file and retry COMM START.

Message 654

value failed to start in the allowed time. Check the event log.

EXPLANATION: An attempt to start the service failed.

ACTION: Check the event log files for other messages indicating the reasons for the failure, and take the recommended action(s).

Message 655

value has not been started

EXPLANATION: The COMM STOP command for the service is ignored because the service is not started.

ACTION: No action is necessary. Use the COMM START command without any parameters to list the services that have already been started.

Message 657

OS/2 error value occurred

EXPLANATION: An operating system error occurred while processing a COMM command. The OS/2 error code returned is shown. This message applies to OS/2-based clients only.

ACTION: Check the OS/2 error code shown.

Message 658

Another primary SNA server already running.

Message 659

Invalid configuration file

EXPLANATION: The configuration file running when SNA Server was asked to start a service is invalid. It might be corrupted, or might not be a configuration file.

ACTION: Check to see that the COM.CFG file exists in the directory specified by the COMCFG share on the primary SNA server.

If you need to replace the COM.CFG file, possible sources are the COM.CFG file on a backup SNA server, or files with the extension .SNA, which is the default extension for backup configuration files created with the File menu Backup command. Copy the appropriate configuration file to the filename COM.CFG. Place the configuration file in the SYSTEM\CONFIG subdirectory of the SNA root directory.

If the error still occurs, call support services at your site.

Message 660

The SnaBase service could not find a primary or backup SNA server.

EXPLANATION: The SnaBase service could not be started because there are no primary or backup SNA servers running in the SNA Server network, and therefore there is no configuration file for the SNA Server components to read.

ACTION: Start a primary or backup SNA server, and then restart the SnaBase service.

Message 661

There are no active network services

EXPLANATION: You used the COMM VIEW command without parameters, which provides a list of active services, but no services have been started. This message applies only to OS/2-based clients.

Message 662

There are no active network services at value

EXPLANATION: You used the COMM VIEW servername command to list all active services on the specified server, but no services were started on this server.

Message 663

The SnaBase service is already active on this computer

EXPLANATION: The SnaBase service could not be started because it has already been started on this computer. No action is necessary.

Message 664

Invalid SnaBase parameter value

EXPLANATION: The user attempted to start the SnaBase service with a parameter which is invalid.

ACTION: Start SNA Server services by using the Control Panel or the SNA Server Admin program. Specify the role of an SNA server or client by using the SNA Server Setup program.

For information about starting and stopping an SNA server, see the Microsoft SNA Server Administration Guide. For information about Setup, see the Microsoft SNA Server Installation Guide.

Message 665

The COMNAP service must be running to execute this command

EXPLANATION: The user on an OS/2-based client tried to run a COMM command without having started the necessary service.

ACTION: Start the COMNAP service and repeat the command.

Message 666

Services cannot be started on SNA Server client computers

EXPLANATION: Services cannot be started from an SNA Server client.

ACTION: Start the services from a server that contains the correct files to run the service.

Message 667

This computer is not configured to run the selected link service

EXPLANATION: To start a link service on a particular server, the correct device drivers must be configured in CONFIG.SYS.

ACTION: Use the Setup program to install the correct software and device drivers, and then start the link service. Refer to the Microsoft SNA Server Installation Guide for more information about installing the SNA Server product.

Message 668

Failed to open file value while checking that a backup configuration file was the same as the primary configuration file.

Retcode from CreateFile = value

EXPLANATION: A backup SnaBase was attempting to open its configuration file to check the file's date. The error means the backup file may not be the same as that on the primary SNA server.

ACTION: If this error persists contact your support personnel.

Message 669

Failed to open file value while checking that a backup configuration file was the same as the primary configuration file.

Retcode from CreateFile = value

EXPLANATION: A backup SnaBase was attempting to get its configuration file age. The error means the backup file may not be the same as that on the primary SNA server.

ACTION: If this error persists contact your support personnel.

Message 670

The primary configuration file value was successfully copied to value.

EXPLANATION: To maintain consistent configuration files across the domain, a backup SnaBase copied the configuration file from the primary SNA server.

ACTION: None.

Message 671

Copy of file value to value failed.

Retcode on CopyFile was value

EXPLANATION: To maintain consistent configuration files across the domain, a backup SnaBase was in the process of updating a backup configuration file from the primary SNA server.

It does this by:

1) Copying the backup COM.CFG to COM.BAK.

2) Copying the primary COM.CFG to COM.TMP.

3) Copying COM.TMP to the backup COM.CFG.

ACTION: The most common cause of this error is SNA Server Admin locking the file prior to writing a change. This will lead to retcode 32 and should clear once SNA Server Admin releases its lock. If the retcode is not 32 or this log is not eventually followed by the informational message 660 (indicating a successful copy), then contact your support personnel.

Message 672

Copy of file value to value has not been possible for over 5 minutes.

EXPLANATION: This message will have been preceded by a message 671. It indicates that the condition which initially prevented the file copy has persisted. Check message 671 for a retcode indicating the cause of the problem and follow the action suggested.

ACTION: See message 671.

Message 673

A Dload response specifying invalid Locality value was received.

EXPLANATION: This message may be recieved when SNA Server version 2.0 clients without patches are run in a 2.1 environment.

ACTION: Contact Microsoft Support for patches for your SNA Server version 2.0 clients or upgrade the client software.

Message 680

Failed to address remote buffer pool extension value

System return code value

EXPLANATION: An attempt was made to process a RamPipe to a local process and this failed. Possible causes include abnormal termination of the target process.

ACTION: If this message occurs repeatedly, or is accompanied by other severe errors then contact your support personnel.

Message 681

Failed to create remote buffer pool extension value

System return code value

EXPLANATION: An attempt was made to process a RamPipe to a local process and this failed. Possible causes include abnormal termination of the target process.

ACTION: If this message occurs repeatedly, or is accompanied by other severe errors then contact your support personnel.

Message 682

Remote buffer pool at maximum size

EXPLANATION: An attempt was made to process a RamPipe to a local process and this failed due to the target buffer pool having reached its maximum size.

ACTION: If this message occurs repeatedly, or is accompanied by other severe errors then contact your support personnel.

Message 683

Buffer inconsistency has been detected.

EXPLANATION: While processing a message, it was noticed that its structure was incorrect. This inconsistency would have led to corruption of the buffer pool, and then a trap at some point in the future.

To help locate the source of the corruption, the faulty component has been stopped and a dump initiated.

ACTION: Contact your support personnel.

Message 684

A buffer pool audit has been triggered by value

value

value

EXPLANATION: This audit contains information about the size of the buffer pool, how many headers and elements each process is using, etc.

ACTION: None, unless there is some other problem. In that case, report this log along with any others.

Message 685

An attempt was made to extend a buffer pool, but the related pool had reached its maximum size. The affected component is terminating, and an audit of the buffer pools just before termination is attached

value

value

EXPLANATION: This error is almost always due to either an SNA component (including possibly an emulator) losing buffers or a slow emulator (or RUI application) using a session without pacing.

ACTION: Contact your support personnel.

Message 686

SNA Server Internal buffer pool error.

Reason  = value

Module  = value

Process = value

Pool  = value

Details = value

EXPLANATION: While processing a buffer pool request, it was noticed that the buffer pool had been corrupted.

To help locate the source of the corruption, the component has been stopped and a dump initiated.

ACTION: Provide your network support personnel with the information contained in this message.

Message 687

SNA Server is applying link back-pressure.

EXPLANATION: Possibly due to one or more slow applications using sessions which are not configured with pacing, SNA Server is now using almost all of its buffers to queue messages. To prevent the shortage becoming fatal, SNA Server is temporarily stopping the inflow of data from the links.

ACTION: Contact your support personnel.

Message 688

SNA Server has release link back-pressure.

EXPLANATION: Sufficient buffers are now available for continued processing of data from the links.

ACTION: None required.

Message 689

The RUI \ 3270 buffer pool has reached its maximum extension. This is a fatal condition and all of  the pools users are now being terminated to maintain the stability of the server.

EXPLANATION: This error is almost always due to either an emulator losing buffers or a slow emulator (or RUI application) using a session without pacing.

ACTION: Contact your support personnel.

Message 951

No application accepted received message.

EXPLANATION: A message was received by the SnaBase service which was not accepted by any currently running application. The application for which the message was intended may have been terminated unexpectedly.

Message 952

Failed to get application file name, rc = value

Message 953

The maximum number of applications for this client has been exceeded.

EXPLANATION: You attempted to start more than the maximum allowed number (40) of applications on a Windows-based client.

Message 954

DMOD request from unknown application (internal error).

EXPLANATION: An application made a call to a DMOD routine (such as sepdrout or sbpusend) without first registering with the DMOD using the sbpuinit call.

ACTION: For information about the sbpuinit call, see the 3270 Emulator Interface Specification.

Message 955

Could not get shared memory address from DMOD (internal error).

Message 956

SnaBase cannot be terminated while its services are being used.

EXPLANATION: You attempted to terminate the SnaBase service while applications (such as a 3270 emulator or APPC) are still running.

ACTION: Terminate all applications before terminating the SnaBase service.

Message 1000

The service called value is not configured in the registry as an SNA service

Message 1001

There is no configuration file COM.CFG in the directory value

Message 1002

This is a primary SNA server yet the configuration file could not be found

Message 1003

SnaBase could not open a sponsor connection to server value

Message 1004

SnaBase didn't find any SNA Servers in your domain value

Message 1005

Unable to locate SNA Server Transport DLL.

Message 1006

Unable to access configuration information

ACTION: The SnaBase service was either unable to open the configuration file or unable to initialize SNACFG.DLL. The error code from SNACFG.DLL is value.

An error code of 0 means that the SnaBase service was unable to initialize SNACFG.DLL.

Message 1007

The SnaBase service could not Convert an ACL.  Registry or File Security may not match what is specified in the SnaAdmin program.  There error occurred at Code Check Point value due to NT Error Number value.  The text of the NT Error is : value.

Message 1008

An unexpected exception occurred while converting an ACL.  The Exception Code is value.  The exception occurred near check point value.

Message 1009

The SnaBase service failed to build a security descriptor for registry and file use.  The error occurred at Code Check Point value due to NT Error Number value.  The text of the NT Error is : value.

Message 1010

An unexpected exception occurred while building a security descriptor.  The Exception Code is value.  The exception occurred near check point value.

Message 1011

The Security Descriptor for the config file has not been updated as SnaBase was not able to generate an appropriate Security Descriptor. (See previous Logs)

Message 1012

The Security Descriptor for the registry has not been updated as SnaBase was not able to generate a legal Security Descriptor. (See previous Logs)

Message 1013

The SnaBase service was not able to apply an updated Security Descriptor to the config file due to NT Error value.  The text of the NT Error is value.

Message 1014

The SnaBase service was not able to apply an updated Security Descriptor to the registry due to NT Error value. The text of the NT Error is : value.

Message 1015

The SnaBase service was not able to get privileges required to maintain security.  This may be because the account has not had the SE_SECURITY or SE_TAKE_OWNERSHIP privleges assigned to it.  The NT error which occurred is value. The text of the error is value.

Message 1016

The SnaBase service was not able to open the registry key which contains domain security information.  The NT Error which occurred is value.  The text of the error is value.

Message 1017

Trying to validate the domain security descriptor, the SnaBase service determined that it is corrupted.  The NT Error which occurred is value.  The text of the error is value.

Message 1018

An error occurred attempting to impersonate a client.  The client request was failed.  The NT Error which occurred is value.  The text of the error is value.

Message 1019

An error occurred trying to lookup a Privilege Value.  The NT error which occurred is value. The text of the error is : value.  The privilege being looked up was : value.

Message 1950

RUI session abend for LU value

Message 1951

RUI buffer shortage, code = value

Message 1952

RUI_INIT complete for LU value

Message 1953

RUI link failure for LU value

Message 1954

RUI internal logic error for LU value, code value

Message 1955

RUI_INIT failed for LU value, primary_rc = value, secondary_rc = value

Message 1956

RUI_TERM complete for LU value

Message 1957

RUI application has ended: cleaning up session for LU value

Message 1958

RUI failed to extend session control block array, rc = value

Message 1959

RUI given bad event handle or callback address value

Message 3000

CPI-C semaphore operation error, system call return code: value

Message 3001

CPI-C failed to get configuration file path, (value)

Message 3002

Open of CPI-C configuration file failed, system call return code: value

Message 3003

CPI-C failed to get semaphore, system call return code: value

Message 3004

CPI-C failed to lock memory

Message 3005

CPI-C failed to allocate memory, system call return code: value

Message 3006

CPI-C failed to create call library semaphore, system call return code: value

Message 3007

New TP Instance started for CPI-C

Message 3008

CPI-C failed to get call library semaphore, system call return code: value

Message 3009

No CPI-C Conversation Characteristic Control Blocks available

Message 3010

Error while reading CPI-C configuration file, system call return code: value

Message 3012

CPI-C failed to access shared directory memory, system call return code: value

Message 3013

New CPI-C conversation accepted

Message 3014

New CPI-C conversation started

Message 3015

CPI-C conversation deallocated

Message 3016

CPI-C conversation in unknown state, value

Message 3017

CPI-C conversation_ID unknown, value value value value

Message 3018

Unknown CPI-C symbolic destination name specified, value

Message 3019

Invalid length of CPI-C data specified, value

Message 3020

Invalid CPI-C side information length specified, value

Message 3021

CPI-C attempt to Accept_Conversation after a conversation has been active

Message 3022

Attempt to exceed maximum number of concurrent CPI-C conversations: value

Message 3023

CPI-C failed to get memory pointer from handle

Message 3024

CPI-C failed to allocate memory

Message 3025

No CPI-C global control blocks available

Message 3026

CPI-C extract state call failed, APPC return code is value

Message 3027

CPI-C failed to get application name

Message 3028

Error returned from APPC that does not map to CPI-C error, value

Message 3029

No free CPI-C Side Information Directory entries

Message 3030

Invalid conversation_id parameter passed to CPI-C Accept_Conversation

Message 3031

Error from close of configuration file, return code is value

Message 3032

A Windows CPI-C application tried to start a conversation before issuing WinCPICStartup

Message 3050

Received value verb

Message 3051

Returning value verb, primary_rc value, secondary_rc value

Message 3052

No SNA Server management control blocks available

Message 3053

CSI return code value too large: mapping to default

Message 3054

Illegal CNOS FSM state

Message 3055

value received lost locality

Message 3056

Received CSI message for value control block value, which is not in use

Message 3057

CNOS received open (cs) error response, local LU alias value

Message 3059

Config semaphore error, rc = value

Message 3060

Error getting shared memory for DISPLAY, rc = value

Message 3061

Configuration file error, rc = value

Message 3062

Couldn't find a node record for the supplied connection, value

Message 3063

The local SNA server has reached the configured limit for retrying connection value. It will no longer try to activate it.

Message 3064

Internal Error - an LUA session has returned an invalid status to RUI.

status_code=value

status_qual=value


Sample Host Definitions
Appendix A	1 of 8

Sample Host Definitions

This appendix presents sample host definitions for SNA Server connections to IBM [image] S/370 (host) systems. The samples show configuration values for SNA Server connections of the following kinds:

Connection type		Connection use		Host system
Token ring		3270 emulation		Virtual Telecommunications Access Method (VTAM)
SDLC switched		3270 emulation		VTAM
SDLC leased		3270 emulation		VTAM
X.25		3270 emulation		VTAM
Any type		LU 6.2		Customer Information Control System (CICS)
Note

The VTAM listings in this appendix omit the column 72 continuation character.


VTAM Sample Definitions for 3270
Sample Host Definitions	2 of 8

VTAM Sample Definitions for 3270

This section presents sample VTAM definitions (version 3.2.2) for SNA Server connections to an IBM 9370 host system for 3270 emulation. There are samples for SDLC, for token ring, and for X.25 connections.


Token Ring Definition
Sample Host Definitions	3 of 8

VTAM Sample Definitions for 3270

Token Ring Definition

Table A.1 shows a VTAM definition for a connection between an SNA Server and an IBM 9370 host computer across a token ring local area network (LAN).

Table A.1    VTAM Token Ring Definitions

Name		Description		Parameters
LANODE		VBUILD		TYPE=LAN
R01100		PORT		CUADDR=100,MACADDR=400001701100, LANCON=(5,2),MAXDATA=2012, MAXSTN=32,SAPADDR=04
G01100		GROUP		DIAL=YES,ISTATUS=ACTIVE,LNCTL=SDLC
L01100A		LINE		CALL=INOUT
P01100A		PU		MAXLU=254
L01100B		LINE		CALL=INOUT
P01100B		PU		MAXLU=254
SWLAN		VBUILD		TYPE= SWNET,MAXGRP=5,MAXNO=12
SERVER01		PU		ADDR=C1,IDBLK=05D,IDNUM=00001, ANS=CONTINUE,MAXDATA=265, MAXOUT=7,MAXPATH=7,PACING=0, VPACING=0,SSCPFM=USSSCS, LANACK=(0,0),LANCON=(5,2), LANINACT=4.8,LANRESP=(5,2), LANSDWDW=(7,1),LANSW=YES, MACADDR=4000000000FD,PUTYPE=2, DISCNT=(NO),ISTATUS=ACTIVE, SAPADDR=04
E01100A		PATH		DIALNO=0004400001701100, GRPNM=G01100,GID=1,PID=1,USE=YES
T0110000		LU		LOCADDR=002,DLOGMOD=D4C32782
T0110001		LU		LOCADDR=003,DLOGMOD=D4C32782
T0110002		LU		LOCADDR=004,DLOGMOD=D4C32782
T0110003		LU		LOCADDR=005,DLOGMOD=D4C32782
T0110004		LU		LOCADDR=006,DLOGMOD=LU33286S
Table A.2 defines key parameters shown in Table A.1.

Table A.2    VTAM Parameter Descriptions for Token Ring

VTAM parameter		Corresponding SNA Server parameter		Description
IDBLK=		First three digits of Local Node ID (basic connection setting)		A three-digit hexadecimal value that, together with IDNUM, identifies the SNA Server. The values 000 and FFF cannot be used; these values are reserved.
IDNUM=		Last five digits of  Local Node ID (basic connection setting)		A five-digit hexadecimal value that, together with IDBLK, identifies the SNA Server.
MAXDATA= (in the PU definition for SERVER01)		Max BTU Length (advanced 802.2 setting)		The maximum length of a basic transmission unit (BTU) sent or received; BTUs are also known as Iframes. Max BTU Length should be less than or equal to MAXDATA.
MACADDR=  in the PORT definition		Remote Network Address (basic 802.2 setting)		The media access control address, a 12-digit hexadecimal address. The Remote Network Address (MACADDR) shown in Table A.1 is 400001701100.
SAPADDR= in the PU definition		Remote SAP Address (advanced 802.2 setting)		The system access point address, a two-digit hexadecimal number, a multiple of 4, between 04 and EC. The Remote SAP Address shown in Table A.1 is 04, the default value. This value is recommended for most installations.
LOCADDR= in the LU definition		LU Number		The LU local address at the PU. For independent LUs that communicate with a host, the LOCADDR parameter must be set to 0. For dependent LUs with VTAM, the LOCADDR must be at least 2. Also, for dependent LUs, the LU Numbers set in SNA Server must match the LOCADDR values on the host. The LU Numbers range from 002 to 006 in Table A.1.
The GRPNM value shown in the sample in Table A.1 is a group name; group names must match the label of a VTAM group definition. The DLOGMOD values shown in the sample are the logon mode table entries from the mode table. For descriptions of the group macros used in these samples, and a complete listing of default mode table entries, see the documentation for your IBM product.


SDLC Definition (for Switched and Leased Lines)
Sample Host Definitions	4 of 8

VTAM Sample Definitions for 3270

SDLC Definition (for Switched and Leased Lines)

Table A.3 shows a sample IBM 9370 VTAM definition for four SDLC lines. The LLGROUP label shows the VTAM definitions for lines B80 and BB0 of a leased group. The SNAGROUP label shows the VTAM definitions for lines B90 and BA0 of a switched group.

Table A.3    VTAM Definition for Four SDLC Lines

Label		Operation		Operands
IBMLINE		VBUILD		TYPE=CA
LLGROUP		GROUP		LNCTL=SDLC,DIAL=NO,ACTIVTO=10
L01B80		LINE		ADDRESS=B80,PAUSE=0.4,REPLYTO=2.0, RETRIES=7
P01B80A		PU		ADDR=C1,DISCNT=NO,PASSLIM=7, PUTYPE=2,MAXOUT=7,USSTAB=AUSSTAB
T01B8002		LU		LOCADDR=002,DLOGMOD=D4C32792
T01B8003		LU		LOCADDR=003,DLOGMOD=D4C32792
T01B8004		LU		LOCADDR=004,DLOGMOD=D4C32792
L01BB0		LINE		ADDRESS=BB0,PAUSE=0.4,REPLYTO=2.0, RETRIES=7
P01BB0A		PU		ADDR=C1,DISCNT=NO,PASSLIM=7, PUTYPE=2,MAXOUT=7,USSTAB=AUSSTAB
T01BB000		LU		LOCADDR=002,DLOGMOD=D4C32792
T01BB001		LU		LOCADDR=003,DLOGMOD=D4C32792
T01BB002		LU		LOCADDR=004,DLOGMOD=D4C32792
T01BB003		LU		LOCADDR=005,DLOGMOD=D3C32792
T01BB004		LU		LOCADDR=006,DLOGMOD=LU33286S
SNAGROUP		GROUP		LNCTL=SDLC,DIAL=YES,MAXLU=20
L01B90		LINE		ADDRESS=B90,PAUSE=0.4,REPLYTO=2.0, RETRIES=7
P01B90A		PU
L01BA0		LINE		ADDRESS=BA0,PAUSE=0.4,REPLYTO=2.0, RETRIES=7
P01BA0A		PU
Table A.4 shows the sample IBM 9370 VTAM switched definition for the SNAGROUP label in Table A.3.

Table A.4    VTAM Switched Definition for SNAGROUP

Label		Operation		Operands
SWNODE		VBUILD		TYPE=SWNET,MAXGRP=0,MAXNO=0
SWPU1		PU		ADDR=C1,IDBLK=017,IDNUM=DC006, DISCNT=NO,PASSLIM=2,PUTYPE=2, MAXDATA=265,MAXOUT=2, USSTAB=MSUSSTAB
T01BA000		LU		LOCADDR=2,DLOGMOD=D4C32782
T01BA001		LU		LOCADDR=3,DLOGMOD=D4C32782
T01BA002		LU		LOCADDR=4,DLOGMOD=D4C32782
T01BA003		LU		LOCADDR=5,DLOGMOD=D4C32782
T01BA004		LU		LOCADDR=6,DLOGMOD=LU33286S
Table A.5 describes key parameters shown in Tables A.3 and A.4.

Table A.5    VTAM Parameter Descriptions for SDLC

VTAM parameter		Corresponding SNA Server parameter		Description
ADDR=		Poll Address (advanced SDLC setting)		A two-digit hexadecimal value that identifies the control unit that the host uses to poll.
IDBLK=		First three digits of Local Node ID (basic connection setting)		A three-digit hexadecimal value that, together with IDNUM, identifies the SNA Server. The values 000 and FFF cannot be used; these values are reserved.
IDNUM=		Last five digits of  Local Node ID (basic connection setting)		A five-digit hexadecimal value that, together with IDBLK, identifies the SNA Server.
MAXDATA= (in the PU definition for SWPU1)		Max BTU Length (advanced SDLC setting)		The maximum length of a basic transmission unit (BTU) sent or received; BTUs are also known as Iframes.
LOCADDR=		LU Number		The LU local address at the PU. For independent LUs that communicate with a host, the LOCADDR parameter must be set  to zero. For dependent LUs with VTAM, the LOCADDR must be at least 2. Also, for dependent LUs, the LU Numbers set in SNA Server must match the LOCADDR  values on the host.
The DLOGMOD values shown in the example are the logon mode table entries from the mode table. For a complete listing of default mode table entries, see the documentation for your IBM product.


X.25 Definition
Sample Host Definitions	5 of 8

VTAM Sample Definitions for 3270

X.25 Definition

Table A.6 shows a sample IBM 9370 VTAM definition for X.25 circuits. The X25GROUP label shows the VTAM definitions for switched virtual circuits 001 through 006.

Table A.6    VTAM Definition for X.25 Connection

Label		Operation		Operands
X25NODE		VBUILD		TYPE=PACKET
PORTA00		PORT		CUADDR=(A00,A08),NETTYPE=1, CHARGACC=YES,CHARGE=NO, VCALLS=(,,001,006,,),DIALNO=31370023061 MAXOUT=7,NETLEVEL=80,PMOD=8, PLENGTH=256,PWINDOW=3,REPLYT0=3, RETRIES=7
VCPA00		VCPARMS		LC=(1,6),PWINDOW=3,PLENGTH=256
X25GROUP		GROUP		DIAL=YES,LNCTL=SDLC,CALL=INOUT, ISTATUS=ACTIVE
L01A00A		LINE		ADDRESS=001,AUTO=001, ISTATUS=ACTIVE
P01AOOA		PU		MAXLU=32
L01A00B		LINE		ADDRESS=002,ISTATUS=INACTIVE, AUTO=002
P01AOOB		PU		MAXLU=32
L01A00C		LINE		ADDRESS=003,ISTATUS=INACTIVE, AUTO=003
P01AOOC		PU		MAXLU=32
L01A00D		LINE		ADDRESS=004,ISTATUS=INACTIVE, AUTO=004
P01AOOD		PU		MAXLU=32
L01A00E		LINE		ADDRESS=005,ISTATUS=INACTIVE, AUTO=005
P01AOOE		PU		MAXLU=32
L01A00F		LINE		ADDRESS=006,ISTATUS=INACTIVE, AUTO=006
P01AOOF		PU		MAXLU=32
Table A.7 shows the sample IBM 9370 VTAM switched definition for the X25GROUP label in Table A.6.

Table A.7    VTAM Switched Definition for X25GROUP

Label		Operation		Operands
X25		VBUILD		TYPE=SWNET,MAXGRP=5,MAXNO=12
USER01		PU		ADDR=C1,IDBLK=05D,IDNUM=00025, ANS=CONTINUE,MAXDATA=265, MAXOUT=7,MAXPATH=0,PACING=0, VPACING=0,SSCPFM=USSSCS, IRETRY=YES,USSTAB=MSUSSTAB, PUTYPE=2,DISCNT=YES,ISTATUS=ACTIVE
T01A0002		LU		LOCADDR=002,DLOGMOD=D4C32792
T01A0003		LU		LOCADDR=003,DLOGMOD=D4C32792
T01A0004		LU		LOCADDR=004,DLOGMOD=D4C32792
T01A0005		LU		LOCADDR=005,DLOGMOD=D4C32792
T01A0006		LU		LOCADDR=006,DLOGMOD=LU33286S
Table A.8 defines key parameters shown in Tables A.6 and A.7.

Table A.8    VTAM Parameter Descriptions for X.25

VTAM parameter		Corresponding SNA Server parameter		Description
IDBLK=		First three digits of Local Node ID (basic connection setting)		A three-digit hexadecimal value that, together with IDNUM, identifies the SNA Server. The values 000 and FFF cannot be used; these values are reserved.
IDNUM=		Last five digits of  Local Node ID (basic connection setting)		A five-digit hexadecimal value that, together with IDBLK, identifies the SNA Server.
DIALNO= in the PORT definition		Remote X.25Address		An address that identifies an X.25 system. The address consists of from 1 through 15 hexadecimal digits. If a 15-digit address is used, the final 3 digits are used for routing between stations with the same 12-digit address.
MAXDATA= (in the PU definition for USER01)		Max BTU Length (advanced X.25 setting)		The maximum length of a BTU sent or received.
LOCADDR=		LU Number		The LU local address at the PU.  For independent LUs that communicate  with a host, the LOCADDR parameter must be set to 0.For dependent LUs with VTAM, the LOCADDR must be at least 2. Also, for dependent LUs, the LU Numbers set in SNA Server must match the LOCADDR values on the host. The LU numbers range from 002 to 006 in  Table A.7.


CICS and VTAM Sample Definitions for LU 6.2
Sample Host Definitions	6 of 8

CICS and VTAM Sample Definitions for LU 6.2

This section presents sample definitions for CICS (version 1.6) and VTAM (version 3.2) for SNA Server connections to an IBM host system for LU 6.2 operation.

To configure a CICS host system for LU 6.2 operation with an SNA Server system, you configure the following information at the host:

The remote systems with which CICS is able to communicate.

The name used by VTAM to communicate with each remote system.

The transaction programs (TPs) available on the CICS system.

The programming language (PL/I, COBOL, or Assembler) in which each program is written.

This information is configured in CICS and VTAM tables. This section provides sample definitions that show how to configure CICS for LU 6.2 using these CICS and VTAM tables.


CICS Tables
Sample Host Definitions	7 of 8

CICS and VTAM Sample Definitions for LU 6.2

CICS Tables

CICS uses the following tables to define LU 6.2 information:

Terminal Control Table (TCT) — defines the remote systems to CICS.

Program Control Table (PCT) — defines the local TPs to CICS.

Program Processing Table (PPT) — defines the load module characteristics to CICS.

The following paragraphs describe these tables, and include sample definitions to illustrate how they are used.

Note

These samples assume there are four TPs residing on CICS written in PL/I with the following names: TRAN0, TRAN1, TRAN2, and TRAN3.

Terminal Control Table

The Terminal Control Table (TCT), Table A.9, defines the remote systems to CICS. Each remote system is specified using a DFHTCT definition, which includes both the name by which CICS knows the system (the SYSIDNT field), and the name by which VTAM knows the system (the NETNAME field).

Table A.9    Sample CICS Terminal Control Table Entries

Label		Definition		Operands
TP11		DFHTCT		TYPE=SYSTEM ACCMETH=VTAM, FEATURE=SINGLE,TRMTYPE=LUTYPE62, NETNAME=TPLU6207,SYSIDNT=DC11, MODENAM=LU62,CONNECT=AUTO, BUFFER=256,RUSIZE=256, TRMSTAT=(TRANSCEIVE)
TP12		DFHTCT		TYPE=SYSTEM ACCMETH=VTAM, FEATURE=SINGLE,TRMTYPE=LUTYPE62, NETNAME=TPLU6208,SYSIDNT=DC12, MODENAM=LU62,CONNECT=AUTO, BUFFER=256,RUSIZE=256, TRMSTAT=(TRANSCEIVE)
TP13		DFHTCT		TYPE=SYSTEM ACCMETH=VTAM, FEATURE=SINGLE,TRMTYPE=LUTYPE62, NETNAME=TPLU6209,SYSIDNT=DC13, MODENAM=LU62,CONNECT=AUTO, BUFFER=256,RUSIZE=256, TRMSTAT=(TRANSCEIVE)
TP14		DFHTCT		TYPE=SYSTEM ACCMETH=VTAM, FEATURE=SINGLE,TRMTYPE=LUTYPE62, NETNAME=TPLU620A,SYSIDNT=DC14, MODENAM=LU62,CONNECT=AUTO, BUFFER=256,RUSIZE=256, TRMSTAT=(TRANSCEIVE)
Program Control Table

The Program Control Table (PCT), Table A.10, defines the local TPs to CICS. Each TP is specified using a DFHPCT definition, which includes the name by which the TP is invoked (the TRANSID field), and the corresponding load module name from the CICS library of TPs.

Table A.10    Sample CICS Program Control Table Entries

TP Label		Definition		Operands
TRAN0		DFHPCT		TYPE=ENTRY PROGRAM=TRAN0000, TWASIZE=1000,SPURGE=NO, TPURGE=NO,RSL=00,RSLC=NO, MODENAM=NORMAL,TRANSID=TRAN0
TRAN1		DFHPCT		TYPE=ENTRY PROGRAM=TRAN0001, TWASIZE=1000,SPURGE=NO, TPURGE=NO,RSL=00,RSLC=NO, MODENAM=NORMAL,TRANSID=TRAN1
TRAN2		DFHPCT		TYPE=ENTRY PROGRAM=TRAN0002,TWASIZE=1000, SPURGE=NO,TPURGE=NO,RSL=00, RSLC=NO,MODENAM=NORMAL, TRANSID=TRAN2
TRAN3		DFHPCT		TYPE=ENTRY PROGRAM=TRAN0003,TWASIZE=1000, SPURGE=NO,TPURGE=NO,RSL=00, RSLC=NO,MODENAM=NORMAL, TRANSID=TRAN3
* ****** * PROFILE TO BE USED IN LU6.2 ALLOCATE * ****** *
		DFHPCT		TYPE=PROFILE, PROFILE=DFHCICSA, INBFMH=ALL,MODENAME=LU62
Program Processing Table

The Program Processing Table (PPT), Table A.11, defines the load module characteristics to CICS.

Each load module is defined using the DFHPPT definition, which includes the name of the load module (the PROGRAM field), and the language in which the module has been written, for example, PL/I, Assembler, or COBOL (the PGMLANG field).

Table A.11    Sample CICS Program Processing Table Entries

Definition		Program name		Language
DFHPPT TYPE=ENTRY		PROGRAM=TRAN0000		PGMLANG=PL/I
DFHPPT TYPE=ENTRY		PROGRAM=TRAN0001		PGMLANG=PL/I
DFHPPT TYPE=ENTRY		PROGRAM=TRAN0002		PGMLANG=PL/I
DFHPPT TYPE=ENTRY		PROGRAM=TRAN0003		PGMLANG=PL/I


VTAM Definitions
Sample Host Definitions	8 of 8

CICS and VTAM Sample Definitions for LU 6.2

VTAM Definitions

Each remote system must be defined to VTAM in its table of Network Addressable Units, called NAUs, using LU definitions (see Table A.12).

Note that if a LOGAPPL parameter is specified on the LU definition naming the CICS system, CICS will attempt to establish a session to that LU whenever it becomes active. This is necessary if TPs residing in CICS do not use the ALLOCATE verb with RETURN_CONTROL=WHEN_SESSION_ALLOCATED to establish sessions. There must also be a VTAM mode table definition present for LU 6.2, although CICS does not use the values specified here.

Table A.12    Sample VTAM Network Control Program (NCP) Definition for LU 6.2

Label		Operation		Operands
TPPU62		PU		ADDR=C1,IBLK=03E,IDNUM=01A1A, IRETRY=YES,DISCNT=NO,ISTATUS=ACTIVE, MAXDATA=265,SSCPFM=USSSCS, MODETAB=MRNDS,USSTAB=USSNDN1, MAXOUT=7,PASSLIM=7,PUTYPE=2
TPLU6207		LU		LOCADDR=7,DLOGMOD=LU62, USSTAB=USSNOMSG
TPLU6208		LU		LOCADDR=8,DLOGMOD=LU62, USSTAB=USSNOMSG
TPLU6209		LU		LOCADDR=9,DLOGMOD=LU62, USSTAB=USSNOMSG
TPLU620A		LU		LOCADDR=A,DLOGMOD=LU62, USSTAB=USSNOMSG
Table A.13 shows NCP mode table entries for LU 6.2.

Table A.13    Sample NCP Mode Table Entries for LU 6.2

Label		Operation		Operands
		MODETAB
LU62		MODEENT		LOGMODE=NORMAL
		. . .
		MODEEND
Note

It is recommended that the mode used by LU 6.2 LUs be listed first, as shown by the listing of LU62 in the preceding table.

TP Coding Requirements

To work with CICS, TPs must be coded to specify a SYSID parameter on the ALLOCATE request that matches the defined SYSIDNT parameter configured in the DFHTCT tables. This request must be in the following format:

EXEC CICS ALLOCATE SYSID('DC11')

The SYSID field must match the SYSIDNT field specified for a CICS program by the DFHTCT definition in the TCT. The TCT then uses the NETNAME parameter to refer to a specific LU in the VTAM table of NAUs for use by the TP to communicate with the remote system.


Program Check Codes and Sense Codes
Appendix B	1 of 3

Program Check Codes and Sense Codes

This appendix lists the program check codes and the sense codes used by SNA Server.


Program Check Codes
Program Check Codes and Sense Codes	2 of 3

Program Check Codes

Program check codes indicate protocol or data stream errors. They appear in the operator guidance message area as PROGnnn messages where nnnwis defined as shown in Table B.1.

Table B.1    Program Check Codes

Value	Meaning

401	Invalid command received.Invalid alias for SFE, MF, or SA.

402	Out-of-range address for SEA, RA, or EUA order.MF order addressed nonfield attribute location.

403	Data stream data after Rd, Rd Mod, EAU command.Invalid parameter following SFE, MF, SA, GE, or RA order.

404	Data stream terminated before end of order.

413	Function not supported.

420	Exception response chain received when BIND specified definite response.

421	Definite response chain received after BIND specified exception response.

422	New response chains not allowed.

423	FI bit not allowed for FM data.

430	Sequence number error.

431	Chaining error.

432	Bracket error.

433	Data traffic reset.

434	Direction error.

442	Request not executable.

443	CD required.

445	ACTLU type not COLD or ERP.

450	Profile error.

451	Primary protocol error.

452	Secondary protocol error.

453	Common protocol error.

454	Screen size error.

455	LU profile error.

456	Negotiable BIND rejected (sense code 0821 sent).

470	Unsupported code point received.

471	Extended data stream function not supported.

472	Read state error.

474	The device does not support extended data stream.

475	WCC had "Start Print" but not last structured field.

498	Negative response received.

499	Internal error report.


Sense Codes
Program Check Codes and Sense Codes	3 of 3

Sense Codes

SNA sense codes are sent on either a negative response to an outbound data stream or an LUSTAT that notifies the host of a change in the secondary LU state.  The sense codes generated by a 3270 emulator program are shown in Tables B.2 and B.3.

Table B.2    Negative Response Sense Codes

Value	Meaning

0802	Intervention required (LU1/LU3 printer soft error).

0814	Bracket bid reject — RTR forthcoming.

081B	Receiver in transmit mode.

081C	Request not executable (hard error).

0821	Invalid session parameters (negotiable BIND request).

0829	Change direction required.

082B	Presentation space integrity lost.

082D	LU busy (usually local copy print in progress).

082E	Intervention required (local copy print soft error).

082F	Request not executable (local copy print hard error).

0843	WCC print command bit not sent (RQD or RQE, CD, EB).

0863	Referenced character set does not exist.

0871	Read partition state error (SLU in retry state).

1003	Function not supported.

1005	Parameter modifying a control function is invalid.

1007	Category not supported (SSCP data for host printer).

Table B.3    LUSTAT Sense Codes

Value	Meaning

0001 B000	Host initialized local copy soft error recovery.

081C 0000	Soft error changed to hard error (LU1/LU3).

081C B000	Soft error changed to hard error (local copy).

082B 0000	LU session changed from SSCP to PLU (SYSREQ).


Registry and Environment Variables for SNA Server
Appendix C	1 of 24

Registry and Environment Variables for SNA Server

This appendix describes the Registry variables and environment variables that can be set for SNA Server.

In most situations, it is recommended that you leave Registry and environment variables set at the default settings. Specifying different values for variables allows you to:

Communicate with a host that implements unusual variants of SNA protocols. Changing the Registry and/or environment variables allows for workarounds with such hosts.

Use special default values for such settings as timers.

Set a variable for an application, when the application could not use a standard API call to set that variable.

Important

Change Registry and environment variables only if your specific situation makes it appropriate. Changing Registry and environment variables inappropriately can disable SNA Server functionality. For most situations, these variables can be left at default settings.

There is a set of variables not documented in this appendix: the variables used for configuring an invokable TP. For information about these variables, see Chapter 2 of the Microsoft SNA Server APPC Programmer's Guide, or Chapter 2 of the Microsoft SNA Server CPI-C Programmer's Guide.


Setting Variables on Different Operating Systems
Registry and Environment Variables for SNA Server	2 of 24

Setting Variables on Different Operating Systems

The following table shows how Registry and environment variables are set on an SNA server and on the various types of SNA Server clients. For information about the Windows NT Registry, see the Windows NT documentation. For information about environment variables for the Windows [image] version 3.x, MS-DOS [image], or OS/2 [image] operating systems, see the appropriate operating system documentation.

Operating system and SNA Server software		Method for setting Registry variables or environment variables
Windows NT with SNA server  or SNA Server client		Change values in the Windows NT Registry by using the Registry editor, REGEDT32.
Windows version 3.x  with SNA Server client		Add or change lines in the WIN.INI file.
MS-DOS  with SNA Server client		Add or change lines in the SNA.INI file.
OS/2  with SNA Server client		Use set commands, either at the command prompt or in CONFIG.SYS.


Lists of Available Variables
Registry and Environment Variables for SNA Server	3 of 24

Lists of Available Variables

Table C.1 outlines the Registry variables that can be set on an SNA server. For detailed information about each variable, see the sections that follow.

Table C.1    Registry Variables for an SNA Server

Variable		What is affected
ALLOCINACT:REG_SZ:{ YES | NO }		Allocation of inactive LUs from a pool
ALLOWBBRQE:REG_SZ:{ YES | NO }		Use of begin bracket, exception response
CLEANUP:REG_SZ:{ YES | NO }		Deactivation method for sessions
COMBUF:REG_DWORD:number		Size of buffer pool available
NO4004:REG_SZ:{ YES | NO }		Handling of sense code 4004
NOINITCNOS:REG_SZ:{ YES | NO }		Time at which CNOS negotiation is performed
BINDRETRY:REG_DWORD:number		Retry time-out for BIND attempts for autoactivated sessions
NORETRY:REG_SZ:{ YES | NO }		Retry of BIND
NOTERMSELF:REG_SZ:{ YES | NO }		Termination of 3270 sessions
RENEGLIMITS:REG_SZ:{ YES | NO }		Automatic CNOS renegotiation when a BIND fails
RETRYCNOS:REG_SZ:{ YES | NO }		Automatic CNOS renegotiation when partner resets session limits
SESTIMEOUT:REG_SZ:number		Time at which unused contention winner sessions are deactivated
NONOTIFYRSP:REG_SZ:{ YES | NO }		How SNA Server responds to the lack of a Notify response.
SyncConfigFiles:REG_SZ:{ ON | OFF }		SnaBase: copying of configuration file from primary to backup SNA servers
ACCPTFMT:REG_SZ:{ 0 | 1}		X.25: use of addresses on CALL_ACCEPT
LUWIDSUP:REG_SZ:{ YES | NO }		APPC: support of logical unit of work identifier
application:REG_SZ:localLUalias		CPI-C: the local LU alias to be used by an application
APPCTPN:REG_SZ:TPname		CPI-C: the local TP name
COMTBLG:REG_SZ:filename		CSV: name of file containing Table G (for code conversion)
COMCPT:REG_DWORD:path		CSV: path of code page (for code conversion)
SNAMAXLUALUS:REG_DWORD:number		LUA: number of frames in the protocol window
LOCALLUS:REG_SZ:localLUname		Assigning of LUs on a per-workstation basis
COMPOP12:REG_SZ:{ YES | NO }		Suppression of level 12 pop-up warnings
Unique5250Names:REG_SZ:{ YES | NO }		Uniqueness of session IDs for 5250 emulators
FrameType:REG_DWORD:number		DIX or 802.3 framing in an Ethernet LAN; significant when communicating via a router
TraceWithTime:REG_SZ:{ ON | OFF }		Tracing with time instead of tracing by process ID
Milliseconds:REG_SZ:{ ON | OFF }		Time interval used with TraceWithTime
BufferAutditInterval:REG_DWORD:number		Auditing of buffer pool at regular intervals
DloadMatchTPOnly:REG_SZ:{ YES | NO }		Method for matching requested TP against available TPs
DloadMatchLocalFirst:REG_SZ:{ YES | NO }		Method for matching requested TP against available TPs
ConfigFilePath:REG_SZ:pathname		Path used when the SNA server accesses the local configuration file
Table C.2 outlines the Registry variables that can be set on an SNA Server client running the Windows NT system. For detailed information about each variable, see the sections that follow.

Table C.2    Registry Variables for an SNA Server Client Running Windows NT

Variable		What is affected
LUWIDSUP:REG_SZ:{ YES | NO }		APPC: support of logical unit of work identifier
application:REG_SZ:localLUalias		CPI-C: the local LU alias to be used by an application
APPCTPN:REG_SZ:TPname		CPI-C: the local TP name
COMTBLG:REG_SZ:filename		CSV: name of file containing Table G (for code conversion)
COMCPT:REG_DWORD:path		CSV: path of code page (for code conversion)
SNAMAXLUALUS:REG_DWORD:number		LUA: number of frames in protocol window
LOCALLUS:REG_SZ:localLUname		Assigning of LUs on a per-workstation basis
COMPOP12:REG_SZ:{ YES | NO }		Suppression of level 12 pop-up warnings
TraceWithTime:REG_SZ:{ ON | OFF }		Tracing with time instead of tracing by process ID
Milliseconds:REG_SZ:{ ON | OFF }		Time interval used with TraceWithTime
BufferAutdit Interval:REG_DWORD:number		Auditing of buffer pool at regular intervals
OtherServers:REG_MULTI_SZ:server1 [server2][ ...]		Access to LUs through SNA servers outside a  client's domain
Note

Tables C.2 and C.3 do not include the variables used for configuring an invokable TP. For information about these variables, see Chapter 2 of the Microsoft SNA Server APPC Programmer's Guide or Chapter 2 of the Microsoft SNA Server CPI-C programmer's Guide.

Table C.3 outlines the environment variables that can be set on an SNA Server client running the Windows version 3.x, MS-DOS, or OS/2 operating systems. For detailed information about each variable, see the sections that follow.

Table C.3    Environment Variables: Windows version 3.x, MS-DOS, or OS/2

Variable		What is affected
LUWIDSUP={ YES | NO }		APPC: support of logical unit of work identifier
[ApplicationName]APPCLLU=localLUalias		CPI-C: the local LU alias to be used by an application
APPCTPN=TPname		CPI-C: the local TP name
COMTBLG=filename		CSV: name of file containing Table G (for code conversion)
COMCPT=path		CSV: path of code page (for code conversion)
SNAMAXLUALUS=number		LUA: number of frames in protocol window
For MS-DOS and Windows version 3.x: LOCALLUS=localLUnameFor OS/2: COMLUASS={ YES | NO }		Assigning of LUs on a per-workstation basis
COMPOP12={ YES | NO }		Suppression of level 12 pop-up warnings
For MS-DOS and Windows version 3.x: OtherServers=server1 [server2][ ...]		Access to LUs through SNA servers outside a client's domain
For MS-DOS: OverrideDefaultLU={ YES | NO }		Default LUs as specified for PC Support instead of SNA Server
For MS-DOS: [SnaBase]LogonUserName=username		User name to use for logging on to SNA servers; useful only for clients not running  Microsoft networking
Note

Note that for clients running Windows version 3.x or MS-DOS but not running Microsoft networking, command line options can also be used to specify the user name and password when starting the SnaBase on the client. For more information, see "Variables for Clients Not Running Microsoft Networking," later in this appendix.

Table C.4 lists the environment variable that can be set on a Windows-based client running the 3270 Applet.

Table C.4    Environment Variable for a Windows-Based Client Running the 3270 Applet

Section and variable for WIN.INI file		What is affected
[SnaServerWin3270]RetryConns={ yes | no }		Retrying when activation of a connection does not initially succeed and the cause of the problem may be temporary


Registry Variables Used Only on an SNA Server
Registry and Environment Variables for SNA Server	4 of 24

Registry Variables Used Only on an SNA Server

The Registry variables in the following sections can be set on an SNA server only. To access or modify these variables, use the Registry Editor, REGEDT32. For information about the Registry Editor, see your Windows NT documentation.


SnaServer Service: Location and Names of Variables
Registry and Environment Variables for SNA Server	5 of 24

Registry Variables Used Only on an SNA Server

SnaServer Service: Location and Names of Variables

The Registry variables in this section affect the SnaServer service. They are all located in the same place in the Registry:

HKEY_LOCAL_MACHINE
   SYSTEM
      CurrentControlSet
         Services
            SnaServr
               Parameters

The variables that affect the SnaServer service are as follows:

ALLOCINACT:REG_SZ:{ YES | NO }       Default: NO

When this variable is set to YES, the node will allocate pooled LUs even if they are inactive LUs on a connection that was activated on server startup or by an administrator. Otherwise, among pooled LUs on such a connection, only active LUs are allocated.

Setting this variable to YES means that when a user cannot get host access, they can use the OIA status line (in a 3270 emulator) to distinguish between two possible causes: all LUs are in use, or the host connection is down.

Note that in Comm Server 1.x, there was a similar environment variable, ALLOCACT, which had the opposite sense. That is, ALLOCACT prevented the allocation of inactive LUs; if ALLOCACT was not set, inactive LUs on activated connections were always allocated.

ALLOWBBRQE:REG_SZ:{ YES | NO }       Default: NO

When this variable is set to YES, the node allows Begin Bracket, Exception Response (BB RQE) on any request, even requests that do not contain End Bracket (EB). Otherwise, requests containing BB RQE but not EB are rejected with sense code 2003, in accordance with SNA protocols.

Note that BB RQE is allowed if Change Direction (CD) is set.

CLEANUP:REG_SZ:{ YES | NO }       Default: NO

When this variable is set to YES, the local LU deactivates sessions by directly sending UNBIND (cleanup). Otherwise, when LU 6.2 sessions are deactivated, the two LUs exchange BIS requests before UNBIND is sent. Setting this variable to YES is a workaround for a host problem in which the LU was being marked inactive.

COMBUF:REG_DWORD:number

This variable sets the size of the buffer pool available to the SnaServer service, in 16K units. Change this variable only if you receive error messages indicating that there is a buffer shortage. With a large number of gateway LUs it may be necessary to set COMBUF to as large a value as 0x7F.

DloadMatchTPOnly:REG_SZ:{ YES | NO }       Default: NO

When this variable is set to YES, the comparison between a request for a transaction program (TP) and the list of available invokable TPs is carried out on the TP name only. Otherwise, the comparison is carried out using both the requested TP name and the requested partner LU alias. This variable affects the servers on which it is set, but does not affect other servers.

Invokable TPs can be configured, through a Registry or environment variable on the system where the TP is located, to use a specific LU alias. If the invokable TP is configured in this way, the setting of DloadMatchTPOnly will control whether the LU alias is used in comparisons against incoming requests. If the invokable TP is not configured to use a specific LU alias, then no matter what LU alias an incoming request is sent to, there cannot be a mismatch (regardless of the setting of DloadMatchTPOnly); with such TPs, matching is only affected by the TP name.

For information about TPs, see the Microsoft SNA Server APPC Programmer's Guide or the Microsoft SNA Server CPI-C Programmer's Guide.

The default is NO, meaning that the comparison uses both TP name and LU alias (when the LU alias has been configured for the invokable TP).

DloadMatchLocalFirst:REG_SZ:{ YES | NO }       Default: YES

When this variable is set to NO, the comparison between a request for a TP and the list of available invokable TPs is carried out without regard to the location of the TP. Otherwise, invokable TPs on the local SNA server are considered first for a potential match. This variable affects the server on which it is set, but not other servers in the domain.

For information about TPs, see the Microsoft SNA Server APPC Programmer's Guide or the Microsoft SNA Server CPI-C Programmer's Guide.

The default is YES, meaning that invokable TPs on the local SNA server are considered first for a potential match.

NO4004:REG_SZ:{ YES | NO }       Default: NO

When set to YES, causes the SNA server to ignore sense code 4004. In other words, causes CEB (conditional end bracket) to be accepted when EC (end chain) is not set, and EB (end bracket) to be accepted when BC (begin chain) is not set. Otherwise, there is a normal response to sense code 4004.

NOINITCNOS:REG_SZ:{ YES | NO }       Default: NO

When this variable is set to YES, SNA Server will perform CNOS negotiation for APPC LUs only when sessions are required. Otherwise, SNA Server performs these negotiations when the connection is started.

Note that with autoactivated sessions, regardless of the NOINITCNOS setting, CNOS negotiation must always be performed when the connection is started.

Setting this variable to YES speeds up the starting process for connections that have large numbers of LUs.

BINDRETRY:REG_DWORD:number       Default: 2

Sets the session retry time-out (in units of 5 seconds) for the SNA server to retry BIND attempts for autoactivated sessions. Setting BINDRETRY to 0 prevents retries.

NORETRY:REG_SZ:{ YES | NO }       Default: NO

When this variable is set to YES, the SNA server does not retry a BIND request when the response to the BIND is an UNBIND cleanup request. This prevents repetitive BIND failures when routing LU 6.2 sessions through a host.

NOTERMSELF:REG_SZ:{ YES | NO }       Default: NO

When this variable is set to YES, 3270 sessions are terminated directly by sending UNBIND (cleanup). Otherwise, a TERM-SELF is sent to solicit UNBIND from host. Setting this variable to YES is a workaround for host-based session monitors that mark the LU as inactive after the TERM-SELF sequence.

RENEGLIMITS:REG_SZ:{ YES | NO }       Default: NO

When this variable is set to YES, SNA Server always performs CNOS renegotiation when three criteria hold: no active sessions exist, SNA Server has a nonzero session limit, and an application BIND fails (regardless of sense code). Otherwise, SNA Server performs CNOS renegotiation according to the setting of RETRYCNOS.

Note that when RENEGLIMITS is set to YES, it overrides any setting of RETRYCNOS.

For a discussion of the renegotiation procedure that SNA Server uses by default (when variables such as RENEGLIMITS are not set), see the description for the next variable, RETRYCNOS.

RETRYCNOS:REG_SZ:{ YES | NO }       Default: YES

When this variable is set to NO, SNA Server will not automatically renegotiate LU 6.2 session limits when the partner, without giving notice, resets these limits. Otherwise, SNA Server renegotiates the session limits whenever they are reset. The following paragraphs provide an overview of the CNOS renegotiation process performed by SNA Server.

By default, SNA Server performs CNOS negotiation at the start of day (when the session limits are initially 0), in response to an application issuing a CNOS verb, or whenever session limits are reset. The resetting of session limits becomes apparent to SNA Server when no active sessions exist, SNA Server has a nonzero session limit, and an application BIND is rejected either by an UNBIND request or with a BIND negative response containing one of the following sense codes:

Sense 1	Sense 2

0x0806	0x3426  (Resource Unknown)

0x0805	xxxxxx  (Session Limit Exceeded)

0x0801	xxxxxx  (Resource Not Available)

SNA Server does not automatically reset session limits after a connection failure; when the connection is reactivated, renegotiation may not be necessary, and does not always occur.

If an application BIND fails after a previously successful CNOS negotiation, the most likely reason is that the partner LU has reset its session limits (perhaps because of a connection failure or being stopped and restarted) without SNA Server being informed by a request to renegotiate the session limits. In this situation, SNA Server will receive a BIND rejection of the type previously described, and by default will perform CNOS renegotiation. This CNOS renegotiation will resolve the problem of having a remote application that is active when no sessions are active on the connection.

If the CNOS renegotiation fails, no further attempts are made to activate the session, until the connection is restarted or the SNA Server application retries.

With Comm Server 1.x, renegotiation of session limits was activated not by default, but by setting this variable to YES. In contrast, with SNA Server, renegotiation is activated by default, and can only be deactivated by setting this variable to NO. For a description of a variable that overrides the effects of RETRYCNOS, see RENEGLIMITS.

Setting this variable to NO is a workaround for problems when communicating with CICS and the AS/400 [image].

SESTIMEOUT:REG_SZ:number

This variable sets the number of 5-second timer ticks allowed before the node deactivates contention winner sessions that are no longer in use. If the variable is not set, 4 timer ticks of 5 seconds each are allowed, for a total of 20 seconds.

Unique5250Names:REG_SZ:{ YES | NO }       Default: YES

When this variable is set to NO, SNA Server will not ensure that session IDs generated by 5250 emulators are unique. Otherwise, SNA Server will substitute a unique session ID if any 5250 emulator generates a duplicate ID.

When a 5250 user establishes a session with an AS/400, a unique device name is required. Unless an override is sent, the AS/400 will generate the name by taking the Local LU and appending a 2-byte session ID sent by the emulator. A session ID generated by an emulator is usually not unique, since the emulator does not have information about the session IDs used by other active emulators. Therefore, by default, SNA Server alters the session IDs as they are sent out to ensure uniqueness. This is the recommended behavior, but it can be disabled by setting this Registry variable to NO.

NONOTIFYRSP:REG_SZ:{ YES | NO }       Default: NO

When this variable is set to YES, SNA Server ignores the lack of response to a Notify request sent by the SNA Server node. If a Notify response is subsequently received, SNA Server processes it normally.

When this variable is set to NO, dependent LU sessions may become unusable due to the lack of a Notify response.


SnaBase Service: Location and Name of Variables
Registry and Environment Variables for SNA Server	6 of 24

Registry Variables Used Only on an SNA Server

SnaBase Service: Location and Name of Variables

The Registry variables that affect the SnaBase service on an SNA server are found in the following location in the Registry:

HKEY_LOCAL_MACHINE
   SYSTEM
      CurrentControlSet
         Services
            SnaBase
               Parameters

These are the variable names and descriptions:

SyncConfigFiles:REG_SZ:{ ON | OFF }       Default: ON

When this variable is set to OFF, replication of the configuration file from the primary SNA server to any backup SNA servers is disabled. Otherwise, the configuration file will automatically be replicated from the primary SNA server to any backup SNA servers whenever the configuration file is changed and saved. Setting this variable to OFF does not offer any performance gains, so it is generally best not to set the variable, that is, best to allow the default behavior (replicating the configuration file).

ConfigFilePath:REG_SZ:pathnameDefault: SnaRoot\SYSTEM\CONFIG\COM.CFG

Specifies the path for the location of the configuration file on the local server; therefore, it applies only to primary or backup SNA servers. This variable may need to be set to an explicit string (for example, a string such as C:\SNA\SYSTEM\CONFIG\COM.CFG) in unusual situations where software interaction prevents normal local access to the configuration file.


DLC (802.2) Link Service: Location and Name of Variable
Registry and Environment Variables for SNA Server	7 of 24

Registry Variables Used Only on an SNA Server

DLC (802.2) Link Service: Location and Name of Variable

The Registry variable that affects the DLC (802.2) link service is found in the following location in the Registry:

HKEY_LOCAL_MACHINE
   SYSTEM
       CurrentControlSet
         Services
            DLCLinkServiceName
               Parameters
                  ExtraParameters

This is the variable name and description:

FrameType:REG_DWORD:number

This variable specifies the type of frames for the DLC (802.2) link service to send over an Ethernet LAN. The variable need be set only if the LAN is Ethernet, not token ring, and only if the SNA server communicates with remote host, peer, or downstream systems via routers (not MAC layer bridges).

If the SNA server communicates over Ethernet via routers, check with the local network support staff to determine what type of frames the routers pass. The frames can be either standard 802.3 format or 802.2 packets prefixed by DIX headers using EtherType value 0x80D5.

Specify the number in FrameType as follows:

Value	Effect

0	Use the frame type specified for this adapter in the Registry entry for the DLC protocol stack: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DLC\Parameters\AdapterName\UseDixOverEthernet. The default for UseDixOverEthernet is 0, resulting in 802.3 format.

1	Use the frame type automatically determined by the DLC stackduring XID exchange.

2	Use standard 802.3 format.

3	Use 802.2 packets prefixed by DIX headers using EtherType value 0x80D5.

If FrameType is not set, it defaults to 0, which means that the frame type is the one specified in UseDixOverEthernet, as described in the preceding table.


X.25 Link Service: Location and Name of Variable
Registry and Environment Variables for SNA Server	8 of 24

Registry Variables Used Only on an SNA Server

X.25 Link Service: Location and Name of Variable

The Registry variable that affects the X.25 link service is found in the following location in the Registry:

HKEY_LOCAL_MACHINE
   SYSTEM
      CurrentControlSet
         Services
            X.25LinkServiceName
               Parameters
                  ExtraParameters

This is the variable name and description:

ACCPTFMT:REG_SZ:{ 0 | 1 }       Default: 0

When this variable is set to 1, calling and called addresses are omitted on a CALL_ACCEPT packet which is sent in response to an incoming call. Setting this variable to 1 is a workaround for a problem when the host rejects standard X.25 CALL_ACCEPT packets.


Registry Variables Used on an SNA Server or a Windows NT-Based Client
Registry and Environment Variables for SNA Server	9 of 24

Registry Variables Used on an SNA Server or a Windows NT-Based Client

The Registry variables in the following sections can be set on an SNA server or a Windows NT-based client, except for MaxThreads, which can be set only on a Windows NT-based client. To access or modify these variables, use the Registry Editor, REGEDT32. For information about the Registry Editor, see your Windows NT documentation.

Note

The following sections do not include the variables used for configuring an invokable TP. For information about these variables, see Chapter 2 of the Microsoft SNA Server APPC Programmer's Guide or Chapter 2 of the Microsoft SNA Server CPI-C Programmer's Guide.


TraceWithTime and Milliseconds
Registry and Environment Variables for SNA Server	10 of 24

Registry Variables Used on an SNA Server or a Windows NT-Based Client

TraceWithTime and Milliseconds

These variables can be set on an SNA server or a Windows NT-based client and are found in the following location in the Registry:

HKEY_LOCAL_MACHINE
   SYSTEM
      CurrentControlSet
         Services
            servicename
               Parameters

These are the variable names and descriptions:

TraceWithTime:REG_SZ:{ ON | OFF }       Default: OFF

When this variable is set to ON, the output from tracing includes a time field, hh:mm:ss, instead of a process ID field. For more detailed timing, see the Milliseconds registry variable.

Milliseconds:REG_SZ:{ ON | OFF }       Default: OFF

When this variable is set to ON, and the TraceWithTime variable is set to ON, milliseconds are displayed in the time field within a trace.


APPC API: Location and Name of Variable
Registry and Environment Variables for SNA Server	11 of 24

Registry Variables Used on an SNA Server or a Windows NT-Based Client

APPC API: Location and Name of Variable

For an SNA server or a Windows NT-based client, the Registry variable that affects the APPC API is found in the following location in the Registry:

HKEY_LOCAL_MACHINE
   SYSTEM
      CurrentControlSet
         Services
             SnaBase
               Parameters
                  Client

This is the variable name and description:

LUWIDSUP:REG_SZ:{ YES | NO }      Default: YES

When this variable is set to NO, support is deactivated for the logical unit of work identifier (luw_id). Normally, this support is used in APPC, but Comm Server 1.x did not support it. Setting this variable to NO allows compatibility with Comm Server 1.x software.


CPI-C API: Location and Names of Variables
Registry and Environment Variables for SNA Server	12 of 24

Registry Variables Used on an SNA Server or a Windows NT-Based Client

CPI-C API: Location and Names of Variables

For an SNA server or a Windows NT-based client, the Registry variables that affect the CPI-C API are found in the following location in the Registry:

HKEY_LOCAL_MACHINE
   SYSTEM
      CurrentControlSet
         Services
            SnaBase
               Parameters
                  Client

These are the variable names and descriptions:

application:REG_SZ:localLUalias

For this variable, substitute the name of the application for application, and the local LU alias for localLUalias. This variable specifies the local LU alias to be used with a CPI-C application that invokes another application. For information about TPs and APPC LUs, see the Microsoft SNA Server Administration Guide.

APPCTPN:REG_SZ:TPname

For this variable, substitute the name of the local TP, in ASCII, for TPname. For information about TPs and APPC LUs, see the Microsoft SNA Server Administration Guide


CSV API: Location and Names of Variables
Registry and Environment Variables for SNA Server	13 of 24

Registry Variables Used on an SNA Server or a Windows NT-Based Client

CSV API: Location and Names of Variables

For an SNA server or a Windows NT-based client, the Registry variables that affect the CSV API are found in the following location in the Registry:

HKEY_LOCAL_MACHINE
   SYSTEM
      CurrentControlSet
         Services
            SnaBase
               Parameters
                  Client

These are the variable names and descriptions:

COMTBLG:REG_SZ:filename

This variable specifies the name of the file that contains Table G for code conversion. Table G is used with the CONVERT verb.

For more information about CSV, see the Microsoft SNA Server APPC Programmer's Guide.

COMCPT:REG_SZ:path

This variable specifies the directory in which the code page file (for code conversion) is located. For example, if the code page file is located in the directory C:\PAGEDIR, the setting to use is as follows:

COMCPT:REG_SZ:C:\PAGEDIR

For more information about code pages, see the Microsoft SNA Server APPC Programmer's Guide.


LUA API: Location and Name of Variable
Registry and Environment Variables for SNA Server	14 of 24

Registry Variables Used on an SNA Server or a Windows NT-Based Client

LUA API: Location and Name of Variable

For an SNA server or a Windows NT-based client, the Registry variable that affects the conventional Logical Unit Application programming interface (LUA) API is found in the following location in the Registry:

HKEY_LOCAL_MACHINE
   SYSTEM
      CurrentControlSet
         Services
            SnaBase
               Parameters
                  Client

This is the variable name and description:

SNAMAXLUALUS:REG_DWORD:number

This variable sets the maximum number of frames in the protocol window. Setting this number lower means that fewer buffers will be required on the system. It is unlikely that this variable would be required for a Windows NT-based system.


SnaBase: Location and Names of Variables
Registry and Environment Variables for SNA Server	15 of 24

Registry Variables Used on an SNA Server or a Windows NT-Based Client

SnaBase: Location and Names of Variables

For an SNA server or a Windows NT-based client, the Registry variables that affect the SnaBase are found in the following location in the Registry:

HKEY_LOCAL_MACHINE
   SYSTEM
      CurrentControlSet
         Services
            SnaBase
               Parameters

These are the variable names and descriptions:

BufferAuditInterval:REG_DWORD:number

This variable causes SNA Server to carry out audits of the buffer pool at regular intervals, and sets the interval length in seconds. (SNA Server rounds the number of seconds upward to the nearest 5 seconds.) The range for number is 1 through 0xFFFFFFFE.

Normally (that is, when this variable is not set), SNA Server only carries out buffer audits when a buffer pool is extended and more than half of the buffer pool is in use.

When SNA Server carries out a buffer audit, the information is placed in message 684 in the application event log.

LOCALLUS:REG_SZ:localLUname

This variable specifies the LUs to be used for this system, regardless of which user is logged on. Multiple LUs can be specified via the Windows NT Registry Editor. If the variable is not set, SNA Server attempts to assign LUs on a per-user basis, using the currently logged on LAN user identification.

OtherServers:REG_MULTI_SZ:server1 [server2][ ...]

This variable specifies one or more SNA servers outside of the client's domain, to which the client's requests for LUs will be sent, if the requests cannot be satisfied by SNA servers in the client's domain. If this variable is not set, only SNA servers in the client's domain will receive the client's requests for LUs.

When specifying the variable, substitute one or more server names for server1 [server2][ ...]. Separate multiple server names with spaces.

COMPOP12:REG_SZ:{ YES | NO }       Default: NO

When this variable is set to YES, level 12 warnings do not display as pop-up messages on the local system. (Level 12 messages are not as severe as level 16 messages.)


Lan Manager Workstation: Location and Name of Variable
Registry and Environment Variables for SNA Server	16 of 24

Registry Variables Used on an SNA Server or a Windows NT-Based Client

Lan Manager Workstation: Location and Name of Variable

If you have an application written to one of the SNA APIs offered by SNA Server (such as APPC, CPI-C or LUA) on Windows NT-based clients using Microsoft networking protocols (NetBEUI or TCP/IP), and your application uses a large number of Windows NT threads, you may need to add a Registry variable on the clients to permit correct operation.

This Registry variable is called MaxThreads. It can be set on a Windows NT-based client and is found in the following location in the Registry:

HKEY_LOCAL_MACHINE
   SYSTEM
      CurrentControlSet
         Services
            LanmanWorkstation
               Parameters

This is the variable name and description:

MaxThreads:REG_DWORD:number

This variable specifies the number of threads available for use by the Workstation service. Set number to a value between 30 and 255, depending on how heavily the workstation is used by APPC. Try to make the value large enough to support all the APPC usage, but low enough to avoid using excessive amounts of memory.

If this variable is not set, it defaults to 6 threads.


Environment Variables Used on Clients Running Windows Version 3.x, MS-DOS, or OS/2
Registry and Environment Variables for SNA Server	17 of 24

Environment Variables Used on Clients Running Windows Version 3.x, MS-DOS, or OS/2

The environment variables in the following sections can be set on an SNA Server client running the Windows version 3.x, MS-DOS, or OS/2 operating systems. For information about accessing or modifying these variables, see "Setting Variables on Different Operating Systems" earlier in this appendix.

Note

The following sections do not include the variables used for configuring an invokable TP. For information about those variables, see Chapter 2 of the Microsoft SNA Server APPC Programmer's Guide or Chapter 2 of the Microsft SNA Server CPI-C Programmer's Guide.


APPC API
Registry and Environment Variables for SNA Server	18 of 24

Environment Variables Used on Clients Running Windows Version 3.x, MS-DOS, or OS/2

APPC API

LUWIDSUP={ YES | NO }       Default: YES

When this variable is set to NO, support is deactivated for the logical unit of work identifier (luw_id). Normally, this support is used in APPC, but Comm Server 1.x did not support it. Setting this variable to NO allows compatibility with Comm Server 1.x software.


CPI-C API
Registry and Environment Variables for SNA Server	19 of 24

Environment Variables Used on Clients Running Windows Version 3.x, MS-DOS, or OS/2

CPI-C API

[ApplicationName]APPCLLU=localLUalias

For this variable, substitute the name of the application for ApplicationName, and the local LU alias for localLUalias. Type the square brackets around the application name, and place the application name on a separate line, as shown. This variable specifies the local LU alias to be used with a CPI-C application (a TP).

APPCTPN=TPname

For this variable, substitute the name of the TP, in ASCII, for TPname. This variable specifies the local TP name.


CSV API
Registry and Environment Variables for SNA Server	20 of 24

Environment Variables Used on Clients Running Windows Version 3.x, MS-DOS, or OS/2

CSV API

COMTBLG=filename

This variable specifies the name of the file that contains Table G for code conversion. Table G is used with the CONVERT verb.

For more information about CSV, see the Microsoft SNA Server APPC Programmer's Guide.

COMCPT=path

This variable specifies the directory in which the code page file (for code conversion) is located. For example, if the code page file is located in the directory C:\PAGEDIR, the setting to use is as follows:

COMCPT=C:\PAGEDIR

For more information about code pages, see the Microsoft SNA Server APPC Programmer's Guide.


LUA API
Registry and Environment Variables for SNA Server	21 of 24

Environment Variables Used on Clients Running Windows Version 3.x, MS-DOS, or OS/2

LUA API

SNAMAXLUALUS=number

This variable sets the maximum number of frames in the protocol window. Setting this number lower means that fewer buffers will be required on the local system. This is particularly important with MS-DOS, where there is only limited buffer availability. The credit values are based on two LUs per application.


SnaBase
Registry and Environment Variables for SNA Server	22 of 24

Environment Variables Used on Clients Running Windows Version 3.x, MS-DOS, or OS/2

SnaBase

These are the variable names and descriptions:

For MS-DOS and Windows version 3.1:

LOCALLUS=localLUname, localLUname[, ...]

This variable specifies the LUs to be used for this system, regardless of which user is logged on. Multiple LU names should be separated with spaces. If the variable is not set, SNA Server attempts to assign LUs on a per-user basis, using the currently logged on LAN user identification.

OtherServers=server1 [server2][ ...]

This variable specifies one or more SNA servers outside of the client's domain, to which the client's requests for LUs will be sent, if the requests cannot be satisfied by SNA servers in the client's domain. If this variable is not set, only SNA servers in the client's domain will receive the client's requests for LUs.

When specifying the variable, substitute one or more server names for server1 [server2][ ...]. Separate multiple server names with spaces.

For OS/2:

COMLUASS={ YES | NO }       Default: NO

When this variable is set to YES, LUs on this system are assigned on a perworkstation basis, using the LAN computer name. Otherwise, SNA Server attempts to assign LUs on a per-user basis, using the currently logged on LAN user identification.

For MS-DOS, Windows version 3.1, and OS/2:

COMPOP12={ YES | NO }       Default: NO

When this variable is set to YES, level 12 warnings do not display as pop-up messages on the local system. (Level 12 messages are not as severe as level 16 messages.)

For MS-DOS:

OverrideDefaultLU={ YES | NO }       Default: NO

When this variable is set to YES, SNA Server will use the default APPC LUs configured for PC Support; these LUs are specified on the RTLN line of the CONFIG.PCS file. Otherwise, SNA Server will use the default APPC LUs configured in SNA Server; these LUs are assigned to users or groups through SNA Server Admin or through the SNA Server command-line interface (snacfg).

For more information about PC Support, see the following sections in Chapter 3 of the Microsoft SNA Server Installation Guide:

"PC Support Used with Windows for Workgroups"

"Installing an MS-DOS – Based Client," which includes the subsection "PC Support Router Replacement"


Variables for Clients Not Running Microsoft Networking
Registry and Environment Variables for SNA Server	23 of 24

Environment Variables Used on Clients Running Windows Version 3.x, MS-DOS, or OS/2

Variables for Clients Not Running Microsoft Networking

The information in this section affects the logon process for clients running Windows version 3.x but not running Microsoft networking. With these clients, two logons must take place: one for access to the Windows NT domain and one for access to the SNA servers in the domain.

For Clients Running Windows version 3.x

For clients running Windows version 3.x but not running Microsoft networking, each time a user logs on for access to SNA servers, the user's name is stored. At the time of the next logon for access to SNA servers, that user name is offered in the logon dialog box. (Password information is not stored.)

Also, for clients running Windows version 3.x but not running Microsoft networking, command line options can be used to specify the user name and password when starting the SnaBase (which is called wnap in the Windows 3.x environment). The syntax for this is:

wnap /user:username /pwd:password

An example of a client for whom the preceding command might be appropriate is a client running Windows version 3.1 with Novell [image] NetWare [image].

A user who does not use a password may want to type the preceding syntax without typing any characters after /pwd:. This will suppress the dialog box that requests a password.

If the preceding syntax line is used on a client running Microsoft LAN Manager (which is a Microsoft network software product), the user and pwd options are ignored, since the only logon needed for clients using Microsoft networking is the logon in the Windows NT domain (that is, no additional logon is needed to access the SNA servers in the domain).

For Clients Running MS-DOS

For clients running MS-DOS but not running Microsoft networking, the following section and line can be placed in the SNA.INI file to simplify the process of starting up the SnaBase and logging on to the SNA servers in the domain. When typing the section name, include the square brackets.

[SnaBase]LogonUserName=username

Note that for clients running MS-DOS but not running Microsoft networking, command line options can also be used to specify the user name and password when starting the SnaBase on the client. The syntax for this is:

snabase /user:username /pwd:password

An example of a client for whom the preceding command might be appropriate is an MS-DOS – based client running Novell NetWare.

A user who does not use a password may want to type the preceding syntax without typing any characters after /pwd:. This will suppress the dialog box that requests a password.

If the preceding syntax line is used on a client running Microsoft LAN Manager (which is a Microsoft network software product), the user and pwd options are ignored, since the only logon needed for clients using Microsoft networking is the logon in the Windows NT domain (that is, no additional logon is needed to access the SNA servers in the domain).


Variable for Windows-Based Clients Running the 3270 Applet
Registry and Environment Variables for SNA Server	24 of 24

Environment Variables Used on Clients Running Windows Version 3.x, MS-DOS, or OS/2

Variable for Windows-Based Clients Running the 3270 Applet

The variable in this section applies only to clients running the 3270 Applet with Windows NT or Windows version 3.x. On either type of client, the variable is set in the WIN.INI file. This is true even for Windows NT-based clients; the WIN.INI file for such clients belongs in the operating-system root directory.

The variable is set in the WIN.INI file by adding a section called [SnaServerWin3270] to the file and adding a line with the following syntax to that section:

RetryConns={ yes | no }      Default: no

If set to yes, causes the 3270 Applet to retry unsuccessful connection attempts in certain circumstances where the condition causing the problem is probably temporary (see the next paragraph). Otherwise, the 3270 Applet does not retry unsuccessful connection attempts; instead, the user can retry manually by disconnecting and connecting again.

Conditions that are considered temporary are:

All LUs in the requested pool are in use at that moment (code 0x0057).

The requested LU pool is not found in the configuration, which may indicate that the server through which the client is attempting to connect is inactive (code 0x0A0E).

The requested connection is inactive at that moment (code 0x1002).

The host (or controller unit) has not yet responded with an ACTPU command (code 0x1010).

The host (or controller unit) has not yet responded with an ACTLU command (code 0x1011).


Details of the Installation Process
Appendix D	1 of 6

Details of the Installation Process

This appendix describes the directory tree, shares, and Registry keys created by SNA Server Setup in the process of installing SNA Server server software. The appendix does not list every item created by Setup; however, if the items listed in this appendix are removed, SNA Server will be removed and can then be reinstalled.

Note

If SNA Server Setup stops working or is interrupted during installation of an SNA server, and the software is left in a partially installed state, first try using SNA Server Setup to remove the software, as described in the Microsoft SNA Server Installation Guide. If this does not work, it is recommended that you contact your product support channel before attempting further action. Although this appendix provides information that could be used to remove a partially installed SNA server, a mistaken deletion in your Windows NT Registry could cause your computer to stop functioning.

SNA Server Setup creates the following types of elements:

A directory tree

Network shares

Registry keys

The following sections describe these elements.


Directory Tree Created by Setup
Details of the Installation Process	2 of 6

Directory Tree Created by Setup

SNA Server Setup creates one directory tree. By default, the root directory of this tree is C:\SNA, but a different drive and/or name can be specified during setup. The directory tree contains the essential files used by SNA Server. A few files are copied to other directories on the computer, but these files do not affect the functioning of the computer if they remain after other SNA Server directories and files are removed.


Shares Created by Setup
Details of the Installation Process	3 of 6

Shares Created by Setup

When an SNA server is installed, SNA Server Setup creates the shares shown in the following table:

Share name		Location
COMCFG		SNAroot\SYSTEM\CONFIG
COMLOGS		SNAroot\SYSTEM
SNASERV		SNAroot


Registry Keys Created by Setup
Details of the Installation Process	4 of 6

Registry Keys Created by Setup

SNA Server Setup creates many Registry keys and entries in the process of installing an SNA server. Note that removing keys from the Registry should be done with care, because correct function of the operating system depends on correct configuration of the Registry. The tool used for modifying the Registry is the Registry Editor, REGEDT32.EXE. If you modify the Registry, be sure to shut down and restart the server (using the Shutdown command in the File menu of Program Manager). For more information about the Registry, see your Windows NT documentation.


Keys Created for Core Software Components
Details of the Installation Process	5 of 6

Registry Keys Created by Setup

Keys Created for Core Software Components

The Registry keys shown in the following lists are created when SNA Server Setup installs core software components (such as the SnaServr service) on an SNA server. For information about keys created for specific link services, see the next section.

Keys under HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft

The subkeys that SNA Server Setup creates under this key are:

SNA Server

NVRunCmd

Keys under HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services

The subkeys that SNA Server Setup creates under this key are:

NVAlert

NVAlert

NVRunCmd

SnaBase

SnaNetMn

SnaServr

Keys under HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ EventLog \ Application

The subkeys that SNA Server Setup creates under this key are:

NVAlert

NVRunCmd

SNA 3270 Emulator

SNA APPC Application

SNA Base Service

SNA CPI-C Application

SNA CSV Application

SNA DFT Link Service

SNA DLC Link Service

SNA NetMn Service

SNA NetView Alerter

SNA RUI Application

SNA SDLC Link Service

SNA Server

SNA SLI Application

SNA X.25 Link Service


Keys Created for Link Services
Details of the Installation Process	6 of 6

Registry Keys Created by Setup

Keys Created for Link Services

The pairs of Registry keys shown in the following lists are created when SNA Server Setup installs a link service on an SNA server. For information about keys created when SNA Server Setup installs components other than link services, see the previous section.

Keys under HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft

The link service subkeys that SNA Server Setup creates under this key are as follows. For all of the listed names, xx represents from 01 through 99 (decimal).

Link type		Key for link service		Key for device driver
Attachmate SDLC		ATMSDLCLS_1.0_xx		ATMSYNCDD_1.0_xx
Attachmate X.25		ATMX25LS_1.0_xx		ATMSYNCDD_1.0_xx
Barr SDLC		BARRSDLCLS_1.0_xx		BARRSYNCDD_1.0_xx
DCA DFT		DCADFTLS_1.0_xx		DCADFTDD_1.0_xx
DCA SDLC		DCASDLCLS_1.0_xx		DCASYNCDD_1.0_xx
DCA X.25		DCAX25LS_1.0_xx		DCASYNCDD_1.0_xx
DLC 802.2		NDISTokenRingLS_1.0_xx		Not applicable (uses the DLC protocol installed through Windows NT Server)
IBM DFT		IBMDFTLS_1.0_xx		IBMDFTDD_1.0_xx
IBM SDLC		IBMSDLCLS_1.0_xx		IBMSYNCDD_1.0_xx
IBM X.25		IBMX25LS_1.0_xx		IBMSYNCDD_1.0_xx
Microgate SDLC		MGATELS_1.0_xx		IBMSYNCDD_1.0_xx
Microgate X.25		MGATEXLS_1.0_xx		IBMSYNCDD_1.0_xx
Keys under HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services

The link service subkeys that SNA Server Setup creates under this key are as follows. For all of the listed names, x represents an alphanumeric character.

Link type		Key for link service		Key for device driver
Attachmate SDLC		AtmSdlcx		ATMSYNC
Attachmate X.25		AtmX25x		ATMSYNC
Barr SDLC		BarrSx		BARRSYNC
DCA DFT		DcaDftx		DCADFTDD
DCA SDLC		DcaSdlcx		DCASYNC
DCA X.25		DCAX25x		DCASYNC
DLC 802.2		SnaDlcx		Not applicable (uses the DLC protocol installed through Windows NT Server)
IBM DFT		SnaDftx		IBMDFTDD
IBM SDLC		SnaSdlcx		IBMSYNC
IBM X.25		SnaX25x		IBMSYNC
Microgate SDLC		SnaMGx		IBMSYNC
Microgate X.25		SnaMGXx		IBMSYNC
Keys under HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ EventLog \ System

The link service subkeys that SNA Server Setup creates under this key are as follows. For all of the listed names, x represents an alphanumeric character.

Link type		Key for link service		Key for device driver
Attachmate SDLC		AtmSdlcx		ATMSYNC
Attachmate X.25		AtmX25x		ATMSYNC
Barr SDLC		BarrSx		BARRSYNC
DCA DFT		DcaDftx		DCADFTDD
DCA SDLC		DcaSdlcx		DCASYNC
DCA X.25		DCAX25x		DCASYNC
DLC 802.2		Not applicable		Not applicable (uses the DLC protocol installed through Windows NT Server)
IBM DFT		SnaDftx		IBMDFTDD
IBM SDLC		SnaSdlcx		IBMSYNC
IBM X.25		SnaX25x		IBMSYNC
Microgate SDLC		SnaMGx		IBMSYNC
Microgate X.25		SnaMGXx		IBMSYNC