Application ModuleX User Guide
Contents
1. OUT NUMBER Return status of the call OUT NUMBER Detailed return status OUT NUMBER hibernating or running OUT STRING X side application command line OUT STRING Point initiating X side application OUT STRING CL name initiating X side application OUT TIME HP UX time application initiated OUT TIME HP UX time application last activated OUT NUMBER current HP UX priority OUT NUMBER X side process identifier IN OUT STRING X side application identifier IN OUT NUMBER Index into X side hibernating queue IN TIME LCN timeout value Refer to Appendix I of the CL AM Reference Manual for more information about the functionality of the call and for definition of the arguments 42 Application Module User Guide 5 96 5 3 OpenDDA Support Supporting function evt_data Reference The OpenDDA Execution Statement HIBERNATE EVENT causes the application to suspend execution awaiting an event initiated from CL The application suspends execution during execution of the HIBERNATE EVENT statement before the event data and status are returned Either of the CL calls AMCL06 Activate_Task or AMCL06 Terminate_Task can cause the application to leave hibernation and resume execution When the application resumes execution it completes the HIBERNATE EVENT statement execution and returns and event data and status to the application Syntax2. AXM services Application class High priority control applications Low priority information level applications This feature requires AXM release R200 There are a number of services available in the AXM These included Data Access and File Access Some of these services can take very long periods of time to complete an associated action To ensure that resources are available for high priority control actions Honeywell has added functionality in AXM release R200 that allows the user to configure Data Access priority There are two basic classes of applications High priority control applications e Low priority information level applications These control applications often have stringent timing requirements for reading and writing LCN data They are involved in closed loop control strategies and often but not always transfer smaller amounts of data Therefore they need access to the LCN for bringing in reasonable amounts of data but the path to the valve must be available when needed These applications typically have more relaxed requirements for access to the LCN for reading writing of data They tend to bring in a large amounts of data for functions such as data collection TPH PC desktop viewing PCDE or background types of applications These are not control applications can often tolerate a little more variability in their access to the LCN and often do not write any data back to the LCN
3. Refer to Appendix I of the CL AM Reference Manual for more information about the functionality of the call and for definition of the arguments Continued on next page 5 96 Application Module User Guide 41 5 2 CL Support Continued Get Hiber Task Status The background CL subroutine AMCL06 Get_Hiber_Task_Status is used to obtain specific information about a single entry in the X side hibernating queue It can be used to obtain information about a known application or to get information about a current hibernating task in the hibernating queue to display on a schematic To obtain information about a known application this subroutine accepts as input an application id obtained from AMCLO06 Initiate_Task of an OpenDDA hibernating application It will return information about the hibernating application including the associated index number in the hibernating queue To get information about a current hibernating task in the hibernating queue to display on a schematic this subroutine accepts as input an index identifier It will return information about the hibernating application for the given index in the hibernating queue The following is the syntax of the AMCL06 Get_Hiber_Task_Status subroutine SUBROUTINE AMCLO6 Get_Hiber_Task_Status Ret_Status Det_Status Task_Status Cmd_Line Point_Name Block_Name Time_Initiated Time_Activated Appl_Priority X_PID Appl_ID Index Req_Timeout
4. Section 2 Security 2 1 HP UX Security Introduction Some important categories File permissions UNIX has long been touted for its security features HP UX is a UNIX derivative and retains these security features Part of this security derives from the operating system architecture which is designed to prevent any program from corrupting any other program or the operating system itself Some of the most important security categories of HP UX are e File permissions e Network security e User security e Audit files These and other categories are covered in HP UX System Security which is available in the HP CD ROM documentation Each file and directory can be set to allow or deny read write and execute permission for each of the following e Owner e Group e Others These permissions can be changed with the chmod change file mode command The owner and group can be changed with the chown and chgrp commands respectively Another command chacl change access control list extends the capabilities of the chmod command by allowing the user to allow or deny file access to additional users and or groups Up to 13 additional sets of permissions called optional access control list entries can be stored in the access control list of the file Refer to the man pages and or the HP CD ROM documentation for detailed information on the chmod chown chgrp and chacl commands Continued on next page 5 9
5. n 2 Average number of messages received by the LCN side from the X side during the 15 second sampling period messages per second n 3 Average number of errors on messages received by the LCN side from the X side during the 15 second sampling period errors per second n 4 21 Spare elements allocated to communication between the X side and the LCN side n 22 30 Spare elements allocated to data access n 31 40 Allocated to events n 41 50 Allocated to file transfer n 51 70 Reserved for future expansion n 71 Average number of on node CDS read requests received by the LCN side from the X side for locally resident CDS segments during the 15 second sample period requests per second n 72 Average number of off node CDS read requests received by the LCN side from the X side for externally resident CDS segments during the 15 second sample period requests per second n 73 Average number of on node CDS write requests received by the LCN side from the X side for locally resident CDS segments during the 15 second sample period requests per second n 74 Average number of off node CDS write requests received by the LCN side from the X side for externally resident CDS segments during the 15 second sample period requests per second Continued on next page 30 Application ModuleX User Guide 5 96 4 2 RCVSTA n Parameter continued Discussion continued Table 4 3 Elements of the RCVSTA n Array continued n 75
6. AXMPERF schematic 28 Custom schematic 28 DATACHNG schematic 28 Introduction 27 Programming example 29 Plant Information Network 2 Processor Status Data Point 27 PSDP 27 S security 13 Physical 75 Procedural 75 Security HP UX Audit Files 74 File permissions 13 important categories 13 Introduction 3 Network security 74 User security 14 Security LCN AXM failover to AM 16 Directory for CL initiated applications 17 Function of XACCES 19 Overview 16 The global X access switch 18 Topics to be covered 76 Using test data with OpenDDA 17 T U V TotalPlant W WSI2 board 6 X Y Z X Windows environment 3 X access switch 1 8 XACCES external load module 79 xdaconfig 50 Sample session 51 54 Application ModuleX User Guide 5 96 READER COMMENTS Honeywell s IAC Automation College welcomes your comments and suggestions to improve future editions of this and other publications You can communicate your thoughts to us by fax mail or toll free telephone call We would like to acknowledge your comments please include your complete name and address BY FAX Use this form and fax to us at 602 313 4108 BY TELEPHONE In the U S A use our toll free number 1 800 822 7673 available in the 48 contiguous states except Arizona in Arizona dial 1 602 313 5558 BY MAIL Use this form detach fold tape closed and mail to us Title of Publication Application ModuleX User Guide Issue Date 5 96 Publicatio
7. Publication Publication Binder Binder Number Title Number Title Application Module System AX11 200 Application Module TDC 2094 3094 Administration Application Module Service Manual AX13 410 510 Application Module TDC 2094 3094 Application ModuleX Troubleshooting AX13 200 Application ModuleX TDC 2094 3094 viii Application Module User Guide 5 96 1 1 What is the Application ModuleX Section 1 Overview Introduction The Application ModuleX AXM is a major component of Honeywell s TotalPlant Open Solutions It uses a dual processor architecture a traditional Application Module AM combined with a powerful workstation processor which we will refer to as the coprocessor The Application Module provides reliability security and a link to the TDC 3000X process control subsystem that may already exist at the customer s plant preserving investment in process control hardware and software The coprocessor uses industry standard state of the art workstation hardware and software providing an open environment for development and execution of advanced process control programs and for acquisition of data for higher level production control functions The coprocessor provides a link to the Plant Information Network an Ethernet LAN that can include PCs workstations and mainframes all contributing to the overall operation of the plant Figure 1 1 shows a block diagram of the AXM Figure 1 1 AXM Block Diagram Plan
8. These applications can therefore take a great deal of time to complete actions and use a great deal of channels and memory in the AM side of the AXM to serve the large data access requests Continued on next page 5 96 Application Module User Guide 47 6 1 Introduction continued Configuration goals Resources Data access channels The configuration functionality is provided to allow the user to tune certain configuration settings to match up with the mix of application types executing in an AXM The following are the ultimate goals e Assure a clean path to the valve for the control applications coexisting in the same AXM with applications used for gathering data for information applications e Do not allow any type of platform service that can take very long period of time like File Services to be able to block control application requests e Provide sufficient low priority resources so that low priority requests are not blocked out indefinitely There are two resources that the user can manage e Data access channels e Data access servers There are only a limited number of channels available for interfacing between the AM side and X side You must assure that a portion of these resources are set aside for use by control applications when needed In an AXM with control applications coexisting with a large number of noncontrol applications the potential exists for the noncontrol applications t
9. i CL Suspended pplication a a Termination Code CL Active or gt EXEC DDA TERMINATE 54125 38 Application ModuleX User Guide 5 96 5 2 CL Support Supporting functions The following background CL calls are available in the AMCLO6 set in LCN release R431 and later e AMCLO06 Initiate_Task Initiates an OpenDDA application capable of hibernating and receiving background CL events e AMCL06 Activate_Task Sends an activate event to a CL initiated hibernating OpenDDA application e AMCL06 Terminate_Task Sends a terminate event to a CL initiated hibernating OpenDDA application providing a graceful shutdown of the application e AMCL06 Get_Hiber_Task_Status Obtains the current status of a CL initiated hibernating OpenDDA application capable of receiving background CL events Continued on next page 5 96 Application Module User Guide 39 5 2 CL Support Continued Initiate_Task The background CL subroutine AMCL06 Initiate_Task is used to initiate a new instance of an OpenDDA application After the call is made the background CL suspends execution and enters a wait condition until the OpenDDA application has initiated and entered hibernation The user provides an application name and once the application has entered hibernation a unique application id is returned to the CL block The CL should store this application id in a CDS parameter or oth
10. Average number of words in on node CDS read requests received by the LCN side from the X side for locally resident CDS segments during the 15 second sample period words per second n 76 Average number of words in off node CDS read requests received by the LCN side from the X side for externally resident CDS segments during the 15 second sample period words per second n 77 Average number of words in on node CDS write requests received by the LCN side from the X side for locally resident CDS segments during the 15 second sample period words per second n 78 Average number of words in off node CDS write requests received by the LCN side from the X side for externally resident CDS segments during the 15 second sample period words per second n 79 100 Spare elements allocated to CDS transfer 5 96 Application Module User Guide 31 4 3 RCVCNT n Parameter Discussion The RCVCNT n parameter is an array of 100 real type numbers that provides a set of statistics based on the total number of data transfers during a 15 second period from the X side to the LCN side Table 4 4 Elements of the RCVCNT n Array Array Element Contents n 1 Total size of messages received by the LCN side from the X side during the 15 second sampling period bytes n 2 Total number of messages received by the LCN side from the X side during the 15 second sampling period n 3 Total number of errors on messages r
11. SRCVCNT n Parameter 32 4 4 XMITSTA n Parameter 34 4 5 SXMITCNT n Parameter 35 SECTION 5 HIBERNATION 44444244000n200000000n nn nun annnnnnnnn nenn nn nnnnnnnnnnnnnnnnnnnnnnnen 37 5 1 OLE RL RE LIE EEE RETTET EEE LEERE EE ZE 37 5 2 CLeSUPPOMs Eine alada 39 5 3 OpenDDA SUPPOTE ca at aac 43 5 4 X Side Support T sait rennen a dE rat 44 SECTION 6 CONFIGURATION OF DATA ACCESS PRIORITY uzu2u4u244000n000n0nn 00 47 6 1 Introduction are Begehren 47 6 2 The ee Te BEE 50 5 96 Application Module User Guide Figures and Tables Figure 1 1 Figure 1 2 Figure 1 3 Figure 1 4 Figure 1 5 Figure 3 1 Figure 5 1 Table 1 1 Table 1 2 Table 1 3 Table 3 1 Table 3 2 Table 3 3 Table 3 4 Table 3 5 Table 3 6 Table 3 7 Table 4 1 Table 4 2 Table 4 3 Table 4 4 Table 4 4 Table 4 5 Table 4 6 Table 5 1 AXM Block DAME dais 1 Standalone Coprocessor Configuration 7 Minimum Network Configuration with a JUS cs T 8 Minimum Network Configuration with an MP AXMST1 9 Initial Setup and Maintenance Configuration 11 Base File System Gtruchure ooooooccccnnnccccnnconanannnconnncnnnnnna nono non cnnnncnannnns 21 Relationship of CL Events and X side Hibernation 38 AXM Five Slot Module Configuration 4 AXM Ten Slot Module Configuration 4 Function of AXM COMPONENTS eei aeara di 5 Key Directories anaiai supers ann Be 22 Ref
12. Spare elements allocated to data access n 31 40 Allocated to events n 41 50 Allocated to file transfer n 51 70 Reserved for future expansion n 71 Average number of host task initiation requests sent from the LCN side to the X side during the 15 second sample period requests per second n 72 100 Spare elements allocated to CDS transfer 34 Application Module User Guide 5 96 4 5 XMITCNT n Parameter Discussion The XMITCNT n parameter is an array of 100 real type numbers that provides a set of statistics based on the total number of data transfers during a 15 second period from the LCN side to the X side Table 4 6 Elements of the XMITCNT n Array Array Element Contents n 1 Total size of messages sent from the LCN side to the X side during the 15 second sampling period bytes n 2 Total number of messages sent by the LCN side to the X side during the 15 second sampling period n 3 Total number of errors on messages sent by the LCN side to the X side during the 15 second sampling period n 4 20 Spare elements allocated to communication between the X side and the LCN side n 21 Total number of point parameters sent by the LCN side to the X side and received by the LCN side from the X side during the 15 second sampling period n 22 30 Spare elements allocated to data access n 31 40 Allocated to events n 41 50 Allocated to file transfer n 51 70 Reserved for future expansion
13. TDC_Open hwiaclicense TDC_Open log TDC_Open common common axm common share LCN bin lib share newconfig I LCN pers alt 54287 5 96 Application ModuleX User Guide 21 3 2 Directories Summary of key Table 3 1 summarizes the key directories and lists the basic types of files in directories each The files indicated in the table are explained in greater detail in subsequent tables Table 3 1 Key Directories Directory Contents var opt TDC_Open common Temporary and log files includes the CDS and LCN daemon log files opt TDC_Open common bin Executable files cds_har cdsdaemon lendaemon xaccess display_appls kill_appls and xdaconfig opt TDC_Open common lib Libraries ibcds sl libhiber si and liblxs sl opt TDC_Open common newconfig Contains reference copies of the base configuration files and scripts that are used at system startup opt TDC_Open common share Include files cds h and cds_err h axm_common h and hiber h opt TDC_Open common share LCN Boot file boot _stub bo opt TDC_Open axm share LCN pers Personality files opt TDC_Open common share LCN qit QLT files files used for test etc opt TDC_Open common Contains the working copies of the base configuration files and scripts that are used at system startup etc Scripts that run at startup users axm Executables or symbolic links to executables for all CL initiated
14. a parameter An X side application cannot change the global X access switch however a configuration file xaccess cfg on the X side provides the restart value for the switch The xaccess cfg file is modifiable by the tool xaccess if the user has execute permission on the tool and read write permission on the configuration file root only in both cases as shipped The configuration file xaccess cfg is in the directory opt TDC_Open common newconfig and the tool xaccess is in the directory opt TDC_Open common bin In all cases the READWRIT state cannot be set unless the XACCES external load module is loaded in the AM side Sample session with The following is a sample session running the tool xaccess xaccess cd opt TDC_Open common bin xaccess XACCESS Configuration Read writes by all applications allowed 0 Read only 1 Read writes by LCN initiated applications allowed 2 Read writes by all applications allowed Enter the new value for X to LCN access 0 1 or 2 2 Continued on next page 18 Application Module User Guide 5 96 2 3 LCN Security Continued ATTENTION Function of XACCES ATTENTION XACCESS is not a checkpointed parameter When the AXM node personality is loaded the restart state of XACCESS is determined solely by a value encrypted in the X side file xaccess cfg The X side must be running for the AXM node personality to load If the X side is restarted while the n
15. example of the use of OpenDDA functionality to access LCN data from an application This publication is not intended to serve as a reference manual The application developer should refer to the OpenDDA publications for detailed reference material The system administrator should refer to the Application ModuleX System Administration manual for specific system administration procedures and the maintenance person should refer to Application Module Service and Application ModuleX Troubleshooting for reference information This publication supports AXM release R200 and TDC 3000X software releases R430 and later R4xx versions and R500 and later R5xx versions 5 96 Application Module User Guide il Application Module User Guide 5 96 Table of Contents SECTION 1 OVERVIEW nie een ia nd 1 1 1 Introduction Hrsg 1 1 2 Application Module Architecture 4 1 3 Application Module System Configurations 7 SECTION 2 SECURIT E 13 2 1 PEUX SOCUILY a neigen 13 2 2 Physical and Procedural Security 00ccceceeeeeeaeeeeeeeeeeeeaeaaeeeeeeeeeeeaea 15 2 3 LEN RTE 16 SECTION 3 FILE SYSTEM 2 2 2222 Ee EES 21 3 1 MEDIE e Sota E E L AE et ARR Ee eae See 21 3 2 NIC ee ER 3 3 ESS A der de Anne aad Se ji ade 23 SECTION A PERFORMANCE MEASUREMENT uuusssssssannnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 27 4 1 SO ne O ie 27 4 2 SRCVSTA n Parameter 30 4 3
16. script that starts the proper daemon based on whether the device is an AXM or a UXS and on what type of coprocessor board it uses xaccess cfg Configuration file that defines the as shipped restart state of the Global X access Switch READONLY xdapriority cfg Configuration file that defines the as shipped number of communication channels AXM R200 and Data Access servers reserved for high priority requests Continued on next page 5 96 Application ModuleX User Guide 23 3 3 Files Continued Working configuration files Data files The files in Table 3 3 reside in the etc opt TDC_Open common directory Table 3 3 Working Configuration Files File Purpose personality config This is a link to a file that contains the personality files location and type UXS or AXM idc3krc Working copy of a script that starts the proper daemon based on whether the device is an AXM or a UXS and on what type of coprocessor board it uses normally a copy of the reference script in opt TDC_Open common newconfig unless user has made changes to the working copy xaccess cfg Configuration file that defines the current restart state of the Global X access Switch the utility program xaccess modifies this file xdapriority cfg AXM R200 Configuration file that defines the current number of communication channels and Data Access servers reserved for high priority requests The uti
17. the 15 second sample period n 77 Total number of words in on node CDS write requests received by the LCN side from the X side for locally resident CDS segments during the 15 second sample period n 78 Total number of words in off node CDS write requests received by the LCN side from the X side for externally resident CDS segments during the 15 second sample period n 79 100 Spare elements allocated to CDS transfer 5 96 Application Module User Guide 33 4 4 XMITSTA n Parameter Discussion The XMITSTA n parameter is an array of 100 real type numbers that provides a set of statistics based on the average number of data transfers during a 15 second period from the LCN side to the X side Table 4 5 Elements of the XMITSTA n Array Array Element Contents n 1 Average size of messages sent from the LCN side to the X side during the 15 second sampling period bytes n 2 Average number of messages sent by the LCN side to the X side during the 15 second sampling period messages per second n 3 Average number of errors on messages sent by the LCN side to the X side during the 15 second sampling period errors per second n 4 20 Spare elements allocated to communication between the X side and the LCN side n 21 Average number of point parameters sent by the LCN side to the X side and received by the LCN side from the X side during the 15 second sampling period point parameters per second n 22 30
18. users can log in from the network and perform system administration and development activities The console terminal connection may also be required for system maintenance If the network is down the console is the only device from which you can access HP UX The console is also the only device from which you can observe the HP UX boot process The console device can be a VT100 or a device doing VT100 emulation Honeywell recommends and supports the use of a UXS or the optional Model MP AMXST1 System Administration and Development Station Either of these devices can be connected to the AXM console port with a serial null modem communications cable Both are shipped with Kermit software which can provide the VT100 emulation Figure 1 5 Initial Setup and Maintenance Configuration Ethernet LAN Null Modem Cable 9600 Baud Serial EE GC Console gt CD Rom Co I Device DAT processor U Xs or AM VT100 or A XM Workstation LCN 51318 The Application ModuleX Service manual contains instructions on information connecting the VT100 like terminal UXS or Model MP AMXSTI System Administration and Development Station to the console port of the AXM The Application ModuleX System Administration manual contains the procedures to invoke Kermit and perform the required AXM configuration 5 96 Application ModuleX User Guide 11 12 Application Module User Guide 5 96
19. 4 Mw additional memory Used only with HMPU version WSI2 Workstation Interface board Contains the coprocessor board Available with the following coprocessor memory options e 32MB e 64 MB e 128 MB 256 MB Available with the following coprocessor speed options e 64 MHz e 100 MHz WSI2 I O I O paddleboard associated with the WSI2 board Provides interface to the PIN and to a console terminal or modem Continued on next page 5 96 Application ModuleX User Guide 1 2 Application ModuleX Architecture continued Function of components continued Coprocessor hardware Coprocessor software Table Table 1 3 Function of AXM Components continued Component Function Hard Disk Holds a primary hard disk drive and an optional hard disk drive Drive Tray Each drive can be either e 525 MB e 1GB e 2GB This tray occupies two card slot positions HDDT I O I O paddleboard associated with the hard disk drive tray Contains an optional SCSI interface connector that is not used with AXM and that must have a cable terminator installed The coprocessor a Hewlett Packard Model 743 processor board is mounted on the WSI2 board This board is also used in the Release 200 Universal Station X The board is based on the Hewlett Packard PA RISC chip Precision Architecture Reduced Instruction Set Computing The coprocessor is available in 64 MHz and 100 MHz versions an
20. 6 Application Module User Guide 13 2 1 HP UX Security Continued Network security User security Audit Files The file usr adm inetd sec allows you to allow or deny specific services to individual users or groups of users Examples of services are login rlogin telnet and ftp Workstations are normally shipped with all of these permissions set to allow minimum security The AXM on the other hand is shipped with all permissions set to deny for maximum security You the user can relax this security and allow whatever level of access is commensurate with the environment and mission of your AXM HP UX includes the traditional UNIX security features that are part of the user management process Each user has a login name user ID group ID and a password that is stored only in encrypted form Passwords are not stored anywhere in the system in plain text unencrypted form They are encrypted using a highly secure technique When a user logs in and enters his password it is encrypted and compared with the encrypted version stored in the system In high security situations it is important to physically secure data transmission media between the user s terminal and the AXM to prevent interception of login sequences which include the password in plain test It is also important to educate users on the types of passwords to use and the types to not use It is also important to establish procedures that require the
21. CLO06 18 AMCLO06 Activate Task 39 40 AMCL06 Get_Hiber_Task_Status 39 42 AMCLO6 Initiate_Task 39 40 AMCLO6 Terminate_Task 39 41 Application ModuleX Architecture Chassis types 4 Coprocessor hardware 6 Coprocessor software 6 Five Slot Module configuration 4 Function of components 5 Ten Slot Module configuration 4 axm group 17 AXMPERE schematic 27 C chacl 73 chgrp 13 chmod 3 chown 3 Components of the AXM 5 configuration files 23 Configurations Expanded network configuration 70 Minimum network configuration with MP AMXST1 workstation 9 Minimum network configuration with UXS 8 Standalone coprocessor 7 Where to find more information control domain 2 coprocessor 6 D E Data Access Priority 47 Introduction 47 xdaconfig 50 Data Definition and Access 2 DATACHNG schematic 27 28 DDA 2 display_appls 44 F G File system Configuration files discussion 23 Continued on next page 25 Data files 24 Discussion 27 Executables 25 Modified HP UX files 26 Reference configuration files 23 Summary of key directories 22 Working configuration files 24 Function of AXM components 5 H Hibernation 37 Advantages 37 CL Support 39 OpenDDA Support 43 HP UX 6 LJ information domain 2 K L M N kill_appls 45 O OpenDDA 2 OpenUSE 2 5 96 Application Module User Guide 53 Index P Q R xdapriority cfg 50 PA RISC 6 Performance measurement Accessing the parameters from the LCN side 27
22. ERFPARM 10 PARAMETER SRCVSTA NUMBER ARRAY 1 100 AVERAGE NUMBER OF TRANSMISSIONS 11 END PERFPARM 12 13 CUSTO 14 PARAMETER NODE_PRE PERFPARM PROCESSOR STATUS DATA POINT 15 VALUE PRSTS19 NODE 19 IS AN AM NODE 16 17 PARAMETER R_VALUES NUMBER ARRAY 1 100 18 END CUSTOM 19 20 BLOCK PERFSTAT POINT PERFSTAT AT GENERAL 21 22 TRANSFER THE PERFORMANCE PARAMETERS TO THE CDS PARAMETERS ONCE YOU HAVE 23 THEM IN THE CDS PARAMETERS THEY BECOME NORMAL POINT PARAMETERS 24 FOR EXAMPLE YOU COULD PUT THEM IN A HISTORY GROUP 25 AT A MINIMUM THEY WILL APPEAR TOGETHER ON THE CDS PAGE OF THE POINT 26 THE ASSIGNMENT STATEMENTS BELOW COULD BE REPLACED BY A FOR LOOP 27 28 6 SET R_VALUES 1 NODE_PRF SRCVSTA 1 29 40 SET R_VALUES 2 NODE_PRF S RCVSTA 2 30 74 SE R_VALUES 3 NODE_PRF S RCVSTA 3 31 108 SE R_VALUES 4 NODE_PRF SRCVSTA 4 32 33 END PERFSTAT 34 END PACKAGE XXXXX X No errors detected 5 96 Application Module User Guide 29 4 2 RCVSTA n Parameter Discussion The RCVSTA n parameter is an array of 100 real type numbers that provides a set of statistics based on the average number of data transfers during a 15 second period from the X side to the LCN side Table 4 3 Elements of the RCVSTA n Array Array Element Contents n 1 Average size of messages received by the LCN side from the X side during the 15 second sampling period bytes
23. EXEC DDA HIBERNATE EVENT EVENT_DATA evt_data STATUS exec_status The variable evt_data is a structure that returns information to the application as it exits hibernation as a result of an AMCLO06 Activate_Task or AMCL06 Terminate_Task call and resumes execution of code The information returned is listed in the following table Table 5 1 Event Data Structure Field Description event_type An integer code that represents the type of the event ACTIVATE TERMINATE or NO_EVENT event_status The status associated with the event function point_name The entity that initiated the wakeup call event_block Name of the block that activated terminated the application init_block Name of the block that initiated the application event_time The HP UX time when the event occurred init_time The LCN time when the application was initiated event_string The CL event string ENT call refer to lt For more information about the EXEC DDA HIBERNATE E Section 6 of the OpenDDA Reference Manual 5 96 Application Module User Guide 43 5 4 X Side Support Tools Introduction Two of the utilities provided by Honeywell in the HP UX directory opt TDC_Open common bin are used to enable the user to view information about all CL initiated X side applications and kill any of these applications particularly useful for those in hibe
24. Honeywell Application ModuleX User Guide AX09 200 Tetal Plant Honeywell Application ModuleX Application ModuleX User Guide AX09 200 Release 200 5 96 Tetal Plant Copyright Notices and Trademarks Copyright 1994 by Honeywell Inc Revision 03 May 1 1996 While this information is presented in good faith and believed to be accurate Honeywell disclaims the implied warranties of merchantability and fitness for a particular purpose and makes no express warranties except as may be stated in its written agreement with and for its customer In no event is Honeywell liable to anyone for any indirect special or consequential damages The information and specifications in this document are subject to change without notice TotalPlant and TDC 3000 are U S registered trademarks of Honeywell Inc OpenUSE is a trademark of Honeywell Inc Other brand or product names are trademarks of their respective owners Honeywell Industrial Automation and Control Automation College 2820 West Kelton Lane Phoenix AZ 85023 602 313 5669 Application Module User Guide 5 96 About This Publication This publication is intended for Application ModuleX users application developers and administrators It includes an overview of the Application Module and describes its function in the Honeywell TotalPlant environment It addresses the security features of the Application Module and includes an introduction and
25. R200 An X side utility that allows the user to display information about CL initiated X side applications kill_appls AXM R200 An X side utility that allows the user to kill CL initiated X side applications including hibernating applications xdaconfig AXM R200 A configuration tool that allows the HP UX root user to adjust the number of communication channels and the number of Data Access servers reserved for high priority requests Continued on next page 5 96 Application Module User Guide 25 3 3 Files Continued Libraries Modified HP UX files These libraries reside in the opt TIDC_Open common lib directory Table 3 6 Library Files File Purpose libcds sl A library for Honeywell use only libhiber s Libraries used by OpenDDA applications libixs sl These are HP UX files that are modified Table 3 7 Modified HP UX Files File Purpose etc rc This is Honeywell s modified version of the HP UX script that is executed each time HP UX boots up one of its functions is to execute tdc3krc which starts the appropriate Honeywell daemons cndaemon cdsdaemon and optionally the license servers etc services Two entries are placed in this file these entries reserve communications ports for Icndaemon and the cdsdaemon etc passwd A user axm is placed in this file with a home directory of users axm which is creat
26. acterized by minimum Ethernet LAN networks In the standalone configuration the AXM is not connected to a LAN In the minimum configurations with MP AMXSTI workstation or UXS a single point to point LAN is used between the AXM and the development administration station These are the simplest configurations and the most secure with respect to network access At the other extreme the AXM can be connected to a complex Ethernet LAN that functions as the Plant Information Network In this environment the AXM can coexist on the PIN with multiple devices and platforms such as UXS workstation VAX PC Macintosh and mainframe With appropriate software and configuration these diverse devices can utilize and exchange LCN data and use this data in plant and process management applications Continued on next page 10 Application Module User Guide 5 96 1 3 Application ModuleX System Configurations continued Initial setup and maintenance configuration Where to find more The AXM is shipped with networking enabled but configured for maximum security Permissions for all services in usr adm inetd sec are set to deny Root is the only user allowed to log in and this is allowed only from the local console terminal If the AXM is to be connected to the Ethernet LAN you must connect a local console terminal and then log in as root and perform the necessary configuration changes After the initial configuration authorized
27. all Det_Status OUT NUMBER Detailed return status Appl_ID IN STRING Application identifier Event_String IN STRING String passed to application X_Task_Timeout IN TIME X side timeout value Req_Timeout IN TIME LCN side timeout value Refer to Appendix I of the CL AM Reference Manual for more information about the functionality of the call and for definition of the arguments Continued on next page 40 Application Module User Guide 5 96 5 2 CL Support Continued Terminate_Task The background CL subroutine AMCL06 Terminate_Task is used to send a terminate event to a CL initiated hibernating OpenDDA application This provides a graceful shutdown of a hibernating OpenDDA application After the call is made the background CL suspends execution and enters a wait condition until the OpenDDA application has received and processed the event and terminated its execution The user provides an application id obtained from AMCLO06 Initiate_Task and an event string which is passed to the OpenDDA application Syntax of the AMCL06 Terminate_Task subroutine SUBROUTINE AMCLO6 Terminate Task Ret_Status OUT NUMBER Return status of the call Det_Status OUT NUMBER Detailed return status Appl_ID IN STRING Application identifier Event_String IN STRING String passed to application X_Task_Timeout IN TIME X side timeout value Reg_Timeout IN TIME LCN side timeout value
28. applications opt DDA See OpenDDA User s Guide subsection 4 1 opt hwiaclicense See License Installation and Administration AXM var hwiaclicense log See License Installation and Administration AXM 22 Application ModuleX User Guide 5 96 3 3 Files Configuration files discussion Reference configuration files Certain key configuration files reference copies are stored in the directory opt TDC_Open common newconfig Working copies are placed in etc op TDC_Open common where they are actually used during startup If the user modifies any of the working files it is easy to go back to the original reference version Also if Honeywell updates software changes are placed only in the reference copies to avoid overwriting the working files that the user may have customized Therefore after an update the user should check the files in opt TDC_Open common newconfig to see if Honeywell has made any changes and should incorporate these changes in the working copies in opWTDC_Open common The files in Table 3 2 reside in the op TDC_Open common newconfig directory Table 3 2 Reference Configuration Files File Purpose personality config Indicates that the device is an AXM personality config axm Identifies personality files type and location personality config axmk Identifies K4LCN personality files type and location R500 rc Reference copy of a script that is executed on startup tac3krc Reference
29. ation is executing By contrast an application that uses hibernation remains in memory between executions This offers the following advantages e Initialization reading in from disk resolving external data and so forth is performed only once e Data remains persistent between executions e The CL does not use an AXM CL queue slot while the application is hibernating Continued on next page 5 96 Application Module User Guide 37 9 1 Event relationships Overview Continued The following diagram shows the relationship between CL events and execution of an X side application that hibernates It will be useful to refer to this diagram while reading the remainder of this section Figure 5 1 Relationship of CL Events and X side Hibernation CL X side i Initiate_Task icati CL Active FS nitiate_Task Application EXEC DDA INITIALIZE CL Suspended Application id Lei Initialize Resolve External References etc CL Active gt CL Active u Activate_Task EXEC DDA HIBERNATE EVENT z Hibernation L gt CL Suspended Application id ma Application Code CL Active E Activate_Task CL Active CL Suspended gt Application id gt EXEC DDA HIBERNATE EVENT t Hibernation mt Application Code CL Active E Terminate_Task EXEC DDA HIBERNATE EVENT lt a Hibernation CL Active
30. d in a configuration file xdapriority cfg that is located in etc opt TDC_Open common The configuration file defines the number of channels reserved for high priority requests as opposed to low priority requests The file also defines the number of Data Access servers assigned to high priority requests as opposed to low priority requests As shipped from Honeywell in the AXM the xdapriority cfg file is set to four high priority DA servers and 10 high priority channels For UXS the file is set to zero for both high priority servers and channels A configuration tool is provided to adjust these two priority related configuration items The tool xdaconfig is in the directory opt TDC_Open common bin The tool is a command line tool that asks the user for the number of channels reserved for high priority requests 0 to 20 and for the number of Data Access servers reserved for high priority requests 0 to 4 The remaining channels and Data Access servers are then assigned to low priority For security the configuration file is not a text file In addition the configuration file and the configuration tool have their access restricted to system administrators only root level Low priority requests cannot be serviced by a high priority queue or by a high priority Data Access serve however high priority requests can be serviced by a low priority queue and servers Therefore if no DA servers are configured for high priority setting the nu
31. d with 32 MB 64 MB 128 MB or 256 MB of memory The coprocessor operating system is version 9 05 of HP UX HP UX is based on UNIX System V It includes many of the most popular extensions from the University of California Berkley version of UNIX and provides full or partial compliance to numerous industry and international standards For more information about the HP UX operating system refer to the Hewlett Packard CD ROM documentation Application Module User Guide 5 96 1 3 Application ModuleX System Configurations Introduction The Application ModuleX can be used in a variety of ways We will cover a few configurations that we anticipate will be typical usage scenarios but they are not intended to represent all possible configurations Standalone The standalone coprocessor configuration shown in Figure 1 2 is the coprocessor simplest configuration Its characteristics are Shipped with one or more applications preloaded and ready to run There is no Ethernet LAN PIN connection therefore there is no access to external media which impacts as follows Data generated by an application cannot be used by other devices You cannot backup the hard disk You cannot load optional software or load software upgrades If the hard disk fails it must be replaced with a new drive that has the operating system and applications preloaded by the application supplier unless you have the optional DAT drive and have the
32. e configuration version of the AXM Table 1 2 AXM Ten Slot Module Configuration Slot Front Rear 10 Unusable slot 9 Unusable slot 8 Hard Disk Drive Tray 7 occupies two slots HDDT I O 6 WSI2 WSI2 1 0 5 Optional Application Board Optional I O board 4 Optional memory board 3 QMEM 4 2 LLCN LCN 1 0 1 HMPU Continued on next page 4 Application Module User Guide 5 96 1 2 Function of components Application ModuleX Architecture continued The following table lists the function and options for each of the components listed in Tables 1 1 and 1 2 Table 1 3 Function of AXM Components Component Function K4LCN Node processor used in Five Slot Module AXM R500 Available with the following memory sizes e 4Mw Note AXM R200 requires a minimum of 6 Mw e 8Mw e 16 Mw Has hardware floating point support K2LCN Node processor used in Five Slot Module AXM Available with the following memory sizes e 4 Mw Note AXM R200 requires a minimum of 6 Mw e 8Mw Does not have hardware floating point support HMPU Node processor used in Ten Slot Module AXM Has 2 Mw of memory Has hardware floating point support LLCN LCN interface board used only with HMPU version this function is built into the K2LCN and KALCN LCN I O I O paddleboard that provides connection to the LCN A and LCN B cables QMEM 4 Memory board provides
33. e backups and for software installations and upgrades You can develop AXM applications from a window at the UXS while logged into the AXM The UXS can be used as the console terminal of the AXM for initial network configuration and for maintenance this is accomplished by connecting the UXS serial printer port to the AXM console port with a null modem cable and by using terminal emulation software in the UXS Kermit software is supplied with the UXS From the UXS or from any US or UXS on the LCN you can activate CL that uses the AMCLO6 extension set to initiate AXM applications Figure 1 3 Minimum Network Configuration with a UXS Point to Point Ethernet LAN C D CD Rom Co Co A DAT processor processor H AM AM uXs US LCN LCN 51316 Continued on next page Application Module User Guide 5 96 1 3 Application ModuleX System Configurations continued Minimum network This configuration is similar to the previous configuration except that the configuration with MP XS js replaced by the Honeywell Model MP AMXSTI System AMXST1 workstation Administration and Development Station This device is a workstation that includes a DAT drive and CD ROM drive It is an option available from Honeywell for application development and or system administration The characteristics which are similar to the previous configuration are The AXM and wor
34. eceived by the LCN side from the X side during the 15 second sampling period n 4 21 Spare elements allocated to communication between the X side and the LCN side n 22 30 Spare elements allocated to data access n 31 40 Allocated to events n 41 50 Allocated to file transfer n 51 70 Reserved for future expansion n 71 Total number of on node CDS read requests received by the LCN side from the X side for locally resident CDS segments during the 15 second sample period n 72 Total number of off node CDS read requests received by the LCN side from the X side for externally resident CDS segments during the 15 second sample period n 73 Total number of on node CDS write requests received by the LCN side from the X side for locally resident CDS segments during the 15 second sample period n 74 Total number of off node CDS write requests received by the LCN side from the X side for externally resident CDS segments during the 15 second sample period Continued on next page 32 Application ModuleX User Guide 5 96 4 3 RCVCNT n Parameter continued Discussion continued Table 4 4 Elements of the RCVCNT n Array continued n 75 Total number of words in on node CDS read requests received by the LCN side from the X side for locally resident CDS segments during the 15 second sample period n 76 Total number of words in off node CDS read requests received by the LCN side from the X side for externally resident CDS segments during
35. ed during installation etc group A group axm is placed in this file 26 Application Module User Guide 5 96 4 1 Overview Introduction Accessing the parameters from the LCN side Accessing the Section 4 Performance Measurement There are four new Processor Status Data Point PSDP parameters available as part of the AXM LCN side functionality the node personality Each of the four PSDP parameters is an array of 100 real type elements These four PSDP parameters are RCVSTA n Provides a set of statistics based on the average number of data transfers during a 15 second period from the X side to the LCN side RCVCNT n Provides a set of statistics based on the total number of data transfers during a 15 second period from the X side to the LCN side XMITSTA n Provides a set of statistics based on the average number of data transfers during a 15 second period from the LCN side to the X side XMITCNT n Provides a set of statistics based on the total number of data transfers during a 15 second period from the LCN side to the X side Three methods that can be used to access the parameters are Use the AXMPERF schematic R500 only Use the DATACHNG schematic Build a custom schematic Access from CL You can access these parameters from the X side using OpenDDA parameters from the applications or PC Data Exchange PCDE PCDE is an X layer applicat
36. er point parameter and then complete the execution of the CL block The application id returned from the subroutine is needed to subsequently activate AMCL06 Activate_Task and terminate AMCL06 Terminate_Task the application Syntax of the AMCL06 Initiate_Task subroutine SUBROUTINE AMCLO6SInitiate_Task Ret_Status OUT NUMBER Return status of the call Det_Status OUT NUMBER Detailed return status Appl_ID OUT STRING Application identifier Cmd_Line IN STRING X side application command line X_Task_Timeout IN TIME X side timeout value Req_Timeout IN IME LCN side timeout value Refer to Appendix I of the CL AM Reference Manual for more information about the functionality of the call and for definition of the arguments Activate Task The background CL subroutine AMCL06 Activate_Task is used to send an activate event to a CL initiated hibernating OpenDDA application After the call is made the background CL suspends execution and enters a wait condition until the OpenDDA application receives and processes the event presumably executes for a while and subsequently returns to hibernation The user provides an application id obtained from AMCL06 Initiate_Task and an event string which is passed to the OpenDDA application Syntax of the AMCL06 Activate Task subroutine SUBROUTINE AMCLO6 Activate Task Ret_Status OUT NUMBER Return status of the c
37. erence Configuration Files 0 ccccceceeceeeeeeeeeeeeeaeeeeeeeeeeeesaaeeees 23 Working Configuration Files 24 Data EE 24 Executable Filds ENNEN aE needa eee 25 Library TTT 26 Modified HP UX EE 26 Using the AXMPERF Gchemate nacos 28 Using the DATACHNG Schematic 00 cceceeeceeeeeeeeeeeeeeaeeeeeeeeeeeeas 28 Elements of the RCVSTA n Array 30 Elements of the RCVCNT n Array 32 Elements of the RCVCNT n Array 33 Elements of the XMITSTA n Array 34 Elements of the XMITCNT n Amay 35 Event Data Structure 43 vi Application Module User Guide 5 96 Acronyms ASM asian Application ModuleX Application Module with Extensions DA Ti A A ede Digital Audio Tape LAN a o a a RA se tte Local Area Network Bel EE Local Control Network OpenDDA EE Open Data Definition and Access PODER rares Rene initiate ts PC Data Exchange PINS cae a RM nt Ne NN nn un Plant Information Network SAM rte ee Pan M Ress a RAITA AA FAOD otre de System Administration Manager TOP doi Transmission Control Protocol Internet Protocol RRG Total Distributed Control TP a a dos Total Plant History A O Bern erh de SE tel duel ni me Al cate ca Universal Control Network US ra ee ass Universal Station A ner se Universal StationX Universal Station with Extensions MN TR a A BE der Workstation Interface 5 96 Application Module User Guide vii References
38. ermission OpenDDA Data Definition and Access provides the software tools that allow an application to access LCN data to read data and with security set properly to write data An application that uses OpenDDA can be compiled with test data imbedded in the program The application can be debugged off line using this test data instead of on line with live LCN data The application can actually be developed and tested in a UXS ora workstation however only the AXM can access live data Continued on next page 5 96 Application ModuleX User Guide 17 2 3 LCN Secu rity Continued The global X access switch The global X access switch controls when an X side application can write LCN data It is implemented by a Processor Status Data Point PSDP parameter called XACCESS which has three possible states e READONLY The X side can read but cannot write LCN data default e RW LCN The X side can read LCN data but can write LCN data only from applications that are initiated by CL on the LCN side e READWRIT The X side can read and write LCN data from CL initiated and non CL initiated applications this state cannot be set by any means unless the external load module XACCES is loaded The state of the global X access switch can be changed From the keyboard with Engineer access e From an LCN side CL program using a call available in AMCLO6 the global X access switch cannot be changed by a normal CL write to
39. h a point e one or all instances of the same application name or e applications that are either running or hibernating The tool is especially useful for killing X side applications that can hibernate because an application that is in hibernation cannot be killed by aborting the CL or inactivating the point to which the CL is attached Syntax There are two ways to invoke this tool One way is to specify the application name and the other way is to specify the associated point The syntax when specifying the application name is kill_appls A application name i application_id p process_id a The syntax when specifying the point name is kill_appls P point_name i application_id p process_id a One of the following three switches is required i application_id Application identifier assigned when the application is initiated by the AMCL06 Initiate_Task call p process_id HP UX process id a If used with the application_name argument all executions of the application will be aborted If used with the point_name argument all X side applications associated with the point will be aborted NOTE All options are case sensitive For additional information about this utility see Appendix I of the CL AM Reference Manual 5 96 Application Module User Guide 45 46 Application Module User Guide 5 96 Section 6 Configuration of Data Access Priority 6 1 Introduction ATTENTION
40. in access and access to critical files and directories A policy and schedule for changing passwords A policy requiring users to log off or use lock command when not at the terminal A policy and procedure regarding audit use review and analysis 5 96 Application Module User Guide 15 2 3 LCN Security Overview The TDC 3000X has a well deserved reputation for reliability Security features are incorporated in the architecture and design of the AXM hardware and software in order to preserve this reliability These features are designed to protect the LCN control environment from X side failures Intrusion by hackers or unauthorized users on the network Corruption while testing new software that is not fully debugged Human error Topics to be covered The security features of the AXM environment that will be covered are AXM failover to AM Special directory for CL initiated applications OpenDDA development using test data The global X access switch The AMCLO06 Store_XAccess call The XACCES external load module AXM failover to AM If an X side failure occurs the AM will continue to function as follows The node status will go to WARNING Page 2 of the Status Detail Display will display the message WS Interface OK gt WARNING Work Station Interface In Process Please wait CL applications that do not communicate with the X side will continue to function normally These will be applications that do not u
41. ion X side available from Honeywell that allows you to access LCN point parameter data from PCs and other devices located on the PIN Continued on next page 5 96 Application Module User Guide 27 4 1 Overview continued AXMPERF schematic DATACHNG schematic Custom schematic CL access The following procedure can be used to view the PSDP statistics parameters NOTE This schematic is available only on R500 or later Table 4 1 Using the AXMPERF Schematic Step Action 1 Press the SCHEM button 2 Enter AXMPERF and then press ENTER 3 Select SPECIFY AXM box and enter number of desired node after SPRSTS in entry port 4 Press ENTER and all implemented values will be displayed live data The following procedure can be used to view the PSDP statistics parameters NOTE The Toolkit set of schematics TLK1 must be copied to the HM The procedure is covered in the LCN Guidelines manual Table 4 2 Using the DATACHNG Schematic Step Action 1 Press the SCHEM button 2 Enter DATACHNG and then press ENTER 3 Select an empty box on the left and enter the name of the desired parameter in the form SPRSTSnn xx where nn is the node number and xx is the parameter name For example to display the second element of the RCVSTA n array average number of transmissions for AXM node 19 enter SPRSTS19 SRCVSTA 2 4 Press ENTER and the value will be displayed li
42. kstation are the only terminals on a point to point local Ethernet LAN The absence of other devices on the LAN makes this configuration secure from the standpoint of network security System administration tasks can be performed from the workstation by doing a remote login rlogin to the AXM over the network and using SAM a system administration manager utility supplied with HP UX The Digital Audio Tape DAT drive on the workstation can be used for hard drive backups and for software installations and upgrades You can develop AXM applications from a window at the workstation while logged into the AXM Using its serial port and terminal emulation the workstation can be used as the console terminal of the AXM for initial network configuration and for maintenance as described for the previous configuration From a US or UXS on the LCN you can activate CL that uses the AMCLO6 extension set to initiate AXM applications The MP AXMST1 provides access to the HP CD ROM documentation Figure 1 4 Minimum Network Configuration with an MP AXMSTI Point to Point Ethernet LAN CDR CD Rom ho eee dl ee er Ess DAT E MP AXMST1 DAT Workstation AXM AM CD Rom LCN 51317 Continued on next page 5 96 Application Module User Guide 9 1 3 Application ModuleX System Configurations continued Expanded network configuration The preceding configurations are char
43. lity program xdaconfig modifies this file Table 3 4 Data Files File Purpose axmh All of the files that are required to load AXM 68020 processor based personality resides in opi TDC_Open axm share LCN pers axmk R500 Files to load AXM 68040 processor based personality resides in opt TDC_Open axm share LCN pers qlt1 pi Quality Logic Texts QLTs that are run on all boards when the node software is loaded resides in opt TDC_Open common share L CN qit boot_stub bo Boot file that is used for UXS and AXM resides in opt TDC_Open common share LCN Continued on next page 24 Application Module User Guide 5 96 3 3 Files Continued Executables All of these executables reside in the etc opt TDC_Open common bin directory Table 3 5 Executable Files File Purpose cds_hdr A utility for Honeywell use only cdsdaemon Handles the initiation from CL of X side applications and handles other functions for Honeywell software lendaemon This is a message handler daemon that performs the interface between the LCN node processor and the HP UX coprocessor there are three versions the 748 version is used by the AXM Xaccess A utility that allows the HP UX root user to change the restart state of the global X access switch refer to the topic The global X access switch in Section 2 display_appls AXM
44. mber of high priority channels to the minimum 0 and the number of Data Access servers to a minimum 0 effectively sets all the DA servers to service both high and low priority requests with the requests prioritized within a single queue Whenever the configuration file is changed the LCN personality must be reloaded or the entire AXM must be restarted in order for the changes to take effect Continued on next page 50 Application Module User Guide 5 96 6 2 The xdaconfig Configuration Tool continued Sample session The following is a sample session utilizing the Data Access configuration tool cd opt TDC_Open common bin xdaconfig KER THE CURRENT DATA ACCESS CONFIGURATION ARE RAR Number of DA servers for HIGH 4 Number of channels reserved for HIGH 10 Do you want to update the configuration file Y or N Y Pleas nter the number of DA servers for HIGH priority 0 to 4 or N 3 Pleas nter the number of channels reserved for HIGH priority 0 to 20 or N 8 EE THE UPDATED DATA ACCESS CONFIGURATION AR E Number of DA servers for HIGH 3 Number of channels reserved for HIGH 8 DA CONFIGURATION COMPLETE 5 96 Application Module User Guide 51 52 Application Module User Guide 5 96 Index RCVCNT n 27 32 RCVSTA n 27 30 XACCESS 18 XMITCNT n 27 35 XMITSTA n 27 34 A B about audit files 74 AM
45. n 71 Total number of host task initiation requests sent from the LCN side to the X side during the 15 second sample period n 72 100 Spare elements allocated to CDS transfer 5 96 Application Module User Guide 35 36 Application Module User Guide 5 96 Section 5 Hibernation 5 1 Overview ATTENTION What is hibernation What will be covered Advantages of hibernation This feature requires AXM and OpenDDA release R200 Hibernation is a cooperative functionality involving CL AM and OpenDDA Hibernation is available in OpenDDA R200 and later and requires LCN R431 or R500 or later Hibernation allows a CL initiated OpenDDA application to suspend execution after invocation and initialization and remain in memory While in hibernation CL can periodically activate the task to do some processing and then resume hibernation CL can also cause the application to gracefully terminate This section will provide an overview of hibernation functionality and associated tools The specifics are covered in the following documents e CL AM Reference Manual Appendix I AMCLO6 Extension e OpenDDA Reference Manual R200 Section 6 OpenDDA Execution Statements CL initiated X side applications that are initiated with the call AMCLO06 Execute Task_With_Wait execute until they terminate normally or exit with an error The CL program uses one AXM CL queue slot while the X side applic
46. n Number AX09 200 Writer Jim Kennedy COMMENTS RECOMMENDATIONS NAME DATE TITLE COMPANY ADDRESS CITY STATE ZIP If returning by mail please tape closed Postal regulations prohibit use of staples Communications concerning technical publications should be directed to Automation College Industrial Automation and Control Honeywell Inc 2820 West Kelton Lane Phoenix Arizona 85023 FIRST CLASS BUSINESS REPLY MAIL PERMIT NO 4332 PHOENIX ARIZONA POSTAGE WILL BE PAID BY Honeywell Industrial Automation and Control 2820 West Kelton Lane Phoenix Arizona 85023 Attention Manager Quality NO POSTAGE NECESSARY IF MAILED IN THE USA GutAlongline SS S U9UILIO EUOHIPPY Honeywell Industrial Automation and Control Helping You Control Your World Honeywell Inc 16404 North Black Canyon Highway Phoenix Arizona 85023 3033 Honeywell Industrial Automation and Control Helping You Control Your World Honeywell Inc 16404 North Black Canyon Highway Phoenix Arizona 85023 3033
47. ncludes CL AM enhancements security features coprocessor development resources and the standard OpenDDA Data Definition and Access the support software that allows a coprocessor application program to access LCN data In order to provide an environment that is both open and secure Honeywell has carefully chosen the areas to open By embracing the Fieldbus standard Honeywell has opened up the instrumentation level so as to be compatible with industry standard devices from a large number of vendors By adding a standard workstation with PIN interface as a coprocessor in the US and AM thereby creating the UXS and AXM Honeywell has provided users and third party developers with a means to develop powerful applications using standard languages that run on standard platforms and that can use live process data While the field instrumentation level and the information domain level are now open the LCN and its process controllers are retained so as to continue the security and reliability that are the hallmark of the TDC 3000X The view of the process and the path to the valve are not compromised in the OpenUSE environment Continued on next page Application Module User Guide 5 96 1 1 X Windows environment Introduction continued Computers on the PIN can use the X Windows Client Server environment This requires e A 5 10 Mbit Ethernet or Token Ring Local Area Network the PIN e TCP IP and X11 R5 o
48. necessary tapes From a network security standpoint this is the most secure configuration because there is no PIN connection From a US or UXS on the LCN you can activate CL that uses the AMCLO6 extension set to initiate AXM applications Note If the AXM is equipped with the optional DAT drive and a console device you can backup the disk and load software Figure 1 2 Standalone Coprocessor Configuration No PIN Connection Este CD Rom Co re GE DAT processor AXM AM LCN 51315 Continued on next page 5 96 Application Module User Guide 7 1 3 Application ModuleX System Configurations continued Minimum network configuration with uXs If applications will be developed locally or if access to a removable media drive is required for backups software installation or other system administration tasks then a minimum of one other network resident device is required This can be a UXS as shown in Figure 1 3 The characteristics are The AXM and UXS are the only terminals on a point to point local LAN The absence of other devices on the LAN makes this configuration secure from the standpoint of network security System administration tasks can be performed from the UXS by doing a remote login rlogin to the AXM over the network and using SAM a system administration manager utility supplied with HP UX The Digital Audio Tape DAT drive on the UXS can be used for hard driv
49. o consume all the available channels use them for long time period tasks and therefore lock out control applications from running within an allowable deterministic and repeatable time period To ensure that this will not happen AXM R200 will allow the user to configure the AXM to set aside a defined number of the data access channels for high priority actions only Then the only contention for these channels will be between high priority control applications such as OpenDDA programs running at Control and RCasEnb data priority levels Low priority tasks will then have to share the remaining channels with other noncontrol applications for example PCDE OpenDDA programs running at NoControl Data Priority levels TPH collectors and programs using platform file services Continued on next page 48 Application Module User Guide 5 96 6 1 Introduction continued Data access servers Summary The second resource to manage is the data access servers and associated AM side pool memory used during the execution of these requests Even when applications are prioritized as high or low for determination of access to data access channels we must then be concerned about priority with multiple queued requests against the data access servers To support this AXM R200 will allow the user to configure the AM side to set aside a defined number of data access servers to service high priority requests only In addition requests from
50. ode personality is running state of X ACCESS is not affected it will remain in its current state The XACCES external load module by its presence or absence allows or disallows writes of LCN data from non CL initiated X side applications This is accomplished as follows s If XACCES is loaded the READWRIT state of the global X access switch can be set by an Engineer from the keyboard or by a CL call When the READWRIT state is set non CL initiated applications are allowed to write LCN data es If XACCES is not loaded the READWRIT state cannot be set and therefore non CL initiated applications cannot write LCN data 5 96 Application Module User Guide 19 20 Application Module User Guide 5 96 Section 3 File System 3 1 Overview Discussion This section presents an overview of the base file structure of the AXM It is not intended to be a complete listing of all files and directories in the system Its purpose is to identify the directories and files that are of special interest in the AXM Figure 3 1 shows the base file system structure Figure 3 1 Base File System Structure root var opt etc users opt axm hwiaclicense opt DDA
51. r later software in both clients and servers e Motif window manager software in all clients The power and versatility of the X Windows environment allows a user on a PIN device of a given platform for example a PC configured as an X Server to open a window and run an application in another PIN device that is of a different platform for example an AXM whose coprocessor is running HP UX In X Windows convention the client is the device running the application and the device providing the screen keyboard and mouse services is the server 5 96 Application Module User Guide 3 1 2 Application ModuleX Architecture Chassis types Five Slot Module configuration Ten Slot Module The AXM is available in three chassis configurations e Five Slot Module uses the K4LCN node processor which has hardware floating point support R500 e Five Slot Module uses the K2LCN node processor and therefore does not support hardware floating point e Ten Slot Module uses the HMPU which has hardware floating point support The following table shows the configuration of the Five Slot Module versions of the AXM Table 1 1 AXM Five Slot Module Configuration Slot Front Rear 5 Optional Application Board Optional I O board 4 Hard Disk Drive Tray 3 occupies two slots HDDT I O 2 WSI2 WSI2 1 0 1 K2LCN K4LCN LCN I O The following table shows the configuration of the Ten Slot Modul
52. rnation The two utilities are e display_appls e kill_appls display_appls This is a command line tool used to obtain specific information about all CL initiated X side applications By default it will display a short version of output although an option 1 allows display of additional information Syntax display_appls 1 Applications are listed in two categories e SYNCHRONOUS APPLICATIONS WITH TERMINATION Lists tasks initiated by AMCLO6 Execute_Task_With_Wait e SYNCHRONOUS APPLICATIONS WITH HIBERNATION Lists tasks initiated with AMCL06 Initiate_Task For each task listed the following information is displayed e command line e initiating point name e initiating CL block name e application status hibernating or running e HP UX process id When the long version is requested by using the 1 option the following is also displayed e application id for hibernating applications only e time initiated e time activated for hibernating applications only e current HP UX priority For additional information about this utility see Appendix I of the CL AM Reference Manual Continued on next page 44 Application Module User Guide 5 96 5 4 X Side Support Tools continued kill_appls The X side tool kill_appls is a command line tool used to abort CL initiated X side applications It can only be executed by a user while a member of the axm group This tool can kill e one or all CL initiated X side applications associated wit
53. se the calls in the CL extension set AMCLO6 CL applications that do communicate with the X side using calls from the AMCLO6 set will get return statuses indicating errors The specific actions that take place when this occurs are handled in the CL application and therefore depend on how the application was coded Continued on next page 16 Application Module User Guide 5 96 2 3 LCN Security Continued Directory for CL initiated Each CL initiated application must have its executable file or a symbolic applications Using test data with OpenDDA link to its executable file in the directory users axm It cannot be started from CL if it is in any other directory This directory is owned by the user axm and the group associated with this directory is the group axm The permissions for this directory as shipped are Owner Group Other rwx TWX zor Application developers when they are added to the system as users will normally be assigned to the group axm Therefore when a developer has compiled and linked an application program the permissions will allow him to store the executable or create a symbolic link to the executable in users axm OpenDDA has an Install command option that will automatically create the symbolic link If you wish to tighten security even further you can modify the permissions on users axm accordingly For example you can make superuser the only user with write p
54. t Information Network PIN Software de Co Processor SE X Application UNIX LCN Server s W Communication Drive s al _ Interface LCN Node Gr AM CL Processor Points W I Custom Data CS Segments Local Control BER PER ET Network LCN gt gt 40000 Continued on next page 5 96 Application ModuleX User Guide 1 1 1 Introduction continued The control and information domains OpenUSE Open yet secure The collection of hardware and software that is most intimately involved in the control of the process is referred to as the control domain This includes the traditional LCN and its nodes and control programs the UCN and Data Hiway and their controllers and the field instrumentation infrastructure the sensors valves and other control elements The information domain includes the various processors connected to the Plant Information Network PIN PC Macintosh VAX and mainframe platforms as well as UXS and AXM coprocessors These computers use data generated by the control domain for production management functions such as unit cost and quality measurement inventory control and inventory cycle time analysis scheduling process optimization and other production management functions The software glue that connects the control and information domains is the Honeywell OpenUSE environment It i
55. the X side can make data access requests with an associated priority The result is that even within the scope of high low classes there is the capability to allow priorities within these classes For example OpenDDA NoControl applications have a higher priority within the low class of requests than for example an application such as PCDE Therefore if a large number of requests are being queued for data access the servers will take care of the OpenDDA applications first This allows for some level of jumping to the front of the line within the priority classes AXM R200 allows a user to customize an AXM s data access priority The user can ensure that a defined number of channels data access servers and corresponding pool memory have been set aside to service high priority requests The result is that after a node has demonstrated a defined operational characteristic for various load configurations the user can have a good sense of assurance that this will be repeatable behavior This will be the case even if for example a large number of PC desktop users should decide to call up Excel spreadsheets that use PCDE for access to LCN data and thereby demand a great deal of AXM resources 5 96 Application Module User Guide 49 6 2 The xdaconfig Configuration Tool Files Configuration tool Discussion ATTENTION The configuration of the priority of the Data Access paths through the X layer are define
56. users to change passwords periodically Each password can be set up with an aging factor the number of days that it remains valid Before the period ends the user must change to a new password HP UX provides the capability to audit computer use both on an individual and system wide basis You can configure the HP UX system to audit users events and system calls You can use the System Administration Utility SAM to set up the auditing functions Refer to the Hewlett Packard CD ROM manual HP UX System Security for additional information about audit files 14 Application Module User Guide 5 96 2 2 Physical and Procedural Security Physical security Procedural security Physical security involves protecting the system from damage or corruption by human and environmental factors Some examples of physical security measures are Fences intrusion alarms security guards Key locks card access systems Fire alarms sprinkler systems automatic fire suppression systems Secure off site storage for backups checkpoints etc Uninterruptible power supplies You should define your security objectives and requirements and develop a management approved security policy The policy should determine a set of practices and procedures that are distributed and followed meticulously Some examples of security practices and procedures are A procedure and schedule for backups and checkpoints Regulation and monitoring of log
57. ve data The PSDP performance parameters can be used directly in schematics by using the Add Value command and specifying the parameter as shown in the following example SPRSTS19 SRCVSTA 2 You can access the PSDP performance parameters from CL by transferring them to CDS parameters The following example shows how this can be done Continued on next page 28 Application Module User Guide 5 96 4 1 Overview continued Programming example CL V41 11 PERFSTAT Line Loc Text 0 8 01 94 08 54 42 5467 Page 1 1 2 THIS PROGRAM SHOWS HOW TO ACCESS PROCESSOR STATUS DATA POINT PARAMETERS 3 IN AM CL YOU MUST FIRST SET UP A PARAMETER LIST CONTAINING THE PARAMETERS 4 YOU WISH TO MONITOR NEXT YOU NEED A CDS TO CREATE A PARAMETER FOR THE 5 THE NODE NAME PRSTSXX USE THE CDS TO ALSO CREATE PARAMETERS FOR EACH 6 PERFORMANCE VALUE 7 8 PACKAGE 9 PARAM LIST P
Download Pdf Manuals
Related Search