uxordre - Trigger a Batch Job

This section describes the uxordre command which enables operations to be triggered from the CL environment or a script.

The uxordre command (alias uxord on OpenVMS) can be used to trigger a task already defined in the Dollar Universe parameter base as a "provoked task" or as a "scheduled task". Default parameters may be used or overridden by those supplied with the trigger command as described below.

Reminder: If the task is:

• Activated: the command uxordre creates an actived launch.
• Simulated: the command uxordre creates a deactivated launch.
• Disactivated: the command uxordre does not create a launch.

The uxordre command also accepts up to thirty applications parameters for transfer:

• To the procedure, if the task is a simple Uproc.
• To the session header, if the task is a session.

The default Environment (area _ node) can be changed. The command displays the launch number in the standard output. The format is "numlaunch nnnnnnn". Its syntax is as follows:

uxordre [TSK=task] [SES=session] [VSES=version] UPR=uproc [VUPR=version] UG=mu|MU=mu [AFTER="date-hhmm"] [ELAPS="(hhhmm)"] [EXCLU="(hhmm,hhmm)"] [QUEUE=queue] [PRINTER=printer] [DTRAIT=date|PDATE=date] [FORCE|NOFORCE] [BYPASS] [PARAM="P1,P2..."] [LAUNCHVAR="variable=value,variable=value..."]

The OS/400 command UXORDRE allows the user to trigger an existing task from the command line. The F4 key allows the user to enter each parameter individually. The F11 key displays the name of each parameter.

Description of Items

• TSK=

  (Compulsory if UPR is absent, incompatible with UPR) Task code. Tasks from an update V5 to V6 have the default identifier: TSK (SES) (VSES) (UPR) (VUPR).
  Format: 64 alphanumeric characters.

• UPR=

  (Compulsory if TSK is absent, incompatible with TSK) Uproc code.
  Format: 64 alphanumeric characters.

• VUPR=

  (Optional) Uproc version (irrelevant for S and X areas).
  Format: 3 numeric characters.

• SES=

  (Optional) Session code.
  Format: 64 alphanumeric characters.

• VSES=

  (Optional) Version session (irrelevant for X area).
  Format: 3 numeric characters.

• MU= or UG=

  Management unit code.
  Format: 64 alphanumeric characters.

• AFTER=

  (Optional) Date and time of start of launch window. Allows jobs to be triggered for deferred processing.
  Format: "date-HHMM", the date format is indicated by the value of the setting U_FMT_DATE, the time is on four characters. On OS/400, the date must be entered in the format used by the system. The time format is HHMMSS.

  Default:

  • Provoked task: corresponding information in the task.
  • Scheduled task: immediately.
    

• ELAPS=

  (Optional) Duration of launch window.
  Format: (HHHMM).

  Default:

  • On Windows / UNIX / OpenVMS: 99959 (999hrs 59min, or 41.6 days)
  • On OS/400: corresponding information in the task.

• EXCLU=

  (On Windows / UNIX, optional) Exclusion period. Exclude a time range from the launch window.
  Format: (HHMM,HHMM).

  Default : Empty

• EXLW=

  (On OS/400, optional) Exclusion period. Exclude a time range from the launch window.
  Format: (HHMMSS HHMMSS).

  Default: Corresponding information in the task.

• QUEUE=

  (Optional) Execution batch queue.
  Format: 32 alphanumeric characters.

  Default: corresponding information in the task.

• PRINTER=

  (Optional) Printer associated with task.
  Format: logical name on four characters.

  Default: corresponding information in the task.

• CENTRAL

  Obsolete.

• FORCE | NOFORCE

  (Optional) Forced launch at end of window flag.

  Default:

  • On Windows / UNIX / OpenVMS: NOFORCE.
  • On OS/400: corresponding information in the task.

• BYPASS

  (Optional) Launch without condition check.

• DTRAIT= or PDATE=

  (Optional) Processing date.
  Format:

  • On Windows / UNIX / OpenVMS: Indicated by the value of the setting U_FMT_DATE.
  • On OS/400: the date must be entered in the format used by the system.

  Default : corresponding information in the task.

• PARAM=

  (Optional) Applications parameters. Enables the transfer of 1 to 30 parameters to the first Uproc of the task. These parameters may be received:

  • In the Uproc CL in the form of variables $1 to $30 or in the Dollar Universe form S_P1 to S_P30.
  • In the scripts executed by the batch envelope: U_ANTE_UPROC and U_POST_UPROC in the Dollar Universe format S_P1 to S_P30.

  The maximum number of parameters is 30. The length of each parameter is limited to 255 characters and the total length (sum of the parameter lengths + twice the number of parameters) must be less than 2074 characters.

  Format: The parameters are separated by commas; each parameter can have any format unless it comprises a space, in which case it must be shown between quotes " ".

• LAUNCHVAR=

  (Optional) The complete list of execution variables and their values.
  Format: "var=val,var=val…", 255 characters maximum. The list is enclosed within quotation marks. Each variable=value couple is separated from the following one by a comma (with no space).

  • The variable’s name must be selected from the list of launch variables.
  • Where the value of the variable is indicated, this value replaces the value of the launch variable. If the value is not indicated (there must be no comma present) the default value of the launch, task or Uproc variable is taken into account. If the value contains non-alphanumeric characters (e.g. spaces, /…) it must be enclosed within quotation marks. The format of the value must be compatible with the format declared upon creation of the variable in the Uproc.

  On OS/400, entering the variable name and variable value are separated.

Example

• This command triggers the provoked Task "IU_DTS S01", existing on node ds5200 in the Production area, with its default parameters, and transfers the following applications parameters to procedure: 34, /tmp, type:2.

  uxordre NODE=ds5200 EXP UPR=IU_DTS MU=S01 PARAM=34,/tmp,type:2