zowe › ca7 › dataset › create-dataset-trigger🖨️

Create Dataset Trigger

Usage

zowe ca7 dataset create-dataset-trigger [options]

Options

• --dataset-name | --dname (string)

  • (Required if dataset-number is omitted) Specifies the data set name whose creation/update causes triggering of a job.
    Note: For VSAM files, specify the cluster name.
    Limits: 1 to 44 alphanumeric characters

• --dataset-number | --dnum (string)

  • (Required if dataset-name is omitted) Specifies the existing data set number whose creation causes triggering. The number is the value that CA 7 assigned to the data set.
    Limits: 1 to 8 numeric characters

• --schid (string)

  • (Optional) Specifies for which schedule ID of the triggering dataset the triggered-job is scheduled.
    Note: If the data set is one that is tracked with use of SASSXDSN (externally tracked data sets), the schid field must be 000 for the trigger to work
    Default: 0 (all schedule IDs)
    Limits: 1 to 3 numeric characters from 0 through 999

• --triggered-job-schid | --tjs (string)

  • (Optional) Denotes a replacement schedule ID to use when the triggered-job is placed into the request queue.
    Default: 0 (no replacement)
    Limits: 1 to 3 numeric characters from 0 through 999
    Note: If triggered-job-schid is used, it replaces the schid value of the triggered job. Any jobs triggered (by triggered-job or data sets it creates) use this triggered-job-schid for their schedule ID unless they also have a triggered-job-schid value.

• --triggered-job-due-out-time | --tjdot (string)

  • (Required if triggered-job-queue-time is omitted) Specifies the due-out time of day of the triggered-job rounded down to 10-minute increments.
    If this parameter is used, triggered-job-queue-time must be omitted.
    Limits: 4 numeric characters that are specified as hhmm, where hh can be 00 through 24 and mm can be 00 through 59, the highest value being 2400. If specified, the lowest value is 10.
    Note: If used and the due-out-time of the triggering job is after the triggered-job-due-out-time, the following calendar day is assumed.

• --triggered-job-queue-time | --tjqt (string)

  • (Required if triggered-job-due-out-time is omitted) Specifies the elapsed queue time of triggered-job rounded down to 10-minute increments.
    If this parameter is used, triggered-job-due-out-time must be omitted because due-out time is then calculated as deadline time plus runtime.
    Deadline time is calculated as current date/time plus queue time.
    Limits: 4 numeric characters that are specified as hhmm, where hh can be 00 through 24.
    The mm can be 00 through 59, the highest value being 2400.

• --triggered-job-lead-time | --tjlt (string)

  • (Optional) Specifies the elapsed lead time for triggered-job rounded to 10-minute increments. This parameter specifies the lead or processing time necessary to ensure triggered-job meets its due-out time.
    Default: 0000
    Limits: 4 numeric characters that are specified as hhmm, where hh can be 00 through 24.
    The mm can be 00 through 59, the highest value being 2400.

• --triggered-job-submit-time | --tjst (string)

  • (Optional) Imposes a submit time of day requirement on triggered-job. When used, the job is not submitted before this time.
    The triggered-job-submit-time is always rounded down to 15-minute increments.
    Default: 0 (no specific submit time requirement)
    Limits: 4 numeric characters that are specified as hhmm, where hh can be 00 through 24 and mm can be 00 through 59, the highest value being 2400.
    Note: If triggered-job-queue-time is used, the date for the submit time requirement is the same as the deadline start date.

    If triggered-job-due-out-time is used and the triggered-job-submit-time is less than the triggered-job-due-out-time, the date for the triggered-job-submit-time is the same as the deadline start date. Otherwise, the triggered-job-submit-time date is the previous day.

Required Options

• --triggered-job | --tj (string)

  • Specifies the job name that the completion of the triggering dataset triggers.
    Limits: 1 to 8 alphanumeric characters

CA7 Connection Options

• --host | -H (string)

  • Host name of the CA7 API service that is running on the mainframe system.

• --port | -P (number)

  • Port for the CA7 API service that is running on the mainframe system.

• --user | -u (string)

  • User name for authenticating connections to the CA7 API service that is running on the mainframe system.

• --password | --pass | --pw (string)

  • Password for authenticating connections to the CA7 API service that is running on the mainframe system.

• --base-path | --bp (string)

  • The base path for your API mediation layer instance. Specify this option to prepend the base path to all resources when making REST requests. Do not specify this option if you are not using an API mediation layer.

• --protocol | -o (string)

  • Specifies protocol to use for CA7 connection (http or https).

    Allowed values: http, https

Profile Options

• --ca7-profile | --ca7-p (string)

  • The name of a (ca7) profile to load for this command execution.

• --base-profile | --base-p (string)

  • The name of a (base) profile to load for this command execution.

Base Connection Options

• --reject-unauthorized | --ru (boolean)

  • Reject self-signed certificates.

    Default value: true

• --token-type | --tt (string)

  • The type of token to get and use for the API. Omit this option to use the default token type, which is provided by 'zowe auth login'.

• --token-value | --tv (string)

  • The value of the token to pass to the API.

• --cert-file (local file path)

  • The file path to a certificate file to use for authentication

• --cert-key-file (local file path)

  • The file path to a certificate key file to use for authentication

Examples

• Create a Dataset Trigger definition DATA.SET.NAME with schid 42 for Triggered job JOBA:

  • zowe ca7 dataset create-dataset-trigger --dname DATA.SET.NAME --schid 42 --tj JOBA --tjdot 0830 Copy