 |
 |
 |
XENTIS Documentation -- Release Notes
XENTIS 4.7a
XENTISV4.7A Release Notes Version 4.7A is funciontally identical to version 4.7 except for the following patches. 1. Sort-On-Totals now works when a Select-On-Total is not used. This problem was introduced in version 4.7. 2. The special date literals of YESTERDAY, TOMORROW, FIRST, LAST, BEGIN, and END were not always processed correctly when the CENTURY- ADJUST setup parameter was set to a non-zero value. This problem was introducted in version 4.5. XENTIS V4.7 Release Notes This document contains information about using XENTIS V4.7 and highlights features that are available in V4.7 that were not available in versions prior to V4.7. 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:XENTIS047.F/SELECT=[*...]*.REL*/SAVE_SET [] where 'tape_dev' is your tape drive. 2. The installation procedure for V4.7 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 XENTIS47$COMFILES: directory. This command file removes the system logicals that were created with the XENTIS47_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 XENTIS47_USER_PACK.EXE. 9. On VAX systems XENTIS V4.7 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.7 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 XENTIS47$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 XENTIS47_USER_PACK.EXE XENTIS_USER_FUNCTION.EXE XENTIS47_USER_FUNCTION.EXE XENTIS_XRP3GL.EXE XENTIS47_XRP3GL.EXE The application program interface (API) to these routines have not changed from V4.2. 15. If you are upgrading from V4.2 or later, please execute the XENTIS_UPGRADE.COM procedure found in XENTIS47$COMFILES:. This purpose of this procedure is to inform the installer of the names of the various XENTIS text files that have been modified by this site in the previous version. 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 47, 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.7 may be installed and started, while a previous version is active and running. It may not be installed while another installation of V4.7 is active and started. The V4.7 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 a version of XENTIS that was previously installed. If it is desired for pre V4.3 batch command files to use version 4.7, then perform the following steps. a. Copy XRP47.EXE to XRP.EXE in the same directory. b. Define a logical as: DEFINE XENTIS$PROGRAM XENTIS47$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.7, set XEN_VER to "47"; 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. XENTIS now supports the creation of HTML Table files. Instead of writing a regular report, XENTIS can produce output that can be viewed with a web browser where the output has the appearance of a table. This feature is invoked by entering a response of WEBPAGE at the "Function" prompt. The resulting dialogue is almost identical to the dialogue for XENTIS/Model. The additional prompts, when compared to XENTIS/Model are: 1. "Table control file" This prompt replaces the "Model control file prompt. The format and style of the output table is determined by the contents of the chosen Table control file. This file contains actual HTML code that XENTIS incorporates into the output file. A number of pre-written Table control files are supplied with XENTIS, however the user may modify existing Table control files or create new Table control files. The file type (extension) of these Table control files is determined by the new DFLT-WEBPAGE-TYPE setup file parameter. 2. "First table title line" This prompt allows the user to produce a title for this report. 3. "Second table title line" See previous prompt. 4. "Third table title line" See previous prompt. 5. "HTML document title" All HTML documents must have a title. The result will be entered in the catalogue if so desired. 6. "Enter into HTML catalogue" A Y or N response controls whether this report will be entered into the HTML catalogue. This prompt is indentical in function to the prompt issued when pre-formatted HTML output reports are produced. 7. "Rows per HTML document" Long documents are usually broken up into multiple pages. How many rows, or lines, are desired for each page. The default value for this prompt is found in the chosen table control file. 8. "Justification" Each data field can be left justified, right justified, or centered in its data cell. Several new setup file parameters exist to support the creation of HTML Table output files. They are: 1. DFLT-WEBPAGE-TYPE. This parameter controls the default file type (extension) of Table control files. Up to seven characters may be used. 2. WEBPAGE-CTL-FILE. This parameter has the name of the default Table control file. If no device/directory is specified, XENTIS assumes this file will be found in the directory pointed to by the XENTIS47$REPORT$DATA logical. 3. HTML-TAB-POSTFIX. This parameter is indentical to the HTML-PRE-POSTFIX parameter introduced in version 4.5 except that this file is used only for HTML Table output. 4. HTML-TAB-INDEX. This parameter is indentical to the HTML-PRE-INDEX parameter introduced in version 4.5 except that this file is used only for HTML Table output. The use of this new feature requires a license for XENTIS/Model or XENTIS/Web (license key modules MOD or WEB). Creating output files consisting of preformatted HTML now requires a XENTIS/Model or XENTIS/Web license. b. A new setup file parameter of INCREMENT-LINE has been created. When using XENTIS/Report, this parameter will determine if XENTIS should automatically increment the default print line should the current field's default placement be greater than the right margin. This condition is determined by examining the value of the RIGHT-MARGIN parameter. If RIGHT-MARGIN is zero, then XENTIS examines the current terminal width. This parameter has valid values of Y or N. The shipped value is N, for compatibility with prior versions. c. A new setup file parameter of ABORT-IF-ERR-EXE has been introduced to function similar to the ABORT-IF-ERR-BATCH parameter. The new setup parameter will cause XENTIS to exit with a fatal error status that can be detected by a DCL command procedure if XENTIS encounters an error condition that it cannot recover after the "Execute" prompt. This parameter has valid values of Y and N with a default shipped value of Y. d. A new setup file parameter of SUPPRESS-DUP-KEY-MSG is now available to optionally suppress "Duplicate key" error messages when using XENTIS/File. Other error messages that occur while writing to the output file will always be displayed. This parameter has valid values of Y and N, with a default shipped value of N. e. User level security has been enhanced. The system manager can now restrict users on the QUERY, SELECT, CREPORT, and the WEBPAGE functions. See the XENTIS_SECURITY.DAT file in the data directory for more information. f. Most error messages that indicate an underlying error will now be displayed on two lines. This improves readability. g. XENTIS now accepts form numbers at the "Form name" prompt. In addition, if the user is operating in display mode, form numbers will be displayed in the info window in addition to the form names. As part of this enhancement, the description for each form will also appear in the info window. h. A new calculation function called ERASE has been added. This function does not return any useful data. It's purpose is to easily set a record to zeros, and spaces. This function takes one argument, a text or numeric field, and always returns a value of one. The record erased is indicated by the file designation of the lone argument. The record in the data file remains unchanged. For example: X = ERASE(C:ORDNUM) IF C:ORD_DATE > 01-MAR-1998 will result in all field of the current record from from C being set to zeros and spaces if the field ORD_DATE from file C has a value greater than 01-MAR-1998. i. A new calculation function called WILD is now available. This function corresponds directly with the OpenVMS system routine STR$MATCH_WILD which compares a data character string against a wildcard character string. This function has two arguments a data text field, and a wildcard text field. It returns a numeric value of one if there is a wildcard match, and zero if there is no match. See OpenVMS documentation on STR$MATCH_WILD for more information. For example: X = WILD(B:PROD_CODE,"%%XA*HN") will result in X being set to one if B:PROD_CODE has the characters XA in positions 3-4 and end with HN, otherwise X will be set to zero. Corresponding with this new WILD function is a new setup file parameter that alters the functioning of the WE and WN (wildcard equals and wildcard not equals) operators. This new parameter is called ENHANCED-WILDCARD. It has valid values of Y and N. If set to Y, the WE and WN operators work using the OpenVMS STR$MATCH_WILD system routine for wildcard matching. If set to N, the WE and WN operators work as they have worked in previous versions. To be compatible with prior versions, the default shipped value of this parameter is N. j. Some minor formatting improvements have been made to the "Browse a report", "Print a report", and "Browse a report definition" menu items. k. The default HTML catalogue file supplied with XENTIS has been changed to support the display of the output file creation date and time. l. The index file produced for preformatted HTML output files has been enhanced to include the first data line of each HTML output file next to the page number. m. XENTIS/Model will now display the fields specified when operating in display mode. n. The LIST SUPPORT command will now display license key information. o. The "Execute" prompt will now accept the /READ=n option to control or limit the number of records to read from the primary file. For example, appending /READ=100 will cause XENTIS to read a maximum of 100 records from the primary data file. p. XENTIS/Report can now be invoked with a foreign command that passes information to the program on the command line. A number of qualifiers, or options, can be specified on the command line. They are: /REPORT=filename1 Same as defining the XENTIS$CMDFILE symbol. /DICTIONARY=filename2 Same as defining the XENTIS$DICT symbol. /PASSWORD=password Same as defining the XENTIS$PASSWD symbol. /CHAIN=filename3 Same as defining the XENTIS$CHAIN symbol. /SELECT=number Same as the "Execute" prompt option. /READ=number Same as the "Execute" prompt option. /NOERR Same as the "Execute" prompt option. /STATS Same as the "Execute" prompt option. /GO Same as the Command File option. /BATCH Same as the Command File option. /NIGHT Same as the Command File option. /SHOW Same as the Command File option. All qualifiers can be abbreviated to as few as three characters. Only one of /GO, /BATCH, or /NIGHT can be used. These foreign comand qualifiers have priority over symbols. For example: $XRP :== $XENTIS47$PROGRAM:XRP47 $XRP/REPORT=CUSTLIST/DICT=MYDICT.DIC/PASS=MYPASS/SEL=100/GO This enhancement results in a change to the callable interface for sites that use callable XENTIS. 2. /Edit There are no enhancements specific to XENTIS/Edit. 3. /Dictionary a. The "Load a file dscription from a text file" utility will now load a temporary dictionary created with XENTIS/Report. The temporary dictionary must have the same file type (extension) as specified in the setup file. After loading, the user needs to adjust those dictionary attributes that are found in a XENTIS dictionary that are not found in a temporary dictionary, including the actual filename and the key (index) specifications if the file is an indexed file. 4. General Enhancements a. The "Browse a report" and "Print an report" menu items can now display files using more than one file type (extension). This ability is controlled by the XENTIS47$BROWSE_FILES logical that is defined in the XENTIS47$COMFILES:XENTIS_LOGICALS.COM file. Normally this logical is defined as follows: DEFINE/SYSTEM/EXEC XENTIS47$BROWSE_FILES LIS If you want multiple file types (extensions) to be processed by these two menu items, then extend this logical into a search list logical. For example, to have "Browse..." process .LIS file, .TXT files, and .LOG files, then define the logical as follows: DEFINE/SYSTEM/EXEC XENTIS47$BROWSE_FILES LIS,TXT,LOG This logical can also be defined in the process table without executive mode as follows: DEFINE XENTIS47$BROWSE_FILES LIS,TXT,LOG b. For date data types RDA, RDR, TDA, MDY, DMY, PDA, JDA, PRD, and JDT, XENTIS has always assumed the data fields that it processed contained valid data. Some customer have indicated that they want XENTIS to display a null or invalid date when it encounters invalid dates in data files. Therefore, there is a new setup parameter called USE-BAD-DATES that determines whether or not XENTIS will process the above listed date data types when they contain invalid dates. The valid values of this parameter are Y and N. The shipped value of this parameter is N. To retain previous XENTIS behavior, set this parameter to Y. c. Included in the 'F' saveset on the XENTIS distribution tape, are several files that may be of interest to sites using the Maxcim application software. The file ECBFILE.DMP is a XENTIS/Dictionary dump file that describes the Maxcim ECB data dictionary as an indexed file. This file can be used to load data descriptions into a XENTIS dictionary, or it can be used as a temporary dictionary to create reports. The file ECBFILE.XCF is a report definition file that creates a listing of a Maxcim ECB data dictionary. The file ECB2XEN.XCF is a report definition file that reads a Maxcim ECB data dictionary and write a text file that is suitable for loading into a XENTIS data dictionary using the dictionary load utility. This allows a user to processes Maxcim files using a XENTIS data dictionary. d. A new DCL procedure called XENTIS_UPGRADE.COM is available in the XENTIS47$COMFILES directory. This procedure examines the user modifiable text files from prior versions that XENTIS uses and compares them with files that were originally shipped. This allows the person installing XENTIS to know which text files in previous versions were modified at that site, so that similar modifications can be performed when installed version 4.7. e. A new DCL procedure called XENTIS_CHECKENV.COM is available in the XENTIS47$COMFILES directory. This procedure examines the process environment to determine whether or not XENTIS is able to execute. It examines several process quotas, and shareable images to assure that XENTIS is able to execute. If it discovers any problems, it reports them to the user. f. Alpha system users should no longer have to relink when using CDD. The minimum version of CDD supported without relinking is 6.1. g. XENTIS no longer requires DECnet to be active. 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 XENTIS47_PRIV_LIST to NOINSTALL before executing the XENTIS startup procedure (SYS$MANAGER:XENTIS47_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. 25. XENTIS version 4.3 and later cannot coexist with version 4.2 on Alpha systems. Version 4.2 was a temporary version and uses translated images. Remove version 4.2 from your Alpha computer system. 26. The CENTURY-ADJUST setup parameter when used with foreign dates, also known as user written dates, is applied only after a valid date is retured from the customer maintained foreign date routine. Once a valid date is returned, if the year, when ignoring the century, is less than the value of the CENTURY-ADJUST parameter, and the year is less than 2000, then XENTIS will add a century to the date. One effect of this is that since the foreign date routine cannot return a date of 29-Feb-1900, a resulting date cannot be 29-Feb-2000. Once again, it is the responsibility of the customer maintained foreign date routine (XENTISnn_USER_PACK) to return a valid date. E. PROBLEMS FIXED IN XENTIS V4.7. 1. A problem existed in version 4.6 where if a long calculation or selection expression was entered using the field number syntax and if upon expansion of that expression the total number of characters of that expression was greater than 222 characters but less than 250 characters, and if the user responded with a "B", "O", or "C" at the "Execute" prompt, then the resulting DCL command file was creating incorrectly and the report would abort. This was corrected in version 4.7. 2. Under some circumstance involving reports with three or more data files using the Simultaneous Access feature, a calculation may not be performed at the right time if the calculation involved data from an auxilliary data file. This problem was introduced in version 4.4 and corrected in version 4.6B 3. When using XENTIS/Model, the software was requiring write access to the model control files. This problem was introduced in version 4.5 and corrected n version 4.6B. 4. 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 and corrected in version 4.6A. 5. 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 and corrected in version 4.6A. 6. 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 and corrected in version 4.6A. 7. 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 and corrected in version 4.6A. 8. If XENTIS startup was aborted by the user when the startup procedure was executing the XENTIS_INSTALL_IMAGES.COM file, then subsequent attempt to startup XENTIS would produce an error unless the user logged off the system first. This problem was introduced in version 4.1 and fixed in version 4.7. 9. If the value of the REGISTRY-FILE parameter was blank, XENTIS would still create a registry file using a blank name, rather than skip the registry file feature. This problem was introduced in version 4.3 and fixed in version 4.7. 10. At the "Form name" prompt, XENTIS would display Printer queue names and Terminal queue names, but not Server queue names. XENTIS now displays Server queue names. 11. The default value for the "Lines to print on page" prompt could at times be a very small value such as 3, or 5, depending upon a variety of conditions. This problem was introduced in version 4.5 and fixed in version 4.7. 12. Under some circumstances when the USER-SECURITY setup parameter was set to Y, XENTIS would abort with a privilege error. This was introduced in version 4.6 and fixed in version 4.7. 13. If the /ACCUM=n qualifier was used on a calculation and the file specified by 'n' was greater than any other file referenced in all the calculations, then the value of 'n' was effectively replaced with the highest file specified in all the calculations. This problem was introduced in version 4.4 and fixed in 4.7. 14. If the COBOL to XENTIS dictionary transfer did not find a valid COBOL record, no error message was displayed. This was fixed in version 4.7.
GrayMatter Home | XENTIS
Home | Download Software |
XENTIS Technical Support |
Contacting GrayMatter | XENTIS
News
| Comments? Send us your feedback. |
|
|
©
Copyright 2020 GrayMatter Software Corp. |
