RE: Issue with embedded lists in a command -- MIDRANGE-L

Dan,

That is how I learned too back in the day. I don't create commands that often anymore so I usually work from something similar to what I want. The command I used had them in this order to help pull like elements together and make it easier for whoever came behind.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Dan Kimmel
Sent: Wednesday, January 09, 2013 12:25 PM
To: Midrange Systems Technical Discussion
Subject: RE: Issue with embedded lists in a command

You're probably right. I'm working from memory on this and it has been a
long time. I looked at some of my commands and I've always put all the
parms at the top above all the labelled groups. I learned this a long, long time
ago; parser rules change over time.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Wednesday, January 09, 2013 12:18 PM
To: Midrange Systems Technical Discussion
Subject: Re: Issue with embedded lists in a command

Hi Dan

IIRC, you CAN put ELEM groups and QUAL groups anywhere - they are
labeled, so it doesn't matter - seems I did that for some commands at RJS, as
a kind of self-documentation.

Of course, I have been wrong a couple times this year, and it's only the 2nd
week!

Vern

On 1/9/2013 11:59 AM, Dan Kimmel wrote:

Rick,

Your code is arranged incorrectly. First the CMD keyword statement, then

all the PARM keyword statements, then the tagged groups of ELEM or QUAL
or whatever referenced in your TYPE's.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Rick.Chevalier@xxxxxxxxxxxxxxx
Sent: Wednesday, January 09, 2013 10:40 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Issue with embedded lists in a command

I am working on a command that I want to have a list as one of the

parameters but I also want the parameter to contain a list as one of the
elements.

I have a code value as the first parameter. For that code value there are

four pieces of information; the code itself, a start date, an end date, and
message information. The message information is itself a list made up of the
message text, configuration text, and size text. So far so good.

Where the issue comes in is when I define the code and message as lists.

There can be up to two codes and there could be up to three message lines
for each code. When I specify the code with a max value of two (MAX(2))
and the message with a max value of three (MAX(3)) the command will not
compile and I get the error shown here. Displaying second level text didn't
tell me anything I didn't already know.

CPD0258 30 More than three levels of nesting specified for keyword

ENRCODE.

I have posted the code here http://code.midrange.com/bf8f32f019.html.

I am not seeing where the three levels are. It looks to me like just two; the

ENRCODE PARM line, and the ELEM line with ENRMSG. Can someone help
me out with what I'm missing?

Rick Chevalier
Software Solutions Development Lead
[cid:image001.gif@01CDEE54.33DB8360]
817-525-7178 (w)

________________________________
Privileged and Confidential. This e-mail, and any attachments there to, is

intended only for use by the addressee(s) named herein and may contain
privileged or confidential information. If you have received this e-mail in
error, please notify me immediately by a return e-mail and delete this e-mail.
You are hereby notified that any dissemination, distribution or copying of this
e-mail and/or any attachments thereto, is strictly prohibited.

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

Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.