RE: [U2] FW: Uonet Timeout

2005-12-09 Thread Brian Leach
Bob

You need to update the unirpcservices file to have a sensible timeout value
for the server. This can time out without notifying the client in a manner
that can be easily trapped. 

Look for the lines headed udcs and defcs and change the final column. Note
that the values are in 1/10th seconds and not (as documented) in seconds.

Brian
 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of Bob Modrich
 Sent: 09 December 2005 01:31
 To: u2-users@listserver.u2ug.org
 Subject: [U2] FW: Uonet Timeout
 
 With the following .net code I am setting the timeout 
 property for a uniobject session. Does anything have to get 
 set on the server side for this to work? 
 
 Try
 UniSession = UniObjects.OpenSession(HostName, 
 UserName, PassWord, AccountPath, udcs)
 UniSession.Timeout = 36000
 Catch ex As UniSessionException
 MsgBox(ex.Message)
 End Try
 ---
 u2-users mailing list
 u2-users@listserver.u2ug.org
 To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] Deciphering Pick UniBasic statement

2005-12-09 Thread Brian Leach
Caleb,

Just to point out - as a newbie don't think all MV coding is like this!
It's this sort of rubbish that gives our industry a bad name.

(Mind you I've seen worse C++ code...)

:)

Brian 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of Caleb Ng
 Sent: 08 December 2005 21:26
 To: u2-users@listserver.u2ug.org
 Subject: RE: [U2] Deciphering Pick UniBasic statement
 
 The general consensus of replies confirms my findings of how 
 this was originally meant to be nested.  Thanks for all your help.
 
 Caleb
 
  [EMAIL PROTECTED] 12/08/05 12:09PM 
 IF P(2)-AR(12)=28 THEN  
CC=CC+1   
INS 0 BEFORE AR(14)1,1  
DEL AR(14)1,9   
 END ELSE 
IF AR(13)=DATE() THEN 
   CC=CC ELSE INS 1 BEFORE AR(14)1,1
   DEL AR(14)1,9
END   
 END  
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


[U2] RE: Program code parsing...

2005-12-09 Thread Gary Gowans

Hi Caleb wrote...

The general consensus of replies confirms my findings of how

 this was originally meant to be nested.  Thanks for all your help.

 Caleb

  [EMAIL PROTECTED] 12/08/05 12:09PM 
 IF P(2)-AR(12)=28 THEN
CC=CC+1
INS 0 BEFORE AR(14)1,1
DEL AR(14)1,9
 END ELSE
IF AR(13)=DATE() THEN
   CC=CC ELSE INS 1 BEFORE AR(14)1,1
   DEL AR(14)1,9
END
 END

as the translation of :

IF P(2)-AR(12)=28 THEN CC=CC+1; INS 0 BEFORE AR(14)1,1; DEL AR(14)1,9; 
ELSE IF AR(13)=DATE() THEN CC=CC ELSE INS 1 BEFORE AR(14)1,1; DEL 
AR(14)1,9


I hate to be pedantic but I think that's wrong...[or maybe just a typo?] -  
If it compiled (which I doubt, due to the isolated ELSE ) it would result in 
the AR(14)1,9 value being deleted where AR(13)=DATE(), when only the CC=CC 
(pointless?!?) should be executed. Viz:


IF P(2)-AR(12)=28 THEN
   CC=CC+1
   INS 0 BEFORE AR(14)1,1
   DEL AR(14)1,9
END ELSE
   IF AR(13)=DATE() THEN
  CC=CC ; * This is meaningless!
   END ELSE
  INS 1 BEFORE AR(14)1,1
  DEL AR(14)1,9 ; * this only happens where AR(13) NE DATE()
   END
END

Hope that doesn't confuse? (Well, it won't confuse as much as rendering the 
assembler code would!)


As a general rule... break the line after any THEN statement, ';' line 
break, before 'ELSE' (and add the END before it) then add an END for each 
END ELSE/THEN statement as appropriate. Simple really!


Gary
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


[U2] F2 Screen Accept

2005-12-09 Thread Bjorn Behr
Hi

Does anybody know what the F@ / Screen Accept Character on SB+ is?

T.I.A

Many Thanks
Bjorn Behr
Programmer (TSD)

Tel : +27 11 523 4202
Email   : [EMAIL PROTECTED] 
Web Site: www.supergrp.com
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] SOX question (United States only, I believe)

2005-12-09 Thread Marc Hilbert

Good Morning Charlie,
No only a US issue, but also an issue for multinationals with US home 
offices. We are in Argentina and have clients that must comply and frankly 
we DO separate the DBA role from the programmer role and I am in favor of 
this although it is an administrative pain at times. Programmers on these 
sites do not get access to the production data-base and only get read-only 
to the user testing environment.

Regards,
Marc Hilbert
Pick Professional Center
Buenos Aires,
Argentina.

- Original Message - 
From: Charlie Rubeor [EMAIL PROTECTED]

To: u2-users@listserver.u2ug.org
Sent: Thursday, December 08, 2005 6:28 PM
Subject: [U2] SOX question (United States only, I believe)



When we started implementing Sarbanes-Oxley, I knew the question of why we
don't separate the Database Admin role from the Programmer role would come
up.  Has anyone on this list been able to provide a satisfactory answer to
the auditors, without spending a lot of time explaining the benefits of an
MV database?

Charlie Rubeor
Unix/Database Administrator
Wiremold/Legrand
60 Woodlawn Street
West Hartford, CT 06110
Tel: 860.233.6251 x3498
Fax: 860.523.3690
Email: [EMAIL PROTECTED]
Internet: www.wiremold.com

[demime 1.01d removed an attachment of type image/jpeg]
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] RE: Program code parsing...

2005-12-09 Thread Mecki Foerthmann
Now I want to be really pedantic  :-P  and therefore here it is, the 
probably ultimate piece of code:


IF AR(13) NE DATE() THEN
  INS (P(2)-AR(12)) LE 28 BEFORE AR(14)1,1
  DEL AR(14)1,9
  CC=CC+AR(14)1,1
END

Mecki

Gary Gowans wrote:


Hi Caleb wrote...


The general consensus of replies confirms my findings of how


 this was originally meant to be nested.  Thanks for all your help.

 Caleb

  [EMAIL PROTECTED] 12/08/05 12:09PM 
 IF P(2)-AR(12)=28 THEN
CC=CC+1
INS 0 BEFORE AR(14)1,1
DEL AR(14)1,9
 END ELSE
IF AR(13)=DATE() THEN
   CC=CC ELSE INS 1 BEFORE AR(14)1,1
   DEL AR(14)1,9
END
 END

as the translation of :

IF P(2)-AR(12)=28 THEN CC=CC+1; INS 0 BEFORE AR(14)1,1; DEL 
AR(14)1,9; ELSE IF AR(13)=DATE() THEN CC=CC ELSE INS 1 BEFORE 
AR(14)1,1; DEL AR(14)1,9


I hate to be pedantic but I think that's wrong...[or maybe just a 
typo?] -  If it compiled (which I doubt, due to the isolated ELSE ) it 
would result in the AR(14)1,9 value being deleted where 
AR(13)=DATE(), when only the CC=CC (pointless?!?) should be executed. 
Viz:


IF P(2)-AR(12)=28 THEN
   CC=CC+1
   INS 0 BEFORE AR(14)1,1
   DEL AR(14)1,9
END ELSE
   IF AR(13)=DATE() THEN
  CC=CC ; * This is meaningless!
   END ELSE
  INS 1 BEFORE AR(14)1,1
  DEL AR(14)1,9 ; * this only happens where AR(13) NE DATE()
   END
END

Hope that doesn't confuse? (Well, it won't confuse as much as 
rendering the assembler code would!)


As a general rule... break the line after any THEN statement, ';' line 
break, before 'ELSE' (and add the END before it) then add an END for 
each END ELSE/THEN statement as appropriate. Simple really!


Gary
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] RE: Program code parsing...

2005-12-09 Thread Mecki Foerthmann

