When using the compiler (bic.exe), your objects will contain the code that is generated because of the programmers code (the script), but also code that is pre-compiled in a kind of link objects.
These files are actually portingset independent (as is the application itself), but also contain fixes and modifications. These will show up in all objects generated with the new code, but also in own compiled objects.
There can be Dynamic Link Failures because of these bic_ files, like when reports and ttstprepdll is involved.
These files in solution 114812 are somewhere in between the application and the portingset, so applicable for all platforms, not platform dependent, but tools version dependent.
So use the solution on NT also.
But on NT you can install them best with a rename step: rename the tar-file (which is a *.dmp file) into *.tar and use winzip to extract the files. (best is: keep system date in tar-file, since the solution is generic and will be updated.)
Also read Luke 24:4-8