TO: Licensees of IBM(R) PLANT FLOOR SERIES(TM)
PlantWorks: Application Automation Edition(TM)
Starter Services/2 for Operating System/2
SUBJECT: Program Number 5713-ADU -- Release 02,
Modification Level 02
Feature 5518
() PLANT FLOOR SERIES, PlantWorks:Application Automation Edition, and
PlantWorks are trademarks of the International Business Machines
Corporation.
() IBM is a registered trademark of the International Business Machines
Corporation.
The material you have received is listed on the enclosed
Packing List. Please review the Packing List to ensure
you have received all items listed.
If there are any discrepancies between the package
contents and the Packing List, please report these via
the Software Distribution Questionnaire which is enclosed
for your convenience.
NOTE: Program Currency: Program services for Starter
Services/2, Release 2.1 will be available until March 31,
1995.
If you are a NEW USER of the PlantWorks products, the
Installation Instructions that you use are in "Installing
and Configuring PlantWorks", SC28-8253-04, shipped with
the Starter Services/2 product.
If you are a CURRENT 2.2 USER of the PlantWorks products
and are hp2.not migrating from a prior installation, the
Installation Instructions that you use are in "Installing
and Configuring PlantWorks", SC28-8253-04, shipped with
the Starter Services/2 product.
If you are a CURRENT USER of the PlantWorks products the
instructions to migrate to this new Release 2.2 are
included in this USER MEMO for Starter Services/2,
5713-ADU. It is extremely important that you understand
these migration instructions before you install the
product diskettes and that you READ all the instructions
before executing them.
CURRENT and NEW USERS of the PlantWorks products require
installation of PTF9. Contact IBM software support by
phoning (1-800-237-5511) if you haven't received PTF9.
Included in Starter Services/2 is Communications System/2
Release 3.1. If you have a downlevel version of the
Communications System/2 product installed on your
PlantWorks node, the migration process will upgrade the
CS/2 product. PlantWorks 2.2 requires one of the
following CS/2 configurations:
1. Communications System/2 Release 3.1 that is shipped
with Starter Services/2
- or -
2. Communications System/2 Release 3.0 SLU1302 with PTF
1303 and PTF UN63358.
NOTE: If you are NOT using Communications System/2 that
is shipped with Starter Services/2, you need to order
SLU1302 with PTF 1303 and PTF UN63358 by phoning IBM
software support for Communications System/2
(1-800-237-5511).
UPGRADE INSTRUCTIONS - REL 2.1 TO REL 2.2
-----------------------------------------
Be sure you have the latest version of "Installing and
Configuring PlantWorks", SC28-8253-04, before proceeding.
If you are a NEW USER, follow the instructions in
"Installing and Configuring PlantWorks". THE REMAINDER OF
THIS MEMO DOES NOT APPLY TO YOU.
PLANTWORKS UPGRADE PROCESS FROM RELEASE 2.1 TO RELEASE 2.2
----------------------------------------------------------
REQUIREMENTS
------------
PlantWorks Release 2.2 requirements:
o OS/2 Release 2.0 or OS/2 Release 2.1
- If you are using OS/2 Release 2.0 you MUST have
the fix for APAR PJ03686 installed.
- When using any level of OS/2 you must have the
appropriate fix for APAR PJ14555 installed.
o Distributed Automation Edition, Communications
System/2 Release 3.1
o Disk space at least twice the size of your current
database (the space used for directory \FF\IM\FILES).
- If PlantWorks is installed on the same drive as
your OS/2 swap file (SWAPPER.DAT), you will need
additional space to allow the swap file to grow
to about 40 MB plus the size of your database.
In other words the total space requirements on a
drive containing an active swap file are 40 MB +
3*(database size) - (current size of
SWAPPER.DAT). The SWAPPER.DAT file is located in
the directory specified by the SWAPPATH statement
of your CONFIG.SYS file (\OS2\SYSTEM is the
default).
IMPORTANT: These migration procedures should be
performed using a copy of the new Installation/Reference
diskette included with PTF9, rather than the one shipped
with PlantWorks release 2.2 GA. The PlantWorks release
2.2 GA Installation/Reference diskette is being replaced
with this new PTF9 release 2.2 Installation/Reference
diskette. You can discard the PlantWorks
Installation/Reference diskette shipped with release 2.2
GA.
NOTES:
1. This procedure must be used ONLY to upgrade
PlantWorks software from Release 2.1 to Release 2.2
and the user should make no changes to the hardware,
software configuration, or the applications
themselves during the migration process. In
addition, do not start any PlantWorks Service during
the PWMIGRAT EXPORT and IMPORT operations.
If you are migrating from any other level of
PlantWorks or have special requirements please
contact PlantWorks Support for technical assistance.
Also, if you intend to migrate your database by any
procedure not documented here, contact PlantWorks
Support for technical assistance.
2. Custom objects created in SLU0891 or earlier versions
of PlantWorks and some custom objects created in
PlantWorks Release 2.1 are not migratable. If a
custom object cannot be migrated, the following
message displays and is logged in the migration log:
This Custom Display Item requires Manual Migration.
Contact PlantWorks Support Personnel for assistance.
A custom object within a display migrates
successfully. If you have custom objects that must
be "fetched", you should put them all in one or more
displays so you can migrate them with the display(s).
Once you successfully migrate them to PlantWorks
Release 2.2, you then can separate them into
individual custom objects using the Display
Definition Service.
3. PlantWorks Release 2.2 contains the following new
built-in functions:
ACKALARM DBCONN DBSELECT INALARM PTPOLOFF
ACKGROUP DBDELETE DBSQL INHGROUP PTPOLON
ARRCOPY DBDISC DBUPDATE LOGEVENT PUSHUP
ARRSET DBFETCH DISALARM OSTSTAMP STAMPOST
BEEP DBINSRT GETSCVL PRNALARM TAGGROUP
CLRGROUP DBROLBAK GETSTATE PTPOLMOD T2RDNXTN
DBCOMMIT
If you have C-language functions or subchains that
are named the same as any of these functions, you
must rename them before exporting your database.
Otherwise they will not be migrated.
4. Videos from PlantWorks 2.1 cannot be migrated. If
you have specific video names associated with alarm
groups, you will need to save the names from the 2.1
alarm groups and change the alarm groups to use "All
videos". After you have migrated to PlantWorks 2.2
and configured all your nodes, you will have to
modify the alarm groups to specify the videos from
2.1. Change your alarm groups to NOT use "All
videos" and add the specific videos. The video names
were changed to be node names from PlantWorks 2.1 to
PlantWorks 2.2. In other words, if you have
WRL:MYVIDEO on node LPN2 in Plantworks 2.1, the video
name becomes WRL:LPN2 in PlantWorks 2.2.
5. Before you begin migration, check any I/O packets you
have defined. If any packets have the last member as
"Bottom of List", delete those members. PlantWorks
2.2 will not allow "Bottom of List" to be a packet
member, but PlantWorks 2.1 did not prevent it. If
you do not delete "Bottom of List" from the 2.1
packets, you might get PlantWorks 2.2 runtime errors
from your devices after you have migrated.
6. The migration process does not migrate version 1.0 of
the alarm tree. If you have alarm groups associated
with WRL:ALMDATA 1.0 that you want migrated, save
that version of the "Alarm Item Definition" under
another version number such as WRL:ALMDATA 1.1.
7. The migration process does not migrate RECORD,
RECFMT, or DISPLAY database items for the WRL
application. If you have defined any RECORD, RECFMT,
or DISPLAY database items under the WRL application,
you need to duplicate those items under another
application name so that they migrate. You also need
to duplicate any item that references those RECORD,
RECFMT, or DISPLAY database items were defined under
the WRL application. After the migration has
completed, move the all of the duplicated items back
to the WRL application.
8. User C Functions created under Plantworks 2.1 using a
16-bit compiler might trap under PlantWorks 2.2.
This is due to an incompatibility between the
Plantworks 2.2 32-bit executable which calls the
16-bit User C Function DLL. If you have used
"sprintf", "fprintf", or "printf" in your User C
Functions under PlantWorks 2.1, you will have to
convert these User C Functions to 32-bit before they
will work properly under PlantWorks 2.2. The old
16-bit versions of the User C Functions will migrate
properly without any changes, but will be inoperable
under PlantWorks 2.2 until they have been converted
to 32-bit User C Functions.
9. If you have installed any customized palettes, they
will not migrate. You must go into Display
Definition services and write the customized palette
to a safe place. During the migration process, you
will be instructed to read in that saved customized
palette for use in PlantWorks 2.2.
DATABASE MIGRATION PROCEDURE
----------------------------
Be sure you have the latest version of "Installing and
Configuring PlantWorks", SC28-8253-04 before proceeding.
If you are a NEW USER, THIS MEMO DOES NOT APPLY TO YOU.
Follow the instructions in "Installing and Configuring
PlantWorks".
ON YOUR PLANTWORKS EXECUTIVE NODE:
1. Start a PlantWorks full-screen session. ALL OF THE
MIGRATION STEPS MUST BE RUN IN THIS ENVIRONMENT.
2. Back up the new Release 2.2 Installation/Reference
diskette using the OS/2 DISKCOPY command. Use this
backup diskette as your Installation/Reference disk
in all migration operations. Remember to use the new
Installation/Reference diskette shipped with PTF9.
DO NOT use PlantWorks release 2.2
Installation/Reference diskette.
3. We recommend performing an OS/2 (system) backup of
your \FF, \CS2 and \ICA directories on the executive
node prior to beginning PlantWorks migration. At the
very least, you should back up your existing
PlantWorks database on the executive node using the
Configuration/ Data Management Utility. Ensure
PlantWorks is shut down prior to performing a backup.
4. Copy the executive node's existing \FF\CFG\NET.CFG
file to the new backup Installation/Reference
diskette as A:\FF\CFG\NET.CFG using the OS/2 COPY
command.
COPY X:\FF\CFG\NET.CFG A:\FF\CFG\NET.CFG
where X is the drive where PlantWorks 2.1
resides
and A is your diskette drive
5. Start PlantWorks release 2.1 on the executive node.
6. Create the migration directory on your hard drive and
load the migration tools into that directory by
performing the following steps using the Release 2.2
backup Installation/Reference diskette created above:
a. In the example in this step and in all the
following steps, the migration work area is named
X:\MIGRATE, where X is the target drive. Check
that you already do not have a work area named
X:\MIGRATE. If you do, choose another work area
name to create in step 6b below, and substitute
that name wherever the migration work area
subdirectory is mentioned. Do not use the root
directory as your work area name. Create a
subdirectory for your work area.
b. Enter "a:\migrate\pwmigrat x:\migrate" in the
PlantWorks full-screen session to load the
migration tools from the release 2.2 backup
Installation/Reference diskette to the migration
work area (X:\MIGRATE).
7. Export the existing applications from the executive
node to a temporary and secure subdirectory on a hard
drive using the EXPORT command file, by performing
following steps:
a. Using the PlantWorks full-screen session, enter
the following commands at the prompt:
>X:
>CD MIGRATE
>EXPORT
where X is the drive containing the
migration work area
subdirectory
This creates a list of the exported database in
X:\MIGRATE\EXPORT.LST. The exported data is
contained in the files named IM*.
Check the X:\MIGRATE\EXPORT.LOG file for errors.
If any errors do exist, correct them, if
possible, and repeat the above steps as
necessary. Contact PlantWorks Support for
further assistance.
b. If your database contains any trend lists, run
Trend Plot Definition and print the trend list(s)
for all nodes and save these lists for later use.
You will have to recreate the trend lists after
the migration.
c. Shut down PlantWorks and Communications System/2.
8. Now delete PlantWorks 2.1 from the executive node and
backup related external files by performing the
following steps:
a. Using the PlantWorks full-screen session, enter
the following commands at the prompt:
>X:
>CD MIGRATE
>DELR21
where X is the drive containing the
migration work area
subdirectory
NOTE: This command removes all files loaded by the
original PlantWorks 2.1 installation. This
command will also save external files
associated with tables, queues and data
history logsets which will be migrated to
Release 2.2. Any of your files residing under
the \FF subdirectories also are removed. MAKE
SURE YOU HAVE YOUR DATABASE ALREADY BACKED UP
AS PREVIOUSLY INSTRUCTED IN STEP 3.
9. Upgrade Communications System/2, reconfigure the
executive node, and upgrade PlantWorks by performing
the following steps:
a. Upgrade Distributed Application Environment
Communications System/2. See Chapter 3 of
"Installing and Configuring PlantWorks" book
section on "Installing Communications System/2".
If you do not wish to upgrade Communications
System/2 at this time, contact your PlantWorks
Support person for assistance.
b. Reconfigure the executive node by following the
instructions in Chapter 5 of the "Installing and
Configuring PlantWorks" book. You should
reconfigure the executive node even if it is
marked as configured in the list of nodes. When
configuring if prompted with a message asking if
PlantWorks release information should be updated,
select "OK".
IMPORTANT: Ensure via "node setup" that
Autostart PlantWorks is not selected at this
time.
Once reconfiguration has completed the PlantWorks
2.2 folder is created on the OS/2 desktop.
c. Install PlantWorks Release 2.2 on the executive
node using the backup Installation/Reference
diskette by doing the following:
NOTE: The procedure described here is designed
to allow continued execution of most of
the PlantWorks network while Release 2.2
is being installed. It installs the
product(s) on the executive node.
If the install process terminates due to
locked DLLs, shut down and restart OS/2,
then repeat the install process.
1) Start Communications System/2 if it is not
running.
2) Insert the backup Installation/Reference
diskette into drive A.
3) From an OS/2 session, enter "a:" to select
the A drive.
4) Enter "install" on the command line.
5) Follow the installation instructions in
Chapter 6 of the "Installing and Configuring
PlantWorks" book. Proceed to the section
"Installing PlantWorks Program Files". While
performing this installation, if you are
prompted with a message asking you if you
wish to reinstall/update select "Yes".
d. Delete the old PlantWorks Group folder on the
executive node by selecting the folder and
pressing the delete key. Ensure that you aren't
deleting the new folder created by PlantWorks
configuration.
e. The PlantWorks 2.2 PTF9 diskettes should be
installed after the PlantWorks base installation
has been completed.
Follow these steps to install PTF9:
o Insert the PTF9 Installation Disk (Disk 1)
into your floppy drive.
o From the PlantWorks environment window,
change to the root directory of the floppy
drive and start the install.cmd file. If
your floppy drive is a:, you would type in
the following:
>a:
>install
o Select "Install PW Diskettes" in the Network
Definition window. The Install PW Diskettes
dialog box appears with the executive node
displayed in the "Local Node to Install"
field. Highlight the executive node only.
o Select "OK" in the Install PW Diskettes
dialog box to initiate the PTF installation
process. A PlantWorks installation message
box appears.
o Follow the prompts to install all 4 of the
PTF9 diskettes.
o When you are finished installing the PTF
diskettes, exit the Network Definition
application.
f. Delete the EVENT.LOG and WARNING.LOG files from
the FF\VISION\FILES directory on your hard drive.
g. Shut down Communications System/2 on the
executive node.
10. Install the default database supplied with PlantWorks
2.2 using the Network Definition Service. Follow the
instructions in Chapter 6 of "Installing and
Configuring PlantWorks" book section on "Initializing
the PlantWorks Database".
NOTE: At this time we are only initializing the
PlantWorks database. We are not restoring the
old PlantWorks database, so you should NOT
refer to Chapter 12 of the "Installing and
Configuring PlantWorks" book.
11. After restoration of the default PlantWorks 2.2
database has completed, start PlantWorks in migration
mode by performing the following steps:
a. Using the PlantWorks full-screen session, enter
the folloiwng commands at the prompt:
>X:
>CD MIGRATE
>PWMIGRUN
where X is the drive containing the
migration work area
subdirectory
This command will start PlantWorks in the
migration mode.
b. Wait until PlantWorks has completed its startup
procedures (initialized fully) before continuing.
Select "Yes" when prompted to update the
reference disk.
NOTE: There will be messages in the Warning Browser
indicating that PlantWorks 2.2 IPCSEND and
IPCRECV have been started in the migrate mode
for migration purposes. There may also be
messages indicating remote nodes to be
reconfigured. These messages are OK and do
not require intervention.
12. Confirm the installed nodes by doing the following:
a. In the PlantWorks Service Control window,
double-click on the NAME LOOKUP icon in the tool
bar, or select NAME LOOKUP on the UTILITY
pull-down of the menu bar.
b. Select the NODE option in the DEVICE combination
box in the Name Lookup Search dialog box, then
select the OK push button.
c. Review the list in the Name Lookup View dialog
box to see if all the required nodes are listed.
If any required nodes are not listed, contact
PlantWorks Support.
d. Select the CANCEL push button in the Name Lookup
View dialog box, then select EXIT on the EXIT
pull-down to exit the Name Lookup Service.
13. If you have used a customized palette for your
displays, read in that palette by following the
instructions in Chapter 7 of the "Using Definition
Services/2" (SC28-8255-01) book.
14. Import and install the old PlantWorks 2.1 exported
database by performing the following steps:
NOTE: Make sure that PlantWorks is still running.
a. Using the PlantWorks full-screen session, enter
the following commands at the prompt:
>X:
>CD MIGRATE
>IMPORT
where X is the drive containing the
migration work area
subdirectory
This imports and installs your old database into
the new release of PlantWorks. Check the
X:\MIGRATE\IMPORT.LOG file for any errors.
When the process completes, a completion message
appears at the bottom of the list within the
PlantWorks full-screen session. If you encounter
any node setup or device setup errors, restore
the Release 2.2 database from \FF\CFG\INITDB
using Network Definition Service and repeat from
step 11 on page 12. If a problem persists,
contact PlantWorks Support for assistance.
If you had defined any RECORD, RECFMT, or DISPLAY
database items under the WRL application, you may
receive error messages in the IMPORT.LOG file
indicating that the database objects that
referenced those database items did not import
correctly. If this is the case, ignore these
error messages. You have already saved these
items under another application name that was
imported correctly and at the end of the
migration process you will copy those items back
to the WRL application.
b. Shut down PlantWorks and Communications System/2
on the executive node.
c. Using the PlantWorks full-screen session, enter
the following commands at the prompt:
>X:
>CD MIGRATE
>REST_EXT
where X is the drive containing the
migration work area
subdirectory
This will restore external files from your
previous installation of PlantWorks. If any
errors are reported, follow the actions given in
the error message. Contact PlantWorks Support if
the error message contains no remedial action, or
if the problem persists.
15. Restart Communications System/2 from the icon in the
PlantWorks folder.
16. Once Communications System/2 is running on the
Executive node, start PlantWorks on the executive
node. Insert the Installation/Reference diskette in
the floppy drive if prompted by a message box.
17. Check to determine if alarms, tables and queues,
logsets, and trend lists need to be installed by
doing one or more of the following:
o If you have user-defined alarms, alarm groups or
alarm templates, do the following:
a. In the PlantWorks Service Control window,
double-click on the NAME LOOKUP icon in the
tool bar, or select NAME LOOKUP on the
UTILITY pull-down of the menu bar.
b. Select the ALARM option in the Name Lookup
Search dialog box then select the OK push
button.
c. Review the list of alarm data items listed in
the Name Lookup View dialog box, selecting
the most recent versions which are not
installed.
d. Select the INSTALL push button to install
these alarms. Alarm templates and groups are
"children" of these items, and will be
updated automatically.
e. Select the CANCEL push button in the Name
Lookup View dialog box, then select EXIT on
the EXIT pull-down to exit the Name Lookup
Service.
o If you have user-defined tables and queues,
install them by doing the following:
a. In the PlantWorks Service Control window,
double-click on the NAME LOOKUP icon in the
tool bar, or select NAME LOOKUP on the
UTILITY pull-down of the menu bar.
b. Select the QUEUE and TABLE options in the
RECORD combination box in the Name Lookup
Search dialog box, then select the OK push
button.
c. Review the list of tables and queues listed
in the Name Lookup View dialog box, selecting
all that have a status of Partially
Installed.
d. Select the INSTALL push button to install
these tables and queues.
e. Select the CANCEL push button in the Name
Lookup View dialog box, then select EXIT on
the EXIT pull-down to exit the Name Lookup
Service.
o If you have data logger items, do the following:
a. Ensure PlantWorks is started on the executive
node, and start Communications System/2 on
each remote node.
b. Start the Data History Definition Service
from the executive node.
c. Select SEARCH WITH DEFAULTS on the NAME
LOOKUP pull-down of the menu bar.
d. If you have partially installed logsets, then
select the INSTALL push button to reinstall
the partially installed logsets.
e. Note the names of all of the logsets in the
Name lookup screen.
f. Exit Name Lookup and return to the Data
History Definition Service.
g. Determine if your continuous logsets are
logging by performing the following:
1) Start a PlantWorks full-screen session.
2) Enter "cd \FF\VISION\FILES\DLT\CUR".
This will switch you to the logset
directory.
3) List the contents of this directory by
entering "dir".
4) Check the date and time stamps of your
logset files to determine if the logset
files are being updated within the rate
interval specified on the Create/Get
Logset screen.
h. Determine if your chain controlled logsets
are logging by triggering the chain that
initiates the logset. Perform steps 17g1 -
17g4 above.
i. If your Logsets are NOT logging execute the
following:
1) Load the logset into Data History
Definition using the GET LOGSET option of
the FILE menu. Enter the name of the
logset to be retrieved when prompted by
the message box.
2) When the CREATE/GET LOGSET dialog box
appears, change the logset status radio
button from LOGSET ENABLED to LOGSET
DISABLED, then select the OK push button.
3) Choose SAVE LOGSET fro mthe FILE menu.
4) Reload the logset again by using the GET
LOGSET option.
5) When the CREATE/GET LOGSET dialog box
appears, this time change the status from
LOGSET DISABLES to LOGSET ENABLED, then
select the OK push button.
This forces PlantWorks to create a new
logset datafile and to activate the
logset. Data from your original logsets
is available in the logset backup
directory \FF\VISION\FILES\DLT\SAV.
6) Again, save the logset by choosing SAVE
LOGSET from the FILE menu.
NOTE: Data History Definition currently
doesn't allow you to resave an enabled
logset, if the current version is also
enabled. This is why we are forced to
perform two saves to activate the
logset.
o If your database contains trend lists, do the
following:
a. In the PlantWorks Service Control window,
double-click on the RUNTIME MONITOR SERVICE
icon in the tool bar, or select RUNTIME
MONITOR on the RUNTIME pull-down of the menu
bar.
b. Select TREND PLOT on the DISPLAYS pull-down
of the Runtime Monitor Service menu bar.
c. Create a trend list following the
instructions in Chapter 4 of the "Using
Execution Services/2" (SC28-8257-01) book and
using the printout from step 7b on page 9.
d. Save the trend list following the
instructions in the "Using Execution
Services/2" book.
18. If you had custom objects that were saved into one or
more displays, remember to separate them into
individual custom objects using the Display
Definition Service.
19. If you had specific videos associated with your Alarm
Groups, you need to go replace those specific videos.
Change your alarm groups to NOT use "All videos" and
add the specific videos. The video names were
changed to be node names from PlantWorks 2.1 to
PlantWorks 2.2. In other words, if you have
WRL:MYVIDEO on node LPN2 in PlantWorks 2.1, the video
name becomes WRL:LPN2 in PlantWorks 2.2.
20. If you had defined any RECORD, RECFMT, or DISPLAY
database items under the WRL application and had
saved them and the related database items under a new
application name so that they would migrate, you need
to move the items back to the WRL application. This
can be accomplished by using the duplicate option in
each of the definition serivces to duplicate the
items back into the WRL application.
21. Shut down PlantWorks on the executive node and back
up the database using the Network Definition Service.
22. Shut down Communications System/2.
23. Shut down OS/2 using the SHUTDOWN option of the OS/2
desktop.
24. Restart OS/2. When OS/2 is running, start PlantWorks
using the Start PlantWorks icon in the PlantWorks
Group folder.
+--------------------------------------------+----------+
| IBM | |
+--------------------------------------------+----------+
+--------------------------------------------+----------+
SUBJECT: PLANTWORKS MIGRATION SERVICE OFFERING
A migration procedure is required in order to move an
existing application from PlantWorks Release 2.1 to
PlantWorks Release 2.2. This upgrade may also require an
upgrade to the levels of the OS/2 and Distributed
Application Environment products that you are using.
The cost of this service offering will vary based on the
size of your application as well as the number of
products that will need to be updated. A typical
application of 2-3000 items with 2 nodes and no upgrade
required for OS/2 or Communications System/2 will be
priced at approximately $3000.00.
If you are interested in learning more about this service
offering, please contact the PlantWorks Project office at
1-800-323-4968.
SUBJECT: PLANTWORKS OPTIONAL MATERIALS (5713-ADU)
There are three (3) PlantWorks demonstrations that are
shipped with Starter Services/2. The instructions for
loading these demonstrations is in the DEMO.DOC file in
the \FF\SETUP directory on the PlantWorks disk.
.
In addition to the database shipped with the Starter
Services/2 product there are two (2) new packages
available to assist you in the development of PlantWorks
applications or to help you demonstrate parts of the
PlantWorks functionality without coding an application.
There is no charge for these packages.
To receive them you must mail the enclosed form to the
indicated address with your selections indicated. Please
check ONLY the box(es) for the package(s) that you want
to receive.
THE TWO PACKAGES ARE:
1. Demonstration programs and Sample Applications
2. Advanced development modules
DEMONSTRATION PROGRAMS AND SAMPLE APPLICATIONS
The demonstration programs are portions of applications
which can be used to demonstrate some of the functions
available in PlantWorks. The sample application code is
a more complete set of displays, chains and data which
demonstrate how some of the basic functionality of
PlantWorks can be applied to solve specific applications.
The code can be copied and used as the basis for your
demonstrations and prototypes. Some of the functional
areas which can be demonstrated are:
o Statistical Process/Quality Control
o Chemical Batch Process Facility
o Facilities/Energy Monitoring
o Waste Water Management
o Bottling Line Monitoring
o PID Loop Control for Process Industry
o Data Collection Terminal Communications
The package will be delivered on 3.5" diskettes. The
documentation is contained in a README.DOC file on the
first diskette. This file can be printed or viewed using
an OS/2 editor.
ADVANCED DEVELOPMENT MODULES
The advanced development modules are pre-coded functions
and the support application components. They allow you
to expand your PlantWorks applications by providing
additional functionality which is not part of the base
products. Examples of this are:
o CIM Integration Interfaces (PMW, POMS)
o Digital/Analog Video Interfaces
The package will be delivered on 3.5" diskettes. The
documentation is contained in a README.DOC file on the
first diskette. This file can be printed or viewed using
an OS/2 editor.
+--------------------------------------------+----------+
| IBM | |
+--------------------------------------------+----------+
+--------------------------------------------+----------+
SUBJECT: PLANTWORKS OPTIONAL MATERIAL ORDER FORM (5713-ADU)
ease send the following packages to the address shown
low:
[_] Demonstration Programs and Sample Applications
[_] Advanced Development Modules
COMPANY NAME__________________________________________________________________
ADDRESS 1_____________________________________________________________________
ADDRESS 2_____________________________________________________________________
CITY____________________________STATE_______ZIP______________
ATTENTION_____________________________________________________________________
IBM CUSTOMER NUMBER________________
:
Mail this completed form to:
IBM CORPORATION
WORLD WIDE PRODUCTION SOLUTIONS
P.O. BOX 1328, I/Z 2102
BOCA RATON, FL 33429-1328
ATTENTION: PLANTWORKS SUPPORT
Last modified: May 4, 1999