Entering Performance Toolkit Subcommands from EXECs or CMS Programs

Most Performance Toolkit subcommands can be executed from within CMS programs or EXEC procedures. The interface built into Performance Toolkit for executing commands will trap the CMS command 'FCONCMD' and pass its arguments on for execution by the Performance Toolkit command handling subroutines.

Two methods are supported:

• Delayed execution of the Performance Toolkit subcommand: Execution of the command string FCONCMD FCSTACK subcmd arg1 arg2 arg3 ...

  will cause the subcommand and its arguments to be stacked in the command queue, and to be executed sequentially (first-in / first-out) like any other command entered from the command line. Execution of stacked commands will start only when the current CMS command or EXEC has ended. Most commands can be submitted and correctly executed in this way.

  Exception: commands which generate GDDM graphics may execute, but the program will require manual intervention (QUIT-function) to end the graphics program.

• Immediate execution of the Performance Toolkit subcommand: Execution of the command FCONCMD subcmd arg1 arg2 arg3 ...

  will cause immediate execution of the subcommand specified. In many cases this is what is desired (e.g. changing the screen update mode from 'UPDTCMS IMMED' to 'UPDTCMS DELAYED' in a procedure which will use full screen displays). In other cases it will not produce the desired results because:

  1. The corresponding subcommand set a flag which would cause execution of the command (e.g. selection of a specific performance display) when the program is looking for more work, or
  2. Subsequent subcommands entered with the FCONCMD interface may reset such a flag before the previous command has actually been executed.

  Use of the 'FCONCMD FCSTACK' format for delayed execution is the preferred method.