For a list of current known issues, refer to the Customer Service Discussion Forums at:
If you are using a callx trigger on a file, and:
the trigger uses the access(16) function
the trigger subroutine is flash compiled
the file being updated is encrypted
the callx will abort. The workaround is to recompile the subroutine non-flashed until a patch can be made available.
D3 Oracle Gateway and D3 MQSeries are not supported on the 64bit version of D3 AIX 9.1. If you need either one of these products to complement your 64bit D3 AIX installation, contact Rocket Customer Support at d3mvsupport@rocketsoftware.com or your Rocket Sales representative.
When logging DL'd files only, removing the l option from a DL'd file on the master system in a cascading configuration with set-dptr -l removes the l option from the file on the primary slave system, but does not remove the l option from the file on the secondary slave system.
On this release of D3 9.0, numeric indexes only support integer numeric indexes, which includes dates that are stored in internal format. If you wish to create numeric indexes on decimal numbers, numeric data must be stored in scaled internal format (that is, with no decimal or thousands separators). This ensures correct behavior when accessing numeric indexes in the VME.
In order to take advantage of indexes when doing date range selects, you must use the 'short form' range specification. For example:
Select invoices with date >= “2/1/13” and <= "2/28/13" |
The statement will use the index to return the entire range of invoices that fall within the 2 dates specified. However, the long form where 2 dict items are specified (even if they are the same dict item) will only use the index to return the invoices that satisfy the first date qualifier. D3 would then look through all of the invoices returned from the first part of the select to compare the dates and select the invoices that also satisfy the second condition, a much slower process.
Select invoices with date >= “2/1/13” and with date <= "2/28/13" |
It is now possible to specify a core memory setting much higher that the 2 GB limit in earlier versions of D3 AIX. However, it is recommended that sufficient physical RAM is present on the machine to accommodate the higher core setting.
To run FlashCONNECT with D3 AIX 9.1, you must upgrade to FlashCONNECT 3.9.