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



i really don't understand the directive to have a separate module for
procs that contain a DS as a parm...sounds like adding extra maintenance
overhead to me. personally i place all related procs in a single module
not several, it just makes maintenance a lot easier. service programs
(and bound modules are NOT dynamically called. they are "bound" at
compile time. as to the whole procedure compiling. when you bind the
module1 to module 2 and accessing ALL exported procs all parms, etc need
to be defined to all modules IMO. but YMMV

Thanks,
Tommy Holden



From:
David FOXWELL <David.FOXWELL@xxxxxxxxx>
To:
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date:
02/27/2008 08:38 AM
Subject:
Service programs suck





-----Message d'origine-----
De : David FOXWELL
Envoyé : mercredi 27 février 2008 14:54
À : 'Websphere Development Studio Client for iSeries'
Objet : Service programs suck

Hi everyone,

We have this problem with 1 procedure that calls another that calls
another :


Module 1 Procedure 1 calls Module 2 Procedure 1.
Module 2 Procedure 2 calls Module 3 Procedure 1.

Module 3 Procedure 1 gets the following modification : a parameter
M3P1Parm that is a DS declared LIKE another DS in the same module. Module
2 Procedure 2 is modified accordingly.

Module 3 is recompiled, no problem.
Module 2 is recompiled, the compiler imports the protoypes of all the
exported procedures of Module 3 with the definition of M3P1Parm, again no
problem.
Module 1 is recompiled, the compiler imports the protoypes of all the
exported procedures of Module 2 : Procedure 1 that is uses, and Procedure
2 that it doesn't - PROBLEM, it doesn't know what is M3P1Parm.


Bigger problem : the policy is to systematically compile ALL the modules
that use the module modified. I realise that probably raises a few
eyebrows but that's the way things are!

Now, I am asked what I think of this way round the problem :

If an exported procedure contains a DS as a parameter then that procedure
must have its own module.

I suggest that Module 2 should be a service program and that Module 1
would not have to be recompiled.
I am reminded that we do not use service programs as they use dynamic
calls and that would mean the same as going back to RPGIII.

Any enlightenment would be greatly appreciated.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.