The problem with trying to look at a bcl file is that it is BINARY, and not a text file.
Just looking at the first few readable characters, it looks like the bcl that we output.
How are you generating the BCL - with CLS output and CLS2CLF? That should be good.
Yes I believe so, I'm posting drom the CLSF manager. We also use another post on the fly interface NIT, which takes care of TCP. We're kind of hoping BCL does the same.
Problem is, we have no manual, so were kind of clueless right now.
Another case of the binary leading the blind?
Production: NX10.0.3.5 MP5 + patch/TC11.2
I'd rather be e-steemed than e-diseaseled