|
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 my
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:Campin's
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
COMPILE tool or the facilities of your change managementtool 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.
As an Amazon Associate we earn from qualifying purchases.
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.