Scripts on Windows

In Windows, Control-M/Agent can run any type of job scripts (such as vbs, perl, DOS bat or cmd, Rexx, etc). To correctly implement scripts for Windows, you need to consider the following:

• Comply with script rules: As part of the post processing of a job, you must do the following to scripts analyzed by Control-M/Server:
  • Begin the script with the echo on command, which ensures that job script statements are written to the output file.
  • End each prompt with the > or ] character. These characters and embedded spaces should not be used inside the prompt text string.
• Use On Statement/Code parameters: Control-M/Agent can use the On Statement/Code job processing parameters to perform post-processing analysis of the output of jobs that are submitted by using these scripts. The following items describe how the On Statement/Code job processing parameter interprets script lines:
  • On Statement/Code output: Text in an output file that follows a > prompt or ] prompt is treated by Control-M/Server as part of the job script. All other text is treated as part of the operating system response. When specifying an On Statement/Code statement (format 1) in a job processing definition, place text that follows either of these prompts in the Stmt parameter. Place other text in the Code parameter.
  • Continuation Lines: Control-M/Server does not process continuation lines for comparison with text in a Stmt sub parameter. Therefore, do not specify script continuation line text in the Stmt sub parameter.
  • Length of script statement: Control-M/Server compares the first 512 characters of a script statement with the text in sub parameter Stmt. Therefore, in subparameter Stmt, do not specify text that comes after the first 512 characters of a script statement. The maximum length of the On Code parameter is 255 characters.

  For more information about the On Statement/Code parameters, see On/Do Actions.

• Enable Control-M/Server to distinguish between exit codes: Both DOS .bat scripts and REXX .cmd scripts can return an exit code to Control-M/Server upon completion. The _exit utility described is used by .bat scripts. For more information about enabling Control-M/Server to distinguish between exit codes, see Using different exit codes for Control-M/Server.
• Use script utilities: The_exit and _sleep utilities can be accessed from within job scripts. For more information, see Control-M/Agent utilities.
• Translate DOS files and REXX scripts to UNC, as described in Translating DOS files and REXX scripts to UNC.