I think I see it -
Level 1 - ENRCODE is itself a simple list of type ENRGROUP
Level 2 - ENRGROUP is a mixed list
Level 3 - one element of ENRGROUP is a simple list of type ENRMSG
Level 4 - ENRMSG is a mixed list
So let's see - heh - a simple list of mixed list elements, one of which
is a simple list of another mixed list!
Anytime you specify a MAX() you are getting a simple list - maybe that
is what didn't jump out at you.
On 1/9/2013 10:39 AM, Rick.Chevalier@xxxxxxxxxxxxxxx wrote:
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?
Software Solutions Development Lead
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.