Ansicht
Dokumentation

CPI5905 - Incoming call request on line &23 rejected. ( OS/400 )

CPI5905 - Incoming call request on line &23 rejected. ( OS/400 )

General Material Data   Vendor Master (General Section)  
This documentation is copyright by IBM.
SAP E-Book


Message : CPI5905
Incoming call request on line &23 rejected.

Message Long Text :

Cause . . . . . : An X.25 incoming call request with protocol identifier &41 was received from the remote system at X.25 network address &40 and was rejected by the local system. The following may have caused the problem:
-- Controller description not varied on.
-- Controller description is asynchronous but is not included in the switched controller list (SWTCTLLST parameter) of line description &23.
-- Controller description already in use.
-- Controller description does not exist.
-- One or more asynchronous X.25 controller descriptions in the switched controller list have the PAD emulation (PADEML parameter) specified *YES.
Recovery . . . :
If this call request was intended for asynchronous support:
Find the controller description with a connection number (CNNNBR parameter) value of &40 or *ANY.
If you cannot find the controller description, create one and use the Change X.25 Line Description (CHGLINX25) command to add the controller description to the SWTCTLLST parameter. Then vary the controller description on (VRYCFG command). Try the call again.
If you found the controller description, determine its status (WRKCFGSTS command). If it is VARIED OFF, vary it on. If it is ACTIVE, wait until the controller description is no longer in use. Try the call again.
If the controller description is VARY ON PENDING, display line description &23 (DSPLIND command). If the SWTCTLLST line description parameter does not include the controller description, verify the controller can use that line and add the controller description to the SWTCTLLST parameter. Try the call again.
If all asynchronous X.25 controllers are VARY ON PENDING, verify the PADEML parameter is specified *NO on the controller descriptions. If not, change the PADEML parameter to *NO.
See the X.25 Network Support book, SC41-5405, for a list of supported protocol identifiers. If this call was intended for the QTCP or QOSI subsystem, verify the protocol identifier is correct.
If the call was intended for a user-defined protocol application, determine if the application needs to be started. Ensure the network controller and device used by the application are active using the WRKCFGSTS command. Try the call again.
If this call request was intended for SNA support, the received protocol identifier was not correct.
Otherwise, report the problem (ANZPRB command).
Technical description . . . . . . . . : The reason code is &48.
00000400 -- An asynchronous protocol identifier (the first byte in the Call User Data Field in the X.25 Incoming Call Packet) was received, but the proper controller description with a network address of &40 either does not exist on the system, or exists but is not in VARY ON PENDING status or is not included in the SWTCTLLST parameter of the line description.

Message File : QCPFMSG
Library Message File : QSYS2924


rdisp/max_wprun_time - Maximum work process run time   Vendor Master (General Section)  
This documentation is copyright by IBM.

Length: 3259 Date: 20240424 Time: 212731     sap01-206 ( 3 ms )