|
Hi Scott, Yes, I either declare it as type *X or as *char Len(1). Am I right in assuming that the definition in the command is merely for the compiler to do some preliminary type checking? ----- Original Message ----- From: "Scott Klement" <klemscot@xxxxxxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Tuesday, February 24, 2004 10:43 PM Subject: Re: Parameter question (long) > > Hi, > > I'm trying to reproduce this problem, but I cannot. when I try to compile > my CL program, it gives me a CPD0784, "Variable &TYPE for parameter KEYVAL > must be *CHAR minimum length 2048" > > How are you defining your CMD source so that it allows you to vary the > length of the RTNVAL(*YES) variable? Are you declaring it as TYPE(*X)? > > On Tue, 24 Feb 2004, Wim wrote: > > > > The programs I wish to use the command in, defines the variables at > > their expected length. The length parameter is passed to avoid writing > > in unknown areas. For example, the <TYPE> keyword/value combination in > > the file returns a maximum keyword length of 10 positions: > > "TYPE=PROGRAM, TYPE=FILE, etc". So I declare the &TYPE var to LEN(10). > > I now create a program that uses the command, like so: > > > > RTVQ FILE('/qopensys/etc/file.inf') KEY('TYPE') KEYVAL(&TYPE) KEYVALLEN(10) > > > _______________________________________________ > 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 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.