XENTIS Documentation -- Release Notes XENTIS 4.6b XENTIS V4.6A Release Notes This document contains information about using XENTIS V4.6A and highlights features that are available in V4.6A that were not available in versions prior to V4.6. This initial section describes the difference between V4.6A and V4.6. The information beyond this section is the standard V4.6 release notes. A. GENERAL INFORMATION. 1. Version 4.6A is a bug fix release. It contains no functional enhancements when compared with V4.6. All compiled command files, (XCC), command files, (XCF), and pointer files created with V4.6, are compatible with V4.6A. 2. The problems fixed are: a. Under some very complex and rare circumstances, some calculations would not be performed at the time they needed to be performed. The circumstance where this happened was when calculation A depended upon calculation B, which was a temporary calculation. Later on, another calculation C was also dependent upon calculation B, but between calculation A and C, calculation B was set to a new value. In addition, the data file that A was dependent upon was different from C, and A's file was lower than C's file. This problem was introduced in version 4.4. b. When using a XENTIS Command File (XCF) with the /SHOW qualifer, if an error was encountered while data files were being opened, then the /SHOW qualifier was turned off until the program was exited or restarted. This problem was introduced in version 4.1. c. When using a Maxcim version 4 or later data dictionary with the ALLOW-ACTUAL setup parameter set to Y and an error was encountered opening a data file, XENTIS would produce an incomplete error message. This problem was introduced in version 4.4 d. Under some circumstances when the license key was entered while installing XENTIS, XENTIS would not see the license key during startup. This problem was introduced in version 4.3. XENTIS V4.6 Release Notes This document contains information about using XENTIS V4.6 and highlights features that are available in V4.6 that were not available in versions prior to V4.6. A. INSTALLATION AND GENERAL INFORMATION. 1. If you have a previous version of XENTIS already installed and you never installed an interim version, we recommend that you copy the release notes of these previous versions from saveset F on your release tape and review them. The following DCL command should retrieve these release notes and place them in your current directory: BACKUP/LOG tape_dev:XENTIS046.F/SELECT=[*...]*.REL*/SAVE_SET [] where 'tape_dev' is your tape drive. 2. The installation procedure for V4.6 is similar to the procedure used in V4.2 to 4.4, however V4.2 installation is quite different from V4.1. Prior to V4.2, all XENTIS images would be linked, with a LINK command, while the installation procedure was executing. Starting with V4.2, XENTIS images are copied onto your system without going through a LINK step. This results in a faster installation. This is accomplished by supplying several shareable images that act as stub routines for databases and other optional software that XENTIS supports but is not present on your system. In addition, the installation procedure no longer prompts the installer for an 'INSTALL' directory. The 'Install' or 'Object' files are no longer loaded onto your system. 3. If you are using XENTIS with Oracle7 then you must relink XENTIS on your system, and you must receive a special tape containing the XENTIS object libraries. The same holds true if you wish to use CDD, now called Oracle CDD, with XENTIS on Alpha systems. Using CDD with Vax systems does not require a relink. 4. Starting with V4.2 XENTIS logicals are created in the SYSTEM table in EXECUTIVE mode. This is done to support the new policy of not linking on the target system. These logicals are now defined during system startup. In version 4.1 and prior, the XENTIS$COMFILES logical was defined in the SYSTEM table in SUPERVISOR mode, while the XENTIS$PROGRAM, XENTIS$DEMO, and XENTIS$REPORT$DATA logicals were defined in the PROCESS table. To help avoid problems with user written DCL command files referring to XENTISLOGICALS.COM, this file's name has been changed to XENTIS_LOGICALS.COM, and XENTISLOGICALS.COM will still exist but contain only comments. 5. In response to customer demand, multiple versions of XENTIS may be installed and active at the same time. Please see section below for more information. 6. Beginning with V4.2, the XENTIS startup procedure defines a number of additional logicals. These logicals define which optional parts of XENTIS are available on your system, and which ones will have to use stub routines. The definition of these logicals are found in the XENTIS_SHARE_LOGICALS.COM file. 7. An additional system DCL command file is supplied for the purposes of shutting down XENTIS. This command file is called XENTIS_SHUTDOWN.COM and can be found in the XENTIS46$COMFILES: directory. This command file removes the system logicals that were created with the XENTIS46_START.COM file. It will also remove the XENTIS images if they were installed with the INSTALL command. (This does not delete any files from disk.) It is recommended that the XENTIS_SHUTDOWN.COM procedure be called from the system shutdown procedure, SYS$MANAGER:SYSHUTDWN.COM. 8. The user pack routine, used for user written data types, is implemented as a shareable image beginning with V4.2. This allows you to write and test your routine without having to relink XENTIS every time. Linking instructions are found in the sample source code, XUUSER_PACK.BAS. In addition, the number of parameters for this routine has changed. Please review the sample source code for further information. This information represents no change from V4.2, however the name of the shareable image is now XENTIS46_USER_PACK.EXE. 9. On VAX systems XENTIS V4.6 requires OpenVMS V5.0 at a minimum. Installation and operations has been tested on a OpenVMS V5.2 system, but it has not been tested on a OpenVMS V5.0 or V5.1 system. As result we recommend that users be running at least OpenVMS V5.2. On Alpha systems XENTIS V4.6 requires OpenVMS V6.2 or later. It is also important to install all the BASIC RTL patches available from Digital. Without these patches, XENTIS will abort under certain circumstances. The patches are available from Digital World Wide Web site: http://www.openvms.digital.com. 10. If an additional cpu is licensed, and that system has a different database configuration, it is not necessary to relink XENTIS. The XENTIS startup procedure effective with V4.2, which must be run on every node licensed for XENTIS, will detect the different database configuration and define the XENTIS logicals appropriate for each licensed CPU. 11. The circumstances where XENTIS needs to be relinked are now quite rare. Therefore, object libraries are no longer included on the distribution tape. 12. Beginning with V4.2, CALLABLE XENTIS is a feature that is available only upon request from your vendor. It is no longer available in the standard release. CALLABLE XENTIS provides the ability for a 3GL program to call XENTIS (except /Dictionary and /Edit) in the context of the same process or image. XENTIS can still be executed in the context of a subprocess. Using XENTIS in a subprocess is not considered CALLABLE XENTIS. 13. When the XENTIS46$SUPPORT logical is set to a value of Y, then whenever XENTIS/Report ( or /File, /Word, /Model, /Creport, /Update) writes a XENTIS Command File, .XCF, it will write into the file considerable information regarding the report, the data files, the setup file, and its operating environment. This information can be very valuable for the customer support staff in diagnosing problems with a particular report. When sending an XCF file to the customer support department, please set this logical to a value of Y before creating the XCF file. This feature became effective with version 4.1. 14. If you are upgrading from V4.2 or prior, please note that the names of the user modifiable shareable images have changed. Their previous and current names are as follows: XENTIS_USER_PACK.EXE XENTIS46_USER_PACK.EXE XENTIS_USER_FUNCTION.EXE XENTIS46_USER_FUNCTION.EXE XENTIS_XRP3GL.EXE XENTIS46_XRP3GL.EXE The application program interface (API) to these routines have not changed from V4.2. 15. The Alpha AXP version of XENTIS has not been tested with CDD. It should work with a relink of XENTIS. The Alpha AXP version does not work with Ingres or Sybase. Contact your vendor regarding more information on these databases. The Rdb interface has been tested and is supported. The Oracle interface works with a relink of XENTIS, and in some cases a redefining of logicals. B. INSTALLING AND USING TWO DIFFERENT VERSIONS AT THE SAME TIME Beginning with version 4.3 XENTIS allows two or more different versions to be installed and active at the same time. This is accomplished by including the version number, in this case 46, with the logicals used by XENTIS and including the version number in many executable files. The information in this section describes how this is accomplished and what the customer needs to do to insure smooth operation of two or more versions at the same time. 1. All XENTIS logicals that previously began with XENTIS, now begin with XENTISnn, where 'nn' is the version number. Please note that symbols such as XENTIS$DICT and XENTIS$PASSWD have not changed. These symbols are unique to your process and do not need to be changed. 2. All XENTIS executable files that may get installed with the INSTALL utility now have the version number appended to the filename. This is because the INSTALL utility does not allow two or more files with the same name to be installed at the same time. Customers that have a limited user count license, or those that have a Progress database interface license must either install XENTIS executables with the SYSLCK privilege or must give each user the SYSLCK privilege. (The XENTIS startup procedure automatically examines the XENTIS license for these two conditions and installs the executables if appropriate.) Please note that due to a bug in Rdb, the XENTIS executables should not be installed if the Rdb interface is to be used. 3. None of the control files or data files that XENTIS uses have had their names modified for this purpose. The lone exception to this rule is the startup file that is executed during system startup. Its name is now XENTISnn_START.COM, found in the SYS$MANAGER directory, where 'nn' is the version number. 4. XENTIS version 4.6 may be installed and started, while a previous version is active and running. It may not be installed while another installation of V4.6 is active and started. The V4.6 installation procedure detects this condition and will halt its processing. 5. During system startup, the various versions of XENTIS should be started in order with the oldest version first and the newest version last. When shutting down XENTIS, it is best if the reverse order is followed; the latest version first. 6. Existing batch command files present a unique problem. Many or most batch command files created prior to version 4.3 contain a line in them similar to "RUN XENTIS$PROGRAM:XRP". Under the old scheme of filenames and logicals, this would always execute the current version of XENTIS. Under the new scheme of filename and logicals, this would execute the version of XENTIS that was previously installed. If it is desired for pre V4.3 batch command files to use version 4.6, then perform the following steps. a. Copy XRP46.EXE to XRP.EXE in the same directory. b. Define a logical as: DEFINE XENTIS$PROGRAM XENTIS46$PROGRAM Beginning with batch command files created under version 4.3 or later, you can control which version of XENTIS is used. This is done with the XEN_VER DCL symbol. To use version 4.3, set XEN_VER to "43"; to use version 4.6, set XEN_VER to "46"; etc. This symbol can be set in a user login file or the system login file, SYS$MANAGER:SYLOGIN.COM. If this symbol is not set, the current version will be used. 7. To remove an older version of XENTIS from your system, execute the XENTIS_SHUTDOWN.COM procedure for all versions in the order of most recent version first. (XENTIS_SHUTDOWN.COM was introduced in version 4.2.) Next, delete all the files from the older version. Next deassign the PKMSSHR logical. Next, execute the XENTIS startup files, found in SYS$MANAGER, in the order of most recent version last. C. NEW FEATURES 1. /Report and /Report modules (/File, /Word, /Model, /Update). a. A new setup file parameter, HTML-RELATIVE-PATH, controls whether or not relative paths are used when XENTIS writes filenames into the HTML catalogue file. This parameter has valid values of Y or N. A Y instructs XENTIS to write relaive paths while an N value instructs XENTIS to write absolute paths. Relative paths are applicable only when the report HTML file is in the same directory as the catalog file or in a sub-directory of the catalog file. b. A new setup file parameter, SORT-ORDER, controls the sort order of the report. Previously only ASCII sorts were allowed. Now EBCDIC and Multinational ASCII sorts are allowed. The allowable values for this parameer are A for ASCII, M for Multinational ASCII, and E for EBCDIC. The shipped value of this parameter is A. The ECBDIC sort should only be used when character data is being sorted. Please see the OpenVMS documentation on the SORT command/utility for more information. c. XENTIS will now use pointer files that were created with an older version, provided they are no older than version 4.0. In addition, the internal format of pointer files has changed to contain the creation date of the data files used. If the creation date stored in the pointer file is different than the date on the file that is used, a warning message will be displayed. This warning message, as with other warning messages, can be suppressed by changing the DISPLAY-WARNINGS setup parameter. d. The LIST FILES command now displays the creation date and the revision date of the data file, if one is available. e. Additional calculation functions have been introduced. They are: 1. CLEAN. This function will remove particular characters from a text field. Specifically it removes characters whose decimal ascii value is one of the following: 0 through 31, 127 through 160, and 255. These characters are typically referred to as unprintable characters. It takes one argument, a text field and returns a text field. An example might be: NEW_DESCR;30 = CLEAN(B:DESCRIPTION) 2. CAP. This function will capitalize the first character of each word in a text field, using a set of word delimiters supplied by the user. CAP take two arguments, both text fields, and returns a text field. The first argument is the text field to capitalize, and the second argument is the set of word delimiters. Each character in the second argument is considered to be a word delimiter. An example might be: FULL_NAME;40 = CAP(CUR_NAME,",./ '-_&#@$%*") In this example, any alphabetic character that follows any of the word delimiter characters will be set up upper case while all other alphabetic characters will be set to lower case. 3. EVEN. This function will round a number up to the next even number, or if negative, down to the next even number. It takes one numeric argument and returns a numeric value. This function may be used an a Calc-on-Total expression. An example would be: EVEN_CASES = EVEN(CASES) 4. ODD. This function will round a number up to the next odd number, or if negative, down to the next odd number. It takes one numeric argument and returns a numeric value. This function may be used an a Calc-on-Total expression. An example would be: ODD_CASES = ODD(CASES) 5. PV. This function will compute the present value of an amount given a future amount, an interest rate, and a number compounding periods. It takes three numerics arguments and returns a numeric value. The first argument is the future amount. The second is the interest rate expressed as a decimal fraction. The third is the number of periods that are to be compounded. For example, to compute the present value of 1000 for 8 periods with an interest rate of 0.5% per period, use the following calculation. RESULT = PV( 1000.0, 0.005, 8.0 ) This function may be used an a Calc-on-Total expression. 6. PVSB. This function will compute the present value of a stream of payments given a payment amount, an interest rate, and a number of periods, with each payment occurring at the beginning of each period. It takes three numeric arguments and returns a numeric value. The first argument is the amount of each payment. The second argument is the interest rate per period expressed as a decimal fraction. The third argument is is the number of periods that are to be compounded. For example, to compute the present value of a stream of 500 dollar payments, with an annual interest rate of 15%, for a period of 9 months, compounding monthly, you would use the following calculation: VALUE = PVSB( 500.0, 0.15/12, 9.0 ) This function may be used an a Calc-on-Total expression. 7. PVSE. This function is identical to PVSB except that payments are at the end of each period. This function may be used an a Calc-on-Total expression. 8. FV. This function is identical to the PV function except that it computes the future value of a current amount. This function may be used an a Calc-on-Total expression. 9. FVSB. This function is identical to PVSB except that it computes the future value rather than the present value. This function may be used an a Calc-on-Total expression. 10. FVSE. This function is identical to PVSE except that it computes the future value rather than the present value. This function may be used an a Calc-on-Total expression. 11. NEXTT. The NEXTT function returns the data value from the corresponding field from the next record in the file referenced by the argument. This function takes one argument, a text field, and returns a text field. For example, to get the vendor name of the next record in the vendor file, where the vendor file is the second file in a report, you would enter a calculation expression similar to: NEXT_VENDOR;30 = NEXTT(B:VENDOR_NAME) Please note, that if the current record is the last record in the file, or if accessing the next record causes an error of any kind, then the NEXTT function will return blanks (spaces). This function is not available for use with XENTIS/Update. This function can be disabled with the ALLOW-NEXT-CALC setup file parameter, for security reasons. 12. NEXTN. This function is identical to the NEXTT function, except that it uses a numeric argument, returns a numeric value, and will return a value of 0 if an error occurrs accessing the next record. 13. NEXTD. This function is identical to the NEXTD function, except that it uses a date-time argument, returns a date-time value, and will return a value of 00-XXX-0000 if an error occurrs accessing the next record. f. The MOD and RAND calculation functions may now be used in a Calc-on-Total expression. g. The use of the PRERT, PRERN, and PRERD functions, for security reasons, is now controlled by the ALLOW-PRER-CALC setup file parameter. h. A new method of specifying multiple primary files is now available. This new method does not limit the number of primary files used. Multiple primary files can now be specified as: generic-file/MULTIPLE=text-file where 'generic-file' is the normal XENTIS generic filename, and where 'text-file' is a text file that contains the names of the multiple primary files. Each filename in the text file should be an OpenVMS filename with one filename per line in the text file. The ALLOW-ACTUAL setup file parameter must be set to Y to use this feature. If /DICT= or /PASS= is used, then they should follow /MULTIPLE=. i. The maximum size of a calculation expression has been expanded from 132 bytes to 250 bytes, except for expressions entered into a XENTIS/Dictionary view, which shall remain at a limit of 132 bytes. j. The CREATEVIEW command is now available in the XENTIS/Report dialogue. When this command is issued, XENTIS will create a text file in a format suitable for loading into a XENTIS/Dictionary with the Dictionary Load utility, containing a dictionary view description. This command should be used only after all input data files have been specified. The format of the command is: CREATEVIEW viewname filename where 'viewname' is the name to be assigned to the view, and 'filename' is the name of the text file that is to be created. If no viewname or filename is entered, XENTIS will make up a name. k. There is a new setup file parameter EXTEND-MASK-TOT that controls whether or not print masks for numerics on total lines will be automatically extended to the left if the value being printed is too large for the print mask. This parameter may have values of Y or N. The default shipped value is Y. l. A warning message will now be displayed when a print mask longer than the maximum allowed is entered. The print mask is accepted, but truncated. Only the warning message is new. m. The undocumented LIST SUPPORT command is now available. It displays the same information that is written to a XENTIS Command File (.XCF) when the XENTIS46$SUPPORT logical is set to a value of Y. This command was added after version 4.6 documentation was completed, but will be included in a future release of the documentation. 2. /Edit There are no enhancements specific to XENTIS/Edit. 3. /Dictionary a. The COBOL to XENTIS transfer utility now processes the 'OCCURS n TO m TIMES DEPENDING' clause. The XENTIS data dictionary does not support a variable number of occurs so it will use the 'm' value when processing this clause. b. The COBOL to XENTIS transfer utility now accepts all documented synonyms for datatypes in the USAGE clause as documented in the DEC COBOL reference manual. c. The CDD/COBOL to XENTIS transfer utility has been enhanced to accept Dibol record descriptions. All fields must have a declared length, and cannot have more than two dimensions. If field names are not unique, XENTIS will change the resultant field name to be unique. Also, integer fields of 16 bytes are not supported. 4. General Enhancements a. The 2 byte versions of the RDA and RDR datatypes have been enhanced to extend their range to the year 2035, by assuming the 2 byte integer is an unsigned integer rather than a signed integer. The sign bit was previously unused. b. An additional date datatype has been added. The new datatype is called Julian Text Date and has an abbreviation of JTD. This datatype can be 5, 7, 11, or 13 bytes long. Each byte contains a numeric character. The format of a JTD datatype must be YYJJJ, YYYYJJJ, YYJJJHHMMSS, or YYYYJJJHHMMSS, where YY is a 2 digit year, YYYY is a 4 digit year, HH is a 2 digit hour, MM is a 2 digit minute, SS is a 2 digit second, and JJJ is a 3 digit day-of-year (1 through 366). The 5 byte JTD field is identical to the result produced by the COBOL language statement of "ACCEPT data-item FROM DAY." c. XENTIS now allows a system manager to control which users have access to the various modules and data dictionaries that XENTIS supports. This feature is turned on by setting the USER-SECURITY setup file parameter to a value of Y. By default, this feature is turned off. If this feature is turned on, then the system manager must define the XENTISnn$SECURITY logical in the system table (LNM$SYSTEM_TABLE) in executive mode, to point to the location of the XENTIS_SECURITY.DAT file. This file contains entries that dictate which users can access the various XENTIS modules and data dictionaries. A complete description of this file can be found in the comments of this file. If a user does not have access to a XENTIS module or a database interface, the user may received one of the following messages: Function not available. Dictionary type error -- You are not licensed for... Not licensed for module. D. KNOWN PROBLEMS AND RESTRICTIONS XENTIS has several known problems and restrictions. Some of these are known bugs in the XENTIS software, some are known bugs in other software that XENTIS uses, such as Rdb, while others are limitations placed upon XENTIS by the operating system. 1. Print frequency U (for Unique) and the setup parameter ACCUM-IF-UNIQUE may not always work when multiple primary files are being used. This is because two records in different primary files may have the same record pointer (RFA in RMS files). After sorting, these two records may get sorted next to each other. As a result, XENTIS thinks they are the same record, because they have the same RFA. 2. If the user enters a prompted literal, then backs up and makes a correction to the prompted literal, the user may be prompted for the first literal even though it is no longer part of the report. This happens because literals that were entered and then changed during the report definition, remain in the internal literal pool. This problem will automatically disappear when the report definition is saved and the report is reexecuted after exiting. 3. A problem may occur with XENTIS Dictionaries created prior to XENTIS V3.1. In some cases the prefix entry in the file record was not created correctly. Due to enhancements made to the processing of prefixes, the incorrect data stored in such prefixes may cause reports or /Edit to work incorrectly. This problem is resolved by running "Edit a Data Dictionary" from the XENTIS/Dictionary menu and selecting "Change" "File" followed by changing the prefix value from spaces to null. Running the program XDFIX_PREFIX found the images directory will also correct this problem. 4. The sizes of all records from all input files, plus calculations, sort records, and literals, cannot exceed 32767 bytes. Under most circumstances this restriction is not a problem. However, should this limitation be reached, it is possible to avoid the limitation by restricting the record size of certain files. This is accomplished as the following example illustrates. $ DEFINE RECSIZE_LIMIT_SALESHIS 12000 If the above DCL command is entered, then XENTIS will limit the SALESHIS file to 12000 bytes. 5. /Update does not allow the same data file to be used twice, unless those files are used only to perform selection and/or calculations. This means that you cannot modify a field or delete a record if that field or record is located in a file that is used two or more times in a single /Update run. This restriction is placed due to problems involving record locking, rereading records by RFA, and RMS not being able to keep track of where the next record is located. This restriction may cause certain existing XENTIS command files to no longer work; receiving the error message "Same physical file update not allowed". These XENTIS command files may not have been working correctly. The solution to this problem is to perform this operation in two passes; the first being a SELECT function where the desired records are selected and their pointers are saved into a pointer file, followed by a REUPDATE where the selected records are read after retrieving their pointers from the pointer file. This restriction was effective with V3.6 of XENTIS. 6. When using a MAXCIM ECB data dictionary, only one version of a data file is allowed. Specifying a version other than the most current version will be ignored. Using the ACTUAL/GENERIC syntax does not get around this restriction. The LIST FILES command will display the filename as the user entered the filename and the name of the file that was actually opened by the software. 7. The DROP-PRIV setup file parameter has no effect with MAXCIM V4 or later files. This is to conform to the MAXCIM security mechanism. 8. Calculations-on-totals should not use more than one occurrence of the same data field in the same report. An easy work around is to specify a calculation such as: AMOUNT3 = AMOUNT(3) 9. There is no support in the software for descending keys. They may, however, work under certain limited circumstances where the ascending/descending nature of the key is not used. 10. Entering a print mask using dual leading dollar signs or dual leading asterisks without including a trailing minus sign is accepted. Printing negative data will thus erroneously print as if it were positive, with no error indicated. 11. The COBOL to XENTIS dictionary transfer does not support sequence numbers in columns 73 through 80. Sequence numbers are typically used in older punched card source files. If you have sequence numbers, you must remove them. In addition sequence numbers in character positions 1 through 6 are not allowed. If they exist you must remove them. Using a 'Box Cut' with the TPU/EVE text editor is an easy way to accomplish this removal. 12. The Rdb interface converts Rdb VARCHAR fields to CHAR fields. This means that VARCHAR fields will have spaces appended to the end of the field to fill out the field to its maximum size allowed. If a VARCHAR field is used in an index, which is usually not wise, and two or more tables are joined using the /NOSQL qualifier, then you will probably have to specify a sub-field as your 'field to build key' field. For example: if the desired index to file B is using datatype VARCHAR(5) but only two of the five characters are really being used, then you should use only the first two characters of the input field from file A. 13. When displaying the output of a report to the screen, there is a limit of the number of lines available. If a detail contains more than the limit, then one or more printed lines may scroll off the top of the screen. 14. The FMTNM function does not support the blank-when-zero feature of print masks, designated by the ampersand character, the trailing DB if negative feature, the trailing CR if negative feature, or the surrounding parenthesis if negative feature. 15. The minimum version of Ingres that is supported is version 6.3. This allows XENTIS to support groupids of the Knowledge Management Extension to Ingres. 16. The Rdb interface does not support the catalog and schema features of Rdb V4.1 and later. When XENTIS/Report attaches to a multischema database it specifies that the multischema capability will be turned off for the duration of the attachment. If a multischema database is used, then the RDB-USE-ATTACH setup parameter must be set to Y. 17. When entering a CDD pathname and you do not want CDD$DEFAULT applied, be sure to start the pathname with _CDD$TOP rather than CDD$TOP. In other words, start the pathname with an underscore character. 18. XENTIS/File does not work when the output file is an Rdb table and the table contains computed_by fields, or virtual fields. 19. Calculation expressions may not include the vertical bar character (|). If you need a vertical bar character, the following calculation expression will yield one: BAR;1 = CHR(124.) 20. Due to a bug in Rdb, the Rdb interface for XENTIS does not work if XENTIS is installed with privileges. If you have a limited user license key, give all XENTIS users the SYSLCK privilege and define the XENTIS46_PRIV_LIST to NOINSTALL before executing the XENTIS startup procedure (SYS$MANAGER:XENTIS46_START.COM). 21. The minimum supported version of Rdb is version 4.0 on Vax systems and 6.0 on Alpha AXP systems. 22. The minimum supported version of Oracle is version 7.0. To use Oracle7 contact your XENTIS vendor as a relink is required. 23. The only supported versions of Progress are 6.2N and 6.2L on VAX systems and 6.2N on Alpha systems. 24. The Info File Creation program does not work with Rdb V4.0, but it does work with later versions of Rdb. E. PROBLEMS FIXED IN XENTIS V4.6. 1. The 12 byte versions of the TDA, MDY, and DMY datatypes were using date-time fields in the YYYYMMDDHHSS, MMDDYYYYHHSS, and the DDMMYYYYHHSS format rather than the documented formats of YYMMDDHHMMSS, MMDDYYHHMMSS, and DDMMYYHHMMSS. This problem was introduced in version 4.1 and is fixed in version 4.6. 2. The Bar Coding utility, XBAR, would abort with either a NOSYSLCK system error or a LOGNF system error if a limited user license key was used. This problem was introduced when XBAR was introduced in version 4.2. It is fixed in version 4.6. 3. Under certain circumstances XENTIS would abort if a print frequency of N was used with a calculation-on-total. This problem was introduced in version 4.5 and has been fixed. 4. In display mode, the "Skip to top of page" prompt did not display all valid responses in the info window. The valid response of 'O', for Odd, was not being displayed. 5. The D5 function did not recognize the year when the 2 digit year was 00 and when the argument to the D5 function was a numeric field rather than a text field. This problem has existed since version 3.0. 6. The error message "Unequal multi-range counts for first/last key" would be displayed when a user would specify a starting key but no ending key, or an ending key but no starting key, for reading the primary file. This problem was introduced in version 4.4. 7. If the user specified spaces for the starting or ending keys for the primary file, XENTIS would behave as if the First record or Last record was specified respectively. This problem was introduced in version 4.3. 8. The D06 and D07 foreign date datatypes did not write dates correctly with XENTIS/File, XENTIS/Update, and XENTIS/Edit when the year was during or after 2000. 9. The CENTURY-ADJUST setup file parameter was ignored if used in a system setup file. It was not ignored if used in a user setup file or entered with a SET command. This problem was introduced in version 4.5. 10. If the setup file parameter FINAL-FF was set to Y, output of the report was to the user's terminal, such as TT:, and zero records were selected, XENTIS would erroneously display a 'Divide by zero' error message immediately prior to program exit. This problem was introduced in version 4.5. 11. When using the QUERY function, if the QUERY-FRMT-PRINT-QUE setup file parameter was set to N, and the output of the report was to a disk file, the XENTIS dialogue would display an error message and refuse to proceed. This problem was introduced in version 4.5. 12. When using Tolas application date formatting, which is controlled by the TOLAS_DATE_FORMAT logical, XENTIS did not recognize date literals of the form DD-Mon-YYYY or D-Mon-YYYY. It did not recognize the 4 digit year. This problem does not exist if the TOLAS_DATE_FORMAT logical does not exist. This problem was introduced in version 4.5.

GrayMatter Home | XENTIS Home | Download Software | XENTIS Technical Support | Contacting GrayMatter | XENTIS News

Comments? Send us your feedback.	www.graysoft.com
	© Copyright 2020 GrayMatter Software Corp. All rights reserved.