Re: Calling a sub-procedure from a service program with a CL program

[Alan Shore <AlanShore@xxxxxxxx>]

Adam, Charles
thanks for your replies. When I get a couple of minutes (hopefully today,
if not, tomorrow) I will keep you posted with my attempts
MUCH appreciated



Alan Shore
Programmer/Analyst, Direct Response
E:AShore@xxxxxxxxxxx
P:(631) 244-2000 ext. 5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill

midrange-l-bounces@xxxxxxxxxxxx wrote on 11/04/2008 09:49:01 AM:

> IIRC, 6.1 includes some similar features for CL.
>
> If you're not there yet, then you're stuck with a two step process in
> order to specify the modules, service programs and/or binding
> directories to use.
>
> CRTCLMOD  MYCLLE
> CRTPGM MYPGM  MODULE(MYCLLE) BNDSRVPGM(MYSRVPGM)
>
> HTH,
> Charles
>
>
> On Tue, Nov 4, 2008 at 9:31 AM, Alan Shore <AlanShore@xxxxxxxx> wrote:
> > Thanks for your reply Adam
> > How does the program know what needs to be bound?
> > In RPGLE the binding directory is specified in the H spec
> >
> >
> >
> > Alan Shore
> > Programmer/Analyst, Direct Response
> > E:AShore@xxxxxxxxxxx
> > P:(631) 244-2000 ext. 5019
> > C:(631) 880-8640
> > "If you're going through Hell, keep going" - Winston Churchill
> >
> > midrange-l-bounces@xxxxxxxxxxxx wrote on 11/04/2008 09:15:34 AM:
> >
> > > Alan Shore wrote:
> > > > Is it possible to call a subprocedure from a service program from
> > within a
> > > > CL (or CLLE) program?
> > >
> > > Yes.
> > >
> > >
> > > > I thought CALLPRC was the thing to use, but it definitely is not
> > working.
> > > It is.  Can you be more specific about how it is not working?  Is it
> > > failing at compile, bind, or run time?
> > >
> > > Here is an example:
> > >
> > > ------- CL --------------
> > >
> > >           DCL        &message    *CHAR LEN(150)
> > >           DCL        &messageLen *INT  LEN(4)
> > >           DCL        &messageV   *CHAR LEN(1002)
> > > ...
> > >
> > >           CHGVAR     var(&message) value('Message changed to +
> > >                                           protect the innocent')
> > >           CHGVAR     var(&messageLen) value(150)
> > >           CALLPRC    prc(UTRMSTRING_makeVarying)    +
> > >                      parm((&message) (&messageLen) (&messageV))
> > > ------- CL --------------
> > >
> > > ------- Procedure prototype --------------
> > >
> > >       D*--------------------------------------------------
> > >       D* Procedure name: UTRMSTRING_makeVarying
> > >       D* Purpose:        Create a VARYING character variable to pass
to
> > RPG
> > >       D* Returns:        Trimmed length of string, < 0 if error
> > >       D* Returns:        Trimmed length of string, < 0 if error
> > >       D* Parameter:      inputString => The string to convert to
> > VARYING ...
> > >       D*                          character
> > >       D* Parameter:      inputLength => Length of the input variable
> > >       D* Parameter:      outputString => The string in VARYING
character
> > > format ...
> > >       D*                          Unpredictable results will occur if
> > > the variable ...
> > >       D*                          you pass is shorter than inputLength
+
> > 2.
> > >       D*--------------------------------------------------
> > >       D UTRMSTRING_makeVarying...
> > >       D                 PR            10I 0
> > >       D  inputString               65535A   CONST
> > >       D                                     OPTIONS(*VARSIZE)
> > >       D  inputLength                  10I 0 CONST
> > >       D  outputString              65535A   VARYING
> > >       D                                     OPTIONS(*VARSIZE)
> > > ------- Procedure prototype --------------
> > > --
> > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > list
> > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > > To subscribe, unsubscribe, or change list options,
> > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > > Before posting, please take a moment to review the archives
> > > at http://archive.midrange.com/midrange-l.
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.