× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Ed,

E01A is not SNA sense data, and it's not one of the common SNA failure codes
which usually start with 80nn or 81nn. It's probably an error code emitted
from Anynet and is hiding the real SNA error. Hopefully someone here who
knows more about Anynet can help....

Patrick

----- Original Message -----
From: "Ed Chabot" <echabot@marlinfirearms.com>
To: <midrange-l@midrange.com>
Sent: Tuesday, October 16, 2001 7:16 AM
Subject: RE: SNA failure


> Patrick,
> The closest I get to an error code is the reason code of X'E01A.  Is that
> the same as an error code?
>
> Ed Chabot
> The Marlin Firearms Company
> 100 Kenna Drive
> North Haven, CT 06473
> (203)985-3254
>
> -----Original Message-----
> From: midrange-l-admin@midrange.com
> [mailto:midrange-l-admin@midrange.com]On Behalf Of Patrick Townsend
> Sent: Monday, October 15, 2001 6:35 PM
> To: midrange-l@midrange.com
> Subject: Re: SNA failure
>
>
> Ed,
>
> There are two places you might look:
>
> 1) In QSYSOPR. If you find APPC failure messages take a look at the second
> level text. You might find sense data (8 bytes of hex values) or error
codes
> (4 byte hex values). If you send it up I'll try to intepret the values.
>
> 2) In the system LOG. Use DSPLOG and look for two messages right together.
> One will be a failure message (Controller BlahBlah failed...), and one
will
> be a recovery message (Recovery in progress...). Put the cursor on the
> Recovery message and press Help. The second level text normally has pretty
> useful SNA and/or link diagnostic information.
>
> Patrick
> ----- Original Message -----
> From: "Ed Chabot" <echabot@marlinfirearms.com>
> To: "MIDRANGE-L@midrange. com" <MIDRANGE-L@midrange.com>
> Sent: Monday, October 15, 2001 11:35 AM
> Subject: SNA failure
>
>
> > Message ID . . . . . . :   CPF9362       Severity . . . . . . . :   20
> > Does anyone know where to find a list of reason codes for APPC failures?
> We
> > are using SNA over TCP/IP to connect to a Perle 494 controller at
another
> > site.  We started getting this message last Thursday and we got it again
> on
> > Saturday.  This whole communications thing is new to us and we aren't
sure
> > where to start looking.  Any help is greatly appreciated.
> >
> > Message type . . . . . :   Diagnostic
> > Date sent  . . . . . . :   10/13/01      Time sent  . . . . . . :
> 00:20:06
> >
> > Message . . . . :   Session ended on device PRT04HR because of an APPC
> > session
> >   failure on device C494E01.
> > Cause . . . . . :   The remote workstation device PRT04HR was using
> advanced
> >   program-to-program communications (APPC) device C494E01 for
> > communications.
> >   The current session for the remote workstation device was ended due to
> an
> >   APPC session failure. The reason code is X'E01A'.
> > Recovery  . . . :   Automatic recovery is in progress. If the problem
> >   persists, check for related messages in the system operator message
> queue
> >   using the Display Message command (DSPMSG), the job log of the QLUS
> >   subsystem using the Display Subsystem command (DSPSBS), and in the job
> log
> >   of the subsystem that handles requests that come from device C494E01
> using
> >   the Display Subsystem command (DSPSBS). If any errors are indicated,
> > attempt
> >   the recovery suggested by those messages.
> >  Technical description . . . . . . . . :   Some reason codes and their
> >    associated meanings are:
> >      400A -- APPC Device Description was varied off
> >      C00B -- Internal failure which caused partial damage
> >      E015-E01A, -- SNA Failure
> >      E020-E022, -- Hardware Failure
> >
> >
> > Ed Chabot
> > The Marlin Firearms Company
> > 100 Kenna Drive
> > North Haven, CT 06473
> > (203)985-3254
> >
> > _______________________________________________
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> > To post a message email: MIDRANGE-L@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > or email: MIDRANGE-L-request@midrange.com
> > 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@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> 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@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.