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


  • Subject: Re: CEA install for 6.1.01
  • From: msassman@xxxxxxxx
  • Date: Tue, 14 Aug 2001 12:31:27 -0500

Mike,

I used to be on the PC Team of the HelpLine here at SSA GT, and Anynet was
notorious for causing headaches and nightmares. I am surprised you have been
successful with it as long as you have. Ever since the option of direct TCP/IP
was introduced in BPCS to replace EHNAPPC, everyone who has tried it seems to
agree that it performs _much_ better than EHNAPPC.  Any time anyone called the
HelpLine (now Support Center) and mentioned that they were still using
EHNAPPC/Anynet, I felt obligated to try to get them to switch to direct TCP/IP
before continuing with the call - because I knew they would be much better off.
I suggest you call the Support Center and talk to the AS/400 and PC teams about
making the switch.

Regards,
Mike Sassmann
SSA GT Quality Assurance

---------- begin original message-----------

Date: Tue, 14 Aug 2001 09:35:14 -0500
From: Mike_Cechal@fmo.com
Subject: Re: CEA install for 6.1.01

In our current environment, when we set up the CEA client, we use the EHNAPPC
transport, with the Netsoft Anynet router, so we don't need to specify the TCPIP
lib as the user lib, and we don't need to start any deamon jobs.  I thought we
would be able to use the same connection method for 6.1.01.  I'm still getting a
"Can not Start Physical Server " message when they to launch any CEA screens.

Anyone else using the Netsoft/Anynet router with 6.1.01?

I also talked to IBM tech support this AM, and they reminded me that the Anynet
router is going away as an option when they discontinue supporting regular
Client Access, in favor of Client Access Express.


"Rhonda Porte" <Porte@wesfi.com.au> on 08/13/2001 10:51:33 PM

Please respond to BPCS-L@midrange.com

To:   BPCS-L@midrange.com
cc:    (bcc: Mike Cechal/Manitowoc_WI_US/Federal-Mogul)
Subject:  Re: CEA install for 6.1.01

Hi Mike,

I would check the JOBD's and *DTAARA's in the TCPIP library.
Also when setting the workstation settings for the Client the user library MUST
be the TCPIP Library.
Hope this works.

Rhonda


>>> Mike_Cechal@fmo.com 08/14/01 04:01am >>>


We are preparing to upgrade from 6.0.02 MM to 6.1.01 MM.  I have a test
environment set up for 6.1.01, and have run the conversion programs to bring
over test data.  All the green screen stuff is working fine.  I've loaded the
6.1.01 CEA client, and figured that as long as I changed the workstation
settings to point to the new libraries, all would be fine.  Unfortunately, I
can't seem to connect to the new environment.  I keep getting various Anynet or
TCP/IP errors.  We're using the Client Access Netsoft router to connect, just
like we've been using for 6.0.02.  The PC is connecting to the AS400 with no
problem, it just doesn't want to connect to the new BPCS environment.  I'm
wondering if I'm missing something in a JOBD or INLIBL somewhere.  Any ideas?


+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.