Re: Target release when recreating triggers via CRTDUPOBJ? -- 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.

Clarification: I compiled the program with TGTRLS(V7R1M0) on V7R3 ...

> On 5/18/2018 3:01 PM, Mark S Waterbury wrote:

David,

I compiled a small program, then did a CRTDUPOBJ to another program name, and when I issue a DSPPGM against the second program, it shows the very same information for:

Earliest release that program can run . . .

I tried doing a CRTDUPOBJ on V7R3 against a PF with a trigger attached, with the TRG(*YES) parameter specified, and DSPFD of the new file shows that it has a trigger, and it has the same name as the original trigger program, with the new library name, but it did not duplicate the actual trigger program.

Does this "feature" not fully work the same way for triggers defined via ADDPFTRG, but perhaps only for triggers defined via SQL DDL?

Mark S. Waterbury

> On 5/18/2018 1:10 PM, David Gibbs wrote:

Folks:

Anyone know if there is a way to control the target release on trigger programs that are created when doing a CRTDUPOBJ on a physical file.

(short of changing command defaults)

Thanks!

david

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.