🚀 go-pugleaf

In <APPC-L%94040516201126@AMERICAN.EDU>, Ron Ritchey <OSG0312@UNLVM.BITNET> writes:
>I have setup communications manager on 2 OS/2 machines to try to get
>APING.EXE to work. When I run APING, I get the following error
>CPI-C return code: 1, CM_ALLOCATE_FAILURE_NO_RETRY.
>OS/2 sense data: FFFF0003

There is a package available within IBM called GETSENSE which can be 
used to provide descriptions of various sense codes.  I don't know if 
it is available outside of IBM.  I used it to generate the following 
text.  What it basically says is you need to define a network node 
server for your lan and make sure all other nodes on the lan have 
connections to that network node server.

Roy Brabson

----------------------------------------------------------------------

GETSENSE version 1.0: display sense data information
  by Peter J. Schwaller (pjs@ralvm6.vnet.ibm.com)

Direct all questions about the contents of the text to:
  Dr. John Q. Walker, II   (johnq@ralvm6.vnet.ibm.com)

FFFFxxxx  Directory Function Error

Explanation:  An error occurred while performing an APPN directory
search or directory delete.

NOTE:  Products use the X'FFFF' prefix on sense codes that are product
dependent and, more importantly, are never sent.  They are only
returned on an API crossing when the architected primary and secondary
return codes do not provide adequate information and there is no
architected sense code with the required definition.

0003 No link to an APPN network node server.  No NNCP server was found
     when a TP issued an Allocate call to find the associated partner
     LU.

     This sense data indicates that a session activation failed because
     APPC could not find any link to connect it to the partner node.
     If your node is serviced by an APPN network node, this sense data
     means that your node could not contact that network node (probably
     because the link is down or defined incorrectly).

     For example, when using the OS/2 Communications Manager in your
     local node, check to see it is serviced by an APPN network node.
     If not, it means that you have not provided a valid
     DEFINE_PARTNER_LU_LOCATION together with a DEFINE_LOGICAL_LINK
     verb which specifies the link to use.  Be sure the
     DEFINE_LOGICAL_LINK verb contains a valid fq_adjacent_cp_name
     parameter and the link is either active, or defined as
     activate_at_startup(NO) (which brings it up right away, as opposed
     to when OS/2 Communications Manager is started).

     Summary: either

     -    Your node does not have a link to an APPN network node; thus
          it has no place to send the Locate RU.

     -    Your node does not have a link to the target node, where the
          searched-for LU is located.

     Examples of how this can happen:

     -    The target MAC address for the APPN network node is wrong.

     -    The data link control (DLC) was deactivated on either
          computer.

     -    APPC is not fully started yet on your local computer, and the
          links have not yet been activated.