telnet problems

Ace

unread,

Feb 2, 2011, 10:56:59 AM2/2/11

to

Hi guys.

I have a number of customers to which I frequently have to telnet to from my AS500 running V5R4M0. Now there is one company to whom I telnet and that specific connection cannot be made. I have the following joblog:

00   02/02/11 16:40:46,585464 QTVUCLIE     QSYS        *STMT    *EXT                    *N
   From module . . . . . . . . :   QTVUUTIL
   From procedure . . . . . . :   qtvu_IssueMessage
   Statement . . . . . . . . . :   358
   Message . . . . :   Connecting to host
     ip44-226-210-87.adsl2.static.versatel.nl at address 87.210.226.44 using port
     23.
   Cause . . . . . :   The client is attempting to open a connection to the
     specified server. A subsequent message will indicate if the attempt was
     successful. Success is determined when the server sends a reply verifying
     that a connection was established.
  40   02/02/11 16:40:46,767808 QTVUWRIT     QSYS        0425     QTVUCLIE    QSYS        *STMT
   To module . . . . . . . . . :   QTVUNTOS
   To procedure . . . . . . . :   IssueWrite
   Statement . . . . . . . . . :   49
   Message . . . . :   Internal system error occurred in program QTVUWRIT.
   Cause . . . . . :   An internal error has occurred in program QTVUWRIT. The

    internal error data is CCB PTR IS NULL. Recovery . . . :   See previously
    listed messages. Contact your system administrator as required. Technical
    description . . . . . . . . :   This message is sent when an internal error
    has occurred in a VTM/FM XPF module.
40   02/02/11 16:40:46,768112 QTVUCLIE     QSYS        *STMT    QTVUCLIE    QSYS
From module . . . . . . . . :   QTVUUTIL
From procedure . . . . . . :   qtvu_IssueMessage
Statement . . . . . . . . . :   358
To module . . . . . . . . . :   QTVUCLIE
To procedure . . . . . . . :   _CXX_PEP__Fv
Statement . . . . . . . . . :   *N
Message . . . . :   Internal system error occurred in program QTVUCLIE.
Cause . . . . . :   An internal error has occurred in program QTVUCLIE. The
    internal error data is ERROR_IN_QTVUWRIT. Recovery . . . :   See previously
    listed messages. Contact your system administrator as required. Technical
    description . . . . . . . . :   This message is sent when an internal error
    has occurred in a VTM/FM XPF module.

I have another AS400 running V4R2M0. This one can make the connection without problems. Does someone of you what could be happening? You can try to set up the telnet connection. That's no problem.

Thanks

Ace

Jonathan Bailey

unread,

Feb 2, 2011, 12:24:31 PM2/2/11

to

Well I can telnet using the windows client - but I dont have access to
an
as400. Maybe there is a setting on the telnet command which you can
use with
F4 ?
Are all your host names as long as this? Maybe thats it? Try just
using the
ip address. I cant think of anything else, sorry.

--
Jonathan

CRPence

unread,

Feb 2, 2011, 1:12:08 PM2/2/11

to

On 2/2/11 7:56 AM, Ace wrote:
>
> <<SNIP>> I have the following joblog:

>
> 00 02/02/11 16:40:46,585464 QTVUCLIE QSYS *STMT *EXT *N
> From module . . . . . . . . : QTVUUTIL
> From procedure . . . . . . : qtvu_IssueMessage
> Statement . . . . . . . . . : 358
> Message . . . . : Connecting to host

> <<SNIP>>

> 40 02/02/11 16:40:46,767808 QTVUWRIT QSYS 0425 QTVUCLIE QSYS *STMT
> To module . . . . . . . . . : QTVUNTOS
> To procedure . . . . . . . : IssueWrite
> Statement . . . . . . . . . : 49
> Message . . . . : Internal system error occurred in program QTVUWRIT.
> Cause . . . . . : An internal error has occurred in program QTVUWRIT.
> The internal error data is CCB PTR IS NULL.

><<SNIP>>

Nice to see one of the better attempts at posting a joblog for having
actually included the spooled version versus print screens of an active
joblog or individual messages, however unfortunately, the message
identifiers which are of great significance were omitted in the above
quoted text. :-( From the text I might infer that the message CPF87D3
is the original exception condition; i.e. a symptom keyword string of
effectively: msgCPF87D3 F/QTVUWRIT T/QTVUCLIE TM/QTVUNTOS TP/IssueWrite
stmt/49 with RC "CCB PTR IS NULL" indicating that the Conversation
Control Block pointer is not set when the TELNET CLIENT processing
attempts to Write.

The recommended action for that condition is to apply maintenance and
if problem persists, or simply, to call for service:
http://www-01.ibm.com/support/docview.wss?uid=nas1a53b17cf8d5ed7c386256cf3006ba9d2

Some PTFs that may be relevant to STRTCPTELN issues:
http://www-912.ibm.com/s_dir/slkbase.NSF/1ac66549a21402188625680b0002037e/7f26d499f84de3f286256a3800632aee?OpenDocument&ExpandSection=12

While the quoted issue is not manifest as recorded in the following
APAR, its PTF [or its supersede listed second] may be preventive for
those symptoms as well:
http://www-01.ibm.com/support/docview.wss?uid=nas22d4e51ac5ec263a48625766b0041eeba
http://www-01.ibm.com/support/docview.wss?uid=nas3e5b9e42093ae3abf8625775100633e2a

Pending or if not applying maintenance nor contacting a service
provider... Given that condition and lack of any similar symptoms on the
Web, I would suggest looking for VLogs issued around that date\time
which might identify some lower level LIC condition giving rise to that
error being reported by the OS. Review also the telnet server
job[logs], history, and vlogs for a failed attempt to connect. Search
those symptoms [instead].

Regards, Chuck