INTRODUCTION
------------
This is the README.DOC file for the IBM PLANT FLOOR SERIES PlantWorks:
APPLICATION AUTOMATION EDITION Version 1 Release 2 Modification 2.
The following areas are covered in this file:
o Migrating from Previous PlantWorks Releases
o Using Communications System/2 CIF Installation
o Using PlantWorks I/O Support
o System Performance Features
o Database Integrity
o PlantWorks Demo Applications
o Service Control Window
o Buildtime Services
o Runtime Services
o List of APARs Fixed in This Release
o Trending and History Data APAR fixes
MIGRATING FROM PREVIOUS PLANTWORKS RELEASES
-------------------------------------------
Topic: Migrating from PlantWorks 2.0 or 2.1
If you are migrating your PlantWorks 2.0 or 2.1 system to PlantWorks
2.2, please see the 'Memo To Users' that was shipped with the product
diskettes. This contains detailed instructions on the migration
process.
Topic: Migrating from the December 1993 Limited Availability Release 2.2
version to the June 1994 General Availability Release 2.2 version.
Follow these steps to retain your network configuration while installing
the General Availability release of PlantWorks 2.2:
1. Create a new PlantWorks Release 2.2 GA Installation/Reference
Diskette using the OS/2 DISKCOPY command to copy the
Installation/Reference Diskette that was shipped as part of
the PlantWorks Release 2.2 GA product.
2. Copy the executive node's existing \ff\cfg\pwnet.cfg file to the
new copy of the Installation/Reference diskette that you just
created.
3. Use this new Installation/Reference diskette to install
PlantWorks Release 2.2 GA. Follow the instructions in the
'Installing and Configuring PlantWorks' book to perform the
installation.
4. Do not change the node name from the previous installation.
As detailed on page 3-3 of "Installing and Configuring PlantWorks" manual,
special considerations may need to taken into account when installing over
a subset of the Communications System/2 not previously installed by PlantWorks.
If you choose to delete Communications System/2 before installing PlantWorks,
certain files need to be backed up. In the \CS2\SYS directory, files ending
with .CFS, .DTn, .PRn, and .Snn (where n is a number) should be backed up.
If you have other CS/2 tables created outside of PlantWorks that reside in
the \CS2 tree, you will want to back those up also. These tables will have
files ending in .DTn, .PRn, and .Snn as detailed above.
When these files are backed up, CS/2 can be deleted as detailed in the manual.
After CS/2 is installed but before the node is configured, restore the backed
up files to their original directory. Immediately before or after you reboot
the machine as requested during the install is an appropriate time to do this.
See the section titled "Trending and History Data APAR fixes" for other
migration steps that you might need to perform.
USING Communications Systems/2 CIF INSTALLATION
-----------------------------------------------
If you choose to install Communications System/2 separately, the
follow options must be chosen:
Base System
Base System: Control Blocks
Base System: Toolkit
Toolkit: Sample Programs
Toolkit: DDMS
Device Data Management Support
32-bit Support
The client and server processes for Communications System/2 Common
Installation Facility can interfere with PlantWorks installation or
configuration. When using the Common Installation Facility (CIF) to
install Communications System/2, be sure to disable the CIF processes
on any node prior to performing installation or configuration of
PlantWorks on that node, including remote installation/configuration.
The Common Installation Facility gives you the option to start the CIF
processes automatically on system startup. You should choose 'N'
for this option.
To verify that the CIF processes are not running on a system:
1. Bring up the OS/2 Window list by hitting - from
the OS/2 desktop.
2. Scroll the window list as necessary to search for the following
programs: "CIFDM TCPIP", "CIFDM Netbios 0", "CIFDM Netbios 1",
and "CIFDM CRON".
3. If any of these programs appear in the Window List, click the
right mouse button (RMB) on the program title. Choose "Close"
from the Popup Menu that appears, then when the dialog box
appears, choose "Yes" to confirm that you want to end the
program. Repeat these steps for each of the CIF programs which
appear in the window list.
USING PLANTWORKS I/O SUPPORT
----------------------------
In order to use the I/O support in PlantWorks, you must set the TZ environment
variable in CONFIG.SYS, using the SET command. For example, if you are
in the Eastern Time Zone, you would add the following line to CONFIG.SYS:
SET TZ=EST5EDT
EST is the three letter code for the time zone you are in.
5 is the offset in hours from Greenwich Mean Time (GMT).
EDT is the letter code for Daylight savings time in your time zone (if any).
SYSTEM PERFORMANCE FEATURES
---------------------------
Topic: User Edits of the VCONFIG file
The VCONFIG file contains statements that set control values for
PlantWorks operations. The updated VCONFIG file included with this
release can be used to update an existing VCONFIG file. The new VCONFIG
file is stored in the FF\CFG directory.
Current working copies of the VCONFIG file are stored in the
FF\VISION\FILES directory.:
To update an existing VCONFIG file, follow these steps:
1. Make a copy of the new VCONFIG file.
2. Compare the copy of the new file with the current file.
3. Edit the copy of the new file and change the appropriate default
settings.
4. Delete the current working copy in the FF\VISION\FILES directory.
5. Store the new, updated copy in the FF\VISION\FILES directory.
6. Maintain a copy of original VCONFIG in the FF\CFG directory.
Instructions for updating the VCONFIG file are included in the
FF\CFG\VCONFIG file.
Topic: Increased shared memory
The maximum allowable shared memory has been increased. If a problem
occurs with constraints on shared memory, you can enter the
sm_total_size
parameter in the VCONFIG file to increase memory up to 15 MB, as
required.
Topic: Improved display refresh
The refresh operation of Runtime Monitor now displays updated data at one
time, not incrementally. Depending on the CPU loading process, system
performance might be impacted significantly. This feature can be disabled
by inserting the following statement the CONFIG.SYS file:
SET RTMNOTSMOOTH=1
If you disable the smooth refresh operation, the system must be rebooted
to take effect.
Topic: Data Refresh Frequency
The PlantWorks system time resolution for this release has a default of
1.0 second. This resolution determines the update frequency of variables
across nodes and the minimum refresh interval for PlantWorks displays.
This value can be enhanced to support higher resolutions. The possible
resolutions are: 1, 1/2, and 1/10 of a second.
You can change the system resolution value in VCONFIG to be one of the
following:
minimum_res: 1000 (1.0 second)
minimum_res: 500 (0.5 second)
minimum_res: 100 (0.1 second)
Note: The system resolution setting of 100 is intended for a 486 class
machine. If you have a 386 class machine and experience adverse
performance while running PlantWorks at this setting, reset the
system resolution value to the default of 1000.
Topic: RSSERVER startup settings
RSSERVER has two possible settings in the VCONFIG file for initialization:
0 and 1.
If the startup for the RSSERVER is set to zero (0), it is started as a
foreground process. This requires that all CMDEXEC function commands that
start a foreground process must begin the command name with the keyword
"start."
If the startup for the RSSERVER is set to one (1), it is started as a
background process. This requires that all CMDEXEC function commands that
start a foreground process must begin the command name with the keyword "start"
and at least one session parameter (such as "/WIN") to tell CMDEXEC where to
open the command session.
A foreground process that executes a .CMD file requires that the .CMD file's
logic has "exit" as the last command to close the session or is started with
the session parameter "/C".
See the OS/2 Online Command reference for more information on the START command.
Typing "help start" on the OS/2 command line will show you this information.
Background startup processes do not require the keyword "start," regardless
of which startup setting is assigned to RSSERVER.
The default setting for the RSSERVER startup is one (1).
Topic: Dynamic Data Exchange (DDE) Support
Dynamic Data Exchange (DDE) operates as a server, exchanging data between
PlantWorks and DDE-enabled client applications, such as a spreadsheet.
Client applications, such as Lotus 1-2-3 and Excel, are restricted to
receiving data. You can write customized DDE applications to exchange data
and interact with PlantWorks activities, such as changing values of variables,
triggering chains, or changing alarm states.
Requirements: PlantWorks DDE support is a 32-bit program, requiring
OS/2 Version 2.x. Special programming or use of additional system
resources is not required. The DDE server can be run on all PlantWorks
nodes, even if the executive node is not running.
Retrieving PlantWorks data for a client application: Once you define
PlantWorks variables, use the appropriate expression on the command line
of your application. DDE requires an application name, a topic, and an
item. The following example is for an Excel spreadsheet application:
=PlantWorks|Interface!"DDE::VAR_0"
where
PlantWorks is the application name
Interface is the topic
"DDE:VAR_0" is the item name of the DDE variable. Enter all
variables in uppercase.
Users can write their own DDE-enabled applications to modify data within
the application, and have the new values take effect in PlantWorks. For
detailed information on using DDE, refer to the "OS/2 2.0 Technical Library
Programming Guide Volume II."
Topic: Sample DDE Client Program
Sample C language files are included on the installation diskettes. You
can use these sample files to build your own DDE client program. The files
are located in the following directory:
\FF\SAMPLES\DDE (for IBM Set++ compiler)
DATABASE INTEGRITY
------------------
Do not shut down by rebooting. If the Node/Network shutdown procedure
available from the Service Control Window is inoperative for any reason,
use the OS/2 Desktop Manager to shut down as many of the PlantWorks and
Communications System/2 processes as possible. Again, only reboot as a
last resort.
Back up your database regularly so you can use it to restore the database
in the event of a failure. Use the Backup Database option of the
Network Definition Utility. In the event of a crash or forced reboot,
there is a possibility of database corruption. If the crash occurs
while you are installing an item, the probability of database corruption
becomes higher.
If you have a multinode network, it is recommended that you do not shut
down and restart remote nodes while you are installing items on the
executive node. Doing so can cause the database on a remote node to get
out of synchronization with the database on the executive node.
If the message BDM Data cache coherency problem appears in the warning
logger file on a node, you need to take the appropriate action:
o If the message occurs on a remote node, restart the remote node while
PlantWorks is running on the executive node.
o If the message occurs the executive node, restart the PlantWorks
network.
When conditions indicate that there is a chance of database corruption,
you must proceed with caution. If the failure that put you at risk occurred
during item installation, you should probably restore your database.
However, if the failure occurred under different circumstances, there is a
good chance that things are okay. You should first run CHKDSK against the
hard disk where PlantWorks is installed.
If your system is running with HPFS, this is done automatically upon system
restart. If you are using the FAT file system, it is your responsibility
to run CHKDSK. If the disk passes CHKDSK with no indication of lost clusters,
and the crash did not occur during item installation, you can be almost certain
that your file system, specifically your saved and installed PlantWorks
items, survived the failure. You should proceed to restart PlantWorks.
If lost clusters are found by CHKDSK, they are recovered automatically on
an HPFS system. However, to recover them on a FAT system, you must run
CHKDSK again with the /F option (booting from an OS/2 bootable diskette).
If the lost clusters are in one of the PlantWorks log files, the PlantWorks
database is probably okay, and you should restart your system.
If they are in the files called CURMASTE.IMG, there is a much higher
probability of database corruption, and you should probably take the safe
approach and restore your database.
PLANTWORKS DEMO APPLICATIONS
Demonstration applications are loaded on the executive node in the
\FF\SETUP directory. You can experiment with these application and get
ideas about how to set up your own applications. Refer to the PlantWorks
Optional Materials Memo for information about how to order other demo and
sample applications.
To install the demo applications in the PlantWorks database, follow these
steps:
1. Make sure PlantWorks is running.
2. Start a session of the PlantWorks full-screen environment on the
executive node.
3. By default, you can do this from the Group - PlantWorks window.
4. Change to the \FF\SETUP directory.
5. Type LOADDEMO on the command line and press Enter.
6. For more information about the demo applications and how to use them,
read the DEMO.DOC file in the \FF\SETUP directory.
Here is a brief description of the demo applications:
Disk Certifier Demo
The Disk Certifier demo is an example of how an application builder can
use PlantWorks to build an application for monitoring and collecting data
from a group of disk certifiers. This application provides a way for a
plant operator to see a status overview of all certifiers by colors that
reflect each machine's production status. Selecting a certifier brings
up a detail display of the particular machine. Use this certifier application
as a model for other applications where a plant operator needs to monitor
a number of similar same machines.
Injection Molding Demo
The Injection Molding demo is an example of how an application builder can
use PlantWorks to build an application for monitoring and operating an
injection molding machine. This application provides a way for a plant
operator to view detailed information about the status of an injection
molding machine and all the machine settings. In addition, there is a
simulation mode that lets the plant operator adjust process settings and
see the corresponding effect on the process.
Data Collection Demo
The Data Collection demo shows how an application builder can use
PlantWorks in conjunction with data collection devices, which collect
inventory and process data. Refer to the PlantWorks Optional Materials
memo for information on how to obtain demo applications that link actual
data collection terminals to PlantWorks and send and receive data to and
from the terminal. (The data can be entered from either the DCT keyboard
or the bar-code wand attached to the DCT.)
SERVICE CONTROL WINDOW
----------------------
Topic: Tool Bar Icons
The PlantWorks Service Control window provides a row of icons, representing
a fast path for starting frequently used PlantWorks services. This area
of the window is referred to as the tool bar.
By double clicking on an icon, the corresponding service becomes active.
A single click displays the name of the service in the lower left area of
the window. For more information on using the tool bar icons, refer to
"Definition Services/2 User Guide, Chapter 1."
Note: The icons currently in the tool bar are subject to change. The
published documentation for this release might not reflect the
most current list of icons.
BUILDTIME SERVICES
------------------
Topic: Accessing Definition Services
Application builders now can access definition services from within
Name lookup in addition to accessing them from the PlantWorks Service
Control window.
In the Name Lookup View dialog box of Name lookup, select the item you want
to edit, then select Edit. (As a short cut, you can double-click on the
item.) One of three events happens, depending on the status of the
definition service where the item was created:
1. If the definition service is not started, the definition service is
started and the selected item is opened.
2. If the definition service is started, but no item is open, the selected
item is opened in the already started service.
3. If the definition service is started and an item is open, a new session
of the definition service is started and the selected item is opened in
that session.
Topic: Definition Services Retrieval Defaults
When retrieving an item in Display Definition Service, Report Definition
Service, or Form Definition Service, the default now places asterisks (*.*)
in the Version or Version Number field. This default setting brings up the
highest numbered version of the requested item, so the application builder
does not need to keep track of specific version levels.
APPLICATION DEFINITION
Topic: Wildcard Export
The field for the Application Name ID in the Export Application dialog
box supports the use of wildcard characters as replacement symbols to
specify the item name(s) of the exported application.
The asterisk (*) symbol represents one or more characters. The question
mark (?) symbol represents only one character.
For example:
AFT: A* locates all items in the application "AFT" beginning with
the letter A.
AFT: A???? locates all items in the application "AFT" beginning with
the letter A and having a name five characters long.
CHAIN DEFINITION
Topic: Chain Trigger Options
The Add Trigger option in the Create Chain dialog box allows you to select
more than one trigger. Triggers are grouped into the following two types:
Time Triggers: Trigger on time of day
Trigger periodically
System Triggers: Trigger on system start
Trigger on system restart
Trigger on system shutdown
You can select any or all of the trigger options but only within the associated
group. You cannot select a time trigger and a system trigger.
Topic: User C Function DLLs
PlantWorks supports both 16- and 32-bit DLLs, and provides the following
run-time DLLs:
- FFCRTLIB.DLL (CSET 2) for 32-bit DLLs
- CRTLIB.DLL (IBM C2 and Microsoft 6.0) for 16-bit DLLs
To make the C functions run correctly, you must assure the following:
o When you are using 16-bit DLLs, you must disable stack probes
(-Gs compiler flag). You will have to recompile your 16-bit DLLs if
stack probe is on.
o The compiler you use might generate a dependency for a DLL that is not
shipped with PlantWorks. It is your responsibility to provide the
appropriate DLLs. You can verify during your testing process by driving
the DLL with a test program on a PlantWorks node.
o The UFSMAIN parameter in your VCONFIG file must be set to 0:
ufsmain: 0
o When you are running a C function using the DosStartSession function
call, the function might return a STATUS code of 457. This is not an
error--it merely notifies you that the session started in the background.
DISPLAY DEFINITION
Topic: Font Enhancement for Displays
The Edit Attributes dialog box supports a selection between four fonts:
o Courier
o Helvetica
o Times New Roman
o Symbol Set
Courier is a scalable font with fixed spacing for each character. Helvetica
and Times New Roman are scalable proportional fonts. Symbol Set is a collection
of Greek and numeric symbols, and can be used like other character sets.
Each font has adjustable scale factors of height and width. Check boxes are
provided to select the font, and entry fields are provided either to select
the default value of 1.0, or to enter a different value.
It is not necessary for you to enter scale factors in the these entry fields.
If you select a scalable font for a textual field in an object, the font adjusts
automatically as the object or, composite image, is sized proportionally in
height or width.
The entry fields, however, are convenient for creating a series of textual
strings of exactly the same size, without having to adjust them manually to
match. The Duplicate option allows you to copy an object, defined with specific
scalable factors, for creating additional objects having the same size and type
of font.
If there are multiple types of objects, you can use the scalable factor to
designate the same scalable font proportions for all the objects.
You also can cause all objects to have the same size and proportions of
textual strings by changing the defaults.
Topic: Visible Grid Enhancements
The Grid option on the View pull-down supports two grid selection check boxes:
o Snap To Grid
o Visible Grid
Selecting Snap To Grid causes newly created objects to automatically align to
the grid. Objects created before you selected this option are not affected.
(Use the Align To option to align existing objects.)
Selecting Visible Grid displays a grid pattern of dots on the Display Definition
working area.
Topic: Alignment Enhancements
The Align To option on the View pull-down supports the following object
alignment selections:
Closest Grid Point
Collective Left Side
Collective Right Side
Collective Bottom Side
Collective Top Side
Collective Center
Collective Horizontal Center
Collective Vertical Center
Even Spaced Left Sides
Even Spaced Right Sides
Even Spaced Bottom Sides
Even Spaced Top Sides
This feature aligns selected display objects to the current grid location.
The alignment selection moves the lower left corner of the object to the
nearest grid point. Objects are aligned by their spatial relationship to each
other, not the screen area.
Closest Grid Point is used for a single object; the remaining options are used
for multiple objects. Grouped, or composite objects, are aligned as one object.
You can remove the effects of the last Align To operation by selecting
Undo.
I/O DEFINITION SERVICE
Topic: Remote point access
You can define remote point access from within the I/O Definition Service
to permit PlantWorks to receive data from non-PlantWorks nodes. Communications
System/2 now enables PlantWorks nodes to read remote I/O data from
non-PlantWorks nodes, as long as the I/O points are defined in I/O Definition
Service. To enable remote point access, the user must edit the VCONFIG file.
To enable the I/O remote point access feature, follow these steps:
1. Access the working copy of the VCONFIG file.
2. Go to the end of the file and add the following line:
FF_DDMS_NODE: < CS2 node name >
where is the Communications System/2 registration
name at the DDMS node in the PlantWorks network.
For example, FF_DDMS_NODE: RMT1.
To disable remote point access after the VCONFIG file has been edited, either
delete the entire line or erase the and leave it blank.
Topic: New Help option
A new Help file has been added to the Help pull-down menu called "What's New."
The What's New file contains information on feature enhancements in the
Buildtime and Runtime Services for Release 2.2. What's New is available
from any Help pull-down where a new feature has been added.
Included in the Help information in the Chain Definition Service is a
listing of PlantWorks built-in functions. The function help contains
generally the same information contained in the "Definition Services/2
Functions" book, providing function description and valid types of parameters.
You can access this list of functions by selecting Contents on the Options
pull-down in the Help window. You also can access this file by pressing
F1 after selecting a function in the Add Function dialog box.
Topic: Sample C Functions
Included in the installation diskettes are sample C Functions for building
user-defined C language functions. These sample functions replace the
functions previously included in the "Definition Services/2 Functions" book.
The functions are located in the following directories:
\FF\SAMPLES\USRDLL\16BITS (for a 16-bit compiler)
\FF\SAMPLES\USRDLL\32BITS (for a 32-bit compiler)
RUNTIME SERVICES
----------------
Topic: Run-time Display List
The Runtime Monitor Service pull-down displays a list of the names of the
most recent displays accessed by the user. Up to eight display names are
listed in the order they are accessed. If the user accesses more than eight,
subsequent display names replace the oldest names in the list. Only display
names entered in the Select Display dialog box appear in the list.
LIST OF APARS FIXED IN THIS RELEASE
-----------------------------------
Definition Services/2
APAR Description
---- -----------
PN39390 Version number of I/O point set increase by 2 when saving the
I/O point set.
PN41605 Text objects in display definition have dotted lines around
them if background color is darker shades.
PN42280 Chain def. traps when saving a chain after adding a local variable
and doing a check function.
PN45829 ICIOTASK handling I/O timestamp incorrectly.
PN47796 Record Format delete option sometimes greyed out following a
certain sequence of steps.
PN48593 Report Definition service with XGA was loading incorrect font.
PN54513 Chain Definition trap_d printing a pictorial chain.
Build Services/2
APAR Description
---- -----------
PN39874 Table Maintenance Utility trap-d on bringing up a large DAE table
with more than 32,767 records.
PN44564 Can not create a reference diskette from Start Node
PN45830 IPCSEND transferring network.cfg file.
PN46374 CS2RDR00 is being reset by PW configuration.
PN48562 Warning DispInsServr GLI006: glib24 generated on installation of
display which had a graph that did limit checking.
PN46661 Table Maintenance Title bar was not being updated.
Execution Services/2
APAR Description
---- -----------
PN42740 Chain aborted at function LGCSWTCH if parameters VAR1 and VAR2
are of different type.
PN41949 Coins should not allow configuration of a slave node from the
executive node.
PN43088 Fexe traps at iftest function when chain-validation flag is checked.
PN44517 RTM shows incorrect display (1 display behind)
PN44548 CHNIVE traps when isntall a chain w/ DISFORM function (use variable
for the index of the record)
PN42008 DD traps when do error check on a display which contain Input Form
PN45663 Vos Exception Handler - Need to expand token list.
PN47841 Background color of dotted line showed white at runtime.
PN48749 Blank page output after Report is printed.
PN52933 Missing MAINT.ARC files from \ff\setup\tools.
PN52934 Cannot create a new Installation/Reference diskette.
PN52935 Warning and Event Browsers show incorrect time stamps.
PN53139 DAESEND RC=0 even though DAESEND failed.
PN53116 Cannot change PW executive node name.
PN53407 Homeset is not updating remote variables.
PN53256 CS2RDR00-CS2RDR0F configured incorrectly for exception handling.
PN53596 Valid variables in history plot are sometimes marked invalid
(red circle on top of the variable name).
PN53408 Cannot start multiple Application Definition services
PN53743 CS2DMR1A.EXE and CS2DMRVA.EXE are bad on the PW Execution
Services/2 diskettes.
PN53745 After defining an unsolicited array, a new array can't access
the symbolic/logical address field.
PN53746 Copy/Paste traps Chain Definition service.
PN53618 PWLDRIC.CMD should load MBXICCFG to save memory.
PN53623 Errors in Warning Browser when PlantWorks is shutdown.
PN53807 Cannot start a PW remote node when the PW executive node is down.
PN53744 Reports are generated with no data or incorrect data present.
PN53747 Chain Definition trap_d when copy/paste of a DISFORM function.
PN53640 Chain Definition invalid comment on the CHNTRIG function.
PN53641 CONFIG.SYS error that \ICA.MSG cannot be found after PW install.
PN53643 On Runtime Monitor Display, holding the CRTL key causes continuous
disk activity.
PN54184 DLGMGR.DLL trap_d using C function in a chain.
PN54221 CSR0029 on CS/2 shutdown after PlantWorks has installed CS/2.
PN54222 Cannot define a video for alarms.
PN54564 Chain that starts/stops logging to a logset causes Warning Browser
errors.
PN54646 Double clicking or pressing Alt-F4 on Service Control Menu causes
an uncontrolled shutdown.
PN54566 Chain Definition trap_d printing a snapshot of a chain.
PN54567 I/O Point Select Services shows incorrect variable time.
PN54568 WRL:TREND trending display does not work correctly.
PN54570 Application Definition problem with saving an application on exit.
PN54650 RTV.EXE (Event Browser) trap_d when called from CMDEXEC.
PN55009 Problems migrating an I/O Pointset from PW 2.1 to PW 2.2.
PN54951 Subchains cannot be run or deleted.
PN54565 Copy/Paste causes source object to be redrawn in Display Definition.
PN54569 Initial Database has two CHNTRIG functions listed.
PN54954 Cancel does not exit all functions in Setup Operations.
PN54965 Printing of alarm acknowledgement message is incomplete.
PN54956 After RNEXEC, 'Get Database Information' shows old executive node
name.
PN55782 Name Lookup Display is incorrect for XGA-2 displays.
PN56051 Working Storage Definition message incorrect for character strings.
PN56450 DISFORM function trap_d after 10 forms displayed.
PN56451 After deleting SECADM0 user id, PlantWorks trap_d on startup.
PN56692 Problems displaying a timestamp variable using the Helvetica font.
PN56619 Chain Definition pictorial print missing title page.
PN56719 CS/2 won't shutdown after PlantWorks has completed its shutdown.
Interface Services/2
APAR Description
---- -----------
PN56061 Errors in Warning Browser when IS/2 is shutdown.
TRENDING AND HISTORY DATA APAR FIXES
-----------------
If you are a new PlantWorks 2.2 customer, please disregard this section.
The PN54568 Trending APAR fix and PN57404 History Data APAR fix are corrected
in the 'PW Initial Database' (\FF\CFG\INITDB) shipped with PlantWorks 2.2.
These fixes affect the Trend Plot (WRL:TREND) and History Data (WRL:TABULAR)
displays. If you are using a PlantWorks 2.2 database from the Early Pilot
Program and require either of these fixes, you must perform the following:
o Export all your PlantWorks applications using the Application Definition
'Export Application' selection on the 'File' pull-down.
o Restore to the 'PW Initial Database' (\FF\CFG\INITDB)
following the instructions in the Installing and Configuring PlantWorks
manual, 'Initializing the PlantWorks Database' on page 6-2.
o Import all your PlantWorks applications into the 'PW Initial Database'
using the Application Definition 'Import Application' selection on the
'File' pull-down.
Last modified: May 4, 1999