assoc_handle OpenVMS usage:association_id type: longword (unsigned) access: write only mechanism: by 32-bit or 64-bit reference (Alpha and Integrity servers) The 32-bit or 64-bit address (on Alpha and Integrity server systems) into which $ICC_OPEN_ASSOC writes the handle assigned to the opened association. assoc_name OpenVMS usage:char_string type: character-coded text string access: read only mechanism: by 32-bit or 64-bit descriptor (Alpha and Integrity servers) An ASCII character string of up to 31 characters in length specifying the name of the application opening the association. Null (0 length), and empty or blank association names are not allowed. If this argument is omitted (that is, a zero is passed in by value), it signifies that the user wants to open the default association. This argument is case sensitive. logical_name OpenVMS usage:logical name type: character-coded text string access: read only mechanism: by 32-bit or 64-bit descriptor (Alpha and Integrity servers) A logical name in a clusterwide logical name table used to maintain the simple association registry. The logical name represents the name of the service provided by the application. Logical names are case sensitive. logical_table OpenVMS usage:logical name table type: character-coded text string access: read only mechanism: by 32-bit or 64-bit descriptor (Alpha and Integrity servers) The table containing the logical name logical_name. Logical name tables are converted to uppercase. Unless your application requires an application-specific logical name table, this argument should be either the default ICC Registry search list (ICC$REGISTRY), or the default registry table (ICC$REGISTRY_TABLE). conn_event_rtn OpenVMS usage:user_routine type: procedure_entry_mask access: call without stack unwinding mechanism: by 32-bit or 64-bit linkage reference (Alpha and Integrity servers) The address of the AST routine to be called for incoming connect events. This routine will be called in the mode of the caller. (No mechanism is provided for the routine to be called at a different mode). You must have a conn_event_rtn to operate as a server. disc_event_rtn OpenVMS usage:user_routine type: procedure_entry_mask access: call without stack unwinding mechanism: by 32-bit or 64-bit linkage reference (Alpha and Integrity servers) The address of the AST routine to be called for incoming disconnect events. This routine will be called in the mode of the caller. (No mechanism is provided for the routine to be called at a different mode). The arguments, conn_event_rtn, and disc_event_ rtn, may reference the same routine. recv_rtn OpenVMS usage:user_routine type: procedure_entry_mask access: call without stack unwinding mechanism: by 32-bit or 64-bit linkage reference (Alpha and Integrity servers) The address of the AST routine to be called for incoming new data events. If the user provides this routine, it indicates that the user will supply a buffer of the size required (specified in an argument to the recv_rtn at each call) each time one is requested. If the user supplies this routine, receive calls should only be issued after receive events arrive and sufficient buffer space has been allocated to handle the incoming data. This routine will be called in the mode of the caller. (No mechanism is provided for the routine to be called at a different mode). maxflowbufcnt OpenVMS usage:longword_unsigned type: longword (unsigned) access: read only mechanism: by value The maximum number of pending inbound messages (per connection) that ICC will allow the user before initiating flow control. A message is pending if it is being held within ICC but no receive call(s) are outstanding from the user. Default = 5 (Pass 0 to get the default) prot OpenVMS usage:longword_unsigned type: longword (unsigned) access: read only mechanism: by value This argument is ignored for non-server applications. The default protection scheme for this association is as follows: 0 - access for everyone (default) 1 - stops WORLD access 2 - stops both WORLD and GROUP access Advanced access control is provided by ICC Security objects. For information about ICC system management and security, see the HP OpenVMS System Manager's Manual.