BLUSAM KSDS dataset missing in output files

It appears you're encountering an issue where the expected KSDS listcat files are not being generated in the outputs/transform/outputs folder during the AWS BluAge L3 troubleshooting workshop. This is an unusual situation, as these files should typically be created during the transformation process.

To address this issue, you might want to consider the following steps:

1. Double-check your project configuration: Ensure that your project is correctly set up to handle VSAM KSDS datasets. The configuration files in the 'config' folder of your project should include the necessary settings for processing KSDS files.

2. Verify the input files: Confirm that the KSDS files in C:/Work/Resources/vsam-ksds are accessible and not corrupted.

3. Review the transformation logs: Look for any error messages or warnings that might indicate why the listcat files weren't generated.

4. Re-run the transformation: Try running the transformation process again, paying close attention to any messages or errors that appear.

5. Check the Blusam configuration: Ensure that the Blusam component is properly configured in your application-main.yml file. Blusam is responsible for handling VSAM datasets in AWS Blu Age.

6. Use the Blusam Administration Console (BAC): If available, use the BAC to check if the datasets are recognized by the system.

If the issue persists after these steps, you may need to contact AWS support or your workshop instructor for further assistance. They might be able to provide specific guidance based on the workshop setup or identify if there's a potential issue with the workshop materials.
Sources
AWS Blu Age Blusam - AWS Mainframe Modernization
Structure of AWS Blu Age managed applications - AWS Mainframe Modernization