Using the PLBCMD Command


 

The PLBCMD command runs a PL/B program using a PLBWIN thread. The thread is created through the PL/B Automation Server. When the PLBCMD command is invoked, it creates a PL/B Automation Server program object and executes the Run method using the command line specified with the PLBCMD command:

 

PLBCMD -g400 test2

 

After the program command line string is passed to the Automation Server, the PLBCMD command terminates immediately even though the PL/B program continues execution by a PLBWIN thread. Program actions and all errors are reported and controlled by the PLBWIN thread being executed. The Automation Server will remain loaded and available for use after the PLBCMD command is terminated.

 

Note that the normal usage of PLBWIN to start a PL/B program as:

 

PLBWIN test3

 

causes a PLBWIN task to execute a PL/B program without using the Automation Server. This normal action remains in place to insure consistent operations with prior releases that did not provide Automation Server functionality.

 

The PLBCMD command has options that MUST begin with the ‘/’ character and MUST immediately follow the PLBCMD name on the command line. The following options are available:

 

Option

Meaning

/?

PLBCMD Help Screen

/reg[=RemoteName]

Initialize registry with optional Remote Server Name specified.

/unreg

Remove Sunbelt registry entries.

/v

Execute in a verbose mode to give additional information.

Examples:

 

Plbcmd /reg

Plbcmd /unreg

 

The ‘/reg’ option for PLBCMD registers for DCOM with an optional Remote Server name specified. The Remote Server name can be a web address or machine name.

 

 

See Also: Automation



Compiler and Runtime Options Using the PLBCGI Command