Sorry, sent this too early
Should be:.
IF AR(13) NE DATE() THEN
 INS (P(2)-AR(12)) GT 28 BEFORE AR(14)1,1
 DEL AR(14)1,9
 CC+= (P(2)-AR(12)) LE 28
END

Mecki Foerthmann wrote:

Now I want to be really pedantic  :-P  and therefore here it is, the 
probably ultimate piece of code:


IF AR(13) NE DATE() THEN
  INS (P(2)-AR(12)) le 28 BEFORE AR(14)1,1
  DEL AR(14)1,9
  CC=CC+AR(14)1,1
END

Mecki

Gary Gowans wrote:


Hi Caleb wrote...


The general consensus of replies confirms my findings of how



 this was originally meant to be nested.  Thanks for all your help.

 Caleb

  [EMAIL PROTECTED] 12/08/05 12:09PM 
 IF P(2)-AR(12)=28 THEN
CC=CC+1
INS 0 BEFORE AR(14)1,1
DEL AR(14)1,9
 END ELSE
IF AR(13)=DATE() THEN
   CC=CC ELSE INS 1 BEFORE AR(14)1,1
   DEL AR(14)1,9
END
 END

as the translation of :

IF P(2)-AR(12)=28 THEN CC=CC+1; INS 0 BEFORE AR(14)1,1; DEL 
AR(14)1,9; ELSE IF AR(13)=DATE() THEN CC=CC ELSE INS 1 BEFORE 
AR(14)1,1; DEL AR(14)1,9


I hate to be pedantic but I think that's wrong...[or maybe just a 
typo?] -  If it compiled (which I doubt, due to the isolated ELSE ) 
it would result in the AR(14)1,9 value being deleted where 
AR(13)=DATE(), when only the CC=CC (pointless?!?) should be executed. 
Viz:


IF P(2)-AR(12)=28 THEN
   CC=CC+1
   INS 0 BEFORE AR(14)1,1
   DEL AR(14)1,9
END ELSE
   IF AR(13)=DATE() THEN
  CC=CC ; * This is meaningless!
   END ELSE
  INS 1 BEFORE AR(14)1,1
  DEL AR(14)1,9 ; * this only happens where AR(13) NE DATE()
   END
END

Hope that doesn't confuse? (Well, it won't confuse as much as 
rendering the assembler code would!)


As a general rule... break the line after any THEN statement, ';' 
line break, before 'ELSE' (and add the END before it) then add an END 
for each END ELSE/THEN statement as appropriate. Simple really!


Gary
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] PHANTOM question

2005-12-09 Thread Rex Gozar
Glen,

I ran into this issue a couple of months ago.  The issue with -U when
starting a phantom appears to be a bug in the command line parser.  When I
type in the command:

   PHANTOM DAILY-UPDATE

The command line parser thinks -U is the user option (for the PHANTOM
command), and subsequently fails.  It doesn't appear to have anything to do
whether your root or not.

FYI - If I rename my paragraph from DAILY-UPDATE to DAILY.UPDATE, it
works as expected.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] SOX question (United States only, I believe)

2005-12-09 Thread Steven M Wagner

Marc

How do the programmers to customer support if they cannot look at the data 
in the production data-base?  It would be hard to research problems if you 
cannot look at live data.


Steve

At 08:49 AM 12/9/05 -0300, you wrote:

Good Morning Charlie,
No only a US issue, but also an issue for multinationals with US home 
offices. We are in Argentina and have clients that must comply and frankly 
we DO separate the DBA role from the programmer role and I am in favor of 
this although it is an administrative pain at times. Programmers on these 
sites do not get access to the production data-base and only get read-only 
to the user testing environment.

Regards,
Marc Hilbert
Pick Professional Center
Buenos Aires,
Argentina.

- Original Message - From: Charlie Rubeor 
[EMAIL PROTECTED]

To: u2-users@listserver.u2ug.org
Sent: Thursday, December 08, 2005 6:28 PM
Subject: [U2] SOX question (United States only, I believe)



When we started implementing Sarbanes-Oxley, I knew the question of why we
don't separate the Database Admin role from the Programmer role would come
up.  Has anyone on this list been able to provide a satisfactory answer to
the auditors, without spending a lot of time explaining the benefits of an
MV database?

Charlie Rubeor
Unix/Database Administrator
Wiremold/Legrand
60 Woodlawn Street
West Hartford, CT 06110
Tel: 860.233.6251 x3498
Fax: 860.523.3690
Email: [EMAIL PROTECTED]
Internet: www.wiremold.com

[demime 1.01d removed an attachment of type image/jpeg]
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


--
Steven M Wagner
[EMAIL PROTECTED]
Cary, North Carolina, United States of America
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] SOX question (United States only, I believe)

2005-12-09 Thread Lance Jahnke
What happens when the programmer is the dba? One person developing and managing 
universe...

-Original Message-
From: [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Fri Dec 09 05:49:55 2005
Subject: Re: [U2] SOX question (United States only, I believe)

Good Morning Charlie,
No only a US issue, but also an issue for multinationals with US home 
offices. We are in Argentina and have clients that must comply and frankly 
we DO separate the DBA role from the programmer role and I am in favor of 
this although it is an administrative pain at times. Programmers on these 
sites do not get access to the production data-base and only get read-only 
to the user testing environment.
Regards,
Marc Hilbert
Pick Professional Center
Buenos Aires,
Argentina.

- Original Message - 
From: Charlie Rubeor [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Thursday, December 08, 2005 6:28 PM
Subject: [U2] SOX question (United States only, I believe)


 When we started implementing Sarbanes-Oxley, I knew the question of why we
 don't separate the Database Admin role from the Programmer role would come
 up.  Has anyone on this list been able to provide a satisfactory answer to
 the auditors, without spending a lot of time explaining the benefits of an
 MV database?

 Charlie Rubeor
 Unix/Database Administrator
 Wiremold/Legrand
 60 Woodlawn Street
 West Hartford, CT 06110
 Tel: 860.233.6251 x3498
 Fax: 860.523.3690
 Email: [EMAIL PROTECTED]
 Internet: www.wiremold.com

 [demime 1.01d removed an attachment of type image/jpeg]
 ---
 u2-users mailing list
 u2-users@listserver.u2ug.org
 To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] PHANTOM question

2005-12-09 Thread Glenn Herbert
   Ahhh.   Since  I  don't  have access to 10 I couldn't get the problem.
   Good option though once this bug gets repaired

   __

   From: [EMAIL PROTECTED]
   [mailto:[EMAIL PROTECTED]  On  Behalf Of Rex Gozar
   [EMAIL PROTECTED]
   Sent: Friday, December 09, 2005 8:14 AM
   To: u2-users@listserver.u2ug.org
   Subject: RE: [U2] PHANTOM question

   Glen,
   I ran into this issue a couple of months ago. The issue with -U when
   starting  a  phantom  appears  to be a bug in the command line parser.
   When I
   type in the command:
   PHANTOM DAILY-UPDATE
   The  command  line  parser  thinks  -U  is  the user option (for the
   PHANTOM
   command),  and  subsequently fails. It doesn't appear to have anything
   to do
   whether your root or not.
   FYI  - If I rename my paragraph from DAILY-UPDATE to DAILY.UPDATE,
   it
   works as expected.
   ---
   u2-users mailing list
   u2-users@listserver.u2ug.org
   To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] PHANTOM question

2005-12-09 Thread Patricia Wilson
IBM Release notes - 


7894Prior to this release, UniVerse incorrectly interpreted
any command line argument to the PHANTOM command containing
a -U to indicate that the PHANTOM command should be run as
a different user, and that the user name would follow the
-U argument. Therefore, a command such as PHANTOM LIST -USER
would fail. The PHANTOM command has been corrected to ensure
any -U contained on the command line has one space on either
side to indicate the intention to run the command as a 
different user.

Problems Fixed in UniVerse Release 10.1.13 (Build 8290)

Patricia Wilson
MIS Programmer
ext :3095
813.635.3095
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rex Gozar
Sent: Friday, December 09, 2005 8:14 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] PHANTOM question

Glen,

