× 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: Wierd Error
  • From: "Mike Silvers" <msilvers@xxxxxxxxxxx>
  • Date: Mon, 16 Jul 2001 06:29:39 -0400
  • Organization: Hainey Business Systems

Martin,

We are at V4R5.

Mike

----- Original Message -----
From: "McCallion, Martin" <MccalliM@Midas-Kapiti.com>
To: <RPG400-L@midrange.com>
Sent: Monday, July 16, 2001 6:01 AM
Subject: RE: Wierd Error


> Mike Silvers wrote:
>
> <snip>
> > I can not find ANY references to a qualified name of
> > the service
> > program, except for the error message.
>
> What OS release are you at?  I remember this sort of thing happening in
> the early days of our ILE development, but I'm pretty sure IBM fixed it
> in PTFs.  At the same time, we had to code some workarounds.
>
> Basically ILE initially appeared to override the traditional library
> list support; it used to be the case that if you moved a service program
> to a different library, calls to client programs would fail, even
> thought the library which now contained the service program was in the
> library list.
>
> Binding directories don't really affect this, as they are only used at
> compile time, but they had a similar problem in that binding directory
> entries had an explicit library name on them by default.  I think we
> worked around that be generating our main binding directory
> programmatically, and forcing each entry to contain *LIBL, thereby
> giving us back *LIBL support at compile time.
>
> If you are having this problem, then something else to watch out for,
> that we had around the same time, is your programs binding to system
> service programs that have been renamed by a temporarily-applied PTF.
> No problem, until you permanently apply the PTF, or deploy on another
> machine that doesn't have the renamed object.  The renamed objects will
> be called things like QPZA123456.
>
> HTH.  Cheers,
>
> Martin.
>
> --
> Martin McCallion
> Midas-Kapiti International
> Work:  mccallim@midas-kapiti.com
> Home: martin.mccallion@ukonline.co.uk
>
> Apologies for the length of this sig, but company policy says:
> This email message is intended for the named recipient only.  It may be
> privileged and/or confidential.  If you are not the intended named
> recipient of this email then you should not copy it or use it for any
> purpose, nor disclose its contents to any other person.  You should
> contact Midas-Kapiti International as shown below so that we can take
> appropriate action at no cost to yourself.
>
> Midas-Kapiti International Ltd, 1 St George's Road, Wimbledon, London,
> SW19 4DR, UK
> Email: Postmaster@midas-kapiti.com Tel: +44 (0)208 879 1188 Fax: +44
> (0)208 947 3373
> Midas-Kapiti International Ltd is registered in England and Wales under
> company no. 971479
>
> +---
> | This is the RPG/400 Mailing List!
> | To submit a new message, send your mail to RPG400-L@midrange.com.
> | To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-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.