|
OK, that makes more sense. I thought you were just using the command itself and it had that as a special value. But, yeah you are right, PARM is just a CL command and has help like all the rest. Mark midrange-l-bounces@xxxxxxxxxxxx wrote on 08/20/2004 04:51:19 PM: > Actually, > > I'm looking at the source for the command itself. One of the parameters was > defined: > Parm FILE Q0001 + > Min( 1 ) + > File( *UNSPFD ) + > Choice( *NONE ) + > Prompt( 'File' ) > > > The *UNSPFD isn't mentioned in the CL programming manual. However, as Doug > suggested, the online help for the PARM command provides more detail > including all possible values for the FILE parameter of the PARM command ;-) > > Charles > > > > -----Original Message----- > > From: Mark Phippard [mailto:MarkP@xxxxxxxxxxxxxxx] > > Sent: Friday, August 20, 2004 4:42 PM > > To: Midrange Systems Technical Discussion > > Subject: Re: Writing Commands, how-to manual where? > > > > > > A command keyword is whatever the writer of the command wants > > it to be. It > > isn't something IBM could document (unless its their command > > in which case > > it should be in the docs for that command). > > > > As someone else pointed out, ideally there would be F1 help > > on the parm to > > explain the special values. > > > > Mark > > > > midrange-l-bounces@xxxxxxxxxxxx wrote on 08/20/2004 04:25:35 PM: > > > > > All, > > > > > > While the CL programming manual has a section about > > defining your own > > > commands. It doesn't seem to go into much detail. > > > > > > For example, I downloaded some code that had the following > > keyword for > > one > > > of the parameters: FILE(*UNSPFD). > > > > > > While the CL programming manual mentions the FILE keyword, > > it doesn't > > tell > > > me what the *UNSPFD means or what the other options may be. > > > > > > Is there another source for this info? > > > > > > > > > ______________________________________________________________ > > _______________ > > Scanned for SoftLanding Systems, Inc. by IBM Email Security > > Management Services powered by MessageLabs. > > ______________________________________________________________ > > _______________ > > -- > > 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. > > > -- > 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. > > > _____________________________________________________________________________ > Scanned for SoftLanding Systems, Inc. by IBM Email Security Management > Services powered by MessageLabs. > _____________________________________________________________________________ _____________________________________________________________________________ Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs. _____________________________________________________________________________
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.