Conference azur::mcc

3262.0. "Announcing VAX DetMCC/VMS Field Test T1.3-13" by STKHLM::TORZSOK (No good...too complicated !) Mon Jun 29 1992 04:42

	Announcing VAX DetMCC/VMS Field Test T1.3-13
	--------------------------------------------

			NOTE

	*** Network kits are for DIGITAL INTERNAL USE ONLY ***

	
	I am very pleased to announce that DetMCC T1.3-13 is ready for
	Field Test.

	The kit is now available for internal use from:

	Directory VAXBOX::LUDDE::LUDDE_KIT:[FT_DETMCC]

	FT_DETMCC013.A;1    FT_DETMCC013.B;1    FT_DETMCC_USER_GUIDE.LN03;1
	FT_DETMCC_USER_GUIDE.PS;1               

	Total of 4 files.
 
	Appended to this mail is the release notes for this field test
	version of DetMCC.

	Please reply to this mail and enter the following information:

	1) Installer's Name / ENet Address:

	2) VMS and DECmcc Version:

	3) System Type and Memory Size.

	4) Problems/suggestions/etc.


	If you have any questions/suggestions/problems please contact me
	me at VAXBOX::TORZSOK.


	May Thanks for your help,
	Ralf Torzsok.



          _______________________________________________________

   B      Release Notes for VAX DetMCC/VMS T1.3-13







          __________________________________________________________________

   B.1    New Features



          ___________________________

   B.1.1  Restriction on Command Buffer removed

          The restriction on the DetMCC command buffer has been
          lifted. DetMCC does now support line editing. The size
          of the command buffer is pointed out by the system
          executive logical name DetMCC_RECALL_BUFFER_SIZE. The
          default value is 20 lines.

          ___________________________

   B.1.2  New Qualifier /LOG added to command verb DetMCC

          A new qualifier /[NO]LOG have been added to the
          command verb DetMCC. The new qualifier tells DetMCC
          whether or not to display the full information when
          trying to connect to the DetMCC Server process. By
          default, only the Welcome and Copyright messages are
          displayed.


          ___________________________

   B.1.3  Logging of connect/disconnect requests to the Server
          Process

          When a process connect/disconnect to the Server
          process a Audit message is written to the file
          pointed out by the logical name DetMCC_AUDIT_FILE.
          The information written to the Audit file includes the
          connect/disconnect time, Pid and Username.

          __________________________________________________________________

   B.2    Bugs Fixed



          ___________________________

   B.2.1  Output badly formatted

          If output from DECmcc was indented and wraped the
          terminal width, the output was written on the next
          line without doing a new indentation. This has been
          fixed.


          ___________________________

   B.2.2  Data overrun and data lost communications problems

          The Server process did not check for XOFF or XON when
          it communicated with the EXEC process. The result of
          this was that the EXEC process could die with data
          lost or data overrun messages. This has been fixed.


          ___________________________

   B.2.3  No status message was passed to the Server proceses
          during KILL

          During shutdown of the DetMCC system with the command
          KILL, no status message was delivered during force
          exit. Due to this a missleading error message was
          entered in the Server and Exec process log files. This
          has been fixed.

          ___________________________

   B.2.4  The timeout always fired if KILL was used at command
          line

          If the internal command KILL was used at command line
          mode, the timer to delete the process was always
          fired, instead of doing a force exit of the Server
          and Exec process. This has been fixed.

          ___________________________

   B.2.5  DetMCC prompted for input while DECmcc was not ready
          for input

          In some cases, after a CTRL/C, DetMCC could prompt for
          input even if DECmcc was not ready for input. If this
          happend, two commands could be queued at the same time
          to the EXEC process. This has been fixed.


          ___________________________

   B.2.6  The MCC_INIT file was read and execute twice during
          Server creation

          If the Server process didn't exist and was created,
          the MCC_INIT file was read and execute twice. First by
          DECmcc and then by DetMCC. This have been fixed.

          ___________________________

   B.2.7  Using CTRL/C could hang the system

          In some cases the user didn't get prompted back after
          CTRL/C had been entered. This has been fixed.

          __________________________________________________________________

   B.3    Known Restrictions

          This section includes all known restrictions in the
          current release.

          ___________________________

   B.3.1  Server Limit

          The Server process can only handle one user connection
          at a time.


          ___________________________

   B.3.2  User Interface

          VAX DetMCC/VMS is limited to work only with the
          command line mode of DECmcc FCL.