HP 3000 Manuals HP 3000 Manuals
Operating Environment
This section describes the hardware and software, on the IBM host and the
HP 3000, required to run SNA IMF.
IBM Host Hardware Requirements
SNA IMF requires the following IBM host hardware:
* An IBM host can be any IBM System/370-compatible computer that
supports the IBM 3270 family of terminals and printers, such as a
System/370, 30xx, 43xx, or compatible processor.An IBM host can
also be an IBM AS/400, System/36, or System/38.
NOTE When you configure an AS/400, System/36, or System/38 to
communicate with SNA IMF, you must configure the device type for
LU.T2 sessions as 3277, not 3278.
Also, bit 11 of the flags parameter of the OPEN3270 intrinsic (the
UNBIND option) must be set to 0.
* An IBM 37xx Communications Controllerthat supports an IBM 3274
Cluster Controller with attached IBM 3278 display stations and IBM
3287 printers. The 37xx must support an SNA line.
IBM Host Software Requirements
SNA IMF requires the following IBM host software:
* Multiple Virtual Storage (MVS)or Disk Operating System/Virtual
Storage Extended (DOS/VSE) operating system.
* Advanced Communications Function/Virtual Telecommunications Access
Method (ACF/VTAM).
* Advanced Communications Function/Network Control Program
(ACF/NCP).
* IBM 3270 host applications such as TSO, CICS, and IMS.
NOTE HP supports certain versions, releases, modifications, and Program
Temporary Fix (PTF)levels of the above software. Your HP
representative can verify whether SNA IMF can be supported with
your particular configuration.
HP 3000 Hardware Requirements
SNA IMF requires the following HP 3000 hardware:
* For SNA IMF/XL: An HP 3000Series 9xx computer system with a PSI
card.
For SNA IMF/V: an HP 3000 Series 37, 39, 40, 42, 44, 48, 58, 64,
68, or 70 computer system with an INP card and the following
memory requirements: nine Segmented Library (SL) segments,
including six Code Segment Table (CST) entries. Your HP
representative can help you estimate your system memory
requirements.
The SNA IMF/V memory requirement is a superset of the IMF/3000
memory requirement. IMF/3000 requires four SL segments, including
one CST entry. If you are migrating from IMF/3000 to SNA IMF/V,
be sure to consider the SL segments and CST entries no longer
required for IMF/3000 when calculating your SNA IMF/V memory
requirement.
* The HP terminals and printers used for emulation are connected
through one of the following:
Datacommunications and Terminal Controller (DTC)(MPE XL only) or
Asynchronous Data Communications Controller (ADCC)(MPE V only) or
Asynchronous Terminal Processor (ATP)(MPE V only) or
Multipoint Terminal Software (MTS)communication line (MPE V only)
or
X.25 Packet Assembler/Disassembler (PAD) or
DS Network Services HP 3000 communications link (HP 3000 to HP
3000 only)or
HP Network Services (NS3000/V)communications link (HP 3000 to HP
3000 only).
NOTE For SNA IMF/XL, Pass Thru is supported only on terminals connected
to a Datacommunications and Terminal Controller (DTC).
* A data communications line (switched or leased) between the HP
3000 and the host.
* A block mode terminalsupported by VPLUSfor Node Management
Services. See the SNA Link Services Reference Manual or the SNA
Link/XL Node Manager's Guide for descriptions of NMS screens
produced by VPLUS.
HP 3000 Software Requirements
SNA IMF requires the following HP 3000 software:
* The HP 3000 Multiprogramming Executive(MPE V or MPE/XL) operating
system.
* SNA IMF/V or SNA IMF/XL.
* SNA Link/V, SNA/SDLC Link/XL, or SNA/X.25 Link/XL.
Language Support
Application programs that call SNA IMF intrinsics can be coded in the
following languages:
* BASIC
* COBOL
* COBOL II
* FORTRAN
* Pascal
* SPL
* C (SNA IMF/XL only)
When using no-wait MPE I/O, application programs must be coded in COBOL
II, FORTRAN, Pascal, SPL, or C.Some of the intrinsics used with no-wait
I/O return a functional value, pass parameters by value, allow a variable
number of parameters, and set condition codes. Neither COBOL nor BASIC
has these capabilities.
NOTE On MPE XL, your application programs that call SNA IMF intrinsics
may be in either native mode or compatibility mode. However, if
your applications are written in BASIC or COBOL, the SNA IMF
intrinsic calls in native mode are different from those in
compatibility mode. See chapter 2 for more information on native
mode and compatibility mode.
The Communications Link
Data communications occurs over either a switched or a non-switched line.
The line protocol is SDLC multipoint(non-contention). Connection to the
line is through a modemthat you must obtain and install. You must ensure
that modems at the HP 3000 end and at the IBM host end are compatible
with each other and properly configured.
SNA IMF can use the same modem and INPor PSIas other SNA Services. Also,
multiple services can run concurrently using the same communications
line. The communications line between the HP 3000 and the host is
configuredon the mainframe end for a Type 2 node. You can find
configuration information in the HP SNA Products: Manager's Guide.
Transmissioncan occur at speeds of up to 64K bps on MPE XL, or up to 56K
bps on MPE V.
NOTE Only one SNA IMF control unit at a time may be configured to
operate over a point-to-point line. However, multipoint lines can
support multiple control units (one control unit per remote drop).
CAUTION Hewlett-Packard has not verified the SNA IMF product with all
possible combinations of host system software releases. We are
continually certifying with new host system software releases.
Check with your Hewlett-Packard representative for the most
up-to-date list.
Hewlett-Packard does not require that the customer run on one of
the verified versions. However, not doing so applies limits to
Hewlett-Packard's liability in addition to the normal limits.
Because of the certification problems imposed by the host system
versions, Hewlett-Packard must restrict its support policy in
the following ways. The resolution of all problems will fall
into one of the categories listed below:
If a problem is caused by incorrect operation of the
Hewlett-Packard product, Hewlett-Packard will repair the
product.
If a problem is caused by incorrect operation at the host,
Hewlett-Packard may require that the user change to a known
working version of the software or may elect to change the
Hewlett-Packard product to conform to the situation.
As always, Hewlett-Packard will in good faith attempt to solve
the problem with the customer.