Conference azur::mcc

2289.0. "New feature s in DAP..." by DFLAT::PLOUFFE (Jerry) Thu Feb 06 1992 18:28

  Based on the comments in QAR #2204 (MCC_INTERNAL database - Thanks Richard!),
  a couple of changes have recently been made to DAP:

    o The UPDATE command used to abort and return an error if the class
      specified was not found in the dictionary.  Now, DAP will continue
      to process the DAP command file specified in the UPDATE command even
      if the class specified was not found in the dictionary.

      This allows users to more easily write command procedures or scripts
      to load the dictionary with their dictionary objects.  They no longer
      have to worry about whether their objects have already been loaded or
      not.

    o The status of DAP commands was not being correctly passed back up to
      the operating system (VMS or ULTRIX).  
 
      Now, DAP will return the status of the last command executed to 
      the operating system.

      On VMS, this status will be either a DAP or MCC status code.  An
      odd value in $status indicates success; even indicates error.
      $severity can be used to retrieve the severity of the status.

      On ULTRIX, this status will be either zero (0) or negative one (-1).
      A zero value in the environmental variable "status" indicates
      success; negative one indicates error.

  These changes will be effective in the next release of the v1.2 kit.  I just
  thought it would be a good idea to post some advance notice in this notes
  file.

                                                                      - Jerry 

Re.0: 

	Great !!!

	So, there is always hope ! We have been waiting for these features
	for 2 years now !

	It is not only script for dev. purpose that will become easier, 
	but also KITINSTALL and setld SCPs that will become cleaner :
	I can now remove from them the line 

	"Ignore the following error message :

	 %MCC-E-NOENTITY,  no corresponding entity instance exists
	 %MCC-E-NOENTITY,  no corresponding entity instance exists  "

	and know if the DAP update has been successful.

	Thanks.

	Pierre.

re .0

Great. Thanks.

re .1

Pierre,  

It is good that it is now fixed. My kitinstall went around the 
 %MCC-E-NOENTITY,  no corresponding entity instance exists 

by doing something like

$
$ DAP       = "manage/toolkit/dictionary"
$ not_found = "%X08D78053"                 ! SEARCH return status of NOT FOUND
$ !
$ DAP show class mcc to sys$scratch:dap_output.tmp
$ define sys$output nl:
$ define sys$error  nl:
$ search sys$scratch:dap_output.tmp "qms_am"
$ search_status = $status
$ deassign sys$output
$ deassign sys$error
$ if search_status .eqs. not_found then goto load_mgmt
$ !
$ DAP update class MCC subclass QMS_AM from mcc_qms_am_mgmt_if.com
$ goto cmd_dispatcher
$ !
$load_mgmt:
$ DAP load class MCC subclass QMS_AM from mcc_qms_am_mgmt_if.com
$ !
$cmd_dispatcher:


Crude but effective.
This should do it for V1.1. Will change it for UPDATE only on V1.2 if it works
as advertised in .0

Phil