Some of my co-workers have started using BC3 and are not able to make changes to modules on MVS like they could with BC2. I've only used BC3 for compares, not updates, so I haven't encountered the problem.
When updating a program from an MVS PDS, the module gets created in a new folder instead of updating the module within the PDS. So, if I have a module called abc.def.ghi(xyz), the updated module will be created in a new file called abc.def.ghi.xyz.
Note that this incorrect name is also what is displayed in the folder name field in BC3.
When updating a program from an MVS PDS, the module gets created in a new folder instead of updating the module within the PDS. So, if I have a module called abc.def.ghi(xyz), the updated module will be created in a new file called abc.def.ghi.xyz.
Note that this incorrect name is also what is displayed in the folder name field in BC3.
Comment