FW: called program not being called

["Charles Sallee" <csallee@xxxxxxxxxxxxxxx>]

Is there any chance any of the procedures are using the LDA and it is
not formatted or populated correctly?

Chuck Sallee
CIS Manager
Lexington Division of Police
-----Original Message-----
From: Jeff Young [mailto:jyoung0950@xxxxxxxxx] 
Sent: Monday, October 01, 2012 2:56 PM
To: RPG programming on the IBM i / System i
Subject: Re: called program not being called

Sounds like the JDE pgm is stepping on memory in the other pgms.
Verify the parms being passed to it as to length and data type.
If you are passing a parm that is smaller than the value it is
expecting,
this could happen.



On Mon, Oct 1, 2012 at 2:27 PM, <wjohnson@xxxxxxxxxx> wrote:

> Thanks for responding Barbara.  The sequence of programs are:
> rpgle(crtbndrpg)  calls another rpgle(Crtdnbrpg)  which 1st call a jde
> (RPG) program , then crashes on calling the CLP program and program
also
> crashes on calling another RPGLE(crtdndrpg) program....All the crashes
> occur after calling the JDE program.......there are no RCLRSC
statements
> anywhere in this sequence.......we are in testing mode for upgrade to
JDE
> a92 in 30 days.....any more input would be greatly appreciated.......
as
> an aside,  this current sequence works just as is supposed to in the
> production envirinment...
>
> Thanks, Sj
>
>
>
> From:   Barbara Morris <bmorris@xxxxxxxxxx>
> To:     rpg400-l@xxxxxxxxxxxx
> Date:   10/01/2012 01:21 PM
> Subject:        Re: called program not being called
> Sent by:        rpg400-l-bounces@xxxxxxxxxxxx
>
>
>
> On 2012/10/1 2:16 AM, Mike Krebs wrote:
> > I think Mark might be on to something. RCLRSC and/or RCLACTGRP is
being
> run someplace and pointers are not clearing to some program? Not sure
that
> explains why qualifying the LIBRARY allows it to run correctly.
> >
>
> Since the failing case is trying to call '000' which is a different
> program name than you coded, there's something going on besides
> activation group issues. It sounds like storage corruption of the
> internal structure that RPG uses for the call. If it's not failing for
> the qualified-program case, then it's likely that the module's storage
> gets laid out a little differently, and the storage corruption isn't
> causing an error.
>
> That's assuming the program name is a literal, EXTPGM('MYPGM') or CALL
> 'MYPGM'. If it's in a variable, then likely the variable is getting
> corrupted.
> --
> This is the RPG programming on the IBM i / System i (RPG400-L) mailing
> list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
>
>
> --
> This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.