OCLI Model: Leveraging JSON and YAML formats for better performance

​The release of OCLI version 10.2.2 has made available two additional formats for model commands: YAML and JSON:

​●       The YAML format is very easy to write and read, which makes it more accessible and less error prone.
●       The JSON format is designed to simplify parsing and it is compatible with Java script.
 
One of the OCLI's features is its ability to easily use and display different object formats with simple commands.

​​The following example illustrates how an object already defined in the Database can be visualized in a YAML file after it was extracted in that format.
Before starting to work with the OCLI, it is important that its config.yaml file is well configured. Beside that, it is also possible to set a working directory for the creation of Jobs using this command:
 
ocli context set current_folder=/OCLI_FOLDER
Once this option is set, all the new objects defined with OCLI will be automatically created in the specified folder.
Let’s now create a new Job. Run the following command to open the editor:

ocli model n
Add the following Job Definition in schedLang format:
$JOBS
/WORKSTATION-NAME#JOB-NAME_OCLI
DOCOMMAND "netstat -an"
STREAMLOGON "User"
TASKTYPE UNIX
RECOVERY CONTINUE
The same Job definition created previously in schedLang format can be visualized in JSON format running this command:
ocli model di job=/WORKSTATION-NAME#/OCLI_FOLDER/JOB-NAME_OCLI -format json
This is what our Job looks like:

​It is now possible to extract the Job in YAML format with these commands:
1)ocli context set format=yaml
2)ocli model extract /tmp/job.yaml from job=/WORKSTATION-NAME#/OCLI_FOLDER/JOB-NAME_OCLI
Where “1)” set the YAML format as default and “2)” is the extract command.
Finally, this is our Job in YAML format:

​Extracting files to YAML makes it possible to commit them on GitHub. This enables versioning on GitHub, giving software engineering teams complete visibility to the code history and a single source of documentation for all files.

If a YAML file were to be modified on GitHub, the edited file could be imported through OCLI. For example, if our YAML job definition was modified from “User” to “User2”, the following command can be used to import the updated job definition:
ocli model add /tmp/job.yaml

​With the latest OCLI version 10.2.3, the context command can be used on even more object types.

---

​Gabriele Buccioli, Software Engineer for Workload Automation
He joined HCL in February 2022 as a member of the Verification Test team and works as verification tester for the Workload Automation suite on distributed environments.
He has a Master's Degree in Management and Automation Engineering at Rome Tre University.

---

​Matteo Liotta, Software Engineer for Workload Automation
He joined HCL in May 2022 as a member of the Verification Test team.He works as verification tester for the Workload Automation suite on distributed environments.
He has a Master's Degree in Electronic Engineering at Sapienza University