RE: Command : OCL Precedence

All replies were logical and reasoned. As I mentioned, the OCL is rampant
throughout the 36EE procedures that invoke most of our applications. My
intent is to replace its functions of the OCL procedure with a CL invoked by
a command. To qualify the command it would be necessary to update hundreds
of OCL procedures; not a welcome option.

The only option that I was able to come up with was to delete/rename the
offending OCL procedure. Then the application OCLs, which simply have the
line TEST as the first line, would find only the command that I wrote. For
example, procedure ORDENT01 might read:

TEST
// LOAD PGMA
// FILE NAME-HEADER..........
// etc.
// RUN

What TEST does or why I want to replace it with a CL isn't relevant.
Suffice it to say that the software house that moved the applications to the
AS/400 years ago from a S/36 couldn't find their collective butts with both
hands.

Jerry C. Adams
IBM i Programmer/Analyst
History teaches us that men and nations behave wisely once they have
exhausted all other alternatives. -Abba Ebban
--
A&K Wholesale
Murfreesboro, TN
615-867-5070


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rich Loeber
Sent: Thursday, October 20, 2011 2:57 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Command : OCL Precedence



Jerry,

I'd replace the TEST OCL with a single statement that calls your
native command.  Easy way out.

Rich Loeber
Kisco Information Systems
http://www.kisco.com
SDG
-------------------------

Quoting "Jerry C. Adams" <midrange@xxxxxxxx>:

I just ran a test in which I am trying to replace a ubiquitous OCL

procedure

with an equivalent IBM i command.  Because the OCL is in just about every
other OCL procedure, I gave the command the same name (say, TEST).  But if

I

key TEST on the command line, it retrieves and runs the 36EE OCL.  I
couldn't find anything in the CHGS36 command that would allow me to change
the precedence whereby the system would look for an IBM i command *before*
it reverted to OCL procedures/commands.  Is there any way to change the
precedence?



Thanks.



Jerry C. Adams

IBM i Programmer/Analyst

No man can have in his mind a conception of the future, for the future is
not yet.  But out of conceptions of the past, we make a future. -Thomas
Hobbes

--

A&K Wholesale

Murfreesboro, TN

615-867-5070



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