Re: Recursive DSPPGMREF -- 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: Recursive DSPPGMREF
From: Sam_L <lennon_s_j@xxxxxxxxxxx>
Date: Sat, 1 Jul 2023 16:39:13 -0400
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>

1) I updated PGM_REFS to handle DSPPGMREF failures. You will need to recreate it.

2) I updated the readme. *Please review it.*

3) I added a sample call in pgm_refs_test.sql for PUB400 and FASTBREED. Ends up with 1800+ references.

Note: This is open source, so you are free to improve it.

On 7/1/2023 12:42 PM, tim ken wrote:

Hi,

Yes, I am testing PGM_REFS in PUB400. COM and since found this type of
error so this pgm might fail in similar kind of cases, seems error handling
is not done inside PGM_REFS considering such cases.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Recursive DSPPGMREF , tim ken

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.