Using command line arguments

You can log in PowerBuilder from a command line (or the Windows
Run dialog box) if you have an online license for PowerBuilder.

The syntax is:

directorypb190.exe {/AC useraccount} {/PW password} {/RC value} {/ALS value} {/SOE value}

1	directorypb190.exe {/AC useraccount} {/PW password} {/RC value} {/ALS value} {/SOE value}

directorypb190.exe {/LIF loginfile}

1	directorypb190.exe {/LIF loginfile}

where directory is the fully qualified name of the directory
containing PowerBuilder.

For example,

pb190 /AC test@appeon.com /PW xxxxxxx /RC N /ALS N /SOE Y

1	pb190 /AC test@appeon.com /PW xxxxxxx /RC N /ALS N /SOE Y

pb190 /LIF c:	est.ini

1	pb190 /LIF c: est.ini

Option	Description
/AC	User Account.
/PW	User Password.
/RC	Remember Credentials (Y or N), default is Y. /RC is always Y when /ALS is Y. Therefore, the /RC value will be ignored, if /ALS is set to Y. This parameter takes effect only when both /AC and /PW are set.
/ALS	Auto Login at Startup (Y or N), default is Y. This parameter takes effect only when both /AC and /PW are set.
/SOE	Sign Out on Exit (Y or N), default is Y. This parameter takes effect only when both /AC and /PW are set.
/LIF	The full path to the license login initialization file which contains your encrypted password and other login settings. The file is created by an independent tool (%AppeonInstallPath%PowerBuilder [version]ToolsLoginIniFileCreator.exe). You can specify the user account, the password, the login settings, and the file path in this tool. The password will be encrypted in the generated file to protect your login credentials. (If you want to copy the tool to other places, make sure to copy the executable file as well as the msvcp100.dll and msvcr100.dll files under the same folder).

You can also start PowerBuilder from a command line and
optionally open a workspace, target, and/or painter. These are the
painters and tools you can open:

Application painter
Database painter
Data Pipeline painter
DataWindow painter
Debugger
File Editor
Function painter
Library painter
Menu painter
Query painter
Structure painter
User Object painter
Window painter

The syntax is:

directorypb190.exe {/workspace workspacepath} {/target targetpath} {/painter paintername} {/output outputpath}

1	directorypb190.exe {/workspace workspacepath} {/target targetpath} {/painter paintername} {/output outputpath}

where directory is the fully qualified name of the directory
containing PowerBuilder.

You can also add one or more of the following options to the
command line after /painter paintername to open a specific object or
create a new one:

{/library libraryname} {/object objectname} {/inherit objectname} {/new} {/run} {/runonly} {/argument arguments}

1	{/library libraryname} {/object objectname} {/inherit objectname} {/new} {/run} {/runonly} {/argument arguments}

The syntax statements show the long form of option names. You
need only use the initial letter or letters of the option name as long
as the option is uniquely identified, as shown in the following
table.

Option	Description
/W workspacepath	Opens the workspace workspacepath. The default is the most recently used workspace if you have selected the Reopen Workspace on Startup check box in the System Options dialog box. If you have not selected this check box, you must specify the /W option before specifying any other options.
/T targetpath	Opens the target targetpath.
/P paintername	Opens the painter paintername. The default is the window that displays when you begin a new PowerBuilder session. The painter name must uniquely identify the painter. You do not have to enter the entire name. For example, you can enter q to open the Query painter and datab to open the Database painter. If you enter the full name, omit any spaces in the name (enter UserObject and DataPipeline, for example). The painter name is not case sensitive. To open the file editor, you could set paintername to FI or fileeditor. Except for the /W, /T, and /L switches, other switches must follow /P paintername on the command line, as shown in the examples after the table.
/OU outputpath	Logs the contents of the Output window to outputpath.
/L libraryname	Identifies the library that contains the object you want to open.
/O objectname	Identifies the object, such as a DataWindow object or window, you want to open.
/I objectname	Identifies the object you want to inherit from.
/N	Creates a new DataWindow object.
/R	Runs the DataWindow object specified with /O and allows designing.
/RO	Runs the DataWindow object specified with /O but does not allow designing.
/A arguments	Provides arguments for the specified DataWindow object.

Examples

The following examples assume that the location of the
PowerBuilder executable file is in your system path.

This example starts a PowerBuilder session by opening the Window
painter in the Client PBL in the Math workspace. The output of the
session is sent to a file called math.log. The workspace file, the
PBL, and the log file are all in the current directory:

pb190 /w Math.pbw /l Client.pbl /p window /out math.log

1	pb190 /w Math.pbw /l Client.pbl /p window /out math.log

Enter this command to start PowerBuilder and open the DataWindow
object called d_emp_report in the workspace Emp.pbw:

pb190 /w D:pbwsEmp.pbw /P dataw /O d_emp_report

1	pb190 /w D:pbwsEmp.pbw /P dataw /O d_emp_report

Building from the command line

You can also build and deploy a workspace from the command
line. For more information, see Building
workspaces.

Document get from Powerbuilder help

Thank you for watching.

Powerbuilder Documentation 2019

August 21, 2023

Was this article helpful?

Connection Information

Using command line arguments – PB Docs 2019

Using command line arguments

Building from the command line

My Website Links