I ran into this issue a couple of months ago.  The issue with -U when
starting a phantom appears to be a bug in the command line parser.  When
I
type in the command:

   PHANTOM DAILY-UPDATE

The command line parser thinks -U is the user option (for the PHANTOM
command), and subsequently fails.  It doesn't appear to have anything to
do
whether your root or not.

FYI - If I rename my paragraph from DAILY-UPDATE to DAILY.UPDATE, it
works as expected.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] SOX question (United States only, I believe)

2005-12-09 Thread Peter Gonzalez
SOX SUCKS! (we have tee shirts with 'SOX SUCKS' on the front)

Our productivity has gone way down. If there is a problem here is what we have 
to do now. And there are plenty of internal and external auditors to make sure 
we do the following.

1. Create a request to modify.
2. Copy the records from LIVE to DEVEL.
3. Debug the process.
4. Mod the program and correct the data records.
5. Create a user approval form.
6. Have the user sign off.
7. Have the IT manager sign off.
8. Notify the manager of programmers of the change
9. The manager of programmers notifies the system admin.
10. The system admin then moves the programs and (or) the corrected data 
records.
11. The system admin then notifies the IT staff of the move.
12. The programmer then notifies the user.

Documentations includes screen shoots of all changes, programs, DICT, screens 
and records.  The average doc package is about 8 pages.


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steven M Wagner
Sent: Friday, December 09, 2005 8:27 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] SOX question (United States only, I believe)

Marc

How do the programmers to customer support if they cannot look at the data 
in the production data-base?  It would be hard to research problems if you 
cannot look at live data.

Steve

At 08:49 AM 12/9/05 -0300, you wrote:
Good Morning Charlie,
No only a US issue, but also an issue for multinationals with US home 
offices. We are in Argentina and have clients that must comply and frankly 
we DO separate the DBA role from the programmer role and I am in favor of 
this although it is an administrative pain at times. Programmers on these 
sites do not get access to the production data-base and only get read-only 
to the user testing environment.
Regards,
Marc Hilbert
Pick Professional Center
Buenos Aires,
Argentina.

- Original Message - From: Charlie Rubeor 
[EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Thursday, December 08, 2005 6:28 PM
Subject: [U2] SOX question (United States only, I believe)


When we started implementing Sarbanes-Oxley, I knew the question of why we
don't separate the Database Admin role from the Programmer role would come
up.  Has anyone on this list been able to provide a satisfactory answer to
the auditors, without spending a lot of time explaining the benefits of an
MV database?

Charlie Rubeor
Unix/Database Administrator
Wiremold/Legrand
60 Woodlawn Street
West Hartford, CT 06110
Tel: 860.233.6251 x3498
Fax: 860.523.3690
Email: [EMAIL PROTECTED]
Internet: www.wiremold.com

[demime 1.01d removed an attachment of type image/jpeg]
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

--
Steven M Wagner
[EMAIL PROTECTED]
Cary, North Carolina, United States of America
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] SOX question (United States only, I believe)

2005-12-09 Thread Gordon J Glorfield
You mean you don't separate them?  Absolutely there needs to be a division 
of labor here.  As a developer I have no time to keep up with mundane 
tasks as password verification, file resizing and maintenance, upgrades, 
etc...  That doesn't even touch on the security and accountability issues.

In a small shop ( 50 users) you might be able to get away with combining 
the two roles.  But in any shop larger than that, I don't see how you 
could effectively do both jobs.


Gordon J. Glorfield
Sr. Applications Developer
MAMSI (A UnitedHealth Company)
301-360-8839

[EMAIL PROTECTED] wrote on 12/08/2005 04:28:09 PM:

 When we started implementing Sarbanes-Oxley, I knew the question of why 
we
 don't separate the Database Admin role from the Programmer role would 
come
 up.  Has anyone on this list been able to provide a satisfactory answer 
to
 the auditors, without spending a lot of time explaining the benefits of 
an
 MV database?

 Charlie Rubeor
 Unix/Database Administrator
 Wiremold/Legrand
[snip]


This e-mail, including attachments, may include confidential and/or 
proprietary information, and may be used only by the person or entity to 
which it is addressed. If the reader of this e-mail is not the intended 
recipient or his or her authorized agent, the reader is hereby notified 
that any dissemination, distribution or copying of this e-mail is 
prohibited. If you have received this e-mail in error, please notify the 
sender by replying to this message and delete this e-mail immediately.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] SOX question (United States only, I believe)

2005-12-09 Thread David Wolverton
The difference is that you have access to LOOK, but not in any way CHANGE...



How do the programmers to customer support if they cannot look at the data
in the production data-base?  It would be hard to research problems if you
cannot look at live data.

Steve
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] SOX question (United States only, I believe)

2005-12-09 Thread Brian Leach
Is it sufficient to formally separate the roles and procedures, even if they
are carried out by the same person?

and just think, you could put in for two pay rises :)

Brian SOX-Free here

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of Lance Jahnke
 Sent: 09 December 2005 13:36
 To: u2-users@listserver.u2ug.org
 Subject: Re: [U2] SOX question (United States only, I believe)
 
 What happens when the programmer is the dba? One person 
 developing and managing universe...
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


[U2] Prime ED, (sort of)

2005-12-09 Thread aegerton
I'm on a different machine than the one where I read the question regarding
a unix version of the PRIMOS ED, so can't reply to the thread directly.
However, Dec's TECO editor was pretty similar to Pr1me's ED, and has been
ported to unix.

Couple pointers that *might* help are:

http://almy.us/teco.html and
http://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/teco/

-- 
Allen Egerton
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] SOX question (United States only, I believe)

2005-12-09 Thread Andy Pflueger
On 12/9/05, Peter Gonzalez [EMAIL PROTECTED] wrote:
 SOX SUCKS! (we have tee shirts with 'SOX SUCKS' on the front)

 Our productivity has gone way down. If there is a problem here is what we 
 have to do now. And there are plenty of internal and external auditors to 
 make sure we do the following.

 1. Create a request to modify.
 2. Copy the records from LIVE to DEVEL.
 3. Debug the process.
 4. Mod the program and correct the data records.
 5. Create a user approval form.
 6. Have the user sign off.
 7. Have the IT manager sign off.
 8. Notify the manager of programmers of the change
 9. The manager of programmers notifies the system admin.
 10. The system admin then moves the programs and (or) the corrected data 
 records.
 11. The system admin then notifies the IT staff of the move.
 12. The programmer then notifies the user.

 Documentations includes screen shoots of all changes, programs, DICT, screens 
 and records.  The average doc package is about 8 pages.

snip

Goodness! How long does it take to get something accomplished with
these steps? Our problem is that our sysadmin doesn't understand how
our Unidata environment works so getting him to move programs from DEV
to PROD would be next to impossible, IMHO. :)

Although, these seem like very nice steps to satisfy most if not all
of SOX requirements.

--
The Linux philosophy is 'Laugh in the face of danger'.
Oops. Wrong One. 'Do it yourself'. Yes, that's it.
Linus Torvalds
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] Deciphering Pick UniBasic statement

2005-12-09 Thread Jerry Banker

Actually it looks like some case tool code to me not a programmers code.

- Original Message - 
From: Brian Leach [EMAIL PROTECTED]

To: u2-users@listserver.u2ug.org
Sent: Friday, December 09, 2005 3:01 AM
Subject: RE: [U2] Deciphering Pick UniBasic statement



Caleb,

Just to point out - as a newbie don't think all MV coding is like this!
It's this sort of rubbish that gives our industry a bad name.

(Mind you I've seen worse C++ code...)

:)

Brian 


-Original Message-
From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of Caleb Ng

Sent: 08 December 2005 21:26
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Deciphering Pick UniBasic statement

The general consensus of replies confirms my findings of how 
this was originally meant to be nested.  Thanks for all your help.


Caleb

 [EMAIL PROTECTED] 12/08/05 12:09PM 
IF P(2)-AR(12)=28 THEN  
   CC=CC+1   
   INS 0 BEFORE AR(14)1,1  
   DEL AR(14)1,9   
