zowe › ca7 › commands › post🖨️

The POST command indicates to the CA Workload Automation CA 7 Edition
system that a preexecution requirement for a job in the request queue is satisfied.
Two categories of requirements can be satisfied, internal and external.
The internal requirements are known within the database and CA WA CA 7 Edition controls them.
An example of an internal requirement is the completion of another job that CA WA CA 7 Edition
controls whose completion satisfies a requirement for a dependent job.
The external requirements are defined in the database but not controlled by CA WA CA 7 Edition.
A manual post must satisfy external requirements unless the requirement is cataloged in the CA WA CA 7 Edition
catalog before the using job is scheduled into the request queue.
This function is available through the QM.2 CPU Job Predecessors Prompt panel.

Usage

zowe ca7 commands post [options]

Required Options

• --ca7Id (string)

  • CA7ONL Instance

Options

• --key (string)

  • The command transaction key

• --ca7# (string)

  • Indicates the job number in up to four digits, for which requirements are posted.

• --usr (string)

  • (Optional) Identifies a user-defined description of a requirement to post as satisfied.
    Mutually exclusive with DEPJOB and DSN.
    When used, must match the text that is used to define the requirement on the DB.6 panel or with the ADDRQ command.
    Limits:
    1 to 36 alphanumeric characters

• --depjob (string)

  • (Optional) Identifies a predecessor job dependency requirement to post as satisfied.
    Value must be a specific job name.
    Mutually exclusive with DSN and USR.
    In normal situations, CA WA CA 7 Edition automatically posts this type of requirement when the predecessor job completes its execution successfully.
    A manual posting is only necessary if a job defined as a requirement was not to be run,
    or ran unsuccessfully and a successor job is to be run.The DEPJOB must be posted if it is not currently defined to CA WA CA 7 Edition
    (an external job).
    Limits:
    1 to 8 alphanumeric characters

• --dsn (string)

  • (Optional) Identifies a data set requirement to post as satisfied.
    Value can be a specific data set name or a CA WA CA 7 Edition data set number.
    If you are using a number, only the number can be specified without the DS prefix.
    Mutually exclusive with DEPJOB and USR.
    dsname
    Indicates a specific data set name.
    Limits:
    1 to 44 alphanumeric characters
    dsnumber
    Indicates a specific data set number. Limits:
    1 to 8 numeric characters

• --internal (string)

  • (Optional) Valid only with DSN to indicate that the data set being posted is internal to the CA WA CA 7 Edition workload.
    YES is the only acceptable value.
    Mutually exclusive with USR, DEPJOB, and PREQ.
    In normal situations, CA WA CA 7 Edition automatically posts requirements for internal data sets.
    Limits:
    YES is the only acceptable value.

• --preq (string)

  • (Optional) Valid only with DSN to identify up to 11 numeric values to include
    with other CA WA CA 7 Edition log data logged as a result of the POST command being issued.
    Mutually exclusive with USR, DEPJOB, and INTERNAL.
    Code values in sublist form, within parentheses.
    You can code up to 11 values that are separated by commas between the parentheses.
    Each value cannot exceed 4 numeric digits.
    This optional field can be useful for logging any meaningful numbers, such as batch numbers, which can later be reviewed in the log data set.

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.

    Note: The CLI does not support certificate files that require a password. For more information, search Troubleshooting PEM Certificates in Zowe Docs.

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

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

Examples

• The requirement for ca7 number 0016 in the request queue is satisfied on Instance1:

  • zowe ca7 commands post --ca7Id Instance1 --ca7# 0016 Copy