Newer version of documentation BMC provides a newer version of the documentation for this version of the product. As a result, BMC no longer accepts comments in this space.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see bao8301.

Testing EXECs with IMFEXEC CNTL NOCMD statements


By including the IMFEXEC statement IMFEXEC CNTL NOCMD, you can write an EXEC and run the EXEC on your system without actually executing the actions specified with the following IMFEXEC statements:

  • IMFEXEC CMD
    • IMFEXEC CICSTRAN
    • IMFEXEC IMSTRAN
    • IMFEXEC SUBMIT
    • IMFEXEC RES EXIT
    • IMFEXEC RES MCMD
    • IMFEXEC RES VMCMD

See Using-the-IMFEXEC-statements for more information about these statements.

For example, you might use the IMFEXEC CMD to issue an MVS command, such as activate a VTAM terminal, in an EXEC. You can execute the EXEC and choose not to issue the MVS command by including the IMFEXEC statement in the EXEC, prior to the IMFEXEC CMD statement.

  • REXX EXEC example— IMFEXEC CNTL NOCMD
  • CLIST example— IMFEXEC CNTL NOCMD

You can track the results of the EXEC by examining the BBI-SS PAS Journal, which indicates that the MVS command was not executed because of the IMFEXEC CNTL NOCMD statement.

Example

The following is a short example of how you might use IMFEXEC CNTL NOCMD.

REXX EXEC example:

"IMFEXEC CNTL NOCMD"
"IMFEXEC CMD #V NET,ACT,ID=BB010A"

CLIST example:

IMFEXEC CNTL NOCMD
IMFEXEC CMD #V NET,ACT,ID=BB010A

The MVS command to vary VTAM terminal BB010A will not be executed when this EXEC is scheduled. In the BBI-SS PAS Journal, you will see a message that looks like the following example:

EM1101I FOLLOWING COMMAND BYPASSED DUE TO TEST   MODE:IMFEXEC CMD #V  
   NET,ACT,ID=BB010A

Related topic

 

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