SPEED II release notes

Release notes for SPEED II, the development environment for Wang computers that preceded APPX, from 6.00.00 to 7.03.03, newest first. They were published on www.appx.com and moved here in October 2026. Upgrade steps are in SPEED II upgrades.

SPEED II 7.03.03

SPEED II Release 7.03.03

SPEED II INTERNALS

GENERAL CORRECTIONS

1. Added Century to the date displayed on line 22 of the workstation.
   
   Sites using Foreign Language files must edit GEN.$-WS-LINE22 and GEN.$-LINE22-WSN to add two characters to the date field.
   
   
2. Added Century to the estimated completion date / time displayed during Output, Update, and Sort functions.
   
   Sites using Foreign Language files must edit FUNCTION.COMPLETION-TIME to add two characters to the date field.
   
   
3. Added Century to the date in the standard headings of reports. This only applies to reports which use SPEED II generated headings.
   
   
4. If a company level override existed for the Date Format, Date Separator, Time Format, and/or Time Separator SPEED II would NOT use it when formatting the estimated completion time during Output, Update, and Sort Functions. This has been corrected.
   
   

SPEED II 7.03.02

SPEED II Release 7.03.02

INSTALLATION CONFIGURATION

Installation Information Maintenance (input function) would cancel with a 'Fatal error file is not open or field is in a file that does not exist' if either a Cancel Menu or a Direct Menu were entered. The function would also cancel and return to the menu if you attempted to SCAN from the Application ID field for either the Cancel Menu or Direct Menu fields. This problem began with SPEED II Release 07.03.01 and has been corrected with this release. (ECR 4541)

APPLICATION DESIGN

DISPOSITION FUNCTIONS (DESIGN)

If a designer attempted to create a Disposition Function which would run in Background and create Comma Delimited Output the system would not allow the function to be created unless at least one of the 'Screen', 'Printer', or 'WP Document ID' fields was 'Y'.

At run time SPEED II would report an error indicating that these three fields all had to be 'N' for Comma Delimited Output. This problem has been corrected.

FIELD OVERLAP REPORT

If the same field is used on multiple input/output functions and in some cases it includes the group character and in others it does not the report may list overlaps which do not exist or it may omit overlaps which do exist. This is a known problem which has NOT been corrected in this release. (ECR 4532)

SPEED II 7.03.01

APPLICATION DESIGN

COMMANDS

• The IF, AND, and OR commands have been modified to use the "Date Pivot" logic if both of the fields have Year as their highest component. This is a change from Release 07.03.00 which would only use the "Date Pivot" logic if one of the fields included Century and the other had Year as its highest component. "Date Pivot" logic can still be disabled completely by setting the "Date Pivot Year" in Installation Information to zero (0).
• The DATE BTW command has been altered to use the "Date Pivot" logic if both fields have Year as their highest component. This is a change from Release 07.03.00.

BUG FIXES

DISPOSITION FUNCTIONS (USER)

• If a user used the 'Comma Delimited Output' feature in a job, SPEED II would continue to create Comma Delimited format for OUTPUT and INQUIRY functions even AFTER the job had finished and returned back to the menu. The user had to execute another job which included a DISPOSITION function to get standard output.
• If a user entered an override value for the Print Filename, Library, or Volume; or used a value other than 'U' for 'Action If Output File Exists' on the DISPOSITION window these values would remain in effect until another DISPOSITION function was executed.

Both of these problems exist in all Release 7.x versions of SPEED II prior to 07.03.01. (ECR 4316)

INPUT FUNCTIONS (DESIGN)

• If an application designer created an INPUT FUNCTION from the Job-Step editor, the INPUT FUNCTION would have an invalid application lock and could not be run. This problem exists in all releases of SPEED II since 06.00.00. The problem has been corrected. (ECR 4315)

INPUT FUNCTIONS (USER)

• If an INPUT FUNCTION included a DATE field which included Century through Hour (at a minimum) AND the Century was being masked AND the field included the AM/PM indicator, SPEED II would cancel with a PC07 whenever the user entered a date which included PM. This problem exists only in Release 07.03.00 of SPEED II. (ECR 4380)

SCAN

• If a file included a DATE field in its key and the Century portion of the date was being masked, SPEED II would not compute the Century when the SCAN key was being used. This would cause the SCAN to position at the wrong position in the file. This problem exists only in Release 07.03.00 of SPEED II.

SPEED II 7.03.00

SPEED II INTERNALS

REGISTRATION DATA

• Changing the registration type from Customer to Consultant; from Consultant to Customer; or from Release 5 to Release 7 would cause SPEED II startup errors in some circumstances. SPEED II would present a Wang VS Getparm screen requesting that the user correct the data necessary to open a file. The user had no way to determine what file SPEED II wanted or what the correct filename, library, and volume should be. SPEED II now correctly changes the registration type when new Verification Numbers are entered while running $$ in $ (Registration Entry). This prevents the subsequent startup error.

INSTALLATION CONFIGURATION

• A new field has been added to window 2 of Installation Information File Maintenance to allow an installation to determine the 'Date Pivot Year'. This field controls the "Date Pivot" logic. If SPEED II needs to compute a Century for a date field, this field is used to determine the value computed. The following logic is used to compute the century (field-century):
  • if system-year >= pivot-year
    if field-year < pivot-year
    field-century = system-century + 1
  • else
    field-century = system-century
  • else
    if field-year < pivot-year
    field-century = system-century
    else
    field-century = system-century - 1
  • Setting this field to zero (0) disables the "Date Pivot" logic.
  • IMPORTANT: The implementation of Pivot Dates in APPX Release 7.x is NOT all that is required to upgrade applications to Year 2000 compliance. Additional conversion steps are required. Please see the Y2K Implementation Guide for further information on these requirements.
• A few examples of the Date Pivot logic:
  • If the target year is '98' and the pivot year is '50':
  • if system year = 1998, target will be 1998
  • if system year = 2001, target will be 1998
  • if system year = 2051, target will be 2098
  • If the target year is '02' and the pivot year is '50':
  • if system year = 1998, target will be 2002
  • if system year = 2001, target will be 2002
  • if system year = 2051, target will be 2102

LANGUAGE UTILITY

• Six new mnemonics have been added to the language file. International installations will need to update their language files as part of the installation of this release. The release tape includes prior version index files to allow upgrading from a release 6 language file or from a release 7.0 (shipped with SPEED II releases 7.0.0 through 7.2.x). If you are upgrading from a release 6 language file you will need to rename some files in library $$$ before running the language utilities.
  • Old Name New Name
  • $0000000 $000R700
  • $0000002 $000R702
  • $000R600 $0000000
  • $000R602 $0000002
• A list of the new mnemonics can be printed by using the language utilities.

APPLICATION DESIGN

COMMANDS

• The IF, AND, and OR commands have been changed to use the "Date Pivot" logic if one part of the comparison is a Date field with Century and the other part of the comparison is a Date field which has the Year as its High End.

