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


  1.  Home
  2. MIDRANGE-L
  3. November 2008

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

Jeff,

For the last time.....

YOU SHOULDN"T HAVE TO CHANGE ANYTHING IN MKS ITSELF!!!!

You simply need to define the objects to MKS correctly.

Instead of telling MKS you want a CLLE *PGM object, tell it you want a
CLLE *MODULE.

Next, tell it you want an additional object ILE *PGM. I don't know
how to do this with MKS, with Aldon, there's an "Extended Attribute"
that I set to ILE.

This is what I'd see in Aldon:
Object Type Attribute
MYCLLE *MODULE CLLE
MYCLLE *PGM

If it's not obvious, the RTFM or call MKS.

Charles

On Tue, Nov 4, 2008 at 2:01 PM, Alan Shore <AlanShore@xxxxxxxx> wrote:

Hi Jeff
Thanks for your reply
I was already contemplating changing the type
In my rush to try and get this change through I obviously have not
explained things very well at all
I CAN change the type to CLLE, but that type uses the command CRTBNDCL
As you and many others have said, use CRTCLMOD command, then use the
CRTPGM command with the BNDDIR parm to create the program.
However, we use MKS implementer that is set up to use the CRTBNDCL command
Others have therefore suggested changing the parameters for MKS. Which
makes sense.
However, to change the parameters here,for MKS involves quite a lot of red
tape, and I know that I'm going to be asked why I don't just create an
RPGLE program that uses the sub procedure, that the CL program can call



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:36:37 PM:

Alan,
Is there any reason that you can not change the source type from CLP
to CLLE and compile it using the CRTCLMOD command, then use the
CRTPGM command with the BNDDIR parm to create the program?
This will allow you to use the CALLPROC command to access the
service program procedure.

Thanks,

Jeff Young
Sr. Programmer Analyst
IBM -e(logo) server Certified Systems Exper - iSeries Technical
Solutions V5R2
IBM Certified Specialist- e(logo) server i5Series Technical
Solutions Designer V5R3
IBM Certified Specialist- e(logo)server i5Series Technical
Solutions Implementer V5R3







----- Original Message ----
From: Alan Shore <AlanShore@xxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, November 4, 2008 1:18:14 PM
Subject: Re: Calling a sub-procedure from a service program with a CL
program


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
a
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
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:

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.
--
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 thread ...
Follow-Ups:
Replies:
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.