END ELSE 
   IF AR(13)=DATE() THEN 
  CC=CC ELSE INS 1 BEFORE AR(14)1,1
  DEL AR(14)1,9
   END   
END  

---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] SOX question (United States only, I believe)

2005-12-09 Thread Les Hewkin
Is that all there is to it

We have to do all that now...

We also produce diff items of the programs. This details all the changes
made.

But I do have access to the live machine as well.  


Les

-Original Message-
From: Peter Gonzalez [mailto:[EMAIL PROTECTED] 
Sent: 09 December 2005 14:13
To: 'u2-users@listserver.u2ug.org'
Subject: RE: [U2] SOX question (United States only, I believe)

SOX SUCKS! (we have tee shirts with 'SOX SUCKS' on the front)

Our productivity has gone way down. If there is a problem here is what
we have to do now. And there are plenty of internal and external
auditors to make sure we do the following.

1. Create a request to modify.
2. Copy the records from LIVE to DEVEL.
3. Debug the process.
4. Mod the program and correct the data records.
5. Create a user approval form.
6. Have the user sign off.
7. Have the IT manager sign off.
8. Notify the manager of programmers of the change
9. The manager of programmers notifies the system admin.
10. The system admin then moves the programs and (or) the corrected data
records.
11. The system admin then notifies the IT staff of the move.
12. The programmer then notifies the user.

Documentations includes screen shoots of all changes, programs, DICT,
screens and records.  The average doc package is about 8 pages.


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steven M Wagner
Sent: Friday, December 09, 2005 8:27 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] SOX question (United States only, I believe)

Marc

How do the programmers to customer support if they cannot look at the
data 
in the production data-base?  It would be hard to research problems if
you 
cannot look at live data.

Steve

At 08:49 AM 12/9/05 -0300, you wrote:
Good Morning Charlie,
No only a US issue, but also an issue for multinationals with US home 
offices. We are in Argentina and have clients that must comply and
frankly 
we DO separate the DBA role from the programmer role and I am in favor
of 
this although it is an administrative pain at times. Programmers on
these 
sites do not get access to the production data-base and only get
read-only 
to the user testing environment.
Regards,
Marc Hilbert
Pick Professional Center
Buenos Aires,
Argentina.

- Original Message - From: Charlie Rubeor 
[EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Thursday, December 08, 2005 6:28 PM
Subject: [U2] SOX question (United States only, I believe)


When we started implementing Sarbanes-Oxley, I knew the question of
why we
don't separate the Database Admin role from the Programmer role would
come
up.  Has anyone on this list been able to provide a satisfactory
answer to
the auditors, without spending a lot of time explaining the benefits
of an
MV database?

Charlie Rubeor
Unix/Database Administrator
Wiremold/Legrand
60 Woodlawn Street
West Hartford, CT 06110
Tel: 860.233.6251 x3498
Fax: 860.523.3690
Email: [EMAIL PROTECTED]
Internet: www.wiremold.com

[demime 1.01d removed an attachment of type image/jpeg]
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

--
Steven M Wagner
[EMAIL PROTECTED]
Cary, North Carolina, United States of America
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

This message has been comprehensively scanned for viruses,
please visit http://virus.e2e-filter.com/ for details.


This e-mail and any attachments are confidential and intended solely for the 
use of the addressee only. If you have received this message in error, you must 
not copy, distribute or disclose the contents; please notify the sender 
immediately and delete the message.
This message is attributed to the sender and may not necessarily reflect the 
view of Travis Perkins plc or its subsidiaries (Travis Perkins). Agreements 
binding Travis Perkins may not be concluded by means of e-mail communication.
E-mail transmissions are not secure and Travis Perkins accepts no 
responsibility for changes made to this message after it was sent. Whilst steps 
have been taken to ensure that this message is virus free, Travis Perkins 
accepts no liability for infection and recommends that you scan this e-mail and 
any attachments.
Part of Travis Perkins plc. Registered Office: Lodge Way House, Lodge Way, 
Harlestone Road, Northampton, NN5 7UG.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] Emails into AIX

2005-12-09 Thread karlp
quote who=Larry Hiscock
 We've done it on Linux  SCO, but not AIX, although the concepts should be
 the same.  Under AIX, the locations and names of the files will
 undoubtedly
 be different ;-)

 There are a couple of issues:

 1) I'm not sure I'd expose my application server's to receive email
 directly
 from the outside world, unless you're REALLY comfortable with setting up
 sendmail securely, and even THEN I probably wouldn't do it.  If you have
 an
 email server, you can receive mail there under an alias, and have it
 forward
 to the AIX box behind the firewall.

 2) If you want automatic processing, you can setup an alias on the AIX box
 that pipes the email to a script.  Under SCO (at least as of 5.0.5,
 haven't
 checked newer releases, although I will be in a couple of weeks), it's
 just
 a matter of creating the alias.  Under RedHat, you have to place the
 script
 to run in /etc/smrsh.  RedHat's sendmail will ONLY run scripts in this
 directory.  The script can call other scripts that are outside the
 sandbox,
 however.

As Glen said, use procmail. The scripts can be run from .forward based on
whatever rule you write to parse through the email.

Do #1 above, however.


 3) Your receiving script (or whatever U2 program it runs) will then need
 to
 parse the incoming email for whatever you want it to do.


 Larry Hiscock
 Western Computer Services



 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of Bob Witney
 Sent: Wednesday, December 07, 2005 2:55 AM
 To: U2-Users (E-mail)
 Subject: [U2] Emails into AIX

 I am happily using sendmail to email from the aix boxes

 but

 I need to be able to email into the aix box to trigger automatioc process

 Is anyone doing this

 How do I set it up ?

 Thanks

 Bob

 __
 This email has been scanned by the MessageLabs Email Security System.
 For more information please visit http://www.messagelabs.com/email
 __
 ---
 u2-users mailing list
 u2-users@listserver.u2ug.org
 To unsubscribe please visit http://listserver.u2ug.org/

 --
 No virus found in this incoming message.
 Checked by AVG Free Edition.
 Version: 7.1.371 / Virus Database: 267.13.13/195 - Release Date: 12/8/2005


 --
 No virus found in this outgoing message.
 Checked by AVG Free Edition.
 Version: 7.1.371 / Virus Database: 267.13.13/195 - Release Date: 12/8/2005
 ---
 u2-users mailing list
 u2-users@listserver.u2ug.org
 To unsubscribe please visit http://listserver.u2ug.org/



-- 
karl

 _/  _/  _/  _/_/_/      __o
_/ _/   _/  _/_/   _-\._
   _/_/_/  _/_/_/ (_)/ (_)
  _/ _/   _/  _/   ..
 _/   _/ arl _/_/_/  _/ earson[EMAIL PROTECTED]

--
IT Director, ATS Industrial Supply, Inc.
http://www.atsindustrial.com
Toll-free: 800-789-9300 x29
Direct2Desk: 801-978-4429
Facsimile: 801-972-3888
--
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] SOX question (United States only, I believe)

2005-12-09 Thread Gordon J Glorfield
I am surprised by all the differing methodology's for being SOX compliant. 
 For data fixes we have an audit approved process as below.

1.  All changes must be requested from the user.  Artifact: User Request 
(Can be a hard copy of an email.)
2.  LIST.ITEM hard copy of the data before the change.
3.  Change data item using a self-documenting change utility.  Must be 
assigned to User Request and associated with a Root Cause Form that's on 
file.
4.  LIST.ITEM hard copy of the data after the change.
5.  Notify user of data fix and how the user can verify the change is 
correct. (Mini Test Plan.  Can be hard copy of an email.)
6.  User approval.  (Can be hard copy of an email.)
7.  IT Manager approval.

Program changes (unless deemed an emergency) are much more artifact 
intensive.  (Formal Specs, Spec Change Requests, Test Plans, Cross 
Testing, Management Approvals of all, etc...)