Example:
'Date YYMMDD' contains '06/03/99' (Jun 03, 99)
'Date CCYYMMDD' contains '01/02/2000' (Jan 02, 2000)

When the "Date Pivot Year" is NOT zero, SPEED II will compute a value for the Century and add it to the 'Date YYMMDD' field before doing the IF, OR, or AND comparison. As long as the "Date Pivot Year" is less than 99, the 'Date YYMMDD' value will be considered LT the 'Date CCYYMMDD' field.

If the "Date Pivot Year" IS zero, SPEED II will add the CURRENT Century to the 'Date YYMMDD' field before doing the IF, OR, or AND comparison. This means that 'Date YYMMDD' will be LT 'Date CCYYMMDD' if the current century is '19', but GT 'Date CCYYMMDD' when the current century is '20'.

• The SET command has been altered to use the "Date Pivot" logic when the Destination field is a Date which includes the Century and the Source field is a Date which has the Year as its High End.
• The DATE ADD command has been altered to use "Date Pivot" logic if the Date field does not include the Century. This is so that SPEED II can determine if the year is a leap year or not.
• The DATE BTW command has been altered to use the "Date Pivot" logic when one Date field includes the Century and the other does not.
• The SET DAY command has been altered to use the "Date Pivot" logic when the Date field does not contain the Century.

DEBUG CHANGES

• When debugging commands, Date fields which have part of the stored date masked will still display the entire date when single stepping through commands or while editing the values in the dates.

FILES / FIELDS (DESIGN)

• New fields have been added to the definition of Date fields which are used as part of the support for "Date Masks". The designer can now specify the default parts of a date field to be displayed. The mask values can be overridden when adding the field to a window (Input or Output).

INPUT FUNCTIONS (DESIGN)

• The ability to specify which parts of a date should be masked on an Input Window has been added. If the Mask Specifications are left blank, then SPEED II uses the Mask specified in the Data Dictionary. If there is no mask specified in the Data Dictionary, then SPEED II will display the entire date field stored in the data file. Masking portions of a date on an Input Window causes SPEED II to compute the value of the masked portions according to the "Date Pivot" logic rules. Consequently, masking portions of a date CAN cause the masked portions to be changed in the data files.

NEW DESIGN CAPABILITES

• Support has been added to mask portions of date fields on Input and Output functions. This allows the designer to add the Century (or any other parts) to a date field while not displaying some portions on the Input Function screen or Output Function report. This feature simplifies Year 2000 support by allowing an application to have century stored in the data files but not displayed on the screens. Because the century is not displayed on the screen, users will not need to key the extra digits for century and the reformatting of screens and reports to make room for the extra digits can be avoided.

During data entry SPEED II will "default" the parts of a date field which are not displayed. If "Date Pivot" logic has been enabled, then SPEED II will compute the century using the "Pivot Year" and the "Date Pivot" logic (described in the Installation Configuration section of this report and on the "Date Pivot Year" field on window 2 of Installation Information File Maintenance) If "Date Pivot" logic has been disabled then the century defaults to the current century.

NEW DESIGN CAPABILITES

• Added a new Input Function which allows a designer to maintain the characteristics of date fields. The function displays each date field (from a file or work fields) and allows changes to the fields on the second window of dates. This includes storage size, default display mask, initial value, range checking, etc. This function can be found on the 'Special utilities' menu.

OUTPUT FUNCTIONS (DESIGN)

• The ability to specify which parts of a date should be masked on an Output Window has been added. If the Mask Specifications are left blank, then SPEED II uses the Mask specified in the Data Dictionary. If there is no mask specified in the Data Dictionary, then SPEED II will display the entire date field stored in the data file. Masking portions of a date on an Output Window does NOT alter the value stored in the data file.

SORT FUNCTIONS (USER)

• SPEED II will continue to display all of the parts of a Date which are stored in the data file when presenting the 'Record Selection' screen to the user even if the Data Dictionary specifies that some parts of the date are to be masked by default. This enables the user to specify the masked portions when selecting dates even if the masked portion will not be displayed on the report. SPEED II also continues to sort by the entire date field stored in the data file regardless of the specifications for Default Mask in the Data Dictionary.

TECH DOCUMENTATION

• Two new Cross Reference Reports have been added to Documentation Management. 'Date/ Non-Date Commands - By Field' and 'Date/Non-Date Commands - By Function'. These reports will search the application for the use of Date fields with Non-Date fields (Constants other than blank, Numbers, Alpha, etc.) in COMMANDS. The report will also list commands which use two Date fields if the fields do not have the same High End and Low End. The report only lists the SET, IF, AND, and OR commands.
• Modified the 'Field to Function - By Field' and 'Field to Function - By Function' reports. The first input function, which allows the designer to enter the fields to be included on the report, now allows you to press PF18 to automatically populate the fields to be included. When PF18 is pressed SPEED II allows the entry of specifications to be used when selecting the fields. The following criteria are allowed: 'Include All Date Fields?' (Y/N/blank), 'All Dates With Year But No Century?' (Y/N/blank), and the ability to specify a phrase which should be part of the field name ('Field Names Containing'). SPEED II allows you to specify the criteria multiple times and will continue to add the qualifying field names to the list of fields to be printed on the cross reference.

FILE MAINTENANCE

FILE MANAGEMENT

• When restructuring a Date field, if the old format had the Year as its High End and the new format has Century as its High End, SPEED II will use the "Date Pivot" logic to determine the Century.

BUG FIXES

COMMANDS

• The DATE BTW command would return erroneous results if one of the two date fields contained the Year, Month, and Day portions (at a minimum) AND the year was an odd number AND the month was 02 (February) AND the day was 28. The second date must have a day value which exceeds 28. For example:

Date1 (CYMD) = 19970228

Date2 (CYMD) = 19961231

DATE BTW Date1 5 Date2 would return -1 instead of -2 (number of months)

This error is present in ALL releases of SPEED II prior to 07.02.02. This correction was first released in 07.02.02. (ECR 4140)

FIELD OVERLAP REPORT

• If a date field included the century and year the Field Overlap Report would indicate that the field overlapped another in certain cases even though the fields were not actually overlapping.

FILES / FIELDS (DESIGN)

• If a field (part of a file or a work field) was type 'D' (domain), and a previously processed field referenced a domain from a different application, and the domain was part of the application being designed, then Process Files and Process Work Fields would report that the domain does not exist. (ECR 4139)

GENERAL CORRECTIONS

• SPEED II was setting the Wang VS Default Printer Number to zero even if there was a different value specified in one or more of the Installation Configuration files. This problem did not cause SPEED II to print to an incorrect printer because SPEED II does not use the default printer number to control the destination of a print file but it did cause the value to be incorrect when a user ran an External Function which needed to obtain the default printer number. This problem has been corrected. SPEED II will now set the Wang VS Default Printer number to the value determined by the various Installation Configuration files which apply to the particular terminal, user, application, etc. in the hierarchy described in the SPEED II documentation. Note that the value is changed after the execution of a Disposition Function and the new value remains in force until another Disposition Function is executed or the job ends. This problem was first corrected in release 07.02.01.

