RE: [U2] [AD] Position available in the Sunshine Coast (Aus)

2007-02-08 Thread Peter Dick
At least it wasn't "horrible" !! ;-)

Pete Dick
Senior Technical Support Analyst

IBM Certified Solutions Expert



This e-mail is for the use of the intended recipient(s) only. If you have 
received this e-mail in error, please notify the sender immediately and then 
delete it. If you are not the intended recipient, you must not use, disclose or 
distribute this e-mail without the author's prior permission. We have taken 
precautions to minimize the risk of transmitting software viruses, but we 
advise you to carry out your own virus checks on any attachment to this 
message. We cannot accept liability for any loss or damage caused by software 
viruses.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] UVODBC on AIX

2005-10-31 Thread Peter Dick
The daemon that UVODBC on AIX uses is the uvrpcd and this is defined in
the /etc/services file.

The daemon should automatically start following a boot / reboot of the
server.

The UVODBC group needs to be included as part of the UniVerse
installation process.

It is also worth doing a "netstat -a |grep rpc" to see what state it is
in.

I would be inclined to change your "installer" and start using your
Support Provider! ;)

Pete Dick

Technology Support

www.epicor.com





This e-mail is for the use of the intended recipient(s) only. If you have 
received this e-mail in error, please notify the sender immediately and then 
delete it. If you are not the intended recipient, you must not use, disclose or 
distribute this e-mail without the author's prior permission. We have taken 
precautions to minimize the risk of transmitting software viruses, but we 
advise you to carry out your own virus checks on any attachment to this 
message. We cannot accept liability for any loss or damage caused by software 
viruses.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] [uV] is fixtool the safest bet on uV-10.0.11?

2005-08-19 Thread Peter Dick
You should be aware that there are known issues with UniVerse 10.1.0
through to 10.1.6 (effectively the same version of UniVerse, but for
different platforms) that can cause data loss / corruption when DYNAMIC
files are used. These releases should be avoided for this reason alone,
and have been superseded.
HTH




The word I got was that the first release that had the "new & improved" 
fixtool (the one that based on my tests not only works but even 
reclaims orphaned buffers) is UV 10.1.2.

Note that is only the command line fixtool. The one in the GUI is a 
different critter, and in my experience, should be avoided.


-- 

Regards,

Clif

~~~
W. Clifton Oliver, CCP
CLIFTON OLIVER & ASSOCIATES
Tel: +1 619 460 5678Web: www.oliver.com
~~~


On Aug 17, 2005, at 2:00 PM, [EMAIL PROTECTED] wrote:

