Uproc Details

This topic describes all options available to define a Uproc: the job to be executed with all its settings.

The General section is described below. For the other sections, follow these links:

• Uproc Variables
• Time Control Management
• Status Management Rules
• Associated Files List
• Launch Formula
• Events
• Email Notification
• Membership
• Successors

Default values can be adjusted in the Uproc Default Settings document. Don't forget to click Save to save your Uproc.

General

• Name

  Uproc name

• Label

  Uproc description. The label can be updated at any time while updating or duplicating a Uproc.

• Version

  Uproc version number (three digits). In the Simulation and Production Areas, the Uproc version number is always “000”.

• Type

  Click on the button to select the type from the drop-down list. The Value help displays the complete list of available Uproc types. Among them:

  • CL_EXT: The script is stored externally to Dollar Universe.
    On OS400, Uprocs that are type CL_EXT are used to submit a program from a library.
    

  • CL_INT: The script is stored in a Dollar Universe directory.
    On OS400, the script must be a list of commands, each line cannot exceed 4096 characters.

  • CMD: The Uproc concerns the execution of a command.
    Not available on OS400

  • FTP_PUT: This Uproc enables you to send files.
    Not available on OS400

  • FTP_GET: This Uproc enables you to receive files.
    Not available on OS400

  Other Uproc types may vary with the Dollar Universe Managers available and are described in the corresponding manager user guides.

• From File…

  The button to the right of the Type field allows the user to select a Uproc sample. Uproc samples are only available for Uprocs type CL_INT.

  A pop-up window will appear with a list of default and user samples. This list represents the scripts stored in the <COMPANY>_<NODE>\bin\clints and <COMPANY>_<NODE>\data\nodefiles subdirectories. Refer to section "Uproc Samples" for more details on creating and using Uproc samples.

• Edit

  The button to the right of the Type field either allows the script to be edited or a configuration window to be opened. Actions proposed will, of course, depend on the Uproc type selected.

  • For CL_EXT type Uprocs, click Edit. In the CL field and enter the path and the script file name (up to 60 characters). A file chooser is not available because all files are considered remote. Click Edit to edit the file.

  • For CL_INT type Uprocs, click Edit to edit the script.

  • For FTP_PUT Uprocs, click Edit to set the parameters to send files, Refer to section "FTP_PUT Type Uproc".

  • For FTP_GET type Uprocs, click Edit to set the parameters to receive files. Refer to section "FTP_GET Type Uproc".

  • For a CMD type Uproc, click Edit to open a new dialog:

    Command line: Enter the command line to be executed in the form: <Directory><Command><arguments>

    For example: C:\temp\script.bat

    On Windows, "CMD /C" must precede a shell command.

    For example: CMD /C dir

    The command line length must not exceed 262 characters. The command directory and arguments can contain variables in the form !VARIABLE!. Refer to the Dollar Universe Reference Guide for the description of these variables in section “Use of Variables in the Command Line”.

    Exec. directory: For a CMD-type Uproc, enter the directory where output files will be created. The default directory is the home directory of the Submission Account executing the Uproc. The directory name length must not exceed 256 characters, plus two possible string delimiter characters "…", making 258 characters maximum.

• Shell

  For Uprocs of type CL_INT, CL_EXT and CMD, the shell type can be specified:

  • DEFAULT: means that the default shell is used (default value)
  • CSCRIPT (except CMD type), POWERSHELL or PERL: the user can specify the shell type used by the Uproc.

• Application

  Enter the application code or click to select an application from a list.

• Domain

  The selection of an application will automatically display the associated domain.

• Interactive job

  On Windows only

• No login shell

  On UNIX only

  	Windows	UNIX
  Checkbox cleared	The job is submitted in batch mode, through the User Service of the Submission Account. If no User Service is available, then, an attempt is made to submit the job in interactive mode, through the "Interactive Desktop" service.	The job is submitted through the “su -user” command (default). The shell of the user (defined in /etc/passwd) is used, and the corresponding environment file is loaded (usually, .profile for KSH, or .bashrc for BASH, etc.) before the execution of the command.
  Checkbox checked	The job is submitted in interactive mode, through the "Interactive Desktop" service. The system user associated with the submission account must be connected so that the job is submitted correctly. Refer to "V6 Accounts"	The job is submitted through the “su -user” command. The shell of the user (defined in /etc/passwd) is used, but the corresponding environment file is NOT loaded: For example when using SH or KSH, the ~user/.profile file won't be loaded before the execution (instead, the Dollar Universe logical environment is kept).