SORT FUNCTIONS (DESIGN)

• If a JOB sorted a file and then executed a JOB as a later step AND that JOB included either an OUTPUT or an UPDATE function which used the same primary window file as was sorted in the calling job the OUTPUT or UPDATE would fail with an error indicating that SPEED II "Cannot Find the Sort Keys". This problem would exist in all SPEED II releases since 07.00.00. This problem has been corrected.

UPGRADING FROM FROM RELEASE 7.0, 7.1, 7.2 TO 7.3

• Release 7.x applications can be converted to Release 7.3 by following the instructions here.

UPGRADING FROM RELEASE 6.X TO 7.3

• Release 6.x applications can be converted to Release 7.3 by following the instructions here.

SPEED II 7.02.00

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)

SPEED II 7.00.00

SPEED II Release 7.0

The SPEED II 7.0 Release Notes summarize the enhancements and other modifications made to SPEED II since the last release and include important information about SPEED II that was unavailable when the documentation went to print. These release notes include:

• What's New in SPEED II 7.0
• Issues Resolved in SPEED II 7.0

_______________________________________________________________________

What's New in SPEED II 7.0?

For SPEED II Designers:

• Enhanced the Data Base Management facility to support domains. A Designer may now define the field type in a Domain record, which may be referenced when defining fields within Files or Work Fields. Domains are similar to SAME AS fields and provide a central depository of data types.
• Modified the Change All References facility to allow multiple sets of changes to be entered before the changes are made. The Designer may batch changes and implement them all together.
• Updated the Query function to allow the use of computed values, which permits the Designer to define how a field is computed and to use that field as part of the Sort/Selection function and the Output function.
• Added the Query Generator function to the Execute Query screen, which allows Queries to be generated more easily.
• Enhanced the Sort function so that sort setup information is now placed into three memory files (MSFN, MSLT, and MSRT) at the end of Sort Setup so it is available for the Designer to print on a report or to use for some other purpose. In addition, the Sort Setup step may now be omitted if the Designer produces the three files prior to executing the Sort step, so that Designers may format their own Sort Setup input functions or obtain the Sort Setup information from sources other than the keyboard.
• Added an Overlapping Fields report to the Documentation menu to search applications for fields which have grown in size and are overlapping other fields on Input or Output windows.
• Added a Find Application Links report to the Documentation menu to search the current application for any references to other applications.
• Enhanced the Startup Job function to allow a Designer to specify a single job to be run at startup. Once this job has completed SPEED II will end. This feature is only available if SPEED II is run from a procedure and can only run a single job. It is accessible from the new GETPARM screen which is only available to procedures. The PRNAME is "OPTION" and the following three parameters are required:
  • COMPANY - 3 alpha characters to indicate a valid company ID
  • APP - 3 alpha characters to indicate a valid application ID
  • JOB - 30 alpha characters to indicate the Job to run. Must be a valid Job in the specified application.

For SPEED II Users:

• Added the following to the Disposition screen:
  • Option to indicate whether 'Comma Delimited Output' is desired .
  • Option to assign the Filename, Library, and/or Volume for the output file.
  • Option to select whether or not the print file should be scratched from the Local system after spooling to a Remote system (requires a Wang VS OS 7.30 or above).
  • Option to assign the File Class for the print file.
  • Option to determine what action SPEED II should take when the output file already exists (i.e.Append, Scratch Old, Make a Unique Name).
• Modified the Comma Delimited Output to produce a consecutive file containing the data which would have printed (with no headings or literals) in a format that may be imported by many PC programs. The output produced is similar to that produced when a WP merge document is requested.

For SPEED II System Administrators:

• Enhanced the Installation Configuration facility so that a site may disable the use of the Special I/O mode. Note: This field should NOT be set to 'N' unless you have the Wang Resource Sharing Facility installed.
• Added several new fields to the Installation Configuration facility to allow the defaulting of the Print File Class and SPOOLSCR parameter.

________________________________________________________________________

Issues Resolved in SPEED II 7.0

For SPEED II Designers:

• Enhanced the Design Transfer facility tosupport"#" characters in the TO filename and to transfer all Query functions.
• Updated the Change All References facility for Query functions to change the commands associated with the Output and Sort functions whose names are being changed.
• Modified the RUN command to reference a Job invoked via the RUN command in the ILF code.
• Enhanced the Field Cross Reference report facility to report references to all fields in a command.

SPEED II 6.01.07

APPLICATION DESIGN

DESIGN TRANSFER

• Design transfer of Query Functions did not transfer the commands associated with the Sort function. This problem has been corrected.

BUGS FIXED

DEBUG CHANGES

• If a DMS Error is detected during the execution of command code SPEED II will now display the address of the file's UFB and the error sub code if available.
  • NOTE: Installations using a Foreign Language must edit the message 'CMND-ERR.DMS-ERROR' adding fields for the UFB and sub code or this new functionality will not work.

DOCUMENTATION CHANGES

• Corrected a problem which caused Technical Documentation to not print if the design files were NOT on the SPEED II volume.

FILE HANDLING CHANGES

• Changed the opening of design files during load module creation to use input mode / shared mode even when running in background and job was submitted from application design. This is to correct a problem where background jobs would have file access problems because they would not attempt to use input mode.

FILE MANAGEMENT

• Corrected a problem in 06.01.03's file creation routines which caused file creation to fail with a 'no entry in file specifications' message if the user's INVOL usage constant did not match the structure volume.

GENERAL CORRECTIONS

• When a function or job was run via the Utilities menu (PF30) results were sometimes different then if the same function or job was run from a menu. We have traced several of these problems to a Wang OS Configuration value being set too low. We recommend that the value for 'Maximum link levels' be set to 18 or higher and 'Maximum PCEXITS' be set to 24 or higher. Both of these values are set in Genedit on the 'Task & VAS Options' screen. If you are running SPEED II from a procedure or another program (such as OFFICE) you may need to set these values even higher. SPEED II is unable to report the error because it needs to link to another program to display the error screen and it can't link because the maximum number of link levels has been reached. Another symptom of this would be the inability to RUN a function from within a function if the original function was run via PF30.
• If a function included a 'SELECT COMPANY' command and the new company used a different volume, 'CREATE' commands would fail. This has been corrected.
• Corrected a problem with the opening of files in background which was causing file in use and file possession conflicts with design files when jobs were run in background while users were running in foreground.

INPUT FUNCTIONS (DESIGN)

• Corrected a problem with the 'Create Input Functions' program. When a non-text field was being placed on an input window the size of the box (rows and columns) was not being set to zero. This would cause the item to export to APPX incorrectly unless the window had been edited at least one time.

INPUT FUNCTIONS (USER)

