|
Chapter 2
Patch Release - V1.1-014
_____________________________________________________________________
This chapter contains a list of bug fixes/changes which are implemented
in MDV V1.1-014.
__________________________________________________________
2.1 Bugs Fixed in this Release
The following is a list of bugs reported after the release of V1.1-
012 which have been fixed in V1.1-014.
1. Incorrect PSECT name used in MDVSHR transfer vectors causing in-
compatability between MDV versions and requiring user written ap-
plication programs to re-link (See Section 4.1).
Transfer vectors now function correctly. Future versions will not
require user written application programs to re-link.
2. CLI opens the files specified in the application record for READONLY
thus preventing any maintenance other than EDIT.
Files are now opened for READWRITE during maintenance.
3. CLI options have missing qualifiers for required data fields.
All required qualifiers now present.
4. CLI multiple delete for the option file does not recognize qual-
ifiers.
Multiple delete for the option file now implemented correctly.
Digital Internal Use Only
2-2 Patch Release - V1.1-014
5. CLI command SHOW GROUP does not show anything except titles.
SHOW GROUP now displays data.
6. Under certain circumstances, beginning and ending quotation marks
["] are not removed from strings in CLI maintenance routines.
Incorrect qualifier types have been redefined.
7. CLI maintenance commands always issue a status message even when
the /LOG qualifier is not present.
Now correctly checks for presence of the /LOG qualifier before is-
suing status messages.
8. Hard coded messages within the MDVSHR code prevent users from fully
converting the HI to local language (e.g. "More..." on the main menu).
Hard coded messages have been removed from the program and have been
replaced by messages in the MDV message file (see Section 2.3.1).
9. Application logout procedures are only executed when leaving an
application and returning to the application selection menu.
Apllication logout procedures are now executed before LOGOUT and
before the exit to DCL level.
10. Unable to use multiple FMS form libraries due to fact that libraries
are always opened on the same fixed channel and are never closed.
MDV will now select a free library channel before opening the li-
brary. Forms are now loaded into memory and the library is closed
after use.
11. Wrong screen displayed after the use of the direct option access
("menu skipping") command.
After execution of the option MDV will return to the menu on which
the selected option was situated. On backing out of this menu, MDV
will return to the menu from which the original command was issued.
12. Screen is not cleared after running interactive options.
Digital Internal Use Only
Patch Release - V1.1-014 2-3
The method used by MDV to clear the screen has been changed to fix
this problem (Only occured when running MDV on a workstation us-
ing a VWS terminal emulator window).
13. Interactive routines (other than type RTN) do not set and re-set
the keypad mode correctly.
Keypad mode is now correctly set and re-set.
14. Batch/detach jobs are aborted if a duplicate/erroneous process name
is encountered.
Error trapping for duplicate/erroneous process names has been sup-
pressed.
15. Logical names defined in the GROUP table for passing parameters
to detached processes are never deassigned.
The detached process controller now deassigns group logicals as part
of the end process cleanup.
16. Application specific print and batch queue names defined in the
application record are not readily available to the application.
Process level logical names containing these values are now avail-
able (see Section 2.3.2).
17. Identifiers specified in the ACLs list are always granted with the
attribute NORESOURCE. This places unnecessary constraints on the
use of identifiers and can cause inconsistencies with the defini-
tions in RIGHTSLIST.DAT.
The attributes defined in RIGHTSLIST.DAT are now used to determine
the attributes of identifiers granted by MDV.
18. Pre- and post-functions are not executed for options of type MNU.
Pre- and post-functions are executed for all executable option types
(see Section 2.3.3).
19. The screen is always cleared before a pre-/post-function. Under
certain circumstances this may not be desirable.
Digital Internal Use Only
2-4 Patch Release - V1.1-014
Screen clearing is now optional (see Section 2.3.4).
20. Hard coded messages within the command procedures prevent users
from fully converting the messages to local language.
Hard coded messages have been removed from the command procedures
and have been replaced by messages in the MDV message file (see Section 2.3.1).
21. MDV messages can not be customized to meet local language require-
ments.
The source of the MDV message file is now provided in the examples
sub-directory (see Section 2.3.1).
22. When using the connection file maintenance, it is necessary to en-
ter the connection description for every user/application connec-
tion.
An option has been provided that allows the connection description
to default to the application description (see Section 2.3.5).
__________________________________________________________
2.2 Known bugs
The following is a list of known bugs which have not been addressed
in this release.
1. Continuation lines do not function correctly from a command file
2. Previous assignments of LNM$FILE_DEV are ignored.
3. Auto-execute does not function if the menu containing only one menu
option also contains a BLK or PRK option.
4. MDV logical names not automatically available to MDVCLI outside of
the MDVSYS account.
5. Errors cause MDVCLI image to crash
Digital Internal Use Only
Patch Release - V1.1-014 2-5
__________________________________________________________
2.3 New Features
__________________________________________________________
2.3.1 Messages
As far as possible, all hard-coded text in both programs and command
files have been moved to the MDV message file. Messages of this type
are identified by the prefix MDV$_TXT.
In order to allow for the local customization of these and other mes-
sages, the message source file is now available in the examples di-
rectory:
MDV$DIR_EXA:MDV$MESSAGES.MSG
In addition, a command file is provided in the command file directory
to facilitate the rebuilding of the customized message file image:
MDV$DIR_COM:MDVMSGBLD.COM
Users of the callable interface may make use of the default message
object file provided in the examples directory:
MDV$DIR_EXA:MDV$MESSAGES.OBJ
If the message file is customized, a new object file can be generated
using the command file mentioned above.
Note When customizing the messages, only the text of the messages should
be changed. The order in which the messages appear in the source file
should not be changed and neither should messages be added to or delete
from the file as this will lead to incorrect messages being displayed.
__________________________________________________________
2.3.2 Batch and Print Queues
The values of the application default batch and print queues as de-
fined in the application file record are now available as logical names
in the process logical name table:
MDV$BATCH_QUEUE
Digital Internal Use Only
2-6 Patch Release - V1.1-014
MDV$PRINT_QUEUE
__________________________________________________________
2.3.3 Menu Pre-/Post-functions
Care should be taken when attempting to pass information between op-
tions by means of logical names, DCL symbols, etc. that are set-up by
the pre- and post-functions. It should be remembered that the pre-functions,
post-functions, option types DCL, COM and EXE execute in the MDV sub-
process whereas options of type MNU and RTN execute in the MDV main
process.
__________________________________________________________
2.3.4 Optional Screen Clear
By default, MDV always clears the screen before entering a pre-function,
command, post-function sequence. This screen clear may now be suppressed
by entering a hash sign (#) in the first position of the the pre-function,
command or post-function fields.
__________________________________________________________
2.3.5 Connection File Description
In order to save the user the chore of entering a description for each
new user/application connection that is entered, the user may now chose
to use the application description as the default connection descrip-
tion. This is achieved by entering an asterisk (*) in the first char-
acter of the connection description field (the remainder of the field
should be left blank). On encountering an asterisk in this field the
system will automatically copy the application description to connec-
tion file record (note that the description will not be displayed at
this time).
|