Knowledge Base > Automation Engine and Target Systems > BS2000 > BS2000 Operating System Command

BS2000 Operating System Command

The creation, forming up and processing of a data sequence is a complex process whereby script functions and statements, as well as special objects, cooperate closely.

The following example shows the necessary definitions for the involved objects and the corresponding script statements and their reference.
The example is kept small and clear to show the principles. It demonstrates how a BS2000 Command is executed from a job and how the result is written line-by-line to the job's activation report.

	Job: SC.PROCESS.BS2000CMD

The script of the job calls the function PREP_PROCESS which prepares the processing of the data sequence. The following parameters are passed:

Name of the computer on which an event job shall be executed - in this case: C70.
Type of the event job to be executed - in this case BS2000CMD.
By specifying BS2000CMD, the job EVENT.BS2000CMD will be executed.
By default, the event jobs EVENT.BS2000.CMD, EVENT.BS2000UCON, EVENT.UNIXCMD, EVENT.UNIXFS and EVENT.WINCMD are supplied with client 0000. They can be used as they are or as a template for your own event jobs.
The third function parameter was omitted. This means that by using the default value "*" as a filter, all output lines from the console command will be taken into account.
The script variable &CMD of the event job is supplied the value /STA P.
The event job executes this command using the Login object AEADMIN.

The job EVENT.BS2000CMD will then be started.

	Job: EVENT.BS2000CMD

This is the job EVENT.BS2000CMD from client 0000 supplied by default.

It is important that in its Attributes tab, the check box "Attribute dialog" is checked. That way, the Include object ATTRDIA.BS2000 is read which normally causes the start of the Attribute Dialog.

	Include: ATTRDIA.BS2000

All attributes listed in the script of the Include can be supplied. The Attribute Dialog is not displayed because passing of the variable contents is done internally.

	Job: EVENT.BS2000CMD

Now the job can log on and the console command can execute.

The scheduled command /STA P is stored in the script variable &CMD.
SYSOUT is redirected to an output file and the command is executed.

The outfile is transferred to the Automation Engine by using the file transfer and is then available as a data sequence. The execution of the job EVENT.BS2000CMD is completed.

	Job: SC.PROCESS.BS2000CMD

The function PREP_PROCESS returns a value which is a handle for information on the data sequence that will be processed.

This value is passed to the statement :PROCESS as a start parameter. :PROCESS and :ENDPROCESS then form a processing loop which in this case, will be cycled until the end of the data sequence is reached. During each iteration, a new line of the data sequence is fetched from the memory. The function GET_PROCESS_LINE can retrieve the contents of the current line by using the current value.

In the example, the current console line is written to the activation protocol.

The :STOP statement interrupts the execution and displays the activation report.