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



On Thu, 2010-10-14 at 11:58 -0700, Albert York wrote:
I just realized it is working correctly. The number of items is 0. I
don't know what bytes 5-8 are for but I don't need them.

They have the last information stored there <grin />, just like any
bytes beyond the end of a passed parameter.

Cheers,
Terry.


Thanks,

Albert

On Thu, Oct 14, 2010 at 11:13 AM, Dennis Lovelady <iseries@xxxxxxxxxxxx> wrote:
Here is the documentation:
http://publib.boulder.ibm.com/infocenter/iadthelp/v7r0/topic/com.ibm.etools.
iseries.pgmgd.doc/evfclmst240.htm#HDRDSLST

If it's not working in accordance with documentation then it's time to get
your software support vendor involved.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Advice is what we ask for when we already know the answer but wish we
didn't."
-- Erica Jong


PARM KWD(LISTFLD) TYPE(FLDTYPE) MAX(128) +
PROMPT('Fields')
FLDTYPE: QUAL TYPE(*NAME)
QUAL TYPE(*CHAR) LEN(64) DFT(*COLHDG) +
SPCVAL((*COLHDG *COLHDG) (*TEXT *TEXT)) +
PROMPT('Description if not default')

Here is one run:

> EVAL fields :x
00000 00000001 5CD5D6D5 C5404040 40405CD5 - ....*NONE
*N
00010 D6404040 40404040 40404040 40404040 - O
00020 40404040 40404040 40404040 40404040 -
00030 40404040 40404040 40404040 40404040 -
00040 40404040 40404040 40404040 40404040 -
00050 40404040 40404040 40404040 40404040 -
00060 40404040 40404040 40404040 40404040 -
00070 40404040 40404040 40404040 40404040 -
00080 40404040 40404040 40404040 40404040 -
00090 40404040 40404040 40404040 40404040 -
000A0 40404040 40404040 40404040 40404040 -
000B0 40404040 40404040 40404040 40404040 -
000C0 40404040 40404040 40404040 40404040 -

here is another:

> EVAL fields :x
00000 0001D4E8 C6C9C5D3 C4404040 D4A84084 - ..MYFIELD My
d
00010 85A28399 8997A389 96954040 40404040 - escription
00020 40404040 40404040 40404040 40404040 -
00030 40404040 40404040 40404040 40404040 -
00040 40404040 40404040 40404040 00015CD5 -
..*N
00050 D6D5C540 40404040 5CD5D640 40404040 - ONE *NO
00060 40404040 40404040 40404040 40404040 -
00070 40404040 40404040 40404040 40404040 -
00080 40404040 40404040 40404040 40404040 -
00090 40404040 40404040 40404040 40404040 -
000A0 40404040 40404040 40404040 40404040 -
000B0 40404040 40404040 40404040 40404040 -
000C0 40404040 40404040 40404040 40404040 -

More...


On Thu, Oct 14, 2010 at 9:59 AM, Dennis Lovelady <iseries@xxxxxxxxxxxx>
wrote:
I have developed many, many commands, and several of those have
MAX( >1 )
parameter types. I have never seen the number-of-entries value
return
anything other than a 2-byte integer. In fact the help that one sees
when
pressing F1 with the cursor in the MAX field for a PARM command
reveals that
the value will be a 2-byte binary. This is at V5R3.

You might try the help on your own system; perhaps this will give you
a
hint.

Or are you possibly mixing MAX() and ELEM() values?

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Abstract Art: A product of the untalented, sold by the unprincipled
to the
utterly bewildered."
-- Al Capp
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Albert York
Sent: Thursday, October 14, 2010 11:29 AM
To: Midrange technical discussions
Subject: Command list size

I have created a command that has a parameter that allows for
multiple
items. When it is passed to my program it sometimes has 2 bytes for
the number of items and sometimes it has 4 bytes. How can I tell in
my
program which one is being used?

Thanks,

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


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


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


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




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.