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.