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



Jorge,

This may or may not work in your environment, but I seem to recall that
back in my System/36 days we had a standard of putting the ?PROC?
expression into the LDA in a standard location so that we could always
reference the first level procedure.  This could then be checked from
within nested OCLs or called RPG programs.

It would only work for the first level procedure and only if you've
followed the S/36 standard of limiting your OCL procedure names to eight
characters or less.

Regards,
Andy Nolen-Parkhouse

> Subject: OCL Question - Identify Current OCL Procedure Running
>
> Hello,
>
> I am sorry for asking this question ... However somwtimes there are
> legacy applications that still need some changes.
>
> I need to find a way to identify the current OCL procedure being used
> (either in an OCL procedure or an RPG36 type program)
>
> Does anyone have a piece of shareware for this task ?
>
> Some very old OCL(s) are referencing the same RPG36 program being used
> and I need to know exactly wich of those are actually working in a
> Production Mode.
>
> I thought of using a validity checker program mover the STRS36PRC
command
> .. thje problem is that in System/36 Mode you can invoke the
procedures
> in many other ways. So that is not a perfect solution.
>
> Your advice will be appreciated.
>
> Jorge Moreno



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.