Implementing advanced JES support

The MainView AutoOPERATOR subsystem is always added to the subsystem vector table after the JES subsystem. Because the JES subsystem occurs in the vector table chain before MainView AutoOPERATOR, JES processes all commands and WTOs before MainView AutoOPERATOR.

However, this chapter describes what you need to do if you want to configure MainView AutoOPERATOR to

  • modify or suppress JES commands
  • modify or suppress WTOs on the JES job log

To accomplish this, you must edit and configure JESFLTR parameter in BBPARM member BBISSP00. When this parameter is used, MainView AutoOPERATOR installs a JES filter that allows MainView AutoOPERATOR to see message or command traffic before JES does.

Note

Editing and configuring the JESFLTR is required for both JES2 and JES3.

If you do not need to use MainView AutoOPERATOR to modify or suppress JES commands or WTOs, then BMC Software recommends that you omit entering this parameter in BBPARM member BBISSP00.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*