Difference between revisions of "CLP Coding Rules"
From MidrangeWiki
m |
|||
Line 7: | Line 7: | ||
* Parentheses go around keywords and values | * Parentheses go around keywords and values | ||
** Example [[SAVLIB]] LIB(XFILES} DEV(TAP01) | ** 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 |
Revision as of 20:04, 25 June 2005
Coding rules for CLP Commands
- 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