RE: Telnet snafu ??? -- MIDRANGE-L

Problem ID . . . . . . . : 1016774714

Current status . . . . . : ANSWERED

Problem . . . . . . . . : Software problem data for QYCDCUSG has
been logged
. Refer to help text for addit

Service assigned number . . . . . : 91258

Answer received . . . . . . . . : Request for problem complete.
PTFs sen
t.

Original reference code . . . . . : FDC7

Description . . . . . . . . . . : Error detected in application
program

Translate table . . . . . . . . : QSYS/QB900FA00

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, July 08, 2010 12:19 PM
To: Midrange Systems Technical Discussion
Subject: RE: Telnet snafu ???

Interesting. Do a WRKPRB, 5=Display details and see if any have
"F9=Display PTFs". Basically see if it downloaded and applied a new
ptf.
Then there's DSPPTF to an out file and querying the dates...

Then again, it could be a timing coincidence and some telnet keep alive
value expired.

Glad it's resolved though.

http://www.google.com/url?sa=t&source=web&cd=3&ved=0CBkQFjAC&url=http%3A
%2F%2Fwww-01.ibm.com%2Fsupport%2Fdocview.wss%3Frs%3D0%26dc%3DDB520%26dc%
3DD900%26dc%3DD800%26dc%3DDA900%26dc%3DDA800%26q1%3DiSeries%2Bcommunicat
ions%2Butilities%2BAND%2BAS400KBXXYYZZRCH%26uid%3Dnas17e55b0674c8e82fb86
256ecc006f62dc%26loc%3Den_US%26cs%3DUTF-8%26lang%3Dall&ei=ZAc2TPKPL4SInQ
fu5pDDDQ&usg=AFQjCNFB6cMtHI97-jpKSII5oOzqD5eXQw

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: "Don Cavaiani" <dcavaiani@xxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion"
<midrange-l@xxxxxxxxxxxx>
Date: 07/08/2010 01:08 PM
Subject: RE: Telnet snafu ???
Sent by: midrange-l-bounces@xxxxxxxxxxxx

OK - so I check QSYSOPR and found this:
-------------------------------------
Message ID . . . . . . : CPI93B9

Date sent . . . . . . : 07/08/10 Time sent . . . . . . :
09:58:16

Message . . . . : Software problem data for QYCDCUSG has been logged.
Refer
to help text for additional information.

Cause . . . . . : Software generated problem determination data has
been
logged in the problem log. The problem identifier is 1016774714.

Recovery . . . : To further investigate this problem, press F14 or
use the
WRKPRB command to work with problem identifier 1016774714. Either of
these
actions may cause the problem to be reported to your service provider.
If
there is a solution to the reported problem, your service provider
may be
able to send you the solution electronically.

------------------------------------------------------------------------
-------
I then reported it through the modem, and within 5 minutes all was
working again !! Message status was then "ANSWERED", but I don't know
what actually cleared things up.

THANKS!

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Ryan
Sent: Thursday, July 08, 2010 11:09 AM
To: Midrange Systems Technical Discussion
Subject: Re: Telnet snafu ???

Nice debugging guide!

On Thu, Jul 8, 2010 at 11:04 AM, <rob@xxxxxxxxx> wrote:

I'd start here

http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/topic/rzaiw/rz
aiwdetprobtelnet.htm

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: "Don Cavaiani" <dcavaiani@xxxxxxxxxxxxx>
To: <midrange-l@xxxxxxxxxxxx>
Date: 07/08/2010 10:50 AM
Subject: Telnet snafu ???
Sent by: midrange-l-bounces@xxxxxxxxxxxx

HELP

Experiencing really strange conditions. From our local as well as
remote locations, our Mochasoft telnet client will NOT CONNECT. Yet,
this is NOT on all PCs. There are some at the local site, and some at

the remote site which remain connected and working!

In addition, I am able to ping to and connect to these PCs (both local

and remote) which are NO LONGER able to get the telnet connection to
the ISeries.

TIA
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.