We only use PICK flavor here, no special options set.
Richard Lewis
--- On Thu 03/20, Ray Wurlod < [EMAIL PROTECTED] > wrote:
From: Ray Wurlod [mailto: [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Date: Thu, 20 Mar 2008 12:03:21 +0800
Subject: RE: [U2] UV: LOOP;EXECUTE cmd CAPTU
From: Ray Wurlod
> Just out of curiosity, because EXECUTE is (may be) handled
> differently, what is the account flavor in each case?
> And have you set any compiler options such as EXEC.EQ.PERFORM ?
Primarilly tested in Pick-flavoured account, but IDEAL, too.
I've tried
$OPTIONS EXEC.EQ.PE
Just out of curiosity, because EXECUTE is (may be) handled differently, what is
the account flavor in each case? And have you set any compiler options such as
EXEC.EQ.PERFORM ?
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
[mailto: [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Date: Wed, 19 Mar 2008 16:31:59 -0400
Subject: RE: [U2] UV: LOOP;EXECUTE cmd CAPTURING X; REPEAT fatal memory
fault.
I hear IBM was finally able to reproduce my problem. I don't know any
other details yet.
After I learn more, maybe
CTED] On Behalf Of rbl000
Sent: Wednesday, March 19, 2008 11:28 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] UV: LOOP;EXECUTE cmd CAPTURING X; REPEAT fatal memory
fault.
Charles,
One of the guys in our shop tested this on one of our machines (HP
Itanium, HPUX 11.23, UV 10.2.6) and
Charles,
One of the guys in our shop tested this on one of our machines (HP Itanium,
HPUX 11.23, UV 10.2.6) and couln't see any problem.
He ran this code for 3,572,053 iterations with no increase in memory (not even
a byte):
0001: CNT = 0
0002: LOOP
0003: CNT +=1
0004: CRT OCONV(CNT, "MR0,
I would love it if someone else using Itanium would tell me if they
do/don't see this.
My guess is similar to Tony's.
The child process does disappear after the execute.
Here's a snippet from where I monitored one of my problem processes (pid
5783) by looping 1x/sec:
"date; ps -flu cds33896|g
Try increasing your paging space.
At 01:21 AM 3/18/2008, Tony G wrote:
I'll take a wild guess. Maybe IBM can confirm this.
When you run a BASIC program the runtime allocates memory space
for BASIC variables. When you use these variables for strings,
integers, or dynamic arrays the BASIC run
I'll take a wild guess. Maybe IBM can confirm this.
When you run a BASIC program the runtime allocates memory space
for BASIC variables. When you use these variables for strings,
integers, or dynamic arrays the BASIC runtime manages that space.
When you EXECUTE, another process is temporarily cr
y consumes
40KB
Regards
Mike
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Louie Bergsagel
Sent: Tuesday, 18 March 2008 1:52 p.m.
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] UV: LOOP;EXECUTE cmd CAPTURING X; REPEAT fatal memory
fault.
I kill
From: Allen Egerton
> Capturing writes to uvtemp.
> Are you running out of disk space or perhaps inodes?
Good question, but no. Plenty of room in uvtemp. Plenty of inodes.
It does leave an 0-byte capturenaa file in uvtemp.
0-byte, because I am really doing nothing (execute a comment).
CTED] On Behalf Of Louie Bergsagel
>Sent: Monday, March 17, 2008 4:52 PM
>To: u2-users@listserver.u2ug.org
>Subject: Re: [U2] UV: LOOP;EXECUTE cmd CAPTURING X; REPEAT fatal memory fault.
>
>I killed this after 1.4 million iterations of executing and displaying the
>date (c
Stevenson, Charles wrote:
IBM can't reproduce this. I'm hoping someone else can.
That didn't come out right. I don't really want to you have this
problem. That would be mean. I just hope this august body can help.
Simplest case:
CDS.BP M
01 LOOP
02 EXECUTE '* anything' CAPTURING
I killed this after 1.4 million iterations of executing and displaying the
date (capturing X) and a counter with no problems.
TEST.FATAL.CS
0001 COUNTER = 0
0002 LOOP
0003 EXECUTE "DATE" CAPTURING X
0004 COUNTER += 1
0005 DISPLAY X:" ":COUNTER
0006
From: Louie Bergsagel
> How long before it fails?
A few minutes for me, for that simple test.
The question is what's memory doing?
Try looking at the process with -l option of the unix ps command.
But look at this where I execute an "SH" command:
EXECUTE "SH -c'# comment'" CAPTURING X
& then pr
From: Ken Hall
> Maybe, just maybe, the loop is executing too fast on the
> Itanium server. Try putting a SLEEP into the loop.
Ken,
See line 9.
Notice SZ column increases by the same amount with or without sleep.
>CT CDS.BP KEN
KEN
0001 PERFORM "SH -c'ps -lp $PPID'"
0002 CR
How long before it fails?
I've been running
LOOP
EXECUTE "DATE" CAPTURING X
REPEAT
for over 8 minutes now, on an IBM P650, AIX 5.2, UniVerse release 10.1.12,
Pick syntax.
Perhaps because it is only March...
-- Louie In Seattle
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsu
Maybe, just maybe, the loop is executing too fast on the Itanium
server. Try putting a SLEEP into the loop.
Ken
At 03:13 PM 3/17/2008, you wrote:
IBM can't reproduce this. I'm hoping someone else can.
That didn't come out right. I don't really want to you have this
problem. That would be me
18 matches
Mail list logo
