Difference between revisions of "CLP/400 examples"

From MidrangeWiki
< CLP
Jump to: navigation, search
m (fix sequence)
Line 11: Line 11:
 
* [[XDSPOBJPGM]] = refresh *OUTFILE directory of [[Query]] definitions so that [[Query]] or other software can be used to see what software we have, to answer the age old question ... do we have a program or [[Query]] that does ___X?
 
* [[XDSPOBJPGM]] = refresh *OUTFILE directory of [[Query]] definitions so that [[Query]] or other software can be used to see what software we have, to answer the age old question ... do we have a program or [[Query]] that does ___X?
 
* [[XDSPGMETC]] = submit [[XDSPOBJPGM]] to JOBQ
 
* [[XDSPGMETC]] = submit [[XDSPOBJPGM]] to JOBQ
 +
* [[WHO BAD]] = identify resource hogs - jobs eating unfair share of system resources (CPU %)

Revision as of 03:19, 29 May 2005


This is intended to be a summary directory of CLP/400 programming examples ... use the links from this page to the actual source code and annotations as to what we can learn from these examples.

  • INVENGFILE = RUNQRY dump some file in whole or in part with Query, from Menu for co-workers with restricted access.
  • INVENGQRY = RUNQRY some Query definition from Menu via CLP program ... user keys in query definition of choice thanks to query being identified from one of several reference lists.
  • INVENGVIEW = CLP program uses Query to Display some range of software availability on our system, from Menu for co-workers with restricted access. This is a sample program ... we can have all sorts of focused lists, such as recently modified software, most popular software, and lots more, after you see the basic princples here.
  • SYSCMDUSNO = Display selected recent critical DSPLOG events that IT wants to know about
  • XDSPOBJPGM = refresh *OUTFILE directory of Query definitions so that Query or other software can be used to see what software we have, to answer the age old question ... do we have a program or Query that does ___X?
  • XDSPGMETC = submit XDSPOBJPGM to JOBQ
  • WHO BAD = identify resource hogs - jobs eating unfair share of system resources (CPU %)