home *** CD-ROM | disk | FTP | other *** search
/ DP Tool Club 8 / CDASC08.ISO / VRAC / CMINFO.ZIP / II07001.CM < prev    next >
Text File  |  1993-07-07  |  19KB  |  236 lines
  1. +-------------------------------------------------------------+                 
  2. | II07001                                                     |                 
  3. |          COMMUNICATIONS MANAGER/2 1.0 562125400             |                 
  4. |                                                             |                 
  5. |          SNA GATEWAY                                        |                 
  6. |                                                             |                 
  7. |          Tips, Techniques, and Frequent Problems            |                 
  8. |                                                             |                 
  9. |LAST UPDATE:  05/26/93                          BY: RHB      |                 
  10. |                                                             |                 
  11. +-------------------------------------------------------------+                 
  12. |RECOMMENDED READING                                                            
  13. | 1. 05/26/93 Communications Manager/2 Configuration                            
  14. |    Guide, SC316171, Chapter 11.                                               
  15. |    This book provides Configuration information and                           
  16. |    instructions for the product.                                              
  17. |                                                                               
  18. | 2. 05/26/93 Communications Manager/2 Network Administration                   
  19. |    and Subsystem Management Guide, SC316168, Chapter 7.                       
  20. |    This book also defines concepts and planning procedures                    
  21. |    for configuration, installation, and networking                            
  22. |    considerations.  Shipped with this book is a                               
  23. |    diskette that contains SAMPLE RESPONSE FILES.                              
  24. |                                                                               
  25. | 3. 05/26/93 Communications Manager/2                                          
  26. |    New Features, GG243958, Chapter 5.                                         
  27. |    This book provides an overview of the new and                              
  28. |    enhanced features of Communications Manager/2.                             
  29. |                                                                               
  30. |CONFIGURATION DIFFERENCES                                                      
  31. |                                                                               
  32. | 1. 05/26/93 There are now two (2) SNA Gateway definition                      
  33. |    verbs located in the .NDF file which can occur                             
  34. |    multiple times.  They are:                                                 
  35. |                                                                               
  36. |     DEFINE_GATEWAY_HOST :                                                     
  37. |       This parameter defines LU POOLS for a specified host                    
  38. |       link and optionally, their AUTO-LOGOFF timers.                          
  39. |                                                                               
  40. |     DEFINE_GATEWAY_WORKSTATION :                                              
  41. |       This parameter defines which HOST LU's will be                          
  42. |       allocated to which workstation, and whether the LU's                    
  43. |       will be POOLED or DEDICATED.  Only POOLED LU's are                      
  44. |       given to IMPLICIT workstations.  Keep in mind that                      
  45. |       the gateway never contacts an IMPLICIT workstation.                     
  46. |                                                                               
  47. | 2. 05/26/93  SNA Gateways can now support up to 3                             
  48. |    MULTIPLE PU's which can all be active at the same                          
  49. |    time.  This means that there will be 2                                     
  50. |    or more DEFINE_LOGICAL_LINK commands in the .NDF                           
  51. |    that specify SOLICIT_SSCP_SESSION(YES).  This signifies                    
  52. |    that APPC is expecting ACTPU's and ACTLU's from the                        
  53. |    other end of the link.                                                     
  54. |                                                                               
  55. | 3. 05/26/93 When configuring a connection to a                                
  56. |    host or logical link through the panels,                                   
  57. |    a HOST LINK will have SOLICIT_SSCP_SESSION(YES)                            
  58. |    and ACTIVATE_AT_STARTUP(YES).                                              
  59. |                                                                               
  60. | 4. 05/26/93 All defined links must specify the following:                     
  61. |       o  ADAPTER_NUMBER                                                       
  62. |       o  DLC_NAME                                                             
  63. |       o  Destination ID                                                       
  64. |                                                                               
  65. |    The destination ID can be defined in 3 ways:                               
  66. |       o  DESTINATION_ADDRESS                                                  
  67. |       o  FQ_ADJACENT_CP_NAME                                                  
  68. |       o  ADJACENT_NODE_ID                                                     
  69. |                                                                               
  70. |    DESTINATION_ADDRESS can be specified through either                        
  71. |    the Communications Manager Configuration panels or                         
  72. |    by editing the .NDF file.                                                  
  73. |                                                                               
  74. |    FQ_ADJACENT_CP_NAME is specified in the panels by the                      
  75. |    Partner network ID and Partner node name on the                            
  76. |    CONNECTIONS PANEL, but this panel forces one to put in a                   
  77. |    destination address and adds a DEFINE_PARTNER_LU                           
  78. |    LOCATION verb.                                                             
  79. |                                                                               
  80. |    ADJACENT_NODE_ID can only be specified by editing the                      
  81. |    .NDF file.                                                                 
  82. |                                                                               
  83. |    Links defined through FQ_ADJACENT_CP_NAME and ADJACENT                     
  84. |    NODE_ID only work with links that perform XID exchanges.                   
  85. |    These links must also have ACTIVATE_at_STARTUP(NO).                        
  86. |    Keep in mind that the remote node must activate the link.                  
  87. |                                                                               
  88. |    FQ_ADJACENT_CP_NAME only works for XID3 exchange, not                      
  89. |    XID0.                                                                      
  90. |                                                                               
  91. |    After changing the .NDF file the configuration will                        
  92. |    need to be verified. See Item 3, under                                     
  93. |    Configuration Problems section.                                            
  94. |                                                                               
  95. | 5. 05/26/93  With Multiple PU (MPU), one link is                              
  96. |    designated as the control point link and:                                  
  97. |      o  it's PU_NAME is either the same as the CP_NAME                        
  98. |         or is not specified.                                                  
  99. |      o  It is used as the HOST_FOCAL_POINT so all NMVT's                      
  100. |         will be sent to it.                                                   
  101. |                                                                               
  102. |                                                                               
  103. |CONFIGURATION PROBLEMS                                                         
  104. |                                                                               
  105. | 1. 05/26/93  Many fields that were in HEX in prior releases                   
  106. |    are now in DECIMAL.  This is especially true for                           
  107. |    NAU ADDRESSES.  If you are upgrading from EE or ES,                        
  108. |    this conversion will be done for you.                                      
  109. |                                                                               
  110. | 2. 05/26/93  In the .NDF file, but not in the panels,                         
  111. |    all numbers are assumed to be in DECIMAL                                   
  112. |    unless preceded by 'X' and enclosed in SINGLE QUOTES.                      
  113. |                                                                               
  114. | 3. 05/26/93  After the .NDF file is updated, the file                         
  115. |    must be verified.  Use CMSETUP or CMVERIFY.                                
  116. |    See Chapter 1 Communications Manager Features under                        
  117. |    Communications Manager Configuration Methods                               
  118. |    in the Network Administration and Subsystem Management                     
  119. |    guide SC316168 and Chapter 5 Configuration Verbs                           
  120. |    in the System Management Programming Reference, SC316173.                  
  121. |    The APPNV.CTL file in the CMLIB sub-directory also shows                   
  122. |    the syntax for these verbs.                                                
  123. |                                                                               
  124. | 4. 05/26/93  POOL NAMES in the GW configuration are                           
  125. |    CASE SENSITIVE but, SNA NAMES (LU names, PU names,                         
  126. |    link names etc) are not.                                                   
  127. |                                                                               
  128. | 5. 05/26/93 If "2B?" or "2B " is received in the OIA                          
  129. |    of the downstream workstations then check                                  
  130. |    the following:                                                             
  131. |    -That link between the SNA Gateway                                         
  132. |     and the host is active.                                                   
  133. |    -That if the workstation is explicitly defined, and                        
  134. |     the LAN Destination Address is specified,                                 
  135. |     then make sure the local address of the                                   
  136. |     downstream workstation matches the defined                                
  137. |     address in the SNA Gateway.                                               
  138. |    -That the NAU addresses match between the                                  
  139. |     downstream workstation configuration and the                              
  140. |     SNA Gateway workstation configuration.                                    
  141. |                                                                               
  142. |MISCELLANEOUS PROBLEMS                                                         
  143. |                                                                               
  144. | 1. 05/26/93 Various Symptoms on Downstream Token-Ring                         
  145. |    workstations attached to the SNA Gateway.                                  
  146. |    -COMM695 on Downstream Workstations.                                       
  147. |    -ACS1231 on Downstream Workstations.                                       
  148. |    -XID failure                                                               
  149. |    -Only some Downstream Workstations Connect.                                
  150. |    -RANDOM COMM695 on Downstream Workstations.                                
  151. |    -Message LT20030 on the SNA Gateway Workstation                            
  152. |     in the LANTRAN.LOG.                                                       
  153. |    -Cannot establish sessions with more than                                  
  154. |     a certain or set number of workstations.                                  
  155. |    On the SNA GATEWAY workstation, change                                     
  156. |    the following configuration items for the                                  
  157. |    Token-ring card connecting the Downstream                                  
  158. |    workstations:                                                              
  159. |        - Use the REFERENCE DISKETTE and set the                               
  160. |          Token-Ring card to use a shared RAM SIZE                             
  161. |          OF 64K, If the workstation is not                                    
  162. |          executing LAN Server via this Card.                                  
  163. |        - In the configuration for the Token-Ring                              
  164. |          Data Link Control increase the max number                            
  165. |          of link stations from to 128.                                        
  166. |        - In the configuration for the LAN Adapter                             
  167. |          and Protocol support, make sure the Max.                             
  168. |          number of link stations is 255.                                      
  169. |        - In the LAN adapter and protocol support (LAPS)                       
  170. |          IEEE 802.2 profile increase the Timer Control                        
  171. |          Blocks setting to 128.                                               
  172. |                                                                               
  173. | 2. 05/26/93 If the GATEWAY reports an error, it will be                       
  174. |    logged in the OS2 SYSTEM OS2MLOG.DAT.  Reference                           
  175. |    II06915 Finding the cause of problems when using                           
  176. |    Communications Manager/2.                                                  
  177. |    Types of messages logged are                                               
  178. |      o  Negative responses to an ACTPU/DACTPU, BIND/UNBIND,                   
  179. |         or NOTIFY.                                                            
  180. |      o  Frame out of sequence.                                                
  181. |      o  Workstation requests an ACTPU, but no associated                      
  182. |         definition for it.                                                    
  183. |                                                                               
  184. | 3. 05/26/93  Message ACS2008 (the gateway is unable to                        
  185. |    create a session) can be logged when nothing is wrong.                     
  186. |    (This does not apply to Communications Manager/2 1.0                       
  187. |    at WR06050.)                                                               
  188. |                                                                               
  189. | 4. 05/26/93  If you are having problems with Alerts not                       
  190. |    getting to NETVIEW, please review the Management                           
  191. |    Services information APAR II06895.                                         
  192. |                                                                               
  193. |SNA GATEWAY APARS RESOLVED IN WR06050                                          
  194. |                                                                               
  195. | 1. 05/26/93  JR06942  Does not produce a distinct                             
  196. |    message indicating that the maximum number of                              
  197. |    link stations defined have been exceeded.                                  
  198. |                                                                               
  199. | 2. 05/26/93   JR07121 The SSCP-PU session between VTAM                        
  200. |    and a SNA Gateway is taking longer than expected.                          
  201. |                                                                               
  202. | 3. 05/26/93   JR07123 Downstream workstations unable to                       
  203. |    re-connect to ES/1 server after a link failure.                            
  204. |                                                                               
  205. | 4. 05/26/93   JR07126 SNA Gateway does not reactivate the                     
  206. |    DLC after VTAM is recycled.                                                
  207. |                                                                               
  208. | 5. 05/26/93   JR07128 On X25 NETWORK, Generates call                          
  209. |    indefinitely responding to clear 00.                                       
  210. |    No way to eliminate or stop the retries.                                   
  211. |                                                                               
  212. |ADDITIONAL READING                                                             
  213. |                                                                               
  214. |There are several books that can be ordered separately                         
  215. |which provides additional planning and installation                            
  216. |information.                                                                   
  217. |                                                                               
  218. | 1. 05/26/93 Host Connection Reference, SC316170.                              
  219. |    Contains parameter matching and sample system                              
  220. |    generations for connections to System 370 and                              
  221. |    OS/400 hosts.                                                              
  222. |                                                                               
  223. | 2. 05/26/93 Scenarios, SC316174.                                              
  224. |    Contains sample scenarios with steps to install                            
  225. |    and configure several types of networks with                               
  226. |    attached workstations.                                                     
  227. |                                                                               
  228. |                                                                               
  229. +-------------------------------------------------------------+                 
  230. |KEYWORDS: CMINFO 562125400 R100  MPU                         |                 
  231. |          GATEWAY SNAGATE COMM695 COM695 COM 695             |                 
  232. |          WORKSTATIONS NOT CONNECTING.                       |                 
  233. |          ACS1231 MSGACS1231 CM2INFO                         |                 
  234. |                                                             |                 
  235. +-------------------------------------------------------------+                 
  236.