• If a user pressed PF32 during SCAN the PF Key Intercept commands would be executed even though they shouldn't have been executed. Also, if the user was on the 'Select Access Path' screen during SCAN and pressed PF32 the input function would cancel. Now PF32 during any phase of SCAN will return the user to the calling input function and beep the terminal alarm. The user will then be able to continue or press PF32 again to perform normal PF32 processing including the execution of PF Key Intercept commands.
• If the user ended out of SCAN with a PF16 or PF32, screens which were presented next (next window or previous window if PF4 was also pressed) would not execute command code properly. This would cause Default Values to not be set and displayed and display of screens without the user variable data under certain circumstances. This has been changed so the commands are now executed as designed and the data is properly displayed.
• Corrected a problem in input functions which resulted in the data from FIND (PF1) not being displayed if the user pressed SCAN (PF2) in error prior to the FIND (PF1).

SPECIAL UTILITIES

• If a designer ran a function using one of the 'Run Program or Function' selections and that function ran a job in the same application (using the RUN verb) the run of the job would fail UNLESS the first function was run from a job. Note that the same function could be run from a menu without problems. This has been corrected.

SPEED II 6.01.04

BUG FIXES

DEBUG CHANGES

• If a DMS Error is detected during the execution of command code SPEED II will now display the address of the file's UFB and the error sub code if available.
  • NOTE: Installations using a Foreign Language must edit the message 'CMND-ERR.DMS-ERROR' adding fields for the UFB and sub code or this new functionality will not work.

FILE MANAGEMENT

• Corrected a problem in 06.01.03's file creation routines which caused file creation to fail with a 'no entry in file specifications' message if the user's INVOL usage constant did not match the structure volume.

GENERAL CORRECTIONS

• If a function included a 'SELECT COMPANY' command and the new company used a different volume, 'CREATE' commands would fail. This has been corrected.
• Corrected a problem with the opening of files in background which was causing file in use and file possession conflicts with design files when jobs were run in background while users were running in foreground.

INPUT FUNCTIONS (DESIGN)

• Corrected a problem with the 'Create Input Functions' program. When a non-text field was being placed on an input window the size of the box (rows and columns) was not being set to zero. This would cause the item to export to APPX incorrectly unless the window had been edited at least one time.

SPEED II 6.01.03

BUG FIXES

DEBUG CHANGES

• If a DMS Error is detected during the execution of command code SPEED II will now display the address of the file's UFB and the error sub code if available .
  • NOTE: Installations using a Foreign Language must edit the message 'CMND-ERR.DMS-ERROR' adding fields for the UFB and sub code or this new functionality will not work.

GENERAL CORRECTIONS

• If a function included a 'SELECT COMPANY' command and the new company used a different volume, 'CREATE' commands would fail. This has been corrected.
• Corrected a problem with the opening of files in background which was causing file in use and file possession conflicts with design files when jobs were run in background while users were running in foreground.

INPUT FUNCTIONS (DESIGN)

• Corrected a problem with the 'Create Input Functions' program. When a non-text field was being placed on an input window the size of the box (rows and columns) was not being set to zero. This would cause the item to export to APPX incorrectly unless the window had been edited at least one time.

SPEED II 6.01.02

APPLICATION DESIGN

COMMANDS

• Added two new options to the RUN command . 'INTERNAL / WS' causes the function processor to leave the workstation open when passing control to the internal function. 'INTERNAL NO PRE / WS' does the same thing except that there is no preopen information passed to the internal routine. The parameter list passed has been modified to add a new parameter to the parameter list. This parameter is the last parameter to be passed and is the address of the workstation's UFB. It is only passed for these new RUN options.
  • Note that if the internal routine READs the Workstation typeahead which was intended for SPEED II would be received by the internal routine and there would be no way to send those characters to SPEED II. If the function is being run in background the UFB address will be passed but the workstation will not be open. The internal routine should check whether or not the workstation is open prior to attempting I/O. (Bit 7 of byte 43 (UFBF1OPEN) in the UFB will be set if open, cleared if closed)

OUTPUT FUNCTIONS (USER)

• SPEED II will now extract the Wang OS usage constant 'SPOOLSCR' and use it when spooling output to a remote system via WSN. If the function producing the output is run in foreground (interactive mode), SPEED II will use the value in this field as of the time the report is sent to the operating system for transfer to the remote system (after PF16 is pressed if the report was displayed on the screen or at the end of the report function). If the function producing the output is run in background, SPEED II will use the value in this field as of the time the user presses PF1 to submit it to background. It does not check the value in effect at the time the procedure is released from the procedure queue if it was placed on hold. This value can be set using Wang Procedure language during the execution of SPEED II by running a Procedure as an EXTERNAL function.

BUG FIXES

APPLICATION DESIGN

• If SPEED II was installed on a CPU running a release 6 version of the VS OS SPEED II would 'loose' the application id when returning to application design from test mode.
• The input functions used to create menus, jobs, input functions, output functions, update functions, status functions, sort functions, disposition functions, and command libraries have all been modified to prevent advancing past the first screen onto continuation windows or command series if adding a record whose key value already exists.
• Modified Files/ Fields and Work fields entry so that if a record is changed to a sequence number or name that already exists, the correct error message is displayed.

CHANGE ALL REFERENCES

• When running 'Change All References' for 'Security Classes' a file status 80 is produced if a field level security class needs to be changed.
• All of the 'Change All References' programs now update the 'Changed By' field in modified files/fields/functions. They also update the Applications file in Installation Information to reflect the date and time of the change so that load modules are recreated properly.
• Change All References for 'Security Classes' did not update execute security classes for any of the function types (Input, Output, etc). It now will update the security classes in all R6 design files.

DISPOSITION FUNCTIONS (USER)

• If a job contains a disposition function which specifies that print output should be displayed on the screen and transferred to WP and the user presses PF31 (print screen) while the report is displayed, the screen is copied to WP (instead of being sent to a printer) and then COPYWP presents a Getparm screen to the user. The user cannot end COPYWP successfully.
• Requesting that report output be transferred to WP or WPPLUS caused a Getparm screen to be presented by the COPYWP or COPYPLUS programs and the user could not exit COPYWP or COPYPLUS successfully.

FILE HANDLING CHANGES

• If SPEED II was installed on a VS with OS 7.21.03 a problem with the OS caused SPEED II to not be able to open a file in Shared mode once a file had been opened in Special/IO or Special/Input mode if it was necessary in the same execution of a function. This problem would most commonly occur if a sort was being performed on a file and 'Use to Limit Reads' was being used on an Alternate Index.

GENERAL CORRECTIONS

• If a user was defined with a startup job and the first step in that job executed a 'RUN EXPLAIN' command the status line (bottom of screen with date/time, etc.) would be corrupted once the explain text had been displayed.

INPUT FUNCTIONS (DESIGN)

