Re: Trigger / 5250 / .Net -- MIDRANGE-L

× 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: Trigger / 5250 / .Net
From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
Date: Fri, 7 Jun 2024 10:08:55 -0700
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

On 6/7/24 10:07 AM, Kirk Yates wrote:

Thank you for all the help. The problem was the library list in the job description associated with the user id used for the .net connection. Once the library list was fixed and they user id changed to access the dev libraries, everything started working correctly.

That sounds like the trigger definition should be changed to use the fully qualified name of the program, rather than relying on library lists.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

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.