home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
plawo22i.zip
/
PLWIDIS1.ZIP
/
readme.doc
< prev
Wrap
Text File
|
1994-05-16
|
8KB
|
219 lines
INTRODUCTION
------------
This is the README.DOC file for the IBM PLANT FLOOR SERIES PlantWorks:
Application Automation Edition, Interface Services/2 Release 2.2.
The following areas are covered:
o Pre-Installation requirements
o Run Time environment prerequisites
o Components
o DAE Configuration Notes
o PlantWorks Configuration
o APPC Environment Setup - Customer Responsibility
o Interface Services/2 Installation
o Interface Services/2 Configuration
o Starting Interface Services/2
o Function Clarifications
PRE-INSTALLATION REQUIREMENTS
-----------------------------
Before you install the Interface Services/2 server (IS/2), you must have
installed the following software:
1. IBM Operating System/2 (OS/2) 2.0 or 2.1
2. Distributed Automation Edition Communication System/2 Release 3.1
Distributed Automation Edition Host Link/2 Release 3.1
3. PlantWorks Execution Services/2 Release 2.2
4. IBM C/2 compiler Version 1.1 (Optional - Required if OS/2
based sample programs are to be compiled)
5. IBM C/370 Compiler and Library (Optional - Required if MVS
based sample programs are to be compiled).
RUN TIME ENVIRONMENT PREREQUISITES
-----------------------------------
1. IS/2 server and client program on the same node - DAE
environment
1.1 IS/2 server requires:
1. OS/2 2.0 or 2.1
2. DAE 3.1 configured to support IS/2
1.2 IS/2 client requires:
1. DAE configured to support IS/2 client
2. IS/2 server and client program on different nodes - DAE
environment
2.1 IS/2 server requires:
1. Same prerequisite as 1.1
2. DAE configured to support a DAE network
2.2 IS/2 client requires:
1. OS/2 2.0 or 2.1 installed
2. DAE 3.1 installed
3. DAE configured to support DAE network and IS/2 client
Use eaclnt2.cbs as a guideline for the setup
3. IS/2 server and client program on different nodes - OS/2 APPC
environment
3.1 IS/2 server requires:
1. Same prerequisite as 2.1
2. OS/2 Communication Manager configured for APPC
Use eaappc2.cfg as a guideline (supports the sample
program when used in conjunction with eaclnt2.cfg using
SDLC protocol).
4. DAE configured to support APPC non-DAE client
5. DAE Host Link/2 program installed and configured
3.2 IS/2 client requires:
1. OS/2 2.0 or 2.1
2. OS/2 Communication Manager configured for APPC
Use eaclnt2.cfg as a guideline (supports the sample
program when used in conjunction with eaappc2.cfg using
SDLC protocol)
4. IS/2 server and client program on different nodes - MVS/VTAM APPC
4.1 IS/2 server requires:
1. Same prerequisite as 3.1 - except -
Use eaappcv.cfg as a guideline to support the sample
program using SDLC.
2. ASCII to EBCDIC conversion on data stream as provided by
ACSSVC.DLL in OS/2 EE 1.3. See Appendix E in "Conversational
LU Application Programming Reference", S01F-0277.
4.2. IS/2 client requires:
1. MVS/VTAM 3.2 or later
2. VTAM setup to match the eaappcv.cfg using SDLC over a
nonswitched line
COMPONENTS
----------
Documentation
Using Interface Services/2, SC28-8258
IS/2 Product - Diskette 1
eapi.exe : server startup and monitoring program
ea_recv.exe : server receive processor
ea_send.exe : server send processor
ea_trig.exe : trigger a chain processor
eapimsg.h : IS/2 transaction definition - include file for "C"
program
readme.doc : this file
DAE CONFIGURATION NOTES
-----------------------
. If you intend to use CS2HTR00.EXE program, set the remote
architecture type to "1" in RCCB and codepage to 037. This is required
whether the client program is running on MVS or OS/2.
PLANTWORKS CONFIGURATION
------------------------
. The IS/2 service can be enabled by the "User Services Access."
. There is no default user setup for use by IS/2 client programs.
You must modify or create a new user to provide access through
IS/2. The sample programs require "EAPIDEMO" as the user ID and
the password.
APPC ENVIRONMENT SETUP - CUSTOMER RESPONSIBILITY
------------------------------------------------
Before attempting to execute either the OS/2 APPC sample program or the
MVS APPC sample program, the underlying APPC environment must be
completely set up. Interface Services/2 assumes that these environments
are capable of supporting APPC and makes no attempt to define the
environments beyond what IS/2 itself requires for the sample program
execution.
Provided with the sample programs are the OS/2 Communication Manager
".cfg" files required for their execution. In addition, for MVS, the
entries required in VTAM to match the CM entries are demonstrated.
However, there is no attempt to provide the complete VTAM and/or NCP
system and network definition. This is the user's responsibility.
INTERFACE SERVICES/2 INSTALLATION
---------------------------------
. You should install IS/2 on the Executive node while DAE is running
and the PlantWorks executive node is not active. See the
Interfaces Services Program Directory for further instructions.
. The files from the first and second diskette are copied to your
hard disk.
. PlantWorks will enable IS/2 to be automatically
started and stopped with the PlantWorks node.
INTERFACE SERVICES/2 CONFIGURATION
----------------------------------
. You are now ready to configure your system to support IS/2 as
described in Chapter 2 of the Using Interface Services/2 manual.
. If you plan to use an IS/2 client program via the APPC protocol
interface, you need to use Communication Manager to create or
modify the communication configuration files. You may use
"eaappc2.cfg" - and - "eaclnt2.cfg" for OS/2 based systems, or
"eaappcv.cfg" and the sample VTAM entries for the MVS to OS/2 setup.
Since APPC programs communicate as partner applications, you need
to carefully match the configurations between the two nodes.
. You may refer to the "easerv2.cbs" and "eaclnt2.cbs" files to see
how you config DAE to support the different kinds of IS/2
client programs.
STARTING INTERFACE SERVICES/2
-----------------------------
If you are going to support the APPC environment, you must start the
Communication Manager before starting DAE and PlantWorks. DAE
requires that the Communication Manager be running before the
APPC REM is started.
FUNCTION CLARIFICATIONS
-----------------------
Topic: EA_ALARM - usage
The alarm flag should be set to 'on' before you send the alarm message.
This will allow you to see the alarm display on the screen because the
alarm program tests the flag when it receives the request message.
Topic: EA_PRINT - text must include printer control character
If you are printing multiple text lines with EA_PRINT, you must
include control characters in the text. IS/2 will do an EBCDIC type G
data conversion for the MVS clients.
CHANGES IN THIS RELEASE
-----------------------
Two functions have been enhanced to:
. Add features to SYMLOOKUP transaction to return record formats
when user requests a RECORD ITEM NAME or RECORD FORMAT NAME
. Add support in EA_RECINIT, EA_READ and EA_WRITE transactions
to handle multiple-character strings in a RECORD.
/* *********** End of the file *********** */