• If an input function contained a CREATE command within Access/Verify the hold on the window record would be lost if the function was a single-level function and a File Status 86 would occur if the function was a multi-level function. Beginning with Release 06.00.00 of SPEED II, the CREATE command required that the user have 'WRITE' access to the System Directory file (00001100 in $$$$$011). This is no longer a requirement. The user must have 'READ' access to the System Directory file. Application Designers and File Managers must have 'WRITE' access to this file (and to all of the Installation Control files).
• Numeric Overflow occurred if attempting to access commands within very large window numbers ( >99999 ) in Input functions. Problem corrected.
• If an input function was selected to be edited from a find key listing, the pre 06.01.00 version of the input function editor was run rather than the new version. This has been corrected.
• Corrected problem with display of status line message for continuation windows greater than 3 in the Input Function editor.

INPUT FUNCTIONS (USER)

• If a user makes a change on an input screen, then presses PF2 (SCAN) and either of the following two conditions occur, SPEED II would not verify the data which had been entered. Consequently, invalid data could be entered into the file. Conditions: 1) the user subsequently cancels the SCAN, or 2) the cursor was NOT on a scannable field.

SORT FUNCTIONS (USER)

• If a field was specified as 'Lower Case Ok, Default to Upper' the user was not able to enter lower case characters during sort setup. Sort setup has been modified to allow lower case characters for this type of field.
• The Sort Processor was performing a FREEALL between each record being sorted even if no REWRITES or DELETES existed within the function. The Sort Processor has been modified to detect when no file updates exist and skip the FREEALL. This will increase the Sort Processor's performance in cases where the FREEALL is not executed.

SPECIAL UTILITIES

• The CALCULATOR utility would display a warning message regarding data loss upon pressing PF32. Problem corrected.

UPDATE FUNCTIONS (DESIGN)

• A File Status 95 occurred if a window number was changed. This has been fixed.

SPEED II 6.01.01

BUG FIXES

MENU CHANGES

• One too many '*' on heading of Special utilities menu .

MENUS (USER)

• No Priority needed for type query, but was requiring it. Corrected.

QUERY FUNCTIONS (USER)

• If a query was defined as a menu item, then upon invoking it, it would not run and the user would just the message 'File Cleanup in Progress'. This has been corrected.

SPEED II 6.00.00

SPEED II INTERNALS

FILE HANDLING CHANGES

• The restructure code has been modified to perform better . For many restructures that do not involve a change to the primary key, restructure now opens the output file in output mode rather than I/O, improving performance.

PERFORMANCE TUNING

• The function processor program 00030001 has been replaced by four function processors, 00031001, 00032001, 00033001, and 00034001 Each of these programs may be assigned the same or different operating system priorities. The purpose of multiple function processors is to allow the system administrator to assign different job steps and menu item selections to different processors, so that, for example, selected input functions would always have a higher execution priority than large reports. The execution priority that is assigned when a menu item is defined or when a job step is defined maps to the digit after the 3 in the program name; thus if the input function CUSTOMERS is assigned an execution priority 2, that function will be executed by 00032001, which may be assigned the same or a different operating system priority as the other function processor programs. The four processor programs are shipped with NO priority set, and so it is not the case that 00032001 will execute at a higher priority than 00034001, unless set up that way by the system administrator.

SORT FUNCTIONS (USER)

• Sort functions have been modifed to perform better. If there is sufficient information available, only a limited number of records will be read from the file to be sorted, rather than the entire file. This means that if a primary key limiting the range, or even just the first part of a multi-part primary key limiting the range, is available, then just those records will be read. This also applies to alternate indicies (but should be used with caution).Sort now processes 2048 records per pass (based upon segment 2 space) instead of 256 This modification alone improves sort times by 20%.

INSTALLATION CONFIGURATION

INPUT FUNCTIONS (USER)

• The last design change date and time now appears on the screen in the applications file in installation control.

MENU CHANGES

• The menu structure has changed so that under the main menu there are now 3 sub menus This was done so that the lists and the input functions for the files could be on the same screen and to allow for the added modules in Security Management.
• All the menus now say 'Press RETURN to Exit' instead of ENTER or PF 16. This change has been made all the way through SPEED II menus and messages.

NEW / CHANGED FIELDS

• 'Convert Alpha' has been added to Installation Control. If Alpha and Text fields should be converted during sort using the translation table in the SPEED II language file enter 'Y'. Entering 'Y' will cause sorts to be slower when alpha and/or text fields are included in the sort order. The purpose of the conversion is so that upper/lower case fields sort as follows: 'AaBbCcDd...Zz' etc. If this field is set to 'N' the sort will be using the standard ASCII collating sequence which results in the following sort order: 'ABCDE...Zabcdef...z'.
• 'Blink Error Messages' has been added to Installation Control. A 'Y' will make ERROR messages blink when displayed.
• 'Blink Warning Messages' has been added to Installation control. A 'Y' will make WARNING messages blink when displayed.
• In the Installation Control file the system defaults for printing of mod logs and error logs used to be combined. Another set of print mode, class, form number, printer, no of copies, and disposition has been added and now mod logs and error logs can be controlled separately. Every place in the installation files where error log and mod log defaults occur they have been separated.
• 'Default Work Volume' has been added to the installation control record to use as a default for work files. If this field is left blank SPEED II will automatically assign work files using the user's system defaults as they existed when the user executed SPEED II unless the 'Use All Eligible Work Volumes?' question is 'Y' in which case the value entered in this field is ignored.
• 'Use all Eligible Work Volumes' has been added to the installation control record If 'Y', SPEED II will automatically use all eligible volumes for work files.
• 'Make VS SSA Speed II SSA' has been added to Installation Control. If 'Y', SPEED II will grant SPEED II SSA rights to VS SSA's automatically, and the value in SPEED II Security Administrator will be ignored for any user with VS SSA status. If this field is 'N' the value in the SPEED II user file will be used.
• 'Help Key OK?' has been added to Installation Control. If 'Y', the HELP key will be enabled for users while running SPEED II. If this field is 'N' the user will not have HELP even if their VS logon allows them to have HELP.
• 'Use all Spool Volumes?' has been added to Installation Control. If 'Y', SPEED II will automatically place print files on different volumes which are eligible for spooling when space does not exist on the user's default volume.
• Added by, date added, changed by, and date changed has been added to most installation configuration files.
• 'Help Key OK?' has been added to the company file, as well as the print defaults for the error logs.
• 'Help Key OK?' has been added to the Company/Applications file, as well as the print defaults for the error logs.
• 'Help Key OK?' has been added to the Users file, as well as the print defaults for the error logs.
• The print defaults for the error logs has been added to the Terminal file.
• In the forms file, FF before and FF after can now both be set to 'N'.
• The version portion of the application id in the applications file in installation control has been made an alternate index to find all applications of the same version.

NEW FILES

