Closed lauren-li closed 5 months ago
After investigation with @lauren-li and @monvora, it looks like an issue with the underlying technology that we will report to the development team.
A defect has been identified with the FileMetadataStore, that will be addressed by the DBB development team.
Please tack the defect in the file metadata store via the support channels.
Enhancements to improve the Exception handling has been delivered via zAppBuild Release 3.6.0
APAR PH58203 has been opened to address the situation that CopyToPDS returns/reports a RC=0 on an exception
When a truncation error occurs during
Transfer.groovy
(e.g. a transferred text file is over 80 columns), an exception is thrown and the console output shows that the build ended in anERROR
state:However, the build result (i.e. retrieved with the
dbb build-result export
command) shows a status of0 'CLEAN'
:The truncation error exception results in the execution of the![Screenshot 2023-11-10 at 1 56 18 am](https://github.com/IBM/dbb-zappbuild/assets/45975633/b264666d-6c9c-42b1-966c-d6ac9e2af4b1)
catch
block inTransfer.groovy
: https://github.com/IBM/dbb-zappbuild/blob/main/languages/Transfer.groovy#L124-L129