HP 3000 Manuals

Glossary [ SNA NRJE Node Manager's Guide ] MPE/iX 5.0 Documentation


SNA NRJE Node Manager's Guide

Appendix B  Glossary 

A 

ACF:  See Advanced Communication Function. 

ACF/NCP:  See Advanced Communication Function for the Network Control 
Program. 

ACF/VTAM:  See Advanced Communication Function for the Virtual 
Telecommunications Access Method. 

active state:    A state in which part of an SNA node is able to function
as it was designed.

Advanced Communication Function (ACF):  A group of IBM program products
that uses SNA concepts.

Advanced Communication Function for the Network Control Program 
(ACF/NCP):  An IBM program product that resides in the 37xx
Communications Controller and supports single and multiple domains.

Advanced Communication Function for the Virtual Telecommunications Access 
Method (ACF/VTAM):  An IBM program product on the host that provides
communication access to and from the SNA network for single and multiple
domains.

B 

batch communications:    A form of data communications in which a
facility collects data over a period of time and then submits the
collected information to a host computer.  Typical batch communications
consist of large amounts of information transmitted at infrequent
intervals.

batch processing:    A technique of data processing in which jobs are
collected and grouped before processing.  Data is collected over a period
of time, then submitted to a host computer.

bind:    An SNA request sent by the host to activate a session between
two logical units.  The request specifies the detailed protocol to be
accepted before initiating an LU-LU session.

C 

chain:    A sequence of RUs constituting a recoverable entity.

CI:  See Command Interpreter. 

cluster controller:    A programmable device that supports one or more
terminals or printers.  For example, the cluster controller would be the
center node in a star shaped cluster network, governing all message
traffic to and from the other nodes.  A cluster controller communicates
with the communications controller either through a local channel
attachment or through modems and phone lines.

Command Interpreter (CI):  The part of MPE which analyzes and processes
commands entered during a session or submitted as part of a job.

communications controller:    A type of front-end processor, such as an
IBM 3705, 3720, or 3725, that communicates between the communications
facility and a host computer.  IBM supports both programmable and
nonprogrammable communication controllers.  Hewlett-Packard's INP and PSI
are types of communications controllers.

communications link:    The hardware that directly connects two locations
for the purpose of data transfer, including the interface boards, cables,
and modems (if a telephone line is used).

Control Unit (CU):  A device that controls input and output for one or
more devices such as printers or display stations.

CU:  See Control Unit.

D 

data set:    In IBM terminology, any file.

Distributed Processing Programming eXecutive (DPPX):  A general-purpose
IBM operating system found on the IBM 8100.  DPPX supports a remote job
entry workstation facility (DPPX/RJE).

Distributed Processing Programming eXecutive/Remote Job Entry (DPPX/RJE) 
workstation facility:    An IBM 8100 facility that enables users
to submit batch jobs to host processors and to receive output.
Hewlett-Packard has developed products which, when taken together,
emulate many of the major DPPX/RJE capabilities.

DPPX:  See Distributed Processing Programming eXecutive. 

DPPX/RJE:  See Distributed Processing Programming eXecutive/Remote Job 
Entry workstation facility. 

E 

emulation:    A technique, using software, allowing one computer to
behave exactly like another computer.  A Hewlett-Packard emulation of an
IBM device is an HP data communications product that enables an HP
computer or terminal to carry out many of the functions of the IBM
device.  For example, the HP SNA NRJE product enables an HP computer to
carry out many of the functions of an IBM 8100 DPPX/RJE workstation.

F 

FMD:  See Function Management Data services. 

FMH:  See Function Management Header. 

front end processor:    A smaller computer that relieves a larger host
computer of certain processing tasks, such as error detection, line
control, and message handling.

Function Management Data (FMD) services:    A generic term that describes
two SNA layers:  Session Presentation and Session Network Services.

Function Management Header (FMH):  An SNA header that selects a
destination or source for subsequent data transmission and supplies
information for other data management tasks.

H 

host:    A central computer that provides services for other computers
and terminals attached to it.

I 

INIT-SELF:  An SNA request to the SSCP to initiate an LU-LU session.

intrinsic:    A subprogram provided by Hewlett-Packard systems.
Intrinsics perform common functions such as opening files, opening
communications lines, or transmitting data over a communications line.

J 

JECL:  See Job Entry Control Language. 

JES:  See Job Entry Subsystem. 

JES2:    See Job Entry Subsystem 2. 

JES3:    See Job Entry Subsystem 3.0. 

job:    The basic unit of batch work on an IBM system.  A job consists of
a series of job control language statements.  In addition to these
statements, a job can include programs and input data.

Job Entry Control Language (JECL):  JECL statements are used for job
control under the VSE/POWER subsystem.  These statements define a job to
VSE/POWER and specify how job input and output are to be processed.

Job Entry Subsystem (JES):  A set of programs and routines that generally
schedules spools and batch jobs.  It also handles input and output.

Job Entry Subsystem 2 (JES2):    A common IBM job entry subsystem used
under the MVS operating system.

Job Entry Subsystem 3 (JES3):    An IBM job entry subsystem that is an
extension of the Asymmetric Multiprocessing System (ASP) program.  JES3,
which supports multiprocessing, receives jobs into the system and
processes all output produced by a job.

L 

ldev:    See logical device. 

ldn:    Logical device number.  See logical device. 

link:    The physical or logical connection between two devices in a
network.

logging:    The recording of significant events that may be of use to the
user at the time they occur.  This is distinguished from tracing, which
is the recording of events for future use.

logical device (ldev):    A disc file, a set of disc files, or a physical
device associated with a data stream between a host and a remote system.
An HP logical device is identified either by a number or by a device
class name.

logical printer:    Receives line printer images from a host system.

logical punch:    Receives card punch images from a host system.

logical reader:    Transmits card punch images to a host system.

Logical Unit (LU):  A program or a set of programs within a node that
provides access to an SNA network for an end user.  A logical unit can
support two types of sessions:  (1) an LU-SSCP session and (2) an LU-LU
session.  The logical unit formats message units, displays information,
and handles error recovery.  Multiple logical units can reside in an SNA
node.

Logical Unit (LU) class:    A set of logical units on the HP 3000.  For
SNA IMF, an LU class may contain multiple LUs.

Logical Unit Type 1 (LU.T1):    A session between an application program
and one or more data processing terminals.  The environment may be
interactive, distributed processing, or batch data transfer.
Character-oriented printer devices, batch support (RJE), and the SNA
Character String (SCS) are supported.

Logical Unit Type 2 (LU.T2):    A session between an application program
and one 3270-type display station using interactive data transfer.IBM
3270 Data Stream Capability (3270 DSC) and 3270-type display station
support is provided.

Logical Unit Type 3 (LU.T3):    A session between an application program
and a printer.  IBM`3270 Data Stream Capability (3270`DSC) is provided.
Many devices support both LU.T1 and LU.T3 print requests.

