Provide an option to prevent VS CODE from checking compile logs when no compile is performed in user build.

When running a User Build in VS Code using the DBB user lifecycle, it will always check for compile logs in Step 13. When using the Transfer.yaml language definition to transfer files to USS, no compile is performed, only a file transfer is initiated. VS Code still checks for compile logs and produces errors when they are not found. This Idea is to allow for Transfer.yaml file transfers to be performed in VS Code without checking for compile logs. This would prevent the CRRZG5183E errors from showing up in the console log when no compile is performed.

2026-01-21T21:18:57.705Z: Step 13: CRRZG5225I Handling problems view

2026-01-21T21:18:57.706Z: CRRZG5182I Checking user build compile message data set for information.

2026-01-21T21:18:58.218Z: CRRZG5183E Failed to fetch user build compile message data set Error: This value was thrown as is, not through an Error.

2026-01-21T21:18:59.117Z: CRRZG5186E Failed to delete compile message data set Error: Rest API failure with HTTP(S) status 404

Idea priority

Medium

Post comment

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.

Shape the future of IBM!

Search existing ideas

Post your ideas

Specific links you will want to bookmark for future use

Provide an option to prevent VS CODE from checking compile logs when no compile is performed in user build.

Please enter your email address

RELATED IDEAS

Provide an option to prevent VS CODE from checking compile logs when no compile is performed in user build.