Difference between revisions of "CLP Coding Rules"
From MidrangeWiki
| Line 3: | Line 3: | ||
[[Category:Commands]] | [[Category:Commands]] | ||
== Coding rules for [[CLP]] Commands == | == Coding rules for [[CLP]] Commands == | ||
| + | These rules apply both on [[Command Line]] and inside a [[CLP]] program. | ||
| + | |||
* Blank space separates parts of a command | * Blank space separates parts of a command | ||
** Example [[WRKOUTQ]] QFISCAL* to get at list of all [[OUTQ]] whose name starts with QFISCAL | ** Example [[WRKOUTQ]] QFISCAL* to get at list of all [[OUTQ]] whose name starts with QFISCAL | ||
Revision as of 20:09, 25 June 2005
Coding rules for CLP Commands
These rules apply both on Command Line and inside a CLP program.
- Blank space separates parts of a command
- Parentheses go around keywords and values
- Example SAVLIB LIB(XFILES} DEV(TAP01)
- Slash connects parts of a qualified name or path name
- Example WRKOBJ XFILES/UFOS
- Single apostrophe indicates beginning and end of a quoted character string (a constant)
- Example SNDMSG MSG{'Intruder Alert'} TOUSR(QBOSS)
- *N is a place holder (take the defaults) indicating the absense of a positional parameter
- Example RUNQRY *N LOG
- Predefined values begin with an asterisk and indicate IBM-defined values which are reserved by OS/400 and may be used in programs to have those set functions
- Example SAVLIB LIB(*ALLUSR} DEV(*SAVF)
- Generic name contains one or more characters that are those that start some object(s) then end in asterisk to signify wild card list of all that share that prefix
- Example DSPF*
