Version
11.61 through 11.95 for the VAX
ACCENT R Utilities
Certain variables were not being initialized during file name analysis. This resulted in a memory access error that has been fixed in this version.
The ENTER IF clause used in a DOMAIN definition in multiple DOMAIN index definitions during node splits caused a memory access violation.
Computed fields defined in Global Storage that referenced other computed fields would sometimes result in a memory access violation.
The CATALOG command was displaying any item created or changed in the last 24 hours if TODAY was specified. This was fixed to only display items created or changed today.
This version contains several fixes to correct the record size reported by OpenVMS. ACCENT R was not reporting the correct record size when closing a file.
ACCENT R was setting @AUX to "MISSI" when it should have been set to "BUSY" when a MATCH BY clause was used and another user had the record locked.
Under certain circumstances the SORT command was causing all records of a data set to contain the data of the first record in the Data Set.
When a PM was being executed as part of the SORT command, the wrong record was made available in the FINAL Section. This has been fixed.
ACCENT R was changed to assign more than a single record area buffer when the record size was a multiple of the OpenVMS disk block size. This will significantly speed up the processing of these records.
Removed the operating system�s version validation if running an ACCENT R demonstration version.
User Based License control has been changed to check for the condition of a user already being listed in the user list before adding the user to the list. ACCENT R first attempts to delete the user and then executes the add operation. The user name, PID, and SID are checked. This will allow a user to come back into ACCENT R if the exit was abnormal (such as in the case of a stack dump, memory access violation or a control Y exit).
User Based License control has also been changed to remove the user from the list if a LINK command or statement is executed. Please note that this makes it possible for a user to lose the ability to return to ACCENT R from a LINK AND RETURN operation if there are no open positions in the list.
CHECK_USERS will now only remove users based on the SID of the CPU on which the program is executing.
A new system field has been added to give more information to the user when @WARNINGS is set. The warning message that is produced is also stored in the new system field called @WARNING.MESSAGE.
A new system field called @AUX.MESSAGE has been added which is set to the message normally produced at the time @AUX gets set.
The bug was fixed which caused the EDIT command to stack dump when using the external editor and the user tried to save the DBL object being edited. This usually only happened when the user returned to the editor after discovering errors from a SAVE command.
A system field called @TESTX2 has been added to provide special testing of a critical simultaneous update problem. It appears that OpenVMS, under some special conditions, is allowing user access to a data block before the user, which has it locked, has freed it. ACCENT R tries to detect this when this has happened by looking at the record area just in front of the one being created. ACCENT R will set @AUX to "OWRRB" or "OWRAB" if the last four characters have nulls. This is the main buffer or special buffer being written. The record is not CREATEd so the user can try again. To use this test you must be sure that the last four characters of your record will not be null. To invoke this checking you must set "200" to the system field @TESTX2 in the PM just before the CREATE statement and check after the CREATE for these special values. When the condition is discovered, action must be taken to try to CREATE the record again and report the error. After the CREATE, set @TESTX2 to "0" else ACCENT R will check for this conditional on all CREATE statements. Again, you must make sure that the data record cannot normally have 4 nulls at the end of the record.
Changed CHECK_USERS and SHOW_USERS so more information is printed including the PID and SID for users logged on and logged off.
This version requires the users to flatten and rebuild all their DBL�s. This was necessary to increase the number of Data Sets that can be related in a PM from 30 to 100.
After the EDT closes, the @TERM.LINE is set to the maximum line length for the file.
ACCENT R will not rename an SF file when the DBL READ ONLY is enabled. This has been corrected so ACCENT R will rename the file if it exists and reports it if it does not exist.
We have fixed several problems with DATETIME (DT) fields.
The field is set up so you may change these values at any time. @CENTURY is used whenever a date is being process that did not have a century included such as any field with the type DATE or values passed to @CAL.
This should take care of any problems with dates that you may have been concerned about with the turn of the century just around the corner.
Several problems concerning dates in the Oracle Gateway have been fixed.
A problem using OSQL UPDATE with the Oracle Gateway has been fixed.
A new equated command is now available called UNDELETE. This allows you to un-delete an item in your DBL if you have not executed a QUIT CLEAN on the DBL. The syntax is:
UNDELETE HELP
UNDELETE {SD, DI, ID, CM, PM, GS, SF, SI, CS} item.name
MODIFY SD SD.NAME ENTRY ONLY
You can make changes such as adding comments, adding field validation clauses, print pictures, use values clauses, and any other changes that do not alter the format of the Data Set.
Any changes that would alter the SD checksum will cause you to be prompted by the message:
The SD checksum has changed. Your changes may affect the format of the DATA SET. Do you wish to continue the SAVE?
If you respond with "Y", it will complete the SAVE. Any other response will abort the save and take you back to the ACCENT R editor.
If you add subfields or computed fields, you will get the above message "The SD checksum has changed...", but it is safe to complete the save. If you override the message by responding with "Y," you will need to execute the following command:
COMPILE ALL ENTRIES USING SD SD.name
This will recompile all associated DI�s, ID�s, CF�s and PM�s in the current DBL. If you have PM�s in other DBL�s that reference DS�s or DI�s associated with the SD, then you must also recompile them.
New options of the COMPILE command have been added that were requested by numerous users. The new options of this command are:
COMPILE ALL {DI, ID, CM, PM, GS, CF}
COMPILE ALL ENTRIES USING SD SD.name
COMPILE ALL ENTRIES USING DI DI.name
A new option of the FORM command has been implemented along with a new system field @DBL_DELETED_SPACE. This system field can now be used to test how much unused space there is in the current DBL. Determine the best time to rewrite it cleaning out space used by deleted entries using the new option of the FORM command.
IF @DBL_DELETED_SPACE > 100000
FORM DBL DBL.name
CONTINUEThe FORM DBL command, unlike QUIT CLEAN will leave you at the command level of ACCENT R.
ACCENT R now provides you with a new feature that will create a journal file entry each time you change or create any item with the DEFINE or MODIFY/EDIT commands. The file created by ACCENT R can be read by defining an SD as shown below. To invoke this feature, you need only store "YES" into the new system field @JOURNAL.
The format of the records created is:
DEFINE SD JRNFILE
FORM IS BINARY DISALLOW IN PLACE DELETES ENTRY_SIZE, BB, 16 ! DBL Entry size DEL_ITEM, BB, 1 ! If 1 then item was deleted FILL2, BB, 7 DBL_TYPE, C, 3 ! Entry type = SD DI PM CM ID GS CS SI ITEM_NAME, C, 40 ! Data Base Library file name. CREATED, I, MAX ! Entry creation date and time. CHGDATE, I, MAX ! Entry change date and time. FILL3, I, MAX VERSION, I, MAX ! ACCENT R creation version no. CREATOR, C, 40 ! User name who created the item. CHGEDBY, C, 40, ! User name who changed the item. FILL4, I, MAX,OCCURS 9 FILL5, C, 8 TEXTADD, I, MAX ! Byte address of the text. TEXTLEN, I, MAX ! Length of the text in characters. FILLER, C, 62 ! MAKE IT MODE 256 The journal file may be operated on by any of the ACCENT R commands as just another data set. A new equated command has been implemented to make it easy to retrieve information from it.
The options of the SHOW JOURNAL command are:
SHOW JOURNAL HELP
Type the following information about this command.SHOW JOURNAL ENTRIES
Lists entry number, entry type, name, creation date, change date of all entries in the journal file.SHOW JOURNAL ENTRIES FOR ALL PM, CM, SD, DI, ID, GS, CF, CS, SI
Lists information for only those entries of the type specified.SHOW JOURNAL ENTRIES FOR item_type item_name
Lists information of all entries if the entries are item_type and item_name.SHOW JOURNAL ENTRY item.number /TEXT/ [SAVE ON file.name]
Lists the item's text to the terminal or to a file. This will access the DBL file to retrieve the text of the item. Once you have executed a QUIT CLEAN or FORM DBL, the text is no longer available.SHOW JOURNAL DIFF item.number1, item.number2
This produces a DIFF listing of the two items. It dumps the text of each into ### DIFF1.TMP and ### DIFF2.TMP and sets up to call the DIFF utility. Once you have executed a QUIT CLEAN or FORM DBL, the text is no longer available. You must use the SHOW command to get the item numbers.
A new equated command is available for starting a PM debugging session. The DEBUG command is used to assist in setting up the debugging of a PM. The syntax of the command is:
DEBUG PM PM.name [GO]
ACCENT R will check for the presence of a DBL and look up the PM to be sure that it exists in the current DBL. It then sets the PM name to @DEBUG_PM_NAME. If the GO option was specified it will start the execution of the specified PM.
The following information is provided for those who would like to know what criteria is used to cause ACCENT R to rebuild an index. The following also gives you information on how to avoid the rebuild process if you know the index is still valid but looks invalid to ACCENT R.
The following tests are made to determine the reforming of a DI:
Test if doing a CREATE, then do not reform.
Test if this is an RMS file, then do not reform.
Test if the OVERRIDE option was specified in the index definition, then do not reform.
Test if ENABLE INDEX OVERRIDE is set, then do not reform.
Test if the index update number is not equal to or greater than the data set update number, and then do the reform.
Test if a control file even exists. Then check the control file's update number instead of the data set update number. If the index update number is not greater than or equal to the control file's update number, then DO the reform.
After the CF is reformed it will update the number from the DBL�s entry number of the Data Set. The control file will be reformed on the fly if it does not exist.
The update number is incremented whenever the data set is opened for update and when the index update number has changed.
Test if the indexes create number is not equal to the data set create number, then do the reform.
The create number is updated whenever the data set is recreated.
If there is a control file it create number is checked instead of the data set create number.
Test if the checksum in the DBL for the index entry is different than that stored in the index itself, and then do the reform. This means you have changed the index entry.
Test if ACCENT R has been changed in such a way that the format of the index has changed, and then do the reform.
You are always informed of this condition when you receive a new version of ACCENT R. This has only been necessary three times since the initial release of ACCENT R.
If you do not want ACCENT R to automatically reform the index (such that you can decide if it is necessary), then specify STATIC in the index definition. ACCENT R will give you a message that the DI is obsolete rather than automatically executing a reform.
If you know it is okay to be automatically reformed, then do the following:
ENABLE INDEX OVERRIDE
USE DS name DI name
ALTER IF 1 # 1 ENDING IF @RECORD = 1This will put the index in sync with the data set so you can:
DISABLE INDEX OVERRIDE
EXTRACT ENDING IF @RECORD = 1This will check the index again to be sure it is okay to continue the application.
This is to clarify what actions take place when records are retrieved with the NOT LOCKED option.
Using the option "GET FROM designator NOT LOCKED ....", instructs ACCENT R to retrieve the requested record from the data set. This ignores any locking condition of the block containing the record and to NOT queue the block with the System Lock Manager.
When ACCENT R returns from executing the GET statement, if it exists in the data set and whether or not another user has it locked at that time, a copy of the record is available to you. ACCENT R will save a copy of the record before allowing you to make changes to it.
When you execute the PUT to update the record, ACCENT R will attempt to execute "GET FROM designator LOCKED...". If another user has it LOCKED at the time it will wait and try again in five seconds and continue until the record is retrieved or the time in @RECORD.WAIT has been exceeded. If there is a timeout then ACCENT R will return with @AUX set to "BUSY". At this point you must decide whether you can continue to wait or take some other action appropriate to the application.
If the record is retrieved then ACCENT R will compare the record's current state to the state of the record when your PM first retrieved it. If there were no changes made to the file copy of the record, then ACCENT R will write YOUR updated version back to the file and unlock the block containing the record.
If the record was changed by another user after you originally retrieved it, ACCENT R will not write the record back and will set @AUX to "CHANG". In this case, ACCENT R also does NOT free the record. What action you should take next is dependent upon your application. If you know this can happen then you should design your program to be able to repeat the updating of the record.
This version provides a change for the GET NOT LOCKED option of the GET statement in a PM. Previously if you did a GET NOT LOCKED without doing a PUT followed by either a CREATE or a DELETE, you would lose a record from the Data Set, assuming the GET NOT LOCKED operation took place on a record also in the last block of the Data Set. Version 11.73 corrects this so you will no longer lose records.
To receive your permanent license, execute the command:
@NIS:GETSYI.com
This command will retrieve the necessary data and write its output to "GETSYI.LOG". Fax or e-mail this file to NIS to receive your license.
A bug introduced in V11.74 which caused the DBL hash table to be incorrect, making some items inaccessible, was corrected. This was the case only where a DBL, with a logical as part of its name, was being renamed.
When fixing dates with no century, null dates were converted to the year 2000. This has been fixed to return century 0.
This version fixes a bug in the "USE ORACLE SERVER AS..." statement. When the user name is enclosed in quotations, the statement failed because extra characters were being appended from the user name string. This has been fixed.
The previous fix to the Oracle Gateway was to allow connections to other nodes by specifying the user name and node name in a string literal in the form "username$nodename". ACCENT R would change the $ to an @ before sending it to the Oracle Server.
USE ORACLE SERVER AS "TERRY$DELTA" PASSWORD IS XYZXYZ.
This version also contains changes to the HLI such that it now only has a single shared section of memory. In the previous HLI, the sharing of 2 sections was obviously done to save memory space that is no longer critical. This means that all HLI programs must be recompiled to work with this version of ACCENT R. This reduced the total amount of shared memory required.
The Britain Lee Data Base Gateway has been completely deleted and is no longer supported.
In previous versions, the Oracle Gateway was sending NULL as the field value to every field that followed a date field whose value was NULL. It now correctly transmits the values to the Gateway for all field types.
When ACCENT R determined that an index needed to be rebuilt, it passed the command "FORM DI DI.name CHECK" to the command dispatcher. In some cases this caused an infinite loop. Previously, the FORM DI command had to be given directly to correct the situation. By removing the CHECK option this condition was corrected.
...SHOWING DATA NO CV and
...SHOWING ALL NO CV
This option is now implemented for all commands that allow the SHOWING clause.
Fixed the UNDELETE command to also operate on SD�s.
The FORM DBL command used to clear the deleted space counter is fixed.
The SHOW JOURNAL equated command has been added to the list of equated commands.
New syntax to the TYPE command has been added to operate the same as the LIST command. For example, the following will now give the same results:
TYPE CM INVOICES
LIST CM INVOICES
Etc.
DELETE DS MONEY
REMOVE DS MONEY
Etc.
An error in handling secondary fields under the NO CV option of the SHOW clause has been corrected.
Use MODIFY SD SD.name ENTRY ONLY (See documentation for restrictions)
This is to inform the user that it may be possible, under this new option, to make the modification without disconnecting the data set from the schema. This is possible if the change will not affect the data.
The BYE command has been added as an equated command to be equivalent to QUIT QUICK.
A new system field called @CVSW has been added to control the printing of the Computed Value fields with the EXTRACT command and the SHOW clause. It is initialized to "YES" meaning, "print the computed field". If set to any other value it will not print the CV fields. The option NO CV specified in the SHOW clause will override the setting of "YES" in @CVSW.
HOLD (DI, CF, ID, CM, PM, GS) DBL.item.name
A new system field called @SAVE_EDIT_FILE has been added to allow the user to not have the ###EDT.TMP file deleted after editing. This will allow the user to keep better control of changes made to a DBL item. It is initialized to "NO", which will cause the files to be deleted. To save the file, set 'yes' to @SAVE_EDIT_FILE.
ENABLE FORM DI TRACE
This will cause the following information to be displayed when an FORM DI DI.name CHECK is executed or commands such as EXTRACT is used to access the data.
>> Checking DI XX reform criteria:
DI update # is 2 DS update # is 2
DI supersede # is 0 DS supersede # is 0
DI file checksum is 1366658659 DBL entry checksum is 1366658659
DI design gen. is 3 ACCENT R DI design gen. is 3
Added all features from the new features manual and release notes to the HELP system.
The following ENABLE/DISABLE options were not documented in previous versions:
This options will print a message containing the name of the file and the operation being performed for file OPEN, CLOSE, DELETE and RENAME options.
Example:
>> Opening DBL file SS:STARS.DBL for reading
This option will print a message each time a file read operation is performed.
Example:
>> Reading DBL file SS:STARS.DBL at 0 for 4096 bytes
This option will print a message each time a file write operation is performed. The format of the message is the same as for the read operation.
ENABLE IO TRACE
A bug was reported in the current HLI where the error number was not being returned in the calling variable. This has been fixed.
In previous versions the Oracle SQL statement FETCH was not being printed when the TRACE COMMAND AREA was enabled. This has been fixed.
Also in the Oracle Gateway, when a designator was used in a PM which was not the same as the table name, ACCENT R was appending both names to the command for the SELECT, UPDATE, and DELETE statements. This has been fixed.
A change was made to Data Sets with schemas that have FORM IS LINED. ACCENT R now declares the record length to be the same as the maximum record size defined in the schema.
A change has been made as to when the Record Busy message is displayed. In prior version, the message "BUSY" was displayed as soon as the busy record was discovered instead of waiting until the @RECORD_WAIT time expired. Accent R now waits for the time in @RECORD_WAIT to elapse before displaying the message.
Fixed bug where FORM DBL was allowed when READ ONLY DBL was enabled.
Fixed bug so that FORM DBL was valid and FORM DBL DBL.name printed an error message.
The ALTER command was not processing a WHEN range correctly. When a SET clause was specified, all records after the initial value matched were being changed. This has been fixed.
The number of cursors supported in the Oracle Gateway has been increased to 20.
This version fixes a problem with the WHEN clause when a range is specified.
This version changed the default line length from 25600 to 4095 for the SAVE ON file. It will be increased if any line is entered into the file buffer that is longer that 4095. The size was increased previously in error when the actual buffer size was increased for efficiency.
A change was made to memory allocation to make all allocation mod 8. This avoided a problem caused by the previous algorithm which, under some conditions, was way over allocating and causing ACCENT R to run out of memory.
An error was corrected dealing with STOP IF ... and END IF ... if used with the WHEN clause. The STOP and END clauses were not getting executed.
A new equated command called SHOW_OBJECT_SIZE has been added. This command will print the address of the DBL Objects text and the size of the text in characters. If there is compiled code associated with the object then the address of the code and its size in characters will be printed.
This version corrects a number of problems dealing with simultaneous update and adding records to a data set while other users were accessing records in the data set using the NOT LOCKED option. It also corrects a problem which occurs when a GET NOT LOCKED command is followed by a "DELETE" command of the record NOT LOCKED.
- REMOVE SF 'string-literal'
Where string-literal is any specification of a set of files acceptable by the DCL DELETE command. This makes it easy to remove a set of system files that were created for a specific application.
Example:
REMOVE SF '*.TMP;*'
This will delete all .TMP files in the directory.
REMOVE SF '*.DI;*'
This will delete all data index files in the directory before rebuilding them.
- PURGE SF 'string-literal'
Where string-literal is any specification of a set of files acceptable by the DCL PURGE command. This makes it easy to remove older versions of files after an application has been completed.
Example:
PURGE SF '*.ds,*.di'
This will purge all old versions of DS's and DI's in the directory.
PID=pid.number USER user.name
If the HUSH option is used to suppress the normal "BUSY" messages, the PM could be programmed to inform the user, in a friendlier message, as to whom had the record locked.
A new system field @CLEAR_FILE has been added to have ACCENT R remove files before creating them so multiple versions of the file will not be created. It is initialized to "NO". If you wanted the files removed before creating new ones, set the value "YES" to this field.
A number of problems were fixed concerning conversion and display for Date/Time values.
Version 11.87 Changes:
This version fixes a bug in @TIME.STAMP. It was not correctly calculating the minutes.
This version expands the maximum length of a print line to 7680 characters.
The new syntax is:
DEBUG PM PM.name [GO]
DEBUG PM.NAME
DEBUG OFFACCENT R will check for the presence of a DBL and look up the PM to be sure that it exists in the current DBL. It then sets the PM name into @DEBUG_PM_NAME and executes the command "ENABLE PM DEBUG". If the GO option was specified it will start the execution of the specified PM.
If the "DEBUG PM.name" option is used, ACCENT R does not check the PM name, executes the command "ENABLE PM DEBUG", and then executes the PM.
If the OFF option is specified, ACCENT R will clear @DEBUG_PM_NAME and execute the command "DISABLE PM DEBUG".
A change was made to fix a problem with the TYPE item item.name statement.
A change was made to the Oracle Gateway to fix possible problems with the SQL DELETE and SQL UPDATE PM statements where, under certain conditions, the table name was getting repeated within the command.
Fixed a problem where if you saved a CM with a "TYPE ItemType ItemName", ACCENT R was executing the TYPE statement instead of just doing a syntax check.
Fixed a problem with dates being entered in a Screen Layout. If a date was entered incorrectly, ACCENT R did not re-prompt for a correct date.
This version corrects a problem with year 2000 dates being entered into declared storage fields and global storage fields thru a Screen Layout. In these cases the century was not getting added when the field was a type 'D' field. If used in any conditional statement it would compare incorrectly if one date was in any 1900 year and the other in any 2000 year.
Under some situations when an SD was changed, related DI's were not being mark to be reFORMed. They should not be reFORMed if the change didn't effect the record format.
Fixed a problem in the Oracle version where the designator was not being defined as an alias; thus, when the designator was used in identifying a column, the call to Oracle failed with 'INVALID COLUMN NAME'.
Fixed a problem with the CONVERT command which did not allow converting date time data to date or full date.
Fixed a problem causing a memory access error while flattening a DBL.
In previous versions, lines stored in the command area were being executed incorrectly when the user was in PM DEBUG mode.
The character table has been extended to recognize the multinational character set.
The operator ALPHA was returning okay incorrectly on characters in the range of 128 to 255. This has been corrected.
If @DECIMAL.POINT contains a comma, indicating multinational, then the operator ALPHA will return okay for the multinational character set.
In this version, a space is allowed as the first character of a date field in SMF which is converted to a zero. This will allow a user to clear a date field by entering a space. Before, a zero had to be entered to accomplish this; zero was not an obvious choice.
FORM DI DI.name CHECK
was executed on a DI defined by an ID, the index was always rebuilt. This has been fixed to not reform the index unless required.
The use of a date in a WHEN clause, used in a command on an RMS ASCII data set, failed to find a match. This has been fixed.
Fixed a problem that takes care of counting the additional carriage return added following an ampersand in lined records.
@FDATE has been fixed to display the year 2000 when OpenVMS returns "2000" as the century.
"Operand is incompatible in this expression"
This has been fixed to compile and execute correctly.
Fixed a problem of re-reading the text of a DBL item which affected scanning screen layouts in the SCAN_2000 utility.
Fixed a problem with an error message in the HLI which should have given the number of extraneous arguments but did not do so.
Fixed a problem with REMOVE SF "string" and PURGE SF "string" command forms which were not being accepted in a CM.
Fixed a problem with PURGE SF "string" command form which could not be executed if a Data Set was not declared first.
This version fixes a problem with the HLI. In previous versions the HLI was executing the BEGIN.ACC files on the first call to ACCCMD. This has been changed to not execute the BEGIN.ACC files on any call to ACCCMD.
This version contains an option to set the INSERT for FLATTEN to your option. This is accomplished by setting @STRING to the insert command you want used.
SET 'INSERT 1,1' TO @STRING(1)
Will cause FLATTEN to use this statement after every DEFINE statement in the flattened file.
If you use the CLEAN option, FLATTEN will now generate the save statement as 'SAVE BUT HOLD AND STOP ON ERROR' instead of just SAVE.
This version is now setup with ERROR ABORT turned off, so that the DBL can be built from the SF. It will instead check if the errors are in the compilation and emit an error message indicating there were compilation errors. This will eliminate the printing of many errors when an item is compiled that was in the process of being developed.
In addition, this will eliminate errors being printed for equated commands not defined.
One should be sure that all EQUATED COMMANDS are defined that are used in all items of the DBL before attempting to rebuild it.
Error messages are only turned off if you use the 'CLEAN' option of FLATTEN. When you use the clean option you must rebuild the DBL with the command "USE flattened.file.name".
This version also contains the new command FLATTEN_ALL which will take a DIRECTORY specification and flatten all DBL�s found in the path defined. It will tell you whether the current version of ACCENT R can FLATTEN the DBL and if not, will show you which version created the DBL.
The following files are created by the FLATTEN_ALL command:
The file DBL_LIST.LOG lists all the DBL�s found. It indicates if they can be flattened in this version of ACCENT R with error messages as to why they cannot be flattened if that is the case.
The file ACC_FLATTEN_DBL.COM is a COM file to be executed to flatten the specified DBL�s.
The file ACC_REBUILD_DBL.COM is a COM file to be executed to rebuild all the flattened DBL�s.
The file ACC_REMOVE_DBL_FLT.COM is a COM file to be executed to delete all the flattened files after the DBL�s have been recreated.
- The file ACC_REMOVE_OLD_DBLS.COM is a COM file to be executed to delete the old DBL files that were renamed as DBL.name.DBL_OLD so you could restore them if the rebuild failed for some reason.
This command is used to synchronize the information between the DS and DI DBL entries along with the DI and CF files by setting the conditions so that ACCENT R will accept the index as is and not re-form it. It assumes that the DS, DI and CF names are the same. You can set all indexes in a given DBL or set individual indexes.
The syntax of the command is:
SYNC DI {ALL; DI.name} IN DBL.name
SYNC HELP
SYNC SYNTAX
In the previous version a coding error prevented the reporting of compilation errors being reported in the COMPILE command. This has been fixed.
Compiled item_type item_name
This gives the user visual feedback as to the progress of the compilation process.
The command "COMPILE ALL" now will compile all SD's, ID's, DI's, GS's, CF's, CM's and PM's in the declared DBL.
Increased the maximum number of PM's to be modified from 500 to 5000.
Cleaned up code to remove temporary files created by PMMOD.
Rewrote documentation under the HELP function.