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



Hi All, just got back to this problem and thought I should update.

Problem is solved - it was the PTFs, so thank you Marty.

This problem led me on quiet a wild goose chase.

I had the original problem on System A - which did not have the PTFs.
I tried System B which had just been upgraded to V5R1 (MC used to work fine on 
it)
and had the PTFs - same problem!
I tried System C on V5R1 which had the PTFs and all worked fine.

System B threw me for a while until we discovered that someone had messed with 
the
Host Table and removed the domain id required by MC!

Thanks to all

Paul

Paul Tuohy wrote:

> Hi Marty,
>
> It looks as if you may have hit the nail on the head. According to the ReadMe
> for SP  SI02795 with an AS/400 running V5R1, APAR SE02365 states that, for
> product 5722SS1 I should have PTFs SI01375, SI01376, SI01377, SI01378, 
>SI01838.
>
> None of which I have. I do have PTF later then these, so does that imply that
> they are not included in a CUM?
>
> I will give an update when I get the PTFs (probably next week)
>
> Thanks all
>
> Paul
>
> "Urbanek, Marty" wrote:
>
> > There were several PTFs that had to be applied to the host. I remember
> > reading an informational APAR about it. Sorry I don't have the specifics
> > handy but I think it was doc'd either in info center or in the readme that
> > accompanied the Client Access service pack.
> >
> > -Marty




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.