|
Buck, Told you I wasn't charging on all cylinders today. I always define qualified parameters or lists in RPG as data structures, but I was having problems defining the DS for this particular parameter. It just didn't occur to me to check the incoming values in a long string as an aid to defining the DS. Worked it out now so many thanks for your help. Regards, Gerry Tucker Technicolor Distribution Services Wembley, England -----Original Message----- From: Buck Calabro [mailto:Buck.Calabro@commsoft.net] Sent: 30 October 2001 14:45 To: rpg400-l@midrange.com Subject: RE: Help needed for command lists within lists and RPGIV >Given the following portion of a command definition, how do I >define the >incoming parameter in RPGIV for the 'Period'??? > > Parm Period + > Type( EPeriod ) + > Prompt( 'Time period for log output' ) > > EPeriod: + > Elem Type( EStrTim ) + > Prompt( 'Start time and date' ) > > Elem Type( EEndTim ) + > Prompt( 'End time and date' ) > >EStrTim: + > Elem Type( *Time ) + > Prompt( 'Beginning time' ) > > Elem Type( *Date ) + > Prompt( 'Beginning date' ) > >EEndTim: + > Elem Type( *Time ) + > Prompt( 'Ending time' ) > > Elem Type( *Date ) + > Prompt( 'Ending date' ) Perhaps the easiest thing to do would be to declare it a very long character field and use a data structure to map out the individual lists. There'll be a two byte binary "element count" in front of each list. Dump the character field in hex and you'll see what I mean. --buck _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l or email: RPG400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-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.