Re: [U2] Unidata 6.1.15 Oddity
Kevin: Many releases ago on Unidata we noticed that this particular code was not working. The code would work when we had it in another program. The program would fail even when we added CRT statements around the code. So, we moved the offending code to another area of the program and the problem was no longer. It seems there was something in the area of code that was causing the compiler to work correctly. Of course we have not seen any of the problem on the current release of 7.3. Regards, Doug www.u2logic.com On Wed, Nov 7, 2012 at 5:25 PM, Kevin King ke...@precisonline.com wrote: We have a customer who has a system that was rebooted a couple days ago. Since then, and only in one certain subroutine, when doing an MCU conversion on a multivalued list, the ASCII 253 value marks are replaced with ASCII 221. Understanding that the difference between an lower and upper case A is 32 in the ASCII table (97 - 65), it seems like Unidata is treating the delimiters like normal characters. But again, this only happens in certain programs. If I extract the lines of code that exhibit this behavior into its own program, the problem does not occur. Any ideas what might be causing this and only in one subroutine? Both my test program and the real program with the problem are $BASICTYPE U. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Unidata 6.1.15 Oddity
FWIW not just @VM. I have standard include code that does a CONVERT CHAR(222) TO @FM after doing MCU conversions on UniData. Since it just gets poked in various places I haven't checked if it is still a problem. BASICTYPE P, but no other UDT.OPTIONs strangely set .. Brian -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Doug Averch Sent: 08 November 2012 15:11 To: U2 Users List Subject: Re: [U2] Unidata 6.1.15 Oddity Kevin: Many releases ago on Unidata we noticed that this particular code was not working. The code would work when we had it in another program. The program would fail even when we added CRT statements around the code. So, we moved the offending code to another area of the program and the problem was no longer. It seems there was something in the area of code that was causing the compiler to work correctly. Of course we have not seen any of the problem on the current release of 7.3. Regards, Doug www.u2logic.com On Wed, Nov 7, 2012 at 5:25 PM, Kevin King ke...@precisonline.com wrote: We have a customer who has a system that was rebooted a couple days ago. Since then, and only in one certain subroutine, when doing an MCU conversion on a multivalued list, the ASCII 253 value marks are replaced with ASCII 221. Understanding that the difference between an lower and upper case A is 32 in the ASCII table (97 - 65), it seems like Unidata is treating the delimiters like normal characters. But again, this only happens in certain programs. If I extract the lines of code that exhibit this behavior into its own program, the problem does not occur. Any ideas what might be causing this and only in one subroutine? Both my test program and the real program with the problem are $BASICTYPE U. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Unidata 6.1.15 Oddity
Hi Kevin, Two times in my Unidata career I've had a problem like this where something doesn't work in a subroutine. My work around, both times, was to add a simple line of code at the beginning of the program. Usually just assigning a value to a new, unused, variable like JUNK=JUNK is all it would take. With it, the program would work flawlessly but if I took it back out, or commented it out, the odd behavior returned. BobW -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Kevin King Sent: Wednesday, November 07, 2012 4:26 PM To: U2 Users List Subject: [U2] Unidata 6.1.15 Oddity We have a customer who has a system that was rebooted a couple days ago. Since then, and only in one certain subroutine, when doing an MCU conversion on a multivalued list, the ASCII 253 value marks are replaced with ASCII 221. Understanding that the difference between an lower and upper case A is 32 in the ASCII table (97 - 65), it seems like Unidata is treating the delimiters like normal characters. But again, this only happens in certain programs. If I extract the lines of code that exhibit this behavior into its own program, the problem does not occur. Any ideas what might be causing this and only in one subroutine? Both my test program and the real program with the problem are $BASICTYPE U. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Multiple UniData Indexes in same select
On 08/11/12 00:47, dennis bartlett wrote: Once again (I'm a fan of these) the answer is to create a file of composite keys (FldA * FldB etc) and index that... The bummer is that the xref file will always be out unless one adds a 'trigger' to each 'to be indexed' file Are you SURE? Itypes can then be created to XLATE the data from the specific files. The index makes + the select quick, + the returned keys are in sequential FldA main sort, FldB nested, + there is a smaller subset of data to do direct reads to the two (or more files). You're assuming that the data is spread across multiple files. It's nicer if you create the files with a set prefix to define that all they are is xref files. The SELECTINDEX can be used. !!! Don't create an IType of the composite and index that... seriously bad idea (or an excellent way to get a continually random, lossy select) Yes, with multiple files. Seriously, I think you're answering the wrong question - iirc the OP wanted UD to combine multiple indexes on ONE file. Something it (and UV) never used to do. If all your data is in one file, and you get the corruption you're describing, I think all us users would be screaming blue murder at Rocket. Cheers, Wol ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
