Information Catalog Manager Administration Guide

ACTION.OBJTYPE

Identifies the action to perform on the object type that is described with the tags that follow ACTION.OBJTYPE.

Context

ACTION.OBJTYPE is used to create, delete, or maintain Information Catalog Manager object types.

ACTION.OBJTYPE is followed by one or more OBJECT and PROPERTY tags, which define the object type being acted on.

Syntax

:ACTION.OBJTYPE(option)

Options

The following options are valid with ACTION.OBJTYPE:

ADD

APPEND

DELETE

DELETE_EXT

MERGE

UPDATE

ACTION.OBJTYPE(ADD)

Creates the object type.

Context

Figure 34. Using the ACTION.OBJTYPE tag when adding object types

:ACTION.OBJTYPE(ADD) :OBJECT.TYPE() CATEGORY() EXTNAME() PHYNAME() ICOFILE() ICWFILE() :PROPERTY.EXTNAME() DT() DL() SHRTNAME() NULLS() UUISEQ() :PROPERTY.EXTNAME() DT() DL() SHRTNAME() NULLS() UUISEQ()

Rules

• The object type must not exist.
• An OBJECT tag and its associated PROPERTY tags must immediately follow the ACTION.OBJTYPE(ADD) tag.
  • The OBJECT tag defines the attributes of the new object type.
  • The PROPERTY tags define the properties that belong to the new object type. The Information Catalog Manager automatically defines the following required properties for every object type:

    OBJTYPID

    INSTIDNT

    NAME

    UPDATIME

    UPDATEBY

• You cannot add object types that belong to the Program or Attachment categories.

ACTION.OBJTYPE(APPEND)

Appends a property to an existing object type.

Context

Figure 35. Using the ACTION.OBJTYPE tag when adding properties to object types

:ACTION.OBJTYPE(APPEND) :OBJECT.TYPE() :PROPERTY.EXTNAME() DT() DL() SHRTNAME() NULLS() UUISEQ()

Rules

• The object type must exist.
• The property being appended must not exist.
• Do not assign the property a UUISEQ value other than 0 (the default). Appended properties must be optional with NULLS(Y) and cannot be part of the UUI.
• An OBJECT tag and one or more PROPERTY tags must immediately follow the ACTION.OBJTYPE(APPEND) tag.
  • The OBJECT tag identifies the object type being appended.
  • Each PROPERTY tag defines a property being appended.
• You cannot append to object types that belong to the Attachment category.

ACTION.OBJTYPE(DELETE)

Deletes the object type.

Context

Figure 36. Using the ACTION.OBJTYPE tag when deleting object types

:ACTION.OBJTYPE(DELETE) :OBJECT.TYPE()

Rules

• The object type must exist. No objects of the object type can exist.
• One or more OBJECT tags must follow an ACTION.OBJTYPE(DELETE) tag. Each OBJECT tag identifies the object type being deleted.
• You cannot delete object types that belong to the Program or Attachment categories.

ACTION.OBJTYPE(DELETE_EXT)

Deletes the object type and objects of that object type.

Context

Figure 37. Using the ACTION.OBJTYPE tag when deleting object types and all objects of that type

:ACTION.OBJTYPE(DELETE_EXT) :OBJECT.TYPE()

Rules

• The object type must exist.
• The object cannot contain objects of a different object type.
• One or more OBJECT tags must follow the ACTION.OBJTYPE(DELETE) tag. Each OBJECT tag identifies the object type being deleted.
• You cannot delete object types that belong to the Program or Attachment categories.

ACTION.OBJTYPE(MERGE)

Checks the information catalog for the input object type name to see if the object type exists.

If the object type exists, the Information Catalog Manager compares properties of the input object type to the properties of the stored object type. If the properties match, then the object types are treated as identical; if not, the input object type is not valid.

If the object type does not exist, the Information Catalog Manager creates a new object type.

Context

Figure 38. Using the ACTION.OBJTYPE tag when merging object types

:ACTION.OBJTYPE(MERGE) :OBJECT.TYPE() CATEGORY() EXTNAME() PHYNAME() ICOFILE() ICWFILE() :PROPERTY.EXTNAME() DT() DL() SHRTNAME() NULLS() UUISEQ() :ACTION.OBJINST(MERGE) :OBJECT.TYPE() :INSTANCE.short_name()

Rules

• An OBJECT tag and its associated PROPERTY tags must immediately follow the ACTION.OBJTYPE(MERGE) tag.
  • The OBJECT tag defines the object type being merged.
  • Each PROPERTY tag defines a property that belongs to the object type.
• Before you can merge objects, you must merge object types to ensure that a valid object type exists in the target information catalog. Therefore, an ACTION.OBJTYPE(MERGE) tag must appear before an ACTION.OBJINST(MERGE) tag in the tag language file.
• You cannot merge object types that belong to the Program or Attachment categories.

ACTION.OBJTYPE(UPDATE)

Changes an object-type external name and ICON file information.

Context

Figure 39. Using the ACTION.OBJTYPE tag when updating object types

:ACTION.OBJTYPE(UPDATE) :OBJECT.TYPE() EXTNAME() ICOFILE() ICWFILE()

Rules

• The object type must already exist.
• One or more OBJECT tags must follow the ACTION tag.