Online Help for Save As Script

Use the Save As Script dialog box to save CommCell operations as scripts that can be run from the command line or incorporate it into other scripts. For more information on saving operations as scripts, see Save as Script Overview.

Client

Enter or select the name of the client computer where the script will be created.

File Path

Enter the location where you want to save the script along with the file name and extension. For example, "C:\scripts\myscript.bat" on Windows and "/usr/scripts/myscript.sh" on Unix. The script will be saved as a .xml file and .bat/.sh file.

  • If .xml and .bat/.sh files with the same name already exist, they cannot be overwritten unless the bAllowSaveAsScriptFileOverWrite additional setting is used. For information on adding bAllowSaveAsScriptFileOverWrite, see Enabling File Overwrite for the Save as Script Option.

  • Do not use reserved device names (for example, LPT1) as the name of the file.

  • The file names are not case-sensitive.

  • Do not end the file name with a trailing space or a period. Although the underlying file system may support such names, the operating system does not support them.

Browse

Click this button to browse a location for the command line script.

Mode

  • Synchronous

    Specifies that the script execute in synchronous mode. A synchronous operation exits only when the operation has completed. This option is only available when scripting a single job.

  • Asynchronous

    Specifies that the script execute in asynchronous mode. An asynchronous operation submits the job to the CommServe and exits immediately, returning control to the calling program or script.

Specify User Account to Run the Script

The user whose credentials will be used to run the script.

  • Authenticate at run time

    Click to prompt for credentials when the script is run.

  • Use the currently logged in user account

    Click to use the credentials of the user logged on to the CommCell Console.

    • User Name

      The user whose credentials will be used to run the script.

  • Use a different user account

    Click to provide the credentials of the user whose credentials will be used to run the script.

    • User Name

      The user whose credentials will be used to run the script.

    • Password

      The password for the user whose credentials will be used to run the script.

    • Confirm Password

      Retype the password for confirmation.

  • Use local admin account

    Click to allow the local administrator of a client computer (or a user with administrative rights) to log on to the CommServe without the need to provide a user name and password.

    This option verifies that the user currently logged on to the client is a local administrator. Once authenticated, the user is automatically logged on to the CommServe as the owner of the client. All the operations that the user can perform will be limited to that client.

  • Use Single Sign On

    Click to use single sign-on (SSO) to log on using the user account credentials from the Active Directory service provider. This option is available on Windows client computers.

Loading...