SmartStar® Version 7.2 Notes for OpenVMS AXP

This document lists the differences in functionality of the SmartStar® V7.2 product for the OpenVMS AXP platform.

Unsupported Features:

On OpenVMS AXP, the following features are not supported in this release:

• SDESIGN/UAR

Additional Notes:

• Version 6.1 of OpenVMS AXP is required.
• Supported database types are LDB, RQP, RDB, Sybase 10, ORACLE 6, and ORACLE 7.
• Supported datatypes in an LDB FILE table are:
  
  scaled/unscaled integer (BYTE, WORD, LONGWORD, QUADWORD) F-FLOAT, D-FLOAT (accurate to 53 mantissa bits), G-FLOAT, CHARACTER, VMS DATE, ANSI DATE

• In RQP and the LDB FILE table types, DOUBLE creates a D-FLOAT with a 53-bit mantissa. Use G-FLOAT to create a G-FLOAT.
• The FLOAT8 function in SQL converts to G-FLOAT rather than D-FLOAT.
• In COPYIN and COPYOUT, use the F8 format for D-FLOAT in the data file, and use FG for G-FLOAT in the data file.
• If you have existing compiled scripts (.SCB files) that use the FLOAT datatype, the scripts will need to be re-compiled on OpenVMS AXP before they will run on OpenVMS AXP. In general, scripts that use floating point datatypes must be compiled under the same operating system on which they will be run. In other words, if you want to run the script under VAX/VMS, you must compile it under VAX/VMS, and if you want to run it under OpenVMS AXP, you must compile it under OpenVMS AXP.
• Since OpenVMS AXP does not allow the UNIVERSAL clause in a LINK statement, you must link shareable images with transfer vectors. For example:
  $LINK myname,sys$input/opt
  SYMBOL_VECTOR=(myname=PROCEDURE) /* or (myname=DATA) */
  
• When linking 3GL programs containing SmartCall routines, use the NONATIVE_ONLY option on the command line. For example:
  $LINK/NONATIVE_ONLY myprogram
• If you are writing 3GL programs in FORTRAN on OpenVMS AXP, SmartStar® functions (such as SC_KBSET, etc.) must be declared as INTEGER*4 rather than INTEGER.