Yes, productivity has gone down but accountability is way up.  It also 
makes the users think about requests rather than just asking for 
shoot-from-the-hip development.  (I don't know exactly what I want but, 
I'll know it when I see it.)


Gordon J. Glorfield
Sr. Applications Developer
MAMSI (A UnitedHealth Company)
301-360-8839

[EMAIL PROTECTED] wrote on 12/09/2005 09:13:00 AM:

 SOX SUCKS! (we have tee shirts with 'SOX SUCKS' on the front)

 Our productivity has gone way down. If there is a problem here is 
 what we have to do now. And there are plenty of internal and 
 external auditors to make sure we do the following.

 1. Create a request to modify.
 2. Copy the records from LIVE to DEVEL.
 3. Debug the process.
 4. Mod the program and correct the data records.
 5. Create a user approval form.
 6. Have the user sign off.
 7. Have the IT manager sign off.
 8. Notify the manager of programmers of the change
 9. The manager of programmers notifies the system admin.
 10. The system admin then moves the programs and (or) the corrected 
 data records.
 11. The system admin then notifies the IT staff of the move.
 12. The programmer then notifies the user.

 Documentations includes screen shoots of all changes, programs, 
 DICT, screens and records.  The average doc package is about 8 pages.

[snip]


This e-mail, including attachments, may include confidential and/or 
proprietary information, and may be used only by the person or entity to 
which it is addressed. If the reader of this e-mail is not the intended 
recipient or his or her authorized agent, the reader is hereby notified 
that any dissemination, distribution or copying of this e-mail is 
prohibited. If you have received this e-mail in error, please notify the 
sender by replying to this message and delete this e-mail immediately.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] SOX question (United States only, I believe)

2005-12-09 Thread Results

Gordon,
I used to work for a $500M company (multi-national, multiple 
office) where I was the Unix Admin, the secondary DBA, the Hiring 
Manager, an Area Manager, Head of Computer Security and QC, and a hands 
on programmer simultaneously. The primary DBA also ran the operations 
department, worked as an Area Manager, and was a hands on coder as well.
   When I worked for a $72M company (multi-national, multiple office), 
I was at on point the AIX Admin, the Sun Admin, the Webmaster, Sr. 
Programmer, and managed all the consultants - while assisting in Mac, 
PC, and network support.
   You'd be amazed at what sort of workloads you can adapt to when need 
impels you.


   - Chuck Renaissance Man Barouch

Gordon J Glorfield wrote:

In a small shop ( 50 users) you might be able to get away with combining 
the two roles.  But in any shop larger than that, I don't see how you 
could effectively do both jobs.

---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] SOX question (United States only, I believe)

2005-12-09 Thread Peter Gonzalez
Les,
I didn't include the MMDIFF program that we run. It too, prints the difference, 
if any, on LIVE and DEVEL.

Our understanding of SOX is not to have one or two people involved in software 
administration and conspiring to hard the system. The more people that are 
involved, the less chances of company fraud. 
 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Les Hewkin
Sent: Friday, December 09, 2005 10:34 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] SOX question (United States only, I believe)

Is that all there is to it

We have to do all that now...

We also produce diff items of the programs. This details all the changes
made.

But I do have access to the live machine as well.  


Les

-Original Message-
From: Peter Gonzalez [mailto:[EMAIL PROTECTED] 
Sent: 09 December 2005 14:13
To: 'u2-users@listserver.u2ug.org'
Subject: RE: [U2] SOX question (United States only, I believe)

SOX SUCKS! (we have tee shirts with 'SOX SUCKS' on the front)

Our productivity has gone way down. If there is a problem here is what
we have to do now. And there are plenty of internal and external
auditors to make sure we do the following.

1. Create a request to modify.
2. Copy the records from LIVE to DEVEL.
3. Debug the process.
4. Mod the program and correct the data records.
5. Create a user approval form.
6. Have the user sign off.
7. Have the IT manager sign off.
8. Notify the manager of programmers of the change
9. The manager of programmers notifies the system admin.
10. The system admin then moves the programs and (or) the corrected data
records.
11. The system admin then notifies the IT staff of the move.
12. The programmer then notifies the user.

Documentations includes screen shoots of all changes, programs, DICT,
screens and records.  The average doc package is about 8 pages.


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steven M Wagner
Sent: Friday, December 09, 2005 8:27 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] SOX question (United States only, I believe)

Marc

How do the programmers to customer support if they cannot look at the
data 
in the production data-base?  It would be hard to research problems if
you 
cannot look at live data.

Steve

At 08:49 AM 12/9/05 -0300, you wrote:
Good Morning Charlie,
No only a US issue, but also an issue for multinationals with US home 
offices. We are in Argentina and have clients that must comply and
frankly 
we DO separate the DBA role from the programmer role and I am in favor
of 
this although it is an administrative pain at times. Programmers on
these 
sites do not get access to the production data-base and only get
read-only 
to the user testing environment.
Regards,
Marc Hilbert
Pick Professional Center
Buenos Aires,
Argentina.

- Original Message - From: Charlie Rubeor 
[EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Thursday, December 08, 2005 6:28 PM
Subject: [U2] SOX question (United States only, I believe)


When we started implementing Sarbanes-Oxley, I knew the question of
why we
don't separate the Database Admin role from the Programmer role would
come
up.  Has anyone on this list been able to provide a satisfactory
answer to
the auditors, without spending a lot of time explaining the benefits
of an
MV database?

Charlie Rubeor
Unix/Database Administrator
Wiremold/Legrand
60 Woodlawn Street
West Hartford, CT 06110
Tel: 860.233.6251 x3498
Fax: 860.523.3690
Email: [EMAIL PROTECTED]
Internet: www.wiremold.com

[demime 1.01d removed an attachment of type image/jpeg]
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

--
Steven M Wagner
[EMAIL PROTECTED]
Cary, North Carolina, United States of America
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

This message has been comprehensively scanned for viruses,
please visit http://virus.e2e-filter.com/ for details.


This e-mail and any attachments are confidential and intended solely for the 
use of the addressee only. If you have received this message in error, you must 
not copy, distribute or disclose the contents; please notify the sender 
immediately and delete the message.
This message is attributed to the sender and may not necessarily reflect the 
view of Travis Perkins plc or its subsidiaries (Travis Perkins). Agreements 
binding Travis Perkins may not be concluded by means of e-mail communication.
E-mail transmissions are not secure and Travis Perkins accepts no 
responsibility for changes made to this message after it was sent. Whilst steps 
have been taken to ensure that this message is virus free, 

OT [U2] SOX question (United States only, I believe)

2005-12-09 Thread Robert Paterson
Believe me - I think there are quite a few of us globally who agree with
that sentiment!

 On another note, I'm really sorry to hear that overseas companies
have to deal with SOX.  Or as I call it, The Great Productivity
Reduction Act of 2002.

 Charlie Rubeor


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] Deciphering Pick UniBasic statement

2005-12-09 Thread Gyle Iverson
Hello, Charles.

Charles Stevenson wrote...
Everyone's going to jump in with the answer, but here's a way to figure
it out yourself (on UV, but not UD): Use VLIST.

I don't know which is more painful, the original code or the VLIST output.
;-) I decompiled Caleb's code using the srs4uv.com decompiler and got the
following result in under a second. A few customers use the SRS recovery
service for just this reason.

IF P(2) - AR(12) = 28 THEN
   CC += 1
   INS 0 BEFORE AR(14)1, 1
   DEL AR(14)1, 9
END ELSE
   IF AR(13) = DATE() THEN
  CC = CC
   END ELSE
  INS 1 BEFORE AR(14)1, 1
  DEL AR(14)1, 9
   END
END 

Best regards,
Gyle
www.srs4uv.com
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] SOX question (United States only, I believe)

2005-12-09 Thread Bob Witney
I know that SOX is a US thing but the change management process you describe is 
very close to that used by government departments in the UK

So its all over, not just you yanks that have to put up with it :-)

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Peter Gonzalez
Sent: 09 December 2005 14:13
To: 'u2-users@listserver.u2ug.org'
Subject: RE: [U2] SOX question (United States only, I believe)


SOX SUCKS! (we have tee shirts with 'SOX SUCKS' on the front)