• A Printers file has been added so that different printers can be referenced from disposition functions. The file also allows the definition of printers on other nodes of a WSN network. Access to the file is thru the Installation Control menu. Disposition functions now allow PF2 (FIND KEY) on the printer field, and if the system has WSN, on the SPOOLSYS field. Both of these fields use the Printers file to do the FIND KEY.
• A System Directory File has been added. This file contains copies of structure files for an application, and is automatically updated every time a file is changed. Only one system directory file may exist per CPU. Use of the system directory file will speed up system performance by reducing the number of files that need to be opened during function loading. A new function has been added to Data File Management to update this file. This function should be used during the conversion process as documented in the release instructions. After the System Directory has been loaded, SPEED II automatically keeps it current as design and / or location changes are made to files To create the System Directory use the Installation File Management functions to set up the file for the correct number of records and create the file. The formula for the number of records is: Number of applications * Average Number of files per application * (Number of companies + 1) + 100. Detailed instructions are in the the upgrade release 5 to 6 document that accompanies the release media.
• Find Key now functions from the Users file input function for cancel menu, startup job, and startup menu. The function also validates the user's access to the startup job, menu, and cancel menu, and displays a warning if the user has been assigned a configuration that their security group cannot access.
• Security Management has been enhanced.
  • Security by Example, a choice from the Security Management Menu allows the user to manage installation security thru utilities the erase, renumber, and assign access to applications for security groups by presenting menus and enabling or disabling choices on the menus.
  • Several new security reports have been added that detail what access to application items the security groups have. These reports do not require that the security by example programs be run, but do require the files for the security by example module.
  • Manage Application Security, a choice from the Security management menu, is a module that contains input functions and lists for maintaining the security classes in an application.

APPLICATION DESIGN

FILES / FIELDS (DESIGN)

• In entering a data dictionary, if the designer is in add mode, then the first portion of the field name defaults to the file name (if the default value in the application information record has been set to 'Y'), and the cursor is positioned after that for typing in the rest of the field name. On the first screen of data dictionary entry, there is a field that can be set to override the value in application information record, for those cases when the first portion of the field name is not the same as the file name. This was done to promote the standard of field names beginning with the file name, as well as for convenience to designers.
• The data type of Field Names has been changed to allow special characters; field names may now include punctuation marks, etc. When fields with special characters are converted to lanuages not allowing special characters, the special characters are converted to hyphens.
• When generating copy libraries, the PR-NAME has been changed to the file name instead of SPEEDII.
• In entering a data dictionary, the file name, sequence number, and field name now displays on the second screen of field entry and in documentation entry.
• In maintaining files / fields, the files may now be accessed in file category order.
• In entering or modifying a data dictionary, SPEED II now keeps track of the files that have been added or modified. When the process data dictionary screen is presented, the files added or modified will be filled in on the screen by SPEED II If more than twenty files have been added or modified, then all the files are blanked out, the process dictionary is set to 'y', and a message is displayed that indicates that more than twenty files were affected, and so the entire data dictionary should be processed.
• The autoaccess field name is defaulted from the data dictionary if the field painted on the window is defined as 'SAME AS' another field and the autoaccess information is entered in the data dictionary Box columns and rows are defaulted from the data dictionary for text fields.

INTERFACE TO OTHER SYSTEMS

• 'Run Selected Program' has been changed to 'Run Program or Function'. This used to allow the designer to run things like DISPLAY from within SPEED II That screen now allows the designer to run anything - jobs, menus, functions etc., without having to put the items on a menu. This should be particularly useful in testing new functions and for running one time updates etc. (We all know how functions would get added to menus to be run once, never get removed, and then were run later by accident). The designer may select to run the item with or without traps active. This program is also accessible from PF 30 directly while in application design, so you don't have to exit to a menu to run this function.

JOBS FUNCTIONS (DESIGN)

• The jobs steps screen has been changed so that the function priority is entered when the job steps are entered and has been reformatted so that more job steps show up at a time on the scrolling window.

MENU CHANGES

• The application design main menu has been reorganized Data Base Management menu has been created, that contains functions for files/fields, work fields, process dictionary, and data file management. Function Management menu has been created, that contains input functions for menus, jobs, all function types, and command libraries. Consolidated Design menu has been created, that contains access to just about everything a designer needs on one menu. Every other menu in application design has also been reorganized, but some changes have been minor.
• 'Select Application', which is PF 1 from the main application design menu has been added to all application design menus, so that at any level of menu within application design, the current application being designed can be changed.

MENUS (DESIGN)

• The menu items definiton that is performed when an item is defined for a window has been changed so that the item execution priority is set when the menu item is defined.

NEW / CHANGED COMMANDS

• New RELATIONS have been added for use in record selection in sort functions. The new relations are: BW-Beginning With, valid only for alpha or text, EX-Excluded if characters found in string (opposite of IN), BL-Blank, and NB-not blank. BL and NB are true boolean operators, and were added so that if the user wants to find all records where, for example, the customer name is blank, the constant portion of the selection information doesn't have to be underlined. BL and NB also can be used for date and numeric type fields.
• The SELECT command has been changed to allow also select of a file, library, volume, and the number of records to be used in creating a file. SELECT can now force a close of a file.
• The RUN command has been enhanced to allow a type RUN INTERNAL. Run internal allows a module of code to be staticly linked into SPEED II. The module number must be from 01 to 19. RUN INTERNAL is a separately licensed feature.

NEW / CHANGED FIELDS

