Working on a z/OS CEE (zCEE) implementation.
Since the API Toolkit would generate different assets (.sar and .aar files) to be stored in the z/OS USS directory, and test in the DEV environment and later those assets (.sar and .aar files) would be promoted from DEV to UAT, and then PROD.
Can Endevor handle the promotion of those USS assets ?
The z/OS CEE implementation USS files (.sar, .aar) are binary archive file types that Endevor can manage in the same way as any other binary file.
1. Relevant documentation pages for USS Supported files and Defining Types:
Endevor® 19.0 > Administrating > Long-Name Files and USS Supported Files
Endevor® 19.0 > Implementation and Customization > Defining Maps and Inventory Structures > Defining Inventory Structures > Defining Types
2. Related KB article 93548: How to set up a USS Type in Endevor