× 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: No %editc in V3R2!!!
  • From: D.BALE@xxxxxxxxxxxxx
  • Date: Thu, 28 Dec 2000 16:38:00 -0500

I didn't make myself clear.  I'm sure that Aldon CMS is flexible enough to
handle activation groups, it's just that no one else here knows heads or tails
about AGs, and, at this point in time, I'm sure not going to convince anyone
that it's time to learn about AGs just so I can "properly" write subprocedures
and service programs that do the edit APIs or anything else for that matter.
The case for doing the edit was a "nice to have" not a requirement.

Yeah, it looks like I'll have to make it a subroutine for now.  Thanks for
your help.

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952

-------------------------- Original Message --------------------------

Hi Dan,

On Thu, 28 Dec 2000 D.BALE@handleman.com wrote:
>
> Scott, your example worked perfectly, except (?!?!?) that the app needs to
 be
> compiled with DFTACTGRP(*NO) ACTGRP(QILE).  Of course, you can't specify
 these
> on the H-spec in V3R2 <groan>, but only in the CRTBNDRPG command, which I
 have
> no control over in the aforementioned Aldon CMS.  I see in my v4r4 softcopy
> that the H-spec supports these but, then, if it were v4r4 I was running on,
> I'd had %editc and avoided this whole mess!  Gotta start pushing some hot
> buttons around here to upgrade!
>

Actually, it doesn't care what activation group you use, as long as it
isn't the default activation group.   You can't use subprocedures in the
default activation group.

If Aldon CMS (which I've never used) can't do any other activation group
besides default, then it is broken and Aldon should fix it.   (in my
opinion, anyway)  They have no business saying that they support RPG IV if
you can't specify activation groups.

> Actually, when I did a straight compile, I got an error message:
>      1 d EditC           PR            43A
> ======>  aaaaa
> *RNF3788 30 a  000100  Keyword EXTPGM must be specified when DFTACTGRP(*YES)
 is
>                        specified on the CRTBNDRPG command.
>
> Is there a way to specify EXTPGM for how I would like to use this
 subprocedure
> (source inline) without having to mess with compiler options?
>
> Dan Bale
> IT - AS/400
> Handleman Company
> 248-362-4400  Ext. 4952
>

No, if you want to use EXTPGM, you'd need to make the "EditC" subprocedure
into a seperate program.   This would be workable, but would not have the
source inline.  Since you can do this with RPG III programs as well,
perhaps your shop standards don't forbid it?

Perhaps a better solution is to convert it from a subprocedure into a
subroutine.  This would be a lot more awkward, hard to reuse, etc... but
it'd solve the problem.
+---
| 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 ...


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.