Our productivity has gone way down. If there is a problem here is what we have 
to do now. And there are plenty of internal and external auditors to make sure 
we do the following.

1. Create a request to modify.
2. Copy the records from LIVE to DEVEL.
3. Debug the process.
4. Mod the program and correct the data records.
5. Create a user approval form.
6. Have the user sign off.
7. Have the IT manager sign off.
8. Notify the manager of programmers of the change
9. The manager of programmers notifies the system admin.
10. The system admin then moves the programs and (or) the corrected data 
records.
11. The system admin then notifies the IT staff of the move.
12. The programmer then notifies the user.

Documentations includes screen shoots of all changes, programs, DICT, screens 
and records.  The average doc package is about 8 pages.


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steven M Wagner
Sent: Friday, December 09, 2005 8:27 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] SOX question (United States only, I believe)

Marc

How do the programmers to customer support if they cannot look at the data 
in the production data-base?  It would be hard to research problems if you 
cannot look at live data.

Steve

At 08:49 AM 12/9/05 -0300, you wrote:
Good Morning Charlie,
No only a US issue, but also an issue for multinationals with US home 
offices. We are in Argentina and have clients that must comply and frankly 
we DO separate the DBA role from the programmer role and I am in favor of 
this although it is an administrative pain at times. Programmers on these 
sites do not get access to the production data-base and only get read-only 
to the user testing environment.
Regards,
Marc Hilbert
Pick Professional Center
Buenos Aires,
Argentina.

- Original Message - From: Charlie Rubeor 
[EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Thursday, December 08, 2005 6:28 PM
Subject: [U2] SOX question (United States only, I believe)


When we started implementing Sarbanes-Oxley, I knew the question of why we
don't separate the Database Admin role from the Programmer role would come
up.  Has anyone on this list been able to provide a satisfactory answer to
the auditors, without spending a lot of time explaining the benefits of an
MV database?

Charlie Rubeor
Unix/Database Administrator
Wiremold/Legrand
60 Woodlawn Street
West Hartford, CT 06110
Tel: 860.233.6251 x3498
Fax: 860.523.3690
Email: [EMAIL PROTECTED]
Internet: www.wiremold.com

[demime 1.01d removed an attachment of type image/jpeg]
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

--
Steven M Wagner
[EMAIL PROTECTED]
Cary, North Carolina, United States of America
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
__

__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
__
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] Emails into AIX

2005-12-09 Thread Scott Ballinger
Check out postie at infradig.com ($75). It is a command line mailer; you
can send email (with attachments) through any smtp mail server, and you
can retrieve/process pop3 or imap mail from anywhere, and even
copy/move/delete messages from your imap folders. All command-line, all
scriptable, all easy to do from inside U2 or Pick.

/Scott Ballinger
Pareto Corporation
Edmonds WA USA
206 713 6006

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Friday, December 09, 2005 7:36 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Emails into AIX

quote who=Larry Hiscock
 We've done it on Linux  SCO, but not AIX, although the concepts 
 should be the same.  Under AIX, the locations and names of the files 
 will undoubtedly be different ;-)

 There are a couple of issues:

 1) I'm not sure I'd expose my application server's to receive email 
 directly from the outside world, unless you're REALLY comfortable with

 setting up sendmail securely, and even THEN I probably wouldn't do it.

 If you have an email server, you can receive mail there under an 
 alias, and have it forward to the AIX box behind the firewall.

 2) If you want automatic processing, you can setup an alias on the AIX

 box that pipes the email to a script.  Under SCO (at least as of 
 5.0.5, haven't checked newer releases, although I will be in a couple 
 of weeks), it's just a matter of creating the alias.  Under RedHat, 
 you have to place the script to run in /etc/smrsh.  RedHat's sendmail 
 will ONLY run scripts in this directory.  The script can call other 
 scripts that are outside the sandbox, however.

As Glen said, use procmail. The scripts can be run from .forward based
on whatever rule you write to parse through the email.

Do #1 above, however.


 3) Your receiving script (or whatever U2 program it runs) will then 
 need to parse the incoming email for whatever you want it to do.


 Larry Hiscock
 Western Computer Services



 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of Bob Witney
 Sent: Wednesday, December 07, 2005 2:55 AM
 To: U2-Users (E-mail)
 Subject: [U2] Emails into AIX

 I am happily using sendmail to email from the aix boxes

 but

 I need to be able to email into the aix box to trigger automatioc 
 process

 Is anyone doing this

 How do I set it up ?

 Thanks

 Bob

 __
 This email has been scanned by the MessageLabs Email Security System.
 For more information please visit http://www.messagelabs.com/email 
 __
 ---
 u2-users mailing list
 u2-users@listserver.u2ug.org
 To unsubscribe please visit http://listserver.u2ug.org/

 --
 No virus found in this incoming message.
 Checked by AVG Free Edition.
 Version: 7.1.371 / Virus Database: 267.13.13/195 - Release Date: 
 12/8/2005


 --
 No virus found in this outgoing message.
 Checked by AVG Free Edition.
 Version: 7.1.371 / Virus Database: 267.13.13/195 - Release Date: 
 12/8/2005
 ---
 u2-users mailing list
 u2-users@listserver.u2ug.org
 To unsubscribe please visit http://listserver.u2ug.org/



--
karl

 _/  _/  _/  _/_/_/      __o
_/ _/   _/  _/_/   _-\._
   _/_/_/  _/_/_/ (_)/ (_)
  _/ _/   _/  _/   ..
 _/   _/ arl _/_/_/  _/ earson[EMAIL PROTECTED]

--
IT Director, ATS Industrial Supply, Inc.
http://www.atsindustrial.com
Toll-free: 800-789-9300 x29
Direct2Desk: 801-978-4429
Facsimile: 801-972-3888
--
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] SOX question (United States only, I believe)

2005-12-09 Thread Allen E. Elwood
Marc

How do the programmers to customer support if they cannot look at the data
in the production data-base?  It would be hard to research problems if you
cannot look at live data.

Steve

The thing that always cracks me up is that all one has to do in a U2/PICK
environment is to create q pointers to the main account from the test
account.  You can look and even modify without having access to that account
unless it is locked down by logon at the OS level, which I have yet to find
and as a consultant I have worked on several 'sox compliant' boxes.

You can even compile a program in the test account, and then copy that to
the main account via q pointers as long as you copy the voc pointer as well.
You have to be sure you get the right path for the object code, but that's a
piece of cake, and then the sox auditors would have absolutely no way of
finding out who did what if you just delete the q pointers when you're done.

Not that I would do such a thing (because I get paid by the hour and the
more complicated the procedure the longer it takes), but it is possible.

fwiw,

Allen E. Elwood www.tortillafc.com
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] SOX question (United States only, I believe)

2005-12-09 Thread David A. Green
I wrote a package for MANAGE-2000 clients that addressed these issues.  I
call it DTS (Development Tracking System).  It does a great job separating
Programmer from Live Data.

To use it one would create a Development Account and an end-user testing
account.  My software would run on the Development Account and would pull
objects from the Live Account into the Development Account and then lock
them so that other programmers won't be changing the same items.  The system
would create a backup copy of the original, creating an undo capability.  

When all the modifications have been completed and tested by the programmer,
in the Development Account, it prompted the programmer to Move the
modifications into the Test Account.  The Move only takes only a few
seconds and no recompiling is needed.  It could then send an email to the
person listed as the contact of the enhancement so that they would know it
was ready for them to test.

After the end-user has tested it in the Test Account someone fills in the
Approved By and it would trigger the Move into the Live Account and
release the lock.

David A. Green
DAG Consulting
(480) 813-1725
www.dagconsulting.com
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] SOX question (United States only, I believe)

2005-12-09 Thread Marc Hilbert

