Re: WEIRDNESS in list parameter in CL program:

James,

The reason your approach won't work is because a list parameter as the number of entries in the list as a 2 byte integer at the beginning of the variable. So, for your situation you could try something like this:

Dcl Var(&ListParm) Type(*Char) Len(162)
Dcl Var(&NbrEnt) Type(*UInt) Len(2) +
Stg(*Defined) DefVar(&ListParm 1)
Dcl Var(&UserLst) Type(*Char) Len(160) +
Stg(*Defined) DefVar(&ListParm 3)

I know I've done something like this in the past, but I can't find my exact example right now. I pulled this definition from an article by Bruce Vining on www.mcpressonline.com.

Dean Eshleman
Software Development Architect

Everence Financial
1110 North Main Street
PO Box 483
Goshen, IN 46527
Phone: (574) 533-9515 x3528
www.everence.com<http://www.everence.com/>



On 2015-02-04 7:23 PM, James H. H. Lampert wrote:> I have a CL program that calls GRTOBJAUT, passing a variable in the

USER parameter.

If I format the variable I'm passing as CHAR(175) passing up to 16 user
profiles, space-delimited (the way I would enter it on a command line,
e.g., "FOO BAR BAZ ABCDEFGHIJ CORGE"), then it rejects it, taking "FOO
BAR BA" as a single list entry.

If I format the variable I'm passing as CHAR(160) passing up to 16 user
profiles aligned on 10-byte boundaries, it STILL rejects it.

What does it want?!?

HELLLLLPPPPPP MEEEEEEEEEEEE!

--
JHHL

______________________________________________________________________
Confidentiality Notice: This information is intended only for the individual or entity named. If you are not the intended recipient, do not use or disclose this information. If you received this e-mail in error, please delete or otherwise destroy it and contact us at (800) 348-7468 so we can take steps to avoid such transmission errors in the future. Thank you.