• 'Automatic Added By' default values have been added to the application information record This field is a Y/N field that controls whether or not the 'Automatic Added By' field in the FILES file is set to a 'y' or 'n'. The field in the FILES file controls whether the added by field is to be automatically added to the file when the data dictionary is processed.
• 'Automatic Changed By' default value has been added to the application information record This field is a Y/N field that controls whether or not the 'Automatic Changed By' field in the FILES file is defaults to a 'y' or 'n'. The field in the FILES file controls whether the changed by field is to be automatically added to the file when the data dictionary is processed.
• 'Automatic Date Changed Hi Value' default value has been added to the application information record This field is a Y/N field that controls whether or not the 'Automatic Date Changed Hi Value' field in the FILES file is defaulted to 'y' or 'n'. The field in the FILES file controls whether the date changed field is to be automatically added to the file when the data dictionary is processed.
• 'Automatic Date Added Hi Value' default value has been added to the application information record This field is the default value for the high end of the date for date added fields and defaults the 'Automatic Date Added Hi Value' in the FILES file. The field in the FILES file controls the high end of the date added field automatically added to the file when the data dictionary is processed. If the field is set to spaces, then no date field will be created. The values in this file may be overridden when entering a specific data dictionary.
• 'Automatic Date Changed Low Value' default value has been added to the application information record This field is the default value for the low end of the date for date changed fields and defaults the 'Automatic Date Changed Low Value' in the FILES file. The field in the FILES file controls the low end of the date changed field automatically added to the file when the data dictionary is processed. If the field is set to spaces, then no date field will be created. The values in this file may be overridden when entering a specific data dictionary.
• 'Automatic Date Added Low Value' default value has been added to the application information record This field is the default value for the low end of the date for date added fields and defaults the 'Automatic Date Added Low Value' in the FILES file. The field in the FILES file controls the low end of the date added field automatically added to the file when the data dictionary is processed. If the field is set to spaces, then no date field will be created. The values in this file may be overridden when entering a specific data dictionary.
• 'Warn Data Loss' default value has been added to the application information record This field is a Y/N field that controls whether or not the 'Warn Data Loss' field in the input function file is set to a 'y' or 'n'. The field in the input function record controls whether the user is to be warned if they press a key that will result in losing data they have entered or changed. This value can be overridden in the input function definintion.
• 'Default First Portion of Field Name to File Name in Sort Function Entry?' has been added to the application information record This field is a Y/N field that controls whether or not the first portion of the field name is defaulted to the file name in entering sort levels and record selection records in sort functions. The value can be overridden on the first screen of sort function entry.
• 'Default First Portion of Field Name to File Name in Data Dictionary Entry?' been added to the application information record This field is a Y/N field that controls whether or not the first portion of the field name is defaulted to the file name in entering fields. The value can be overridden on the first screen of data dictionary entry.
• Added By, Changed By, Date Added, and Date Changed have been added to most files in application design.
• The Jobs Documentation field size has been increased to 1027 bytes.
• In the FILES file (00000500) automatic added by and changed by and automatic date added and date changed fields have been added. These fields enable the designer to add these fields to a file by filling in only 6 fields on one screen instead of having to add the fields manually. The fields are added when the file is processed, and all the appropriate descriptive headings and column headings are created for the fields. Once these fields have been created, then the data in the FILES file is ignored.
• In the FILES file (00000500) 'Alt Index Packing Density' has been added. If the installation is licensed for OVEREASY this field is used to set the alternate index packing density when reorganizing alternate indexed files with the OVEREASY utility.
• In the FILES file (00000500) 'Reorg Allocation for Growth' has been added. If the system has OVEREASY licensed the value in this field will be used to indicate what percentage of growth to allow for during file reorganizations with the OVEREASY utility.
• In the FIELDS file (00000600) default box rows and columns have been added for type text fields for input and output function defaults. These fields are set in the data dictionary, and then when the field is defined in an input or output window, the box columns and rows are defaulted from the data dictionary values. The values may be overridden. These fields were added because when adding a field to a window, one doesn't know the size of the text field, and it makes defining the correct sizes for box columns and rows more tedious.
• In the FIELDS file (00000600) Autoaccess Application and Field have been added for type 'SAME AS' fields. The autoaccess application and field may be entered in the data dictionary for fields which the designer would enter an autoaccess field in an input or output function. For example, in the BALANCE2 record, the field 'BALANCE2 FULL' is defined as 'SAME AS' BALANCE1 FULL. If BALANCE1 FULL is entered as the autoaccess field, then in input and output function window painting, when BALANCE2 FULL is defined on the window, BALANCE1 FULL will automatically be entered in the autoaccess information.
• In the FIELDS file (00000600) 'Lower Case OK?' has been changed from a Y/N field to a field that allows 3 values: 0-Upper only, 1-Lower ok, and 2-Lower case ok - default to Upper case. If a field is set to type 2, then when a user is entering data, if lower case is desired, then by pressing PF 15 (Set Item Attributes), lower case entry can be allowed by setting a new field on that screen. Type 1 also allows PF 15 to change the input to upper case only.
• In the INPUT Function File (00100100) the field 'Warn Prior to Data Loss' has been added. The default value for this field is obtained from the application information record, but can be overridden. This feature used to be in an earlier release of SPEED II, but there were many complaints about it, and so it was removed. However, others liked the feature, particularly for novice users, and so now the feature can be controlled by the designer.
• In the UPDATE Windows File (00300200) a documentation field has been added (1264 bytes) for detailing what processing occurs in each window. This was added per request so that all the documentation would not have to be embedded in the command code.
• In the Menu Items File (00000200) 'Execute Priority' has been added. The execute priority controls which of the four function processor programs is to be used to run the function/job.
• In the Job Steps file (00000400) 'Execute Priority' has been added. The execute priority controls which of the four function processor programs is to be used in running the job step.
• In the Sort Function Record Selection file (00600300) a new field 'Use to limit reads?' has been added. This new field is for those cases when record selection is based upon an alternate index, and the designer wants the alternate index path to be used to select the records from the file. If a file has an alternate index, such as CUSTOMER ALPHA, then that alternate index path will be used to select records if this new field is flagged 'Y'. This can speed up record selection significantly, since it will avoid reading every record in the file. However, this must be used with discretion, since if an alternate index path has very few unique values and thus many duplicates, the overhead of reading along the alt index path can cause the report to take longer that it would have just by reading every record.
• In the Sort Function Record Selection file (00600300) three new fields 'Find Data Application', 'Find Data Field Name', and 'Find Data Occurrence' have been added These fields work in conjunction with the added PF 2 functionality for record selection at run time. Note: A utility has been added to the utilities menu to load these fields automatically for existing applications, if desired. The data loaded into the constant portion does not have to be a key - it can be any portion of a record accessed through PF 2.
• In Disposition Functions (00700100) several new fields have been added:
• 1) Foreground Security - This is a security class that can be entered for type 3 disposition functions (run in background or foreground) so that users with access to the class can run the job in foreground, while otherwise it can only be run in background
• 2) Spool System - This field was added to route printouts to other printers on different nodes of a WSN network. PF2 from this field accesses the new printers file. (Editable)
• 3) Use Tabs - This field was added to better format output that is to be converted to a WP document. (Editable)
• 4) WP+ library name has been expanded to 8 characters.
• In Commands File (00000800) Date added, date changed, added by, and changed by have been added and are accessible for display through the special functions PF KEY 1 during command entry.

NEW DESIGN CAPABILITES

• The Speed II language utility is now included in releases. This utility will allow the designer to further customize SPEED II for specific installations.
• From the Special Utilites Menu a new option, 'Turn TRAPS On or Off' is now available The designer can select specific functions, all functions of one type, or all functions in an application. Traps that exist are converted to comments; the true/false flags are preserved, and the comment is non-modifiable so that the comment may later be identified to be restored into a TRAP.
• 'Load Find Data Names' is now available from the Special Utilites Menu. This utility will load in the find data field name into the record selection records based upon criteria that uses 'SAME AS' definitions and field types to determine how to set the find data field name. This was added so that PF 2 from record selection screen is available without having to manually modify every sort function definition. After this utility is run, technical documentation for sort functions should be run to check the Find Data field names that were filled in by the utility. Some of them will need to be edited.
• From the Design Transfer menu, design transfer of fields and files have been separated into two different programs so that the designer does not have to type in 'FILE' or 'FIELD' according to the type of transfer desired. The design transfer of files now brings up an additional screen that defaults the first portion of the field name in the new file to be created to the new file name, rather than using the prior logic of appending an A, B, C, to the end of the field name.
• From the Change All References Menu, the change of fields and files have been separated into two different programs so that the designer does not have to type in 'FILE' or 'FIELD' according to the type of change desired.

OUTPUT FUNCTIONS (DESIGN)