Steve,
If you have a good set of test data the user can frequently replicate the 
problem in a test environment. You must regularly update your test data. As 
a last resort, there is an emergency password for a programmer to have 
access, in read-only mode to the production data. Sounds tedious, and it is. 
But after a period of adaptation the need to access production data goes 
sharply down as the users and programmers begin to (forcably) understand the 
need for thorough testing. In this scenario rarely does a faulty 
implementation make its way into production.
I must emphasize that this is not for every user site, total development 
times probably are at least double, but the end result is more than twice as 
solid. But you probably can't sell this to a small or medium size company.

Regards,
Marc

- Original Message - 
From: Steven M Wagner [EMAIL PROTECTED]

To: u2-users@listserver.u2ug.org
Sent: Friday, December 09, 2005 10:27 AM
Subject: Re: [U2] SOX question (United States only, I believe)



Marc

How do the programmers to customer support if they cannot look at the data 
in the production data-base?  It would be hard to research problems if you 
cannot look at live data.


Steve

At 08:49 AM 12/9/05 -0300, you wrote:

Good Morning Charlie,
No only a US issue, but also an issue for multinationals with US home 
offices. We are in Argentina and have clients that must comply and frankly 
we DO separate the DBA role from the programmer role and I am in favor of 
this although it is an administrative pain at times. Programmers on these 
sites do not get access to the production data-base and only get read-only 
to the user testing environment.

Regards,
Marc Hilbert
Pick Professional Center
Buenos Aires,
Argentina.

- Original Message - From: Charlie Rubeor 
[EMAIL PROTECTED]

To: u2-users@listserver.u2ug.org
Sent: Thursday, December 08, 2005 6:28 PM
Subject: [U2] SOX question (United States only, I believe)


When we started implementing Sarbanes-Oxley, I knew the question of why 
we
don't separate the Database Admin role from the Programmer role would 
come
up.  Has anyone on this list been able to provide a satisfactory answer 
to
the auditors, without spending a lot of time explaining the benefits of 
an

MV database?

Charlie Rubeor
Unix/Database Administrator
Wiremold/Legrand
60 Woodlawn Street
West Hartford, CT 06110
Tel: 860.233.6251 x3498
Fax: 860.523.3690
Email: [EMAIL PROTECTED]
Internet: www.wiremold.com

[demime 1.01d removed an attachment of type image/jpeg]
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


--
Steven M Wagner
[EMAIL PROTECTED]
Cary, North Carolina, United States of America
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] SOX question (United States only, I believe)

2005-12-09 Thread Marc Hilbert

Peter,
I am frequently frustrated at having to spend 2 to 3 times as much time to 
fix something thanks to SOX or SOX-like norms. However if you put yourself 
in the place of a director of a large company who doesn't know the IT staff 
personally, you must bear in mind that your department (IT) holds the key to 
daily operations and any slight mistake - be it intentional (remember that 
the director does not know you, so he doesn't know that you and your entire 
staff are above reproach) or accidental could potentially be much more 
costly than paying for twice as much staff. The other way to look at it is 
that somebody is paying you to be VERY thorough with your work. 
Productivity goes way down, as you say, and so do bugs.

Regards,
Marc


- Original Message - 
From: Peter Gonzalez [EMAIL PROTECTED]

To: u2-users@listserver.u2ug.org
Sent: Friday, December 09, 2005 11:13 AM
Subject: RE: [U2] SOX question (United States only, I believe)



SOX SUCKS! (we have tee shirts with 'SOX SUCKS' on the front)

Our productivity has gone way down. If there is a problem here is what we 
have to do now. And there are plenty of internal and external auditors to 
make sure we do the following.


1. Create a request to modify.
2. Copy the records from LIVE to DEVEL.
3. Debug the process.
4. Mod the program and correct the data records.
5. Create a user approval form.
6. Have the user sign off.
7. Have the IT manager sign off.
8. Notify the manager of programmers of the change
9. The manager of programmers notifies the system admin.
10. The system admin then moves the programs and (or) the corrected data 
records.

11. The system admin then notifies the IT staff of the move.
12. The programmer then notifies the user.

Documentations includes screen shoots of all changes, programs, DICT, 
screens and records.  The average doc package is about 8 pages.



-Original Message-
From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of Steven M Wagner

Sent: Friday, December 09, 2005 8:27 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] SOX question (United States only, I believe)

Marc

How do the programmers to customer support if they cannot look at the data
in the production data-base?  It would be hard to research problems if you
cannot look at live data.

Steve

At 08:49 AM 12/9/05 -0300, you wrote:

Good Morning Charlie,
No only a US issue, but also an issue for multinationals with US home
offices. We are in Argentina and have clients that must comply and frankly
we DO separate the DBA role from the programmer role and I am in favor of
this although it is an administrative pain at times. Programmers on these
sites do not get access to the production data-base and only get read-only
to the user testing environment.
Regards,
Marc Hilbert
Pick Professional Center
Buenos Aires,
Argentina.

- Original Message - From: Charlie Rubeor
[EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Thursday, December 08, 2005 6:28 PM
Subject: [U2] SOX question (United States only, I believe)


When we started implementing Sarbanes-Oxley, I knew the question of why 
we
don't separate the Database Admin role from the Programmer role would 
come
up.  Has anyone on this list been able to provide a satisfactory answer 
to
the auditors, without spending a lot of time explaining the benefits of 
an

MV database?

Charlie Rubeor
Unix/Database Administrator
Wiremold/Legrand
60 Woodlawn Street
West Hartford, CT 06110
Tel: 860.233.6251 x3498
Fax: 860.523.3690
Email: [EMAIL PROTECTED]
Internet: www.wiremold.com

[demime 1.01d removed an attachment of type image/jpeg]
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


--
Steven M Wagner
[EMAIL PROTECTED]
Cary, North Carolina, United States of America
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] SOX question (United States only, I believe)

2005-12-09 Thread Richard Brown
 The thing that always cracks me up is that all one has to do in a U2/PICK
 environment is to create q pointers to the main account from the test
 account.  You can look and even modify without having access to that
account
 unless it is locked down by logon at the OS level, which I have yet to
find
 and as a consultant I have worked on several 'sox compliant' boxes.

 You can even compile a program in the test account, and then copy that to
 the main account via q pointers as long as you copy the voc pointer as
well.
 You have to be sure you get the right path for the object code, but that's
a
 piece of cake, and then the sox auditors would have absolutely no way of
 finding out who did what if you just delete the q pointers when you're
done.

 Not that I would do such a thing (because I get paid by the hour and the
 more complicated the procedure the longer it takes), but it is possible.

 fwiw,

 Allen E. Elwood www.tortillafc.com


Well,  there goes any new U2 install's in a SOX company.  No decent auditor
is going to stand for anything like that.

Richard
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] SOX question (United States only, I believe)

2005-12-09 Thread Gordon J Glorfield
That why we have triggers on our basic program files and on the voc.  If 
you do copy something from dev to live, it will show up in the logs.  Then 
your supervisor comes to you not in a very genial mood.  You then have to 
end up doing the paperwork anyway.


Gordon J. Glorfield
Sr. Applications Developer
MAMSI (A UnitedHealth Company)
301-360-8839

[EMAIL PROTECTED] wrote on 12/09/2005 02:38:04 PM:

[snip]
 The thing that always cracks me up is that all one has to do in a 
U2/PICK
 environment is to create q pointers to the main account from the test
 account.  You can look and even modify without having access to that 
account
 unless it is locked down by logon at the OS level, which I have yet to 
find
 and as a consultant I have worked on several 'sox compliant' boxes.

 You can even compile a program in the test account, and then copy that 
to
 the main account via q pointers as long as you copy the voc pointer as 
well.
 You have to be sure you get the right path for the object code, but 
that's a
 piece of cake, and then the sox auditors would have absolutely no way of
 finding out who did what if you just delete the q pointers when you're 
done.

 Not that I would do such a thing (because I get paid by the hour and the
 more complicated the procedure the longer it takes), but it is possible.

 fwiw,

 Allen E. Elwood www.tortillafc.com
[snip]


This e-mail, including attachments, may include confidential and/or 
proprietary information, and may be used only by the person or entity to 
which it is addressed. If the reader of this e-mail is not the intended 
recipient or his or her authorized agent, the reader is hereby notified 
that any dissemination, distribution or copying of this e-mail is 
prohibited. If you have received this e-mail in error, please notify the 
sender by replying to this message and delete this e-mail immediately.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] SOX question (United States only, I believe)

