       $                               Compaq   Software Product  Description   C ___________________________________________________________________   C PRODUCT NAME:  Compaq FMS for OpenVMS, Version 2.4     SPD 45.06.01 (                (Forms Management System)   DESCRIPTION   D Compaq FMS for OpenVMS (FMS) is a mature, character-cell based formsF management system for interactive applications running on OpenVMS sys-D tems that use video forms as the user interface. FMS provides appli-F cation programmers with a set of development tools to create and main-C tain forms-based user interfaces and a run-time system for display- D ing and managing the application's user interface at execution time.  C FMS has been superseded by Compaq DECforms for OpenVMS. DECforms is D the preferred forms product for character cell terminal applicationsI and should be used for all new application development requiring a forms-  based user interface.    Features  F Forms defined using FMS provide the programmer with the ability to use1 the following features of VT terminals by Compaq:   D o  Individual character attributes of reverse video, bold, blinking,    and underline  ? o  Line attributes of double width, double height, and scrolled   F o  Screen width attributes such as 80 or 132 column lines, and reverse    video  G o  Alternate character sets including the VT100 "special graphics char-     acter set" for line drawing  C                                                        January 2000        E FMS form data structures are used by the Form Driver (FDV) during run E time to display forms, and to access and validate data entered by the G terminal operator. Forms can be created and modified interactively with C the interactive editing facility (FMS/EDIT), or they can be defined F as a source form description with the Form Language and then convertedL to a form data structure using the Form Language Translator (FMS/TRANSLATE).E In general, forms larger than 54 lines in 80-column mode and 63 lines F in 132-column mode can only be created and modified with the Form Lan- guage Translator.   D Forms usually reside in form library files on disk and are retrievedE as needed by application programs at execution time. This arrangement E results in a high degree of independence between form data structures E and application programs. Forms can be modified without recompilation D or relinking of the application program. Forms can also be convertedD into an object module and linked with application programs to createC memory-resident forms, or forms can be dynamically loaded into mem-  ory by the application program.   E FMS applications use the Form Driver to control the display of forms, C their associated data fields, and the input and output of data into C fields. All data input from the terminal and output to the terminal  is passed as ASCII strings.   I Data for each field in a FMS form is validated by the Form Driver. Field- D validation characters are used to construct a "field validation pic-H ture." During program execution, characters input or output to the fieldC are compared to the picture to determine if they are valid. In most E instances, the field picture can contain several different field val- G idation characters and also field-marker characters. Field-marker char- I acters, used to improve the readability of the displayed form, are trans- " parent to the application program.  C Attributes from the following list can be assigned to each individ- 
 ual field:   o  Name of the Field   o  A default value  "                                  2        o  A help message   
 o  Autotab   o  Clear Character   o  Display Only    o  Fixed Decimal  
 o  Indexed   o  Left Justify    o  Right Justify   o  Must Fill  
 o  No Echo   o  Response Required   o  Supervisor Only   o  Uppercase  6 o  User action routines and associated data parameters   o  Zero Fill   o  Zero Suppress  C The attributes assigned to each field are checked for validity when C the form is created. Some combinations of attributes are not legal. E Each form has attributes that apply to the form as a whole. These at-  tributes include:    o  Name of the form   " o  Name of an associated help form  5 o  Screen background (black, white, or do not change)   ; o  Screen width (80 columns, 132 columns, or do not change)   0 o  Screen area to clear when displaying the form   o  Terminal character set   "                                  3       6 o  User action routines and associated data parameters  D o  Video attributes to be used if the field being worked on is to be    highlighted at run time  / o  The order in which fields are to be accessed   
 o  Named Data   ! Application Development Utilities    Interactive Form Editor   E The FMS/EDIT command invokes the interactive editing facility that is E used by the form developer to create and modify video forms. The cre- D ation of forms with the interactive editing facility is accomplishedD in phases. The layout phase is used to specify the visual appearanceE of the form, the background text, and what types of characters are to D be valid input to the fields. While laying out a form on the screen,G one has available a set of 48 function keys and key combinations. These D keys perform functions such as cursor movement, delete and undelete,F cut and paste, box drawing, video attribute assignment, centering, andD displaying Help. Additional phases are used to assign form and fieldH attributes, to enter Named Data, and to assign field access order. NamedG Data and all form and field attributes, including user action routines, C are specified by filling in questionnaires. Highlighting is used to D indicate which field is being referred to during the field attributeE and the field order assignment phases. Finally, the test phase allows F the developer to interact with a form just as the end user would with-  out exiting the editing session.   Form Language Translator  C The Form Language Translator provides an alternate means for defin- F ing forms. The Form Language is a free-form, keyword-oriented, declar-G ative language that provides the means to create and modify source form + descriptions with a text editor or program.       "                                  4       E The FMS/TRANSLATE command is used to convert the source form descrip- I tions (contained in a text file) to form data structures. The data struc- C tures created are equivalent to those created with the FMS interac- E tive editor. Existing form data structures can be converted back into D Form Language source code for modification or documentation by using! the FMS/DESCRIPTION/FULL command.   " Other Application Development Aids  D FMS provides additional facilities to aid in the application programG development process. The facilities are invoked with the following com-  mands:  7 o  FMS/LIBRARY - To create and maintain form libraries.   F o  FMS/DESCRIPTION - To obtain any of the following basic types of de-    scriptions of forms:   H    -  /BRIEF - Summary information about a form, its fields, Named Data,       and user action routines.   E    -  /FULL - Text files containing Form Language statements suitable 0       for input to the Form Language Translator.  E    -  /DECLARATIONS - To obtain data division code that can be edited C       by the user to create a COBOL Data Division or DATATRIEVE Do- H       main Definition reflecting the names, lengths, and order of fields       on the screen.  C    -  /DISPLAY_IMAGE - A printable image of a form in either termi- C       nal image format (with escape sequences) or line printer for- %       mat (without escape sequences).   C o  FMS/DIRECTORY - To obtain a directory list of forms in a library     or in form files.  C o  FMS/OBJECT - To generate an object module containing one or more C    form data structures that, when linked with the application pro- ?    gram, will allow access to the forms through virtual memory.   D o  FMS/VECTOR - To generate an object module containing a vector ta-C    ble of addresses that point to the user action routines that are '    linked with the application program.   "                                  5       C o  FMS/TEST - To invoke the form testing facility, which allows the D    application developer to display a form as an application program>    would, to type data into fields, and to display field Help.   Form Driver   D The Form Driver is the run-time component of FMS. It consists of ASTD reentrant, shareable subroutines that are called by application pro-C grams to control the interaction of the terminal, the user, and the C application program. The Form Driver provides facilities for manag- I ing multiple work areas (each of which contains a single form data struc- C ture). Multiple forms can be displayed on a single terminal screen.   C Form Driver subroutines provide for terminal input and output, dis- E play of forms, manipulation of the screen, basic input validation and D formatting, calling user action routines, and responding to the ter-E minal operator's requests for help. Input and output can be specified - one field at a time or on a whole form basis.   E The Form Driver has a number of features to facilitate fine tuning of E the application human interface. A timeout facility allows the appli- E cation program to continue execution after waiting a specified period E of time for the operator to enter the next character. Field video at- C tributes, cursor position, and Insert/Overstrike mode can be dynam- E ically altered by Form Driver calls in the application program. Field H highlighting, controlled by the Form Driver, causes the video attributesD of each field to be altered as the cursor enters the field and to beC restored to their original state when the operator exits the field.   D The Form Driver may be purchased separately for systems that require1 only run-time support for applications using FMS.   
 Named Data  F The Form Driver supports the creation of parameter-driven applicationsI by providing Named Data. Named Data are form constants that can be stored E as part of the form data structure and retrieved at execution time by F calls in the application program. Named Data allows information neededC by the application program (such as form linkage, operator messages F and other human language information, and data validation criteria for  "                                  6       C user subroutines) to be defined, stored, and modified independently  of the application program.    User Action Routines  E User action routines (UARs) are procedures written by the user in any F supported OpenVMS programming language. UARs are associated with formsD and fields during the creation of form data structures and are auto-C matically called by the Form Driver under the following conditions:   * o  When processing for a field is finished  C o  Before and after processing the terminal operator's Help request   4 o  When the terminal operator presses a function key  / o  When a screen refresh operation is requested   D The Form Driver transfers program control to the user action routineC under the circumstances defined. The user action routine has avail- E able to it (through Form Driver calls) a parameter string of 80 char- C acters (defined as part of the form) which can be used to give pro- 8 cessing information and the current Form Driver context.   Sample Application Program  C The Sample Application Program (SAMP) is a supported FMS demonstra- C tion program, included in the distribution kit, and is used to cer- D tify proper installation of FMS. The documentation for FMS gives ex-C amples from the Sample Application Program. The sample programs (in C each of the documented programming languages) and form descriptions G are included in the documentation and in the distribution kit. The Sam- D ple Application Program can be installed on the target system at the user's discretion.   Printing Forms  F Form images can be created and written to a file for subsequent print-I ing by either an application program using a Form Driver call, FDV$PRINT_ K SCREEN, or by a terminal operator using an FMS DCL command, FMS/DESCRIPTION ; /DISPLAY_IMAGE. The following screen images can be created:   "                                  7       E Line Printer Image - Line drawing graphic characters are converted to E standard printable ASCII characters and all other characters from al- # ternate character sets are ignored.   D Terminal Image - All escape sequences and control characters are in-E cluded to present an exact image of the screen as displayed. This im- D age can be output properly only to a printer that understands or canF interpret the control characters and escape sequences used by the cur- rent terminal.  
 Documentation   D The FMS documentation set is bundled with the development kit and isG also available separately. It is not part of the FMS run-time only kit.   " The documentation set consists of:   o  Introduction to FMS   o  Form Driver Reference Manual    o  Utilities Reference Manual    o  Language Interface Manual   o  Mini-Reference    o  Installation Guide    HARDWARE REQUIREMENTS    Processors Supported  G FMS is supported on all hardware configurations referenced in the Open- C VMS Operating System for Alpha and VAX, Version 7.2, Software Prod-  uct Description (SPD 25.01.xx).    Processors Not Supported  + The following processors are not supported:   
 o  MicroVAX I    o  VAXstation I   "                                  8        o  VAXstation 8000  
 o  VAX-11/725   
 o  VAX-11/782    Terminals Supported    Form Development  C Using the Interactive Form Editor, a VT100, VT200, VT300, VT420, or D VT500-series terminal is required for the creation of forms of up toF 23 lines. A supported OpenVMS workstation is required for the creationF of forms of up to 54 lines in 80-column mode or 63 lines in 132-columnC mode. Using the Form Language, forms of up to 254 lines can be cre-  ated on any terminal.    Application Execution   F FMS based application execution or usage of the form test facility us-H ing forms of up to 23 lines in length is fully supported on VT52, VT100,E VT200, VT300, VT420, and VT500-series terminals. Forms up to 54 lines G in 80-column mode and 63 lines in 132-column mode can only be displayed I on supported OpenVMS workstations. With the exception of VT420 and VT500- E series terminals that contain features to permit the display of forms F up to 72 lines, forms greater than 63 lines cannot be displayed on any terminal, but may be printed.   C ___________________________________________________________________ C Terminal__________________________Notes____________________________   # VT52                              1  VT100,VT100 w/AVO  VT101,VT102,VT103,VT125 # VT131                             2  VT180  VT220 # VT240                             3 # VT241                             4   "                                  9         C ___________________________________________________________________   # VT320                             5 % VT330                             5,6 ' VT340                             4,5,6 # VT420                             7 # VT510                             7 # VT520                             7 C VT525_____________________________4,7______________________________   E 1. Supported for application execution only. The Interactive Form Ed- (    itor cannot be used on this terminal.  6 2. The VT131 terminal is supported in VT102 mode only.  C 3. The usage of blinking, double-wide, and/or double-sized lines in 9    forms can result in substantially reduced performance.   # 4. Usage of color is not supported.   7 5. Usage of the status line, line 25, is not supported.   8 6. Usage of the locator device (mouse) is not supported.  D 7. Forms of up to 72 lines may be defined for VT420 and VT500 seriesG    terminals. These terminals can display 24, 36, or 48 lines on a sin- D    gle screen. Forms larger than the screen size can be panned underC    local hardware control. FMS does not support access to the F1-F5 C    function keys or to the ALTERNATE key to activate another termi- D    nal session. The COMPOSE key is supported when configured for LO-    CAL COMPOSE.    Terminal Emulators  G Terminal emulators on workstations and personal computers are supported_C only to the extent that the emulator conforms to the supported ter- ! minal environment being emulated.D  0 Disk Space Requirements (Block Cluster Size = 1)  C FMS can be installed with or without the Sample Application Program- (SAMP).d  "                                 10    l  E These counts refer to the disk space required on the system disk. ThenD sizes are approximate; actual sizes may vary depending on the user's8 system environment, configuration, and software options.  C ___________________________________________________________________aC Kit________________VAX__________Alpha______________________________y  , Development        3,000        4,000 blocks Installation       blocks (    with SAMP       1,536 Kb     2,000 Kb  , Development        1,850        2,500 blocks Installation       blockse(    without SAMP    948 Kb       1,250 Kb  , Development        2,650        3,500 blocks Permanent          blocksn(    with SAMP       1,357 Kb     1,800 Kb  , Development        1,300        1,800 blocks Permanent          blocksd&    without SAMP    666 Kb       900 Kb  * Run-Time In-       350          500 blocks stallation         blocks &                    180 Kb       250 Kb  * Run-Time Perma-    300          400 blocks nent               blockshC ___________________154_Kb_______200_Kb_____________________________    SOFTWARE REQUIREMENTS                 "                                 11 a  u    C ____________________OpenVMS________________________________________cC Software____________VAX__________OpenVMS_Alpha_____________________b  6 Operating System    V5.5-2,      V6.2, V7.1, or higher                     V6.2,T                     V7.1, orC ____________________higher_________________________________________    OpenVMS Tailoring Classesg  E For VMS V5.x systems, the following VMS classes are required for fullt& functionality of this layered product:   o  VMS Required Save Set   o  Programming Support   o  Utilities   OPTIONAL SOFTWAREt  * Compaq DATATRIEVE for OpenVMS, V6.1 - V7.2   SOFTWARE LICENSING  E This software is furnished only under a license. For more informationgD about Compaq's licensing terms and policies, contact your local Com- paq office.   ! LICENSE MANAGEMENT FACILITY (LMF)d  C This layered product supports the OpenVMS License Management Facil-F ity.  C License units for both the Development System and the Run-Time Sys- 7 tem are allocated on a capacity basis by hardware tier.e  E For more information on the License Management Facility, refer to thepD OpenVMS Operating System Software Product Description (SPD 25.01.xx)G or the License Management Facility manual of the OpenVMS Operating Sys-  tem documentation set.  "                                 12 p  e   CLUSTER ENVIRONMENT   C This layered product is fully supported when installed on any validdE and licensed VMScluster configuration without restrictions. The Hard--F ware Requirements section of this Software Product Description details. any special hardware required by this product.  E VMScluster configurations are fully described in the VMScluster Soft-lE ware Product Description (SPD 29.78.xx) and include CI, Ethernet, andt" Mixed Interconnect configurations.   YEAR 2000 READYe  E This product is Year 2000 Ready and is capable of accurately process-rF ing, providing, and/or receiving date data from, into, and between theF twentieth and the twenty-first centuries, and the years 1999 and 2000,F including leap year calculations, when used in accordance with the as-H sociated product documentation and provided that all hardware, firmware,C and software used in combination with the product properly exchange $ accurate date data with the product.   DISTRIBUTION MEDIA   This product is distributed on:n  6 o  CD-ROM (as an individual product for OpenVMS Alpha)  = o  CD-ROM (as part of the OpenVMS Software Product Libraries)a  C The software documentation is also available as part of the OpenVMSn) Online Documentation Libraries on CD-ROM.p   ORDERING INFORMATION  C ___________________________________________________________________fC OpenVMS_VAX__________________Part_Number___________________________   ( Development License,         QL-VD7A*-AA
 Unlimited User  "                                 13 a  h    C ___________________________________________________________________   ( Development Update Li-       QL-VD7A*-RA cense ( Development Software         QT-VD7A*-** Product Services( Run-Time License, Unlim-     QL-VD8A*-AA ited Use( Run-Time Update License      QL-VD8A*-RA( Run-Time Software Product    QT-VD8A*-** Services  ( Media and Documentation      QA-5G88A-H8 (OpenVMS VAX Software  Product Library)  C Hardcopy_Documentation_______QA-VD7AA-GZ___________________________l  C ___________________________________________________________________hC OpenVMS_Alpha________________Part_Number___________________________   ( Development License,         QL-MVSA*-AA
 Unlimited Use,( Development Update Li-       QL-MVSA*-RA censes( Development Media and        QA-MVSAA-H8
 Documentationa( Development Software         QT-MVSA*-** Product Services( Run-Time License, Unlim-     QL-MVTA*-AA ited Use( Run-Time Update License      QL-MVTA*-RA( Run-Time Media               QA-MVTAA-H8( Run-Time Software Product    QT-MVTA*-** Services        "                                 14 m  d    C ___________________________________________________________________.  ( Media and Documentation      QA-03XAA-H8 (OpenVMS Alpha Software  Product Library)  C Hardcopy_Documentation_______QA-MVSAA-GZ___________________________e  F *  Denotes variant fields. For additional information on available li-D    censes, services, and media, refer to the appropriate price book.   GROWTH CONSIDERATIONSr  E The minimum hardware and software requirements for any future versionoC of this product may be different from the requirements for the cur-t
 rent version.r   SOFTWARE PRODUCT SERVICES   E The Mature Product Support with Sustaining Engineering Service is of-rC fered for this product and includes telephone support, tested soft- I ware patches for any new problems, and problem escalation to engineering- C level resources if appropriate. This support offering is equivalentrE to current version support. Compaq will not be adding new features oraF functionality to this product and no new releases are planned. Accord-E ingly, License Subscription and Software Update Distribution ServiceskH are no longer available. Please contact your local Compaq Services SalesE Specialist for more information about the Mature Product Support with  Sustaining Engineering Service.a  D A variety of service options are available from Compaq. For more in-, formation, contact your local Compaq office.   SOFTWARE WARRANTYA  F This software is provided by Compaq with a 90-day conformance warrantyF in accordance with the Compaq warranty terms applicable to the license	 purchase.I  "                                 15 s  e  F The above information is valid at time of release. Please contact your8 local Compaq office for the most up-to-date information.  "  2000 Compaq Computer Corporation  C Compaq, the Compaq logo, and the DIGITAL logo are registered in thee! U.S. Patent and Trademark Office.   D All other product names mentioned herein may be trademarks or regis-/ tered trademarks of their respective companies.   G Confidential computer software. Valid license from Compaq Computer Cor-hH poration or authorized sublicensor required for possession, use or copy-E ing. Consistent with FAR 12.211 and 12.212, Commercial Computer Soft- E ware, Computer Software Documentation, and Technical Data for Commer- C cial Items are licensed to the U.S. Government under vendor's stan-  dard commercial license.  D Compaq Computer Corporation shall not be liable for technical or ed-E itorial errors or omissions contained herein. The information in thiso- document is subject to change without notice.   G CI, DATATRIEVE, DECforms, FMS, MicroVAX, OpenVMS, VAX, VAXstation, VMS,tC VMScluster, VT, VT52, VT100, VT220, VT300, VT320, VT330, VT340, and 4 VT420 are trademarks of Compaq Computer Corporation.                              "                                 16