Re: Command : OCL Precedence

Hi, Jerry:

My understanding is that the S/36 Environment does the following:

1. it tries the command as a "built-in" OCL command;
2. if it is not built-in, it tries it as an OCL PROCEDURE;
3. if it is neither of the above, then it tries to execute an OS/400 command with that name.

There appears to be no way to change this sequence.

So, I think you need to rename (or delete) the original OCL PROCEDURE by that name, to "un-cover" the new OS/400 command with that name.

Hope that helps?

Mark

On 10/20/2011 3:29 PM, Jerry C. Adams wrote:

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