> uV 10.0.11 on AIX 5.2.
> Yes, I know that 10.1.14 would be better, please don't tell me.
>
> is "fixtool ... -fix" considered both safe and effective?
> I tested that and it seemed safe, but ineffective,
> so I tried "RESIZE ... * * *" instead.
>
> for a damaged 32bit static hashed file:
> fixtool counts 80,000 more records than do FILE.STAT and uvfixfile.
> fixtool also finds one error in the file.
>
> after "RESIZE * * *" that one error is gone (or is it?)
> but the record counts are still different,
> and fixtool is counting 50,000 more records
> than are counted by uvfixfile and by FILE.STAT,
> so fixtool seem to be detecting some kind of error,
> even though it says not.
>
> which seems to indicate that "RESIZE * * *" is,
> likewise, not effective at repairing this file,
> or, perhaps, RESIZE worked but fixtool is wrong?
>
> Details:
>
> SH -c 'uname -srv'
> AIX 2 5
>
> CT VOC RELLEVEL
>  RELLEVEL
> 0001 X
> 0002 10.0.11
> 0003 PICK
> 0004 PICK.FORMAT
> 0005 10.0.11
>
> SH -c 'ls -l BAD.MEMO'
> -rwxrwx---   1 jsmith   USER 1909102592 Aug 17 14:20 BAD.MEMO
>
> 14:30:44 17 AUG 2005
> FILE.STAT BAD.MEMO
> File name   = BAD.MEMO
> File type   = 2
> Number of groups in file (modulo)   = 1605529
> Separation  = 2
> Number of records   = 2006586
> Number of physical bytes= 1909102592
> Number of data bytes= 908245660
> Average number of records per group = 1.2498
> Average number of bytes per group   = 565.6987
> Minimum number of records in a group= 0
> Maximum number of records in a group= 4
> Average number of bytes per record  = 452.6323
> Minimum number of bytes in a record = 20
> Maximum number of bytes in a record = 61344
> Average number of fields per record = 12.9160
> Minimum number of fields per record = 1
> Maximum number of fields per record = 1708
> Groups  25%50%75%   100%   125%   150%   175%   200% full
>  509072 387360 345746 162336  78082  49224  27132  46577
>
> 14:31:28 17 AUG 2005
> SH -c 'uvfixfile -file BAD.MEMO -s'
> File Statistics
> pathname= BAD.MEMO, size = 1909102592 bytes
> file revision   = 0xacef010b
> modulo  = 0x00187f99 (001605529)
> separation  = 0x0002 (2)
> file type   = 0x0002 (2)
> free list   = 0x (0)
> header size = 0x0400 (01024)
> group size  = 0x0400 (01024)
> Beginning TRACE of BAD.MEMO.
> TRACE of BAD.MEMO completed.
> Scanning overflow buffers.
> Scan complete.
> 1605529 group(s) processed.
> 1642162 group buffer(s) processed.
> 2006586 record(s) processed.
> Number of data bytes = 680719004.
>
> 14:31:46 17 AUG 2005
> SH -c 'fixtool -file BAD.MEMO'
> Filename: BAD.MEMO
> Start Diagnostics.
> 0 Errors found in physical structure.
> 0 Errors found in file header.
> 0 Errors found in primary groups.
> 0 Errors found in data.
> 1 Other errors found in file.
> 2087369 records processed.
> 1 Errors on file.
> Fixtool Completed.
>
> 14:32:14 17 AUG 2005
> RESIZE BAD.MEMO * * *
> 14:57:26 17 AUG 2005
>
> SH -c 'ls -l BAD.MEMO'
> -rw-rw-rw-   1 jsmith   USER 1899482112 Aug 17 14:57 BAD.MEMO
>
> 14:57:26 17 AUG 2005
> FILE.STAT BAD.MEMO
> File name   = BAD.MEMO
> File type   = 2
> Number of groups in file (modulo)   = 1605529
> Separation  = 2
> Number of records   = 2006586
> Number of physical bytes= 1899482112
> Number of data bytes= 908194656
> Average number of records per group = 1.2498
> Average number of bytes per group   = 565.6669
> Minimum number of records in a group= 0
> Maximum number of records in a group= 4
> Average number of bytes per record  = 452.6069
> Minimum number of bytes in a record = 20
> 

RE: [U2] Bad Address for Breakpoint in Debugger

2005-07-28 Thread Peter Dick
... because it's in the middle of a loop?

Pete Dick

Technology Support

www.epicor.com



Tel.: +44 (0)1344 468220
Fax: +44 (0)1344 468055

1 The Arena, Downshire Way, Bracknell, Berks, UK, RG12 1PU This e-mail
is for the use of the intended recipient(s) only. If you have received
this e-mail in error, please notify the sender immediately and then
delete it. If you are not the intended recipient, you must not use,
disclose or distribute this e-mail without the author's prior
permission. We have taken precautions to minimize the risk of
transmitting software viruses, but we advise you to carry out your own
virus checks on any attachment to this message. We cannot accept
liability for any loss or damage caused by software viruses.


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Thursday, July 28, 2005 4:21 PM
To: u2-Users
Subject: [U2] Bad Address for Breakpoint in Debugger

Hi all,

Anyone see why I cannot set a breakpoint at line 60?

 SIS907:  59:IF BAL.LIST<1,ARI.PTR> # 0 THEN
 SIS907:  60:   ARI.ID = ARI.LIST<1,ARI.PTR>
 SIS907:  61:   MAT VARIABLES = ""
 SIS907:  62:   READ ARI.RCD FROM ARI.FILE,ARI.ID ELSE
ARI.RCD = ""
:: 60B
Bad address for breakpoint.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


This e-mail is for the use of the intended recipient(s) only. If you have 
received this e-mail in error, please notify the sender immediately and then 
delete it. If you are not the intended recipient, you must not use, disclose or 
distribute this e-mail without the author's prior permission. We have taken 
precautions to minimize the risk of transmitting software viruses, but we 
advise you to carry out your own virus checks on any attachment to this 
message. We cannot accept liability for any loss or damage caused by software 
viruses.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/