|
The question now is: How do you program the CHOICEPGM to do what I asked in my original posting. Dare ----- Original Message ----- From: <vhamberg@attbi.com> To: <midrange-l@midrange.com> Sent: Friday, July 19, 2002 12:07 PM Subject: Re: Programming Command - CMD > There is a way to get a list of items for a prompt. It > works on an F4. You specify CHOICE(*PGM) CHOICEPGM > (lib/pgm) on the parameter. > > Only problem might be, that this program does not get > all the parameter values - it's limited to the parameter > for which you specified it. > > I don't know if a prompt override could do anything here. > > There's also a command exit point that, I think, is run > before even the validity checker. But the command has > not been displayed yet, so you'd need some way to > display the choices and then give the user a way to > select one. Maybe an inquiry message listing the > choices, then take the response and compare against the > list. > > Fiona, > > > > My original posting indicate "No SUBFILE". Thanks 4 ur input. > > > > Dare > > > > ----- Original Message ----- > > From: <fiona.fitzgerald@notes.royalsun.com> > > To: <midrange-l@midrange.com> > > Sent: Friday, July 19, 2002 11:34 AM > > Subject: Re: Programming Command - CMD > > > > > > > > > > To be dynamic, you are going to have to look up the files within a library > > > at the time of prompting. > > > I agree that it would be a waste of time to hardcode filenames, > > > but the only way I can suggest of achieving a promptable list is to have > > > the command > > > prompt the user if the second parameter is blank - perhaps cued by a > > > validity checker pgm ? > > > > > > Then your prompt pgm will receive the library parm, > > > populate a file list from this (PFs only ?) > > > and present the user with a list of possible files. > > > Why not use a subfile for this - isn't that what they're for ? > > > Best of luck, commands are fun, > > > > > > Fiona > > > > > > _______________________________________________ > > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > > list > > > To post a message email: MIDRANGE-L@midrange.com > > > To subscribe, unsubscribe, or change list options, > > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > > > or email: MIDRANGE-L-request@midrange.com > > > 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@midrange.com > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > > or email: MIDRANGE-L-request@midrange.com > > 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@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > 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.