× 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: CA/400 Cooperative Process Manager
  • From: Glenn Gundermann <ggundermann@xxxxxxxxxxxxxx>
  • Date: Mon, 07 Jun 1999 12:13:59 -0400
  • Organization: Ronald A. Chisholm Limited

Thanks Stuart!!!

Once Multimedia was uninstalled on one PC, the error went away as well.  I'm
keeping it on mine for experimentation.

Also, I found the Multimedia server through Operations Navigator just like you
said (Network, Servers, Client Access).  It was stopped.  In the properties, the
box to "Start when TCP/IP is started" is greyed out.  Why is that?  Does this
mean I would have to start this server manually after each IPL?

Is anyone using the functions of multimedia?

Glenn Gundermann
Ronald A. Chisholm Limited
Toronto

Allen, Stuart wrote:

> This is something to do with Ultimedia System Facilities.
> When doing a CA install, select Custom, and highlight Operations Navigator.
> Click details & you can de-select Ultimedia here.
>
> The error is due to a host server not being started on the 400 - cant
> remember what it is from green-on-black, but if you browse to
> Network>Services>Client access from Ops. Nav you can start it from there.
>
> Its something to do with storing & distribution of multimedia files on the
> 400 - don't know much more as we don't use it, and the CA manual is sketchy
> on it aswell.
>
> Hope this helps,
> Stuart
>
> > -----Original Message-----
> > From: Glenn Gundermann [SMTP:ggundermann@rachisholm.com]
> > Sent: Monday, June 07, 1999 2:26 PM
> > To:   midrange-l@midrange.com
> > Subject:      CA/400 Cooperative Process Manager
> >
> > Hi all,
> >
> > When starting a TCP/IP connection to the AS/400, we are getting a box
> > titled "Cooperative Process Manager" and an error message "Error
> > starting USF communications thread".
> >
> > This only happens on the clients that were fresh installed from CD.  The
> > clients that upgraded to v3.2 do not get this.  This leads me to believe
> > we are installing a new feature that we didn't have before.  I would be
> > interested to (1) know how to fix this error, and (2) know what option
> > to not install to avoid this error.
> >
> > Any and all help is appreciated.  Thanks.
> >
> > Glenn Gundermann
> > Ronald A. Chisholm Limited
> > Toronto

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


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.