logical writer:    A logical printer or a logical punch.

LU:  See Logical Unit. 

LU class:    See Logical Unit class. 

LU-LU session:    A connection between two LUs.

LU.T1:    See Logical Unit Type 1. 

LU.T2:    See Logical Unit Type 2. 

LU.T3:    See Logical Unit Type 3. 

M 

modem:    An acronym for MODulator-DEModulator.  A modem converts serial
digital data from a transmitting terminal into a form suitable for
transmission over the analog telephone channel.  A second modem
reconverts this signal to serial digital data for acceptance by the
receiving terminal.  Bell 201, 208, and 209 modems are used for
synchronous data transfer.

MPE:  See MultiProgramming Executive. 

Multiple Virtual Storage (MVS):  An IBM operating system that is an
extension of OS/MVT. MVS is also known as OS/VS2 Release 2.  IBM enhanced
the original version of MVS; these enhanced systems include MVS/SP
(Multiple Virtual Storage/System Product) and MVS/XA (Multiple Virtual
Storage/eXtended Architecture).

MultiProgramming Executive (MPE):  The Hewlett-Packard operating system
for the HP 3000 computer.  MPE consists of programs that handle exchanges
between HP terminals, printers, and executing programs and the internal
HP 3000 Communications Software.

MVS:  See Multiple Virtual Storage. 

N 

Native Language Support (NLS):  A Hewlett-Packard product that provides
the HP 3000 with the features necessary to produce localized application
programs for end users without reprogramming for each language or
country.

NAU:  See Network Addressable Unit. 

NCP:  See Network Control Program. 

network:    A series of points interconnected by a communications
channel.  These may be computers, terminals, or other peripherals.

Network Addressable Unit (NAU):  Either a program or group of programs
that represents the source and destination of data in a network.  The
three kinds of network addressable units are SSCP, LU, and PU. A
communication session must exist before data can be transferred.
Sessions are established by the SSCP in this order:

 *  First with the PU.

 *  Then, with each LU before two LUs can communicate in a session.

Four types of sessions exist:

 *  SSCP-SSCP

 *  SSCP-PU

 *  SSCP-LU

 *  LU-LU

Network Control Program (NCP):  A program that controls the operation of
a communications controller.

Network File Transfer (NFT):  A user-level protocol that enables the
transfer or copying of files from one node to another or within a single
node, interactively or programmatically.

Network Services Procedure Error (NSPE):  An SNA request from the SSCP to
the LU indicating an error during session startup or shutdown.

NFT:  See Network File Transfer. 

