RE: Communication problem

I have seen Internal system Failure message on comms before.  I have
found that either an IPL (sounds like Windows) or a reset of the IOP
will solve the problem.
cjg

Carl J. Galgano
EDI Consulting Services, Inc.
550 Kennesaw Avenue, Suite 800
Marietta, GA  30060
(770) 422-2995 - voice
(419) 730-8212 - fax
mailto:cgalgano@ediconsulting.com
http://www.ediconsulting.com
AS400 EDI, Networking, E-Commerce and Communications Consulting and
Implementation
http://www.icecreamovernight.com
Premium Ice Cream Brands shipped Overnight
FREE AS/400 Timesharing Service -
http://www.ediconsulting.com/timeshare.html
"You ain't gonna learn what you don't want to know" - rw


-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com] On Behalf Of
steven.donnellan@simonjersey.com
Sent: Friday, May 17, 2002 7:10 AM
To: Midrange-L@midrange.com
Subject: Communication problem


This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
We have a modem which dials in to the BACS network here in the UK.  It
is now not connecting and I get the following message on QSYSOPR;
Message ID . . . . . . :   CPA5877       Severity . . . . . . . :   99
Message type . . . . . :   Inquiry
Date sent  . . . . . . :   17/05/02      Time sent  . . . . . . :
11:56:50

Message . . . . :   Contact not successful on controller BACS. Internal
syst
  failure. (C R)
Cause . . . . . :   The system cannot establish contact with controller
BACS
Recovery  . . . :   Do one of the following:
    -- Type C to cancel recovery and to inform any applications that are
  waiting for an operation that the recovery has been canceled.
    -- Type R to try the operation one more time.
    If the problem continues, press F14 to run problem analysis. In
addition
  try varying the controller off and then on again using the Vary
  Configuration (VRYCFG) command.
Possible choices for replying to message . . . . . . . . . . . . . . . :
  C -- Cancel.
  R -- Try again one more time.
Technical description . . . . . . . . :   The exchange identifier (XID)
is

  *NOID. The error code is X'42001274': Internal system failure. The
X.25

  cause code is: *N (X.25 cause code not specified). The X.25 diagnostic
code
  is: *N (SNA: X.25 diagnostic code not specified), (CCITT/ISO: X.25
  diagnostic code not specified).
    For more information on XIDs, see Systems Network Architecture
Formats,
  GA27-3136.
    For more information on X.25 cause codes and diagnostic codes, see
the

  X.25 Network Support book, SC41-5405.

Another application that uses the same modem is generating 'Controller
not contacted' messages. I changed the modem over so that our ECS line
pointed to it.  Sent a test service request to IBM and it worked! Any
suggestions



Steven Donnellan
AS/400 Systems Manager
IBM Certified Specialist - AS/400 Professional Operator
Simon Jersey Ltd

http://www.simonjersey.com

**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error please delete it
immediately and notify the sender, do not discuss or disclose the
contents. The views expressed in the e-mail are those of the author and
not necessarily those of Simon Jersey Limited.
**********************************************************************
--



_______________________________________________
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.