Re: [U2] Unidata 6.1.15 Oddity

2012-11-09 Thread Kevin King
Thank you everyone for the feedback.  I had some suspicion in the back of
my mind that doing an OCONV MCU on a full mv'd string was a Somewhat Bad
Idea, now I know why. :-)

On Thu, Nov 8, 2012 at 10:56 AM, Woodward, Bob bob_woodw...@k2sports.comwrote:

 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

___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users


Re: [U2] Unidata 6.1.15 Oddity

2012-11-09 Thread Dave Davis
Were you doing an OCONVS or just an OCONV?

-Original Message-
From: u2-users-boun...@listserver.u2ug.org 
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Kevin King
Sent: Friday, November 09, 2012 11:46 AM
To: U2 Users List
Subject: Re: [U2] Unidata 6.1.15 Oddity

Thank you everyone for the feedback.  I had some suspicion in the back of my 
mind that doing an OCONV MCU on a full mv'd string was a Somewhat Bad Idea, now 
I know why. :-)

On Thu, Nov 8, 2012 at 10:56 AM, Woodward, Bob bob_woodw...@k2sports.comwrote:

 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

___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users



Dave Davis
Team Lead, RD

P: 614-875-4910 x108
F: 614-875-4088
E: dda...@harriscomputer.com
[http://www.harriscomputer.com/images/signatures/HarrisSchools.gif]

[http://www.harriscomputer.com/images/signatures/DivisionofHarris.gif]http://www.harriscomputer.com/
6110 Enterprise Parkway
Grove City, OH
43123
www.harris-schoolsolutions.comhttp://www.harris-schoolsolutions.com

This message is intended exclusively for the individual or entity to which it 
is addressed. This communication may contain information that is proprietary, 
privileged or confidential or otherwise legally exempt from disclosure. If you 
are not the named addressee, you are not authorized to read, print, retain, 
copy or disseminate this message or any part of it. If you have received this 
message in error, please notify the sender immediately by e-mail and delete all 
copies of the message.

___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users


Re: [U2] Unidata 6.1.15 Oddity

2012-11-08 Thread Doug Averch
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

2012-11-08 Thread Brian Leach
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

2012-11-08 Thread Woodward, Bob
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


[U2] Unidata 6.1.15 Oddity

2012-11-07 Thread Kevin King
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


Re: [U2] Unidata 6.1.15 Oddity

2012-11-07 Thread Doug Averch
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

2012-11-07 Thread Bill Haskett

Kevin:

You might try to re-compile the code.  Ever since I went to UniData on 
Windows I have an occasional burp in programs.  Last week one of our 
clients reported an index not working properly. A thorough review showed 
no problems.  We had their IT people in and still were having problems.  
The index showed:


...removing indexes for ARTMASTER,ARTMASTER file...
errno=13: Permission denied
Delete index file 'ARTMASTER\X_ARTMASTER' failed

There was absolutely no permissions problem!  The solution was to simply 
recompile all code and the problem went away.  I've had this /*very*/ 
occasional problem on every UD installation I've had since I moved to UD 
six years ago.  Today, the first thing I do with clients who complain of 
weird things happening is to recompile the code.  Sometimes two lines of 
code say WRITE... then WRITE... and the second write doesn't occur.


Again, this is a very rare occurrence but it does happen.

HTH,

Bill


- Original Message -
*From:* ke...@precisonline.com
*To:* U2 Users List u2-users@listserver.u2ug.org
*Date:* 11/7/2012 4:25 PM
*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] Unidata 6.1.15 Oddity

2012-11-07 Thread Wally Terhune
From memory...
The difference may depend on the UNIX LANG setting for different users.
LANG=C may be required. You don't say what platform you are on.
We may also have fixed something since 6.1.15. My memory isn't what it used to 
be. You can certainly scan the readmes for MCU and/or UPCASE.

Wally Terhune
Technical Support Engineer
Rocket Software
4600 South Ulster Street, Suite 1100 **Denver, CO 80237 **USA
t: +1 720 475 8055 **e: wterh...@rocketsoftware.com **w: u2.rocketsoftware.com


-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 5: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