NLS:  See Native Language Support. 

NMS:  See Node Management Services. 

node:    A set of hardware devices and associated software at the end of
a data link.  In an SNA network, nodes can be distributed or host
processors, communications controllers, cluster controllers, or
terminals.

Node Management Services (NMS):  A major software component of the HP
3000 operating system that provides a common set of services to HP
networking products.  It includes utilities and commands for
configuration, event logging, message tracing, link management, and
subsystem initiation, termination and control.

node name:    A name assigned to a node configured into a Local Area
Network (LAN). It must be a maximum of eight characters in length and
cannot be qualified.

NSPE:  See Network Services Procedure Error. 

P 

Physical Unit (PU):  A component of an SNA node.  A PU controls the
resources of a node and reports errors and physical failures to the SSCP.
One PU exists per node.  A PU is the access method in a host node, the
NCP in the communications controller node, and the hardware and software
in the peripheral nodes.  PU types for each kind of node are:

 *  PU.T1 is a terminal or printer in an SNA node.

 *  PU.T2 is a cluster controller, such as the IBM 3274, in an SNA node.

 *  PU.T4 is a communications controller, such as the IBM 3705, 3720, or
    3725.

 *  PU.T5 is a host processor with a System Services Control Point
    (SSCP).

POWER:  See Priority Output Writers, Execution processors, and input 
Readers. 

Priority Output Writers, Execution processors, and input Readers:    A
common IBM subsystem used to improve the input and output of jobs to the
VSE operating system environment.

PU:  See Physical Unit. 

R 

remote:    A workstation that is not local to the host system, and is
configured under the host job entry subsystem.  A remote can be connected
to its host by communications facilities or by direct attachment.

remote job access:    The submission of batch jobs to a host system from
remote sites over communication links.

Remote Job Entry (RJE):  Submission of jobs through an input unit which
has access to a computer through a data communications link.

Request Header (RH):  Control information that precedes a
request/response unit (RU). It specifies the type of RU and contains
control information for the RU.

Request Unit (RU):  A message unit containing control information, such
as a request code or function management headers, end-user data, or both.

Response Header (RH):  Control information that indicates whether a
response is positive or negative.  A response unit optionally follows it.

Response Unit (RU):  A message unit that acknowledges a request unit.  If
the response unit is negative, it will contain sense data that defines
the exception condition.  If the response unit is positive, it may
contain additional information; for example, it may contain session
parameters in response to BIND SESSION.

RH:  See Request Header or Response Header. 

RJE:  See Remote Job Entry. 

RU:  See Request Unit or Response Unit. 

S 

SDLC:  See Synchronous Data Link Control. 

session:    A logical connection between two network addressable units
that allows them to communicate.

SNA:  See Systems Network Architecture. 

spooled reader:    The MPE ldev for holding jobs to be sent to the host
for a given SNA NRJE workstation.

SSCP:  See System Services Control Point. 

Synchronous Data Link Control (SDLC):  An IBM term for a link protocol
used for the transfer of data between stations.  The information transfer
is synchronous, thus eliminating the need for start and stop bits.  It is
also code-transparent, transmitted serial-by-bit, and may be transmitted
in duplex or half-duplex over switched or nonswitched links.  The link
configuration may be point-to-point, multipoint, or loop.

System Services Control Point (SSCP):  A part of an SNA host node that
helps to manage configurations, controls network operations, does problem
solving, and provides other session services for end users.  An SSCP
exists only in the host and is exercised by the host's communications
access method.

Systems Network Architecture (SNA):  A comprehensive specification for
distributed data processing developed by IBM. SNA defines a layered
protocol for communicating and controlling a communications network
within the IBM environment.

T 

TERM-SELF:  An SNA request to the SSCP to terminate an LU-LU session.

TH:  See Transmission Header. 

timeout:    Time limit imposed for a given task to be completed.

tracing:    The recording of events for future use.  (See also logging).

Transmission Header (TH):  A transmission header is used by the
Transmission Control and Path Control layers of SNA for routing and
sequencing data sent through an SNA network.

transmission queue:    A queue of jobs to be transmitted to the host;
spooled reader.

V 

virtual reader:    A logical device configured into the operating system
that is used to queue files waiting for transmission to the host on a
logical reader.

Virtual Storage Extended (VSE):  An operating system that manages data
processing resources for IBM System/370 mainframes.

Virtual Telecommunications Access Method (VTAM):  An IBM communications
access method within the host that handles the data communications and
network control details for the host.

VSE:  See Virtual Storage Extended. 

VSE/POWER:  A common IBM subsystem used to control the input and output
of jobs to the VSE operating system environment.

VTAM:  See Virtual Telecommunications Access Method. 



MPE/iX 5.0 Documentation