INTRODUCTION ------------ This is the README.DOC file for the IBM PLANT FLOOR SERIES PlantWorks: APPLICATION AUTOMATION EDITION Version 1 Release 2 Modification 3 PTF-2. The following topics are covered in this README.DOC file: Table of Contents o Upgrading Plantworks 2.3 To Plantworks 2.3 PTF-2 o PlantWorks 2.3 PTF-2 Publications o DBCS Enablement o Update PlantWorks 2.1 user C Functions to run under PlantWorks 2.3 PTF-2 o Deleting unneeded Trend Sets o Backup/Restore of PlantWorks Database o OS/2 Database Manager Is Not Supported o Displaying a SQLCODE After A Database Function Call o System Defined Videos In PlantWorks (2.2) o Using Communications System/2 CIF Installation (2.2) o Using PlantWorks I/O Support (2.2) o System Performance Features (2.2) o Database Integrity (2.2) o PlantWorks Demo Applications (2.2) o Service Control Window (2.2) o Buildtime Services (2.2) o Runtime Services (2.2) o List of APARs Fixed in PTF-1 o List of APARs Fixed in PTF-2Upgrading Plantworks 2.3 To Plantworks 2.3 PTF-2
This section explains how to upgrade your current PlantWorks 2.3 installation to PlantWorks 2.3 PTF-2. If you do not have PlantWorks 2.3 installed on your system or if you are using PlantWorks 2.1 or 2.2, you cannot use this upgrade package to install PlantWorks 2.3 PTF-2. Instead, you must order the full PlantWorks 2.3 product diskettes or the PlantWorks 2.3 Upgrade through your normal IBM distribution channel. WARNING: This installation procedure will overwrite some data files in the PlantWorks program directory (\ff). The following data files will be overwritten: - Warning Browser log file (\FF\VISION\FILES\WARNING.LOG) - Initial Database Files (\FF\CFG\INITDB\*.*) If you need to save the information in these files for historical purposes, be sure to back them up before starting this installation. Note that the initial database directory (\FF\CFG\INITDB) contains a copy of the original database that was shipped with PlantWorks. It does not contain your current database. The PlantWorks 2.3 PTF-2 Upgrade consists of 4 upgrade disks, as well as a new Build Services/2 Installation/Reference disk, and a new Starter Services/2 Installation/Reference disk. You will only need to use one of the new Installation/Reference disks based on whether you are using Build Services/2 or Starter Services/2. Follow these directions to upgrade to PlantWorks 2.3 PTF-2: 1. Shutdown the PlantWorks network if it is currently running. 2. It is recommended that you perform an OS/2 (system) backup of your \FF, \CS2 and \ICA directories on the executive node prior to beginning the PlantWorks upgrade. At the very least, you should back up your existing PlantWorks database on the executive node using the Network Definition Utility. Ensure PlantWorks is shut down prior to performing a backup. 3. Create a new Installation/Reference disk: a. If you have Build Services/2 installed on your system, make a diskcopy of the new Build Services/2 Installation/ Reference disk. If you have Starter Services/2 installed on your system, make a diskcopy of the new Starter Services/2 Installation/Reference disk. Keep the original copy of the new Installation/Reference disk for safekeeping. b. Start the 'Network Definition' application that resides in the PlantWorks Desktop Folder. c. Insert your new copy of the Installation/Reference disk into the disk drive and select 'Save' from the 'File' menu. This will update the new Installation/Reference Diskette with your network configuration information. d. Exit the Network Definition application. e. This new Installation/Reference disk replaces the original Installation/Reference disk that you created when installing the GA version of PlantWorks 2.3. You should use the new version of the Installation/Reference diskette from now on. 4. Install the upgrade disks: a. If the PlantWorks 2.3 PTF-2 is to be installed on multiple nodes, ensure the installation procedure is performed at the executive node and that Communications System/2 is running on each remote node to be updated. If Communications System/2 is not started on a node: 1. Select the PlantWorks folder from the OS/2 desktop on that node. The PlantWorks Icon View window appears. 2. Select the Start Communications System/2 icon. Communications System/2 is started. b. Start a 'PlantWorks windowed environment' or 'PlantWorks full-screen environment' by double-clicking on the appropriate icon in the PlantWorks Desktop Folder. c. Insert the first Upgrade Disk (Disk 1) into your floppy drive. d. 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: cd \ install e. 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. f. Highlight the executive and all the remote nodes in the 'Other Nodes to install' list box. If you want to install additional nodes, they must be defined and configured with Communications System/2 currently running. g. Select 'OK' in the Install PW Diskettes dialog box to initiate the installation of the upgrade. A PlantWorks Installation message box appears. If the local node is not able to communicate with a selected remote node, a message is displayed and the upgrade will not be installed on the node. h. Follow the prompts to install all of the upgrade disks. i. When you are finished installing the upgrade disks, Exit the Network Definition application.PlantWorks 2.3 PTF-2 Publications
PlantWorks publication haven't been updated in release 2.3 so the PlantWorks 2.2 publications are still valid.DBCS Enablement
PlantWorks can support running on Korean and Taiwanese versions of OS/2. PREREQUISITE OS/2 FONT SUPPORT REQUIRED The following fonts must be installed, in addition to the basic fonts, in order for PlantWorks to perform properly on Korean/Taiwanese systems. MINCHO OUTLINE GOTHIC OUTLINE In OS/2 2.1, these fonts are contained in a separate 8 disk set that has to be installed separately from OS/2 2.1. In OS/2 Warp, these fonts can be installed during the normal installation process. You will experience problems with Display Definition, Runtime Monitor, and Chain Definition if these fonts are not installed. A new command file, SETDBCS.CMD, has been added to allow proper display of PlantWorks windows on a DBCS VGA resolution (640x480) system. Type SETDBCS in a PlantWorks full screen session for instructions.Update PlantWorks 2.1 user C Functions to run under PlantWorks 2.3 PTF-2
User C Functions created under Plantworks 2.1 using a 16-bit compiler might trap under PlantWorks 2.3 PTF-2. This is due to an incompatibility between the Plantworks 2.3 PTF-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.3 PTF-2. The old 16-bit versions of the User C Functions will migrate properly without any changes, but will be inoperable under PlantWorks 2.3 PTF-2 until they have been converted to 32-bit User C Functions.DELETING UNNEEDED TRENDSETS
To delete an unneeded trendset on a PlantWorks node, you must perform the following from either a PlantWorks window or full screen session. 1) Make the drive where PlantWorks is installed the current drive. 2) Change directory to \ff\vision\files\dlt\cur 3) List the names of all the trend sets that exists on this node by typing dir *.tps 4) Use the erase command to erase each trend set that is no longer needed. For example, to erase the var.tps trend set file, type erase var.tpsBACKUP/RESTORE OF PLANTWORKS DATABASE
To perform a PlantWorks backup or restore of the entire PlantWorks database you must perform the backup or restore operation from the PlantWorks executive node. Performing these operations from a PlantWorks remote node will only backup or restore that remote node's database.OS/2 DATABASE MANAGER IS NOT SUPPORTED
The 'Installing and Configuring Plantworks' manual incorrectly states that Plantworks provides an SQL interface to OS/2 Database/2 (DB2/2) and OS/2 Database Manager (DBM). The SQL interface DOES NOT support OS/2 Database Manager (DBM). If you are currently using OS/2 Database Manager and you wish to access these databases using the Plantworks SQL interface, you will need to install the OS/2 Database/2 (DB2/2) product and migrate your DBM SQL databases to DB2/2.DISPLAYING A SQLCODE AFTER A DATABASE FUNCTION CALL
If you are using any of the SQL chain functions (DBCONN, DBSELECT, DBINSERT, etc.) and the status return value (STATUS) is 6500, the EXSTATUS variable will contain the SQLCODE that was returned by DB2/2. Previously, if you tried to display the EXSTATUS value using Logic Monitor, Data Monitor, or the DISVAR chain function, the EXSTATUS variable seemed to be displaying garbage rather than the SQLCODE. This is because the EXSTATUS variable is defined internally as an usigned integer while the SQLCODE variable is defined as a signed integer. The logic monitor has been fixed to display the SQLCODE properly. In order to display the EXSTATUS variable properly using DISVAR or Data Monitor, you will need to copy the EXSTATUS variable into another variable of type INT4. You can then display the INT4 variable to see the proper SQLCODE. The best way to do this is to create a subchain as follows: - Create a subchain that accepts two parameters of type INT4 called STAT and EXSTAT. - When an SQL function exits out of the side exit (indicating an error has occurred), call this subchain and pass in the STATUS and EXSTATUS variables. - Within the subchain, check the STAT value to see if it is 6500. If it is, then the EXSTAT variable contains an SQLCODE. You can now use DISVAR to display the value of EXSTAT. For a sample subchain that performs the function described above, contact the Plantworks Support group.SYSTEM DEFINED VIDEOS IN PLANTWORKS (2.2)
The concept of user defined videos was eliminated in PlantWorks 2.2. Under PlantWorks 2.2, the system will create videos for each node during the installation process. The videos will all belong to the WRL: application. The video for the executive node will be called WRL:MSTRVID, while the videos for the remote nodes will use the node name as the video name. For example, if we have a three node network, LPN1, LPN2, and LPN3, our videos will be called WRL:MSTRVID, WRL:LPN2, and WRL:LPN3. These video names will be used if you decide to disable the all videos option in the Edit Group dialog box from within the Alarm Item Definition service.USING Communications System/2 CIF INSTALLATION (2.2)
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 (2.2)
Topic 1: Building DDMS Servers If any devices besides those supported by the CS/2 Communication Protocol Programs/A (i.e. Allen-Bradley, MODICON, GE-Fanuc, or Texas Instruments), are used, a DDMS server might need to be built. To build your own DDMS server, you will need to install the appropriate DDMS options that are not included in the PlantWorks installation of CS/2. Refer to the section above, "Using Communications System/2 CIF INSTALLATION", for information about installing CS/2. Additional information about I/O and DDMS servers is found in Chapter 4 of the Installing and Configuring PlantWorks book and in the CS/2 Installation and Configuration Guide Book. Topic 2: TZ Environment Variable 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 (2.2)
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 (CMDEXEC FUNTION BLOCK) RSSERVER has two possible settings in the VCONFIG file for initialization: 1 and 0. If the startup for RSSERVER is set to 1 it is started as a background process. This setting should only be used for programs running in the background which have no user interface and are not windowed. If the startup for RSSERVER is set to 0 it is started as a foreground process. This requires that all windowed programs begin with the keyword "start" followed by either "/f" or "/b" (Foreground or Background). In most cases the CMD.EXE shell should terminate after the program has terminated. If this does not happen then use the "/c" option. (Example = start /f /c program.exe) to eliminate the CMD.EXE shell. Examples of windowed: Vconfig - RSSERVER = 0 a) "start /f \ff\vision\bin\post.exe" - foreground b) "start /b \ff\vision\bin\post.exe - background Processes which are not windowed do not require the keyword "start". However, standard output is directed to the "PlantWorks" startup window where the process list is shown. This window is minimized when the PlantWorks database is initialized. The recommended setting for RSSERVER startup is 0. 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 (2.2)
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 (2.2)
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. 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 (2.2)
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 (2.2)
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: - FFRTDLL.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. If some function blocks do not snap to grid follow the directions below to align the offending blocks. 1. Get the Chain 2. Click "View" then "Grids" 3. De-Select "Snap to Grid" and Select "Grid Visible" 4. With your mouse move all offending function blocks to the desired position. 5. Click "View" then "Grids" 6. Select "Snap to Grid" 7. Save and Install the Chain All function blocks will now snap to the same grid. 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 > whereis 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. and 2.3. 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 (2.2)
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. CHAIN DEFINITION (2.3) (PTF1) ----------------------------- Topic: Find and Replace Within PTF1 Find and Replace will now search through CHNSTART and part of SUBCHNST. The 'type:' field in SUBCHNST will not be searched. However, the 'name:' field will. In CHNSTART the field 'If chain is stopped:' will now be accessible by Find and Replace. Other 'Find and Replace APARS also included in PTF1 are shown below. Topic: Local Parameters A limitation on the byte count of local parameters has been set at 64000. All older chains should work normally. However, all new chains will be subject to this limitiation. If your chains are trapping when triggered then try reducing the local parameter count. If you exceed 64000 bytes with your new chains they will not install. AUDIT TRAIL REPORTS (2.3) (PTF1) -------------------------------- Topic: Search Filter Within PTF1 a search filter was added to Audit Trail. Now Audit Trail works similiar to I/O Point Select. When you select 'Chain Audit Trail' or 'Subchain Audit Trail' a search filter will be presented. If you wish to view every chain defined just click 'Lookup' with nothing in the search field. If you wish to view every chain starting with 'S' just type 'S*' in the search field and click 'Lookup'. Now you can go directly to the chain or subchain of interest.LIST OF APARS FIXED - PTF-1
PTR609 DISPLAY DEFINITION FIND SHOWING BLANKS IN LIST PTR617 I/O READ/WRITE SECURITY ACCESS WAS NOT ENFORCED IN RTM PTR618 STRRES WAS NOT BEING RESOLVED FOR MOST OF DB SQL FUNCTIONS PTR625 TABLE MAINTENANCE TIMESTAMP SEARCH NOT WORKING PTR626 CAN START ALARM MANAGER SERVICES TWICE PN80714 BDM0023 ERROR MESSAGE MISLEADING PN82423 AUT0325 ON CHAIN AUDIT TRAIL WHEN 2646 CHAINS INSTALLED IN PW PN83475 THE ALARM DEFN, TEXT PRINT, PRINTS INCORRECT VALUE (0)FOR PN83476 NETWORK RECONFIGURATION ALWAYS REBUILD ICONS PN84498 TRAP IOP / DLGMGR.DLL PN84532 VOS.DLL GIVES TRAP000D WHEN USED WITH NEW TQSERVER.EXE PN85137 INCREASE THE MAXIMUM NUMBER OF THREADS IN TQSERVER.EXE PN85458 EXPORT/IMPORT PROCESS FORCES A UNIQUE PRIMARY FILENAME PN85688 FFRTLDLL.DLL ON DLT AFTER UPGRADE TO 2.3 PN86078 STRLEN DOES NOT STOP AT FIRST NON-BLANK CHARACTER PN86191 DISPLAY DEFINITION DOUBLE FIND FUNCTION CAN TRAP OR LOCK DISPLAY PN86201 In Display defn CTL/M toggles the pull down menu from visable PN86292 DSS0001 WHEN USING FIND TO DELETE AN OPERATION PN86295 DSS0001 WHEN USING FIND ON A RECORD OF FORM PN86583 CHD AND FFRTDLL TRAP000D ON FIND/REPLACE MEMORY NOT ALLOCATED PN86585 CHD FIND ACTION CHANGES THE CASE OF CHARACTER STRINGS WITHIN PN86589 PW 2.3 CTL-R FOR RETRIEVING A DIALOG BOX TO THE SURFACE NO PN86683 FIND & REPLACE IN CHAIN DEF WHEN A WILD CARD HAS BEEN USED IN PN86996 TND MISSING FROM X:\FF\CFG\PW.INV AFTER INSTALLATION OF PW 2.3 PN87370 GLOBAL.VALUE FIELD OF AN I/O POINT ON A REMOTE NODE INCORRECT PN88398 AMS ALARM MESSAGES, ACTION, TRIGGER DISPLAY / F7 GREYED OUT PN88450 FEXEXEC TRAP00D WHEN THE LOCAL VARIABLE REQUIREMENTS ARE > 64K PN89152 CHD AND FFRTDLL TRAP000D ON FIND/REPLACE WITH CHNSTART OPTIONS SET PN89195 NOT RECOGNIZING LEAP YEAR 2000 PN90190 PEAKLONG BYPASSFLAG NOT FUNCTIONING ON THE FIRST EXECUTION. PN90827 FEXEXEC TRAP000D WHEN LOCAL VARIABLE DEFINITION SIZE IS HIGH PN92165 PSL0003 AND PSL0009 ON MULTIPLE NODE PRINTING OF A HIGH VOLUME PN92296 TMS TRAP000D WHEN THE DESKTOP LOCKUP IS ACTIVATED PN92300 TMS FLOAT VALUE LESS THAN 1 IS NOT PROCESSED PROPERLYLIST OF APARS FIXED - PTF-2
PTR633 TOOLBOX IS NOT DBCS ENABLED. PTR634 WINDOW TRANSPARENCY WITH DATA MONITOR, EVENT & WARNING BROWSER PN90614 DISVAR FAILS TO DISPLAY CHARACTER VARIABLE XXX:CHAR10 1 . PN92442 LOCKS NODE WHEN SHUTDOWN WHILE LOGIC MONITOR IS MONITORING A CHAIN PQ01246 TIMEOUT TOO SHORT FOR BDM TRANSFER UNDER SOME CONDITIONS AND PQ01316 A FLOATING UNDERFLOW EXCEPTION. ERROR SYS3183 ASSOCIATED WITH PQ02395 RUNTIME DIALOG BOX CAN BE OVER LAYED IF ISSUED FROM CHAIN/DISPR PQ02563 CMDEXEC IS NOT FUNCTIONING AS DESCRIBED IN README.DOC PQ02632 IT IS POSSIBLE TO HAVE TWO RECORD FORMATS ASSOCIATED TO A FORM PQ02845 ICIOTASK.EXE CONTAINS DEBUG CODE PQ03096 ALARMS GENERATED BY IO DO NOT ENABLE TRIGGER DISPLAY BY ALARM MANAGER PQ03802 SCALING POINT VALUES REVERSED IN IO POINT SELECT PQ04272 TREND ANALYSIS GOES AWAY WHEN THE 12TH OR 13TH VARIABLE OF A PQ05241 FRD0001 FATAL ERROR IN FILE SETUP FORM - WHEN ALL 4 FIELDS ARE CHANGED PQ05813 RCLEAR TRAPS OR LOCKS SYSTEM IF YOU USE IT ON A RECORD OR ARRAY
Last modified: May 4, 1999