2005-12-09 Thread Allen E. Elwood
Ahh, but if one were to copy just the object code to the same path as the
voc that already existed in the main account, no trigger would be activated.
Doing this, someone could potentially 'cry war and wreck havoc'.

Or, someone could quickly disable the trigger, do the dirty work and
re-enable, unless that is locked down somehow.

Also, I believe someone told me that triggers didn't work on directories in
UV so it wouldn't work there (unless that someone was wrong).

Just playing the devils advocate on this - TGIF.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Gordon J
Glorfield
Sent: Friday, December 09, 2005 13:55
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] SOX question (United States only, I believe)


That why we have triggers on our basic program files and on the voc.  If
you do copy something from dev to live, it will show up in the logs.  Then
your supervisor comes to you not in a very genial mood.  You then have to
end up doing the paperwork anyway.


Gordon J. Glorfield
Sr. Applications Developer
MAMSI (A UnitedHealth Company)
301-360-8839

[EMAIL PROTECTED] wrote on 12/09/2005 02:38:04 PM:

[snip]
 The thing that always cracks me up is that all one has to do in a
U2/PICK
 environment is to create q pointers to the main account from the test
 account.  You can look and even modify without having access to that
account
 unless it is locked down by logon at the OS level, which I have yet to
find
 and as a consultant I have worked on several 'sox compliant' boxes.

 You can even compile a program in the test account, and then copy that
to
 the main account via q pointers as long as you copy the voc pointer as
well.
 You have to be sure you get the right path for the object code, but
that's a
 piece of cake, and then the sox auditors would have absolutely no way of
 finding out who did what if you just delete the q pointers when you're
done.

 Not that I would do such a thing (because I get paid by the hour and the
 more complicated the procedure the longer it takes), but it is possible.

 fwiw,

 Allen E. Elwood www.tortillafc.com
[snip]


This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity to
which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [ ] - RE: [U2] SOX question (United States only, I believe) - Found word(s) list error in the Text body

2005-12-09 Thread Bob Woodward
So if you're use to working with triggers, you know how to take the
trigger off the file, do the dirty deed, then put the trigger back on.

The bottom line of SOX is that someone in authority is ultimately
responsible for the accuracy of the financial reports that get
published, there-by giving stock holders/analysts/purchasers some kind
of assurance that the numbers they use to base their financial decisions
on are accurate.  All of this is to provide a CYA shield for those
that rely on others to provide them accurate information.

SOX is a good thing, in spite of the complexity it causes, but a bottom
line understanding needs to be propagated up the chain of command that
any programmer worth his/her salt, can get into the system, probably
without being detected, to change data or programs regardless of their
title or job duties.  SOX is a lock and locks are only there to keep the
honest people honest.

I was once given a task to change a selection of data so that it
includes two weeks instead of one week.  It took me three days to jump
through all the hoops to document changing a number from 7 to 14 in a
procedure record.

Guess we all have to decide how we react to more government
requirements.

BobW
 
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gordon J
Glorfield
Sent: Friday, December 09, 2005 1:55 PM
To: u2-users@listserver.u2ug.org
Subject: [ ] - RE: [U2] SOX question (United States only, I believe) -
Found word(s) list error in the Text body

That why we have triggers on our basic program files and on the voc.  If

you do copy something from dev to live, it will show up in the logs.
Then 
your supervisor comes to you not in a very genial mood.  You then have
to 
end up doing the paperwork anyway.


Gordon J. Glorfield
Sr. Applications Developer
MAMSI (A UnitedHealth Company)
301-360-8839

[EMAIL PROTECTED] wrote on 12/09/2005 02:38:04 PM:

[snip]
 The thing that always cracks me up is that all one has to do in a 
U2/PICK
 environment is to create q pointers to the main account from the test
 account.  You can look and even modify without having access to that 
account
 unless it is locked down by logon at the OS level, which I have yet to

find
 and as a consultant I have worked on several 'sox compliant' boxes.

 You can even compile a program in the test account, and then copy that

to
 the main account via q pointers as long as you copy the voc pointer as

well.
 You have to be sure you get the right path for the object code, but 
that's a
 piece of cake, and then the sox auditors would have absolutely no way
of
 finding out who did what if you just delete the q pointers when you're

done.

 Not that I would do such a thing (because I get paid by the hour and
the
 more complicated the procedure the longer it takes), but it is
possible.

 fwiw,

 Allen E. Elwood www.tortillafc.com
[snip]


This e-mail, including attachments, may include confidential and/or 
proprietary information, and may be used only by the person or entity to

which it is addressed. If the reader of this e-mail is not the intended 
recipient or his or her authorized agent, the reader is hereby notified 
that any dissemination, distribution or copying of this e-mail is 
prohibited. If you have received this e-mail in error, please notify the

sender by replying to this message and delete this e-mail immediately.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] SOX question (United States only, I believe)

2005-12-09 Thread Bill_H
Allen:

Which makes one wonder why in the world security was pulled out of the dbms.
There's something illogical about an O/S administrator knowing better how to
set up security in the application than the application vendor.

Bill 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of 
 Allen E. Elwood
 Sent: Friday, December 09, 2005 11:38 AM
 To: u2-users@listserver.u2ug.org
 Subject: RE: [U2] SOX question (United States only, I believe)
 
 The thing that always cracks me up is that all one has to do 
 in a U2/PICK environment is to create q pointers to the main 
 account from the test account.  You can look and even modify 
 without having access to that account unless it is locked 
 down by logon at the OS level, which I have yet to find and 
 as a consultant I have worked on several 'sox compliant' boxes.

[snipped]
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] SOX question (United States only, I believe)

2005-12-09 Thread Bruce Nichol

At 17:04 09/12/05 -0800, you wrote:


Allen:

Which makes one wonder why in the world security was pulled out of the dbms.
There's something illogical about an O/S administrator knowing better how to
set up security in the application than the application vendor.

Bill


Might it have something to do with Them that can, do.  Them that can't, 
consult.  Them that can't consult, teach.  Them that are left over from 
that frame legislation against it?





--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.1.371 / Virus Database: 267.13.13/197 - Release Date: 09/12/05


Regards,

Bruce Nichol
Talon Computer Services
ALBURYNSW 2640
Australia

http://www.taloncs.com.au

Tel: +61 (0)411149636
Fax: +61 (0)260232119

If it ain't broke, fix it till it is! 



--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.1.371 / Virus Database: 267.13.13/197 - Release Date: 09/12/05
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] Deciphering Pick UniBasic statement

2005-12-09 Thread Stevenson, Charles
I have not had occasion to use the src4uv.com decompiler service.
Probably worth the price when you really need it.

I am thankful for the wonderful www.src4uv.com freebie download,
SRC.UV.HEADER, that allows access to info about the object file from an
I-descriptor subroutine.

Besides VLIST, but similar to it, RAID has the I  X commands that could
be useful when trying to understand EXACTLY what the program is doing:
  X Displays the current object code instruction and address.
  I Displays and executes the next object code instruction.

cds

 From: Gyle Iverson
 
 Hello, Charles.
 
 Charles Stevenson wrote...
 Everyone's going to jump in with the answer, but here's a 
 way to figure 
 it out yourself (on UV, but not UD): Use VLIST.
 
 I don't know which is more painful, the original code or the 
 VLIST output.
 ;-) I decompiled Caleb's code using the srs4uv.com decompiler 
 and got the following result in under a second. A few 
 customers use the SRS recovery service for just this reason.
 
 IF P(2) - AR(12) = 28 THEN
CC += 1
INS 0 BEFORE AR(14)1, 1
DEL AR(14)1, 9
 END ELSE
IF AR(13) = DATE() THEN
   CC = CC
END ELSE
   INS 1 BEFORE AR(14)1, 1
   DEL AR(14)1, 9
END
 END 
 
 Best regards,
 Gyle
 www.srs4uv.com
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/