Closed FALLAI-Denis closed 1 year ago
This is very odd. User build should only upload local files from your workspace. It must not upload any files retrieved via Zowe from the temp directory (as those file are already on the host and cannot be changed in the editor and could therefore be used for the build from their original locations). Somehow the code that detects those files and excludes them must have gotten a regression. We have to investigate.
Hi @phaumer
That's right, I don't remember ZOE uploading copybooks already coming from the remote system.
Besides, despite these errors, the compilation proceeds normally because the copybooks in error are indeed found in the reference PDS.
That said, it could be of interest to do so: use case where the user build would be done on a machine other than the project builds machine
This use case could apply to test environments managed by Wazi Sandbox, (user test, unit test, automated test...):
I suggest turning this anomaly into a feature and implementing a setting to decide whether copybooks downloaded from a remote system should be uploaded to the remote user builds system.
We fixed this regression in v3.1.1.
Development environment used
Setup_IBM_User_Build.txt
IBM_User_Build_with_Full_upload.txt
Problem Description
Detailed steps for reproducing the problem:
Observed behavior
For "IBM User building" a COBOL program, ZOE detects referenced copybooks and searches for them. Some copybooks are local to the Workspace (Current Git Repository, or imported Git Repositories), other copybooks are downloaded from the remote z/OS-USS system.
During the total build, ZOE uploads the copybooks to the working folder on z/OS-USS:
Result of "setup" and "full upload":