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



Chris --

With a virtual IOP, X.25 isn't supported.

http://www-912.ibm.com/s_dir/slkbase.NSF/643d2723f2907f0b8625661300765a2a/60deb3a36421e41b862573c5004b3a92?OpenDocument

Scott

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Chris Bipes
Sent: Friday, February 25, 2011 6:18 PM
To: Midrange Systems Technical Discussion
Subject: Power 7 hardware and V.35 X25 lines

I am trying to configure a *X25 line using V.35 protocol. I can configure it ok.
CRTLINX25 LIND(TNSLIN ) RSRCNAME(CMN08) +
LGLCHLE((001 *SVCBOTH)(002 *SVCBOTH)(003 *SVCBOTH)(004 +
*SVCBOTH)(005 *SVCBOTH)(006 *SVCBOTH)(007 *SVCBOTH)(008 +
*SVCBOTH)) NETADR(87654321) EXNNETADR(*NO) +
CNNINIT(*LOCAL) ONLINE(*NO) INTERFACE(*X21BISV35) +
CNN(*NONSWTPP) X25DCE(*NO) VRYWAIT(*NOWAIT) CLOCK(*MODEM) +
LINESPEED(56000) EXCHID(056FFFFF) MAXFRAME(1024) +
DFTPKTSIZE(1024 *TRANSMIT) +
MAXPKTSIZE(*DFTPKTSIZE *TRANSMIT) MODULUS(8) +
DFTWDWSIZE(2 *TRANSMIT) ADRINSERT(*NO) IDLTMR(40) +
FRAMERTY(7) THRESHOLD(*OFF) MODEM(*NORMAL) +
LINKSPEED(48000) COSTCNN(128) COSTBYTE(128) +
SECURITY(*PKTSWTNET) PRPDLY(*PKTSWTNET) USRDFN1(128) +
USRDFN2(128) USRDFN3(128) DSRDRPTMR(6) AUTOANSTYP(*DTR) +
CTSTMR(25) RMTANSTMR(60) CMNRCYLMT(99 5) MSGQ(*SYSVAL) +
TEXT('TNS Line')

But I get this error when I try to vary it on:
--0000200E: Protocol conflict between IOA and line description TNSLIN or the protocol is not supported on this IOP.


Any ideas? I will be calling IBM Monday to open a support ticket. I can create async lines on the same hardware port and they work just fine. I have tried the X25 on both:
CMB09 576C Operational Comm Processor
LIN04 576C Operational Comm Adapter
CMN07 576C Operational Comm Port
CMN08 576C Operational V.24 Port
CMB12 2742 Operational Comm Processor
LIN05 2742 Operational Comm Adapter
CMN09 2742 Operational V.24 Port
CMN10 2742 Operational Comm Port

I do not have a V.35 cable available to hook up and test with. After I attached a V.24 cable, the port changed from Comm to V.24.

Will that make a difference.

--
Chris Bipes
Director of Information Services
CrossCheck, Inc.

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

<html>
<body>
________________________________ Scott Schollenberger Vice President, Research &amp; Development P: 610-239-9988 x305 F: 610-239-9995 E: SSchollenberger@xxxxxxxxxxxxxxxxxx [http://www.harriscomputer.com/images/signatures/HarrisSchools.gif] [http://www.harriscomputer.com/images/signatures/DivisionofHarris.gif]
100-2011 Renaissance Blvd. King of Prussia, PA 19406 www.harris-schoolsolutions.com This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged or confidential
or otherwise legally exempt from disclosure. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately
by e-mail and delete all copies of the message.
</body>
</html>

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.