Creates the OSAK module.  Refer to HELP ENTITY OSAK for information
    about this entity and its subentities.

    create  [node node-id] osak

    Select application for information on creating osak application
    and osak application invocation subentities on OpenVMS.

1  –  Exception Message

 o  entity exists

    An osak entity already exists.

2  –  application (OpenVMS)

    Creates an osak application entity which represents an OSI application
    and is created each time an OSI application that is running over the
    OSAK software opens an initiator or a responder.  The entity also
    records information about the name and address of an application.

    create  [node node-id] osak application "presentation address"

    For OpenVMS, an osak application entity has zero or more application-
    entity invocations, each represented by an OSAK application invocation
    entity.  In addition to recording information about the name and
    address of an application, it also records information that controls
    the way in which inbound association requests for that application
    are handled by the OSAK software.

    You should create an osak application and an osak application
    invocation for each passive application that you want to run,
    identifying the application by its presentation address.  Also,
    an osak application entity is created automatically for an active
    application and deleted at the end of the connection.

    Example:

    create osak application "'0001'H/'0001'H/'0004'H/NS+21,CLNS"

2.1  –  invocation (OpenVMS)

    Creates an osak application invocation entity which represents one
    invocation of an application.

    create  [node node-id] osak application "presentation address"
            invocation invocation-identifier

    An osak application invocation entity can be created in two ways:

    o  Automatically, each time an OSI application that is running over
       the OSAK software opens an initiator or a responder

    o  Manually, when you use this create command to create a passive
       application, which becomes active only when your OpenVMS system
       receives an OSI call for that particular application invocation.

    Example:

    create osak application "'0001'H/'0001'H/'0004'H/NS+21,CLNS" -
            invocation [AP_Invocation = -1, AE_Invocation = -1]