$Title ( iRMX-NET Name Server Configuration for iRMX II on MBII ) ; *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- ; ; ; Module Name: nam2cfg ; ; This module is used to configure the Name Server portion of ; iRMX-NET. The following macros are invoked in this file: ; ; ; 1. max_number_of_object - This macro specifies the number of objects the ; Name Server can support. It is invoked as follows: ; ; max_number_of_object ( n_obj ) ; ; where: n_obj is a WORD indicating the maximum number of objects that ; the Name Server can support. The limitation is for objects ; defined on the local system, not for those defined throughout ; the network. This number does not include the first 9 objects ; which are entered into the Name Server table by iRMX-NET ; during initialization. ; ; ; 2. max_length_for_value - This macro specifies the maximum character ; length for the property value object type. It is invoked as ; follows: ; ; max_length_for_value ( max_value_len ) ; ; where: max_value_len is a WORD indicating the maximum length of ; the property value. max_value_len must not be less than ; 20 (decimal). ; ; ; 3. name_server_mc_id - This macro specifies the multi-cast address ; used by the Name Server to transmit the ; Name Server queries. It is invoked as follows: ; ; name_server_mc_id ( m1, m2, m3, m4, m5, m6 ) ; ; where: m1 to m6 are BYTES indicating the multicast address to be ; used by the Name Server. ; ; ; 4. name_tsap_id - This macro specifies the transport service access ; points (TSAP) ids for the Name Server. It is invoked as ; follows: ; ; name_tsap_id ( init_tsap, resp_tsap ) ; ; where: init_tsap is a WORD indicating the TSAP id to be used by the ; Name Server initiator. ; ; resp_tsap is the TSAP id to be used by the Name Server ; responder. ; ; ; 5. nfs_tsap - This macro specifies the first byte of the TSAP IDs ; for the File Server and the File Consumer. ; It is invoked as follows: ; ; nfs_tsap ( fs_tsap, fc_tsap ) ; ; where: fs_tsap is a BYTE indicating the first byte of the TSAP ID ; portion of a File Server transport address. ; ; fc_tsap is a BYTE indicating the first byte of the TSAP ID ; portion of a File Consumer transport address. ; ; ; The actual TSAP-ID is two bytes. The second byte is added ; by the iRMX-NET code internally. In MULTIBUS I and AT-Bus ; systems, the second byte is set to 0. In a MULTIBUS II ; system, the second byte corresponds to the slot id of the ; host. ; ; ; 6. retry_timeout - This macro specifies the maximum time interval the ; Name Server will wait before retrying a request to ; a remote system. It is invoked as follows: ; ; retry_timeout ( time_out ) ; ; where: time_out is a WORD indicating the interval expressed in ; increments of 100 microseconds. ; ; ; 7. max_retry - This macro specifies the maximum number of retries ; before discontinuing an operation. It is invoked as follows: ; ; max_retry ( num ) ; ; where: num is a WORD indicating the maximum number of retries. ; ; ; 8. number_of_irb - This macro specifies the number of internal request ; blocks used by the Name Server. It is invoked as follows: ; ; number_of_irb ( n_irb ) ; ; where: n_irb is a WORD indicating the number of internal request ; blocks. ; ; ; 9. max_responses - This macro defines the number of responses the ; initiator can handle. The Name Server can receive multiple ; responses for both GET NAME and GET VALUE functions when a ; non-unique name is specified. Any additional responses ; received by the Name Server would be discarded. ; ; max_responses ( max_resp ) ; ; where: max_resp is the number of maximum responses the Name Server ; can handle. ; ; ; 10. ns_local_only - This macro defines whether the name server is to ; support local object table operations only. It is invoked as ; follows: ; ; na_local_only ( y/n ) ; ; where: y/n is 'y' if the name server supports only local object table ; operations and is 'n' if the name server supports both local ; and remote object table operations. ; ; ; 11. number_of_buffers - This macro is only invoked for the Name Server ; running on the COMMengine with iNA. It specifies the number ; of internal buffers to be created for each of the three ; buffers in a Name Server Request Block. It is invoked as ; follows: ; ; number_of_buffers ( name, value, extra ) ; ; where: name is the number of name buffers. ; value is the number of value buffers. ; extra is the number of extra buffers. ; ; ; 12. Data_link_hardware_type - This macro defines the data link hardware. ; It is invoked as follows: ; ; Data Link Hardware Type (hardtype) ; ; where: hardtype - Data Link hardware type. Use one of the following ; values: ; ; 20H for 82586, 82596 and MIX ; 21H for SBX 586 ; ; ; 13. end_name_config - This macro must be the last one invoked. ; It is invoked as follows: ; ; end_name_config ; ; ; DO NOT CHANGE THE ORDER IN WHICH THE MACRO CALLS ARE MADE. ; ; For more information on configuring the iRMX-NET Name Server using ; these macros, refer to the iRMX-NET Installation and Configuration ; Guide. For more information on the Name Server in general, refer ; to the iRMX-NET User's Guide. ; ; *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- name name_configuration $include(:rmxnet:config/asm86.lit) $include(:rmxnet:config/namcfg.mac) %max_number_of_object ( 50 ) %max_length_for_value ( 20 ) %name_server_mc_id ( 01, 0AAH, 0,0FFH, 0FFH, 0FEH ) %name_tsap_id ( 0042H, 0043H ) %nfs_tsap ( 10H, 11H ) %retry_timeout ( 2000H ) %max_retry ( 3 ) %number_of_irb ( 3 ) %max_responses ( 25 ) %ns_local_only ( n ) %number_of_buffers ( 6, 5, 5 ) %dl_hardware_type ( 20h ) %end_name_config end