• The autoaccess field name is defaulted from the data dictionary if the field painted on the window is defined as 'SAME AS' another field and the autoaccess information is entered in the data dictionary Box columns and rows are defaulted from the data dictionary for text fields.

PF KEY CHANGES

• Window Formatting PF Keys have been changed. Left and Right 5 (PF Keys 19 and 22) have been removed as options PF 19 and 22 are now Left 1 and Right 1 PF 20 is now Special Characters (Underline), and PF 5 is now Center in *, which will center text on a window and put asterics to either side (to be used for window headings.) PF 30 accesses the menu from which calculator, calendar, and Run program or function can be run.
• Search and replace has been changed to PF 15 from PF 16 in the command editor. If the search string is blank, then search and replace mode ends rather than attempting to search for blanks.

SCREEN CHANGES (MISC)

• During command edit, if the designer is in inquire mode, then the bottom of the screen displays only the PF key selections that are valid.

SORT FUNCTIONS (DESIGN)

• In defining a sort function, the sort level window has been changed so that now it is a scrolling window allowing multiple records per screen. The application id and first portion of the field name are defaulted to the file to be sorted in add mode according to the default value in the application information record (but can be overridden on the first screen of sort functions.) The relations are defaulted to GE and LE and from that point those fields are saved as the default values for the next record. The application id and first portion of the field name are also defaulted adding record selection records.

FILE MANAGEMENT

INTERFACE TO OTHER SYSTEMS

• If the installation is licensed for OVEREASY, then the reorganiztion of files through SPEED II will use OVEREASY rather than the WANG copy program. The growth %, and the alternate index packing density %, which can now be set in the data dictionary, are passed to OVEREASY to use during the reorganization of the files. The interface to OVEREASY is a separately licensed feature.

SCREEN CHANGES (MISC)

• In all file management screens, when you select 'Enter/Edit File Specifications', the actual disk file name now appears on the screen instead of just the descriptive file name. This was done to correct the ambiguity caused when design transfer was used to create a new data dictionary for a file, and the new file's descriptive name never was changed.
• In selecting specific files, Speed II used to sort the files by file category, which in most cases only made it more difficult to find the files you wanted. It now sorts the files only by file name.

USER INTERFACE

DISPOSITION FUNCTIONS (USER)

• Find key is now available for access to the spool system, the printer number, and the form number. The information about the spool system only appears on the screen if WSN is active.

INPUT FUNCTIONS (USER)

• Inquire mode in input functions no longer performs a read with hold.

INTERFACE TO OTHER SYSTEMS

• PF 30 now displays a menu that allows access to the Calculator program and the Calendar program for use by users.

PF KEY CHANGES

• PF Key 1 from Find Record or Find Key used to be the cancel key, and PF 16 used to end the user all the way out of the function back to a menu. PF 16 is now the cancel key, and it only returns the user to the previous level, not all the way out. PF key 1 is not used for cancel from Find Record or Find Key.
• PF Key 17 is now the key to be used to actually delete a record rather than PF 1. PF 5 has been added to the Delete mode options message.
• The HELP key may now be disabled for specific users, companys, etc. See INSTALLATION CONFIGURATION changes.
• Set Item Attributes now allows the user to allow lower case entry for those fields that are text and defined by the designer as type 2-Default to Upper case, Lower case OK. The user may also set type 1-Lower Case ok to upper case entry through PF 15.

SCREEN CHANGES (MISC)

• The Status line at the bottom of the screen has been changed to display the workstation number, and if the CPU is one node on a WSN network, then to also display the current node id. In input functions, the status line displays the current spoolsys id.
• Whenever a new load module is being created, a message now displays at the bottom of the screen: 'Creating Load Module'.

SORT FUNCTIONS (USER)

• PF 2 now functions for record selecton options that have been defined as allowing the user to enter/modify a constant at run time. The designer must enter the Find Data field to be accessed by the PF 2 in the record selection design entry (or use the program on the utility menu to load them). The data selected into the constant area does not need to be a key, and does not need to be on the screen when the PF2 generated list of records is displayed.
• In sort setup and record selection, only the active PF key choices are displayed at the bottom of the screen.

BUG FIXES

DEBUG CHANGES

• While running the SPEED II debugger, a designer can now edit two different occurrences of a field in edit mode if fields are on same command line (e.g., SET CAR CUSTOMER ADDRESS 001 = CAR CUSTOMER ADDRESS 002.)
• When a job is submitted to run in background, it is now submitted with DUMP=Y.

DOCUMENTATION CHANGES

• Technical Documentation - If there are two applications and both applications have a file name that is the same, then if cross reference of file names is run within one application for the file name in the other application, then all the cases in which the file name is reference in either application would print out on the report. This has been corrected.
• User documentation has been fixed so that the documentation screens print out correctly. (Documentation that had been carefully entered into columns on the screen would print out completely reformatted with all the columnar formatting gone.)

FILE HANDLING CHANGES

• Problem corrected where SPEED II would sometimes not recognize an END AT condition being met and would continue reading to the end of the file. The problem was due to security access to the records within the loop not being met.
• Problems reported with regorganizing installation control files have been corrected.
• Design File restructure for versions of applications other than 00 has been corrected.

INPUT FUNCTIONS (USER)

• If a user changed from inquire to add mode after a full screen of records had been displayed in a scrolling input function, the last record that had been displayed was not cleared out of the record buffer and was displayed when the user went into add mode. This has been corrected.

OUTPUT FUNCTIONS (DESIGN)

• In output functions the 1st page number would get overridden if the first page had not yet been printed. This has been corrected so that multiple reports can be set up for continuous sequential pagination.

OUTPUT FUNCTIONS (USER)

• For output functions that generate more than one file, if the output was to be displayed, then SPEED II would display the last print file rather than the first, even though the screen would say that the first was displayed. This has bee, n corrected. If the output was to be spooled to hardcopy as well as display, and the user selected to not print the output, the first print files had already been spooled to a printer. This has been corrected.
• A problem existed with inquiry functions that produced a single page output. A page break would display on the screen just prior to the last line of print if either form 000 was not defined or was defined but had form feed before set to 'N' and form feed after set to 'Y'. This has been corrected.

QUERY FUNCTIONS (DESIGN)

• Design transfer and change all references of query functions has been fixed.
• A problem existed in editing a existing query if the output function associated with the query had been deleted. The function that allows modification of queries has been modified so that if the sort function or the output function for the query does not exist in change mode, the records are added.
• A problem existed in editing an existing query if the file to be queried was changed: the sort function would reference the original file, and then the sort function would not execute because the file to be sorted did not match the file in the query record This has been modified so that if a query is modified, the file to be queried cannot be changed.

SCREEN CHANGES (MISC)

• If a user had a startup job defined and the startup job ran a status function that did not have an in progress message, then a garbled version of the registration information screen would be displayed when the status function ran. This problem has been corrected, and for release 5 versions of SPEED II, putting an in progress message in the status function will also correct the problem.