gerd_renz3
VIP Member
Hi List,
I was running a full E900 package after an Upgrade on V5R4. After the run failed we found that the header files in /QIBM/include are corrupted, full of strange characters, certainly not .h source code.
There is a second folder on my client´s system named /QIBM_V5R4 that contains readable, apparently correct code in the .h files.
How can I point the E900 package build process to use this alternative folder? Or should I just rename it to /QIBM ? My client does not know where all this is coming from and I am only half-literate on the AS.
Any help would be appreciated.
Thanks Gerd
I was running a full E900 package after an Upgrade on V5R4. After the run failed we found that the header files in /QIBM/include are corrupted, full of strange characters, certainly not .h source code.
There is a second folder on my client´s system named /QIBM_V5R4 that contains readable, apparently correct code in the .h files.
How can I point the E900 package build process to use this alternative folder? Or should I just rename it to /QIBM ? My client does not know where all this is coming from and I am only half-literate on the AS.
Any help would be appreciated.
Thanks Gerd
