|
Subject:
RE: Stored procedure for EIM information
From:
Rob Berendt <rob@xxxxxxxxx>
Date:
12/21/2021, 11:21 AM
To:
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
I don't see any. As my dear departed pappy used to say, that and 50 cents will buy you a cup of coffee. (He's been gone awhile.)
Tried the new navigator (recent ptf's required) athttp://myibmi:2002/Navigator It has a sql icon off to the right to see the sql behind each function. However it seems inactive on the EIM information. Then again, we've not tried to use EIM in years.
Rob Berendt
-- IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 7310 Innovation Blvd, Suite 104 Ft. Wayne, IN 46818 Ship to: 7310 Innovation Blvd, Dock 9C Ft. Wayne, IN 46818 http://www.dekko.com -----Original Message----- From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Monty G. James Sent: Tuesday, December 21, 2021 10:25 AM To: 'midrange-l@xxxxxxxxxxxxxxxxxx' <midrange-l@xxxxxxxxxxxxxxxxxx> Subject: Stored procedure for EIM information CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Is anyone aware of a stored procedure(s) that would return EIM information. I would like an existing method where that I could use an existing target ID/profile and ascertain the what source id, source domain and distinguished name that relate to it. Yes I can use existing API(s) to do this just looking a lazy way around it. ________________________________ This email message, including any attachment(s) is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is strictly prohibited. If you are not the intended recipient, please immediately contact the sender by email. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: https://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l. Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions. Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com
-- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: https://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l. Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions. Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com
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.