Specifications

Data Export
Known Data Export Anomalies in SPECTRUM 6.0.3
SPECTRUM Software Release Notes Page 63
export contains models with names longer than the previous default, the
export will likely fail with an Oracle error indicating that the insert value
was too large for the column.
Solution: Manually drop the existing table and then perform the export.
This will establish the column width to the value specified in the dtxscript.
Problem 6: Statistical exports fail to SQL databases because of an
incorrect echo statement in the scripts that when run perform database
insertions.
Solution: In the echo_no_cr() function, there is a case statement with
the following line:
AIX|SunOS|ULTRIX) # berkeley; use -n option
The above statement should be changed to:
AIX|SunOS|ULTRIX|Windows_NT # berkeley; use -n option
In addition, the following two lines:
# append \c
echo “$*\c”
should be changed to:
# append -n
echo -n “$*”
Problem 7: When scheduling a Report or a Data Export through Windows
NT using Internet Explorer 4.0.x, you cannot see previously saved entries
once you exit and then reenter the Scheduler view and thus cannot delete
or modify them.
Solution: To solve the problem in Reports, upgrade to Internet Explorer
5.0 or greater and set the schedule service requirements for Windows NT
as specified in the Report Generator User’s Guide.
In Data Export, the filtering mechanism fails to work correctly. As a
workaround, upgrade to Internet Explorer 5.0 or greater and then view,
add or modify Data Export entries in the Scheduler on the Control Panel.
This problem will be corrected in a future release of SPECTRUM.