Conference azur::mcc

About REGISTER and CREATE ...

The CREATE is still part of the "Add Entity" operation.   The algorithm 
was modified to only perform the REGISTER and/or CREATE directive if
the entity being added isn't registered and/or created.  

When you enter the entity instance in the first form, the code now does a
DIRECTORY <entity> and a SHOW <entity> before attempting to register and
create the entity.  If a successful response is returned
for each of the above commands, the is already registered or created.  (The
logic here is that there is no need to ask for the register and create arguments
if the enity already exists.)  The user only needs to drop the icon in the map.

If the entity is not registered and/or created, the second form will 
appear which contains the register and/or create directive arguments.  I
say "and/or" because only the information necessary is asked for. 

The previous release of the Iconic Map PM always required the register and
create directive arguments.  We got lots of feedback that this was anoying
when the user knew that the entity was registered and created, especially
if one of the arguments was "required".  

About DEREGISTER and DELETE...

The delete and double delete icons in the toolbox perform the DEREGISTER 
and DELETE directives.  This is why they do not appear in the operations
menu.  

If you are at a global entity level, you can 

	delete the global entity from the domain (via delete icon)
	delete the global entity from the domain, delete the global entity,
	  and deregister the entity.  (via double delete icon).

If you are at the subentity level, there is only one delete icon.  This
always deletes and deregisters the subentity.

 
/Jim

Regarding the delete/deregister operations in the toolbox. It looks like there
are (potentially) three repositories that will have knowledge of a global
entity instance.

1. The iconic map (MCC$_<domain>.DAT), which records the name of the
instance, the icon to place on the map, and the x,y coords of the icon.

2. DNS, in which the global entity instance is registered.

3. The MIR, if the AM chooses to store instance and orphaned attribute info.

From the iconic interface, and starting from a state where an instance does
not exist in any of the respositories, I can create an entry in all of them.

But if I want to get rid of the entries, it seems that I can only delete
from repositoies 1 and 2. I have to go to FCL to ask the AM to delete its
instance. The "Delete" operator in the toolbox deletes the icon from the map
(repos #1). The "Double-Delete" deletes the icon and Deregisters the global
entity from DNS (repos #2). But a DELETE entity instance is never done to
the AM.

If the iconic PM will do the create, shouldn't it also do the delete?

  The double delete tool removes the the entity instance from all
of them.  It issues the following commands:

	DELETE DOMAIN <X> MEMBER <Y>    (removes from map file and domain)
	DEREGISTER <Y> 			(removes from DNS)
	DELETE <Y> 		        (deletes entity)


The DELETE <Y> operation should remove the info stored in the MIR by the
CREATE <Y> operation.  If this is not happening, either the Iconic Map
is not issuing the DELETE correctly, or the DELETE directive is not
cleaning up after itself.

/Jim

RE: .3

Jim,

I checked just now to be sure. I turned on directive entry-point breakpoints.
When I create the global entity, the Show entry point in my AM is called
to see if the entity exists, and if it doesn't (after getting forms filled
in) the Create entry point is called.

Using the double-delete on the icon results in no calls to my AM. I put
the icon back and tried the single-delete too, just for grins, no AM
calls.

The AM supports the delete, I can access it from FCL, and it does delete
the instance when called.

MCC X1.1.0 Sept

re .4

I also checked it. Double delete does not call my Delete entry in the AM. The
delete works fine from the FCL.

   I will check the code to see why this is happening and will post
results here.

Thanks
/Jim

  The probem is in the delete global entity code.  It is only deregisters
the entity.  It will be fixed in the next release.  

I will QAR this. 

Many thanks for finding it!

/Jim

The problem described in replies .4 through .7 still exists. Applying the
double delete to a global entity does not call the delete entry point
in the AM. Delete from FCL works.

This isn't mentioned as a restriction on the Iconic PM in the Release Notes
for V1.1 SSB.

This fell through the cracks. (Actually it was a pilot error.  I
made the change, tested it and THOUGHT I put it back in CMS.  The evidence
indicates otherwise.)

It WILL be fixed in the next release.

/Jim