RE: Checking Library List

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Au contraire, mon frere!

QCLSCAN is just a program call - nothing fancy and easily done in CL. Other 
APIs are harder to use. This is probably easier to use than QCMDEXC.

Option 2 involves standard CL techniques of looping through a string 
(sorry, character variable  <g>) with repositioning with a CHGVAR. Easier 
with pointers? Sure. Does it use GOTOs? Sure. Hard to do? No.

Your point is good but I don't think this problem is the one to hang it on.

Regards

Vern

At 08:50 AM 6/17/2003 -0500, you wrote:
> And at this point I say stop trying to force CL into the wrong slot.  Use
> a HLL for this.
>
> Rob Berendt
> --
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety."
> Benjamin Franklin
>
>
>
>
>
> Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 06/17/2003 07:51 AM
> Please respond to Midrange Systems Technical Discussion
>
>         To:     Midrange Systems Technical Discussion
> <midrange-l@xxxxxxxxxxxx>
>         cc:
>         Fax to:
>         Subject:        RE: Checking Library List
>
>
> Character search not needed. You could use QCLSCAN. But it's limited, at
> V5R1, to 999 characters in the string being searched. &USRLIBL could need
> to be 2750 on V5R1 and later. Guess you could break it up.
>
> Or take the 10-char substrings (every 11 chars) and test for equality with
>
> candidate library.
>
> Vern