Article View: comp.protocols.ibm
Article #1122Re: Manual Help Needed,FAP
From: Louis Meadows
Date: Wed, 06 Jan 1993 18:38
Date: Wed, 06 Jan 1993 18:38
30 lines
1870 bytes
1870 bytes
[BOB's Question] > code that I can't seem to find the answers to. Some of these are: > What do I screw up if I accidentally send the host two consecutive > NOTIFYs? In this case, is the reception of a sense message good > enough to continue or am I hosed up from then on? (I. e, pending > my fixing that particular problem, is the rest of what I see okay?) > What do I do if the reserved bit of byte0 of the RH is set sometimes > and not others? What exactly is the meaning of the DR1 bit? > There are more. > Bob, One document you need is the old SNA format and protocol reference manual (FAP). It is IBM document number SC30-3112 file code S370-30. This document attempts to describe the SNA flow, THs, RHs, RUs, etc. Notify is a request pertaining to the reporting the status of the session initiation or temination of the LU. I would expect the host to respond to second (identical) Notify with a NSPE (Network Services Procedure error) indicating failure if the notify was from an ILU (init-self LU) or TLU (Term-self LU) Otherwise you should see a Notify -RSP with a vector key of X'03' returned. See Chapter 8. Session services under NSPE, NOTIFY. DR1 is the definate response indicator. If you can give me a trace I'll break it down for you and let you know what you need to do. Louis
Technical Details
Message-ID:
<1993Jan6.183821.16984@tandem.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!dtix!darwin.sura.net!zaphod.mps.ohio-state.edu!sdd.hp.com!elroy.jpl.nasa.gov!ames!pacbell.com!tandem!cpd.Tandem.COM!louisReferences:
<H7yVwB2w164w@campbell.Gwinnett.COM>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!dtix!darwin.sura.net!zaphod.mps.ohio-state.edu!sdd.hp.com!elroy.jpl.nasa.gov!ames!pacbell.com!tandem!cpd.Tandem.COM!louis From: louis@cpd.Tandem.COM (Louis Meadows) Newsgroups: comp.protocols.ibm Subject: Re: Manual Help Needed,FAP Message-ID: <1993Jan6.183821.16984@tandem.com> Date: 6 Jan 93 18:38:21 GMT References: <H7yVwB2w164w@campbell.Gwinnett.COM> Sender: news@tandem.com Organization: Tandem Computers Inc., Cupertino CA Lines: 30 Nntp-Posting-Host: case.cpd.tandem.com