ProIV 5.5 333 for RH Linux
Posted 06 April 2004 - 11:12 PM
You may want to forgo 333 on RH. After installation, every report function that had a scratch variable as one of the fields failed to gen. A cryptic undocument ERROR 630 comes up.
Replace the scracth variable with a file variable and the report gens fine. Of course, we really do need to use scratch variables...
Posted 06 April 2004 - 11:59 PM
This is what they say about the problem on the ProIV site....
Q Why do I get the message 'SYSTEM E630' after upgrading to PROIV 5.5r333?
A This error message is produced for report functions when using a set of bootstraps from an earlier release with the 5.5r333 kernel. Several new error messages were introduced with 5.5r333, along with enhanced validation for XML report tags. Consequently the set of bootstraps provided with that release should be used.
The error message E630 ('630 - XML TAG NAME CONTAINS INVALID CHARACTER') is produced because no tag name has been assigned to a scratch variable field. Since it is possible to redirect a report at run time to produce XML output all report functions have their XML tags validated at gen time. If an XML tag is not specified the kernel will use the field tag name. If there is no field tag the XML tag will be set to the field name. Since scratch variables begin with either am octothorpe (#) or a dollar ($) symbol, which are invalid characters for an XML tag, this error message will be output.
To correct the problem you should upgrade to the latest bootstraps. This is done by exporting your functions from the earlier set and then importing them into the new set of bootstraps. You must not upgrade by extracting dbase.out or rbase.out into the existing bootstraps.
It is possible that this error message will also occur after upgrading correctly to the new set of bootstraps. This will happen if the native development environment is used to create or maintain report functions. To correct the problem in this situation the function exhibiting the error should be loaded into DeveloperStudio or VIP.
Did you upgrade properly??? Because if you did not then that is why you got the problem.
If you just did isout/isin, this is not the way to upgrade.
You have to export / import your functions,
Posted 07 April 2004 - 06:14 AM
No, I didn't do all the work of exporting and importing all functions. I had not considered moving from 332 to 333 a major upgrade.
If this is the only solution, it certainly represents a significant hurdled to upgrading clients as well.
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users