NS Configurator Logging Location Codes

CAUSE: When NETCP attempted to create a new protocol module for an existing NI, some specific data could not be read from the NMCONFIG file (PARM = 16-bit status returned by the call to nmconfgetdata).

ACTION: Use NMMGR to check and validate the NMCONFIG file. Then retry the operation. If the problem persists, see Appendix A “Submitting an SR ”A of this manual.

CAUSE: When NETCP attempted to create a new NI or a new protocol module for an existing NI, one of the following code routines was not found in the NL: the module itself, its Read Completor, or the FDDI Read Completor (PARM = 32-bit status returned by the call to hpgetsysplabel).

ACTION: Use NMMGR to check and validate the NMCONFIG file. Then retry the operation. If the problem persists, see Appendix A “Submitting an SR ” of this manual.

CAUSE: When NETCP attempted to create a new NI or a new protocol module for an existing NI, after successfully creating a Port Data Area and locating a server plabel, an error occurred while trying to create a message port for the module (PARM = 32-bit status returned by the call to create_port).

ACTION: There may be a problem with the Ports subsystem of MPE, or the system may be low on memory. If necessary, see Appendix A “Submitting an SR ” of this manual.

CAUSE: When NETCP attempted to create a new protocol module for an existing NI, after successfully creating a Port Data Area, an error occurred while trying to create a message pool for the modules message port (PARM = 32-bit status returned by the call to create_pool).

ACTION: There may be a problem with the Ports subsystem of MPE, or the system may be low on memory. If necessary, see Appendix A “Submitting an SR ” of this manual.

CAUSE: When NETCP attempted to create a new protocol module for an existing NI, after successfully creating some data structure, an error occurred while trying to add that structure's ID into the NS Registry (PARM = 32-bit status returned by the call to reg_add_entity).

ACTION: The NS registry may be full. Try stopping and restarting Transport. If the problem persists, see Appendix A “Submitting an SR ” of this manual.

CAUSE: When NETCP attempted to create a new NI or a new protocol module for an existing NI, after successfully creating a message port for the module, an error occurred while trying to send the first initialization message to it (PARM = 32-bit status returned by the call to send_msg).

ACTION: There may be a problem with the Ports subsystem of MPE. See Appendix A “Submitting an SR ” of this manual.

CAUSE: When NETCP attempted to create a new protocol module for an existing NI, after successfully creating a message port for the module and sending other messages to it, an error occurred while trying to send a Protocol Start message (PARM = 32-bit status returned by the call to send_msg).

ACTION: There may be a problem with the Ports subsystem of MPE or a bug in the Module Configurator. See Appendix A “Submitting an SR ” of this manual.

CAUSE: When NETCP attempted to create a new protocol module for an existing NI, after successfully creating a message port for the module and sending other messages to it, an error occurred while trying to send an Information message (PARM = 32-bit status returned by the call to send_msg).

ACTION: There may be a problem with the Ports subsystem of MPE or a bug in the Module Configurator. SeeAppendix A “Submitting an SR ” of this manual.

CAUSE: When NETCP attempted to create a new NI or a new protocol module for an existing NI, an error occurred while trying to create a Port Data Area for the module (PARM = 32-bit status returned by the call to create_object).

ACTION: There may be a problem with the Ports subsystem of MPE, or the system may be low on memory. It is also possible bad data in the NMCONFIG file has caused size calculations to overflow (see Control Process error 654). Check memory usage and the NMCONFIG file, and if necessary, see Appendix A “Submitting an SR ” of this manual.

CAUSE: When NETCP attempted to create a process for a general protocol module, an error occurred while trying to start the process (PARM = 32-bit status returned by the call to createprocess).

ACTION: The program file (i.e., ICMPSERV.NET.SYS) may be missing or inaccessible, or there may be a problem with the program or with the Process Management or Loader subsystems of MPE. Check that the file exists and if necessary, see Appendix A “Submitting an SR ” of this manual.

CAUSE: When NETCP attempted to create an address resolution protocol module for an existing NI, an error occurred while trying to obtain the station address of the hardware interface card used by that NI (PARM = 32-bit status returned by the call to lan_8023_station_address).

