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

Rats
maybe I need a vacation
A CLLE program uses the command CRTBNDCL, but I cannot see a parameter for
binding directory
Is it time for some new glasses (new eyes, new brain, vacation (permanent
or otherwise))?

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 01:18:14 PM:

Thanks for your reply Charles
I had already thought of that.
What I may end up doing is probably creating an RPGLE program using this
sub procedure and have the cl program call that instead.
NOT the way I want to go, but changing the MKS parameters here, involves

lot of read tape, AND I KNOW that I will be asked "why not use an RPG
program to call etc. etc.

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 12:53:51 PM:

If David doesn't jump into this within the next two minutes or so...

Call MKS.

I'd be willing to bet you're doing something wrong.

We use Aldon, and when you specify object type *PGM attribute RPGLE or
CLLE, there's also an extended attribute of type BND or ILE. If you
use BND, then the CRTBNDxxx commands are used. If you specify an
attribute of ILE, the CRTPGM command is used. (Note that
techinically, the attribute of RPGLE/CLLE doesn't apply to a true ILE
program, Aldon lets you put it there, but it has no effect)

Charles

On Tue, Nov 4, 2008 at 11:38 AM, Alan Shore <AlanShore@xxxxxxxx> wrote:

I have found that missing parameter is causing me a headache
We use MKS implementer and for a CL (or CLLE) program, it

automatically

uses the CRTCLPGM command
Cannot apply the BNDDIR
For the moment, I am stumped

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

"Jeff Crosby"
<jlcrosby@dilgard
foods.com>

To

Sent by: "'Midrange Systems Technical
midrange-l-bounce Discussion'"
s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx>

cc

11/04/2008 11:31

Subject

AM RE: Calling a sub-procedure

from

a

service program with a CL

program

Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>

I always thought there should be a BNDDIR parm on the CRTBNDCL

command.

--
Jeff Crosby
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com

The opinions expressed are my own and not necessarily the opinion of

company. Unless I say so.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vern Hamberg
Sent: Tuesday, November 04, 2008 9:57 AM
To: Midrange Systems Technical Discussion
Subject: Re: Calling a sub-procedure from a service program
with a CL program

There is also a BNDDIR parameter on CRTPGM - since you
already use a binding directory in RPGLE, use that parameter

If you are building it with modules, then the MODULE
parameter just takes care of it. As Adam suggests.

Adam Glauser wrote:

Alan Shore 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

So far I've been using the BNDSRVPGM and MODULE parameters on the
CRTPGM command. However, it is probably better to use Alan

Campin's

COMPILE tool or the facilities of your change management

tool if you have one.

--
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.

--
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.