Customizing DYNAMIC Configuration for ZRD-DS Discovery Agent on USS

This topic provides information about how to customize the FILE_DYNAMIC_JCL.YML file configuration.

About this task

The JCL DYANMIC file contains information of a job running on the system. The following is an example JCL DYNAMIC file:

FORMAT": "JOB_DYNAMIC_SYSPLEX",
  "CONTENT":[
    {
      "unique_id": "sysplex1.job1",
      "version": 1,
      "timestamp": "2023-10-12 00:38:22",
      "deleted": false,
      "sysplex_name": "sysplex1",
      "jobname": "job1",
      "extra":{}
    },{
      "unique_id": "sysplex1.job2",
      "version": 1,
      "timestamp": "2023-10-12 00:38:22",
      "deleted": true,
      "sysplex_name": "sysplex1",
      "jobname": "job2",
      "extra":{}
}
  ]
}

Procedure

Go to the discovery-dynamic directory where you have copied the FILE_DYNAMIC_JCL.YML file in step.
```
cd discovery-agent-<version>/config
```

Update the values in the FILE_DYNAMIC_JCL.YML file.

The format of the FILE_DYNAMIC_JCL.YML file is:

files:
  - version: v1
    type: DYNAMIC
    timestamp: 2023-01-01 00:00:00
    deleted: false
    sysplex_name: SYSPLEX_NAME
    dataset_name: DATASET_NAME
    member_name: MEMBER_NAME
  - version: v1
    type: DYNAMIC
    timestamp: 2023-01-01 00:00:00
    deleted: false
    sysplex_name: SYSPLEX_NAME
    dataset_name: DATASET_NAME
    member_name: MEMBER_NAME

For DYNAMIC type, the deleted and sysplex_name are ignored and can be set in the source DYNAMIC file. The dataset_name and member_name columns locate the source DYNAMIC file that needs to be transformed to ZRD-DS API.

The following is an example of FILE_DYNAMIC_JCL.YML for DYNAMIC type:

files:
  - version: v1
    type: DYNAMIC
    timestamp: 2023-01-01 00:00:00
    deleted: 
    sysplex_name: 
    dataset_name: DS.DY 
    member_name: DYNAMIC1