Automation Scripts

The DATABridge 6.2 Client service uses scripts (command files in Windows; shell scripts in UNIX) to allow the user to gain control at key points of client operations. Scripts allow the user to perform pre-processing and post-processing for client runs (typically process commands) and supplement the service's built-in error recovery with additional recovery or error-reporting mechanisms.

Additionally, users can start a script from the mainframe by using the BCNOTIFY program. The BCNOTIFY program is designed to make the service start the script whose name it supplies. By inserting BCNOTIFY at key points in a WFL (Work Flow Language) job, the WFL can trigger a task on the client machine, such as restarting audit file processing. Scripts can interact with the service via the Batch Console, a program which interprets source files that contain programs written in a language similar to Visual Basic. Scripts can also perform arbitrary tasks that may not be directly related to the service (for example, start a run that generates a report).

Automation scripts fall into two basic categories:

  • Scripts that are associated with a process command. These scripts are associated with a data source and run before or after a client run. (See Process-Related Scripts.)
  • Scripts that are initiated by the BCNOTIFY program on the mainframe. (See BCNOTIFY Initiated Scripts.)

All scripts start with the current directory set to the service’s working directory. Additionally, the service sets up the environment variable INSTALLDIR that points to the install directory where the Batch Console program resides. You must use this environment variable as the path when invoking the Batch Console (on Windows, %INSTALLDIR%\bconsole; on UNIX, $INSTALLDIR/bconsole). You cannot rely on the install directory being in the PATH. For more information about Batch Console, see Introducing the Batch Console.