 |
|
 |
XENTIS Documentation -- Release Notes
XENTIS 3.3
XENTIS V3.3 Release Notes This document contains information about using XENTIS V3.3 and highlights features that are available in V3.3 that were not available in previous versions. A. INSTALLATION AND GENERAL INFORMATION 1. XENTIS V3.3 uses the VMSINSTAL utility to install XENTIS. XENTIS can be installed on any device or in any directory. 2. Release notes and new features are included on the tape. Installation instructions are sent separately. 3. The minimum VMS version level for XENTIS V3.3 is VMS V4.5. 4. XENTIS V3.3 works with VMS V5.0. If VMS 5.0 is installed after XENTIS V3.3 and you wish to use the user defined date formats, then you must re-install XENTIS V3.3. 5. XENTIS V3.3 has not yet been tested with CDD/Plus V4.0. If you plan on using XENTIS with the CDD, we are asking that you do not install CDD/Plus V4.0 until we have tested it. We will support CDD/Plus V4.0 in a future release of XENTIS. B. USING OLDER VERSION XENTIS FILES IN XENTIS V3.3 1. All compiled command files must be recreated using XENTIS V3.3. XENTIS V3.3 compiled command files are smaller than in previous versions. 2. All pointer files must be recreated using XENTIS V3.3. 3. All standard (uncompiled) full or partial and substitution command files created with FIS V4.X or XENTIS V2.X must be converted in order to run with XENTIS V3.X. Command file conversion is a one-time operation for each existing command file; XENTIS V3.X command files or files that have already been converted to XENTIS V3.X format need NOT be converted. C. DOCUMENTATION 1. The entire XENTIS Reference Manual is stored in one three-ring binder with dividers separating the sections. The Table of Contents and the Index have been separated to accommodate those who wish to remove sections of the manual and distribute only a portion to their end users. 2. The Index has been completely recreated using a word processing index utility. 3. The following sections have been completely rewritten, reformatted and updated: /Report: /Report Introduction, Data Dictionaries, All Option 1 sections, Option10, Option 11, Appendix E. /Dictionary: All sections. /Edit: All sections. 4. The following are new sections or sections that contain many new items: /Report: /Report Introduction (parts), Appendix A (new parameters), Appendix E (parts),Appendix G and Appendix H. 5. The following are sections that have been reformatted: /Report: /Report modules, Appendices, Some /Report options. D. New Features I. XENTIS/Dictionary 1. File type M is a feature added to provide better support of MCBA's DIBOL based application software. Even though MCBS DIBOL application files are RMS relative files, XENTIS treats them as if they are a single key RMS indexed file (SAM). 2. More data types are allowed to be key fields. In previous versions of XENTIS, only data types that always worked as a key were allowed. Now, if a data type works as a key under restricted circumstances, it is allowed as a key in XENTIS. This affects the following data types: NZ, NDA, TDA, RDA, DIO, to DI5, CVW, Q, QU, and DA. 3. A RENAME function is added to the "Edit a dictionary" menu. Use RENAME to change a field name, a file name, a table name, a view name, or a password. In pevious versions of XENTIS, a user had to delete the old name and then add the new name. 4. When changing a field description, the field description can be accessed by field number or field name. In previous versions of XENTIS, field descriptions could be accessed only by field name. 5. Data type NDA is supported. This data type is used only by MAXCIM application software. 6. A default value of /PREV is supported. /PREV is used by XENTIS/Edit to default the field's data value in the current record to the value in the last record added. This applies only to add mode. 7. A default value may include a qualifier of n1/INCR=n2, where n1 indicated an initial default for the field and n2 indicated an increment amount. The qualifier is used by XENTIS/Edit to default the field's data value in the current record to a value based on the same field in the last record added. This applies only to add mode. 8. Views may include selection logic. Up to twelve selection expressions may be entered in a view. Use view selection logic to provide record security. Syntax checking is not performed at the time the selection expressions are entered. 9. The FIELD TO UPDATE on ADD or CHANGE can be any date data type. In previous versions of XENTIS, these could only be defined as VMS date data types (DA) fields. 10. The DISCARD-AFTER-RET setup parameter is used by XENTIS/Dictionary. 11. The audit trail process is created with the UIC of the user creating the audit trail. In previous versions of XENTIS, the process was created with a UIC of [1,77]. II. XENTIS/Edit 1. MCBA DIBOL based data files simulated as single key indexed files (file type 'm') are supported for change, delete, and list modes. Add mode is not supported. Key fields cannot be changed. 2. Data type NDA is supported. The NDA data type is used only by MAXCIM application software. 3. A default value of /PREV is supported in add mode. See XENTIS/Dictionary new feature #6. 4. The /INCR qualifier is supported on a default in add mode. See XENTIS/Dictionary new feature #7. 5. The FIELD TO UPDATE on ADD or CHANGE can be any date data type. See XENTIS/Dictionary new feature #9. 6. When retrieving a record to list, change, or delete, XENTIS/Edit requires that the record read match the key entered. In previous versions of XENTIS, if a record did not exist for a key entered by the user, XENTIS/Edit displayed the next record in the file. Thus, the wrong record could be easily changed or deleted inadvertently. 7. Several Yes/No responses in XENTIS/Edit are no longer case sensitive. 8. The DISCARD-AFTER-RET setup parameter is used by XENTIS/Edit. III. XENTIS/File 1. A valid response to the "Output to new seq. file" is 'H'. If H is entered, the first record in the output sequential file will be a header record containing a record count in the first four bytes (stored as longword). Convert the file to an RMS relative file before using it as an input file in /Report. This feature provides additional support to MAXCIM application software. IV. XENTIS/Model 1. A default print mask appears in the dialogue for date and calculation result fields. V. XENTIS/Report 1. MCBS DIBOL application files are supported as single key indexed files. See XENTIS/Dictionary new feature #1. 2. FMS files (application software from MANUS, GSI Transcomm, NCA and other vendors) are supported. 3. The break section of the dialogue supports the RECALC and the NORECALC reporting commands. Default print positions for break descriptions are calculated only in RECALC mode. 4. The number of characters allowed in response to the primary file prompt is 255. In previous versions of XENTIS, the limit was 64 characters. 5. The /SELECT=n qualifier used at the Execute prompt no longer overrides the value given at the "Number of records to select" prompt when writing responses to a command file. 6. Performance for TDA date data types has been enhanced. 7. A segment of a text calculation result can be specified with the /Start-End syntax. In previous versions of XENTIS, the SEG calculation function had to be used. 8. The name of the batch .COM file created when 'B' or 'O' is entered at the Execute prompt is changed to XENTIS_nnnn or XENTIS_xxxx_nnnn (where nnnn is a number based on time of day and xxxx is the name of the user's command file if one was used). 9. Time can be printed from a VMS Date field by extending the print mask. 10. User defined date/time formats supported by VMS V5.0 are supported by XENTIS/Report. See Installation and General Information note #4. The logical LIB$DT_FORMAT controls the date/time format. 11. The location of all temporary files, including sort files, is the disk and directory indicated by the logical SYS$SCRATCH. In previous versions of XENTIS, temporary files were created in the user's current default directory. SYS$SCRATCH is assigned by VMS when a user logs in. 12. For efficiency reasons, output report files are now extended 16 blocks at a time. This can result in an output file whose allocation is greater than its usage. The difference should never be more than 15 blocks. 13. ' T' is an allowed value for the FF-OR-COUNT setup parameter. When the value of FF-OR-COUNT is 'T', XENTIS/Report suppresses the form feed if title lines are suppressed. If title lines are not suppressed, a form feed is used. 14. The number of characters allowed for the setup parameters BATCH-QUE -NOW and NIGHT-BATCH-QUE is 64. This allows the user to add additional DCL qualifiers to the queue name. For example, if batch jobs are queued to SYS$BATCH and the user wants to be notified when the batch job completes, the value of the queue name can be SYS$BATCH/NOTIFY. 15. In the Info window in display mode, fields occurring multiple times subscripted fields) are displayed with either ( ) or (,). 16. When using the CDD as the data dictionary and entering domain names, the domain names are displayed as the default when the user backs up to a previous file prompt. In previous versions of XENTIS, XENTIS/ Report converted the domain name to a record path name and an actual data file name. 17. Compiled command files can be created with an implicit '/GO' qualifier. To do so, respond with a 'G' at the "Compile this command file" prompt. 18. The "First record" and "Last record" responses at the First/Last record/key to read prompts are no longer case sensitive. 19. The INSERT and DELETE reporting commands used at the field prompts can be entered at the command line (after the DO of PF3 keys have been pressed). 20. Form names are validated if the user is queuing a report to the system printer. 21. The components of the default output file are used with what a user enters. For example, if the default output file is DISK1:[ABC]XENTIS.RPT and the user enters REPORT1, the output file is DISK1:[ABC]REPORT1.RPT. In previous version of XENTIS, the output file was SYS$DISK:REPORT1.LIS. 22. If the user saves a XENTIS command file (.XCF), the default .XCF name is derived from the output file name. 23. When report output is to the user's terminal, the commands that can be entered at the "Press return to continue" prompt can be entered at the "Press return to exit" prompt. 24. The data types displayed for the LST reporting command match the data types used by XENTIS/Dictionary. 25. XENTIS/Report, along with the /Model, /Word, /File, and /Update options, support the selection logic associated with a view. View selection logic is hidden from the user and cannot be changed or modified in the dialogue. View selection logic can only be modified using the XENTIS/Dictionary utilities. 26. XENTIS/Report is callable by other application software without generating a subprocess. The calling program calls XRPTOP and passes it a default data dictionary name, a default password, and a command file name (which can be null). 27. The command file conversion utility issues a warning message when command file substitution blank lines are encountered. Either of these circumstances may result in a converted command file that will not work correctly. 28. Many performance enhancements have been made in the print phase. Substantial reduction in CPU usage will realized when numeric fields are printed. Improvements in CPU usage will also be noticed when dates are printed. TDA (text) dates will use less CPU everywhere they are used in a report. 29. When a print mask for a numeric field is too small for a data value being printed, XENTIS/Report will print a series of asterisks. In previous versions of XENTIS, the number was printed in scientific notation, but only that portion that would fit in the space allocated for the print mask. VI. XENTIS/Word 1. A default print mask appears in the dialogue for date and calculation result fields. VII. Other General Enhancements 1. The user defined data type packing and unpacking routines used to define foreign data types are stored in XUUSER_PACK. In previous versions of XENTIS, user defined data types were defined in two different routines, XRPUSR_PACK and XUUSER_PACK. 2. The F14 key on an LK201 (VT220) keyboard toggles insert and overstrike mode. This conforms with DCL. 3. The F8 key on an LK201 (VT220) keyboard backs up one prompt in a dialogue. 4. CTRL/B recalls the precious response. This conforms with DCL. XENTIS retains a buffer of 10 responses in DISPLAY mode. 5. The names of the XENTIS data files are changed. XRPBAT.DAT is now XENTISBAT.DAT, XRPSET.DAT is now XENTISSET.DAT, XRPSET.XEN is now XETISSET.XEN, XRPHLP.IDX is now XENTISHLP.IDX. 6. XENTIS.COM is rewritten to include XRP_FRONT.COM. Because VMS V4.5 is the minimum VMS version required for XENTIS V3.3, XENTIS.COM has been updated to take advantage of DCL enhancements made since VMS V4.0. 7. The menu control file is changed; the EXIT commands have been replaced with GOTO MENU_EXIT commands. The QUIT commands remain the same but instead of generating a DCL EXIT command they now result in a DCL GOTO MENU_EXIT command. This allows XENTIS.COM to gain control over how the menu is exited. The MENU_EXIT label must not be removed from XENTIS.COM. 8. Search list logicals are fully supported. VIII. New and Changed Setup Parameters 1. ALLOW-ACTUAL. This Yes/No parameter controls whether or not a user can enter the actual/generic filename syntax at a file prompt. 2. ALLOW-SPAWN. This Yes/No parameter controls whether or not a user can enter the SPAWN of ATTACH reporting command in XENTIS/Report. 3. ALLOW-DIR. This Yes/No parameter controls whether or not a user can enter the DIR reporting command in XENTIS/Report. 4. ALLOW-FILE. This Yes/No parameter controls whether or not a user can access the FILE function. 5. ALLOW-REUPDATE. This Yes/No parameter controls whether or not a user can access the REUPDATE function. 6. DISPLAY-DCL. This Yes/No parameter controls whether or not DCL messages display on a user's terminal when a batch job is submitted or a print job is queued. 7. DFLT-CMD-LOC. This parameter controls the default location, disk, and directory of XENTIS command files and XENTIS/Report pointer files. 8. IGNORE-CHARS. This parameter controls the number of characters ignored when XENTIS compares field names in the KEY section of a dialogue to determine a default. This is useful for application software packages that prefix field names with a file designator. 9. ENCRYPT-PASSWORD. This Yes/No parameter controls whether or not the password is hidden when XENTIS/Report generates a .COM or .XCF. 10. The FF-OR-COUNT parameter allows a value of 'T'. See XENTIS/Report new feature #13. 11. The NOW-BATCH-QUE parameters can hold a 64 character value. See XENTIS/Report new feature #14. 12. When the MENU-DONE parameter is set to 'N', a user returns to the XENTIS dialogue after the prompt "Press return to exit program" is encountered. 13. Several obsolete parameters have been removed.
GrayMatter Home | XENTIS
Home | Download Software |
XENTIS Technical Support |
Contacting GrayMatter | XENTIS
News
| Comments? Send us your feedback. |
|
|
©
Copyright 2020 GrayMatter Software Corp. |