ACTION: There may be an I/O configuration problem, a Link Services problem, or a problem with the driver or its hardware. Check the configuration and the hardware and if necessary, see Appendix A “Submitting an SR ” of this manual.

CAUSE: When NETCP attempted to create a new protocol module for an existing NI, an error occurred while trying to read the pool ID for that modules message port (PARM = 32-bit status returned by the call to xp_get_pool_id).

ACTION: There may be a problem with the port_info call into the Ports subsystem of MPE. See Appendix A “Submitting an SR ” of this manual.

CAUSE: When NETCP attempted to create a new protocol module for an existing NI, after successfully creating a message port for the module, an error occurred while trying to release ownership of the port (PARM = 32-bit status returned by the call to port_control).

ACTION: There may be a problem with the Ports subsystem of MPE or a bug in the Module Configurator. See Appendix A “Submitting an SR ” of this manual.

CAUSE: When NETCP attempted to create a new protocol module for an existing NI, after successfully creating a message port for the module and sending other messages to it, an error occurred while trying to send a Bind message (PARM = 32-bit status returned by the call to send_msg).

ACTION: There may be a problem with the Ports subsystem of MPE or a bug in the Module Configurator. See Appendix A “Submitting an SR ” of this manual.

CAUSE: When NETCP attempted to destroy a protocol module attached to an NI, or the NI itself, an error occurred while trying to send a termination message to the module (PARM = 32-bit status returned by the call to send_msg).

ACTION: Resources allocated to the module were not released. There may be a problem with the Ports subsystem of MPE, a bug in the Module Deconfigurator, or the modules port may be full. If this problem occurs every time, see Appendix A “Submitting an SR ” of this manual.

CAUSE: When NETCP attempted to unbind or destroy a protocol module attached to an NI, after successfully sending a termination message to the module and awaiting a reply message, the reply received was not a termination reply (PARM = 0).

ACTION: Resources allocated to the module were not released. Another module may have unexpectedly sent a message to the reply subqueue of NETCP's Transport port, or the module which received the termination message may be confused. If this problem occurs every time, see Appendix A “Submitting an SR ” of this manual.

CAUSE: When NETCP attempted to destroy a protocol module attached to an NI, after successfully sending a termination message to the module and awaiting a reply message, a reply was received but the function code in the reply was not for a termination message (PARM = 0).

ACTION: Resources allocated to the module were not released. Another module may have unexpectedly sent a message to the reply subqueue of NETCP's Transport port, or the module which received the termination message may be confused. If this problem occurs every time, see Appendix A “Submitting an SR ” of this manual.

CAUSE: When NETCP attempted to create a new protocol module for an existing NI, after successfully creating a Compatibility Mode message port DST for the module, an error occurred while trying to form a Native Mode pointer into that DST (PARM = 32-bit status returned by the call to convert_dst).

ACTION: The DST may not have been built correctly. There may be a problem with the Ports subsystem of MPE, an addressing mismatch between the protocol module code and its Module Configurator, or a bug in the Module Configurator. See Appendix A “Submitting an SR ” of this manual.

CAUSE: When NETCP attempted to destroy a protocol module attached to an NI, after a successful termination message exchange with the module and successful release of all other resources, an error occurred while trying to purge the modules message port (PARM = 32-bit status returned by the call to purge_port).

ACTION: The module may have been unexpectedly reinvoked by another processor, or there could be a problem with ownership of the port or a bug in the Ports subsystem of MPE. If this problem occurs every time, see Appendix A “Submitting an SR ” of this manual.

CAUSE: When NETCP attempted to destroy a protocol module attached to an NI, after a successful termination message exchange with the module and successful release of all other resources, an error occurred while trying to purge the modules Port Data Area (PARM = 32-bit status returned by the call to release_object).

ACTION: The object may have already been released by MPE when the port was purged, indicating a bug in the Module Deconfigurator. Otherwise there may be a problem with the Virtual Space Management subsystem of MPE. If this problem occurs every time, seAppendix A “Submitting an SR ” of this manual.