home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 8 Other
/
08-Other.zip
/
nsc12.zip
/
nscug.INF
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1996-07-18
|
212KB
|
8,807 lines
ΓòÉΓòÉΓòÉ 1. Version Notice ΓòÉΓòÉΓòÉ
Second Edition (June 1993)
This edition replaces and makes obsolete the previous edition.
This edition contains changes for Network SignON Coordinator/2 Version 1.2.
This release contains several functional enhancements. For a detailed list of
enhancements and changes, see Summary of Changes.
The following paragraph does not apply to the United Kingdom or any country
where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS
MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states
do not allow disclaimer of express or implied warranties in certain
transactions; therefore, this statement may not apply to you.
This publication could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time.
It is possible that this publication may contain reference to, or information
about, IBM products (machines and programs), programming, or services that are
not announced in your country. Such references or information must not be
construed to mean that IBM intends to announce such IBM products, programming,
or services in your country.
Requests for copies of this publication and for technical information about IBM
products should be made to your IBM Authorized Dealer or your IBM Marketing
Representative.
ΓòÉΓòÉΓòÉ 2. Notices ΓòÉΓòÉΓòÉ
References in this publication to IBM products, programs, or services do not
imply that IBM intends to make these available in all countries in which IBM
operates. Any reference to an IBM product, program, or service is not intended
to state or imply that only IBM's product, program, or service may be used. Any
functionally equivalent product, program, or service that does not infringe any
of IBM's intellectual property rights or other legally protectible rights may
be used instead of the IBM product, program, or service. Evaluation and
verification of operation in conjunction with other products, programs, or
services, except those expressly designated by IBM, are the user's
responsibility.
IBM may have patents or pending patent applications covering subject matter in
this document. The furnishing of this document does not give you any rights to
these patents. You can inquire, in writing, to the IBM Director of Commercial
Relations, IBM Corporation, Purchase, NY 10577 - USA.
For online versions of this book, we authorize you to:
Copy, modify, and print the documentation contained on the media, for use
within your enterprise, provided you reproduce the copyright notice, all
warning statements, and other required statements on each copy or partial
copy.
Transfer the original unaltered copy of the documentation when you
transfer the related IBM product (which may be either machines you own,
or programs, if the program's license terms permit a transfer). You must,
at the same time, destroy all other copies of the documentation.
You are responsible for payment of any taxes, including personal property
taxes, resulting from this authorization.
THERE ARE NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
Some jurisdictions do not allow the exclusion of implied warranties, so the
above exclusion may not apply to you.
Your failure to comply with the terms above terminates this authorization.
Upon termination, you must destroy your machine readable documentation.
The following terms, denoted by an asterisk (*) in this publication, are
trademarks of the IBM Corporation in the United States and/or other countries:
IBM C Set/2 System/370
Operating System/2 OS/2 CICS/ESA
Personal System/2 PS/2 MVS/ESA
Extended Services OfficeVision RACF
Extended Services for OS/2 OfficeVision/VM VTAM
Presentation Manager AS/400 OS/400
Distributed Database DB2
Connection Services/2
The following terms, denoted by a double asterisk (**) in this publication,
are trademarks of other companies:
Microsoft and Windows are registered trademarks of Microsoft Corporation.
Novell, NetWare, and NetWare Requester for OS/2 are registered trademarks
of Novell, Inc.
RUMBA is a registered trademark of Wall Data Incorporated.
ΓòÉΓòÉΓòÉ 3. About This Book ΓòÉΓòÉΓòÉ
This book describes the tasks required to install, configure, and use Network
SignON Coordinator/2 (NSC). NSC is a productivity aid for either DOS or OS/2(*)
end users whose environment includes either multiple LAN Servers or multiple
central site host computer facilities. NSC synchronizes password changes for
all the end user's security signons and can also automate their host and LAN
Server logons.
ΓòÉΓòÉΓòÉ 3.1. Before you Begin ΓòÉΓòÉΓòÉ
You should be familiar with OS/2. You may also need to be familiar with your
LAN and emulator support software.
If you will be configuring NSC, you will need to be familiar with a text editor
or word processor in order to edit and work with the NSC Configuration file. If
you are not familiar with such an editor, see your operating system
documentation.
ΓòÉΓòÉΓòÉ 3.2. Who Should Use This Book ΓòÉΓòÉΓòÉ
This book assists the network administrator in the following tasks:
Planning and preparing for NSC installation.
Configuring NSC for each end user and NSC Servers.
Customizing NSC to address additional needs.
Problem determination.
This book also contains information for the end user about the commands they
use to execute NSC. Finally, this book describes information used by
application programmers to interface directly with NSC.
ΓòÉΓòÉΓòÉ 3.3. How This Book Is Structured ΓòÉΓòÉΓòÉ
This book is organized as follows:
Overview and information on supported configurations with their
prerequisites (see Introduction)
Information for the end user of NSC (see Using Network SignON
Coordinator/2)
Installation instructions (see Installing Network SignON Coordinator/2)
Configuration instructions (see Configuring Network SignON Coordinator/2)
A programmer's guide for using the OS/2 API and Toolkit (see Using the
Application Programming Interface)
An appendix of error messages and explanations (see Messages)
An appendix describing problem determination and log messages (see
Problem Determination)
An appendix on how to write an Exit Routine (see Exit Routines)
An appendix on changes in this version (see Summary of Changes)
ΓòÉΓòÉΓòÉ 3.3.1. Conventions ΓòÉΓòÉΓòÉ
This book uses the following terminology conventions unless otherwise noted:
LAN Server
Is a general term which refers to any of the following products which
provide a server capability:
- IBM OS/2 LAN Server Version 1.3 or later.
- Novell(**) NetWare(**) Version 3.11
DOS
Refers to IBM DOS Version 3.3 or later.
Communications Manager
Refers to one of the following products:
- IBM OS/2 Extended Edition 1.3 (EE 1.3) Communications Manager
- IBM OS/2 Extended Services(*) 1.0 (ES 1.0) Communications Manager
- IBM Communications Manager/2 Version 1.0 or later.
LAN Support Program
Refers to the version of the IBM LAN Support Program that is included
with the IBM LAN Server.
Emulator support
Is a general term which refers to software providing 3270 or 5250
terminal emulation communications between a PC and another computer.
Note: Highlighting may vary online depending on the type of display.
The following text conventions are used:
Bold Bold print indicates choices made from a menu or action bar.
Italics Italics introduces new terms in the text and indicates
variables.
UPPERCASE Uppercase letters are used for commands, and for directory,
device, and file names.
ΓòÉΓòÉΓòÉ 3.4. Related Publications ΓòÉΓòÉΓòÉ
The following is a list of related publications. For information about
ordering these publications, contact your IBM authorized dealer or IBM
marketing representative.
RACF/MVS General Information, GC28-0722
MVS/ESA General Information, GC28-1600
Local Area Network Technical Reference, SC30-3383
IBM Extended Edition Version 1.3 Programming Services and Advanced
Problem Determination for Communications.
IBM Extended Services for OS/2 Programming Services and Advanced Problem
Determination for Communications.
ΓòÉΓòÉΓòÉ 4. Introduction ΓòÉΓòÉΓòÉ
This chapter describes Network SignON Coordinator/2 (NSC) and defines its
prerequisites and supported configurations.
Overview explains NSC's functions and the terms used in later sections.
DOS Clients explains the prerequisites and supported function for NSC DOS
Clients.
OS/2 Clients explains the prerequisites and supported function for NSC OS/2
Clients.
NSC Server explains the prerequisites and supported function for NSC Servers.
Host Systems explains the prerequisites and supported function for hosts.
RAM and DASD requirements gives RAM and Disk requirements.
Security Considerations gives some security considerations.
ΓòÉΓòÉΓòÉ 4.1. Overview ΓòÉΓòÉΓòÉ
Network SignON Coordinator/2 is a productivity aid for DOS and OS/2 end users
whose environment requires multiple user signons to different access control
functions. OS/2 User Profile Management (UPM), IBM LAN Server, and Resource
Access Control Facility (RACF) are examples of access control functions. NSC
refers to these access control functions as "locations". Each location requires
you to signon with an ID and a password before providing access to its
resources. NSC allows you to signon, change passwords, and signoff at one or
more locations with a single operation. A signon, change password, or signoff
operation is referred to as a "request".
Locations are defined in the NSC configuration file (NSC.INI). The location
definition can contain a User ID to be used for request processing. The same
location can be defined as many times as necessary to include all IDs you have
at that location. NSC prompts for your current password and User ID (if
unknown). NSC then combines the location information, User ID, and password to
process your request. NSC assumes you have the same password at all locations.
Password change requests are performed at all locations. Signon requests,
however, are only performed at selected locations based on the location
definition. The signoff request signs you off all systems logged on to by a
signon request. Using the graphical interface, you can selectively signon or
signoff a particular location using any ID you defined for that location. This
provides an easy method of accessing a location without affecting your current
access at other locations.
NSC operates as a Client (DOS and OS/2) and as a Server (OS/2 only)
configuration. Figure "NSC Configurations", below, shows how these NSC
configurations relate to locations and the requests that each supports.
NSC Configurations
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Host Γöé
Γöé Γöé
Γöé VM MVS OS/400(*) Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé Γöé
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NSC Client Γöé Γöé NSC Server Γöé Γöé NSC Client Γöé
Γöé Γöé Γöé Γöé Γöé Γöé
Γöé Change Pswd Γöé Γöé Change Pswd Γöé Γöé Change Pswd Γöé
Γöé Signon Γöé Γöé Γöé Γöé Signon Γöé
Γöé Signoff Γöé Γöé Γöé Γöé Signoff Γöé
Γöé Γöé Γöé Γöé Γöé Γöé
Γöé OS/2 Γöé Γöé OS/2 Γöé Γöé DOS Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÿ
Γöé Γöé Γöé Γöé
Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé LAN Server Γöé
Γöé Γöé
Γöé NetWare IBM LAN Server Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
The boxes in the middle of Figure "NSC Configurations" show the major NSC
configurations -- the Client and the Server. NSC uses location definitions to
determine how to process a request (signon, change password, and signoff). The
location definitions are:
LANServer
Specifies the name of an IBM OS/2 LAN Server domain or Novell NetWare
file server to process the user request. Multiple LAN Server definitions
can be specified. Options include:
- Use a User ID other than the default.
- Log the user onto the LANServer for default signons.
- Execute an Exit Routine after performing the request.
If the user provides a new password, NSC processes a password change for
all LAN Servers defined.
Local
Specifies that OS/2 User Profile Management (UPM) is to process the user
request. A Local Logon is performed for a signon. Multiple Local
definitions can be specified. Options include:
- Use a User ID other than the default.
- Log the user on for default signons.
- Execute an Exit Routine after performing the request.
If the user provides a new password, NSC processes a password change for
all Local definitions.
Node
Specifies that OS/2 UPM is to process the user request. A Node Logon is
performed for a signon. Multiple Node definitions can be specified.
Options include:
- Use a User ID other than the default.
- Log the user on for default signons.
- Execute an Exit Routine after performing the request.
If the user provides a new password, NSC updates all Node logons.
Host
Specifies a host system to process the user request and the type of host
connection. MVS, VM, and AS/400 can be host locations. Multiple Host
definitions can be specified.
NSC supports two types of host connections:
- 3270 or 5250 terminal emulation
NSC can use a terminal emulation session with a host computer via
Emulator High-Level Language Application Programming Interface
(EHLLAPI). EHLLAPI is provided by emulators on an OS/2 or DOS
workstation to access a host terminal presentation space for 3270
and 5250 terminal emulators. MVS, VM, and AS/400 are examples of IBM
systems that support these types of terminals.
- Advanced Program to Program Communications (APPC)
APPC is an implementation of Systems Network Architecture (SNA) for
logical unit (LU) type 6.2. It provides, distributed transaction
processing, in which two or more programs cooperate to carry out
some processing function. MVS/ESA is the only host system with which
NSC on OS/2 can communicate using APPC.
Options include:
- Use a User ID other than the default.
- Log the user on to multiple host terminal emulation sessions for
default signons.
- Check the password as valid and active (not expired) at a host
connected via APPC during default signons.
- Execute an Exit Routine after performing the request.
If the user provides a new password, NSC processes a password change for
all Host definitions.
NSC Server processing is initiated by the NSC Client when it processes
definitions in its NSC configuration file which follow an NSC Server
definition. The NSC Server capability provides remote UPM password changes,
increases flexibility in host connectivity, and extends the capabilities of
the NSC DOS Client. For example, in an IBM OS/2 Database Manager environment,
you can run the NSC Server in the Database Server machine and change a user's
password from that user's NSC Client.
Network SignON Coordinator/2 provides additional features for users to
customize their system, including:
User Exits for additional coordination or synchronization of signons,
password changes, and signoffs.
The ability to specify different User IDs on each system.
Configuration options for User ID character set, User ID length, and
password length.
The ability to access configuration files from a remote LAN node for a
specific user or group of users.
Dynamic host emulator session allocation.
An OS/2 API and toolkit that supports all of the function of NSC while
bypassing the user interface.
Queueing requests to hosts, LAN Servers, or NSC Servers when the remote
locations are not online.
Users in the double-byte character set (DBCS) environment are limited to using
single-byte characters in their User IDs and passwords.
ΓòÉΓòÉΓòÉ 4.2. Configurations and Prerequisites ΓòÉΓòÉΓòÉ
NSC operates in three different configurations: DOS Client, OS/2 Client, and
NSC Server. See the following sections for details about each configuration:
DOS Clients
OS/2 Clients
NSC Server
For details on Host system requirements, see Host Systems. For RAM and Disk
requirements, see RAM and DASD requirements.
ΓòÉΓòÉΓòÉ 4.2.1. DOS Clients ΓòÉΓòÉΓòÉ
The NSC DOS Client requires:
DOS Version 3.3 or later.
For NSC Server requests, NETBIOS support must be installed. This support
can be provided by any product conforming to the DOS NETBIOS software
specification as defined in the Local Area Network Technical Reference,
SC30-3383.
For IBM LAN Server Domain requests, IBM OS/2 LAN Server Version 1.3 or
later (DOS LAN Requester component).
For Novell NetWare Version 3.11 file server requests, the appropriate
NetWare configuration for the level of DOS as defined by Novell must be
installed.
For host emulator sessions, terminal emulation software that provides an
EHLLAPI X'7F' software interrupt handler.
The following emulators have been validated:
IBM PC 3270 Emulation Program Entry Level Version 2.0 and 3.0
IBM Personal Communication/3270 (DOS Mode) Version 2.0 and 3.0
IBM Personal Communication/3270 (Windows(**) Mode) Version 3.0 (1)
RUMBA(**) for the Mainframe Version 3.1, Update 05 (1)
RUMBA for the AS/400 Version 1.0, Update 03, with PTF 8757 (1).
(1) Works in Windows 386/486 Enhanced mode only.
The NSC DOS Client has the following function:
Client Functions
The NSC DOS Client can request a signon, password change, or signoff for
LAN Servers or hosts connected to the client.
If the user requests a password change while signed on to the LAN Server,
the user remains signed on. If the user is not signed on to a LAN Server,
the user is signed on, the password is changed, and the user is signed
off.
Server Functions
The NSC DOS Client can utilize all the functions provided by the NSC
Server.
ΓòÉΓòÉΓòÉ 4.2.2. OS/2 Clients ΓòÉΓòÉΓòÉ
The NSC OS/2 Client requires:
OS/2 Version 1.3 or later.
NETBIOS support
For IBM LAN Server Domain requests, IBM OS/2 LAN Server Version 1.3 or
later (either the LAN Requester or LAN Server component).
For Novell NetWare Version 3.11 file server requests, the NetWare
Requester must be installed on OS/2 2.0 or later.
For local UPM requests, one of the following:
IBM OS/2 Extended Edition 1.3 (EE 1.3)
IBM OS/2 Extended Services 1.0 (ES 1.0)
IBM OS/2 LAN Server Version 1.3 or later (either the LAN Requester
or LAN Server component).
IBM Communications Manager/2 Version 1.0 (CM/2 1.0) or later.
For requests to hosts connected to the Client, Communications Manager
from either EE 1.3, ES 1.0 or CM/2 1.0.
The NSC OS/2 Client has the following function:
Client Functions
The NSC OS/2 Client can request a signon, password change, or signoff for
a LAN Server, local UPM accounts, UPM node logons, or hosts connected to
the client.
Server Functions
The NSC OS/2 Client can utilize all the functions provided by the NSC
Server.
Queueing of Retries
If a LAN Server, local UPM, host, or NSC Server does not respond to a
request, the NSC OS/2 Client can place the request on a retry queue if
the NSC Retry Process has been started.
ΓòÉΓòÉΓòÉ 4.2.3. NSC Server ΓòÉΓòÉΓòÉ
The NSC Server requires:
OS/2 Version 1.3 or 2.0, or OS/2 Warp
NETBIOS support
For local UPM requests, one of the following:
IBM OS/2 Extended Edition 1.3 (EE 1.3)
IBM OS/2 Extended Services 1.0 (ES 1.0)
IBM OS/2 LAN Server Version 1.3 or later (either the LAN Requester
or LAN Server component).
IBM Communications Manager/2 Version 1.0 (CM/2 1.0) or later.
For requests to hosts connected to the Server, Communications Manager
from either EE 1.3, ES 1.0 or CM/2 1.0.
The NSC Server has the following function:
Server Functions
The NSC Server can process requests from NSC Clients for password changes
for local UPM accounts or hosts connected to the NSC Server. The NSC
Server can also process signon verification requests from NSC Clients for
hosts connected via APPC.
The NSC Server can be a single point for an administrator to maintain all
the NSC configuration files needed by the NSC Client workstations. The
NSC Clients are configured to request their configuration files from an
NSC Server. The Clients then access the configuration files at the Server
based on the ID of the user signed on to the workstation.
Queueing of Retries
If the local UPM or a host does not respond to a request, the NSC Server
can place the request on a retry queue if the NSC Retry Process has been
started.
ΓòÉΓòÉΓòÉ 4.2.4. Host Systems ΓòÉΓòÉΓòÉ
Network SignON Coordinator/2 communicates to host systems using APPC on OS/2 or
host emulator sessions on DOS or OS/2. The following defines the host system
support requirements for these connections.
Emulator Sessions
NSC interfaces with PC communications software packages which support
3270 or 5250 terminal emulation and provide EHLLAPI. The supported
emulators depend on whether the workstation is using DOS or OS/2. NSC has
no special host programming support requirements.
APPC
NSC host support via APPC operates only on OS/2 and uses the
Communications Manager. The host computer must have MVS/ESA, RACF/MVS,
and ACF/VTAM. RACF/MVS verifies and manages passwords.
The host system must use the MVS/ESA System Product, program product
numbers 5695-047 (JES2) or 5695-048 (JES3). See MVS/ESA General
Information, GC28-1600 for further information.
If the host system has MVS/ESA Version 4 Release 3 or later, the
following additional software is needed:
- RACF/MVS 1.9.2 or later, program product number 5740-XXH. See
RACF/MVS General Information, GC28-0722 for further information.
- Appropriate levels of ACF/VTAM, NCP, and SSP.
If the host system has MVS/ESA Version 4 Release 1 or 2, the following
additional software is needed:
- CICS/ESA Version 3 Release 3 or later, program product number
5685-083.
- RACF/MVS 1.9.0 or later, program product number 5740-XXH. See
RACF/MVS General Information, GC28-0722 for further information.
- Appropriate levels of ACF/VTAM, NCP, and SSP.
ΓòÉΓòÉΓòÉ 4.2.5. RAM and DASD requirements ΓòÉΓòÉΓòÉ
Static memory and fixed-disk space requirements for Network SignON
Coordinator/2 are given in the following table for each configuration:
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé RAM and DASD Requirements Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé REQUIREMENT Γöé DOS Γöé OS/2 Γöé OS/2 Γöé OS/2 Γöé
Γöé Γöé CLIENT Γöé CLIENT Γöé SERVER Γöé CLIENT/SERVERΓöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Memory Γöé 160KB Γöé 170KB Γöé 130KB Γöé 200KB Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Fixed-Disk Γöé 230KB Γöé 640KB Γöé 455KB Γöé 665KB Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
If you do not require APPC Host connections, the fixed-disk space requirements
for all OS/2 configurations can be reduced by 95K by deleting the sample
Communications Manager configuration file.
Memory requirements do not include dynamic memory allocated for buffering
locally accessed configuration files or host information files.
ΓòÉΓòÉΓòÉ 4.3. Security Considerations ΓòÉΓòÉΓòÉ
Network SignON Coordinator/2 is not a security product; it is a productivity
aid. However, since it does help the user manage passwords, some care has been
taken to avoid creating additional security exposures for the user. Review the
following with respect to your security requirements:
NSC assumes the user has the same password at all locations. If a user's
password is compromised, the security exposure may be greater since all
locations can be accessed with that password.
If this exposure is unacceptable, you should not use NSC.
NSC can remember the user's password once it has been entered, but only
if this option (SAVEPW) is configured. The default operation requires the
user to reenter the password each time it is required.
The password is always discarded when NSC is terminated, even if SAVEPW
is configured.
NSC does not keep passwords in the clear in memory except when necessary
to call external application programming interfaces. The password is
masked and distributed using a simple reversible algorithm designed to
prevent casual viewing of the password.
NSC does not send passwords from NSC Clients to NSC Servers in the clear.
The password is disguised to prevent casual viewing of the password via
network analyzers.
Products supported by NSC send the passwords across the network using
different techniques. For information on how passwords are communicated
by these products, consult the product information for that product.
NSC provides no function for restricting access to locations. Access to
other locations is controlled by each location's own security facility.
NSC performs no encryption, and is therefore not subject to any export
restriction related to encryption.
ΓòÉΓòÉΓòÉ 5. Using Network SignON Coordinator/2 ΓòÉΓòÉΓòÉ
This chapter contains the following sections, which explain how you interact
with Network SignON Coordinator/2:
End User Commands explains how you use the command line interface, DOS
menu interface and OS/2 graphical interface.
Special Considerations discusses specific situations you may encounter.
NSC Support Processes explains how you start the NSC Server and NSC Retry
Process.
When any of the NSC End User Commands or Support Programs terminate, they set
the operating system ERRORLEVEL to one of the following values:
ERRORLEVEL Meaning
0 No errors or warnings
1 One or more warnings (no errors)
2 One or more errors
ΓòÉΓòÉΓòÉ 5.1. End User Commands ΓòÉΓòÉΓòÉ
The way you use NSC to signon and signoff your personal computer depends on
which computer interface you prefer:
Command Line If you are familiar with operating system commands, the
command line interface is an efficient way to perform NSC
requests. When you type in a command, the results are
displayed as text on the screen. This interface method is
also very useful in building customized command files. If you
create a command file which includes a password, consider the
security exposure of who may gain access to the command file.
The command line interface is available for both DOS and OS/2
Clients. The command is described in Command Line Interface.
Menu The menu interface requests you to enter information at
prompt fields. You type the required information on the
keyboard. This interface does not display information entered
in password fields.
The menu interface is available only for DOS Clients. The
command is described in Menu Interface.
Graphical A graphical interface lets you make selections and enter
information using both mouse and keyboard. A graphical
interface is easy to use and lets you enter passwords in
non-displayed fields. You also have easy access to online
help information. NSC messages are presented in a scrollable
area. The graphical interface also supports signon and
signoff for a selected system.
The graphical interface is available only for OS/2 Clients.
The command is described in Graphical Interface.
ΓòÉΓòÉΓòÉ 5.1.1. Command Line Interface ΓòÉΓòÉΓòÉ
To signon to the locations for which you specified the ON option in your
configuration, use the NSC command with the ON parameter. The syntax for this
is:
>>ΓöÇΓöÇNSCΓöÇΓöÇONΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇ><
ΓööΓöÇuseridΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÿ
ΓööΓöÇcurrentΓöÇpasswordΓöÇΓöÿ
If you do not specify your userid and current-password, the menu or graphical
interface is presented.
To signoff of all locations where you are currently signed on, use the NSC
command with the OFF parameter. The syntax for this is:
>>ΓöÇΓöÇNSCΓöÇΓöÇOFFΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇ><
ΓööΓöÇuseridΓöÇΓöÿ
To change your password at all of your configured locations, use the NSC
command with the CHGPW parameter. The syntax for this is:
>>ΓöÇΓöÇNSCΓöÇΓöÇCHGPWΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇ><
ΓööΓöÇuseridΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÿ
ΓööΓöÇcurrentΓöÇpasswordΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÿ
ΓööΓöÇnewΓöÇpasswordΓöÇΓöÿ
If you do not specify your userid, current-password and new-password, the menu
or graphical interface is presented.
Whenever you specify userid with the NSC command, it overrides any USERID
option in a NSC configuration file. If you type NSC and press Enter without the
ON, OFF or CHGPW parameter, the menu or graphical interface is presented. If
you specify all of the parameters required for the operation so that the menu
or graphical interface is not presented, all of the messages for the requests
initiated by NSC are written to standard output (the display, unless you
redirect standard output).
ΓòÉΓòÉΓòÉ 5.1.2. Menu Interface ΓòÉΓòÉΓòÉ
To use the menu interface for DOS, type NSC and press Enter. The command syntax
is the same as that defined in Command Line Interface. If you do not specify
all of the parameters required to execute the command, the menu interface is
presented. If you specify the ON or CHGPW parameter, the appropriate menu will
be displayed. If you specify the userid, it overrides any USERID option in a
NSC configuration file. If you specify the current-password for the CHGPW
command, it is used for the menu value.
The menu interface displays a full-screen character-mode menu, giving you the
option to signon, change passwords, or signoff. Signon/signoff for a selected
system, online information and help are not available from the menu interface.
ΓòÉΓòÉΓòÉ 5.1.3. Graphical Interface ΓòÉΓòÉΓòÉ
The graphical interface can be initiated by using the mouse to open the icon
representing NSC in the Network SignON Coordinator/2 folder.
You can also initiate the graphical interface for OS/2 in the same way you
start the menu interface for DOS -- type NSC and press Enter. The command
syntax is the same as that defined in Command Line Interface. If you do not
specify all of the parameters required to execute the command, the graphical
interface is presented. If you specify the ON or CHGPW parameter, the
appropriate panel will be displayed. If you specify the userid, it overrides
any USERID option in a NSC configuration file. If you specify the
current-password for the CHGPW command, it is used for the panel value.
The graphical interface can also be initiated directly by typing NSCPM and
pressing Enter. In fact, the icon representing NSC in the Network SignON
Coordinator/2 folder does just that. NSCPM is the Presentation Manager (PM)
program. It should be used when starting NSC from a folder because it avoids
starting a full screen program for NSC first. The command syntax for NSCPM is
the same as that defined for NSC in Command Line Interface. It always presents
the graphical interface.
When you start the graphical interface, a logo panel is conditionally
displayed. The duration for which it is displayed is controlled by your OS/2
System setting for logos.
The graphical interface opens two Presentation Manager windows. In the primary
window, NSC displays icons indicating the status of each location where you can
sign on (icons are not displayed for locations where signon is not allowed). If
you are currently signed on to a location, the icon is displayed with a shaded
workstation screen and a connection indicator if the location is not Local, and
the User ID signed on is displayed (in this case, if the User ID is displayed
as "<Unknown>", this indicates NSC is not certain of the signed on User ID). If
you are signed on to a host emulation session, the session id is displayed
after the host name. Double clicking on the icon will sign you off.
If you are not currently signed on to a location, the icon is displayed with a
clear workstation screen and no connection indicator, and no User ID is
displayed (in this case, if the User ID is displayed as "<Unknown>", this
indicates NSC is not certain of the signon state). Double clicking on the icon
will sign you on using the User ID for the first definition for this location.
The action bar menu provides the following menu hierarchy of functions:
Actions
- Signon
-- Default Systems -- Signon to the locations for which you
specified the ON option in your configuration.
-- Selected Systems -- Signon to the currently selected (cursored)
location.
- Change Password... -- Change passwords at all configured locations.
- Signoff
-- All Systems -- Signoff of all locations where you are currently
signed on.
-- Selected System -- Signoff of the currently selected (cursored)
location.
- Exit -- Exit NSC.
Options
- Show/Hide Messages -- Display or minimize the Messages window
(depending on the current state of the window).
Help
- Using help -- Display instructions on using the help facility.
- General help -- Display help for NSC.
- Keys help -- Display help on keys.
- Reference Information -- Display the NSC online reference
information.
- Product Information -- Display the NSC logo and product information.
Clicking the right mouse button on an icon will cause a menu of available
actions to be displayed for the location, including a signon action for each
User ID defined for the location. Clicking the right mouse button in the
client area but not on an icon will cause a menu of available actions to be
displayed for all locations.
As actions are performed, messages are written to the list box in the Messages
window (the second PM window opened by NSC). The window may be scrolled back
to review messages. New messages will always cause the list box to be scrolled
to the end so the new message will be visible. Help for error messages is
provided by selecting the message in the list box.
If you move or resize either of the NSC windows, NSC will remember the
position and size of the windows the next time you start the graphical
interface. You can start multiple PM sessions running the graphical interface;
however, only one set of window locations/sizes is saved.
ΓòÉΓòÉΓòÉ 5.2. Special Considerations ΓòÉΓòÉΓòÉ
Password Change Considerations discusses what to do when your passwords get out
of sync between computer systems.
If you have a LOCAL signon and use EE 1.3 or have a LANSERVER signon and use
IBM LAN Server 1.3, you should review the information in Incorrect Passwords.
ΓòÉΓòÉΓòÉ 5.2.1. Password Change Considerations ΓòÉΓòÉΓòÉ
This section describes what to do when an error occurs while changing a
password. It also explains the steps to take the first time you use NSC.
When you change your password, Network SignON Coordinator/2 attempts to make
the change on every computer system defined in the NSC configuration file.
Occasionally a password change cannot be processed (e.g., the communication
link to the host system is down) or the request fails for another reason. NSC
displays an error message on your screen, but it changes your password at all
the other systems. For example, suppose the NSC configuration file contained
the following three system definitions:
HOST,NAME=SYSTEM1,...
HOST,NAME=SYSTEM2,...
HOST,NAME=SYSTEM3,...
Assume your current password is BLUE and you decide to change it to RED. Using
NSC, you make a change password request, which results in these actions:
1. Password changed to RED on SYSTEM1
2. Password change fails on SYSTEM2
3. Password changed to RED on SYSTEM3
Your passwords are now out of sync. SYSTEM2 has the password BLUE.
How do you straighten this mess out?
When SYSTEM2 is available, repeat the change password request using BLUE as
your current password and RED as your new password. This results in the
following actions:
1. Password change fails on SYSTEM1
2. Password changed to RED on SYSTEM2
3. Password change fails on SYSTEM3
You can ignore the failures reported from SYSTEM1 and SYSTEM3 because your
first password change request was successful. Should SYSTEM2 fail again,
repeat the process when the failure has been corrected. You should repeat this
process until all of your system passwords are back in sync. If the password
change failed because the new password is not acceptable, pick another new
password and follow the password change process.
When you first use NSC, you probably will have different passwords on each
system defined in the NSC configuration file. You should choose a new password
acceptable on all your systems, and use NSC to make a password change.
Remember to repeat the request using each system's current password until you
get them all in sync.
You should not attempt a LAN Server domain password change more than once when
logged on to a LAN Server domain. If you need to repeat a password change to
get your passwords in sync and have a LAN Server domain, perform a signoff
request before starting.
ΓòÉΓòÉΓòÉ 5.2.2. Incorrect Passwords ΓòÉΓòÉΓòÉ
If you have a LOCAL signon and use EE 1.3 or have a LANSERVER signon and use
IBM LAN Server 1.3, then review the following information.
If you enter an incorrect password in either the EE 1.3 or IBM LAN Server 1.3
environments, you will be prompted to enter a different password. Figure
"Incorrect Passwords" shows the pop-up panel that appears.
Incorrect Passwords
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Logon Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Γöé
Γöé Γöé
Γöé Note: The password will not display Γöé
Γöé Γöé
Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé
Γöé User ID ΓöéPDQUEUE.Γöé Γöé
Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé
Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé
Γöé Password Γöé........Γöé Γöé
Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé
Γöé Γöé
Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé
Γöé Γöé Enter Γöé Γöé Cancel Γöé Γöé Help Γöé Γöé
Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé
Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
The panel shown in Figure "Incorrect Passwords" is displayed by UPM, not NSC.
You should select Cancel to return to NSC. Then, use NSC to repeat the signon
with the correct password.
ΓòÉΓòÉΓòÉ 5.3. NSC Support Processes ΓòÉΓòÉΓòÉ
NSC provides two support processes to help you keep your password changes in
sync more easily and to extend your connection to either another OS/2 or host
system.
These support processes are:
NSCRETRY - Start the NSC Retry Process
NSCNDMN - Start the NSC Server
ΓòÉΓòÉΓòÉ 5.3.1. NSCRETRY - Start the NSC Retry Process ΓòÉΓòÉΓòÉ
NSCRETRY creates a queue for requests that originally failed, and retries these
requests at set intervals. The retry queue is lost in a power failure or when
you shutdown the workstation. NSCRETRY is installed on the NSC OS/2 Client and
on the NSC Server.
By default, outstanding requests will be retried three times at fifteen minute
intervals. The number of retries and the retry interval are configurable. if a
request is removed from the queue because the maximum number of retries has
been reached, NSCRETRY sounds a 2.5 second beep. If a request has been queued
for retry, once the situation causing the original failure has been remedied,
you should check the NSCRETRY output messages to verify that the request was
processed.
EXIT processing specified in an NSC configuration definition is not done for
any request handled by NSCRETRY. Your exit routine will only get control when
the initial request fails and is queued for retry.
NSCRETRY may be run as a windowed or full screen program. Start NSCRETRY from
"STARTUP.CMD" or from the OS/2 System Startup folder. Use the following command
to start NSCRETRY in STARTUP.CMD.
START "NSC Retry Process" NSCRETRY.EXE
Once NSCRETRY starts, you can stop it by:
Pressing Ctrl+c
Pressing Ctrl+Break
Closing the task from your desktop
Syntax
<ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ<
>>ΓöÇΓöÇNSCRETRYΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇ><
ΓööΓöÇΓö¼ΓöÇ/InnΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÿ
Γö£ΓöÇ/RnnnΓöÇΓöÇΓöñ
ΓööΓöÇ/DEBUGΓöÇΓöÿ
Parameters:
May be entered in lower case, upper case, or mixed case.
/Inn The /I option specifies the delay interval in minutes
between retries. nn is the number of minutes to
delay, from 1 to 60. The default is 15 minutes.
/Rnnn The /R option specifies the number of retries before
the request is deleted from the queue. nnn is the
number of retries, from 1 to 100. The default is 3.
/DEBUG This option causes NSC to log additional debugging
trace information. See Problem Determination for
further details.
Example
The following example causes the NSC Retry process to be started
with a delay interval of 20 minutes.
NSCRETRY /I20
Output
When NSCRETRY is started, the following messages are displayed:
(c) Copyright IBM Corporation 1992, 1995
Network SignON Coordinator/2 Retry Process Version 1.2
IN 01 nn:nn:nn NSCRETRY System queue for retry requests created.
IN 01 nn:nn:nn NSCRETRY Maximum number of attempts per request is nnn.
IN 01 nn:nn:nn NSCRETRY Delay interval between attempts is nn minute(s).
IN 01 nn:nn:nn NSCRETRY Waiting for retry request.
Whenever the queue becomes empty, the last message listed above
is redisplayed. Whenever the queue is empty and a retry request
is received, the following message is displayed:
IN 01 nn:nn:nn NSCRETRY Sleeping until time to retry.
When a request is retried, messages are displayed in the
following format:
IN 01 nn:nn:nn NSCRETRY <execution message>
The execution messages are documented in Messages.
ΓòÉΓòÉΓòÉ 5.3.2. NSCNDMN - Start the NSC Server ΓòÉΓòÉΓòÉ
NSCNDMN is installed on an NSC Server. It must be started on an OS/2
Workstation before NSC Clients can access configuration files stored on the NSC
Server, or process requests on the NSC Server or Host systems connected to it.
NSCNDMN listens for NETBIOS connections from NSC Clients, establishes sessions
with NSC Clients to do the following:
Receive remote requests for configuration files, read the requested
configuration files, and send them to the NSC Client. Refer to GETDEFS
for information on using configuration files stored on the NSC Server.
Receive remote requests for signon verification or password changes, and
execute the requests for the NSC Clients. Refer to SERVER for information
on configuring location definitions at the NSC Server.
NSCNDMN may be run as a windowed or full screen program. It writes messages to
the screen and sounds a beep when an error is detected. Start NSCNDMN from
"STARTUP.CMD" or from the OS/2 System Startup folder. Use the following
command to start NSCNDMN in STARTUP.CMD.
START "NSC Server Process" NSCNDMN.EXE
Once NSCNDMN starts, you can stop it by:
Pressing Ctrl+c
Pressing Ctrl+Break
Closing the task from your desktop
Syntax
<ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ<
>>ΓöÇΓöÇNSCNDMNΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇ><
ΓööΓöÇΓö¼ΓöÇ/CnnΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÿ
Γö£ΓöÇ/DEBUGΓöÇΓöñ
ΓööΓöÇnameΓöÇΓöÇΓöÇΓöÿ
Parameters:
May be entered in lower case, upper case, or mixed case.
/Cnn The /C option specifies the maximum number of
concurrent NSC Client requests processed by the NSC
Server. nn is the number of concurrent requests, from
1 to 16. If this option is specified, the NSC Server
will require nn NETBIOS sessions and nn NETBIOS
commands to initialize successfully. The default is
to attempt to allow up to 6 concurrent requests if
there are adequate NETBIOS resources when the NSC
Server starts; if fewer NETBIOS sessions or commands
are available, the NSC Server will use them as long
as there are at least 2 of each. See Configuring
NETBIOS for further details on NETBIOS Resources.
Specifying a large number for this option may improve
NSC Server throughput when the NSC Server is used by
a large number of NSC Clients.
/DEBUG This option causes NSC to log additional debugging
trace information. See Problem Determination for
further details.
name The name parameter specifies a name to be used for
this NSC Server. It is used in SERVER definitions
(see SERVER) and GETDEFS definitions (see GETDEFS).
If this parameter is not specified, NSC uses the
computername configured for the IBM LAN Requester or
IBM LAN Server, and can be found in the IBMLAN.INI
file in the IBMLAN directory.
You must specify this parameter if neither LAN
Requester or LAN Server is installed. In this case,
the name specified must be unique within the LAN and
can not match any other NSC Server's name, LAN
Requester computername, or LAN Server computername.
The name must be from 1 to 15 characters in length.
Lower case alphabetic characters are converted to
upper case.
Example
The following example causes the NSC Server process named
NSCSERV01 to be started with debugging.
NSCNDMN NSCSERV01 /debug
Output
When NSCNDMN is started, the following messages are displayed:
(c) Copyright IBM Corporation 1992, 1995
Network SignON Coordinator/2 Server Version 1.2
IN 01 nn:nn:nn NSCNDMN NSC Server NSCSERV01 has successfully started.
ΓòÉΓòÉΓòÉ 6. Installing Network SignON Coordinator/2 ΓòÉΓòÉΓòÉ
This chapter explains how to install Network SignON Coordinator/2 onto a
workstation's hard disk. You can install NSC on a workstation in one of four
configurations:
NSC DOS Client
NSC OS/2 Client
NSC Server
NSC OS/2 Client and NSC Server
This allows a workstation to function as both an NSC OS/2 Client and an
NSC Server.
All installation instructions assume that the installation diskette (or its
files stored in the same directory structure) is in the current drive and that
your current directory is the root of that drive. For example, if you are
using a diskette enter these commands:
A:
CD \
to proceed with the installation instructions.
If you have a LAN Server and have copied the installation diskette onto its
hard disk, you can perform the installation across a LAN. You should copy the
installation diskette into a separate directory on the LAN Server's disk. At
the LAN server enter these commands:
MD D:\NSCDISK
CD D:\NSCDISK
XCOPY A: /S
Assuming you have the LAN Requester running on the workstation you only need
to switch to a drive that logically represents the directory containing the
NSC install diskette image. For example, if N is a redirected drive, the
following commands get you ready to start the installation.
N:
CD \
If you are installing NSC Version 1.1 over NSC Version 1.0, the install will
keep your NSC.INI configuration file as it is.
You should be ready to start the install. Choose among these options:
Installing DOS Workstations
Installing OS/2 Workstations
ΓòÉΓòÉΓòÉ 6.1. Installing DOS Workstations ΓòÉΓòÉΓòÉ
To install an NSC client on a DOS workstation, follow these steps:
1. Decide whether to install NSC in an existing directory or to make a new
one. Here are the considerations:
Existing If you pick a directory that already exists and is
specified in your AUTOEXEC.BAT PATH statement, you will
not need to update your PATH and create a new disk
directory.
New If you want to keep NSC in its own directory, then you
must:
- Create a disk directory.
- Update or add the AUTOEXEC.BAT PATH statement.
- Re-boot the machine before installation.
2. Assuming the disk directory you selected in the preceding step was
C:\TOOLS, use the following command:
INSTALL C:\TOOLS
3. Edit AUTOEXEC.BAT to include a SET statement for the environment variable
DPATH. NSC uses DPATH to locate the installation drive and path. For
example:
SET DPATH=C:\TOOLS
4. To use NSC with Windows Version 3.1 in 386/486 Enhanced mode, follow
these steps:
a) Add NSC to a program group by selecting either the group's icon or
its window.
b) Select the File menu from the Program Manager's action bar.
c) Select the New... item.
d) Select the Program Item option.
e) Select the OK push button.
f) Enter <NSC PATH>\NSC.PIF in the Command Line field of the Program
Item Properties dialog.
g) Select the OK push button.
h) Use the NSC program icon in the selected program group to start NSC.
You have completed the installation.
Table "Installed Files" lists the NSC files installed on your system.
ΓòÉΓòÉΓòÉ 6.2. Installing OS/2 Workstations ΓòÉΓòÉΓòÉ
This section describes the considerations and steps you take to install an NSC
OS/2 Client or Server. The installation process involves running the
INSTALL.CMD file located on your installation diskette. The INSTALL process
will ask you questions about where to place the NSC files. If you are using
OS/2 2.0 or later, you are also asked about adding NSC processes to your
Startup folder.
Before installing, consider the following:
1. Decide whether to install NSC in an existing directory or to make a new
one. Here are the considerations:
Existing If you pick a directory that already exists and is
specified in your CONFIG.SYS PATH, LIBPATH, and DPATH
statements, you will not need to update CONFIG.SYS and
create a new disk directories.
The executable files and NSC.INI files must be placed in
the directory specified by PATH and DPATH. The dynamic
execution library has to be installed in a directory
specified by your LIBPATH.
New If you want to keep NSC in its own directory, then you
must:
- Create at least one disk directory.
- Update the CONFIG.SYS PATH and DPATH statement for the
executables.
- Update LIBPATH for the dynamic execution library.
- Re-boot the machine before installation.
2. Decide whether to install the NSC Server on your workstation. The NSC
Server component should be installed on your workstation only when users
on other NSC Client workstations need to issue NSC requests to your
workstation either to
change a UPM password on your workstation (for example, if your
workstation is an IBM Database Manager server, but not an IBM LAN
Server domain controller or additional server), or
change a password on a host connected to your workstation (but not
connected directly to the NSC Client workstation -- for example, an
APPC gateway workstation).
The NSC Server should not be installed on LAN Servers which handle only
LAN Server logons, logoffs and password change requests from clients
(these requests can be handled by the NSC Client). The NSC Server should
not be installed on additional servers for the purpose of changing
passwords on the additional server (these requests must be directed to
the LAN Server that controls the additional server).
3. If you are using OS/2 2.0 or later, you will be asked whether or not you
want the NSC Retry process and the NSC Server (if this configuration is
requested) added to your desktop's Startup folder.
Choosing to add them will cause them to startup automatically when the
system is restarted. You do not have to add them to your system startup
at installation. They can be added later. See NSCRETRY - Start the NSC
Retry Process and NSCNDMN - Start the NSC Server for further information.
To install the NSC OS/2 Client or Server, use the following command:
INSTALL
The INSTALL command will ask you to select the type of NSC configuration you
want and any necessary information.
Table "Installed Files" lists the NSC files installed on your system.
If you are using OS/2 1.3 and want to create an NSC program group or add
either the NSC Retry Process or NSC Server program to an existing group, you
must create or modify the group manually from the OS/2 1.3 desktop.
ΓòÉΓòÉΓòÉ 6.3. Files Installed ΓòÉΓòÉΓòÉ
Table "Installed Files" lists the NSC files installed on your system based on
the NSC configuration selected. The table headings on the right side indicate
the configuration types for which the files are installed.
NOTE If you do not use APPC Host connections, or you have already
configured your APPC Host connections, the fixed-disk space requirements
for all OS/2 configurations can be reduced by 95K by deleting the sample
Communications Manager configuration file NSCSAMPL.CFG.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Installed Files Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé FILE NAME Γöé DESCRIPTION Γöé OS/2 Γöé OS/2 Γöé DOS Γöé
Γöé Γöé Γöé CLIENTΓöé SERVERΓöé CLIENTΓöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSCREAD.ME Γöé Read before installing Γöé X Γöé X Γöé X Γöé
Γöé Γöé NSC Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSC.INI Γöé Default NSC configuration Γöé X Γöé X Γöé X Γöé
Γöé Γöé file Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSCVERSN.LVLΓöé Version level of NSC Γöé X Γöé X Γöé X Γöé
Γöé Γöé installed Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSCMVS.HIF Γöé Sample host information Γöé X Γöé X Γöé X Γöé
Γöé Γöé file for MVS Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSCOS400.HIFΓöé Sample host information Γöé X Γöé X Γöé X Γöé
Γöé Γöé file for OS/400 Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSCVM.HIF Γöé Sample host information Γöé X Γöé X Γöé X Γöé
Γöé Γöé file for VM Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSCVMOV.HIF Γöé Sample host information Γöé X Γöé X Γöé X Γöé
Γöé Γöé file for VM with Γöé Γöé Γöé Γöé
Γöé Γöé OfficeVision Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSCIIN.HIF Γöé Sample host information Γöé X Γöé X Γöé X Γöé
Γöé Γöé file for the IBM Informa- Γöé Γöé Γöé Γöé
Γöé Γöé tion Network Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSC.EXE Γöé Program providing command Γöé X Γöé Γöé X Γöé
Γöé Γöé line execution as well as Γöé Γöé Γöé Γöé
Γöé Γöé the menu or graphical Γöé Γöé Γöé Γöé
Γöé Γöé interface Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSCPM.EXE Γöé PM graphical interface Γöé X Γöé Γöé Γöé
Γöé Γöé program Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSCHELP.HLP Γöé Online helps for NSCPM Γöé X Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSCUG.INF Γöé Information file for Γöé X Γöé X Γöé Γöé
Γöé Γöé online documentation Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSCAPI.DLL Γöé Dynamic link routines and Γöé X Γöé X Γöé Γöé
Γöé Γöé API Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSRETRY.EXE Γöé NSC Retry Process program Γöé X Γöé X Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSCNDMN.EXE Γöé NSC Server program Γöé Γöé X Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSCSAMPL.CFGΓöé Sample Communications Γöé X Γöé X Γöé Γöé
Γöé Γöé Manager configuration Γöé Γöé Γöé Γöé
Γöé Γöé file for APPC Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSCRSON.EXE Γöé Stub for obsolete command Γöé X Γöé Γöé X Γöé
Γöé Γöé line / menu program (it Γöé Γöé Γöé Γöé
Γöé Γöé executes NSC.EXE) Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSCRSOFF.EXEΓöé Stub for obsolete command Γöé X Γöé Γöé X Γöé
Γöé Γöé line / menu program (it Γöé Γöé Γöé Γöé
Γöé Γöé executes NSC.EXE) Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSCRSIGN.LIBΓöé Toolkit library con- Γöé X Γöé Γöé Γöé
Γöé Γöé taining the NSCRSIGN API Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSCRSIGN.H Γöé Toolkit 'C' header file Γöé X Γöé Γöé Γöé
Γöé Γöé for the NSCRSIGN API Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSCNET.EXE Γöé LAN Server and User Exit Γöé Γöé Γöé X Γöé
Γöé Γöé interface program Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSC.PIF Γöé Windows Program Informa- Γöé Γöé Γöé X Γöé
Γöé Γöé tion File Γöé Γöé Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 7. Configuring Network SignON Coordinator/2 ΓòÉΓòÉΓòÉ
This chapter contains information on how to configure Network SignON
Coordinator/2.
Configuration information for NSC is stored in a file named "NSC.INI". NSC.INI
file defines the defaults for NSC operation and defines where you want to
signon, change passwords, and signoff. This file is created when you install
NSC. You can use any ASCII file editor to modify the file to meet your
configuration requirements. A copy of the file must either reside in the
current directory or in a directory specified in the DPATH when executing NSC
(or NSCRSON, NSCRSOFF, or NSCPM) or calling the NSCRSIGN API.
NSC is usually used in one or more of the following environments. Determine
which of these environments most closely matches yours, then see The NSC
Configuration File. After reviewing the definitions in The NSC Configuration
File, read Special Considerations.
Host Emulation Workstations using host terminal emulation to multiple
host systems (MVS, VM, or OS/400). NSC coordinates
password changes for all configured host systems. To
configure NSC for this environment, you need the following
definition:
HOST,EMULATOR,NAME=...
This definition is described in HOST. You should also read
Configuring EMULATOR Connections for a description of host
information files along with some samples. Follow the
directions for using the sample host information file for
your host system.
LAN Servers Workstations using multiple LAN Servers. NSC coordinates
password changes for all configured LAN Servers. To
configure NSC for this environment, you need the following
definition:
LANSERVER,...,NAME=...
This definition is described in LANSERVER.
OS/2 Database Manager DOS and OS/2 workstations using one or more OS/2
Database Manager Servers. NSC coordinates password changes
for users at the configured NSC Servers running on the
Database Server workstations. To configure NSC for this
environment, you need the following definitions:
NODE,NAME=...
SERVER,NAME=...
LOCAL
These definitions are described in NODE, SERVER and LOCAL.
Be sure to read the special considerations in OS/2
Database Requester Considerations.
MVS/ESA - APPC NSC Clients that have User IDs on MVS/ESA. APPC provides
faster and more reliable password changes than the Host
Emulation capability. NSC coordinates password changes for
all configured MVS/ESA systems. To configure NSC for this
environment, you need the following definitions:
SERVER,NAME=...
HOST,APPC,NAME=...
These definitions are described in SERVER and HOST. See
Configuring APPC for a description of how to configure
Communications Manager and suggestions for the host system
software.
If you plan to use an NSC Server on your LAN, see Configuring NETBIOS for a
description of the NETBIOS resource requirements for NSC, along with
information on how to configure these resources.
ΓòÉΓòÉΓòÉ 7.1. The NSC Configuration File ΓòÉΓòÉΓòÉ
Each line of the NSC configuration file defines a default for NSC operation or
defines a location where you want to signon or change a password. Any line
beginning with an asterisk or blank (space) character is considered a comment
and ignored. Any text following the first blank character on a line is
considered comment text and ignored. Although the definitions are shown in
upper case, you may enter them in upper, lower or mixed case.
The following sections explain how you configure Network SignON Coordinator/2.
Changing the Defaults explains the NSC operation defaults.
Defining Locations explains how you define the signon or change password
locations.
Other Configuration Definitions explains how you define user exits that
can be associated with your location definitions, or how to include
configuration definitions stored on an NSC Server or in a user-specific
configuration file.
Special Considerations contains some special considerations for accessing
configuration files on NSC Servers, supporting multiple users on the same
machine and OS/2 Clients that are also OS/2 Database Requesters.
Configuration File Example contains a complete example configuration
file.
ΓòÉΓòÉΓòÉ 7.1.1. Changing the Defaults ΓòÉΓòÉΓòÉ
You define how NSC interacts with an end user and how NSC validates user input.
The order of the definitions does not matter. If NSC.INI contains duplicate
definitions, the one nearest the bottom takes effect. The definition defaults
you can change are:
To specify Definition
------------- -------------
Error beeps BEEP
Character Set CHARSET
Exit warning CONFIRMEXIT
Debugging DEBUG
Minimum Password Length MINPWLEN
Maximum Password Length MAXPWLEN
Minimum User ID Length MINUIDLEN
Maximum User ID Length MAXUIDLEN
Password retention SAVEPW
Shortcut to signon SIGNON
Default User ID USERID
ΓòÉΓòÉΓòÉ 7.1.1.1. BEEP ΓòÉΓòÉΓòÉ
Use the BEEP definition to turn off the beeps NSC sounds when error messages
are displayed or the user presses invalid keys.
Syntax BEEP={ON|OFF}
Values Choose either ON or OFF.
Default ON
Example BEEP=OFF
NSC will not beep when displaying error messages or invalid keys
are pressed.
ΓòÉΓòÉΓòÉ 7.1.1.2. CHARSET ΓòÉΓòÉΓòÉ
Use the CHARSET definition to specify the characters (other than alphanumerics)
that are valid in passwords.
Syntax CHARSET=characters
Values characters is a string of non-blank characters. You cannot
specify the alphanumeric characters A through Z, a through z, or
0 through 9. Specify only graphic ASCII characters other than a
space (i.e., 0x21 through 0x7E and 0x80 through 0xFE).
Do not specify lower case extended ASCII characters, because
they will not be converted to upper case and may not give the
desired result when passed to UPM or LAN Server. You can specify
up to 159 characters. No check is made for duplicate characters.
Default The default ignore this CHARSET definition.
Example CHARSET=с
This restricts the character set for passwords to just
alphanumeric characters and с.
ΓòÉΓòÉΓòÉ 7.1.1.3. CONFIRMEXIT ΓòÉΓòÉΓòÉ
Use the CONFIRMEXIT definition to display a warning message before NSC exits
(when closing the main window).
Syntax CONFIRMEXIT={ON|OFF}
Values Choose either ON or OFF.
Default OFF
Example CONFIRMEXIT=ON
When the user selects Close or Exit, a warning message is
displayed before NSC exits. If OK is selected, NSC exits. If
NSC was started from a folder and is active when Shutdown is
selected from the desktop, the warning message will be displayed
when the system attempts to close NSC. The user may then cancel
Shutdown.
ΓòÉΓòÉΓòÉ 7.1.1.4. DEBUG ΓòÉΓòÉΓòÉ
Use the DEBUG definition to have NSC record additional LOG information when a
problem occurs (user request processing is slower when DEBUG is defined). See
Problem Determination, for further information.
Syntax DEBUG
Values None
Default None
Example DEBUG
NSC will log non-error information as well as error information.
ΓòÉΓòÉΓòÉ 7.1.1.5. MINPWLEN ΓòÉΓòÉΓòÉ
Use the MINPWLEN definition to set the minimum password length. If the user
enters fewer characters than this in the menu for the current or new password,
an error message is displayed.
Syntax MINPWLEN={1..14}
Values Pick a value between 1 and 14.
Default 5
Example MINPWLEN=6
NSC will check that the password contains at least 6 characters.
ΓòÉΓòÉΓòÉ 7.1.1.6. MAXPWLEN ΓòÉΓòÉΓòÉ
Use the MAXPWLEN definition to set the maximum password length. If the user
enters more characters than this in the menu for the current or new password,
an error message is displayed.
Syntax MAXPWLEN={1..14}
Values Pick a value between 1 and 14.
Default 8
Example MAXPWLEN=7
NSC will check that the password contains no more than 7
characters.
ΓòÉΓòÉΓòÉ 7.1.1.7. MINUIDLEN ΓòÉΓòÉΓòÉ
Use the MINUIDLEN definition to set the minimum User ID length. If the user
enters fewer characters than this in the menu for a User ID, an error message
is displayed.
Syntax MINUIDLEN={1..8}
Values Pick a value between 1 and 8.
Default 4
Example MINUIDLEN=5
NSC will check that the User ID contains at least 5 characters.
ΓòÉΓòÉΓòÉ 7.1.1.8. MAXUIDLEN ΓòÉΓòÉΓòÉ
Use the MAXUIDLEN definition to set the maximum User ID length. If the user
enters more characters than this in the menu for a User ID, an error message is
displayed.
If you use a GETDEFS definition (see GETDEFS), do not specify a MAXUIDLEN
greater than 8 since the User ID is used to construct the filename containing
the additional configuration definitions. If you have a User ID greater than 8
and want to use a GETDEFS, you must pick a pseudo User ID of 8 or fewer
characters and specify the larger User ID on the location definition(s) where
it is applicable.
Syntax MAXUIDLEN={1..47}
Values Pick a value between 1 and 47.
Default 8
Example MAXUIDLEN=7
NSC will check that the User ID contains no more than 7
characters.
ΓòÉΓòÉΓòÉ 7.1.1.9. SAVEPW ΓòÉΓòÉΓòÉ
Use the SAVEPW definition to have NSC remember the end user's password once it
has been entered. This allows you to signon to a selected location without
having to renter your password. If you select the Default Signons or Change
Password actions, the previously entered password is used.
If you change your password, the new password becomes the saved password if the
change is successful everywhere. If the change fails anywhere, the saved
password is cleared and you will have to reenter it the next time you select a
signon action.
The password is not stored on disk, but kept hidden and masked in memory. When
NSC is closed, the saved password is no longer available.
Syntax SAVEPW={ON|OFF}
Values Choose either ON or OFF.
Default OFF
Example SAVEPW=ON
Once entered, the password is saved and reused.
ΓòÉΓòÉΓòÉ 7.1.1.10. SIGNON ΓòÉΓòÉΓòÉ
When you start the NSC graphical interface (see Graphical Interface), you can
have NSC automatically initiate the dialog to perform a Signon to Default
Systems by using the SIGNON definition.
Syntax SIGNON
Values None
Default None
Example SIGNON
NSC starts a signon to the user's default locations. This is
equivalent to using the mouse to select Actions, then selecting
Signon, then selecting Default Systems.
ΓòÉΓòÉΓòÉ 7.1.1.11. USERID ΓòÉΓòÉΓòÉ
Use the USERID definition to specify your default User ID. This User ID can be
overridden by a User ID entered as a command line parameter. The default User
ID is used for all location definitions that do not explicitly specify a USERID
parameter.
The most appropriate use of the USERID definition is for a workstation that has
a single user. In this situation, it eliminates the user having to enter their
User ID every time they start NSC.
USERID should not be specified on workstations used by multiple users or where
a user moves between workstations. In this case, use a GETDEFS definition (see
GETDEFS) and let NSC prompt the user at startup for their User ID.
Syntax USERID=userid
Values The userid is a string of characters. It should not include any
character that is not part of the Character Set you defined (see
CHARSET). Lower case alphabetic characters are converted to
upper case, and the string is then displayed in the NSC menus as
the initial value for User ID.
Default None
Example USERID=SMITH
The User ID "SMITH" will be the default User ID.
ΓòÉΓòÉΓòÉ 7.1.2. Defining Locations ΓòÉΓòÉΓòÉ
You must define where you want to signon or change passwords. In the
definitions that follow, the term "request" means a signon, signoff, or change
password action. The definitions to do this are:
LOCAL
NODE
LANSERVER
HOST
SERVER
The order of these definitions is very important because:
NSC processes requests in the order that you list the definitions.
Each definition is processed without checking for duplicate definitions.
When a request is duplicated for the same User ID at the same location,
the second request usually fails.
The SERVER definitions determine where requests are processed.
All definitions for requests to be processed at the local workstation
must precede the first SERVER definition. Definitions that follow a
SERVER definition are sent to that NSC Server for request processing.
For example, suppose you have an OS/2 workstation in your office and you also
have a UPM account on another workstation down the hall. The two workstations
are connected by a LAN as in Figure "Two Workstations".
Two Workstations
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Workstation Γöé Γöé Workstation Γöé
Γöé in your Γöé Γöé down the Γöé
Γöé office Γöé Γöé hall Γöé
Γöé Γöé Γöé Γöé
Γöé Γöé Γöé Γöé
Γöé Γöé Γöé Γöé
Γöé OS/2 Γöé Γöé OS/2 Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Γöé Γöé
Γöé LAN Γöé
ΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇ
NSC changes your passwords on both machines from your workstation. Figure "NSC
Client/Server" shows the necessary relationship and configuration definitions
at the bottom.
NSC Client/Server
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NSC Client Γöé Γöé NSC Server Γöé
Γöé Γöé Γöé SERVE1 Γöé
Γöé Γöé Γöé Γöé
Γöé - Local Γöé Γöé - Local Γöé
Γöé Γöé Γöé Γöé
Γöé OS/2 Γöé Γöé OS/2 Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
NSC configuration file
USERID=ELVIS
LOCAL,ON
SERVER,NAME=SERVE1
LOCAL
The NSC configuration file located at your workstation should contain two
LOCAL signon definitions. One is processed on your workstation and the other
at the workstation down the hall (SERVE1) whenever you change your password.
In this example, the User ID on both workstations is ELVIS.
Your configuration file may contain up to 255 location definitions. A location
definition cannot be made in the same configuration file as a GETDEFS
definition. The location definitions must be made in the referenced
configuration file. You can specify the definitions below:
To specify Definition
------------- -------------
UPM Local signon LOCAL
UPM Node signon NODE
LAN Server signon LANSERVER
NSC Server machine HOST
Host signon SERVER
ΓòÉΓòÉΓòÉ 7.1.2.1. LOCAL ΓòÉΓòÉΓòÉ
Use the LOCAL definition to change OS/2 UPM passwords and, optionally, to logon
to the local UPM. You can specify multiple LOCAL definitions.
A DOS Client cannot process LOCAL definitions, but an NSC Server can process
them for the DOS Client.
When users move between workstations or a workstation has several users, you
should avoid defining a UPM account for each user on each OS/2 workstation. Not
only does this require a lot of UPM configuration work, but it also creates a
situation where it is impossible to keep a single user's password up to date on
every workstation. You can use a NODE definition (see NODE) instead of a LOCAL.
The User ID associated with a node logon does not require a UPM account
definition. For more information on this topic, see Special Considerations.
Syntax
<ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ<
>>ΓöÇΓöÇLOCALΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇ><
ΓööΓöÇΓö¼ΓöÇ,ONΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÿ
Γö£ΓöÇ,USERID=useridΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓööΓöÇΓö¼ΓöÇ,EXIT=filenameΓöÇΓö¼ΓöÇΓöÿ
ΓööΓöÇ,EXITID=exitidΓöÇΓöÿ
Parameters:
ON Causes Network SignON Coordinator/2 to perform a
local logon as well as synchronize password changes
with UPM.
The ON parameter is valid on only an OS/2 Client. You
can specify the ON parameter for only one LOCAL
definition, because a workstation session can have
only one active local logon.
The ON parameter cannot be specified in a LOCAL
definition that follows a SERVER definition.
USERID Specifies the User ID to be used for the request.
Specify this parameter when the user's account on the
local workstation is under a different User ID than
that provided to NSC (from the USERID configuration
definition, from the command line, from the API, or
from the User ID dialog). Lower case alphabetic
characters are converted to upper case. This
parameter also allows a user to synchronize passwords
for multiple UPM accounts and selectively signon
different User IDs for a local logon.
EXITID Identifies an EXIT definition defining a command file
or program to be executed after the request has been
processed. See EXIT for a description of the EXIT
definition. See Exit Routines for information on how
to define exit routines.
EXIT This parameter is equivalent to "EXITID=exitid" where
the EXIT definition is specified as
"EXIT,ID=exitid,NAME=filename" (all other options are
defaulted).
Example
In the following example, the user has three different local User
IDs defined in UPM on the client workstation; two of these User
IDs are also defined in UPM on the NSC Server "DBSERVER". When
requested to signon, NSC performs a local logon for the User ID
"PDQUEUE" on the client workstation. When requested to change
passwords, NSC performs a password change for each of the three
User IDs on the client workstation and the two User IDs on the
NSC Server. After processing each request for User ID "PDQUEUE",
the user command file "MYEXIT.CMD" is executed in the background.
In the OS/2 graphical interface, the user can signon using either
of the other two User IDs defined in UPM on the client
workstation.
USERID=PDQUEUE
LOCAL,ON,EXIT=D:\TOOLS\MYEXIT.CMD
LOCAL,USERID=DBADM
LOCAL,USERID=SYSADM
SERVER,NAME=DBSERVER
LOCAL
LOCAL,USERID=DBADM
ΓòÉΓòÉΓòÉ 7.1.2.2. NODE ΓòÉΓòÉΓòÉ
Use the NODE definition to perform a node logon to your local UPM. Node signons
do not perform any User ID or password validation; they are always successful.
Node logons create User ID and password information used by OS/2 Database
Manager, APPC applications, and the Communications Manager 5250 Emulator. You
can specify multiple NODE definitions to be processed locally, but NODE
definitions cannot follow a SERVER definition.
NSC does no signon processing for DOS Clients since there is no UPM on DOS. A
NODE definition on a DOS Client can be used to execute an exit routine (for
example, to perform a logon to the DOS Database Requester). They can also be
used for this purpose on OS/2 because of the low overhead of a node logon
(except on EE 1.3, which requires that a new process be started).
A 5250 node logon can be automated by using a NODE definition with an exit
routine which starts the Communications Manager.
Syntax
<ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ<
>>ΓöÇΓöÇNODEΓöÇΓöÇ,NAME=nameΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇ><
ΓööΓöÇΓö¼ΓöÇ,ONΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÿ
Γö£ΓöÇ,USERID=useridΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓööΓöÇΓö¼ΓöÇ,EXIT=filenameΓöÇΓö¼ΓöÇΓöÿ
ΓööΓöÇ,EXITID=exitidΓöÇΓöÿ
Parameters:
NAME name is the Server Node Name configured in the OS/2
Database Manager Workstation Directory for a database
server, or the PLU Name for an APPC application.
Lower case alphabetic characters in the name will be
converted to upper case.
ON Causes NSC to perform a node logon on an OS/2 Client.
You can specify the ON parameter for multiple NODE
definitions. You should only specify it for one NODE
definition with the same NAME. If you specify the ON
parameter on more than one NODE definition with the
same NAME, signon will fail for all but the first of
the definitions because you are already signed on.
USERID Specifies the User ID to be used for the request. For
example, for OS/2 Database Requesters, specify this
parameter when the User ID for the remote database
connection is different from the default User ID
provided to NSC (from the USERID configuration
definition, from the command line, from the API, or
from the User ID dialog). Lower case alphabetic
characters are converted to upper case. This
parameter also allows a user to selectively signon
different User IDs for a node logon.
EXITID Identifies an EXIT definition defining a command file
or program to be executed after the request has been
processed. See EXIT for a description of the EXIT
definition. See Exit Routines for information on how
to define exit routines.
If you have more than one NODE definition for the
same node name (i.e. for multiple User IDs), you
should specify the same exit routine for each of
these definitions. For a password change, only the
exit routine for the last of these definitions is
executed, and only if there is a current node logon
for the node (the User ID will be the currently
logged on User ID).
EXIT This parameter is equivalent to "EXITID=exitid" where
the EXIT definition is specified as
"EXIT,ID=exitid,NAME=filename" (all other options are
defaulted).
Example
In the following example, the user has two different User IDs
defined in UPM on the NSC Server "DBSERVER". These User IDs are
not necessarily defined in UPM on the client workstation. When
requested to signon, NSC performs a node logon for the User ID
"PDQUEUE" on the client workstation. When requested to change
passwords, NSC performs a password change for each of the two
User IDs on the NSC Server, and performs a new node logon for the
currently logged on User ID on the client workstation using the
new password. After processing each request, the user command
file "MYEXIT.CMD" is executed in the background (it will only be
executed once for a password change). For DOS Clients, this
command file could handle the logon for the DOS Database
Requester (see the example exit routine in Logging on to a DOS
Database Client). In the OS/2 graphical interface, the user can
choose to signon the User ID "DBADM", replacing the node logon
for "PDQUEUE".
USERID=PDQUEUE
NODE,ON,EXIT=D:\TOOLS\MYEXIT.CMD
NODE,USERID=DBADM,EXIT=D:\TOOLS\MYEXIT.CMD
SERVER,NAME=DBSERVER
LOCAL
LOCAL,USERID=DBADM
ΓòÉΓòÉΓòÉ 7.1.2.3. LANSERVER ΓòÉΓòÉΓòÉ
Use the LANSERVER definition to change LAN Server passwords and, optionally, to
logon to the LAN Server. You can specify multiple LANSERVER definitions to be
processed locally, but LANSERVER definitions cannot follow a SERVER definition.
Syntax
<ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ<
>>ΓöÇΓöÇLANSERVERΓöÇΓöÇ,ΓöÇΓö¼ΓöÇIBMΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇ,NAME=nameΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇ><
ΓööΓöÇNOVELLΓöÇΓöÿ ΓööΓöÇΓö¼ΓöÇ,ONΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÿ
Γö£ΓöÇ,USERID=useridΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓööΓöÇΓö¼ΓöÇ,EXIT=filenameΓöÇΓö¼ΓöÇΓöÿ
ΓööΓöÇ,EXITID=exitidΓöÇΓöÿ
Parameters:
IBM Identifies this as an IBM LAN Server.
Because a workstation can have only one active IBM
LAN Server logon, you can specify the ON parameter
for only one IBM LANSERVER definition.
If you are configuring for a DOS IBM LAN Requester,
specify the /NMS:n parameter (where n is greater than
or equal to 1) in its DOSLAN.INI file.
NOVELL Identifies this as a NetWare file server.
If you specify the ON parameter, NSC uses interfaces
provided by NetWare to do a LOGIN to the file server.
However, NetWare does not execute the user login
script. You can achieve some of the same results
using an exit routine that executes NetWare MAP
commands. OS/2 NetWare Drive Mapping and DOS NetWare
Drive Mapping are examples of exit routines that use
the MAP command.
NAME name is the IBM LAN Server domain or the NetWare file
server's name. Lower case alphabetic characters in
the name will be converted to upper case.
ON Causes NSC to perform a LAN Server logon and to
synchronize password changes with the LAN Server.
USERID Specifies the User ID to be used for the request.
Specify this parameter when the user's User ID for
the LAN Server is different from the User ID provided
to NSC (from the USERID configuration definition,
from the command line, from the API, or from the User
ID dialog). Lower case alphabetic characters are
converted to upper case. This parameter also allows a
user to synchronize passwords for multiple accounts
on the same LAN Server.
EXITID Identifies an EXIT definition defining a command file
or program to be executed after the request has been
processed. For example, an exit routine could check
for a successful IBM LAN Server logon and then
perform a NET USE for an IBM LAN Server resource. See
EXIT for a description of the EXIT definition. See
Exit Routines for information on how to define exit
routines.
EXIT This parameter is equivalent to "EXITID=exitid" where
the EXIT definition is specified as
"EXIT,ID=exitid,NAME=filename" (all other options are
defaulted).
Example
In the following example, the user has User IDs "PDQUEUE" and
"SYSADM" defined on the IBM LAN Server domain "LANSYS04", and
User ID "PDQUEUE" defined on the IBM LAN Server domain
"LANSYS07". When requested to signon, NSC performs a logon for
the User ID "PDQUEUE" to domain "LANSYS04". When requested to
change passwords, NSC performs a password change for "PDQUEUE"
and "SYSADM" on domain "LANSYS04" and "PDQUEUE" on domain
"LANSYS07". In the OS/2 graphical interface, the user can choose
to signon to the domain "LANSYS04" using the User ID "SYSADM", or
domain "LANSYS07" using the User ID "PDQUEUE". In either case, a
domain logoff is first performed.
LANSERVER,IBM,NAME=LANSYS04,ON
LANSERVER,IBM,NAME=LANSYS04,USERID=SYSADM
LANSERVER,IBM,NAME=LANSYS07
ΓòÉΓòÉΓòÉ 7.1.2.4. HOST ΓòÉΓòÉΓòÉ
Use the HOST definition to change host passwords and, optionally, logon to the
host. You can specify multiple HOST definitions.
Syntax
>>ΓöÇΓöÇHOSTΓöÇΓöÇΓö¼ΓöÇ,APPCΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇ,NAME=hostnameΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
Γöé <ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ< Γöé
ΓööΓöÇ,EMULATORΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÿ
ΓööΓöÇΓö¼ΓöÇ,HIF=filenameΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÿ
ΓööΓöÇ,Vn=variableΓöÇtextΓöÇΓöÿ
<ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ<
>ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇ><
ΓööΓöÇΓö¼ΓöÇ,ONΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÿ
Γö£ΓöÇ,USERID=useridΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓööΓöÇΓö¼ΓöÇ,EXIT=filenameΓöÇΓö¼ΓöÇΓöÿ
ΓööΓöÇ,EXITID=exitidΓöÇΓöÿ
Parameters:
APPC Specifies that APPC is to be used to make the host
connection. APPC and EMULATOR are mutually exclusive.
If the workstation has a host emulator session, use
the emulator connection to avoid additional
communications configuration work. APPC provides a
faster, more reliable method of changing passwords on
a host system than does a host emulator session.
However, not all host systems provide support for NSC
APPC connections.
EMULATOR Specifies that a host emulator session is to be used
to make the host connection. APPC and EMULATOR are
mutually exclusive.
EMULATOR can be used with either 3270 or 5250 host
emulator session. If a 5250 session on OS/2 is used,
the emulator prompts the user for a node logon when
that session is started. This node logon can be
automated through the use of the EXIT parameter. See
Exit Routines for an example illustrating how this
can be accomplished.
NOTE: If a 5250 session is used on an NSC Server, the
node logon must be done manually.
HIF Identifies the host information file for the host
emulator session (see Configuring EMULATOR
Connections for a description of host information
files). A complete path (up to 80 characters) may be
specified if the host information file is not in the
same directory as the NSC configuration file. If a
file extension is not specified, the default is
".INI".
Use this parameter when you have multiple User IDs at
the same host location. Each definition should
specify the same host information file.
Vn Specifies an HIF Variable. Up to 10 HIF Variables may
be defined (V0 through V9). The HIF Variable
parameters for a single HOST definition are limited
to a total of 80 characters. An HIF Variable defines
a string (variable-text) that can replace the HIF
Variable in the host information file. If the
variable-text string is enclosed in double quotes,
the string can contain embedded spaces and commas.
Two successive double quotes ("") represent a single
double quote character.
Using an HIF Variable can reduce the number of host
information files needed. For example, you may have
two MVS systems that are the same but, their signon
screens have a different system name (e.g., "TSO1"
versus "TSO2"). You can use an HIF Variable to
substitute values into a search string. Another
example is to use the HIF Variable to specify the
host emulator session.
HIF variables contained within a variable-text string
are recursively replaced by their corresponding
variable-text strings. If the User ID is "JUDY" and
you define the following HIF variables:
V1=Good,V2=morning,V3="@V1 @V2 @u"
then all occurances of @V3 in the HIF are replaced
with:
Good morning JUDY
If you specify HIF variables within a variable-text
string, do not make a circular definitions since they
cannot be resolved. The following definitions are
circular and will cause and endless series of
replacements.
V1=@V1
V1=@V2,V2=@V1
NAME NSC uses the hostname to locate further definitions
needed to make the host connection.
For APPC, hostname is the name of the Partner LU
profile in the APPC configuration (see Personal
Computer Definitions describes these profiles).
For EMULATOR, choose a value for hostname that
identifies the host. This name is used in messages
and in the graphical interface. Use the same hostname
for different User IDs at the same location (these
definitions should also specify the same HIF
parameter and use the same host emulator session
ids). NSC uses the hostname in the graphical
interface to combine all User IDs for the same
location and provide a list of valid signon requests.
If you want to signon two different User IDs to the
same host location at the same time, you must specify
a different hostname for the second User ID and use a
different host emulator session id.
If the HIF parameter is not specified, hostname
specifies the name of the host information file used
for the emulator session. In this case, a file
extension of ".INI" is appended to hostname to get
the filename, and the host information file must be
in the same directory as the NSC configuration file.
ON For host emulator sessions, the ON parameter causes
NSC to perform a host logon and to synchronize
password changes with the host.
For APPC connections, the ON parameter causes NSC to
verify the User ID and password at the host and
notify the user of the host signon status (valid,
invalid, or password expired) at signon.
The ON parameter cannot be specified in a HOST
EMULATOR definition that follows a SERVER definition.
USERID Specifies the User ID to be used for the request.
Specify this parameter when the user's host ID is
different from the User ID provided to NSC (from the
USERID configuration definition, from the command
line, from the API, or from the User ID dialog).
Lower case alphabetic characters are converted to
upper case. This parameter also allows a user to
synchronize passwords for multiple host accounts.
EXITID Identifies an EXIT definition defining a command file
or program to be executed after the request has been
processed. See EXIT for a description of the EXIT
definition. See Exit Routines for information on how
to define exit routines.
EXIT This parameter is equivalent to "EXITID=exitid" where
the EXIT definition is specified as
"EXIT,ID=exitid,NAME=filename" (all other options are
defaulted).
Example
In the following example, the user has defined three different
User IDs on two different host systems. The sample host
information file for VM is used, taking advantage of HIF
variables to assign host sessions and to supply search string
text. HIF variable V1 is used to select the host session. HIF
variable V2 is substitution text used in a host information file
search string. NSC uses "VM1" or "VM2" to identify the host
system in its messages.
When requested to signon, NSC performs a logon for the User ID
"PDQUEUE" to VM1 (using either session A or C) and VM2 (using
session B). When requested to change passwords, NSC performs a
password change for User ID "PDQUEUE" on VM1 and VM2, and a
password change for User ID "SYSADM" on VM1. If "PDQUEUE" is
signed on to VM1 session A, the password change for "SYSADM" will
be done using host emulator session C; otherwise, it will use
session A. The same is true for User ID "PDQUEUE" if "SYSADM" is
signed on to session A. In the OS/2 graphical interface, the user
can choose to signon to VM1 using the User ID "SYSADM"; if signed
on as "PDQUEUE", the user will first be signed off and then
signed on as "SYSADM".
USERID=PDQUEUE
HOST,EMULATOR,NAME=VM1,HIF=d:\nsc\nscvm.hif,V1="A-C",V2=VM1,ON
HOST,EMULATOR,NAME=VM1,HIF=d:\nsc\nscvm.hif,V1="A-C",V2=VM1,USERID=SYSADM
HOST,EMULATOR,NAME=VM2,HIF=d:\nsc\nscvm.hif,V1=B,V2=VM2,ON
ΓòÉΓòÉΓòÉ 7.1.2.5. SERVER ΓòÉΓòÉΓòÉ
Use the SERVER definition to specify an NSC Server that will process the
definitions that follow it. You can specify multiple SERVER definitions.
NSC Server processing is initiated by the NSC Client when it processes
definitions in the Client NSC configuration. The NSC Server processes only host
and local definitions. The main difference between the NSC Client and NSC
Server processing is that a definition passed to the NSC Server cannot request
a signon operation. At signon, the NSC Server processes only password change
requests and APPC password verification requests. Another difference is that
Exit Routines are driven only in the NSC Client. The following sequence takes
place:
1. NSC Client displays the in-progress message for the definition.
2. NSC Client sends the definition to the NSC Server.
3. NSC Server processes the definition.
4. NSC Server sends results to the NSC Client.
5. NSC Client displays the completion message for the definition.
6. NSC Client drives the Exit Routine.
Consider using an NSC Server when you use host APPC connections and make the
APPC connection definition at the Server. This reduces the configuration work
at the workstation (Communications Manager and NSC both) and at the host
computer site.
Syntax
>>ΓöÇΓöÇSERVERΓöÇΓöÇ,NAME=machineΓöÇnameΓöÇΓöÇ><
Parameters:
NAME The machine-name is the name assigned to an NSC
Server. NSCNDMN - Start the NSC Server explains how
the server is named. Lower case alphabetic characters
in the machine name will be converted to upper case.
Example
In the following example, the user has defined the User ID
"PDQUEUE" in UPM on the NSC Server "MAC2", an account for
"PDQUEUE" on the MVS Host "MVSSYS01", and the User ID "DBADM" in
UPM on the NSC Server "DBM03". When requested to signon, NSC
connects to the NSC Server "DBM03" and validates the User ID
"PDQUEUE" and password via APPC at the MVS Host "MVSSYS01". When
requested to change passwords, NSC does the following:
1. Connects to the NSC Server "MAC2".
2. Performs a password change for User ID "PDQUEUE" on the NSC
Server "MAC2".
3. Executes the exit routine "MYEXIT.CMD" on the client
workstation.
4. Connects to the NSC Server "DBM03".
5. Performs a password change via APPC at the MVS Host
"MVSSYS01" for User ID "PDQUEUE".
6. Performs a password change for the User ID "DBADM" on the
NSC Server "DBM03".
USERID=PDQUEUE
SERVER,NAME=MAC2
LOCAL,EXIT=MYEXIT.CMD
SERVER,NAME=DBM03
HOST,APPC,NAME=MVSSYS01,ON
LOCAL,USERID=DBADM
ΓòÉΓòÉΓòÉ 7.1.3. Other Configuration Definitions ΓòÉΓòÉΓòÉ
EXIT explains how you define user exits that can be associated with your
location definitions.
GETDEFS explains how to include configuration definitions stored on an
NSC Server or in a user-specific configuration file.
ΓòÉΓòÉΓòÉ 7.1.3.1. EXIT ΓòÉΓòÉΓòÉ
You can define user exit routines by identifying the command file or program to
be executed after a request has been processed. User exit definitions can be
referenced by one or more location definitions. Up to 40 EXIT definitions may
be defined. See Exit Routines for more information on exit routines and the
parameters passed to the exit routines.
For example, an exit routine could check for a successful IBM LAN Server logon
and then perform a NET USE for an IBM LAN Server resource. In OS/2, exit
routines that allow user interaction may be started.
Syntax
<ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ<
>>ΓöÇΓöÇEXITΓöÇΓöÇ,ID=exitidΓöÇΓöÇ,NAME=filenameΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇ><
ΓööΓöÇΓö¼ΓöÇΓö¼ΓöÇ,BGΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÿ
Γöé ΓööΓöÇ,FGΓöÇΓöÿ Γöé
Γö£ΓöÇΓö¼ΓöÇ,WAITΓöÇΓöÇΓöÇΓö¼ΓöÇΓöñ
Γöé ΓööΓöÇ,NOWAITΓöÇΓöÿ Γöé
Γö£ΓöÇΓö¼ΓöÇ,NORCΓöÇΓö¼ΓöÇΓöÇΓöÇΓöñ
Γöé ΓööΓöÇ,RCΓöÇΓöÇΓöÇΓöÿ Γöé
ΓööΓöÇΓö¼ΓöÇ,NOMSGSΓöÇΓö¼ΓöÇΓöÿ
ΓööΓöÇ,MSGSΓöÇΓöÇΓöÇΓöÿ
Parameters:
ID Identifies this EXIT definition. The exitid must be
an integer from 1 to 40. This ID may be referenced by
one or more location definitions to associate the
exit routine defined by this EXIT definition with a
specific location.
NAME Identifies the user exit command file or executable
program. A complete path (up to 80 characters) may be
specified if the command file or executable program
is not in the PATH.
BG Specifies that the exit routine will be executed in
the background (this is the default).
FG Specifies that the exit routine will be executed in
the foreground. If this option is not specified, the
exit routine will be executed in the background. This
parameter is ignored in DOS.
WAIT Specifies that NSC should wait until the exit routine
terminates before processing the next location
definition (this is the default).
NOWAIT Specifies that NSC should continue processing the
next location definition without waiting for the exit
routine to finish. If this option is not specified,
NSC waits until the exit routine finishes before
processing the next location definition. This
parameter is ignored in DOS. Do not specify this
parameter if the exit routine returns an error code
and you want details on the result of the exit
routine.
NORC Specifies that the exit routine does not set the
ERRORLEVEL or return an error code (this is the
default).
RC Specifies that the exit routine sets the ERRORLEVEL
or returns a return code to indicate its success or
failure. See Exit Routines for a description of
return codes. If this option is not specified, it is
assumed that the exit routine does not set the
ERRORLEVEL or return a return code. If the NOWAIT
parameter is specified, this parameter is ignored.
NOMSGS Specifies that in-progress and successful completion
messages should not be displayed when the user exit
is executed (this is the default). Error messages for
the user exit will always be displayed.
MSGS Specifies that in-progress and successful completion
messages should be displayed when the user exit is
executed. If this option is not specified,
in-progress and successful completion messages will
not be displayed.
Example
The following example causes NSC to execute the exit routine
"MYEXIT.CMD" after processing a request for the Local User ID. In
this example, the exit routine is assumed to be an OS/2 REXX
command file requiring user interaction and returning a return
code, so the user exit is defined so that NSC will start the exit
routine in a foreground session and wait for it to terminate
before continuing. When the exit routine terminates, if it
returns an error, NSC will display an appropriate error message
based on the return code.
EXIT,ID=1,NAME=D:\TOOLS\MYEXIT.CMD,FG,WAIT,RC,NOMSGS
LOCAL,ON,EXITID=1
ΓòÉΓòÉΓòÉ 7.1.3.2. GETDEFS ΓòÉΓòÉΓòÉ
You can combine configuration definitions from another file with the
definitions in the Client NSC.INI file using the GETDEFS definition.
Definitions can be included from a local file or from an NSC Server, allowing
centralized configuration management. The included file must be in the same
directory as the NSC configuration file. Included definitions can be either
user-specific or group-specific:
Included files can be identified by User IDs. A file extension of "NSC"
is appended to the default User ID to get the filename for the included
definitions.
On an NSC Server, included files can be identified by a Group ID. To
group User IDs together, create a flat ASCII file called "NSCGROUP.TAB"
in the same directory as the NSC configuration file on the NSC Server.
Each line in this file must have the syntax:
Group-ID,User-ID *comment
A line may have leading blanks or embedded blanks preceding the comment
indicator (asterisk). If the default User ID is found in this file, a
file extension of "NSC" is appended to the associated Group ID to get the
filename for the included definitions. If the default User ID is not
found in this file, or if the file does not exist, a user-specific file
is assumed.
If an included configuration file is located on an NSC Server, it is used to
complete the NSC configuration definitions. Also, any host information files
referenced by HOST definitions are copied from the NSC Server to the NSC
Client's execution directory. The local host information file copies are then
used by NSC as long as NSC is not exited.
Any configuration definition may be used in an included configuration file.
However, if the NSC.INI file contains a GETDEFS definition, it may not contain
any location or user exit definitions (i.e. all location or user exit
definitions must be placed in the included configuration file). See Special
Considerations for other considerations.
Syntax
>>ΓöÇΓöÇGETDEFSΓöÇΓöÇ,SERVER=machineΓöÇnameΓöÇΓöÇ><
Parameters:
NAME The machine-name is the name assigned to an NSC
Server. NSCNDMN - Start the NSC Server explains how
the server is named. Lower case alphabetic characters
in the machine name will be converted to upper case.
If the SERVER parameter is not specified, the
included configuration file is assumed to be on the
NSC Client.
Example
The following example causes NSC to read the file "PDQUEUE.NSC"
on the NSC Server "DBM03" and process configurations definitions
in this file in addition to those found in the NSC.INI file. Any
host information files referenced in HOST definitions within
"PDQUEUE.NSC" will by copied from the NSC Server to the NSC
Client.
USERID=PDQUEUE
GETDEFS,SERVER=DBM03
If the NSCGROUP.TAB file on the NSC Server contains the following
line:
DEPT100,PDQUEUE
NSC will process the file "DEPT100.NSC" on the NSC Server instead
of "PDQUEUE.NSC".
ΓòÉΓòÉΓòÉ 7.1.4. Special Considerations ΓòÉΓòÉΓòÉ
Accessing Remote Configuration Files explains how you can access
configuration files on remote LAN nodes (NSC Servers).
Supporting Multiple Users at a Workstation explains how you can use
user-specific configuration files for multiple users on the same machine.
If you have an OS/2 Client running OS/2 Database Requester, you should
review the information in OS/2 Database Requester Considerations.
ΓòÉΓòÉΓòÉ 7.1.4.1. Accessing Remote Configuration Files ΓòÉΓòÉΓòÉ
In large installations, it may be desirable to store all NSC configuration
files in a central location to make it easier to manage changes. This is
supported by NSC via the GETDEFS definition with the SERVER parameter (see
GETDEFS). Instead of specifying location definitions in the NSC.INI file on the
NSC Clients, a GETDEFS definition is specified, identifying the NSC Server on
which the configuration files are stored. NSC processes the NSC.INI file on the
NSC Client, then connects to the NSC Server and processes the associated
configuration file.
The file containing the included configuration definitions can be identified
either by a User ID or a Group ID. To group User IDs together, create a flat
ASCII file called "NSCGROUP.TAB" in the same directory as the NSC configuration
file on the NSC Server. Each line in this file must have the syntax:
Group-ID,User-ID *comment
If the default User ID is found in this file, a file extension of "NSC" is
appended to the associated Group ID to get the filename for the included
definitions. This allows a single configuration file to be used for all users
with the same configuration. If the default User ID is not found in this file,
or if the file does not exist, a file extension of "NSC" is appended to the
default User ID to get the filename for the included definitions.
If included location definitions contain HOST definitions for emulator
sessions, the host information files will also be copied to the NSC Client.
This allows one copy of an host information file to be maintained for all users
accessing an emulator session using the host information file.
Smaller host information files (less than 2K bytes in size) can reduce NSC
startup time. Edit host information files stored on an NSC Server to remove
unnecessary commentary.
ΓòÉΓòÉΓòÉ 7.1.4.2. Supporting Multiple Users at a Workstation ΓòÉΓòÉΓòÉ
In some installations, a single workstation may be used by more than one
person. If each person using the workstation has a unique User ID, it may be
desirable to have a unique NSC Configuration File for each user. This is
supported by NSC via the GETDEFS definition with no SERVER parameter (see
GETDEFS). Default definitions that are common for all users at the workstation
can be placed in the NSC.INI Configuration File. The location and user exit
definitions can be placed in a file with a file extension of "NSC" appended to
the User ID for the filename. The User ID may be entered from the command line;
if not, NSC will prompt for the User ID before accessing the user-specific
configuration file.
Avoid using the USERID definition. USERID should not be specified on
workstations used by multiple users or where a user moves between workstations.
NSC will prompt the user at startup for their User ID.
When users move between workstations or a workstation has several users, you
should avoid defining a UPM account for each user on each OS/2 workstation. Not
only does this require a lot of UPM configuration work, but it also creates a
situation where it is impossible to keep a single user's password up to date on
every workstation. You can use a NODE definition (see NODE) instead of a LOCAL
definition.
ΓòÉΓòÉΓòÉ 7.1.4.3. OS/2 Database Requester Considerations ΓòÉΓòÉΓòÉ
If your OS/2 Client is an OS/2 Database Requester, Database Manager uses either
a node logon, local logon or domain logon to get your User ID and password to
validate your access to databases on the Database Server. For local or domain
logons (using the LOCAL or LANSERVER,IBM definitions) the password provided by
UPM to Database Manager after a password change may be incorrect (the NET
command does not update the UPM table from which the password is retrieved).
However, for node logons (using the NODE definition), NSC will force UPM to
update the password for the node logon after a password change by performing
another node logon with the currently logged on User ID and the new password.
For OS/2 Clients running OS/2 Database Requester, use a NODE definition to
identify your User ID to Database Manager for each Database Server to which you
connect. See NODE for an example and information on configuring the NODE
definition.
ΓòÉΓòÉΓòÉ 7.1.5. Configuration File Example ΓòÉΓòÉΓòÉ
The following configuration file shows several configuration definitions and
illustrates how the placement of definitions for host connections is
significant.
NSC Configuration File Example
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé * NSC Configuration File for Paul D. Queue Γöé
Γöé USERID=PDQUEUE Default User ID Γöé
Γöé * Passwords on VM1A and VM2B must beΓöé
Γöé MINPWLEN=5 - at least five chars long, and Γöé
Γöé MAXPWLEN=6 - no more than six. Γöé
Γöé BEEP=OFF Run quietly Γöé
Γöé LOCAL,ON Local UPM Γöé
Γöé NODE,NAME=DBM03,ON Node logon for DBM Γöé
Γöé * Signon to VM1A 3270 Session Γöé
Γöé HOST,EMULATOR,NAME=VM1A,ON,HIF=d:\nsc\nscvm.hif,V1=A,V2=AUSVM1 Γöé
Γöé * Signon to VM2B 3270 Session Γöé
Γöé HOST,EMULATOR,NAME=VM2B,ON,HIF=d:\nsc\nscvm.hif,V1=B,V2=AUSVM2 Γöé
Γöé * Signon to LAN Server LANSYS04 Γöé
Γöé LANSERVER,IBM,NAME=LANSYS04,ON Γöé
Γöé * LAN Server LANSYS07 (no signon) Γöé
Γöé LANSERVER,IBM,NAME=LANSYS07 Γöé
Γöé SERVER,NAME=DBM03 OS/2 Database Server/Gateway Γöé
Γöé * Route everything behind this to Γöé
Γöé * NSC Server DBM03 Γöé
Γöé LOCAL Change UPM passwords at DBM03 Γöé
Γöé HOST,APPC,NAME=MVSSYS01,ON DB2 Host pswd verify and changes Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
This is a customized configuration file for Mr. Paul D. Queue. Comments in the
configuration file explain most of the definitions. The User ID Character Set
definition is not specified since "PDQUEUE" is the only User ID Mr. Queue will
ever use, and the default character set is acceptable for passwords as well.
Since he always allows the User ID to default, the minimum and maximum User ID
length are not a concern.
Mr. Queue has specified the LOCAL definition with the ON parameter, requesting
a local logon at signon. He has also specified the NODE definition with the ON
parameter, requesting a node logon at signon for the OS/2 Database Manager at
the DBM03 workstation.
The first two HOST definitions precede the first SERVER definition and are
accessed via 3270 emulation sessions from Mr. Queue's workstation. The sample
host information file NSCVM.HIF will be used to log Mr. Queue on to both hosts
at signon, since the HOST definition specifies the ON parameter for both of
these hosts.
Mr. Queue is defined on two IBM LAN Server domains. He wants to be signed on to
LANSYS04 at signon, so he has specified the ON parameter in the LANSYS04
LANSERVER definition. The other LANSERVER definition is specified without the
ON parameter, so that only password changes are made on the LANSYS07 domain.
Finally, Mr. Queue uses Extended Services Database Manager to access a remote
database. The computername of the database server is "DBM03". He also uses
Distributed Database Connection Services/2(*) (DDCS/2) to access a DB2(*)
database using the database server as a gateway. To synchronize his passwords
on the database server and on the MVS host where DB2 resides, Mr. Queue
specifies a SERVER definition followed by a LOCAL definition and a HOST
definition. Specifying the LOCAL definition after the SERVER definition
indicates a UPM password change is processed at DBM03 (an NSC Server).
Specifying the HOST definition after the SERVER definition indicates the host
connection is from DBM03. An APPC profile "MVSSYS01" has been defined in the
Communications Manager configuration on DBM03 to send password changes to the
host.
ΓòÉΓòÉΓòÉ 7.2. Configuring NETBIOS ΓòÉΓòÉΓòÉ
If you have an NSC Server (NSCNDMN program with or without NSCRETRY) or run an
NSC Client that uses an NSC Server, you may have to configure additional
NETBIOS resources.
NSC programs require the following NETBIOS resources:
NSCNDMN
6 sessions (*)
6 commands (*)
1 name
NSCRETRY
1 session
1 command
1 name
NSC (or NSCPM, NSCRSON or NSCRSOFF)
1 session
1 command
1 name
You may configure the NETBIOS sessions and commands required by NSCNDMN as
command line parameters to the NSCNDMN program. The number specified
determines how many concurrent NSC Client requests the NSC Server can process.
The default is for the NSC Server to request 6 sessions and 6 commands, but
fail only if it is allocated less than 2 sessions or 2 commands.
If you have not configured enough NETBIOS resources, the NSC process will fail
when it is started and the following message is logged and displayed:
NB 01 tt:tt:tt ResAlloc add nn more SESSIONS, nn more NCBS, and nn more NAMES.
In the message, "nn" is the number of additional resources needed to
successfully start the NSC process.
In Extended Services 1.0 and LAN Server 2.0, these NETBIOS resources are
configured in the "PROTOCOL.INI" file located in the "C:\IBMCOM" directory.
The parameters are specified in the "NETBEUI" section of the file as follows:
SESSIONS = nn
NCBS = nn
NAMES = nn
Note that "NCBS" is equivalent to "commands". In Extended Edition 1.3, the
NETBIOS parameters are changed using the Communications Manager Configuration
function. You must restart the workstation for the new resource allocations to
take effect.
NSC NETBIOS resource requirements are additive. Add the requirements for each
NSC program that will run concurrently on the workstation to get a total
NETBIOS resource requirement. For example, on an OS/2 Client where NSCRETRY
will be running when a signon is performed, a minimum of two is required for
each of the NETBIOS parameters. An NSC Server running NSCRETRY requires a
minimum of 7, 7, and 2 respectively for these parameters.
NSC Clients register NETBIOS names that begin with "NSC". NSC may be
incompatible with a NETBIOS application that also attempts to register names
beginning with "NSC".
ΓòÉΓòÉΓòÉ 7.3. Configuring EMULATOR Connections ΓòÉΓòÉΓòÉ
NSC uses a host information file (HIF) to process your requests using a host
emulator session. NSC reads what is on the emulated terminal screen and inputs
keystroke information just as if you had pressed the keys on the keyboard. You
use the host information file to tell NSC how to interpret the screen
information and what to send the host computer system.
The host information file is a flat ASCII file that you may change using any
ASCII editor (for example, the OS/2 Enhanced Editor). If you do not identify
the host information file using the HIF parameter on the HOST definition, then
the host information file must reside in the same directory as NSC.INI and have
a file extension of "INI". When the host connection is made from an NSC Server,
the host information file is accessed at the computer specified in the Client's
SERVER definition.
NSC provides sample host information files for MVS, VM, and OS/400 host
emulator sessions. You may be able to use one of these sample host information
files with your host emulator session without making changes. To configure a
host emulator connection, follow these steps:
1. If you have a DOS Client, see Emulator Considerations.
2. Refer to the sample host information file for your system in Sample Host
Information Files.
3. Read the instructions for using the host information file.
4. Make a copy of the sample host information file.
5. Configure your HOST definition in the NSC configuration file using the
copy of the host information file.
a) Specify the HIF filename
b) Specify the HIF variable for the session id
c) Specify any other HIF variables required for the sample host
information file
6. If you have more than one host account, repeat step 5 for each account.
Be sure to specify a unique hostname and session id for each unique host.
If you have multiple User IDs on the same host, or if you have more
accounts than available session ids, refer to the notes in SESSION for
information on how to assign session ids.
You may need to customize your host information file because of software
differences on your host. If so, see the following sections:
General HIF Information
HIF Structure
Configuration Definitions
Screen Definitions
ΓòÉΓòÉΓòÉ 7.3.1. Emulator Considerations ΓòÉΓòÉΓòÉ
To communicate with your terminal emulation session, NSC uses the Emulator High
Level Language Application Program Interface (EHLLAPI). Many terminal emulation
packages provide EHLLAPI support. For OS/2, NSC will work only with those
emulators listed in OS/2 Clients. For DOS, NSC can work with any DOS or Windows
emulators that provide a software interrupt handler for interrupt X'7F'. The
DOS and Windows emulators that have been validated to work with NSC are listed
in DOS Clients.
This section describes special considerations for the following validated DOS
emulators:
IBM PC 3270 Emulation Program Entry Level Version 2.0 and 3.0
IBM Personal Communications/3270 (DOS Mode) Version 2.0 and 3.0
IBM Personal Communications/3270 (Windows Mode) Version 3.0
RUMBA for the Mainframe Version 3.1 Update 05
RUMBA for the AS/400 Version 1.0 Update 03 PTF 8757
ΓòÉΓòÉΓòÉ 7.3.1.1. IBM PC 3270 Emulation Program Entry Level Version 2.0 and 3.0 ΓòÉΓòÉΓòÉ
This emulator supports only one emulation session, which is assigned a
session id of E. You must use E for the SESSION definition in the host
information file.
This emulator does not support the BackSpace key (@K) or the End key
(@D). Do not use these control characters in the host information file.
To get EHLLAPI support with Version 2.0 of this emulator follow these
steps:
1. Edit the batch file that you normally use to start this emulator,
which will be either the AUTOEXEC.BAT file, or a file you have
created to do this. If you currently execute PC3270.COM to start the
emulator, you need to create a batch file. Modify the batch file so
that it contains these two commands:
- <PC3270 PATH>\PC3270 r
This command starts the emulator in resume mode so that NSC can
continue running when you have switched to the emulation
session. Do not use the command line option c when executing
this command, it disables EHLLAPI support.
- <PC3270 PATH>\EEHLLAPI
This command loads EHLLAPI support.
2. If the emulator is currently running, reboot your system by pressing
the Ctrl+Alt+Delete keys.
3. Start the emulator as you normally do, or by using the new batch
file if you had to create one. You now have EHLLAPI support.
To get EHLLAPI support with Version 3.0 of this emulator follow these
steps:
1. Alter the emulators configuration file by executing the Entry Level
3.0 command CONFIG.
2. On the initial menu, enter the name of your existing configuration
file. This is the name of the command you execute to start the
emulator. For example:
D:\PC3270\PC3270.BAT
3. Press F8 until you get to the menu titled CUT Configuration.
4. Set High Level Language Application Program Interface to YES.
5. Press F8 until you get to the final menu.
6. Press F6 to save the change.
7. Press F3 to exit CONFIG.
8. If the emulator is currently running, reboot your system by pressing
the Ctrl+Alt+Delete keys.
9. Start the emulator as you normally do. You now have EHLLAPI support.
ΓòÉΓòÉΓòÉ 7.3.1.2. IBM Personal Communications/3270 (DOS Mode) Version 2.0 and 3.0 ΓòÉΓòÉΓòÉ
This emulator supports up to 8 sessions, which are assigned a session id
of A through H. The session id for a particular emulator session is
displayed in the 7th column of its Operator Information Area (OIA), that
occupies the bottom row of the host screen.
This emulator does not support the End key (@D). Do not use this control
character in the host information file.
You may not have chosen to include EHLLAPI support when you installed
this emulator. If you did not include EHLLAPI support, follow these
steps:
1. Insert Disk 1 of the emulator's installation diskettes into a
diskette drive.
2. Change to the root directory of the diskette drive.
3. Type INSTALL and press Enter.
4. Press F8 to go to the menu titled Personal Communications/3270
Installation.
5. Select Flexible Installation, and press F8.
6. Enter the name of your existing configuration file. This is the
name of the command you execute to start the emulator. For example:
D:\PC3270\PC3270.BAT
7. Press F8 until you get to the menu titled End of Link Options.
8. Set Advanced Configuration Options to YES, and press F8.
9. Set Facilities to YES, and press F8.
10. Set High Level Language Application Program Interface to YES.
11. Press F8 until you get to the final menu.
12. Press F6 to install EHLLAPI support.
13. Follow the screen prompts for the installation diskettes.
14. When finished installing, press F3 to exit INSTALL.
15. If the emulator is currently running, switch to a host session and
press the Ctrl+End key to stop the emulator.
16. Start the emulator as you normally do. You now have EHLLAPI support.
ΓòÉΓòÉΓòÉ 7.3.1.3. IBM Personal Communications/3270 (Windows Mode) Version 3.0 ΓòÉΓòÉΓòÉ
NSC will work with this emulator only in Windows 386/486 Enhanced mode.
Refer to Installing DOS Workstations for information on how to install
NSC for use in Windows 386/486 Enhanced mode.
This emulator supports multiple sessions. The session id for a particular
session is displayed in the session's title bar, the session's icon text,
and in the 7th column of its Operator Information Area (OIA), that
occupies the bottom row of the host screen.
This emulator does not support the End key (@D). Do not use this control
character in the host information file.
To configure the emulator to provide EHLLAPI support, follow these steps:
1. From the Personal Communications group, start the Setup program.
a) Select the Options menu from the action bar.
b) Select the Change System Settings... item.
c) Check the box for the Dos-Mode EHLLAPI item in the API settings
group.
d) Select the OK push button.
e) Select the Restart Windows push button from the Exit Windows
dialog.
2. When Windows has restarted, for each of the sessions you will use
NSC with, follow these steps:
a) From the Personal Communications group, start the session's
WorkStation program.
b) Select the File menu from the action bar.
c) Select the API Settings... item.
d) Check the DDE/EHLLAPI box.
e) Select ON for the Dos-Mode EHLLAPI item.
f) Select the OK push button.
g) Select the OK push button from the Personal Communications
dialog.
h) Select the File menu from the action bar again.
i) Select the Save item.
Note: If you have not yet created a WorkStation Profile for
this WorkStation icon, you are presented with the Save
WorkStation Profile as dialog. To save the new settings, follow
these steps:
1. Enter a file name in the File Name field.
2. Select the OK push button.
3. Select the YES push button from the Personal
Communications dialog. This creates a new icon for a
WorkStation program using these new settings.
4. Enter a name of your choice in the Program Group field
when presented with the Add WorkStation Program to Program
Group dialog, or accept the supplied name.
5. Select the OK push button.
6. Select the OK push button from the Personal Communications
dialog.
j) Select the File menu from the WorkStation program's action bar.
k) Select the Exit item.
l) Start the session's WorkStation program. You now have EHLLAPI
support for this session.
ΓòÉΓòÉΓòÉ 7.3.1.4. RUMBA for the Mainframe Version 3.1 Update 05 ΓòÉΓòÉΓòÉ
NSC will work with this emulator only in Windows 386/486 Enhanced mode.
Refer to Installing DOS Workstations for information on how to install
NSC for use in Windows 386/486 Enhanced mode.
This emulator supports multiple sessions. The session id for a particular
session is specified during configuration of the emulator's EHLLAPI
support (see below).
To configure the emulator to provide EHLLAPI support, follow these steps:
1. Edit the AUTOEXEC.BAT file, adding the command <RUMBA PATH>\SET7F to
the beginning of the file, for example:
@ECHO OFF
D:\RUMBA\SET7F
...
2. Edit the Windows SYSTEM.INI file, that is located in the Windows
install directory, for example C:\WINDOWS\WINDOWS.INI. Add the
statement DEVICE=<RUMBA PATH>\VWHLLD.386 to the [386Enh] section of
the file, for example:
[386Enh]
DEVICE=D:\RUMBA\VWHLLD.386
...
3. Select the File menu from the Program Manager's action bar.
4. Select the Exit Windows... item.
5. Select the OK push button from the Exit Windows dialog.
6. Reboot your system by pressing the Ctrl+Alt+Delete keys.
7. When the system has restarted, if Windows was not auto started from
the AUTOEXEC.BAT file, start it by entering the WIN command. For
each of the sessions you will use NSC with, follow these steps:
a) From the RUMBA Applications or Rumba Profile program group,
start the session's Terminal program.
b) Select the Session menu from the action bar.
c) Select the EHLLAPI Configuration... item.
d) Check the EHLLAPI SDK box from the EHLLAPI Configuration
dialog.
e) Enter a one character session id in the Short Name... field.
Note: This is the session id you must specify in the SESSION
definition of the host information file.
f) Select the OK push button.
g) Select the File menu from the action bar.
h) Select the Save item.
Note: If you have not yet created a Terminal Profile for this
Terminal icon, you are presented with the Save Profile dialog.
To save the new settings, follow these steps:
1. Enter a file name in the Filename field.
2. Check the Create Icon Entry box for the Program Item
settings group.
3. Enter description text in the Program Item Description
field. It may be helpful to include the session id you
chose in this description text. For example: if you enter
"Terminal Session A", this text is displayed as the icon's
description text, and makes it easier to find the session
id when needed.
4. Select the OK push button. This creates a new icon for a
Terminal program using these new settings. The new icon is
added to the Rumba Profile program group.
5. Select the OK push button. This creates a program icon for
a Terminal program using these new settings. The icon is
added to the Rumba Profile program group. Use this icon to
start the session's Terminal program.
i) Select the File menu from the action bar.
j) Select the Exit item.
k) Start the session's Terminal program. You now have EHLLAPI
support for this session.
ΓòÉΓòÉΓòÉ 7.3.1.5. RUMBA for the AS/400 Version 1.0 Update 03 PTF 8757 ΓòÉΓòÉΓòÉ
NSC will work with this emulator only in Windows 386/486 Enhanced mode.
Refer to Installing DOS Workstations for information on how to install
NSC for use in Windows 386/486 Enhanced mode.
This emulator supports multiple sessions. The session id for a particular
session is specified during configuration of the emulator's EHLLAPI
support (see below).
To configure the emulator to provide EHLLAPI support, follow these steps:
1. Edit the AUTOEXEC.BAT file, adding the command <RUMBA PATH>\SET7F to
the beginning of the file, for example:
@ECHO OFF
D:\RUMBAPCS\SET7F
...
2. Edit the Windows SYSTEM.INI file, that is located in the Windows
install directory, for example C:\WINDOWS\WINDOWS.INI. Add the
statement DEVICE=<RUMBA PATH>\VWHLLD.386 to the [386Enh] section of
the file, for example:
[386Enh]
DEVICE=D:\RUMBAPCS\VWHLLD.386
...
3. Select the File menu from the Program Manager's action bar.
4. Select the Exit Windows... item.
5. Select the OK push button from the Exit Windows dialog.
6. Reboot your system by pressing the Ctrl+Alt+Delete keys.
7. When the system has restarted, if Windows was not auto started from
the AUTOEXEC.BAT file, start it by entering the WIN command. For
each of the sessions you will use NSC with, follow these steps:
a) From the RUMBA for AS/400 Applications program group, start the
session's Terminal program.
b) Select the Session menu from the action bar.
c) Select the EHLLAPI Configuration... item.
d) Check the EHLLAPI SDK box from the EHLLAPI Configuration
dialog.
e) Enter a one character session id in the Short Name field.
Note: This is the session id you must specify in the SESSION
definition of the host information file.
f) Select the OK push button.
g) Select the File menu from the action bar.
h) Select the Save item.
Note: If you have not yet created a Terminal Profile for this
Terminal icon, you are presented with the Save Profile dialog.
To save the new settings, follow these steps:
1. Enter a file name of your choice in the Filename field.
2. Select the OK push button.
3. Select the File menu from the action bar.
4. Select the Exit item.
5. To create a program icon that can be used to start this
session, follow these steps:
a) Select the program group you would like to add the
icon to by selecting either the group's icon or its
window via the mouse or keyboard.
b) Select the File menu from the Program Manager's
action bar.
c) Select the New... item.
d) Select the Program Item option.
e) Select the OK push button.
f) Enter description text in the Description field of
the Program Item Properties dialog. It may be helpful
to include the session id you chose in this
description text. For example: if you enter "Terminal
Session A", this text is displayed as the icon's
description text, and makes it easier to find the
session id when needed.
g) Enter <RUMBA PATH>\RUMBAWSF.EXE Profile Name in the
Command Line field. Profile Name is the file name you
supplied when saving the terminal profile in a
previous step. For example: D:\RUMBAPCS\RUMBAWSF.EXE
SESSIONA.WSF.
h) Enter <RUMBA PATH> in the Working Directory field.
i) Select the OK push button. This creates a program
icon for a Terminal program using these new settings.
The icon is added to the program group you selected.
Use this icon to start the session's Terminal
program.
i) Start the session's Terminal program. You now have EHLLAPI
support for this session.
ΓòÉΓòÉΓòÉ 7.3.2. General HIF Information ΓòÉΓòÉΓòÉ
The following sections contain information on the syntax of definitions found
in the host information file.
Syntax
Control Characters
HIF Variables
ΓòÉΓòÉΓòÉ 7.3.2.1. Syntax ΓòÉΓòÉΓòÉ
The host information file syntax rules are:
Line length may not exceed 256 characters (bytes).
Empty lines, blanks, and tabs are ignored.
Only one keyword is permitted per line.
A keyword and the first parameter must be separated by at least one
blank, and the remaining parameters must be separated by commas (,). For
example:
NEXT "enter password", "@p@E", "logoff@E"
A keyword and the parameters must all appear on the same line.
Keywords are not case sensitive (i.e., Logon, LOGON, and logon are
equivalent). Keywords are shown in uppercase in the examples to help
distinguish them.
Character strings are case sensitive and must be enclosed by double
quotes ("). To include a double quote within a string, two consecutive
double quotes must be used (""). For example:
"This is a double quote "" in a string"
Comments can appear either on a separate line or on the same line as a
keyword. All characters following an asterisk (*) are assumed to be
commentary, unless the asterisk is in a character string. For example:
* This comment appears on a separate line
SESSION A * This comment shares a line
ΓòÉΓòÉΓòÉ 7.3.2.2. Control Characters ΓòÉΓòÉΓòÉ
Control characters are used within a character string to specify a
non-alphanumeric terminal keystroke or to substitute some information in the
string. A control character is indicated by a preceding at sign (@). To include
an at sign within a string, two consecutive at signs must be used (@@). Note:
control characters are case sensitive.
Table "Keyboard Control Characters" shows control characters that represent
keystrokes. Table "Substitution Control Characters" shows control characters
that allow you to substitute the User ID, password, and new password in a
string. You can also use a special control character that causes a time delay.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Keyboard Control Characters Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé CHAR- Γöé KEY Γöé CHAR- Γöé KEY Γöé
Γöé ACTER Γöé Γöé ACTER Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé @ Γöé @ Γöé j Γöé PF19 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 1 Γöé PF1 Γöé v Γöé PF20 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 2 Γöé PF2 Γöé w Γöé PF21 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 3 Γöé PF3 Γöé x Γöé PF22 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 4 Γöé PF4 Γöé y Γöé PF23 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 5 Γöé PF5 Γöé z Γöé PF24 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 6 Γöé PF6 Γöé A Γöé Attention Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 7 Γöé PF7 Γöé B Γöé Left Tab Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 8 Γöé PF8 Γöé C Γöé Clear Screen Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 9 Γöé PF9 Γöé D Γöé End (1) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé a Γöé PF10 Γöé E Γöé Enter Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé b Γöé PF11 Γöé F Γöé New Line Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé c Γöé PF12 Γöé H Γöé Home Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé d Γöé PF13 Γöé I Γöé Insert Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé e Γöé PF14 Γöé K Γöé Back Space (1) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé f Γöé PF15 Γöé R Γöé Reset Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé g Γöé PF16 Γöé T Γöé Right Tab Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé h Γöé PF17 Γöé X Γöé System Request Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé i Γöé PF18 Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NOTE: Γöé
Γöé Γöé
Γöé 1. Not supported by all DOS emulators. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Substitution Control Characters Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé CHAR- Γöé REPLACED BY Γöé
Γöé ACTER Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé n Γöé new password text Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé N Γöé new password text followed by the Tab key Γöé
Γöé Γöé if the text length is shorter than the Γöé
Γöé Γöé value of PField. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé p Γöé password text Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé P Γöé password text followed by the Tab key if Γöé
Γöé Γöé the text length is shorter than the value Γöé
Γöé Γöé of PField. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé s Γöé 1-second delay, allows the host time to Γöé
Γöé Γöé process keystrokes Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé S Γöé 2-second delay, allows the host time to Γöé
Γöé Γöé process keystrokes Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé u Γöé User ID text Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé U Γöé User ID text followed by the Tab key if the Γöé
Γöé Γöé text length is shorter than the value of Γöé
Γöé Γöé UField. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 7.3.2.3. HIF Variables ΓòÉΓòÉΓòÉ
HIF variables are used within the host information file to allow substitution
of user specified text. A HIF variable is case sensitive, and is indicated by a
preceding at sign (@). Ten HIF variables, @V0 through @V9, are supported, and
may appear anywhere within the host information file. They are replaced with
your text on the HOST definition line of the NSC configuration file.
For details on how to specify HIF variables in the NSC configuration file,
refer to HOST. For examples of how to use HIF variables within host information
files, refer to Sample Host Information Files.
ΓòÉΓòÉΓòÉ 7.3.3. HIF Structure ΓòÉΓòÉΓòÉ
The host information file contains five sections:
CONFIGURATION Provides information about the host emulator session and
the host system.
See Configuration Section for more details.
GLOBAL This section defines how NSC interacts with the host
system while performing a signon, signoff, or password
change.
See Global Section for more details.
LOGON This section defines how NSC interacts with the host
system to perform a signon.
See Logon Section for more details.
PASSWORD This section defines how NSC interacts with the host
system to perform a password change.
See Change Password Section for more details.
LOGOFF This section defines how NSC interacts with the host
system to perform a signoff.
See Logoff Section for more details.
Figure "Host Information File Sections" shows the host information file
sections.
Host Information File Sections
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéCONFIGURATION *Section for config definitions Γöé
Γöé . Γöé
Γöé . Γöé
Γöé . Γöé
Γöé Γöé
ΓöéGLOBAL * Section for global definitions Γöé
Γöé . Γöé
Γöé . Γöé
Γöé . Γöé
Γöé Γöé
ΓöéLOGON * Section for logon definitions Γöé
Γöé . Γöé
Γöé . Γöé
Γöé . Γöé
Γöé Γöé
ΓöéPASSWORD * Section for password change definitions Γöé
Γöé . Γöé
Γöé . Γöé
Γöé . Γöé
Γöé Γöé
ΓöéLOGOFF * Section for logoff definitions Γöé
Γöé . Γöé
Γöé . Γöé
Γöé . Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Sections may appear any number of times, in any order.
ΓòÉΓòÉΓòÉ 7.3.3.1. Configuration Section ΓòÉΓòÉΓòÉ
The Configuration section, denoted by the keyword CONFIGURATION, defines
general information about the host system. Configuration definitions may appear
in any order within this section. If the same definition appears more than
once, the last value is the one used.
The following host definitions are allowed in the Configuration section:
SESSION
SESSIONWAIT
HOSTWAIT
UFIELD
PFIELD
ΓòÉΓòÉΓòÉ 7.3.3.2. Global Section ΓòÉΓòÉΓòÉ
The Global section, denoted by the keyword GLOBAL, defines common screens that
may be encountered at any time while interacting with a host system. This
section can be used for such things as clearing a screen when a full screen
indicator is displayed, or for exiting a host application or menu system
sub-menu so that a successful signon, signoff, or password change can be
achieved. A section consists of one or more screen definitions.
Example:
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéGLOBAL Γöé
Γöé * these screen definitions describe common host interactions Γöé
Γöé Γöé
Γöé * these definitions will clear the screen Γöé
Γöé * clear the screen if the host says "HOLDING" Γöé
Γöé CLEAR "HOLDING" Γöé
Γöé * clear the screen if the host says "MORE..." Γöé
Γöé CLEAR "MORE..." Γöé
Γöé * clear the screen if the host says "Messages Waiting" Γöé
Γöé CLEAR "Messages Waiting" Γöé
Γöé Γöé
Γöé * these definitions will exit an application Γöé
Γöé * send the F3 key to exit if reading your mail Γöé
Γöé NEXT? "MAILBOX", "@3" Γöé
Γöé * send the F2 key to save & F3 key to exit if using an editorΓöé
Γöé NEXT? "XEDIT", "@2@3" Γöé
Γöé Γöé
Γöé * these definitions will back out of a submenu Γöé
Γöé * send the F11 key to return to the main menu if in menu 2 Γöé
Γöé NEXT? "MENU 2", "@b" Γöé
Γöé * send the F12 key to return to previous menu if in sub-menu Γöé
Γöé NEXT? "PF12=Return", "@c" Γöé
Γöé * send the F12 key to return to previous menu if in sub-menu Γöé
Γöé NEXT? "Press PF12 for previous menu", "@c" Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
If the host is in one of the specified screens, that screen definition will be
processed.
The following host screen definitions are allowed in the Global section:
CLEAR
NEXT?
ΓòÉΓòÉΓòÉ 7.3.3.3. Logon Section ΓòÉΓòÉΓòÉ
The Logon section, denoted by the keyword LOGON, defines the screens
encountered while logging on to a host system. A section consists of one or
more groups of screen definitions. A screen definition group begins with a
START definition and ends with a STOP definition.
Example:
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéLOGON Γöé
Γöé * this group of screen definitions describes a logon sequenceΓöé
Γöé Γöé
Γöé * send node and User ID when prompted Γöé
Γöé START "Enter node User ID", "NODE1 @u@E" Γöé
Γöé * check if the User ID is valid Γöé
Γöé UINV "User ID invalid", "logoff@E" Γöé
Γöé * send password when prompted Γöé
Γöé NEXT "enter your password", "@p@E", "logoff@E" Γöé
Γöé * logon is successful if the host says "Ready;" Γöé
Γöé STOP? "Ready;" Γöé
Γöé * check if the password is valid Γöé
Γöé PINV "password invalid", "logoff@E" Γöé
Γöé * check if the password has expired Γöé
Γöé PEXP "password expired", "logoff@E" Γöé
Γöé * check if the password will expire soon Γöé
Γöé PWRN "password will expire" Γöé
Γöé * logon is successful if the host says "Ready;" Γöé
Γöé STOP "Ready;" Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
If the host is in a start screen, that start screen's sequence of screen
definitions will be processed in an attempt to reach its stop screen. If the
host is already in one of the stop screens specified in this section, the user
is already logged on.
The following host screen definitions are allowed in the Logon section:
START
NEXT
NEXT?
HNAVL
ULOGD
UINV
PINV
UPINV
PEXP
PWRN
STOP?
STOP
ΓòÉΓòÉΓòÉ 7.3.3.4. Change Password Section ΓòÉΓòÉΓòÉ
The Change Password section, denoted by the keyword PASSWORD, defines the
screens encountered while changing a user's password on a host system. A
section consists of one or more groups of screen definitions. A screen
definition group begins with a START definition and ends with a STOP
definition.
If the host is in a start screen, that start screen's sequence of screen
definitions will be processed in an attempt to reach its stop screen.
Example:
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéPASSWORD Γöé
Γöé * this group of screen definitions describes the password Γöé
Γöé * change sequence if the user is logged off Γöé
Γöé Γöé
Γöé * send node and User ID when prompted Γöé
Γöé START "Enter node User ID", "NODE1 @u@E" Γöé
Γöé * check if the User ID is valid Γöé
Γöé UINV "User ID invalid", "logoff@E" Γöé
Γöé * when prompted for password, enter Γöé
Γöé * password/new password/new password Γöé
Γöé NEXT "enter your password", "@p/@n/@n@E", "logoff@E" Γöé
Γöé * check if the current password is valid Γöé
Γöé PINV "password invalid", "logoff@E" Γöé
Γöé * check if the new password is valid Γöé
Γöé NINV "new password invalid","logoff@E" Γöé
Γöé * when password is changed and finished logging on, logoff Γöé
Γöé NEXT "Ready;", "logoff@E", "@A@slogoff@E" Γöé
Γöé * pswd change successful if the host is in the stop screen Γöé
Γöé STOP "Enter node User ID" Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
The following host screen definitions are allowed in the Password section:
START
NEXT
NEXT?
HNAVL
ULOGD
UINV
PINV
UPINV
NINV
PNINV
STOP?
STOP
ΓòÉΓòÉΓòÉ 7.3.3.5. Logoff Section ΓòÉΓòÉΓòÉ
The Logoff section, denoted by the keyword LOGOFF, defines the screens
encountered while logging off from a host system. A section consists of one or
more groups of screen definitions. A screen definition group begins with a
START definition and ends with a STOP definition.
If the host is in a start screen, that start screen's sequence of screen
definitions will be processed in an attempt to reach its stop screen. If the
host is already in one of the stop screens specified in this section, the user
is already logged off.
Example:
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéLOGOFF Γöé
Γöé * this group of screen definitions is a logoff sequence Γöé
Γöé Γöé
Γöé * exit when in the menu system Γöé
Γöé START "Menu I", "@3" Γöé
Γöé * logoff when finished exiting menu system Γöé
Γöé NEXT "Ready;", "logoff@E", "@A@slogoff@E" Γöé
Γöé * logoff successful if the host is in the stop screen Γöé
Γöé STOP "Enter node User ID" Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
The following host screen definitions are allowed in the Logoff section:
START
NEXT
NEXT?
STOP?
STOP
ΓòÉΓòÉΓòÉ 7.3.4. Configuration Definitions ΓòÉΓòÉΓòÉ
The configuration definitions and where to find out more about them are:
To specify Definition
------------- -------------
Session Identifier SESSION
Session wait time SESSIONWAIT
Host wait time HOSTWAIT
User ID field length UFIELD
Password field length PFIELD
ΓòÉΓòÉΓòÉ 7.3.4.1. SESSION ΓòÉΓòÉΓòÉ
Use the SESSION definition to specify which emulator sessions NSC should try to
use to make the host connection. You can specify multiple sessions to try and
the order in which they should be tried. An emulator session must be started
and available for NSC to use it.
Syntax
<ΓöÇ,ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ<
>>ΓöÇΓöÇSESSIONΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇ><
ΓööΓöÇΓö¼ΓöÇ{A..Z}ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÿ
Γö£ΓöÇ{A..Z}ΓöÇ{A..Z}ΓöÇΓöñ
ΓööΓöÇ?ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Values
Choose one or more from the following:
To use a particular session, specify a single character
between "A" and "Z".
To pick from a set of sessions, specify each session ID ("A"
to "Z"), separated by commas. NSC will check the sessions in
the order you specify them.
To pick from a range of sessions, specify the first and last
session IDs in the range separated by a dash ("-"). You can
specify an ascending or descending range.
To pick any session, specify a question mark ("?").
Default
A
Example
The following example causes NSC to search for an available
session.
SESSION A,C-E,H-F,?
NSC checks the emulator sessions in the following order:
1. A
2. C, D, and then E.
3. H, G, and then F.
4. B and then I through Z. In this case, "?" is the set of IDs
that have not been previously specified.
1. Session IDs are not case sensitive.
2. If the same session ID appears more than once, the second occurrence is
ignored.
3. If you do not know what session IDs are available to you, refer to your
emulator support information on how to determine the correct session ID.
4. You can specify the SESSION as a HIF Variable (e.g. %V1). In this case,
all of the rules that apply to session IDs still apply to the string
assigned to the HIF Variable. Specifying the SESSION as a HIF Variable
allows the same host information file to be used for HOST definitions
using different host emulator sessions (this is how the SESSION is
specified in the sample HIFs).
5. If you have more HOST definitions than available sessions, you must keep
in mind that if you are signed on to a host emulator session, you cannot
use that session to change your password on another account on the same
host. You must either:
reserve one session that can be used for changing passwords, or
change passwords only when you are not signed on to a shared
emulator session
6. If you have multiple HOST definitions that must share the same session,
specify a unique hostname for each HOST definition, and specify the
session ID as a combination of the shared session ID for signon and the
session ID reserved for changing passwords (e.g. "A,D"). Before you
selectively signon to one of these hosts, you will have to signoff of the
one currently signed on.
7. If you have multiple User IDs on the same host, you can configure them in
one of two ways:
If you want to be able to signon to more than one of the User IDs at
the same time, and you have enough available emulator sessions,
specify a unique hostname and session ID for each User ID.
If you only want to signon to one User ID at a time, specify the
same hostname for each HOST definition, and specify the session ID
as a combination of the session ID for signon and the session ID
reserved for changing passwords. When you selectively signon to one
of these User IDs, NSC will first signoff the User ID currently
signed on.
ΓòÉΓòÉΓòÉ 7.3.4.2. SESSIONWAIT ΓòÉΓòÉΓòÉ
Use the SESSIONWAIT definition to specify the maximum number of seconds NSC
waits to gain access to an emulator session.
Syntax SESSIONWAIT {1..600}
Values Choose a number between 1 and 600.
NSC attempts to access all of the specified sessions repeatedly
until successful, or the specified session wait maximum is
reached. If the emulator session has not been started, or the
session is in use, NSC will not be able to access it. If the
session is started shortly before NSC attempts an access, it may
not have finished starting yet. If the session is on an NSC
Server, it is probably used by others for password changes and
at times the session will be in use when a new request arrives.
Specifying a higher value increases the chances of gaining
access to a session, but a lower value decreases the time spent
waiting for an invalid session. If the session is nearly
finished starting before NSC attempts an access, and is
dedicated to one user, the default value will be adequate.
Default 30
Example The following causes NSC to try for up to 60 seconds to gain
access to any one of the specified session ids.
SESSIONWAIT 60 *try for up to 60 seconds
ΓòÉΓòÉΓòÉ 7.3.4.3. HOSTWAIT ΓòÉΓòÉΓòÉ
Use the HOSTWAIT definition to specify the maximum number of seconds NSC waits
for the host to update the screen. If the host doesn't update the screen within
this time, NSC assumes the host has finished processing all keystrokes.
Syntax HOSTWAIT {1..60}
Values Specify a value equal to the longest delay between screen
updates you have observed while interacting with the host via an
emulator session. If NSC doesn't wait long enough for the host
to make its updates, increase this number. If the value is too
low, your signon request will not be processed correctly. If the
value is too high, your signon request may take longer than
necessary. The default should work in many cases.
Note: Use care in setting this value since host and network
responses vary. Setting the value too low can result in
occasional request failures.
Default 5
Example The following causes NSC to wait up to 3 seconds for a screen
update.
HOSTWAIT 3 *Wait up to 3 seconds
ΓòÉΓòÉΓòÉ 7.3.4.4. UFIELD ΓòÉΓòÉΓòÉ
Use the UFIELD definition to specify the length of the emulator session
screen's User ID field. A screen can be formatted with an entry field to hold
the User ID. If the User ID fills the entry field, the cursor is automatically
advanced to the next entry field on the screen. When the User ID is shorter
than its entry field, NSC will add a Tab key following it to advance to the
next entry field.
Syntax UFIELD {4..16}
Values Specify a value between 4 and 16.
Default 8
Example The following causes NSC to add a Tab key when the User ID is
shorter than 16 characters.
UFIELD 16 *User ID screen entry field length
ΓòÉΓòÉΓòÉ 7.3.4.5. PFIELD ΓòÉΓòÉΓòÉ
Use the PFIELD definition to specify the length of the emulator session
screen's password fields. A screen can be formatted with an entry field to hold
a password. If the password fills the entry field, the cursor is automatically
advanced to the next entry field on the screen. When the password is shorter
than its entry field, NSC will add a Tab key following it to advance to the
next entry field.
Syntax PFIELD {4..16}
Values Specify a value between 4 and 16.
Default 8
Example The following causes NSC to add a Tab key when the password is
shorter than 7 characters.
PFIELD 7 *Password screen entry field length
ΓòÉΓòÉΓòÉ 7.3.5. Screen Definitions ΓòÉΓòÉΓòÉ
Screen definitions are used to describe a specific host screen, and how to
change the host to the next screen. They are used in the Global, Logon,
Password, and Logoff sections.
Three types of string parameters are used with screen definitions:
Search Used to specify the text message that appears on the emulator's
screen. NSC will search the emulator session screen buffer for this
string.
Control characters within this string parameter are not processed,
but HIF variables are. Refer to Control Characters and HIF Variables
for more information.
If an empty string is specified for this parameter, i.e.: "", the
search string will always be found in the screen buffer. Consider
this affect before specifying an empty search string.
Response Used to specify the keys that should be sent to the host to continue
the requested host operation. This key sequence should result in the
host changing to a screen from which the host operation can be
continued or completed.
Control characters and HIF variables within this string parameter
are processed. Refer to Control Characters and HIF Variables for
more information.
If an empty string is specified for this parameter, i.e.: "", no
keys are sent to the host.
Reset Used to specify the keys that should be sent to the host to
terminate the requested host operation. This key sequence should
result in the host changing to a screen from which the host
operation can be initiated again.
Control characters and HIF variables within this string parameter
are processed. Refer to Control Characters and HIF Variables for
more information.
If an empty string is specified for this parameter, i.e.: "", no
keys are sent to the host.
In the Logon, Password, and Logoff sections, screen definitions are specified
in Start-Stop groups, that tell NSC how to achieve the request if the host is
in that specific start screen. Each section can contain multiple Start-Stop
groups, but they may not be nested. NSC will check the host for all START
screen definitions listed in a section; if the host is not found to be in any
of the specified start screens, an appropriate error message will be returned.
If the host is found to be in one of the specified start screens, each screen
definition following that start definition is processed sequentially through
the associated stop screen definition. Screen definitions are order-dependent;
they must occur in the order they will be encountered while interacting with
the host system.
Example:
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéLOGON Γöé
Γöé* one logon sequence Γöé
ΓöéSTART "Enter Id:","@u@E" * send userid Γöé
Γöé NEXT "Enter pw:","@p@E","logoff@E"* send pw when prompted, Γöé
Γöé * else logoff Γöé
ΓöéSTOP "Ready;" * finished logon Γöé
Γöé Γöé
Γöé* another possible logon sequence Γöé
ΓöéSTART "Node =>","MVS1@E" * send "MVS1" Γöé
Γöé NEXT "User Id:","@U@E","logoff@E" * send uid when prompted, Γöé
Γöé * else logoff Γöé
Γöé NEXT "Password:","@P@E","logoff@E"* send pw when prompted, Γöé
Γöé * else logoff Γöé
ΓöéSTOP "RUNNING" * finished logon Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
In this example, two different logon sequences are possible. NSC will
determine if the host is in any of these start screens. If the string "Node
=>" is found on the host screen, that Start-Stop group will be processed to
completion. In this case, the string "RUNNING" notifies NSC that the logon has
completed.
The screen definitions and where to find out more about them are:
To specify Definition
------------- -------------
Clear screens CLEAR
Start screens START
Required next screens NEXT
Optional next screens NEXT?
Host not available screens HNAVL
User ID already logged on screens ULOGD
Invalid User ID screens UINV
Invalid password screens PINV
Invalid User ID or password screens UPINV
Expired password screens PEXP
Password will expire soon screens PWRN
Invalid new password screens NINV
Invalid old or new password screens PNINV
Optional stop screens STOP?
Stop screens STOP
ΓòÉΓòÉΓòÉ 7.3.5.1. CLEAR ΓòÉΓòÉΓòÉ
Use the CLEAR screen definition to specify a message that is displayed by the
host to indicate it is waiting for the screen to be cleared. When a host has
more data to display than will fit on one screen, it displays a full screen of
data and some indicator that more data is waiting. Usually, the user presses
the Clear key to display more data.
NSC scans the screen buffer looking for the search string. If found, NSC:
Sends the response string to the host.
If the search string is not found, NSC:
Processes the next screen definition in the GLOBAL section.
Syntax
>>ΓöÇΓöÇCLEARΓöÇΓöÇsearchΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇ><
ΓööΓöÇ,responseΓöÇΓöÿ
Parameters
search Specifies the string that NSC searches for in the
screen buffer to determine whether a Clear key is
needed to clear the screen. Refer to Screen
Definitions for more information about the search
string.
Carefully consider the string specified since the
host may not be expecting a clear response.
response Specifies the optional string that NSC sends to the
host when the search string is found. If not
supplied, the Clear key ("@C") is used. Refer to
Screen Definitions for more information about the
response string.
Example
The following examples cause NSC to clear a screen when the
screen buffer contains "HOLDING".
CLEAR "HOLDING" *Screen full?, send clear key
or
CLEAR "HOLDING","@C" *Screen full?, send clear key
ΓòÉΓòÉΓòÉ 7.3.5.2. START ΓòÉΓòÉΓòÉ
Use the START screen definition to specify a message that is displayed by the
host to indicate it is ready to accept a logon, logoff, or change password
request. It is also used to mark the beginning of a Start-Stop group. Multiple
START definitions can be specified, as long as they are paired with a STOP
definition.
NSC scans the screen buffer looking for the search string. If found, NSC:
Selects this Start-Stop group to process the user request.
Sends the response string to the host.
Processes the next screen definition in this group.
If the search string is not found, and another Start-Stop group exists, NSC:
Continues processing with the START definition in the next group.
If the search string is not found, and no more Start-Stop groups exist, NSC:
Terminates request processing.
Displays an error message on the screen.
Syntax
>>ΓöÇΓöÇSTARTΓöÇΓöÇsearchΓöÇΓöÇ,ΓöÇΓöÇresponseΓöÇΓöÇ><
Parameters
search Specifies the string that NSC searches for in the
emulator session screen buffer to determine whether
to process this Start-Stop group of definitions.
Refer to Screen Definitions for more information
about the search string.
response Specifies the string that NSC sends to the host when
the search string is found. Refer to Screen
Definitions for more information about the response
string.
Example
The following shows a logon request causing NSC to send the User
ID to the host when the host prompts for it.
LOGON *section definition
START "Enter User ID:", "@u@E" * send User ID
* when asked
ΓòÉΓòÉΓòÉ 7.3.5.3. NEXT ΓòÉΓòÉΓòÉ
Use the NEXT (Required Next) screen definition to specify a message that must
be displayed by the host before NSC can continue processing the request.
Multiple NEXT definitions can be specified.
NSC scans the screen buffer looking for the search string. If found, NSC:
Sends the response string to the host.
Processes the next screen definition in this group.
If the search string is not found, NSC:
Sends the reset string, if supplied, to the host.
Terminates request processing.
Displays an error message on the screen.
Syntax
>>ΓöÇΓöÇNEXTΓöÇΓöÇsearchΓöÇΓöÇ,ΓöÇΓöÇresponseΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇ><
ΓööΓöÇ,resetΓöÇΓöÿ
Parameters
search Specifies the string that NSC searches for in the
emulator session screen buffer to determine that
request processing should continue. Refer to Screen
Definitions for more information about the search
string.
response Specifies the string that NSC sends to the host when
the search string is found. Refer to Screen
Definitions for more information about the response
string.
reset Specifies the optional string that NSC sends to the
host when the search string is not found. Refer to
Screen Definitions for more information about the
reset string.
Example
This shows a user's password being sent to the host during a
logon request using the NEXT definition. When the "enter
password" string is found in the screen buffer, the user's
password followed by the Enter key is sent to the host.
If the "enter password" string doesn't appear, the string
"logoff" followed by the Enter key is sent to the host. Sending
the "logoff" should reset the host session to a condition where
another logon can be attempted.
LOGON *section definition
START "Enter User ID:", "@u@E" * send User ID
* when asked
NEXT "enter password", "@p@E", "logoff@E"
ΓòÉΓòÉΓòÉ 7.3.5.4. NEXT? ΓòÉΓòÉΓòÉ
Use the NEXT? (Optional Next) screen definition to specify a message that may
be displayed by the host to indicate it is waiting for user interaction.
Multiple NEXT? definitions can be specified.
NSC scans the screen buffer looking for the search string. If found, NSC:
Sends the response string to the host.
Processes the next screen definition in this group.
If the search string is not found, NSC:
Processes the next screen definition in this group.
Syntax
>>ΓöÇΓöÇNEXT?ΓöÇΓöÇsearchΓöÇΓöÇ,ΓöÇΓöÇresponseΓöÇΓöÇ><
Parameters
search Specifies the string that NSC searches for in the
emulator session screen buffer. Refer to Screen
Definitions for more information about the search
string.
response Specifies the string that NSC sends to the host when
the search string is found. Refer to Screen
Definitions for more information about the response
string.
Example
The following shows how you can use NEXT? to exit a system news
host application. When the "SYSNEWS" string is found in the
screen buffer, the host is sent an F3 key to cause an exit from
this application.
NEXT? "SYSNEWS", "@3" * exit if in system news application
ΓòÉΓòÉΓòÉ 7.3.5.5. HNAVL ΓòÉΓòÉΓòÉ
Use the HNAVL (Host Not Available) screen definition to specify a message that
is displayed by the host to indicate it is currently not available. Multiple
HNAVL definitions can be specified.
NSC scans the screen buffer looking for the search string. If found, NSC:
Sends the reset string to the host.
Terminates request processing.
Displays an error message on the screen.
If the search string is not found, NSC:
Processes the next screen definition in this group.
Syntax
>>ΓöÇΓöÇHNAVLΓöÇΓöÇsearchΓöÇΓöÇ,ΓöÇΓöÇresetΓöÇΓöÇ><
Parameters
search Specifies the string that NSC searches for in the
emulator session screen buffer to determine that the
host is not available. Refer to Screen Definitions
for more information about the search string.
reset Specifies the string that NSC sends to the host when
the search string is found. Refer to Screen
Definitions for more information about the reset
string.
Example
The following shows a HNAVL definition that logs the user off
when the host sends a message indicating the host is not
available.
HNAVL "host application is down", "logoff@E"
ΓòÉΓòÉΓòÉ 7.3.5.6. ULOGD ΓòÉΓòÉΓòÉ
Use the ULOGD (User Logged on From Another Session) screen definition to
specify a message that is displayed by the host to indicate the User ID is
already logged on from another session. Multiple ULOGD definitions can be
specified.
NSC scans the screen buffer looking for the search string. If found, NSC:
Sends the reset string to the host.
Terminates request processing.
Displays an error message on the screen.
If the search string is not found, NSC:
Processes the next screen definition in this group.
Syntax
>>ΓöÇΓöÇULOGDΓöÇΓöÇsearchΓöÇΓöÇ,ΓöÇΓöÇresetΓöÇΓöÇ><
Parameters
search Specifies the string that NSC searches for in the
emulator session screen buffer to determine that the
User ID is already logged on from another session.
Refer to Screen Definitions for more information
about the search string.
reset Specifies the string that NSC sends to the host when
the search string is found. Refer to Screen
Definitions for more information about the reset
string.
Example
The following shows a ULOGD definition that logs the user off
when the host sends a message indicating the User ID is already
logged on from another session.
ULOGD "User is already logged on", "logoff@E"
ΓòÉΓòÉΓòÉ 7.3.5.7. UINV ΓòÉΓòÉΓòÉ
Use the UINV (User ID Invalid) screen definition to specify a message that is
displayed by the host to indicate that an invalid User ID was entered. Multiple
UINV definitions can be specified.
NSC scans the screen buffer looking for the search string. If found, NSC:
Sends the reset string to the host.
Terminates request processing.
Displays an error message on the screen.
If the search string is not found, NSC:
Processes the next screen definition in this group.
Syntax
>>ΓöÇΓöÇUINVΓöÇΓöÇsearchΓöÇΓöÇ,ΓöÇΓöÇresetΓöÇΓöÇ><
Parameters
search Specifies the string that NSC searches for in the
emulator session screen buffer to determine that the
User ID is invalid. Refer to Screen Definitions for
more information about the search string.
reset Specifies the string that NSC sends to the host when
the search string is found. Refer to Screen
Definitions for more information about the reset
string.
Example
The following shows a UINV definition that logs the user off when
the host sends a message indicating the User ID is invalid.
UINV "User ID not valid", "logoff@E"
ΓòÉΓòÉΓòÉ 7.3.5.8. PINV ΓòÉΓòÉΓòÉ
Use the PINV (Password Invalid) screen definition to specify a message that is
displayed by the host to indicate an invalid password was entered. Multiple
PINV definitions can be specified.
NSC scans the screen buffer looking for the search string. If found, NSC:
Sends the reset string to the host.
Terminates request processing.
Displays an error message on the screen.
If the search string is not found, NSC:
Processes the next screen definition in this group.
Syntax
>>ΓöÇΓöÇPINVΓöÇΓöÇsearchΓöÇΓöÇ,ΓöÇΓöÇresetΓöÇΓöÇ><
Parameters
search Specifies the string that NSC searches for in the
emulator session screen buffer to determine that the
password is invalid. Refer to Screen Definitions for
more information about the search string.
reset Specifies the string that NSC sends to the host when
the search string is found. Refer to Screen
Definitions for more information about the reset
string.
Example
The following shows a PINV definition that logs the user off when
the host sends a message indicating the password is invalid.
PINV "invalid password", "logoff@E"
ΓòÉΓòÉΓòÉ 7.3.5.9. UPINV ΓòÉΓòÉΓòÉ
Use the UPINV (User ID or Password Invalid) screen definition to specify a
message that is displayed by the host to indicate an invalid password or User
ID was entered. Multiple UPINV definitions can be specified.
NSC scans the screen buffer looking for the search string. If found, NSC:
Sends the reset string to the host.
Terminates request processing.
Displays an error message on the screen.
If the search string is not found, NSC:
Processes the next screen definition in this group.
Syntax
>>ΓöÇΓöÇUPINVΓöÇΓöÇsearchΓöÇΓöÇ,ΓöÇΓöÇresetΓöÇΓöÇ><
Parameters
search Specifies the string that NSC searches for in the
emulator session screen buffer to determine that the
User ID or password is invalid. Refer to Screen
Definitions for more information about the search
string.
reset Specifies the string that NSC sends to the host when
the search string is found. Refer to Screen
Definitions for more information about the reset
string.
Example
The following shows a UPINV definition that logs the user off
when the host sends a message indicating the password is invalid.
UPINV "invalid id or password", "logoff@E"
ΓòÉΓòÉΓòÉ 7.3.5.10. PEXP ΓòÉΓòÉΓòÉ
Use the PEXP (Password Expired) screen definition to specify a message that is
displayed by the host to indicate the password has expired. Multiple PEXP
definitions can be specified.
NSC scans the screen buffer looking for the search string. If found, NSC:
Sends the reset string to the host.
Terminates request processing.
Displays an error message on the screen.
If the search string is not found, NSC:
Processes the next screen definition in this group.
Syntax
>>ΓöÇΓöÇPEXPΓöÇΓöÇsearchΓöÇΓöÇ,ΓöÇΓöÇresetΓöÇΓöÇ><
Parameters
search Specifies the string that NSC searches for in the
emulator session screen buffer to determine that the
password has expired. Refer to Screen Definitions for
more information about the search string.
reset Specifies the string that NSC sends to the host when
the search string is found. Refer to Screen
Definitions for more information about the reset
string.
Example
The following shows a PEXP definition that logs the user off when
the host sends a message indicating the password has expired.
PEXP "password has expired", "logoff@E"
ΓòÉΓòÉΓòÉ 7.3.5.11. PWRN ΓòÉΓòÉΓòÉ
Use the PWRN (Password Will Expired) screen definition to specify a message
that is displayed by the host to indicate the password will soon expire.
Multiple PWRN definitions can be specified.
NSC scans the screen buffer looking for the search string. If found, NSC:
Sends the response string, if supplied, to the host.
Processes the next screen definition in this group.
Displays a warning message on the screen.
If the search string is not found, NSC:
Processes the next screen definition in this group.
Syntax
>>ΓöÇΓöÇPWRNΓöÇΓöÇsearchΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇ><
ΓööΓöÇ,responseΓöÇΓöÿ
Parameters
search Specifies the string that NSC searches for in the
emulator session screen buffer to determine that the
password will expire soon. Refer to Screen
Definitions for more information about the search
string.
response Specifies the optional string that NSC sends to the
host when the search string is found. Refer to Screen
Definitions for more information about the response
string.
Example
The following shows a PWRN definition.
PWRN "password will expire"
ΓòÉΓòÉΓòÉ 7.3.5.12. NINV ΓòÉΓòÉΓòÉ
Use the NINV (New Password Invalid) screen definition to specify a message that
is displayed by the host to indicate the new password is invalid. Multiple NINV
definitions can be specified.
NSC scans the screen buffer looking for the search string. If found, NSC:
Sends the reset string to the host.
Terminates request processing.
Displays an error message on the screen.
If the search string is not found, NSC:
Processes the next screen definition in this group.
Syntax
>>ΓöÇΓöÇNINVΓöÇΓöÇsearchΓöÇΓöÇ,ΓöÇΓöÇresetΓöÇΓöÇ><
Parameters
search Specifies the string that NSC searches for in the
emulator session screen buffer to determine that the
new password is invalid. Refer to Screen Definitions
for more information about the search string.
reset Specifies the string that NSC sends to the host when
the search string is found. Refer to Screen
Definitions for more information about the reset
string.
Example
The following shows a NINV definition that logs the user off when
the host sends a message indicating the new password is invalid.
NINV "invalid new password", "logoff@E"
ΓòÉΓòÉΓòÉ 7.3.5.13. PNINV ΓòÉΓòÉΓòÉ
Use the PNINV (Password or New Password Invalid) screen definition to specify a
message that is displayed by the host to indicate the password or new password
is invalid. Multiple PNINV definitions can be specified.
NSC scans the screen buffer looking for the search string. If found, NSC:
Sends the reset string to the host.
Terminates request processing.
Displays an error message on the screen.
If the search string is not found, NSC:
Processes the next screen definition in this group.
Syntax
>>ΓöÇΓöÇPNINVΓöÇΓöÇsearchΓöÇΓöÇ,ΓöÇΓöÇresetΓöÇΓöÇ><
Parameters
search Specifies the string that NSC searches for in the
emulator session screen buffer to determine that the
password or new password is invalid. Refer to Screen
Definitions for more information about the search
string.
reset Specifies the string that NSC sends to the host when
the search string is found. Refer to Screen
Definitions for more information about the reset
string.
Example
The following shows a PNINV definition that logs the user off
when the host sends a message indicating some password is
invalid.
PNINV "a password was invalid", "logoff@E"
ΓòÉΓòÉΓòÉ 7.3.5.14. STOP? ΓòÉΓòÉΓòÉ
Use the STOP? (Optional Stop) screen definition to specify a message that is
displayed by the host to indicate a logon, logoff, or change password has
completed. Multiple STOP? definitions can be specified. Use STOP? definitions
in conjunction with a STOP definition in situations where more than one host
message indicates a request has completed successfully.
NSC scans the screen buffer looking for the search string. If found, NSC:
Terminates request processing.
Displays a completion message on the screen.
If the search string is not found, NSC:
Processes the next screen definition in this group.
Syntax
>>ΓöÇΓöÇSTOP?ΓöÇΓöÇsearchΓöÇΓöÇ><
Parameters
search Specifies the string that NSC searches for in the
emulator session screen buffer to determine that the
request has completed. Refer to Screen Definitions
for more information about the search string.
Example
The following shows a STOP? definition that checks for "MENU I"
along with a STOP definition that terminates the definition
group.
STOP? "MENU I"
STOP "Ready;"
ΓòÉΓòÉΓòÉ 7.3.5.15. STOP ΓòÉΓòÉΓòÉ
Use the STOP screen definition to specify a message displayed by the host to
indicate a logon, logoff, or change password has completed. It is also used to
mark the end of a Start-Stop group. Multiple STOP definitions can be specified,
as long as they are paired with a START definition.
NSC scans the screen buffer looking for the search string. If found, NSC:
Terminates request processing.
Displays a completion message on the screen.
If the search string is not found, NSC:
Terminates request processing.
Displays an error message on the screen.
Syntax
>>ΓöÇΓöÇSTOPΓöÇΓöÇsearchΓöÇΓöÇ><
Parameters
search Specifies the string that NSC searches for in the
emulator session screen buffer to determine that the
request has completed. Refer to Screen Definitions
for more information about the search string.
Example
The following shows a STOP definition that checks for "RUNNING".
STOP "RUNNING"
ΓòÉΓòÉΓòÉ 7.3.6. Sample Host Information Files ΓòÉΓòÉΓòÉ
This section contains sample host information files included on the NSC
installation diskette.
NSCMVS.HIF shows a sample for a MVS Host System.
NSCVM.HIF shows a sample for a VM Host System.
NSCVMOV.HIF shows a sample for a VM Host System with OfficeVision.
NSCOS400.HIF shows a sample for an OS/400 Host System.
NSCIIN.HIF shows a sample for the IBM Information Network.
ΓòÉΓòÉΓòÉ 7.3.6.1. NSCMVS.HIF ΓòÉΓòÉΓòÉ
NSCVMS.HIF is a host information file for a MVS Host System. It defines start
and stop screens for the standard TSO prompts. It uses a RACF command to change
the host password. If your host system does not use RACF, you will need to
modify the host information file based on the host security software program
used. To signon to the host, it sends the node id of the host (you specify this
as a HIF Variable in the HOST definition) followed by your User ID. NSCMVS.HIF
has two HIF Variables:
V1 defines the host session id (e.g. V1=A)
V2 defines the node id sent for a signon with the userid (e.g. V2=TSO1)
The following is an example of a HOST definition using this host information
file.
USERID=PDQUEUE
Host,EMULATOR,Name=TSO1,ON,HIF=d:\nsc\nscmvs.hif,V1=A,V2=TSO1
In this example, "V1=A" specifies host emulator session A will be used for the
host "TSO1", and "V2=TSO1" specifies that the initial connection to the host
will be made by sending the string "TSO1 PDQUEUE" to the emulator.
NSCMVS.HIF
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
* This is a sample host information file for an MVS host system
* It requires the following HIF Variables in the NSC configuration file:
* V1=host session id (e.g. V1=A or V1=A-E)
* V2=the first command sent for a signon with the userid (e.g. V2=TSO1)
CONFIGURATION * Section for configuration options
SESSION @V1 * Host session id from HIF Variable V1
HOSTWAIT 5 * Wait for Host up to 5 seconds
SESSIONWAIT 60 * Wait for Session up to 60 seconds
UFIELD 8 * UserID entry field length
PFIELD 8 * Password entry field length
GLOBAL * Section for global screen definitions
* The following definitions are for when the screen needs to be cleared
CLEAR " *** ", "@C@E" * if " *** ", send Clear,Enter
LOGON * Section for logon screen definitions
START "Enter access code:", "@V2 @u@E" * Start screen
* if found, send V2," ",UID,Enter
UINV "not authorized to", "@3" * UserID Invalid error screen
* if found, send PF3
NEXT "Password ===>", "@P@E", "@3" * Required next screen
* if found, send PW,Enter
* if not found, send PF3
STOP? "READY" * Conditional stop screen
ULOGD "IN USE", "logoff@E" * UserID is already logged on
* if found, send "logoff",Enter
PINV "PASSWORD NOT AUTH", "@3" * Password invalid error screen
* if found, send PF3
PEXP "PASSWORD HAS EXPIRED", "@3" * Password expired error screen
* if found, send PF3
PWRN "PASSWORD WILL EXPIRE" * Password expiring warning screen
STOP "READY" * Required stop screen
PASSWORD * Section for password change screen definitions
* Password change screen definitions if logged off
START "Enter access code:", "@V2 @u@E" * Start screen
* if found, send V2," ",UID,Enter
UINV "not authorized to", "@3" * UserID Invalid error screen
* if found, send PF3
NEXT "Password ===>", "@P@N@E", "@3" * Required next screen
* if found, send PW,NPW,Enter
* if not found, send PF3
ULOGD "IN USE", "logoff@E" * UserID is already logged on
* if found, send "logoff",Enter
NEXT "Reenter the new", "@N@E", "@3" * Required next screen
* if found, send NPW,Enter
* if not found, send PF3
PINV "PASSWORD NOT AUTH", "@3" * Password invalid error screen
* if found, send PF3
NINV "NEW-PASSWORD IS INVAL","@3" * NewPassword invalid error screen
* if found, send PF3
NEXT "READY", "logoff@E","logoff@E" * Required next screen
* if found, send "logoff",Enter
* if not found, send "logoff",Ent
STOP "Enter access code:" * Required stop screen
* Password change screen definitions if logged on
START "READY", "password password(@p @n)@E" * Start screen
* if found, send
* "password password(",PW," ",
* NPW,")",Enter
PINV "NOT CURRENT PASSWORD", "@C@E" * Password invalid error screen
* if found, send Clear,Enter
NINV "MATCHES A PREVIOUS", "@C@E" * NewPassword invalid error screen
* if found, send Clear,Enter
NINV "CANNOT EQUAL CURRENT", "@C@E" * NewPassword invalid error screen
* if found, send Clear,Enter
NINV "CHANGE REJECTED", "@C@E" * NewPassword invalid error screen
* if found, send Clear,Enter
NINV "INVALID NEW PASSWORD", "@A@C@E" * NewPassword invalid error screen
* if found, send Attn,Clear,Enter
STOP "READY" * Required stop screen
LOGOFF * Section for logoff screen definitions
START "READY", "logoff@E" * Start screen
* if found, send "logoff",Enter
STOP "Enter access code:" * Required stop screen
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
ΓòÉΓòÉΓòÉ 7.3.6.2. NSCVM.HIF ΓòÉΓòÉΓòÉ
NSCVM.HIF is a host information file for a VM Host System (see NSCVMOV.HIF for
a host information file for a VM Host System with OfficeVision). It defines
start and stop screens for the standard CMS prompts. It uses a RACF command to
change the host password. If your host system does not use RACF, you will need
to modify the host information file based on the host security software program
used. To signon to the host, it sends the node id of the host (you specify this
as a HIF Variable in the HOST definition) followed by your User ID. NSCVM.HIF
has two HIF Variables:
V1 defines the host session id (e.g. V1=A)
V2 defines the node id sent for a signon with the userid (e.g. V2=AUSVM2)
The following is an example of two HOST definitions using this host
information file.
USERID=PDQUEUE
Host,EMULATOR,Name=VM2,ON,HIF=d:\nsc\nscvm.hif,V1=B,V2=AUSVM2
Host,EMULATOR,Name=VM6,ON,HIF=d:\nsc\nscvm.hif,V1=C,V2=AUSVM6
In this example, "V1=B" specifies host emulator session B will be used for the
host "VM2", and "V2=AUSVM2" specifies that the initial connection to the host
will be made by sending the string "AUSVM2 PDQUEUE" to the emulator.
The host "VM6" is defined in a similar way using the same host information
file.
NSCVM.HIF
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
* This is a sample host information file for a VM host system
* It requires the following HIF Variables in the NSC configuration file:
* V1=host session id (e.g. V1=A or V1=A-E)
* V2=the first command sent for a signon with the userid (e.g. V2=AUSVM2)
CONFIGURATION * Section for configuration options
SESSION @V1 * Host session id from HIF Variable V1
HOSTWAIT 5 * Wait for Host up to 5 seconds
SESSIONWAIT 60 * Wait for Session up to 60 seconds
UFIELD 8 * UserID entry field length
PFIELD 8 * Password entry field length
GLOBAL * Section for global screen definitions
* The following definitions are for when the screen needs to be cleared
CLEAR "HOLDING" * if "HOLDING", send Clear
CLEAR "MORE..." * if "MORE...", send Clear
* The following definitions are for exiting intermediate functions
NEXT? "SYSNEWS:", "@s@3" * if "SYSNEWS:", send PF3
NEXT? "F3=Exit", "@3" * if "F3=Exit", send PF3
NEXT? "3=EXIT", "@3" * if "3=EXIT", send PF3
NEXT? "3= Quit", "@3" * if "3= Quit", send PF3
NEXT? "PF12 Return", "@c" * if "PF12 Return", send PF12
LOGON * Section for logon screen definitions
START "MSG10", "@V2 @u@E" * Start screen
* if found, send V2," ",UID,Enter
HNAVL "may be down.", "help@E@S@4" * Host not available error screen
* if found, send "help", Enter,
* Wait 2 seconds, send F4
UINV "not in CP directory", "logoff@E" * UserID Invalid error screen
* if found, send "logoff",Enter
NEXT "Enter your password", "@p@E" * Required next screen
* if found, send PW,Enter
STOP? "Ready;" * Conditional stop screen
ULOGD "Already logged on", "logoff@E" * UserID is already logged on
* if found, send "logoff",Enter
PINV "incorrect password", "logoff@E" * Password invalid error screen
* if found, send "logoff",Enter
PEXP "PASSWORD EXPIRED", "logoff@E" * Password expired error screen
* if found, send "logoff",Enter
PWRN "PASSWORD WILL EXPIRE" * Password expiring warning screen
NEXT? "CP READ", "b@E" * Optional next screen
* if found, send "b",Enter
STOP? "Ready;" * Conditional stop screen
STOP "RUNNING" * Required stop screen
PASSWORD * Section for password change screen definitions
* Password change screen definitions if logged off
START "MSG10", "@V2 @u@E" * Start screen
* if found, send V2," ",UID,Enter
HNAVL "may be down.", "help@E@S@4" * Host not available error screen
* if found, send "help", Enter,
* Wait 2 seconds, send F4
UINV "not in CP directory", "logoff@E" * UserID Invalid error
* if found, send "logoff",Enter
NEXT "Enter your password", "@p/@n/@n@E" * Required next screen
* if found, send
* PW,"/",NPW,"/",NPW,Enter
ULOGD "Already logged on", "logoff@E" * UserID is already logged on
* if found, send "logoff",Enter
PINV "incorrect password", "logoff@E" * Password invalid error screen
* if found, send "logoff",Enter
NINV "NEW PASSWORD INVALID", "logoff@E" * NewPassword invalid error screen
* if found, send "logoff",Enter
NEXT? "CP READ", "b@E@E" * Optional next screen
* if found, send "b",Enter,Enter
NEXT "Ready;", "logoff@E" * Required next screen
* if found, send "logoff",Enter
STOP "MSG10" * Required stop screen
* Password change screen definitions if logged on and in native CMS
START "RUNNING", "password@E" * Start screen
* if found, send "password",Enter
NEXT "U P D A T E", "@P@N@N@E" * Required next screen
* if found, send PW,NPW,NWP,Enter
PNINV "RACF did not like", "@C" * PW or NewPW invalid error screen
* if found, send Clear
STOP "Ready;" * Required stop screen
LOGOFF * Section for logoff screen definitions
START "RUNNING", "logoff@E" * Start screen
* if found, send "logoff",Enter
STOP "MSG10" * Required stop screen
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
ΓòÉΓòÉΓòÉ 7.3.6.3. NSCVMOV.HIF ΓòÉΓòÉΓòÉ
NSCVMOV.HIF is a host information file for a VM Host System with OfficeVision.
It is designed for the user who starts OfficeVision from PROFILE EXEC. Thus it
defines start and stop screens for the OfficeVision menus. It uses the
OfficeVision menus (PF11 and PF5) to change the host password. To signon to the
host, it sends the node id of the host (you specify this as a HIF Variable in
the HOST definition) followed by your User ID. NSCVMOV.HIF has two HIF
Variables:
V1 defines the host session id (e.g. V1=A)
V2 defines the node id sent for a signon with the userid (e.g. V2=AUSVM1)
The following is an example of a HOST definition using this host information
file.
USERID=PDQUEUE
Host,EMULATOR,Name=VM1,ON,HIF=d:\nsc\nscvmov.hif,V1=A,V2=AUSVM1
In this example, "V1=A" specifies host emulator session A will be used, and
"V2=AUSVM1" specifies that the initial connection to the host will be made by
sending the string "AUSVM1 PDQUEUE" to the emulator.
NSCVMOV.HIF
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
* This is a sample host information file for a VM host system with OfficeVision
* It requires the following HIF Variables in the NSC configuration file:
* V1=host session id (e.g. V1=A or V1=A-E)
* V2=the first command sent for a signon with the userid (e.g. V2=AUSVM1)
CONFIGURATION * Section for configuration options
SESSION @V1 * Host session id from HIF Variable V1
HOSTWAIT 5 * Wait for Host up to 5 seconds
SESSIONWAIT 60 * Wait for Session up to 60 seconds
UFIELD 8 * UserID entry field length
PFIELD 8 * Password entry field length
GLOBAL * Section for global screen definitions
* The following definitions are for when the screen needs to be cleared
CLEAR "HOLDING" * if "HOLDING", send Clear
CLEAR "MORE..." * if "MORE...", send Clear
CLEAR "Messages Waiting" * if "Messages Waiting", send Clear
* The following definitions are for exiting intermediate functions
NEXT? "SYSNEWS:", "@s@3" * if "SYSNEWS:", send PF3
NEXT? "FEEDBACK", "@3" * if "SYSNEWS:", send PF3
NEXT? "In-Basket:", "@3" * if "In-Basket", send PF3
NEXT? "F3=Exit", "@3" * if "F3=Exit", send PF3
NEXT? "3=EXIT", "@3" * if "3=EXIT", send PF3
NEXT? "3= Quit", "@3" * if "3= Quit", send PF3
NEXT? "PF12 Return", "@c" * if "PF12 Return", send PF12
NEXT? "PF12= Return", "@c" * if "PF12= Return", send PF12
NEXT? "PF12 Return", "@c" * if "PF12 Return", send PF12
NEXT? "MENU 2", "@b" * if "MENU 2", send PF11
LOGON * Section for logon screen definitions
START "MSG10", "@V2 @u@E" * Start screen
* if found, send V2," ",UID,Enter
HNAVL "may be down.", "help@E@S@4" * Host not available error screen
* if found, send "help", Enter,
* Wait 2 seconds, send F4
UINV "not in CP directory", "logoff@E" * UserID Invalid error screen
* if found, send "logoff",Enter
NEXT "Enter your password", "@p@E" * Required next screen
* if found, send PW,Enter
STOP? "MENU 1" * Conditional stop screen
ULOGD "Already logged on", "logoff@E" * UserID is already logged on
* if found, send "logoff",Enter
PINV "incorrect password", "logoff@E" * Password invalid error screen
* if found, send "logoff",Enter
PEXP "PASSWORD EXPIRED", "logoff@E" * Password expired error screen
* if found, send "logoff",Enter
PWRN "PASSWORD WILL EXPIRE" * Password expiring warning screen
NEXT? "CP READ", "b@E" * Optional next screen
* if found, send "b",Enter
STOP "MENU 1" * Required stop screen
PASSWORD * Section for password change screen definitions
* Password change screen definitions if logged off
START "MSG10", "@V2 @u@E" * Start screen
* if found, send V2," ",UID,Enter
HNAVL "may be down.", "help@E@S@4" * Host not available error screen
* if found, send "help", Enter,
* Wait 2 seconds, send F4
UINV "not in CP directory", "logoff@E" * UserID Invalid error
* if found, send "logoff",Enter
NEXT "Enter your password", "@p/@n/@n@E" * Required next screen
* if found, send
* PW,"/",NPW,"/",NPW,Enter
ULOGD "Already logged on", "logoff@E" * UserID is already logged on
* if found, send "logoff",Enter
PINV "incorrect password", "logoff@E" * Password invalid error screen
* if found, send "logoff",Enter
NINV "NEW PASSWORD INVALID", "logoff@E" * NewPassword invalid error screen
* if found, send "logoff",Enter
NEXT? "CP READ", "b@E@E" * Optional next screen
* if found, send "b",Enter,Enter
NEXT "MENU 1", "logoff@E" * Required next screen
* if found, send "logoff",Enter
STOP "MSG10" * Required stop screen
* Password change screen definitions if logged on and in OfficeVision
START "MENU 1", "@b" * Start screen
* if found, send PF11
NEXT "MENU 2", "@5" * Required next screen
* if found, send PF5
NEXT "CHANGE PASSWORD", "@N@N@P@E" * Required next screen
* if found, send NPW,NPW,PW,Enter
PNINV "Password not changed", "@c@b" * PW or NewPW invalid error screen
* if found, send PF12,PF11
NINV "must be different", "@c@b" * NewPassword invalid error screen
* if found, send PF12,PF11
NEXT "MENU 2", "@b" * Required next screen
* if found, send PF11
STOP "MENU 1" * Required stop screen
LOGOFF * Section for logoff screen definitions
START "MENU 1", "logoff@E" * Start screen
* if found, send "logoff",Enter
STOP "MSG10" * Required stop screen
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
ΓòÉΓòÉΓòÉ 7.3.6.4. NSCOS400.HIF ΓòÉΓòÉΓòÉ
NSCOS400.HIF is a host information file for an OS/400 System. It defines start
and stop screens for the OS/400 menu system. It uses the chgpwd command to
change the password. To signon to the host, it uses the OS/400 initial Sign On
screen. NSCOS400.HIF has one HIF Variable:
V1 defines the host session id (e.g. V1=A)
The following is an example of HOST definition using this host information
file.
USERID=PDQUEUE
Host,EMULATOR,Name=AS400,ON,HIF=d:\nsc\nscos400.hif,V1=D
In this example, "V1=D" specifies host emulator session D will be used for the
host "AS400".
NSCOS400.HIF
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
* This is a sample host information file for an OS/400 host system
* It requires the following HIF Variables in the NSC configuration file:
* V1=host session id (e.g. V1=C)
CONFIGURATION * Section for configuration options
SESSION @V1 * Host session id from HIF Variable V1
HOSTWAIT 5 * Wait for Host up to 5 seconds
SESSIONWAIT 60 * Wait for Session up to 60 seconds
UFIELD 10 * UserID entry field length
PFIELD 10 * Password entry field length
LOGON * Section for logon screen definitions
START "Sign On", "@U@P@E" * Start screen
* if found, send UID,PW,Enter
STOP? "===>" * Conditional stop screen
UINV "does not exist", "@C" * UserID Invalid error screen
* if found, send Clear
PINV "Password not correct", "@C" * Password invalid error screen
* if found, send Clear
PEXP "Password has expired", "@3@sY@E" * Password expired error screen
* if found, send PF3,"Y",Enter
PWRN "until password expire","@3" * Password expiring warning screen
* if found, send PF3
STOP "===>" * Required stop screen
PASSWORD * Section for password change screen definitions
* Password change screen definitions if logged off
START "Sign On", "@U@P@E" * Start screen
* if found, send UID,PW,Enter
UINV "does not exist", "@C" * UserID Invalid error screen
* if found, send Clear
PINV "Password not correct", "@C" * Password invalid error screen
* if found, send Clear
* Password change screen definitions if password has not expired
NEXT? "===>", "chgpwd@E" * Optional next screen
* if found, send "chgpwd",Enter
NEXT? "Change Password", "@P@N@N@E" * Optional next screen
* if found, send PW,NPW,NWP,Enter
PINV "Current password not", "@3@ssignoff@E" * Password invalid error screen
* if found,send PF3,"signoff",Ent
NINV "Name is not valid", "@3@ssignoff@E" * NewPW invalid error screen
* if found,send PF3,"signoff",Ent
NINV "password cannot be", "@3@ssignoff@E" * NewPW invalid error screen
* if found,send PF3,"signoff",Ent
* Password change screen definitions if password has expired
NEXT? "Password has expired", "@9" * Optional next screen
* if found, send PF9
NEXT? "Change Password", "@P@N@N@E" * Optional next screen
* if found, send PW,NPW,NWP,Enter
PINV "Current password not", "@3@s@3@sY@E" * Password invalid error screen
* if found,send PF3,PF3,"Y",Enter
NINV "Name is not valid", "@3@s@3@sY@E" * NewPW invalid error screen
* if found,send PF3,PF3,"Y",Enter
NINV "password cannot be", "@3@s@3@sY@E" * NewPW invalid error screen
* if found,send PF3,PF3,"Y",Enter
NEXT "===>", "signoff@E" * Required next screen
* if found, send "signoff",Enter
STOP "Sign On" * Required stop screen
* Password change screen definitions if logged on
START "===>", "chgpwd@E" * Start screen
* if found, send "chgpwd",Enter
NEXT "Change Password", "@P@N@N@E" * Required next screen
* if found, send PW,NPW,NWP,Enter
PINV "Current password not", "@3" * Password invalid error screen
* if found, send PF3
NINV "Name is not valid", "@3" * NewPassword invalid error screen
* if found, send PF3
NINV "password cannot be", "@3" * NewPassword invalid error screen
* if found, send PF3
STOP "Password changed" * Required stop screen
LOGOFF * Section for logoff screen definitions
START "===>", "signoff@E" * Start screen
* if found, send "signoff",Enter
STOP "Sign On" * Required stop screen
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
ΓòÉΓòÉΓòÉ 7.3.6.5. NSCIIN.HIF ΓòÉΓòÉΓòÉ
NSCIIN.HIF is a host information file for the IBM Information Network (IIN). It
defines start and stop screens for the IIN Product Selection screen. It uses
the IIN Services screens to change the IIN password. It does not support any
particular product that you may access via IIN. It can only change your
password if you are signed off, or signed on and at the IIN Product Selection
screen.
To signon to the IIN, it sends the node id for IIN, (typically "IIN", but you
specify this as a HIF Variable in the HOST definition). NSCIIN.HIF has five HIF
Variables:
V1 defines the host session id (e.g. V1=A)
V2 defines the node id sent for a signon (e.g. V2=IIN)
V3 defines the account name, plus a tab if less than 8 characters (e.g.
V3=ACCOUNT1 or V3=AUSD@T)
V4 is normally an empty string; if you want NSC to construct an extended
password for you, it is the first character for passwords (e.g. V4="" or
V4=".")
V5 is normally 8; if you want NSC to construct an extended password for
you, it must be 7 (e.g. V5=8 or V5=7)
Some IIN accounts require the use of extended passwords. Extended passwords
must contain one of the following special characters:
. ? ; ' " ( ) : &
Since many security facilities do not allow these characters in passwords, we
have added some special provisions to this host information file to allow you
to keep your IIN password in sync if you must use extended passwords. There
are three different ways that you can choose for using NSCIIN to access the
IIN:
1. IIN password is not extended, and the same password is used everywhere.
In this case, you should define:
MAXPWLEN=8
HOST,EMULATOR,...V4="",V5=8
2. IIN password is extended, and the same password is used everywhere (this
requires that all locations support your extended password). In this
case, you should define:
MAXPWLEN=8
CHARSET=.?;'"():&
HOST,EMULATOR,...,V4="",V5=8
Adding the CHARSET definition enables the entering of the extended
characters in NSC.
3. IIN password is extended, and the password excluding the extended
character is used everywhere else. In this case, you should define:
MAXPWLEN=7
HOST,EMULATOR,...,V4=".",V5=7
You can choose any of the extended characters for V4. NSC will always
prefix your password with this character before sending it to the
emulator for IIN. You may have to first change your password to a
password that conforms to this syntax without using NSC before allowing
NSC to perform signons or change your password. You do not need the
CHARSET definition, since you never actually enter the extended character
in NSC. The length of the password field is set to 7 so that NSC will
send a Tab key with your password only if your password is less than 7
characters (the extended character goes into the password field on the
screen, but NSC does not count it as part of the password length).
The following is an example of a HOST definition using this host information
file.
USERID=PDQUEUE
MAXPWLEN=8
Host,EMULATOR,Name=IIN,HIF=d:\nsc\nsciis.hif,V1=A,V2=iin,V3=ACCT@T,V4="",V5=8
In this example, "V1=A" specifies host emulator session A will be used for the
host "IIN", and "V2=iin" specifies that the initial connection to the IIN will
be made by sending the string "iin" to the emulator. "V3=ACCT@T" specifies the
account as "ACCT", and includes a tab character since it is less than eight
characters long. Since this account does not require extended passwords, V4 is
set to an empty string and V5 is set to 8.
NSCIIN.HIF
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
* This is a sample host information file for the IBM Information Network.
* It requires the following HIF Variables in the NSC configuration file:
* V1=host session id (e.g. V1=A or V1=A-E)
* V2=the first command sent for a signon (e.g. V2=iin)
* V3=the account name, plus a tab if less than 8 characters (e.g. V3=AUSD@T)
* V4=first character of PW if extended PW reqd (e.g. V4="" or V4=".")
* V5=password field length: 7 if using extended PWs, 8 otherwise (e.g. V5=7)
CONFIGURATION * Section for configuration options
SESSION @V1 * Host session id from HIF Variable V1
HOSTWAIT 5 * Wait for Host up to 5 seconds
SESSIONWAIT 60 * Wait for Session up to 60 seconds
UFIELD 7 * UserID entry field length
PFIELD @V5 * Password entry field length
GLOBAL * Section for global screen definitions
* The following definitions are for when the screen needs to be cleared
* The following definitions are for exiting intermediate functions
LOGON * Section for logon screen definitions
START "MSG10", "@V2@E" * Start screen
* if found, send V2,Enter
NEXT "SVM0201P", "@V3@U@V4@p@E" * Required next screen
* if found,
* send V3,UID,V4,PW,Enter
STOP? "SVM0401P" * Conditional stop screen
UINV "account and userid", "@T@T@Tlogoff@E" * UserID Invalid error screen
* if found,
* send Tab,Tab,Tab,"logoff",Enter
PINV "an extended password", "@Tlogoff@E" * Password invalid error
* if found,
* send Tab,Tab,Tab,"logoff",Enter
PINV "a valid password", "@Tlogoff@E" * Password invalid error
* if found,
* send Tab,Tab,Tab,"logoff",Enter
PEXP "SVM3201P", "@3@T@T@Tlogoff@E" * Password expired error
* if found, send PF3,
* Tab,Tab,Tab,"logoff",Enter
STOP "SVM0401P" * Required stop screen
PASSWORD * Section for password change screen definitions
* Password change screen definitions if logged off
START "MSG10", "iin@E" * Start screen
* if found, send "iin",Enter
NEXT "SVM0201P", "@V3@U@V4@p@E" * Required next screen
* if found,
* send V3,UID,V4,PW,Enter
UINV "account and userid", "@T@T@Tlogoff@E" * UserID Invalid error screen
* if found,
* send Tab,Tab,Tab,"logoff",Enter
PINV "an extended password", "@T@T@Tlogoff@E" * Password invalid error
* if found,
* send Tab,Tab,Tab,"logoff",Enter
PINV "a valid password", "@T@T@Tlogoff@E" * Password invalid error
* if found,
* send Tab,Tab,Tab,"logoff",Enter
* Password change screen definitions if password has not expired
* If password has expired, system goes directly to the Required next screen
NEXT? "SVM0401P", "@5" * Conditional next screen
* if found, send PF5
NEXT? "SVM1501P", "PAS@E" * Conditional next screen
* if found, send "PAS",Enter
NEXT "SVM3201P", "@V4@P@V4@N@V4@N@E" * Required next screen
* if found,
* send V4,PW,V4,NPW,V4,NPW,Enter
PNINV "an extended password", "@3@3@3@T@T@Tlogoff@E"
* PW or NewPW invalid error screen
* if found, send PF3,PF3,PF3
* Tab,Tab,Tab,"logoff",Enter
PNINV "a valid password", "@3@3@3@T@T@Tlogoff@E"
* PW or NewPW invalid error screen
* if found, send PF3,PF3,PF3
* Tab,Tab,Tab,"logoff",Enter
NINV "new password was inv", "@3@3@3@T@T@Tlogoff@E"
* NewPW invalid error screen
* if found, send PF3,PF3,PF3
* Tab,Tab,Tab,"logoff",Enter
NEXT "successfully changed", "@3","@3@3@3@T@T@Tlogoff@E"
* Required next screen
* if found send PF3, else PF3,PF3
* PF3,Tab,Tab,Tab,"logoff",Enter
NEXT? "SVM1501P", "@3" * Conditional next screen
* if found, send PF3
NEXT "SVM0401P", "@3@T@T@Tlogoff@E" * Required next screen
* if found, send PF3,
* Tab,Tab,Tab,"logoff",Enter
STOP "MSG10" * Required stop screen
* Password change screen definitions if logged on at the main menu
START "SVM0401P", "@5" * Start screen
* if found, PF5
NEXT "SVM1501P", "PAS@E" * Required next screen
* if found, "PAS",Enter
NEXT "SVM3201P", "@V4@P@V4@N@V4@N@E" * Required next screen
* if found,
* send V4,PW,V4,NPW,V4,NPW,Enter
PNINV "an extended password", "@3@3" * PW or NewPW invalid error screen
* if found, send PF3,PF3
PNINV "a valid password", "@3@3" * PW or NewPW invalid error
* if found, send PF3,PF3
NINV "new password was inv", "@3@3" * NewPW invalid error screen
* if found, send PF3,PF3
NEXT "successfully changed", "@3@3","@3@3"* Required next screen
* send PF3,PF3
STOP "SVM0401P" * Required stop screen
LOGOFF * Section for logoff screen definitions
START "SVM0401P", "@3@T@T@Tlogoff@E" * Start screen
* if found, send PF3,
* Tab,Tab,Tab,"logoff",Enter
STOP "MSG10" * Required stop screen
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
ΓòÉΓòÉΓòÉ 7.4. Configuring APPC ΓòÉΓòÉΓòÉ
NSC can communicate with a host computer program using APPC. (APPC is a
communication protocol that is used by programs to talk to each other.) The
host computer programs that can use APPC to talk to NSC are described in Host
Systems. Before NSC and the host program can talk, network definitions must be
done at the personal computer and at the host computer. The following
information will help you make those definitions.
You can use APPC host connections from either an NSC OS/2 Client or an NSC
Server. Making your APPC connection at an NSC Server requires less work for you
and your host system communication programmer. If the APPC connection is done
over an expensive communications circuit, you may also reduce your circuit
cost. You can have APPC password change operations done for either an NSC DOS
or OS/2 Client by an NSC Server by placing these two statements in the client's
NSC configuration file:
SERVER,NAME=....
HOST,NAME=....,APPC
Using an NSC Server means you must make the Communications Manager definitions
for only the server workstation (not every client). The same thing applies to
the host computer. Each workstation (client) having an APPC connection requires
a host system definition.
Browse through this subsection for planning purposes, then contact your host
system communication programmer for help with the host computer definitions.
The definitions you make at the personal computer must fit with those made at
your host computer. You may then want to review the information in detail and
proceed with your definitions.
The personal computer definitions must be done with the Communications Manager.
See Personal Computer Definitions.
The host computer definitions may involve NCP, VTAM, and CICS or other host
computer software. After reading about the personal computer definitions, you
will find the host computer definition information and some host examples in
Matching the Host and PC Definitions.
ΓòÉΓòÉΓòÉ 7.4.1. Personal Computer Definitions ΓòÉΓòÉΓòÉ
You must define several Communications Manager configuration profiles to effect
the APPC connection at the personal computer. Figure "PC APPC Profiles" depicts
the relationship among the various APPC profiles you will define.
PC APPC Profiles
NSC configuration file
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéHOST..=<host-name>,APPC Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Γöé ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇ Γöé ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé APPC Partner LU Profile Γöé
Γöé Γöé <PLU alias> Γöé
Γöé Γöî V ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé
Γöé Γöé...<LU alias>...<Mode Name>...<Initial Session Limit>Γöé Γöé
Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Γöé ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Γöé ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Γöé ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé
Γöé Γöé Γöé Γöé Γöé
Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÉ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé
Γöé Γöé APPC LU Profile Γöé Γöé Γöé
Γöé Γöé <LU alias> Γöé Γöé Γöé
Γöé ΓöîΓöÇΓöÇΓöÇΓöÇ V ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé
Γöé Γöé.............<LU Name>..Γöé Γöé Γöé Γöé
Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé Γöé Γöé
Γöé Γöé Γöé Γöé
Γöé APPC Transmission Service Mode ProfileΓöé Γöé
Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé Γöé
Γöé Γöé <Mode Name> Γöé Γöé
Γöé ΓöîΓöÇΓöÇΓöÇΓöÇ V ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé
Γöé Γöé........................Γöé Γöé Γöé
Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé Γöé
Γöé Γöé Γöé
Γöé APPC Initial Session Limit Profile Γöé Γöé
Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé
Γöé Γöé <Initial Session Limit> Γöé
Γöé ΓöîΓöÇΓöÇΓöÇΓöÇ V ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé
Γöé Γöé........................Γöé Γöé
Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé
Γöé Γöé
Γöé Communications Manager Configuration Definitions Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
The APPC connection starts with your NSC configuration file. The HOST option in
the NSC configuration file defines a host-name. The value for host-name is the
name of an APPC Partner LU Profile. The APPC Partner LU Profile in turn
identifies three other APPC profiles.
Use any of the following methods to define the options:
Copy NSC provides a sample Communications Manager configuration file that
you can modify to meet your configuration requirements. If you have
just installed the Communications Manager, this is probably the
fastest and easiest way to get started. See Using the Sample for a
description of this process.
Merge You can merge the NSC sample Communications Manager configuration
file profiles into another Communications Manager configuration
file. If you have already configured Communications Manager for your
network, this may the easiest way to get started. See Merging the
Sample for a description of this process.
New You can create a new Communications Manager configuration file. See
APPC Definitions for a description of this process.
ΓòÉΓòÉΓòÉ 7.4.1.1. Using the Sample ΓòÉΓòÉΓòÉ
To use the sample OS/2 EE 1.3 Communications Manager configuration file, follow
these steps:
1. Use the OS/2 COPY command to copy the NSC sample Communications Manager
configuration file into CMLIB. For example:
COPY C:\TOOLS\NSCSAMPL.CFG C:\CMLIB\MYOWN.CFG
NOTE You must provide the path locations to the sample file and to CMLIB.
The location of the sample file is where NSC was installed. To determine
the location of CMLIB, enter PATH at the OS/2 command prompt and determine
the path from the information presented.
2. If you are using Communications Manager ES 1.0, follow these steps to
upgrade the configuration file:
a) Switch to the Communications Manager task window.
b) At the Main Menu select the Advanced pulldown and the Upgrade
configuration files option.
c) When prompted, enter the the name of the file you created with the
copy in Step 1.
When prompted for a target file name, you can reuse the source file
by specifying the same name.
When prompted, enter a report file name.
3. See Matching the Host and PC Definitions to customize the configuration
file. If your host connection supports APPC but is not LAN Token Ring,
then add the host link definition (DLC profile) and change the DLC type
in the APPC Partner LU Profile.
ΓòÉΓòÉΓòÉ 7.4.1.2. Merging the Sample ΓòÉΓòÉΓòÉ
To merge the sample OS/2 EE 1.3 Communications Manager configuration file,
follow these steps:
1. Use the OS/2 COPY command to copy the NSC sample Communications Manager
configuration file into CMLIB. For example:
COPY C:\TOOLS\NSCSAMPL.CFG C:\CMLIB\MYOWN.CFG
NOTE You must provide the path locations to the sample file and to CMLIB.
The location of the sample file is where NSC was installed. To determine
the location of CMLIB, enter PATH at the OS/2 command prompt and determine
the path from the information presented.
2. Switch to the Communications Manager task window.
3. If you are using Communications Manager ES 1.0, follow these steps to
upgrade the configuration file:
a) At the Main Menu select the Advanced pulldown and the Upgrade
configuration files option.
b) When prompted, enter the the name of the file you created with the
copy in Step 1.
When prompted for a target file name, you can reuse the source file
by specifying the same name.
When prompted, enter a report file name.
4. At the Communications Manager Main Menu select the Advanced pulldown and
the Configuration option.
5. When prompted, enter the name of a Communications Manager configuration
file. You should then see the Communication Configuration Menu.
6. Select the Configuration file utilities.
7. The Configuration File Utilities menu should be displayed. Use the
options provided to copy the APPC profiles from the NSC sample file you
upgraded in Step 3b or that you copied in Step 1.
8. See Matching the Host and PC Definitions to customize the configuration
file. If your host connection supports APPC but is not LAN Token Ring,
then add the host link definition (DLC profile) and change the DLC type
in the APPC Partner LU Profile.
ΓòÉΓòÉΓòÉ 7.4.1.3. APPC Definitions ΓòÉΓòÉΓòÉ
If you have defined your data link connection profiles, follow these steps to
make the APPC definitions shown in Figure "PC APPC Profiles".
1. Switch to the Communications Manager task window.
2. At the Main Menu select the Advanced pulldown and specify the
Configuration option.
3. You will be prompted to specify the name of a Communications Manager
configuration file. After you select the configuration file to change,
you should see the Communication Configuration Menu.
4. Select the SNA feature profiles option.
5. Select the options in the SNA Feature Configuration menu to define the
APPC profiles.
HINT: It is easier to make these definitions from the bottom up. For
example, do the Mode and LU definitions before the Partner LU definition.
6. If you are using Communications Manager ES 1.0, follow these steps after
you define the PLU, LU, and Mode:
a) Edit the Network Definition File (.NDF) associated with the
Communications Manager configuration file containing your SNA
network definitions. The NDF file is located in the APPN
subdirectory of CMLIB. The filename is the same as your
configuration file and its extension is NDF.
b) Add a CNOS definition to the NDF file. The CNOS links the LU and
Mode definitions together with the PLU. For example:
CNOS LOCAL_LU_ALIAS(TPC01PI0) <ΓöÇΓöÇLUName
PARTNER_LU_ALIAS(NSCPLU01)
MODE_NAME(LU62P ) <ΓöÇΓöÇModeName
SET_NEGOTIABLE(NO)
PLU_MODE_SESSION_LIMIT(3) <ΓöÇΓöÇSesLim
MIN_CONWINNERS_SOURCE(3)
MIN_CONWINNERS_TARGET(0)
AUTO_ACTIVATE(3);
The values specified for LOCAL_LU_ALIAS, MODE_NAME, and
PLU_MODE_SESSION_LIMIT must match those used in your Communications
Manager definitions and in your host computer definitions.
The value of PARTNER_LU_ALIAS must match the name given to the PLU
you defined.
c) After adding the CNOS definition, use the Communications Manager to
verify the configuration file.
7. See Matching the Host and PC Definitions to verify that your
configuration matches the host definitions.
ΓòÉΓòÉΓòÉ 7.4.2. Matching the Host and PC Definitions ΓòÉΓòÉΓòÉ
Be sure that the Communications Manager configuration file matches your host
definitions so that NSC can use APPC to talk to the host. This section
discusses the other Communications Manager profiles that must be coordinated
with host definitions. The profiles discussed are:
Workstation profile
LAN feature profiles
SNA feature profiles
ΓòÉΓòÉΓòÉ 7.4.2.1. Workstation profile ΓòÉΓòÉΓòÉ
The Workstation profile must specify that the SNA/APPC service be loaded. If
you do not configure your system for APPC, NSC provides an error message when
host signon is attempted.
ΓòÉΓòÉΓòÉ 7.4.2.2. LAN feature profiles ΓòÉΓòÉΓòÉ
If you use a LAN to connect to the host, then your LAN feature profile must
specify addressing information to locate the host computer. Review the LAN
feature profile and change it as needed.
NOTE In Communications Manager ES 1.0, the LAN feature profile is called
the LAN Adapter and Protocol Support.
ΓòÉΓòÉΓòÉ 7.4.2.3. SNA feature profiles ΓòÉΓòÉΓòÉ
Several profiles within the SNA feature profile definitions must match their
host counterparts. In Communications Manager ES 1.0, these profiles are stored
in the SNA network definitions part of the SNA feature profile.
The SNA profiles are:
SNA base profile (EE 1.3) or Local Node Characteristics (ES 1.0)
The PU name (EE 1.3) or Local node name (ES 1.0) for your personal
computer must match the CPNAME given in the host VTAM definition (see
CPName in Figure "VTAM Switched Major Node Definition").
The name of the Network your personal computer is attached to must match
the Network name given when VTAM is started (see NetID in Figure "Host
VTAM Startup Parameter").
APPC LU profile (EE 1.3) or Additional SNA Features Local LU (ES 1.0)
The LU name must match the LU name given in the VTAM definition (see
LUName in Figure "VTAM Switched Major Node Definition"). If your host
uses CICS, the LU name must also match the one given in the CICS
definition (see LUName in Figure "Host CICS Definition 1").
The PC's LU can be dependent or independent. The sample file defines it
as independent, because that is more flexible.
Transmission Service Mode profile (EE 1.3) or Additional SNA Features
Modes (ES 1.0)
The Mode name must match:
1. One of the LOGMODE entries defined in a LOGMODE Table (see ModeName
in Figure "Host LOGMODE Definition").
2. It should also match the LOGMODE specified for the host LU (see
ModeName in Figure "Host VTAM APPL LU Definition"). The Mode name
may also be specified in the VTAM definition (see ModeName in Figure
"VTAM Switched Major Node Definition") as the default entry.
3. If your host uses CICS, the Mode name must also match the one given
in the CICS definition (see ModeName in Figure "Host CICS Definition
2").
Initial Session Limit profile (EE 1.3) The Minimum number of contention
winners source should match the DSESLIM (see SesLim in Figure "Host VTAM
APPL LU Definition") and the SESSIONS PROPERTIES MAximum in the CICS
definition (see SesLim in Figure "Host CICS Definition 2").
You can have multiple concurrent sessions with the host to handle host
logon validations. In this case, use the personal computer as a gateway
(NSC Server) for other workstations to perform the host logon
validations.
Sessions are allocated only as needed, up to the session limit you
establish. The more sessions you establish, the faster your host logon
request is serviced when concurrent signon operations are active. A host
logon typically takes 2 seconds to process. The number of sessions you
need to provide good service depends on the number of attached
workstations and the arrival rate of their requests. Start with 3
sessions and add more if the logon service is too slow.
If you are using ES 1.0, this value does not have to be specified since
the host computer never initiates a session with the PC. The maximum
number of sessions is defined in Additional SNA Features Modes.
APPC Partner LU Profile
The Fully qualified PLU name is a required field naming the host
application program which NSC talks with (e.g., CICS). The name consists
of:
1. The network name (see NetID in Figure "Host VTAM Startup Parameter")
2. An LU Name (see PLUName in Figure "Host VTAM APPL LU Definition")
that is defined to VTAM as the host LU to talk to NSC. In the sample
configuration file, the network name is NET001 and the LU name is
TH2CICS. VTAM knows CICS by the name TH2CICS since it is specified as a
part of the VTAM definition process.
If you are not using CICS, your host VTAM programmer would define an APPL
LU similar to that shown in Figure "Host VTAM APPL LU Definition". You
must specify the same name (PLUName) as the second part of the Fully
qualified PLU name.
The Mode name field must be the same as that previously discussed about
the Transmission Service Mode profile.
If you are using ES 1.0, the association between the Partner LU and the
Local LU is accomplished via a CNOS definition in the APPN Network
Definition File (.NDF). The NDF file is located in the APPN subdirectory
of CMLIB.
ΓòÉΓòÉΓòÉ 7.4.3. Host Computer Definitions ΓòÉΓòÉΓòÉ
This section contains figures depicting the host APPC definitions needed in an
MVS/ESA environment with and without CICS/ESA. These are not the complete
definitions necessary for MVS or CICS, only the pieces that involve a PC using
APPC communications.
The definitions are:
VTAM Startup Parameters
VTAM Switched Major Node Definition
Host VTAM Partner LU Definition
Host LOGMODE Definition
Host CICS Definition 1
Host CICS Definition 2
ΓòÉΓòÉΓòÉ 7.4.3.1. VTAM Startup Parameters ΓòÉΓòÉΓòÉ
Figure "Host VTAM Startup Parameter" shows the VTAM startup parameters.
Host VTAM Startup Parameter
**********************************************************************
** **
** VTAM STARTUP OPTION - COMMON STARTUP PARAMETERS FOR: **
** **
** **
** NOTE: ATCSTR00 IS THE DEFAULT VTAM START-UP OPTIONS MEMBER **
** USED TO INITIALIZE A SPECIFIC VTAM DOMAIN AND IS ALWAYS **
** PROCESSED. IF A USER DEFINED "ATCSTRYY" IS SPECIFIED **
** (WHERE "YY" IS ANY TWO ALPHANUMERIC DIGITS), THAT **
** MEMBER IS PROCESSED BEFORE AND MERGED INTO THE ATCSTR00 **
** MEMBER. **
** **
** **
*
* BUFFER DEFINITION POSITIONAL PARAMETERS
* (BASENO,BUFSIZE,SLOWPT,F,XPANNO,XPANPT,XPANLIM)
*
CRPLBUF=(250,,10,,30,30), RPL-COPY - PAGEABLE X
IOBUF=(2000,288,3,,90,36), I/O BUFFERS - FIXED X
LFBUF=(80,,2,,5,5), LARGE GENERAL PURPOSE - FIXED X
LPBUF=(60,,1,,6,2), LARGE GENERAL PURPOSE - PAGEABLE X
SFBUF=(30,,1,,5,5), SMALL GENERAL PURPOSE - FIXED X
SPBUF=(30,,2,,8,4), SMALL GENERAL PURPOSE - PAGEABLE X
CDRSCTI=1H, DYNAMIC CDRSC RETENTION 0-32767 480 X
IOINT=28800, SUPPRESS PENDING MESSAGES 0-99999999 180 X
MAXSUBA=31, 15 X
MSGMOD=NO, INCLUDE VTAM MODULE NAME IN MESSAGES NO X
NETID=NET001, <ΓöÇΓöÇNetID ** SNI - UNIQUE NETWORK IDENTIFIER ** X
SSCPDYN=YES, ** DEFAULT ** X
DYNASSCP=YES, ** DEFAULT ** X
COLD, ** DEFAULT ** X
DYNLU=NO, ** NO DYNAMIC DEFINITION OF LUS ** X
NMVTLOG=NEVER, ** DON'T WRITE NV ALERTS TO LOGREC ** X
PROMPT, PROMPT X
NOTRACE,TYPE=VTAM, ** X
PPOLOG=YES ** VTAM COMMANDS TO NETWORK LOG NO
ΓòÉΓòÉΓòÉ 7.4.3.2. VTAM Switched Major Node Definition ΓòÉΓòÉΓòÉ
Figure "VTAM Switched Major Node Definition" shows shows part of the VTAM
definition defining a PC having an APPC LU and four 3270 LU 2 sessions.
VTAM Switched Major Node Definition
SWTRD80 VBUILD TYPE=SWNET TOKEN RING 00400003
* 19810016
TPC01P PU ADDR=04, X19820017
CPNAME=TPC01P, PU 2.1 X19821017
Γöé
CPName
MAXDATA=1033, X
SSCPFM=USSSCS, X
USSTAB=USSHATS, X
MODETAB=LOGMODES,DLOGMOD=D3270M0Q
*
TPC01P02 LU LOCADDR=2
TPC01P03 LU LOCADDR=3
TPC01P04 LU LOCADDR=4
TPC01P05 LU LOCADDR=5
TPC01PI0 LU LOCADDR=0,DLOGMOD=LU62P,USSTAB=USSLU62
Γöé Γöé
LUName ModeName
ΓòÉΓòÉΓòÉ 7.4.3.3. Host VTAM Partner LU Definition ΓòÉΓòÉΓòÉ
Figure "Host VTAM APPL LU Definition" shows shows the host application
definition for the Partner LU the PC talks to when using MVS/ESA without CICS.
The host LU name of TH2CICS was used because it matches the Fully qualified PLU
name in NSCSAMPL.CFG.
Host VTAM APPL LU Definition
TH2CICS APPL ACBNAME=Z010AP03,
Γöé
PLUName
APPC=YES,
AUTOSES=0,
DDRAINL=NALLOW,
DLOGMOD=LU62P,
Γöé
ModeName
DMINWNL=0,
DMINWNR=3,
DRESPL=NALLOW,
DSESLIM=3,
Γöé
SesLim
LMDENT=19,
MODETAB=LOGMODES,
PARSESS=YES,
SECACPT=PERSISTV,
SRBEXIT=YES
ΓòÉΓòÉΓòÉ 7.4.3.4. Host LOGMODE Definition ΓòÉΓòÉΓòÉ
Figure "Host LOGMODE Definition" shows the LOGMODE definition.
Host LOGMODE Definition
LOGMODES MODETAB
EJECT
TITLE 'SNASVCMG'
**********************************************************************
* LOGMODE TABLE ENTRY FOR RESOURCES CAPABLE OF ACTING *
* AS LU 6.2 DEVICES *
**********************************************************************
SNASVCMG MODEENT LOGMODE=SNASVCMG,FMPROF=X'13',TSPROF=X'07', *
PRIPROT=X'B0',SECPROT=X'B0',COMPROT=X'D0B1', *
RUSIZES=X'8585',ENCR=B'0000', *
PSERVIC=X'060200000000000000000300'
**********************************************************************
* LOGMODE table entry for Network SignON Coordinator *
* It functions as an LU 6.2 device. *
* The default RU Size is 1024 (1K) and supports *
* parallel sessions. *
* *
* NOTE: CICS does not support AUTOINSTALL for *
* parallel sessions. *
* *
**********************************************************************
LU62P MODEENT LOGMODE=LU62P, <ΓöÇΓöÇModeName X
TYPE=0, X
FMPROF=X'13',TSPROF=X'07', X
PRIPROT=X'B0',SECPROT=X'B0', X
COMPROT=X'50B1', X
SSNDPAC=X'00',SRCVPAC=X'00', X
RUSIZES=X'8585',PSNDPAC=X'00', X
PSERVIC=X'060200000000000000002F00'
**********************************************************************
* End of LOGMODE table entries *
**********************************************************************
MODEEND
END
ΓòÉΓòÉΓòÉ 7.4.3.5. Host CICS Definition 1 ΓòÉΓòÉΓòÉ
Figure "Host CICS Definition 1" shows part of the CICS definition referencing a
PC using APPC.
Host CICS Definition 1
OBJECT CHARACTERISTICS CICS RELEASE = 0330
CEDA VIew
Connection : C0P1
Group : OS2LU62
DEscription : LU62 CONNECTION WITH PARALLEL SESSIONS
CONNECTION IDENTIFIERS
Netname : TPC01PI0 <ΓöÇΓöÇLUName
INDsys :
REMOTE ATTRIBUTES
REMOTESystem :
REMOTEName :
CONNECTION PROPERTIES
ACcessmethod : Vtam Vtam | IRc | INdirect | Xm
Protocol : Appc Appc | Lu61
SInglesess : No No | Yes
DAtastream : User User | 3270 | SCs | STrfield | Lms
RECordformat : U U | Vb
OPERATIONAL PROPERTIES
AUtoconnect : No No | Yes | All
INService : Yes Yes | No
SECURITY
SEcurityname :
ATtachsec : Local Local | Identify | Verify | Persistent
| Mixidpe
BINDPassword : PASSWORD NOT SPECIFIED
BINDSecurity : No No | Yes
ΓòÉΓòÉΓòÉ 7.4.3.6. Host CICS Definition 2 ΓòÉΓòÉΓòÉ
Figure "Host CICS Definition 2" shows part of the CICS definition referencing a
PC using APPC.
Host CICS Definition 2
OBJECT CHARACTERISTICS CICS RELEASE = 0330
CEDA View
Sessions : C0P1001
Group : OS2LU62
DEscription : LU62 CONNECTION WITH PARALLEL SESSIONS
SESSION IDENTIFIERS
Connection : C0P1
SESSName :
NETnameq :
MOdename : LU62P <ΓöÇΓöÇModeName
SESSION PROPERTIES
Protocol : Appc Appc | Lu61
MAximum : 003 , 000 <ΓöÇΓöÇSesLim 0-999
RECEIVEPfx :
RECEIVECount : 1-999
SENDPfx :
SENDCount : 1-999
SENDSize : 01024 1-30720
RECEIVESize : 01024 1-30720
SESSPriority : 000 0-255
Transaction :
OPERATOR DEFAULTS
OPERId :
OPERPriority : 000 0-255
OPERRsl : 0 0-24,...
OPERSecurity : 1 1-64,...
PRESET SECURITY
USERId :
OPERATIONAL PROPERTIES
Autoconnect : No No | Yes | All
INservice : No | Yes
Buildchain : Yes Yes | No
USERArealen : 000 0-255
IOarealen : 00000 , 00000 0-32767
RELreq : No No | Yes
DIscreq : No No | Yes
NEPclass : 000 0-255
RECOVERY
RECOVOption : Sysdefault Sysdefault | Clearconv | Releasesess
| Uncondrel | None
RECOVNotify : None None | Message | Transaction
ΓòÉΓòÉΓòÉ 8. Using the Application Programming Interface ΓòÉΓòÉΓòÉ
The NSCRSIGN API allows both 16-bit and 32-bit applications to take full
advantage of the capabilities of Network SignON Coordinator/2 while bypassing
the NSC user interface. The request (signon or signoff), User ID, password, and
optionally a new password are provided to the API. In addition, the application
must pass the address of a procedure that will be called for each message
generated by the API. The application can display these messages, write them to
a log file, or perform other processing based on return codes associated with
each message.
For more information on using the NSCRSIGN API, refer to the following:
NSCRSIGN
OS/2 Toolkit
Compiling and Linking
Example
ΓòÉΓòÉΓòÉ 8.1. NSCRSIGN ΓòÉΓòÉΓòÉ
The NSCRSIGN function performs the signon, change password, and signoff actions
as defined in the user's NSC configuration file. For more information, refer to
the following:
Syntax
Parameters
Return Codes
Message Callbacks
ΓòÉΓòÉΓòÉ 8.1.1. Syntax ΓòÉΓòÉΓòÉ
#include "nscrsign.h"
unsigned char UserId[NSC_MAXUIDLEN+1]; /* User ID */
unsigned char Password[NSC_MAXPWLEN+1]; /* Current Password */
unsigned char NewPassword[NSC_MAXPWLEN+1]; /* New Password */
short Action; /* NSC_LOGON, NSC_LOGOFF, NSC_CHGPW */
FNMSGDSP *msgdsp; /* Message Callback Procedure */
short return_code; /* Return Code */
return_code = NSCRSIGN (UserId, Password, NewPassword, Action, NULL, msgdsp);
ΓòÉΓòÉΓòÉ 8.1.2. Parameters ΓòÉΓòÉΓòÉ
UserId (unsigned char *) -- input
The User ID for signon or signoff. If the requested action is NSC_LOGON
or NSC_CHGPW, the "UserId" parameter is required. If the requested action
is NSC_LOGOFF, the "UserId" parameter is not required, but if specified
will be used for some messages.
Password (unsigned char *) -- input
The Current Password for signon. If the requested action is NSC_LOGON or
NSC_CHGPW, the "Password" parameter is required. If the requested action
is NSC_LOGOFF, the "Password" parameter is ignored.
NewPassword (unsigned char *) -- input
The New Password for change password. If the requested action is
NSC_CHGPW, the "NewPassword" parameter is required. If the requested
action is NSC_LOGON or NSC_LOGOFF, the "NewPassword" parameter is
ignored.
Action (short) -- input
The requested action must be one of the following:
- NSC_LOGON
- NSC_CHGPW
- NSC_LOGOFF
reserved (void *) -- not used
The reserved fifth parameter should be set to NULL.
msgdsp (FNMSGDSP *) -- input
The address of the procedure for processing messages. This procedure will
be called for each error encountered while processing the request. This
procedure will also be called for each informational message normally
displayed will processing a request. If no configuration errors are
found, this procedure will be called with an empty message to indicate
processing has begun. See Message Callbacks for a description of this
procedure.
ΓòÉΓòÉΓòÉ 8.1.3. Return Codes ΓòÉΓòÉΓòÉ
NSCRSIGN returns values defined as a short integer (2 bytes).
A value of 0 indicates the call was successful. The following non-zero values
are returned:
Return Code Error
NSC_INVALID_REQUEST The "Action" parameter contains a value other
than NSC_LOGON or NSC_LOGOFF.
NSC_BAD_ADDRESS The address passed as a parameter for "msgdsp"
is invalid, or one of the addresses passed as a
parameter for "UserId" or "Password" is invalid
for a NSC_LOGON request, or one of the addresses
passed as a parameter for "UserId", "Password",
or "NewPassword" is invalid for a NSC_CHGPW
request.
NSC_BAD_PARMS The "UserID", "Password", or "NewPassword" is
longer than 8 characters. The length of the
"UserId" parameter must be less than
NSC_MAXUIDLEN. The length of the "Password" or
"NewPassword" parameter must be less than
NSC_MAXPWLEN.
NSC_NO_USERID No "UserId" parameter was specified for a
NSC_LOGON request. The "UserId" parameter is
required for this request.
NSC_NO_PW Either no "Password" parameter was specified for
a NSC_LOGON request, or no "Password" or
"NewPassword was specified for a NSC_CHGPW
request. The "Password" parameter is required
for both the NSC_LOGON and NSC_CHGPW request.
The "NewPassword" parameter is required for the
NSC_CHGPW request.
NSC_CONFIG_ERRORS Configuration Errors were found and passed to
the procedure specified by "msgdsp".
NSC_EXEC_WARNINGS Execution Warnings were encountered and passed
to the procedure specified by "msgdsp".
NSC_EXEC_ERRORS Execution Errors were encountered and passed to
the procedure specified by "msgdsp".
ΓòÉΓòÉΓòÉ 8.1.4. Message Callbacks ΓòÉΓòÉΓòÉ
Errors from the NSCRSIGN API are reported to the caller via a message callback
procedure as each location defined in an NSC configuration file is processed.
The address of this procedure is passed as a parameter to NSCRSIGN. This saves
the NSCRSIGN API from having to interact with the user, and allows the
application to be a either a full screen or PM application.
The message callback procedure should be defined as follows:
void NSC_DLL_ENTRY
dspmsg (short config_index,
short return_code,
short reserved,
unsigned char * NSCPTR message_text)
This procedure is passed the following parameters:
config_index (short) -- input
The index of the LOCAL, LANSERVER, HOST, or SERVER definition being
processed from the NSC configuration file. This parameter allows
identification of a specify remote location as the source of an error.
For configuration errors that do no refer to a LOCAL, LANSERVER, HOST, or
SERVER definition, this parameter is set to 0. For informational
messages, this parameter is set to 0. The first definition has an index
of 1.
return_code (short) -- input
The return code associated with the error message. For information
messages, this parameter is set to 0. For warnings or errors, the return
code is one of the values defined in NSCRSIGN.H.
reserved (short) -- not used
This parameter should be ignored.
message_text (unsigned char * NSCPTR) -- input
The message text associated with the error or informational message. For
error message explanations see Messages.
ΓòÉΓòÉΓòÉ 8.2. OS/2 Toolkit ΓòÉΓòÉΓòÉ
The NSC OS/2 Client contains the following two toolkit files:
NSCRSIGN.LIB - a library containing the import definition for the
NSCRSIGN API.
NSCRSIGN.H - a C header file for the NSCRSIGN API
The NSCRSIGN.H file contains the C prototype for the API and the message
callback procedure, as well as return code definitions, and must be included
in the application source code. If using the IBM C Set/2 Compiler, NSC32 must
be defined prior to including this header file (for example, by using the
-DNSC32 compiler option).
The NSCRSIGN.LIB file can be linked with an application to resolve the
reference to NSCRSIGN (the API itself is in NSCAPI.DLL).
ΓòÉΓòÉΓòÉ 8.3. Compiling and Linking ΓòÉΓòÉΓòÉ
The NSCRSIGN API may be used with one of two compilers:
Microsoft(**) C 6.0
IBM C Set/2(*)
When using the Microsoft C Compiler, use the large memory model.
When using the IBM C Set/2 Compiler, specify the -DNSC32 option.
The NSCRSIGN API may require up to 12K of stack space.
Specify the NSCRSIGN.LIB file when linking.
ΓòÉΓòÉΓòÉ 8.4. Example ΓòÉΓòÉΓòÉ
The following example illustrates a call to NSCRSIGN with all messages written
to standard output. The example consists of four files:
example.def - definition file
example.c - C source file
example.mak - nmake file for Microsoft C 6.0
example2.mak - nmake file for IBM C Set/2
The "example.mak" file uses the Microsoft C 6.0 Compiler with the combined
library "llibcep.lib" and can be invoked with the following command:
nmake /F example.mak all
The "example2.mak" file uses the IBM C Set/2 Compiler with the library
"dde4sbs.lib" and can be invoked with the following command:
nmake /F example2.mak all
Note that compiler option "-DNSC32" is used in this make file to enable 32-bit
definitions in the NSCRSIGN.H header file as well as in EXAMPLE.C.
The definition file "example.def" defines EXAMPLE.EXE to be a
window-compatible protect mode executable. This program will request NSC to
perform a signon for user "USERID" with the password "PASSWORD" and using the
NSC configuration file.
EXAMPLE.DEF
NAME EXAMPLE WINDOWCOMPAT
PROTMODE
EXAMPLE.C
#include <stdio.h>
#include <stdlib.h>
#include "nscrsign.h"
void NSC_DLL_ENTRY
dspmsg (short config_index,
short return_code,
short reserved,
unsigned char * NSCPTR message_text);
int main (void);
#ifdef NSC32
#pragma linkage (dspmsg, far16 pascal)
#endif
int main ()
{
short rc;
rc = NSCRSIGN ("userid", "password", NULL, NSC_LOGON, NULL, dspmsg);
printf ("NSCRSIGN rc = %d\n", rc);
return (0);
}
void NSC_DLL_ENTRY
dspmsg (short config_index,
short return_code,
short reserved,
unsigned char * NSCPTR message_text)
{
(void) reserved;
if (message_text[0])
{
printf ("%3d %3d %s\n",
config_index, return_code, (void *) message_text);
}
}
EXAMPLE.MAK
ALL: example.exe
example.obj: example.c nscapi.h
cl /c /AL /G2s /W4 /Ox example.c
example.exe: example.obj nscapi.lib example.mak example.def
link $*, $* /M /NOD /ST:12288, $*, llibcep+os2+nscrsign, $*;
EXAMPLE2.MAK
ALL: example.exe
example.obj: example.c nscapi.h
ICC -c -Kb+ /DNSC32 example.c
example.exe: example.obj nscapi.lib example.mak example.def
link386 $*, $* /M /NOD /ST:12288, $*, dde4sbs+os2386+nscrsign, $*;
ΓòÉΓòÉΓòÉ 9. Messages ΓòÉΓòÉΓòÉ
All of the messages displayed by Network SignON Coordinator/2 are numbered, and
they are ordered accordingly as follows:
Messages 100-138
Messages 140-153
Messages 154-178
Messages 180-309
Messages 401-419
Messages 420-445
Messages displayed by the operating system are described in
System Error Messages
Network SignON Coordinator/2 displays several different types of messages,
each containing different information to explain the situation.
An in-progress message is displayed as the action requested for each
configuration file definition begins execution. This message is: NSC0106 The
requested action is in progress.
Execution completion messages are displayed as the action requested for each
configuration file definition succeeds or fails.
Data Entry error messages are displayed when the NSC Signon panel is entered
(OK is selected). For the PM interface, these messages are displayed in a
pop-up window, which must be removed before continuing. For the full screen
interface, these messages are displayed in the message area, and are cleared
when the next key is pressed. In either case, the data entry field in error is
cleared, and the entry must be re-keyed.
Configuration error messages are displayed when NSC, NSCRSON, or NSCRSOFF is
executed if any problems exist in the NSC configuration file. Network SignON
Coordinator/2 will identify as many configuration errors as it can. Most of
the configuration error messages are followed immediately by the actual line
from the configuration file that is in error. "line <nn>" in the error
messages gives the actual line number in the NSC configuration file.
ΓòÉΓòÉΓòÉ 9.1. Messages 100-138 ΓòÉΓòÉΓòÉ
NSC0100 The requested action is complete.
Explanation: The indicated action has completed successfully.
Severity: Informational
User Response: None.
NSC0101 The requested action completed, but the password will expire soon.
Explanation: The signon has completed successfully. Your password
will expire shortly. For LOCAL, APPC, and LAN Server accounts, this
warning is returned when your password will expire within 5 days.
For host emulator sessions, this warning is returned when the host
notifies you at signon of this condition (as determined by the
search string in your host information file).
Severity: Warning
User Response: Change your password.
NSC0102 The user is already signed on.
Explanation: You attempted to signon but were already signed on. For
host emulator sessions or NetWare servers, you may be signed on
under a different User ID. For IBM LAN Servers, you may be signed on
to the requested domain under a different User ID, or you may be
signed on to a different domain.
Severity: Warning
User Response: None.
NSC0103 The user has already signed off.
Explanation: You attempted to signoff when you were not signed on.
Severity: Warning
User Response: None
NSC0104 The password change completed successfully, but Signon failed.
Explanation: RACF has changed the password, however it was then
unable to complete a signon process.
Severity: Warning
User Response: If you have any subsequent problem signing on at this
location, contact the security administrator of that location.
NSC0105 The requested action has completed successfully , but the password
has expired.
Explanation: The signon has completed successfully, but the password
has expired. This error can be returned for a local logon on a LAN
Server with local security.
Severity: Warning
User Response: Change your password.
NSC0106 The requested action is in progress.
Explanation: NSC has begun processing the action you just indicated.
Severity: Informational
User Response: None.
NSC0107 The password change completed successfully, but could not Signon
again.
Explanation: The password was changed and no user is currently
signed on.
To make the change, it was necessary to signon the user whose
password was changed. There was a different user signed on before
the request was processed and NSC could not sign the original user
back on.
NSC probably had the wrong password for the original user when it
tried the Signon.
Severity: Warning
User Response: If you need to sign the original user back on, make a
Signon request with the correct password.
NSC0108 The NSC operation is complete.
Explanation: The indicated operation has completed successfully.
Severity: Informational
User Response: None.
NSC0126 The requested action completed, with warnings.
Explanation: One or more signon requests have completed with warning
conditions.
Severity: Warning
User Response: Review messages preceding this one to determine the
locations with warnings and take any further actions needed.
NSC0127 The requested action completed, with errors.
Explanation: One or more signon requests have failed with error
conditions.
Severity: Error
User Response: Review messages preceding this one to determine which
locations failed and why.
NSC0128 Error executing NSCPM.EXE.
Explanation: NSC was unable to successfully execute the PM
executable NSCPM.EXE. This message is displayed if the session for
the NSCPM.EXE program could not be started.
Severity: Error
User Response: Make sure the NSCPM.EXE program is in the same
directory as the NSC.EXE program. Reinstall the NSC OS/2 Client if
necessary.
NSC0130 The user ID is not valid.
Explanation: The User ID was not recognized.
Severity: Error
User Response: Resubmit the request with the correct User ID.
NSC0131 The user ID or password is not valid.
Explanation: The action attempted in the preceding in-progress
message failed. Possible reasons for the failure could be:
- The user ID was not recognized.
- The current password entered for signon or change password was not
valid.
- The user ID is not allowed to signon at this time.
Severity: Error
User Response: Resubmit the request with the correct User ID and
password. It the failure persists, try the signon using the normal
signon facility for the location to more precisely identify the
problem.
NSC0132 The password is not valid.
Explanation: The current password entered for signon or change
password was not valid.
Severity: Error
User Response: Resubmit the request with the correct password. If
your passwords are out of sync, change your password.
NSC0133 The password has expired.
Explanation: Your password has expired.
Severity: Error
User Response: Change your password.
NSC0134 The password or the new password is not valid.
Explanation: Either the current password entered for change password
was not valid, or the new password was not accepted. If you are
certain you entered your current password correctly, the new
password was rejected because it violated some rule for passwords.
Severity: Error
User Response: Resubmit the request with the correct current
password and a different new password. If you successfully changed
the password to the offending password at other locations, you will
need to change the password at those locations to the new password.
Both of these requests can be submitted using NSC -- simply ignore
the errors from the locations where the operation was not necessary.
NSC0135 The password cannot be changed.
Explanation: The LAN Server will not let you change your password
for one of two reasons:
- The LAN Server administrator has specified that you are not
allowed to change your own password.
- The LAN Server administrator has specified a minimum password age
before the password may be changed.
Severity: Error
User Response: Contact your LAN Server administrator to remove the
restriction, or do not attempt to change your password on the LAN
Server at this time.
NSC0136 The password change request failed. The new password is not valid.
Explanation: You attempted to change passwords, and the new password
was not accepted. The new password was rejected because it violated
some rule for passwords.
Severity: Error
User Response: Resubmit the request with a different new password.
If you successfully changed the password to the offending password
at other locations, you will need to change the password at those
locations to the new password. Both of these requests can be
submitted using NSC -- simply ignore the errors from the locations
where the operation was not necessary.
NSC0137 Error executing LOGON program.
Explanation: The installed level of UPM did not support APIs for
logon and logoff, so NSC attempted to execute the LOGON.EXE program.
An error occurred attempting this operation. The most likely causes
are:
- The appropriate software is not installed.
- The appropriate paths for the software were not set up.
Severity: Error
User Response: Either install the appropriate software, or do not
attempt to configure a LOCAL option.
NSC0138 Error executing LOGOFF program.
Explanation: The installed level of UPM did not support APIs for
logon and logoff, so NSC attempted to execute the LOGOFF.EXE
program. An error occurred attempting this operation. The most
likely causes are:
- The appropriate software is not installed.
- The appropriate paths for the software were not set up.
Severity: Error
User Response: Either install the appropriate software, or do not
attempt to configure a LOCAL option.
ΓòÉΓòÉΓòÉ 9.2. Messages 140-153 ΓòÉΓòÉΓòÉ
NSC0140 NETWKSTA.200 is not started.
Explanation: The NETWKSTA.200 device driver was not started. The
most likely cause is that the appropriate software support for
NETBIOS has not been installed.
Severity: Error
User Response: Install the appropriate software or remove the
configuration option from your configuration file.
NSC0141 The IBM LAN Requester is not started.
Explanation: The IBM LAN Requester is not started (or possibly not
installed). The request was not queued because the NSC Retry Process
was not started. If you were attempting to change passwords, your
password will be out of sync on the IBM LAN Server domain. If you
were attempting to signon, you will not be signed on to the IBM LAN
Server domain.
Severity: Error
User Response: Start the LAN Requester and resubmit the request.
If you start the NSC Retry Process at startup, failures such as this
can be queued and automatically retried when the LAN Requester has
started.
NSC0142 The IBM LAN Requester is not started. The operation has been
queued.
Explanation: The IBM LAN Requester is not started. The request was
queued to be retried. The operation will be retried by the NSC Retry
Process (see NSCRETRY - Start the NSC Retry Process). If the IBM LAN
Requester is not started and you were attempting to change
passwords, your password will be out of sync at the location
indicated in the preceding in-progress message. If you were
attempting to signon, you will not be signed on to the location.
Severity: Warning
User Response: Start the IBM LAN Requester. Once the IBM LAN
Requester has been started, check the NSC Retry Process to verify
that the operation was successfully retried. If the retry was not
successful, resubmit the request.
NSC0143 Cannot change password on additional server.
Explanation: You attempted to change your password locally on a
workstation installed as an additional server for an IBM LAN Server.
The UPM account database for an additional server is replicated from
the IBM LAN Server domain controller, and passwords can only be
modified by changing the password on the IBM LAN Server domain
controller.
Severity: Error
User Response: If you configured a LANSERVER or DOMAIN option for
the IBM LAN Server domain controller that controls your additional
server, you can ignore this error, since the password change to the
domain controller is replicated to the additional server. Otherwise,
your password on the IBM LAN Server domain controller may be out of
sync. Use a LANSERVER option for the IBM LAN Server domain
controller instead of a LOCAL option for the additional server.
NSC0144 Unable to execute IBM NET program.
Explanation: NSC either attempted to call an IBM LAN Requester
function in OS/2 or attempted to execute its NSCNET.EXE program in
order to execute a NET LOGON or NET LOGOFF command for DOS. An error
occurred attempting this operation. The most likely causes are:
- The appropriate software is not installed.
- The appropriate paths for the software were not set up.
Severity: Error
User Response: Either install the appropriate software, or do not
attempt to configure a LANSERVER or DOMAIN option.
NSC0145 IBM LAN Server logon has active sessions.
Explanation: An IBM LAN Server logoff failed because some session
has a redirected drive as the current drive. The request was not
queued because the NSC Retry Process was not started. You are not
logged off of the domain.
Severity: Error
User Response: Determine which session is using the redirected drive
and change the current drive for the session. Resubmit the request.
If you start the NSC Retry Process at startup, failures such as this
can be queued and automatically retried later.
NSC0146 IBM LAN Server logon has active sessions. The operation has been
queued.
Explanation: An IBM LAN Server logoff failed because some session
has a redirected drive as the current drive. NSC has queued your
request to be retried. The logoff will be retried by the NSC Retry
Process (see NSCRETRY - Start the NSC Retry Process). If the use of
the redirected drive by other sessions is not resolved, you will
remain logged on to the IBM LAN Server.
Severity: Warning
User Response: Determine which session is using the redirected drive
and change the current drive for the session.
Once the redirected drive is no longer in use, check the NSC Retry
Process to verify that the operation was successfully retried. If
the retry was not successful, resubmit the request.
NSC0147 <userid> is already signed on at another workstation.
Explanation: For IBM LAN Servers, you have specified 'multilogon =
no' in the IBMLAN.INI file in the C:\IBMLAN directory, and <userid>
is already signed on to this IBM LAN Server on another client
workstation. For host emulator sessions, <userid> is already signed
on to the host from another emulator session (possibly from another
workstation).
Severity: Error
User Response: For IBM LAN Servers, signoff the IBM LAN Server from
the other client workstation, or specify 'multilogon = yes' in the
IBMLAN.INI file in the C:\IBMLAN directory and restart the LAN
Requester services. For host emulator sessions, signoff the host
from the other emulator session.
NSC0148 No mailslots configured for IBM DOS LAN Requester.
Explanation: No mailslots have been configured for the IBM DOS LAN
Requester in the DOSLAN.INI file where DOS LAN Requester is
installed. Network SignON Coordinator/2 requires at least one
mailslot for the IBM DOS LAN Requester functions it uses.
Severity: Error
User Response: Edit the DOSLAN.INI file in the directory where IBM
DOS LAN Requester is installed and configure at least one mailslot.
For example, adding "/NMS:1" at the end of the configuration will
configure one mailslot. Restart the IBM DOS LAN Requester before
attempting to use Network SignON Coordinator/2.
NSC0150 NETBIOS is not installed.
Explanation: Network SignON Coordinator/2 could not connect to an
NSC Server because NETBIOS is not installed. NETBIOS is included as
part of PCLP or IBM DOS LAN Requester for DOS, or as part of IBM
OS/2 LAN Requester, IBM OS/2 LAN Server, or IBM OS/2 Communications
Manager.
Severity: Error
User Response: Install the appropriate software and restart the
machine before attempting to connect to an NSC Server.
NSC0151 NETBIOS Connection error (see LOG file).
Explanation: Network SignON Coordinator/2 could not connect to an
NSC Server to perform the requested action. If the action is
Initialization, an error may have occurred accessing a configuration
file or host information file on the NSC Server. The connection
request was not queued because the NSC Retry Process was not
started. If you were attempting to change passwords, your password
will be out of sync on hosts accessed from the NSC Server and local
accounts on the NSC Server. If you were attempting to signon, your
signon password was not verified at the APPC host connected to the
NSC Server.
Severity: Error
User Response: Examine the NETBIOS messages in the LOG files on the
NSC Client and NSC Server and follow the directions indicated in the
User Response for the message to resolve the NETBIOS problem. If you
were attempting to change passwords, resubmit the password change.
If you start the NSC Retry Process at startup, failures other than
Initialization can be queued and automatically retried when the NSC
Server or host becomes available.
NSC0152 NETBIOS Connection error (see LOG file). The operation has been
queued.
Explanation: Network SignON Coordinator/2 could not connect to an
NSC Server to perform the requested action. NSC has queued the
connection request to be retried. The connection will be retried by
the NSC Retry Process (see NSCRETRY - Start the NSC Retry Process).
The operation will be retried once the connection retry is
successful. If the NETBIOS connection problem is not resolved and
you were attempting to change passwords, your password will be out
of sync on hosts accessed from the NSC Server and local accounts on
the NSC Server. If you were attempting to signon, your signon
password was not verified at the APPC host connected to the NSC
Server.
Severity: Warning
User Response: Examine the NETBIOS messages in the LOG file and
follow the directions indicated in the User Response for the message
to resolve the NETBIOS problem. If you were attempting to change
passwords, once the NETBIOS connection is established, check the NSC
Retry Process to verify that the connection was successfully
retried. If the retry was not successful, resubmit the password
change.
NSC0153 <location> is not available.
Explanation: The configured location <location> did not respond to
the preceding NSC request. The computer location is probably down
(i.e., powered off, software not started, etc.), too busy to
respond, or the location name is incorrectly specified in the NSC
configuration file.
The request was not queued because the NSC Retry Process was not
started. If you were attempting to change passwords, your password
was not changed at the location and will be out of sync with your
other locations. If you were attempting to signon, you will not be
signed on to the location.
Severity: Error
User Response: Verify the location name <location> is correct. Check
the following based on the type of location:
- LANSERVER or NSC Server, machine is powered on and software
started.
- HOST, host computer is available.
- LOCAL or NODE, the local UPM was probably busy... retry the
request.
Resolve the problem and resubmit the request. If the location is an
NSC Server, the log file on the NSC Server may help in determining
the problem.
If you start the NSC Retry Process at startup, failures other than
Initialization can be queued and automatically retried when the
location becomes available.
ΓòÉΓòÉΓòÉ 9.3. Messages 154-178 ΓòÉΓòÉΓòÉ
NSC0154 <location> is not available. The operation has been queued.
Explanation: The configured location <location> did not respond to
the preceding NSC request. The computer location is probably down
(i.e., powered off, software not started, etc.), too busy to
respond, or the location name is incorrectly specified in the NSC
configuration file.
The request was queued to be retried. The operation will be retried
by the NSC Retry Process (see NSCRETRY - Start the NSC Retry
Process). If you were attempting to change passwords, your password
was not changed at the location and will be out of sync with your
other locations. If you were attempting to signon, you will not be
signed on to the location.
Severity: Warning
User Response: Verify the location name <location> is correct. Check
the following based on the type of location:
- LANSERVER or NSC Server, machine is powered on and software
started.
- HOST, host computer is available.
- LOCAL or NODE, the local UPM was probably busy... retry the
request.
If the location is an NSC Server, the log file on the NSC Server may
help in determining the problem.
Resolve the problem before the NSC Retry Process reaches its retry
limit. Once the problem has been resolved, check the NSC Retry
Process to verify that the operation was successfully retried. If
the retry was not successful, resubmit the request.
NSC0160 Communications Manager is not started.
Explanation: Communications Manager has not been started or had not
completed its startup when your request was processed. The request
was not queued because the NSC Retry Process was not started. If you
were attempting to change passwords, your password will be out of
sync on the host. If you were attempting to signon, you will not be
signed on to the host.
Severity: Error
User Response: Start Communications Manager and retry your request.
If you start the NSC Retry Process at startup, failures such as this
can be queued and automatically retried when the NSC Server or host
becomes available.
NSC0161 Communications Manager is not started. The operation has been
queued.
Explanation: Communications Manager has not been started or had not
completed its startup when your request was processed. NSC has
queued your request to be retried. The operation will be retried by
the NSC Retry Process (see NSCRETRY - Start the NSC Retry Process).
If the problem with the host is not resolved, and you were
attempting to change passwords, your password will be out of sync on
the host; if you were attempting to signon, you will not be signed
on to the host.
Severity: Warning
User Response: Start Communications Manager.
Once Communications Manager has started, check the NSC Retry Process
to verify that the operation was successfully retried. If the retry
was not successful, resubmit the request.
NSC0162 APPC is not installed.
Explanation: APPC has not been installed with Communications
Manager.
Severity: Error
User Response: Contact the person who installed Communications
Manager and have them assist you in determining whether or not APPC
was installed with Communications Manager.
NSC0163 APPC is not available.
Explanation: APPC has not been installed or configured with
Communications Manager.
Severity: Error
User Response: Contact the person who installed Communications
Manager and have them assist you in determining whether or not APPC
was installed with Communications Manager.
NSC0164 APPC allocate error.
Explanation: APPC has indicated an allocation error that should not
be retried.
Severity: Error
User Response: The most likely cause for this error is a mismatch in
your APPC definitions and those made at the Host computer. You
should:
- Contact the person who has installed and configured NSC for
assistance.
- Review the Communications Manager Message file for any additional
information.
- See Problem Determination and make sure the DEBUG option is
enabled as it may produce additional information to help pinpoint
the problem.
NSC0165 APPC Partner LU is not defined.
Explanation: An APPC PLU could not be found or is not configured
correctly.
Severity: Error
User Response: You should have seen a more detailed message
preceding this which will better determine the cause. See Problem
Determination on how to locate the LOG, if it is not on your screen.
NSC0166 Communications Manager is not installed.
Explanation: NSC could not access the host because Communications
Manager is not installed.
Severity: Error
User Response: Install Communications Manager and restart the
machine before attempting to access a host.
NSC0167 Communications Manager must be restarted.
Explanation: NSC could not access the host because Communications
Manager has experienced a fatal error.
Severity: Error
User Response: Restart Communications Manager and retry the request.
NSC0170 EHLLAPI is not installed.
Explanation: EHLLAPI has not been installed or configured correctly.
Severity: Error
User Response: Refer to Emulator Considerations, and the emulator's
support information to determine how to install and configure
EHLLAPI support.
NSC0171 Host emulator session is in use.
Explanation: The host emulator session is in use by another user.
NSC is not able to access it. The request was not queued because the
NSC Retry Process was not started. If you were attempting to change
passwords, your password will be out of sync on the host. If you
were attempting to signon, you will not be signed on to the host.
Severity: Error
User Response: Try the operation again at a later time.
If you start the NSC Retry Process at startup, failures such as this
can be queued and automatically retried when the host session
becomes available.
NSC0172 Host emulator session is in use. The operation has been queued.
Explanation: The host emulator session is in use by another user.
NSC is not able to access it. NSC has queued your request to be
retried. The operation will be retried by the NSC Retry Process (see
NSCRETRY - Start the NSC Retry Process). If the host emulator
session does not become available, and you were attempting to change
passwords, your password will be out of sync on the host; if you
were attempting to signon, you will not be signed on to the host.
Severity: Warning
User Response: Once the host emulator session has become available,
check the NSC Retry Process to verify that the operation was
successfully retried. If the retry was not successful, resubmit the
request.
NSC0173 Host info file open/access error.
Explanation: The host information file was not found, or could not
be accessed.
Severity: Error
User Response: Refer to the relevant log file for more detailed
information. (See Problem Determination for more details). Review
the ParseHIF function's log messages near the end of the log file.
The last ParseHIF log message will tell you the host information
file name, the line number, and the column number where the file
open/access error was encountered. Verify the host information file
is named correctly, resides in the correct directory, and can be
accessed successfully.
NSC0174 Host emulator session id is invalid.
Explanation: The host emulator session id specified in the host
information file's configuration section does not correspond to a
configured/started host emulator session.
Severity: Error
User Response: Verify that the one character session id specified in
the host information file's configuration section corresponds to a
host emulator session that has been configured/started.
NSC0175 Host info file contains a syntax error.
Explanation: The host information file contains a syntax error (for
example, a misspelled keyword, a missing comma, a missing double
quote for a string, etc.).
Severity: Error
User Response: Refer to the relevant log file for more detailed
information. (See Problem Determination for more details). Review
the ParseHIF function's log messages near the end of the log file.
The last ParseHIF log message will tell you the host information
file name, the line number, and the column number of syntax error.
The contents of the host information file line in error will appear
in the log file on a following line. Edit the host information file,
correcting the syntax error.
NSC0176 Host info file contains a parameter that is not valid.
Explanation: The host information file contains a parameter that is
not valid.
Severity: Error
User Response: Refer to the relevant log file for more detailed
information. (See Problem Determination for more details). Review
the ParseHIF function's log messages near the end of the log file.
The last ParseHIF log message will tell you the host information
file name, the line number, and the column number of the parameter
in error. The contents of the host information file line in error
will appear in the log file on a following line. Edit the host
information file, correcting the parameter.
NSC0178 Host info file exceeds maximum line length.
Explanation: The host information file contains a line that exceeds
the maximum line length allowed.
Severity: Error
User Response: Refer to the relevant log file for more detailed
information. (See Problem Determination for more details). Review
the ParseHIF function's log messages near the end of the log file.
The last ParseHIF log message will tell you the host information
file name, the line number, and the column number of the line
exceeding the maximum length allowed. The contents of the host
information file line in error will appear in the log file on a
following line. Edit the host information file, reducing the length
of the line in error.
ΓòÉΓòÉΓòÉ 9.4. Messages 180-309 ΓòÉΓòÉΓòÉ
NSC0180 Cannot start from the host session's current screen.
Explanation: The host emulator session is not in one of the
specified start screens for the requested signon operation. If you
were attempting to change passwords, your password will be out of
sync on the host. If you were attempting to signon, you will not be
signed on to the host.
Severity: Error
User Response: Check the host emulator session. If the host is in a
valid start screen for the requested operation, edit the host
information file, adding a corresponding new sequence of screen
definitions, or correct an existing one. Otherwise, reset the host
emulator session to a valid start screen and try the operation
again.
NSC0181 Cannot continue from the host session's current screen.
Explanation: The host emulator session did not enter one of the
required screens for the requested signon operation. Thus, the
operation cannot be continued.
Severity: Error
User Response: Refer to the relevant log file for more detailed
information. (See Problem Determination for more details). Review
the PerfAct function's log messages near the end of the log file.
The last PerfAct log message will tell you the host screen that was
required but not encountered.
Edit the host information file, adding a corresponding new screen
definition, or correcting an existing one for the requested
operation. If the screen definition already exists and is correct,
you may need to increase the value of the configuration option
HOSTWAIT until NSC waits long enough for the host to finish changing
screens.
Check the host emulator session. If the host has not already been
reset, reset it to a valid start screen.
NSC0182 No host screen definitions configured.
Explanation: The host information file does not contain any screen
definitions for the requested operation.
Severity: Error
User Response: Edit the host information file, adding the required
screen definitions for the desired operation.
NSC0183 No available host emulator session.
Explanation: The host emulator session ids specified in the host
information file's configuration section are all either in use,
invalid, or not available.
Severity: Error
User Response: Modify the session ids specified in the host
information file's configuration section, or make sure the desired
host emulator session is configured/started.
NSC0190 An unexpected system error was encountered.
Explanation: An internal NSC function detected a software failure.
Severity: Error
User Response: Submit an NSC problem report along with your NSC
LOGs.
NSC0191 Not enough memory is available.
Explanation: Not enough memory is available to perform the desired
operation.
Severity: Error
User Response: Free up system resources. Resubmit the request.
NSC0192 User Exit could not be executed.
Explanation: NSC was unable to successfully execute the user exit
routine for the location just processed. This message is displayed
in DOS if the exit routine could not be started, or in OS/2 if the
session for a user exit program could not be started.
Severity: Error
User Response: Review the preceding messages to determine the
location definition being processed. Look in the configuration file
to determine the user exit program or command file specified for the
definition. Check the file name specification and make sure the
program or command file is in the path.
NSC0193 User Exit failed. Return code = <rc>.
Explanation: The user exit routine for the location just processed
return the return code rc to NSC.
Severity: Unknown
User Response: Review the preceding messages to determine the
location definition being processed. Look in the configuration file
to determine the user exit program or command file specified for the
definition. Consult your administrator if necessary to determine the
cause of the error.
NSC0200 You are not authorized to Signon at this time of day.
Explanation: You attempted to Signon in a time period which you have
not been authorized by the system administrator.
Severity: Error
User Response: Contact the system administrator to verify your
authorization to use the LAN Server. This may have been caused by an
incorrect clock setting on the server.
NSC0201 You are not authorized from this computer.
Explanation: You attempted to Signon from a computer which you have
not been authorized by the system administrator.
Severity: Error
User Response: Contact the system administrator to verify your
authorization.
NSC0202 Your account is empty.
Explanation: Your account either has a zero balance, no credit, or
it has been disabled by the system administrator.
Severity: Error
User Response: Contact the system administrator to reset your
account.
NSC0220 Novell NetWare not installed.
Explanation: NSC cannot access Novell NetWare to process the
request.
Severity: Error
User Response: Install NetWare or change the LANSERVER definition in
the configuration file to not specify NOVELL.
NSC0301 The User ID is too short or was not entered.
Explanation: Either you failed to enter your User ID, or you entered
a User ID that is shorter than the minimum length specified in the
configuration file for the MinUIDLen definition.
Severity: Error
User Response: Enter the correct User ID, or exit Network SignON
Coordinator/2 and modify the MinUIDLen option in the configuration
file.
NSC0302 The password is too short or was not entered.
Explanation: Either you failed to enter your password, or you
entered a password that is shorter than the minimum length specified
in the configuration file for the MinPWLen definition.
Severity: Error
User Response: Enter the correct password, or choose a different new
password, or exit Network SignON Coordinator/2 and modify the
MinPWLen option in the configuration file.
NSC0303 The User ID is too long.
Explanation: You entered a User ID that is longer than the maximum
length specified in the configuration file for the MaxUIDLen
definition.
Severity: Error
User Response: Enter the correct User ID, or exit Network SignON
Coordinator/2 and modify the MaxUIDLen option in the configuration
file.
NSC0304 The password is too long.
Explanation: You entered a password that is longer than the maximum
length specified in the configuration file for the MaxPWLen
definition.
Severity: Error
User Response: Enter the correct password, or choose a different new
password, or exit Network SignON Coordinator/2 and modify the
MaxPWLen option in the configuration file.
NSC0305 The new and confirmation passwords are not the same.
Explanation: You entered a Confirmation Password that did not match
the entered New Password. Both entries must be identical.
Severity: Error
User Response: Enter the new password correctly in both fields.
NSC0306 The current and new passwords are the same.
Explanation: You entered a New Password that was identical to the
entered Current Password.
Severity: Error
User Response: Enter a new password that is different than the
current password.
NSC0307 User ID or password contains characters that are not valid.
Explanation: You typed a character that is not valid in the User ID
or password command line parameter. For the User ID, any graphic
ASCII character is valid (ASCII controls are not valid). For
passwords, each character must either be alphanumeric or in the
character set specified by the CHARSET definition in the
configuration file (or in the default character set (#, @ or $) if
the CHARSET definition is not specified in the configuration file).
Severity: Error
User Response: Restart the command with a valid User ID and/or
password.
NSC0308 Too many command line parameters specified.
Explanation: You attempted to execute either
- "NSC ON" with more than two additional command line parameters
(valid parameters for ON are User ID and Password), or
- "NSC OFF" with more than one additional command line parameters
(the only valid parameter for OFF is User ID), or
- "NSC CHGPW" with more than three additional command line
parameters (valid parameters for CHGPW are User ID, Current Password
and New Password).
Severity: Error
User Response: Restart the command with a valid number of command
line parameters.
NSC0309 A command line parameter that is not valid <parm> was specified.
Explanation: You specified something other than "ON", "OFF" or
"CHGPW" as the first command line parameter.
Severity: Error
User Response: Restart the command with a valid parameter.
ΓòÉΓòÉΓòÉ 9.5. Messages 401-419 ΓòÉΓòÉΓòÉ
NSC0401 Actions are not available because of errors.
Explanation: NSC encountered errors during initialization, or
detected a configuration error.
Severity: Error
User Response: Close the window to exit NSC. Correct the errors and
restart the program.
NSC0403 <pppp> not allowed with definition on line <nn> of NSC config file.
Explanation: One of the following has occurred:
- You specified the APPC, EMULATOR or EHLL parameter for a
LANSERVER, DOMAIN, LOCAL, NODE or SERVER definition. These
parameters can be used only with a HOST definition.
- You specified the IBM or NOVELL parameter for a DOMAIN, HOST,
LOCAL, NODE or SERVER definition. These parameters can be used only
with a LANSERVER definition.
- You specified a HIF parameter or HIF Variable parameter for a
LANSERVER, DOMAIN, LOCAL, NODE or SERVER definition, or a HOST
definition of type APPC. The HIF parameter and HIF Variable
parameter are only allowed with a HOST definition of type EMULATOR.
Severity: Error
User Response: Delete the parameter or change the definition.
NSC0404 <def> definition on line <nn> of NSC config file not allowed after a
SERVER definition.
Explanation: You placed a NODE, LANSERVER or DOMAIN definition after
a SERVER definition in your configuration file. Definitions for node
logons or LAN Servers can be configured only for the local
workstation, and must precede all SERVER definitions.
Severity: Error
User Response: For node logons, place the NODE definition preceding
all SERVER definitions. For password synchronization to the LAN
Server, place the LANSERVER definition preceding all SERVER
definitions; the definition would then cause NSC to process password
changes for the LAN Server from the local workstation.
NSC0405 Configuration file <config-file> was not found.
Explanation: The configuration file identified by config-file was
not found in the current directory or in the DPATH.
Severity: Error
User Response: Either change the current directory before executing
or calling NSC or modify the DPATH.
NSC0406 EXIT or EXITID not allowed with SERVER definition on line <nn> of
NSC config file.
Explanation: You specified an EXIT or EXITID parameter on a SERVER
definition. No signon or password synchronization is associated with
the SERVER definition. Because no action is taken that can be passed
on to an exit routine, the EXIT or EXITID parameter is not allowed.
Severity: Error
User Response: Remove the EXIT or EXITID parameter from the SERVER
definition. If a user exit needs the results of access to the local
UPM on the Server, specify the EXIT or EXITID parameter on a LOCAL
definition following the SERVER definition.
NSC0407 Configuration definition on line <nn> of NSC config file is not
valid.
Explanation: NSC did not recognize the definition on the indicated
line from the configuration file.
Severity: Error
User Response: Either correct the spelling of the definition, or
start the line with an asterisk if the line should be ignored.
NSC0408 Definition or parameter value <vvvv> on line <nn> of NSC config file
is not valid.
Explanation: The value vvvv is outside the range of valid values for
this definition or parameter on the indicated line from the
configuration file For Menu Parameter Length definitions (MinUIDLen,
MaxUIDLen, MinPWLen, and MaxPWLen), valid values are 1 to 8. For
Beep and ConfirmExit definitions, valid values or ON and OFF. For
the ID parameter, valid values are 1 to 40. For the ExitID
parameter, the value must match a value specified in an ID parameter
for an Exit definition.
Severity: Error
User Response: Correct the value.
NSC0409 The parameter <pppp> on line <nn> of NSC config file is not valid.
Explanation: The parameter pppp is not a valid parameter for this
definition.
- For LOCAL definitions, the only valid parameters are ON, USERID,
EXIT and EXITID.
- For NODE definitions, the only valid parameters are ON, NAME,
USERID, EXIT and EXITID.
- For LANSERVER definitions, the only valid parameters are ON, NAME,
IBM, NOVELL, USERID, EXIT and EXITID.
- For DOMAIN definitions, the only valid parameters are ON, NAME,
USERID, EXIT and EXITID.
- For HOST definitions, the only valid parameters are ON, NAME,
APPC, EMULATOR, USERID, EXIT and EXITID.
- For SERVER definitions, the only valid parameter is NAME.
- For EXIT definitions, the only valid parameters are NAME, ID, FG,
BG, WAIT, NOWAIT, NOMSGS, MSGS, RC, and NORC.
- For GETDEFS definitions, the only valid parameter is SERVER.
Severity: Error
User Response: Remove the invalid text from the definition, or
insert a space in the definition prior to the text that should be
ignored.
NSC0410 LOCAL definition not allowed before SERVER definition in DOS on line
<nn> of NSC config file.
Explanation: You defined a LOCAL definition preceding a SERVER
definition on the DOS Client. NSC does not support local signons for
your NSC DOS Client.
Severity: Error
User Response: Remove the LOCAL definition. A NODE definition is
valid on a DOS Client and can be used to run a User Exit routine.
NSC0411 MINPWLEN cannot be greater that MAXPWLEN.
Explanation: You specified a value for the minimum length of a
password (MINPWLEN) that is greater than the value you specified for
the maximum length of a password (MAXPWLEN).
Severity: Error
User Response: Either change the MINPWLEN Option value to be less
than or equal to MAXPWLEN (it must remain greater than or equal to
1), or change the MAXPWLEN Option value to be greater than or equal
to MINPWLEN (it must remain less than or equal to 8).
NSC0412 MINUIDLEN cannot be greater that MAXUIDLEN.
Explanation: You specified a value for the minimum length of a User
ID (MINUIDLEN) that is greater than the value you specified for the
maximum length of a User ID (MAXUIDLEN).
Severity: Error
User Response: Either change the MINUIDLEN Option value to be less
than or equal to MAXUIDLEN (it must remain greater than or equal to
1), or change the MAXUIDLEN Option value to be greater than or equal
to MINUIDLEN (it must remain less than or equal to 8).
NSC0413 More than one LANSERVER (type IBM) or DOMAIN definition with the ON
option on line <nn> of NSC config file.
Explanation: You specified more than one IBM LANSERVER or DOMAIN
definition with the ON parameter. Only one IBM LAN Server logon may
be active at a time for a workstation.
Severity: Error
User Response: Remove the ON parameter from one of the LANSERVER or
DOMAIN definitions to allow password synchronization or delete one
of the LANSERVER or DOMAIN definitions.
NSC0414 More than one LOCAL definition with ON parameter on line <nn> of NSC
config file.
Explanation: You specified more than one LOCAL definition with the
ON parameter for the local workstation. Only one Local Logon may be
active for a session.
Severity: Error
User Response: Remove the ON parameter from one of the LOCALs
definition to allow password synchronization or delete one of the
LOCAL definitions.
NSC0415 NAME not allowed with LOCAL definition on line <nn> of NSC config
file.
Explanation: A NAME parameter was specified for a LOCAL definition.
For LOCAL definitions, the only valid parameters are ON, USERID and
EXIT.
Severity: Error
User Response: Remove the NAME parameter from the LOCAL definition.
To specify the User ID for the LOCAL definition, use the USERID
parameter.
NSC0416 Name is too long on line <nn> of NSC config file.
Explanation: You specified a Host name, IBM LAN Server domain name,
NetWare server name, or NSC Server name for the NAME parameter of a
HOST, LANSERVER, DOMAIN or SERVER definition that is too long. The
maximum length of node names and host names is 8 characters. The
maximum length of IBM LAN Server names and NSC Server names is 15
characters. The maximum length of a NetWare server name is 47
characters.
Severity: Error
User Response: Determine the correct name and modify the parameter.
For HOST definitions defining APPC hosts, this is the name of the LU
profile in the APPC configuration. For HOST definitions defining
emulator sessions, this is the name of the host information file for
the emulator session (not including the file extension of ".INI").
For SERVER definitions, this is the computername specified when
installing LAN Requester or LAN Server (this can be found in the
IBMLAN.INI file in the C:\IBMLAN directory). For IBM LANSERVER or
DOMAIN definitions, this is the IBM LAN Server domain name. For
NOVELL LANSERVER definitions, this is the NetWare file server name.
For NODE definitions, this is the Server Node Name configured in the
OS/2 Database Manager Workstation Directory for a database server,
or the PLU Name for an APPC application.
NSC0417 No host type specified for HOST definition on line <nn> of NSC
config file.
Explanation: You specified a HOST definition without a host type of
either EMULATOR or APPC, or you did not specify the host type prior
to an optional parameter.
Severity: Error
User Response: For the HOST definition, specify the host type as
either EMULATOR or APPC preceding any optional parameters.
NSC0418 NSC terminated because of configuration errors.
Explanation: NSC was not able to execute because of errors detected
in your configuration file.
Severity: Error
User Response: Correct the configuration errors and restart the
program.
NSC0419 Signon not allowed at an NSC Server on line <nn> of NSC config file.
Explanation: You specified the ON parameter for a SERVER definition,
or for a LOCAL definition or HOST definition with a host type of
EMULATOR or EHLL following a SERVER definition. Signon is not
supported at the Server.
Severity: Error
User Response: Remove the ON parameter from the definition to allow
password synchronization at the location, or delete the definition.
ΓòÉΓòÉΓòÉ 9.6. Messages 420-445 ΓòÉΓòÉΓòÉ
NSC0420 Path Name is too long on line <nn> of NSC config file.
Explanation: You specified a path name for an EXIT definition or an
EXIT or HIF parameter that is longer than 80 characters. The
complete path specification must be less than 80 characters in
length.
Severity: Error
User Response: Correct the path name. If necessary, make sure the
current path includes the path where the exit routine resides, and
specify only the file name of the exit routine.
NSC0421 Too many Exits on line <nn> of NSC config file.
Explanation: You specified more than 40 different EXIT definitions
or unique filenames as exit routines on the EXIT parameters for
location definitions in the configuration file. Network SignON
Coordinator/2 supports a maximum of 40 EXIT definitions. Each EXIT
parameter that specifies a filename that is not specified in any
EXIT definition or any other EXIT parameter is also counted.
Filename uniqueness is case-sensitive.
Severity: Error
User Response: Remove one or more EXIT definitions, or remove the
EXIT parameter from one or more of the definitions, or combine the
functions of one or more exit routines into a single exit routine.
NSC0422 Too many location definitions in NSC config file.
Explanation: More than 255 LOCAL, NODE, LANSERVER, DOMAIN, HOST and
SERVER definitions were specified in the configuration file. Network
SignON Coordinator/2 supports a maximum of 255 configured location
definitions.
Severity: Error
User Response: Delete the extra definitions. It may be possible to
support additional signon and password synchronization using user
exits.
NSC0424 User ID contains characters that are not valid on line <nn> of NSC
config file.
Explanation: You specified a User ID containing an ASCII control
character. Only graphic ASCII characters are valid in User IDs.
Severity: Error
User Response: Correct the User ID.
NSC0425 User ID is too long on line <nn> of NSC config file.
Explanation: You specified a User ID that is longer than the maximum
length specified in the configuration file for the MaxUIDLen
definition.
Severity: Error
User Response: Correct the User ID.
NSC0426 USERID not allowed with SERVER definition on line <nn> of NSC config
file.
Explanation: You specified a USERID parameter on a SERVER
definition. No signon or password synchronization is associated with
the SERVER definition. Thus, the USERID parameter is not allowed.
Severity: Error
User Response: Remove the USERID parameter from the SERVER
definition. If password synchronization with the local UPM on the
Server is required, specify the USERID parameter on a LOCAL
definition following the SERVER definition.
NSC0427 No name specified for a <def> definition on line <nn> of NSC config
file.
Explanation: You specified a NODE, LANSERVER, DOMAIN, HOST, SERVER
or EXIT definition without a NAME parameter.
Severity: Error
User Response: Specify a NAME parameter. For a LANSERVER (type IBM)
or DOMAIN definition, specify the IBM LAN Server domain name. For a
LANSERVER (type NOVELL) definition, specify the NetWare Server name
using the NAME parameter. For a HOST definition, specify the host
name. For a SERVER definition, specify the machine name. For an EXIT
definition, specify the user exit filename. For NODE definitions,
specify the Server Node Name configured in the OS/2 Database Manager
Workstation Directory for a database server, or the PLU Name for an
APPC application.
NSC0428 I/O error reading <config-file> after line <nn>.
Explanation: NSC detected an I/O error when reading the NSC
configuration file or host information file identified by
config-file. The error was detected after reading line nn.
Severity: Error
User Response: Retry the operation. If the disk error persists, take
steps to circumvent the error. Possible corrective actions include:
- Rename the file so that the faulty disk space is not reused, then
recreate the file.
- Reformat the disk to eliminate bad sectors, then restore your
system.
- Replace your disk, then restore your system.
NSC0429 Line <nn> in NSC config file is too long.
Explanation: Line <nn> contains too many characters.
Severity: Error
User Response: Edit the NSC configuration file and delete unneeded
characters, then retry the operation.
NSC0431 No server type specified for LANSERVER definition on line <nn> of
NSC config file.
Explanation: You specified a LANSERVER definition without a host
type of IBM or NOVELL, or you did not specify the host type prior to
an optional parameter.
Severity: Error
User Response: For the LANSERVER definition, specify the host type
as IBM or NOVELL preceding any optional parameters.
NSC0432 User ID is too short on line <nn> of NSC config file.
Explanation: You specified a User ID that is shorter than the
minimum length specified in the configuration file for the MinUIDLen
definition.
Severity: Error
User Response: Correct the User ID.
NSC0433 Host type already specified for HOST definition on line <nn> of NSC
config file.
Explanation: You specified a host type of both EMULATOR (EHLL) and
APPC for the HOST definition. You may only specify one host type.
Severity: Error
User Response: Remove the incorrect host type.
NSC0434 Server type already specified for LANSERVER definition on line <nn>
of NSC config file.
Explanation: You specified a LAN Server type of both IBM and NOVELL
for the LANSERVER definition. You may only specify one LAN Server
type.
Severity: Error
User Response: Remove the incorrect LAN Server type.
NSC0435 Too much variable length text on line <nn> of NSC config file.
Explanation: The length of your location names, userid, and user
exit paths, combined with the large number of location definitions
you have configured, requires too much memory.
Severity: Error
User Response: If the same user exit path is specified more than
once, try using specifying it once with an EXIT definition and
referencing it using the EXITID parameter. If this does not help,
reduce the number of location definitions,
NSC0436 No ID specified for an EXIT definition on line <nn> of NSC config
file.
Explanation: You specified an EXIT definition without an ID
parameter.
Severity: Error
User Response: Specify a unique ID number for the user exit using
the ID parameter.
NSC0440 V<x> already specified for HOST definition on line <nn> of NSC
config file.
Explanation: You specified the same HIF Variable parameter twice for
the HOST definition.
Severity: Error
User Response: Remove one of the HIF Variable parameters.
NSC0441 V<x> string syntax error for HOST definition on line <nn> of NSC
config file.
Explanation: The HIF Variable parameter was specified starting with
a double quote, but not terminated by a double quote.
Severity: Error
User Response: Terminate the HIF Variable parameter value with a
double quote.
NSC0442 Too much variable string text for HOST definition on line <nn> of
NSC config file.
Explanation: The combined length of all of the HIF Variable
parameters for the HOST definition is greater than 80. The HIF
Variable parameters for a single HOST definition are limited to a
total of 80 characters.
Severity: Error
User Response: Reduce the number of HIF Variable parameters or
reduce the length of the values for one or more of the HIF Variable
parameters.
NSC0443 Multiple GETDEFS found; or an EXIT or location definition used with
a GETDEFS definition.
Explanation: One or more of the following configuration errors has
occurred:
- The NSC.INI file has multiple GETDEFS.
- The NSC.INI file contained a GETDEFS as well as an EXIT definition
or location definition.
Severity: Error
User Response: Determine which configuration error occurred and
correct it. In the first case, delete the extraneous GETDEFS. In the
second case, either remove the GETDEFS or remove the location and
EXIT definitions.
NSC0444 A linked to definition file contained a GETDEFS definition.
Explanation: The configuration file loaded because of a GETDEFS in
the NSC.INI file contains a GETDEFS.
Severity: Error
User Response: Either remove the GETDEFS from the NSC.INI file or
the file referenced by the GETDEFS.
NSC0445 Unable to create local copy of HIF file <filename>.
Explanation: When NSC loads a configuration file from an NSC Server,
it attempts to copy all HIF files referenced from the server and
created a local copy of the HIFs. NSC was attempting to copy the
filename HIF file.
Severity: Error
User Response: Investigate the following:
- Is there adequate disk space on the drive where NSC is installed
at the Client workstation to hold the HIF?
- Does the HIF exist on the NSC Server in the NSC execution
directory?
Correct the problem and restart NSC.
ΓòÉΓòÉΓòÉ 9.7. System Error Messages ΓòÉΓòÉΓòÉ
SYS1041: The name specified is not recognized as an internal or external
command, operable program or batch file.
Explanation: This error is displayed by OS/2, not by Network SignON
Coordinator/2. If displayed while attempting to startup NSC, it may
mean that the working directory or path is not set up correctly to
specify the directory where NSC is installed.
Severity: Error
User Response: Correct the specification of the working directory
for Network SignON Coordinator/2, or change the current directory to
where NSC is installed, or correct the PATH environment string for
the NSC session.
ΓòÉΓòÉΓòÉ 10. Problem Determination ΓòÉΓòÉΓòÉ
At times things just don't work in spite of our best efforts. You may not have
done anything different, but NSC can not successfully do what you requested.
You get messages from NSC in response to your signon and signoff requests that
explain what it perceives to be the problem. There may be additional problem
determination available that can help resolve the situation. This section will
help identify additional sources of information and how it can be used. This
information may help an end user, but it is primarily used by the network
administrator or the person who installed and configured NSC.
NSC creates a file of all error and information messages on disk. Most of these
are displayed on your screen too. The messages are written to disk to avoid
loss since some processes are not monitored by an end user (e.g., NSCRETRY and
NSCNDMN).
NSC can create as many as three logs on a single workstation, depending on what
processes are running. Table "NSC Logs" identifies the logs by process and the
default for capturing debug information.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NSC Logs Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PROCESS Γöé FILE NAME Γöé DEBUG Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSC (1) Γöé NSC.LOG Γöé Off Γöé
Γöé Γöé Γöé Γöé
Γöé Γöé NSCNET.LOG (2) Γöé N/A Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSCRETRY Γöé NSCRETRY.LOG Γöé Off Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSCNDMN Γöé NSCNDMN.LOG Γöé Off Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NOTE: Γöé
Γöé Γöé
Γöé 1. Or NSCPM, NSCRSON or NSCRSOFF. Γöé
Γöé Γöé
Γöé 2. Only exists in DOS. Contains error mes- Γöé
Γöé sages generated doing LAN Domain logon and Γöé
Γöé logoffs. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
NSC writes these disk files (logs) in the directory that contains the NSC
configuration file (NSC.INI). A log is an ASCII text file and can be processed
using an operating system command (PRINT, TYPE, etc.) or viewed with a text
editor.
Each line is a message and follows a certain format, illustrated by the
following sample message:
IN 01 nn:nn:nn NSCRETRY System queue ....
Γöé Γöé Γöé Γöé Γöé
Γöé Γöé Γöé Γöé Γöé
Γöé Γöé Γöé Γöé Text
Γöé Γöé Γöé Γöé
Γöé Γöé Γöé Function
Γöé Γöé Γöé
Γöé Γöé TimeStamp
Γöé Γöé
Γöé ThreadID
Γöé
FunctionalArea
FunctionalArea Is a two-character code that identifies the internal NSC
functional area that originated the message.
ThreadID Is the two-digit OS/2 thread number on which the function
was executing. Since concurrent requests can be processed,
this value can be used to associate messages for the same
request. In DOS, this value is always "01".
TimeStamp The time when the message was written. This may be useful
in finding messages that were logged when the user had an
earlier problem.
Function Is used to either clarify the function generating the
message or the type of message. It is always eight
characters in length. Abbreviations for OS/2 functions,
NET functions, UPM functions, APPC verbs and NETBIOS verbs
can be found in LOG Functions.
Text Is a variable length message constructed by NSC.
When Debug information is requested, additional messages are logged. Debug
logging is turned "ON" in the NSC process by including a DEBUG command in the
NSC configuration file. Debug logging is turned "ON" in the NSCRETRY and
NSCNDMN processes by using the /DEBUG parameter option when starting the
process.
ΓòÉΓòÉΓòÉ 10.1. LOG Functions ΓòÉΓòÉΓòÉ
The following table defines the abbreviations for OS/2 functions, NET
functions, UPM functions, C library functions, APPC verbs, EHLLAPI verbs and
NETBIOS verbs that may be found in the Function field of LOG messages.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NSC LOG message functions Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ABBREVIATION Γöé FUNCTION Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé AddName Γöé NETBIOS ADD_NAME_WAIT Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Allocate Γöé APPC ALLOCATE Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé AllocSeg Γöé OS/2 DosAllocSeg Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé BeginT Γöé C _beginthread Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ConnPS Γöé EHLLAPI CONNECT PRESENTATION SPACE Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DeAlloc Γöé APPC DEALLOCATE Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DiscoPS Γöé EHLLAPI DISCONNECT PRESENTATION SPACE Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé dup2 Γöé C dup2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Call Γöé NETBIOS CALL_WAIT Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé CfgGet2 Γöé NetConfigGet2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Confirm Γöé APPC Confirm Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé CloseQ Γöé OS/2 DosCloseQue Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé CreateQ Γöé OS/2 DosCreateQue Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Execute Γöé C spawnv Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé FreeSeg Γöé OS/2 DosFreeSeg Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé GetDCNam Γöé NetGetDCName Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé GetSeg Γöé OS/2 DosGetSeg Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé GiveSeg Γöé OS/2 DosGiveSeg Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé HangUp Γöé NETBIOS HANG_UP_WAIT Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Init Γöé NETBIOS Initialize Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Listen Γöé NETBIOS LISTEN_WAIT Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé lseek Γöé C lseek Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ModalGet Γöé NetUserModalsGet Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé open Γöé C open Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé OpenQ Γöé OS/2 DosOpenQue Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Pause Γöé EHLLAPI PAUSE Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé QryHUpdt Γöé EHLLAPI QUERY HOST UPDATE Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé read Γöé C read Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ReadQ Γöé OS/2 DosReadQue Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé RcvWait Γöé APPC RECEIVE_AND_WAIT Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Receive Γöé NETBIOS RECEIVE_WAIT Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé RelPS Γöé EHLLAPI RELEASE Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ResAlloc Γöé NETBIOS RESET_WAIT Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ResetSys Γöé EHLLAPI RESET SYSTEM Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé RsvPS Γöé EHLLAPI RESERVE Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NSC LOG message functions Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ABBREVIATION Γöé FUNCTION Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SearchPS Γöé EHLLAPI SEARCH PRESENTATION SPACE Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Send Γöé NETBIOS SEND_WAIT Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SendData Γöé APPC SEND_DATA Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SendKey Γöé EHLLAPI SEND KEY Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SetSessP Γöé EHLLAPI SET SESSION PARAMETERS Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Status Γöé NETBIOS STATUS_WAIT Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé StpHNtfy Γöé EHLLAPI STOP HOST NOTIFICATION Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SttHNtfy Γöé EHLLAPI START HOST NOTIFICATION Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé TpStart Γöé APPC TP_STARTED Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé UGetInfo Γöé NetUserGetInfo Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé upmelocu Γöé UPM UPMELOCU Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé upmeulgf Γöé UPM UPMEULGF Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé upmeulgn Γöé UPM UPMEULGN Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé upmeusrl Γöé UPM UPMEUSRL Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé UPWSet Γöé NetUserPasswordSet Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Wait Γöé EHLLAPI WAIT Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé WkstaSet Γöé NetWkstaSetUID2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé WriteQ Γöé OS/2 DosWriteQue Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 11. Exit Routines ΓòÉΓòÉΓòÉ
User exits may be specified for specific locations definitions to allow an exit
routine to provide additional coordination or synchronization of signons,
password changes, and/or signoffs. Refer to EXIT for a description of how to
specify an user exit.
Exit routines can be command files or programs. The following sections
described how exit routines are executed by NSC, and give details required for
writing exit routines.
OS/2 Considerations
DOS Considerations
Parameters
Return Codes
Examples
ΓòÉΓòÉΓòÉ 11.1. OS/2 Considerations ΓòÉΓòÉΓòÉ
Exit routines in OS/2 are started in a separate session and may be windowed,
full screen or PM applications. The session inherits the environment of the
Network SignON Coordinator/2 session. Exit routines may be defined to start in
the background or foreground. Exit routines may be defined to execute
synchronously (NSC waits for the user exit to terminate) or asynchronously (NSC
processes the next definition without waiting for the user exit to terminate).
If an exit routine requires user interaction, and you want NSC to wait for it
to complete before continuing, you should define it to start in the foreground.
Exit routines that end with an extension of ".CMD" are started using the
command interpreter as a windowed session. All other exit routines are started
as executable programs.
ΓòÉΓòÉΓòÉ 11.2. DOS Considerations ΓòÉΓòÉΓòÉ
Exit routines in DOS are started with standard output and standard error
redirected to files (NSCNET.UID and NSCNET.ERR) to prevent most routines from
overwriting the Network SignON Coordinator/2 menu. You should avoid using exit
routines that require user interaction. If the prompt is written to standard
output, it will not display. If you have an exit routine that writes directly
to the screen, it will corrupt the Network SignON Coordinator/2 menu.
Exit routines are always executed synchronously in DOS (NSC waits for the user
exit to terminate before processing the next definition).
ΓòÉΓòÉΓòÉ 11.3. Parameters ΓòÉΓòÉΓòÉ
Exit routines are called with the following parameters:
1. Either
"0" for a signon request
"1" for a signoff request
"2" for a change password request
2. The configuration index of the associated definition (the first
definition is "1")
3. The return code from the request for the associated definition (i.e. LAN
Server, Host, or Local UPM). Return codes are listed in the NSCRSIGN.H
header file.
4. User ID (may be blank for Signoff)
5. Current Password (blank for Signoff)
6. New Password (blank for Signoff or if password was not changed)
ΓòÉΓòÉΓòÉ 11.4. Return Codes ΓòÉΓòÉΓòÉ
Exit routines can be defined to return an ERRORLEVEL indication to NSC (RC
parameter on EXIT definition, see EXIT). If the EXIT definition does not
include the RC parameter, NSC will ignore the return code from the exit
routine. When RC is specified, NSC displays a message if a non-zero return code
is returned by the exit routine. This allows a user to receive feedback on the
success or failure of the exit routine. Return codes and their interpretations
are defined in the file NSCRSIGN.H. Messages displayed by NSC and their
explanations can be found in Messages by adding 100 to the return code to
determine the NSC message number.
Note: Caution, exit routines which are command files may terminate with
syntax errors resulting in a non-zero return code.
If the EXIT definition MSGS parameter is not specified, NSC will only display
an exit status message if an error occurs.
ΓòÉΓòÉΓòÉ 11.5. Examples ΓòÉΓòÉΓòÉ
The following sections contain examples of exit routines for OS/2 and DOS:
Accessing Network Resources
Enabling 5250 Node Logons
Logging on to a DOS Database Client
Keeping Audit Logs of Signons
OS/2 NetWare Drive Mapping
DOS NetWare Drive Mapping
ΓòÉΓòÉΓòÉ 11.5.1. Accessing Network Resources ΓòÉΓòÉΓòÉ
The following example illustrates a command file that could be executed as the
exit routine for an IBM LAN Server on either an OS/2 or DOS Client. It performs
a NET USE following a successful signon. It does not return a return code.
@echo off
rem %1 = 0 for signon, 1 for signoff, 2 for change password,
rem %2 = Configuration definition index
rem %3 = Return code
rem %4 = User ID
rem %5 = Current Password
rem %6 = New Password
rem
rem exit if not a signon request
if not %1 == 0 goto end
rem
rem exit if signon request was not successful
if %3 == 0 goto success
if %3 == 1 goto success
goto end
rem
rem access the network drive
:success
NET USE N: \\LSERVER\NETDRV
:end
ΓòÉΓòÉΓòÉ 11.5.2. Enabling 5250 Node Logons ΓòÉΓòÉΓòÉ
The following example illustrates a command file that can be executed as the
exit routine for a HOST definition using an OS/2 Communications Manager 5250
emulator session. It generates a command file each time the password is
changed. The generated command file performs a 5250 node logon, and then starts
Communications Manager. If this generated command file is used to start
Communications Manager, the UPM node logon screen is bypassed when the
Communications Manager 5250 terminal session starts.
@echo off
rem %1 = 0 for signon, 1 for signoff, 2 for change password,
rem %2 = Configuration definition index
rem %3 = Return code
rem %4 = User ID
rem %5 = Current Password
rem %6 = New Password
rem
rem exit if not a change password request
if not %1 == 2 goto end
rem
rem exit if change password request was not successful
if not %3 == 0 goto end
rem
rem generate the command file
echo @LOGON %4 /P:%6 /N:PLUALIAS > D:\NSC\STARTCM.CMD
echo @CM 5250.CFG >> D:\NSC\STARTCM.CMD
rem PLUALIAS is the partner logical unit alias for this 5250 session,
rem which can be found either in the Communications Manager configuration file,
rem or on the Communications Manager initiated node logon screen.
rem 5250.cfg is the configuration file you use to start Communications Manager
:end
Note: This approach to bypassing the UPM node logon screen stores the password
in the clear on the hard disk. If this is an unacceptable security exposure,
the above example could be altered to scramble the password when writing it to
disk, and unscramble the password when reading it from disk.
ΓòÉΓòÉΓòÉ 11.5.3. Logging on to a DOS Database Client ΓòÉΓòÉΓòÉ
The following example illustrates a command file that could be executed as the
exit routine for a NODE definition from a DOS Client running the DOS Database
Requester.
@echo off
rem %1 = 0 for signon, 1 for signoff, 2 for change password,
rem %2 = Configuration definition index
rem %3 = Return code
rem %4 = User ID
rem %5 = Current Password
rem %6 = New Password
rem
rem if a signon request
if not %1 == 0 goto off
rem
rem perform the database logon
sqllogn2 %4 /p:%5
goto end
:off
rem
rem if a signoff request
if not %1 == 1 goto pw
rem
rem perform the database logoff
sqllogf2
goto end
:pw
rem
rem if a change password request
if not %1 == 2 goto end
rem
rem perform the database logon using the new password
sqllogn2 %4 /p:%6
:end
ΓòÉΓòÉΓòÉ 11.5.4. Keeping Audit Logs of Signons ΓòÉΓòÉΓòÉ
The following example illustrates a command file that could be executed as the
exit routine for any signon from either an OS/2 or DOS Client to record the
time and date of a user signon. The "e" drive may either be local, or may be a
network drive to which the user received access via the signon. The file
"rtn.inp" contains nothing but a line end.
@echo off
rem %1 = 0 for signon, 1 for signoff, 2 for change password,
rem %2 = Configuration definition index
rem %3 = Return code
rem %4 = User ID
rem %5 = Current Password
rem %6 = New Password
rem
rem exit if not a signon request
if not %1 == 0 goto end
rem
echo %1 %2 %3 %4 >>e:\audit.log
date <e:\rtn.inp >>e:\audit.log
time <e:\rtn.inp >>e:\audit.log
:end
ΓòÉΓòÉΓòÉ 11.5.5. OS/2 NetWare Drive Mapping ΓòÉΓòÉΓòÉ
The following example illustrates a command file that could be executed as the
exit routine for an OS/2 signon to assign subdirectories on a NetWare file
server to OS/2 disk drives.
/************************************************************************/
/* OS/2 NSC Sample Novell User Exit -- NOVELL1.CMD */
/* */
/* This sample is intended to be used for multiple LANSERVER */
/* definitions. For example: */
/* */
/* EXIT,ID=1,NAME=D:\NSC\NOVELL1.CMD,RC */
/* LANSERVER,NOVELL,NAME=DEPT_036_SERVER,ON,EXITID=1 */
/* LANSERVER,NOVELL,NAME=DEPT_042_SERVER,ON,EXITID=1 */
/* LANSERVER,NOVELL,NAME=DEPT_102_SERVER,EXITID=1 */
/* */
/* */
/* This exit returns if this is NOT a signon request that */
/* succeeded. If successful, based on which file server */
/* was signed on to, causes different drive map commands to */
/* be issued. */
/* */
/************************************************************************/
'@ECHO OFF'
/*TRACE ?R */
/* set default values */
UserID = ''
CurPswd = ''
NewPswd = ''
exitrc = 0;
NSC.RC.ERROR.BOUNDARY = 10; /* Warnings are less than this value */
/* get the parameters passed from NSC to this exit command file */
parse upper arg Request Location Result UserID CurPswd NewPswd;
if (Request <> 0) then signal TheEnd; /* if not signon --> exit */
/* If signon resulted in an error --> exit */
if (Result > (NSC.RC.ERROR.BOUNDARY-1)) then signal TheEnd;
/* The following check of Location is dependent on the physical */
/* line the LANSERVER definition appears in the NSC.INI file. */
/* Review the values any time a change is made to NSC.INI. */
select
when Location = 1 /* Department 36 Server */
then do
/* map drives M and N to subdirectories on Server 36 */
'MAP M:=DEPT_036_SERVER/SYS:HOME/'||UserID
if (rc > exitrc) then exitrc = rc;
'MAP N:=DEPT_036_SERVER/SYS:PUBLIC';
if (rc > exitrc) then exitrc = rc;
end
when Location = 2 /* Department 42 Server */
then do
/* map drive P to a subdirectory on Server 42 */
'MAP P:=DEPT_042_SERVER/SYS:'||UserID;
if (rc > exitrc) then exitrc = rc;
end
when Location = 3 /* Department 102 Server */
then do
/* map drive N to a subdirectory on Server 102 */
/* NOTE: this assumes you are not signed on to both */
/* Server 36 and 102 at the same time. */
'MAP N:=DEPT_102_SERVER/SYS:PUBLIC';
if (rc > exitrc) then exitrc = rc;
end
OTHERWISE
do /* Unknown ..... */
say "Error in Location codes ";
exitrc = 8;
end
end
TheEnd:
/* command files are limited to 256 as the highest ERRORLEVEL */
if (exitrc > 256) then exitrc = 256;
exit exitrc;
ΓòÉΓòÉΓòÉ 11.5.6. DOS NetWare Drive Mapping ΓòÉΓòÉΓòÉ
The following example illustrates a command file that could be executed as the
exit routine for a DOS signon to assign subdirectories on a NetWare file server
to disk drives.
@ECHO OFF
:/************************************************************************/
:/* DOS NSC Sample Novell User Exit -- NOVELL2.BAT */
:/* */
:/* This sample is used for a single LANSERVER definition. */
:/* For example: */
:/* */
:/* EXIT,ID=1,NAME=D:\NSC\NOVELL2.BAT */
:/* LANSERVER,NOVELL,NAME=DEPT_036_SERVER,ON,EXITID=1 */
:/* */
:/* This exit returns if this is NOT a signon request that */
:/* succeeded. If successful, based on which file server */
:/* was signed on to, causes different drive map commands to */
:/* be issued. */
:/* */
:/************************************************************************/
rem
rem If no parameters provided, exit.
if .%1 == . goto TheEnd
rem If not a password change, exit.
if not %1 == 0 goto TheEnd
rem Check if successful or warnings. If not, exit.
if %3 == 0 goto DoMap
if %3 == 1 goto DoMap
if %3 == 2 goto DoMap
if %3 == 3 goto DoMap
if %3 == 4 goto DoMap
if %3 == 5 goto DoMap
if %3 == 6 goto DoMap
if %3 == 7 goto DoMap
if %3 == 8 goto DoMap
if %3 == 9 goto DoMap
goto TheEnd
:DoMap
rem map drives M and N to subdirectories on Server 36
MAP M:=DEPT_036_SERVER/SYS:HOME/%4
MAP N:=DEPT_036_SERVER/SYS:PUBLIC
:TheEnd
ΓòÉΓòÉΓòÉ 12. Summary of Changes ΓòÉΓòÉΓòÉ
This document contains changes for Network SignON Coordinator/2 Version 1.1.
This is a maintenance release for Network SignON Coordinator/2 Version 1.0
which also includes several functional changes summarized here:
Installation Changes
Novell NetWare Support
DOS Emulator Support
Graphical Interface Changes
End User Command Changes
Configuration Definitions Changes
Message Changes
NETBIOS Usage Changes
User Exit Changes
Host Information File Changes
NOTE If you have an NSC Server, you must install a Version 1.1 NSC Server
at the same time you install Version 1.1 NSC Clients (and vice-versa).
Version 1.0 NSC Clients are not compatible with the Version 1.1 NSC
Server, and the Version 1.0 NSC Server is not compatible with Version 1.1
NSC Clients.
ΓòÉΓòÉΓòÉ 12.1. Installation Changes ΓòÉΓòÉΓòÉ
New installation command files have been shipped for Version 1.1. Installation
for both DOS and OS/2 is now performed with the same command, specifically
INSTALL
This command file can handle both a first-time installation, or a
reinstallation (over Version 1.0 or Version 1.1). For reinstallation, your NSC
configuration file will be preserved.
For DOS, the INSTALL command installs the DOS client. For OS/2, you will be
asked to select the type of NSC configuration you want. For OS/2 2.0 and later,
the NSC Folder is recreated.
Installation procedures are described fully in Installing Network SignON
Coordinator/2.
ΓòÉΓòÉΓòÉ 12.2. Novell NetWare Support ΓòÉΓòÉΓòÉ
NSC now supports signons to Novell NetWare File Servers from both OS/2 and DOS
Clients. See LANSERVER for information on configuring NetWare File Servers.
ΓòÉΓòÉΓòÉ 12.3. DOS Emulator Support ΓòÉΓòÉΓòÉ
NSC now supports DOS host emulators for 3270 or 5250 terminal emulation from
DOS Clients. See DOS Clients for information on supported software.
ΓòÉΓòÉΓòÉ 12.4. Graphical Interface Changes ΓòÉΓòÉΓòÉ
The graphical interface now displays icons in the client window for each system
on which you can sign on from your client. A second window is created to
contain the messages from NSC. Signon status is displayed for each location
with the icon. Icons may be selected to signon or signoff a single location.
The menu options have been enhanced to support selective signon. The new user
interface is described more fully in Graphical Interface.
When you start the graphical interface, a logo panel is conditionally
displayed. The duration for which it is displayed is controlled by your OS/2
System setting for logos.
ΓòÉΓòÉΓòÉ 12.5. End User Command Changes ΓòÉΓòÉΓòÉ
The NSCRSON and NSCRSOFF commands documented in Version 1.0 have been replaced
in Version 1.1 by the NSC command. The command syntax is defined in Command
Line Interface. The NSC command now supports both the command line interface
and the menu or graphical interface. This is described fully in End User
Commands.
NSC Version 1.1 contains two small executables, NSCRSON.EXE and NSCRSOFF.EXE,
which execute the NSC.EXE program, maintaining compatibility with Version 1.0.
Parameters are mapped as follows:
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NSCRSON and NSCRSOFF Support Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé OLD COMMAND Γöé NEW COMMAND Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSCRSON Γöé NSC ON (1) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSCRSON UID Γöé NSC ON UID (1) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSCRSON UID PW Γöé NSC ON UID PW (2) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSCRSON UID PW NPW Γöé NSC CHGPW UID PW NPW (2) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSCRSOFF Γöé NSC OFF (2) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NSCRSOFF UID Γöé NSC OFF UID (2) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NOTE: Γöé
Γöé Γöé
Γöé 1. Presents the menu or graphical interface Γöé
Γöé Γöé
Γöé 2. Executes as the command line interface Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 12.6. Configuration Definitions Changes ΓòÉΓòÉΓòÉ
We have replaced the "Domain" configuration definition with the "LANServer"
definition. The definition syntax is defined in LANSERVER. The "Domain"
definition is still supported in Version 1.1, maintaining compatibility with
Version 1.0. The "LANServer" definition allows specification of the LAN Server
as an IBM or Novell LAN Server.
In general, the use of the term "LAN Server" has replaced the use of the term
"domain" in much of the documentation.
We have added a "Node" configuration definition to support Node logons to UPM
on OS/2 Clients (primarily to support OS/2 Database Manager clients).
We have added a "GetDefs" configuration definition that allows you to store
configuration definitions on a single LAN node for easier NSC configuration
management.
When you exit the graphical interface, a new popup warning message may
optionally be displayed. We have added a new configuration definition,
"ConfirmExit". The default is "ConfirmExit=NO". If you specify
"ConfirmExit=YES", when you exit from the NSC panel, a popup warning message
will be displayed asking you to confirm that you want to exit.
The "ON" parameter may now be specified with the "Host" definition for an APPC
connection to request User ID and password verification at signon.
User exits may now be specified using the "Exit" definition. This gives
additional flexibility for OS/2, including the ability to specify execution in
the foreground or background, whether or not NSC should wait for the user exit
to complete, and whether NSC should display in-progress and completion messages
(based on the errorlevel set by the user exit). The "ExitID" parameter can be
used in a location definition to reference a user exit defined by an "Exit"
definition. We have raised the number of exit routines that can be specified to
40.
We have eliminated the restriction on the number of configuration definitions
that can be associated with a "Server" definition. This used to be 5, but is
now only limited by the limitation on the total number of definitions, which
has been raised from 50 to 255.
The "SavePW" definition has been added to instruct NSC to remember your
password and not reprompt for it on subsequent requests.
The "EHLLAPI" parameter has been changed to "EMULATOR". In general, the use of
the term "host emulator session" has replaced the use of the term "EHLLAPI Host
connection" in much of the documentation. For host emulation sessions, several
new parameters have been added to make it possible for one host information
file to be used for multiple hosts. The "Hif" parameter allows the
specification of the host information file name, allowing the Host name to be
independent of the host information file name. The "V0" through "V9" parameters
allow variable information to be substituted in the host information file.
ΓòÉΓòÉΓòÉ 12.7. Message Changes ΓòÉΓòÉΓòÉ
We have added a message number identifier to all messages, and messages are now
ordered in the documentation by message number in Messages.
We now display an "in progress" message as each definition is processed.
Definitions that are associated with NSC Servers are now processed one at a
time. This is intended to give you better feedback on what NSC is currently
doing.
Other message changes have been made as a result of the functional changes in
this release.
ΓòÉΓòÉΓòÉ 12.8. NETBIOS Usage Changes ΓòÉΓòÉΓòÉ
We have optimized the NETBIOS resource usage, with some resulting performance
improvements. The new resource requirements are described in Configuring
NETBIOS.
The NSC Server NETBIOS resource requirements can now be specified as a command
line option. The option is defined in NSCNDMN - Start the NSC Server.
Passwords are now masked when transmitted from an NSC Client to an NSC Server.
ΓòÉΓòÉΓòÉ 12.9. User Exit Changes ΓòÉΓòÉΓòÉ
User exits for OS/2 can now be executed synchronously (NSC waits for the user
exit to terminate) or asynchronously (NSC processes the next definition without
waiting for the user exit to terminate). The session for user exits for OS/2
can also be specified to be start in the foreground or background. User exits
may now return an errorlevel to NSC, with feedback to the user on the result of
the user exit. The default is to start a session in the background and wait for
it to terminate, and only display a message if the user exit cannot be
executed.
ΓòÉΓòÉΓòÉ 12.10. Host Information File Changes ΓòÉΓòÉΓòÉ
Support for dynamic session ids and substitution strings has been added to make
host information files more flexible and allow a single host information file
to be used for more than one host location. We have removed several restriction
on strings, section ordering and screen definitions within host information
files. Old host information files are fully supported. The host information
file is described in Configuring EMULATOR Connections.
New sample host information files are included that make use of substitution
strings so that they can in general be used as-is for many host systems. These
sample host information files are described in Sample Host Information Files.