Using filtering to control and display information

JES2 allows you to refine how certain information is displayed or processed. Using command parameters and keyword values, you can define the selection criteria JES2 is to use, and how much information JES2 should display in the message text.

Defining the Selection Criteria

To limit the type of information JES2 should look for, you can define the selection criteria JES2 is to use by specifying an asterisk or a numerical range within parentheses after the command verb, specific keyword value or part of a keyword value. For example,

$D MODULE(*),LOADMOD=HASC*

$HASP468 MODULE(HASCDAU)   ADDRESS=034DD018,ASSEMBLY=(03/08/93,
$HASP468                   13.03),ENVIRON=USER,EXITPTS=(),
$HASP468                   IBMJES2=BASE,LASTAPAR=NONE,
$HASP468                   LENGTH=0002D0,LOADMOD=HASCDAU,
$HASP468                   MACLEVEL=4,SPLEVEL=CHECK

$HASP468 MODULE(HASCDSAL)  ADDRESS=0349F358,ASSEMBLY=(03/08/93,
$HASP468                   13.03),ENVIRON=USER,
$HASP468                   EXITPTS=(31,34,48),IBMJES2=BASE,
$HASP468                   LASTAPAR=NONE,LENGTH=004CA0,
$HASP468                   LOADMOD=HASCDSAL,MACLEVEL=4,
$HASP468                   SPLEVEL=CHECK

$HASP468 MODULE(HASCXJCT)  ADDRESS=033C0090,ASSEMBLY=(04/21/93,
$HASP468                   12.27),ENVIRON=USER,EXITPTS=(),
$HASP468                   IBMJES2=BASE,LASTAPAR=NONE,
$HASP468                   LENGTH=0005B0,LOADMOD=HASCXJCT,
$HASP468                   MACLEVEL=4,SPLEVEL=CHECK
⋮

JES2 limits its search to load modules that begin with the characters HASC. It then displays a variety of information about all the modules that are assembled and linked into load modules that begins with the characters HASC.

Limiting how much information JES2 displays

To limit the amount of information JES2 should display, specify a parameter, but no keyword value for the parameter. For example,

$D MODULE(*),LOADMOD

$HASP468 MODULE(FREDXJ00)
$HASP468 MODULE(HASCDAU)   LOADMOD=HASCDAU
$HASP468 MODULE(HASCDSAL)  LOADMOD=HASCDSAL
$HASP468 MODULE(HASCDSOC)  LOADMOD=HASCDSOC
$HASP468 MODULE(HASCDSS)   LOADMOD=HASCDSS
$HASP468 MODULE(HASCGGKY)  LOADMOD=HASCGGKY
$HASP468 MODULE(HASCGGST)  LOADMOD=HASCGGST
⋮

JES2 displays only the limited amount of information you requested to see--all the module names and the load module names.

Combining techniques
You can combine both techniques to obtain information that is very specific. For example,
$D MODULE(*),LOADMOD=HASCX*,LOADMOD $HASP468 MODULE(HASCXJCT) LOADMOD=HASCXJCT
In this example, the command limits the number of modules that meet the criteria set; the module must be assembled and linked into a load module that begins with the characters HASCX. Also, the amount of information you wish to see about each module is limited to display only the load module name.

Selection filtering is not limited to display commands. For example, you may want to change the destination associated with all SYSOUT queues to class A. This could be done using the $TO JOBQ command. However, the command $TO JOBQ(*),QUEUE=A,DEST=N2 would change both the output queue and the destination associated with all SYSOUT. For keywords such as QUEUE= you must indicate whether this is being used as a filter or as a modification keyword. To do this, prefix the keyword with a "/". If you want to change all output queues to class A to have a destination of N2, enter the command $TO JOBQ(*),/QUEUE=A,DEST=N2. The "/" prefix can be used on any command to indicate that the keyword that follows is a filter. It is only required on commands where a single keyword could be interpreted as both a filter and a modification keyword. For example, to change the execution class of all CLASS A jobs to CLASS B, enter the command $TJOB(*),/CLASS=A,CLASS=B. All filter keywords must precede modification keywords. To ensure compatibility with future changes, IBM® recommends that non-display commands which use selection filtering, prefix filter keywords with the "/". This is especially important for commands issued by automation scripts.

Expanding filtering techniques

Some commands can use wild cards, the JOBMASK parameter, or the JOBQ parameter (or a combination of all three) to control the action JES2 is to take. For example, using wild cards, and the JOBQ and JOBMASK parameters, you can control the amount of jobs JES2 is to release, as shown in the next example.

$A JOBQ,JOBMASK=I*

  STC00010  $HASP890 JOB(INIT)
  $HASP890 JOB(INIT)     STATUS=(EXECUTING/IBM1),CLASS=STC,
  $HASP890               PRIORITY=9,SYSAFF=(IBM1),HOLD=(NONE),
  $HASP890               INITASID=012D
  STC00017  $HASP890 JOB(INIT)
  $HASP890 JOB(INIT)     STATUS=(EXECUTING/IBM2),CLASS=STC,
  $HASP890               PRIORITY=9,SYSAFF=(IBM2),HOLD=(NONE),
  $HASP890               INITASID=NONE
  JOB00018  $HASP890 JOB(IEBGENER)
  $HASP890 JOB(IEBGENR)  STATUS=(AWAITING EXECUTION),CLASS=A,
  $HASP890               PRIORITY=9,SYSAFF=(ANY),HOLD=(NONE),
  $HASP890               INITASID=NONE
  JOB00036  $HASP890 JOB(IBMUSERX)
  $HASP890 JOB(IBMUSERX) STATUS=(AWAITING EXECUTION),CLASS=A,
  $HASP890               PRIORITY=9,SYSAFF=(ANY),HOLD=(NONE)

In this example, JES2 releases all held jobs, started tasks, and time-sharing users whose job names begin with the character I.