INSTALLATION CONFIGURATION
DISPOSITION FUNCTIONS (USER)
Modified the print file class fields throughout Installation Configuration to all lower case values. Use of lower case values requires Wang VS OS Version 7.53 or above. SPEED II will convert lower case values to their corresponding upper case value if the operating system does not support lower case print file classes. NOTE: The print file class is used to determine which printer(s) are able to print a file. It does not determine the protection class of the report file.
OUTPUT FUNCTIONS (USER)
Added a new field to allow installations to determine if special characters (Hex 80 - 9F) should be passed through to printers without translation (Release 7.0 functionality) OR if they should be underlined (Release 6.x and below functionality). International installations which need to underline the special characters used for foreign languages should set this value to 'N'. (ECR 3820)
APPLICATION DESIGN
DISPOSITION FUNCTIONS (DESIGN)
Disposition functions now allow lower case values for Print Class. Use of lower case values requires Wang VS OS Release 7.53 or above. If a Disposition function specifies a lower case value and SPEED II is run on a machine with an Operating System Version below 7.53 SPEED II will convert the lower case value to the corresponding upper case value at run time.
USER INTERFACE
DISPOSITION FUNCTIONS (USER)
Modified the Disposition Screen to allow lower case print class values if SPEED II is run under Wang VS OS Release 7.53 or above.
BUG FIXES
CHANGE ALL REFERENCES
Change All References for Application IDs did not change the application ID for Auto Access Keys in Data Dictionary Maintenance. This has been corrected. (ECR 3139)
When changing a filename, SPEED II did not update the Date Changed and Changed By User ID fields for the file. This has been corrected.
DISPOSITION FUNCTIONS (USER)
If a Disposition Function changed the SPOOLSYS to a machine other than the machine SPEED II was being executed on SPEED II would reset the SPOOLSYS after the first report was completed. This has been corrected. (ECR 3243) If you want the SPOOLSYS value selected during the execution of a job to remain in effect after a job has completed remember to add an additional disposition function after the user has selected the SPOOLSYS which has the value '*' in the SPOOLSYS field. This disposition function does not need to be displayed to the user. For additional information refer to the HELP screen (PF28) while positioned on the SPOOLSYS field in disposition function design.
If a user had their SPOOLSYS set to a non-blank value SPEED II would clear out the value during initialization. This has been corrected. (ECR 2617)
SPEED II was always setting the Wang Printer Number to 000 regardless of what value it should have been set to. SPEED II will now correctly set the Printer Number.
GENERAL CORRECTIONS
When SPEED II was executed on a VS using Wang VS 0S Release 7.40 or above the Day of Week in the status line (line 22 of workstation) would display incorrect values, the SET DATE command would set the Century portion to 00, and DATEADD would not function correctly. This has been corrected. (ECR 2616)
Made numerous changes to make SPEED II correctly set the century when SPEED II is running across the century change.
Modified SPEED II so it computes the Elapsed Time correctly when creating a Usage Log record if the execution of the job spanned the change of century. (Job started in 20th century and completed in the 21st century.)
OUTPUT FUNCTIONS (DESIGN)
If an OUTPUT function specified "Print Beside" SPEED II would print it down one line (effectively printing below). This has been corrected. (ECR 2635)
If an OUTPUT function specifies a Subheading window, but the SORT preceding the OUTPUT does not specify a subheading on the Control Field for that subheading SPEED II would abort in OUT105 just after the Merge was 100% complete. This has been corrected. (ECR 2615)
SORT FUNCTIONS (DESIGN)
Unable to access the Sort Memory Files (MSFN, MSLT, MSRT) if the application version is not 00. This has been corrected. (ECR 3025)
SORT FUNCTIONS (USER)
If a job containing a SORT was executed from within a function (e.g. INPUT) or was called from a direct menu and then an OUTPUT function was executed (after the previous job completed) SPEED II would report that "Sort Files Do Not Match between Sort, Sort Setup, Output, and Update Functions". This has been corrected. (ECR 2683)
UPDATE FUNCTIONS (USER)
If an UPDATE function specifies a Subheading window, but the SORT preceding the UPDATE does not specify a subheading on the Control Field for that subheading SPEED II would abort in UPDT105 just after the Merge was 100% complete. This has been corrected. (ECR 2697)