1 of 1

m_tws_adhoc_appl

Module for ADHOC record in IWSz process

The REST-API for this module can only be used to create or modify ADHOC records in IWSz process.

In the interactive mode, this module allows to create or modify ADHOC records and edit the operation list with JCL edit and JCL check.

Important: Currently, it is not possible to edit the operation list with JCL edit and JCL check by Rest-API!

Example 1 - Create ADHOC record without parameters

In the most simple case it is possible to create ADHOC record where all parameters are adjusted using Procman process config and environment config.

The REST-API should only contain the instruction "CreateADHOC" for the task with m_tws_adhoc_appl module.

{
  "process": 999,
  "action": "CREATE_ADHOC",
  "ignore_predprocess_status": true,
  "activity_input_data": {
    "task": {
      "t0140": {
        "instruction": {
          "type": "CreateADHOC"
        }
      }
    }
  }
}

Example 2 - Create ADHOC record with selected JCL jobs

In case that the ADHOC record loads JCL from the z/OS request, you have to call the previous task m_jcl_select_file_sys (t0130 in the example below) with selection criteria.

In the following example, the member JOB1 from the library JOBLIB1 is loaded.

{
  "process": 999,
  "action": "CREATE_ADHOC",
  "ignore_predprocess_status": true,
  "activity_input_data": {
    "task": {
      "t0130": {
        "interrupt": false,
        "import": {
          "check_system": "SYSTEM_ID",
          "items": [
            {
              "source": [
                "SYSTEM_ID/LIBS.JOBLIB1(JOB1)"
              ],
              "target": "SYSTEM_ID/LIBS.JOBLIB1"
            }
          ]
        }
      },
      "t0140": {
        "instruction": {
          "type": "CreateADHOC"
        }
      }
    }
  }
}

Example 3 - Create ADHOC record with ADHOC parameters

The request for ADHOC record can contain ADHOC parameters.

The parameters are placed in request to the adcom section inside inputAD node.

List of available parameters that can be used:

adowner: Owner ID
addesc: Text
adodesc: Owner Text
adprior: Priority
adgroup: Authority group id
adrjvtab: Variable table

{
  "process": 9999,
  "action": "CREATE_ADHOC",
  "ignore_predprocess_status": true,
  "activity_input_data": {
    "task": {
      "t0140": {
        "instruction": {
          "type": "CreateADHOC",
          "inputAD": {
            "adcom": {
              "addesc": "test ADHOC app",
              "adowner": "T139A",
              "adodesc": "ADHOC user",
              "adprior": "7",
              "adgroup": "GRPGROUP1",
              "adrjvtab": "ADHOCTABLE1"
            }
          }
        }
      }
    }
  }
}

m_tws_adhoc_appl

Module for ADHOC record in IWSz process

The REST-API for this module can only be used to create or modify ADHOC records in IWSz process.

In the interactive mode, this module allows to create or modify ADHOC records and edit the operation list with JCL edit and JCL check.

Important: Currently, it is not possible to edit the operation list with JCL edit and JCL check by Rest-API!

Example 1 - Create ADHOC record without parameters

In the most simple case it is possible to create ADHOC record where all parameters are adjusted using Procman process config and environment config.

The REST-API should only contain the instruction "CreateADHOC" for the task with m_tws_adhoc_appl module.

{
  "process": 999,
  "action": "CREATE_ADHOC",
  "ignore_predprocess_status": true,
  "activity_input_data": {
    "task": {
      "t0140": {
        "instruction": {
          "type": "CreateADHOC"
        }
      }
    }
  }
}

Example 2 - Create ADHOC record with selected JCL jobs

In case that the ADHOC record loads JCL from the z/OS request, you have to call the previous task m_jcl_select_file_sys (t0130 in the example below) with selection criteria.

In the following example, the member JOB1 from the library JOBLIB1 is loaded.

{
  "process": 999,
  "action": "CREATE_ADHOC",
  "ignore_predprocess_status": true,
  "activity_input_data": {
    "task": {
      "t0130": {
        "interrupt": false,
        "import": {
          "check_system": "SYSTEM_ID",
          "items": [
            {
              "source": [
                "SYSTEM_ID/LIBS.JOBLIB1(JOB1)"
              ],
              "target": "SYSTEM_ID/LIBS.JOBLIB1"
            }
          ]
        }
      },
      "t0140": {
        "instruction": {
          "type": "CreateADHOC"
        }
      }
    }
  }
}

Example 3 - Create ADHOC record with ADHOC parameters

The request for ADHOC record can contain ADHOC parameters.

The parameters are placed in request to the adcom section inside inputAD node.

List of available parameters that can be used:

adowner: Owner ID
addesc: Text
adodesc: Owner Text
adprior: Priority
adgroup: Authority group id
adrjvtab: Variable table

{
  "process": 9999,
  "action": "CREATE_ADHOC",
  "ignore_predprocess_status": true,
  "activity_input_data": {
    "task": {
      "t0140": {
        "instruction": {
          "type": "CreateADHOC",
          "inputAD": {
            "adcom": {
              "addesc": "test ADHOC app",
              "adowner": "T139A",
              "adodesc": "ADHOC user",
              "adprior": "7",
              "adgroup": "GRPGROUP1",
              "adrjvtab": "ADHOCTABLE1"
            }
          }
        }
      }
    }
  }
}