1 0 Ref. F2 - VMNCP : DIAGNOSTIC CODES (Ref. F2) + _____ __________ _____ ___ __ 0 Version 3 + _______ _ 0 8 March 1982 + _ _____ ____ 0 P M Girard + _ _ ______ 0 The diagnostic codes issued by VMNCP (and also by DKNCP in the MVT system) are based on those recommended in the Transport Service specification (Ref. A6). 0 The list below covers those actually used, and explanatory comments are added where appropriate. 0 X'01' : DISCONNECT received from other end X'11' : Number busy (no ports into application) X'12' : Out of order (no response from application) X'13' : Invalid address X'17' : Network congestion (at call set-up) X'21' : Protocol error (accusation) X'22' : Timeout X'24' : Flow control error X'25' : Network congestion (during call) X'26' : Network failure (call lost) X'27' : Lost contact with Application X'28' : Transport Service failure X'29' : Call (or program) killed by operator X'2C' : RESET received from other end X'41' to X'5F': VMCF error codes (low 6 bits) X'7F' : VMCF not available X'80' to X'BF': Application-level codes (low 6 bits) X'C0' to X'FF' : Gateway codes (low 6 bits) 0 If NCP closes down the Application/NCP interface on its own initiative (without receiving a Clear Indication packet from the network), the Application will see a 'clearing cause' of X'40' accompanied by one of the diagnostic codes defined above, or possibly (while setting up an outging call) by one one the following: 0 X'33' : Line to network out of service X'34' : Invalid network address X'35' : No network resources for more calls X'36' : Invalid address in an ADDRESS messages X'37' : Protocol violation by Application X'39' : Ambiguous network address 0 Reference: + _________ 0 A6 : A Network Independent Transport Sevice (PSS User Forum Study Group 3) - VMNCP : DIAGNOSTIC CODES PAGE 1