MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » January 2013

Re: Issue with embedded lists in a command



fixed

Rick

Like maybe make each line of message be part of a qualified item? That would eliminate, I think, one level of nesting.

Did my analysis make sense? Of the nested stuff? I do see 4 in your code, if I read the docs correctly.

Later
Vern

On 1/9/2013 1:17 PM, Rick.Chevalier@xxxxxxxxxxxxxxx wrote:
Vern,

While you are correct on the definition of QUAL, John may be on to something. If I can't have the multiple lists I want maybe I can create a list of qualified elements with the parts of the QUAL the elements I am currently trying to make a list out of. Does that make sense?


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

John

I beg to differ. QUAL is for qualified names - like library/object or the
jobnumber/jobuser/jobname kind of thing that can be treated as a single
component in the parameters.

Mixed lists are created using ELEM. From the documentation -

"If a parameter's value is a mixed list, the elements of the list must be
defined separately using an Element (ELEM) statement for each element."

HTH
Vern

On 1/9/2013 12:20 PM, Voris, John wrote:
You probably do not want a "List" of elements "Elem"
You probably want a mixed list for your command parms.
That would be QUAL

http://publib.boulder.ibm.com/iseries/v5r2/ic2924/books/c415721513.htm

-
==========================================================
==-
message: 5
date: Wed, 9 Jan 2013 10:39:47 -0600
from: <Rick.Chevalier@xxxxxxxxxxxxxxx>
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)
--
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.






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact