Charles Stevenson | 12 Jun 2012 22:01
Picon

[U2] [UV] "Program "X": Line 2, WRITE failure. ( SYS.MESSAGE 040019 )

Does anyone have a complete list of what kinds of problems will throw 
this error?

 >RUN CDS.BP X
    Program "X": Line 2, WRITE failure.

uv\errlog:
    Tue Jun 12 15:54:05  12848 cdstevenson Program "X": Line 2, 
Message[040019]

Although I generated it here by attempting to write a record with a 
system delimiter in the Id:

    01 OPEN 'CDSTMP' TO F ELSE STOP 201
    02 WRITE '' TO F, 'ABC': <at> VM:'XYZ'

while I have UVCONFIG's param prohibiting that:

    ALLOWMARKS 0

Yet, I fear there are several & sundry ways to yield up that generic 
message.
Care to contribute to the list?
_______________________________________________
U2-Users mailing list
U2-Users <at> listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users

Wjhonson | 12 Jun 2012 22:43
Picon
Favicon

Re: [U2] [UV] "Program "X": Line 2, WRITE failure. ( SYS.MESSAGE 040019 )


Permissions

Remote server offline

-----Original Message-----
From: Charles Stevenson <stevenson.chas <at> gmail.com>
To: U2 Users List <u2-users <at> listserver.u2ug.org>
Sent: Tue, Jun 12, 2012 1:28 pm
Subject: [U2] [UV] "Program "X": Line 2, WRITE failure. ( SYS.MESSAGE 040019 )

Does anyone have a complete list of what kinds of problems will throw 
his error?
 >RUN CDS.BP X
   Program "X": Line 2, WRITE failure.
uv\errlog:
   Tue Jun 12 15:54:05  12848 cdstevenson Program "X": Line 2, 
essage[040019]

lthough I generated it here by attempting to write a record with a 
ystem delimiter in the Id:
    01 OPEN 'CDSTMP' TO F ELSE STOP 201
   02 WRITE '' TO F, 'ABC': <at> VM:'XYZ'
while I have UVCONFIG's param prohibiting that:
    ALLOWMARKS 0
Yet, I fear there are several & sundry ways to yield up that generic 
essage.
are to contribute to the list?
______________________________________________
2-Users mailing list
(Continue reading)

Martin Braid | 12 Jun 2012 22:52

Re: [U2] [UV] "Program "X": Line 2, WRITE failure. ( SYS.MESSAGE 040019 )

Not a complete list, but on UD ...
You are writing a key containing an asterisk into a DIR type file.
Permissions.
A programming error to do with STATUS in a global Trigger routine.
Possible problem with e.g. McAfee not releasing at NT level fast enough.
Martin

-----Original Message-----
From: u2-users-bounces <at> listserver.u2ug.org
[mailto:u2-users-bounces <at> listserver.u2ug.org] On Behalf Of Charles
Stevenson
Sent: 12 June 2012 21:02
To: U2 Users List
Subject: [U2] [UV] "Program "X": Line 2, WRITE failure. ( SYS.MESSAGE
040019 )
Does anyone have a complete list of what kinds of problems will throw
this error?
>RUN CDS.BP X
    Program "X": Line 2, WRITE failure.
uv\errlog:
    Tue Jun 12 15:54:05  12848 cdstevenson Program "X": Line 2,
Message[040019]

Although I generated it here by attempting to write a record with a
system delimiter in the Id:
    01 OPEN 'CDSTMP' TO F ELSE STOP 201
    02 WRITE '' TO F, 'ABC': <at> VM:'XYZ'
while I have UVCONFIG's param prohibiting that:
    ALLOWMARKS 0
Yet, I fear there are several & sundry ways to yield up that generic
(Continue reading)

Charles Stevenson | 13 Jun 2012 00:48
Picon

Re: [U2] [UV] "Program "X": Line 2, WRITE failure. ( SYS.MESSAGE 040019 )

Thanks, but does UD have the same error numbers as UV?
Something similar, but not exactly the same as SYS.MESSAGE,  uv/errlog  
file, right?

I'm looking for causes of that particular 040019 "WRITE failure."
A very particular number for a very generic error.

(A wonderful documentation enhancement would be a better description of 
the error codes and their possible causes.)

On 6/12/2012 3:52 PM, Martin Braid wrote:
> Not a complete list, but on UD ...
> You are writing a key containing an asterisk into a DIR type file.
> Permissions.
> A programming error to do with STATUS in a global Trigger routine.
> Possible problem with e.g. McAfee not releasing at NT level fast enough.
> Martin
>
> -----Original Message-----
> From: u2-users-bounces <at> listserver.u2ug.org
> [mailto:u2-users-bounces <at> listserver.u2ug.org] On Behalf Of Charles
> Stevenson
> Sent: 12 June 2012 21:02
> To: U2 Users List
> Subject: [U2] [UV] "Program "X": Line 2, WRITE failure. ( SYS.MESSAGE
> 040019 )
> Does anyone have a complete list of what kinds of problems will throw
> this error?
>> RUN CDS.BP X
>      Program "X": Line 2, WRITE failure.
(Continue reading)

Martin Braid | 13 Jun 2012 01:22

Re: [U2] [UV] "Program "X": Line 2, WRITE failure. ( SYS.MESSAGE 040019 )

Correct. I was merely stating that these cause "UniBasic WRITE failed"
and may cause your error in UV.

-----Original Message-----
From: u2-users-bounces <at> listserver.u2ug.org
[mailto:u2-users-bounces <at> listserver.u2ug.org] On Behalf Of Charles
Stevenson
Sent: 12 June 2012 23:48
To: U2 Users List
Subject: Re: [U2] [UV] "Program "X": Line 2, WRITE failure. (
SYS.MESSAGE 040019 )

Thanks, but does UD have the same error numbers as UV?
Something similar, but not exactly the same as SYS.MESSAGE,  uv/errlog
file, right?

I'm looking for causes of that particular 040019 "WRITE failure."
A very particular number for a very generic error.

(A wonderful documentation enhancement would be a better description of
the error codes and their possible causes.)

On 6/12/2012 3:52 PM, Martin Braid wrote:
> Not a complete list, but on UD ...
> You are writing a key containing an asterisk into a DIR type file.
> Permissions.
> A programming error to do with STATUS in a global Trigger routine.
> Possible problem with e.g. McAfee not releasing at NT level fast
enough.
> Martin
(Continue reading)

David Jordan | 12 Jun 2012 23:45
Picon
Favicon

Re: [U2] [UV] "Program "X": Line 2, WRITE failure. ( SYS.MESSAGE 040019 )

If it is an SQL table it may be a conflict with table rules.  Ie you cannot write multivalues to a column that is
not defined as multivalue.

David Jordan

-----Original Message-----
From: u2-users-bounces <at> listserver.u2ug.org [mailto:u2-users-bounces <at> listserver.u2ug.org] On
Behalf Of Charles Stevenson
Sent: Wednesday, 13 June 2012 6:02 AM
To: U2 Users List
Subject: [U2] [UV] "Program "X": Line 2, WRITE failure. ( SYS.MESSAGE 040019 )

Does anyone have a complete list of what kinds of problems will throw this error?

 >RUN CDS.BP X
    Program "X": Line 2, WRITE failure.

uv\errlog:
    Tue Jun 12 15:54:05  12848 cdstevenson Program "X": Line 2, Message[040019]

Although I generated it here by attempting to write a record with a 
system delimiter in the Id:

    01 OPEN 'CDSTMP' TO F ELSE STOP 201
    02 WRITE '' TO F, 'ABC': <at> VM:'XYZ'

while I have UVCONFIG's param prohibiting that:

    ALLOWMARKS 0

(Continue reading)

Wjhonson | 13 Jun 2012 00:14
Picon
Favicon

Re: [U2] [UV] "Program "X": Line 2, WRITE failure. ( SYS.MESSAGE 040019 )


What about an exclusive file lock ?  Could that be one?

-----Original Message-----
From: David Jordan <David <at> dacono.com.au>
To: U2 Users List <u2-users <at> listserver.u2ug.org>
Sent: Tue, Jun 12, 2012 3:12 pm
Subject: Re: [U2] [UV] "Program "X": Line 2, WRITE failure. ( SYS.MESSAGE 040019 )

If it is an SQL table it may be a conflict with table rules.  Ie you cannot 
rite multivalues to a column that is not defined as multivalue.
David Jordan
-----Original Message-----
rom: u2-users-bounces <at> listserver.u2ug.org [mailto:u2-users-bounces <at> listserver.u2ug.org] 
n Behalf Of Charles Stevenson
ent: Wednesday, 13 June 2012 6:02 AM
o: U2 Users List
ubject: [U2] [UV] "Program "X": Line 2, WRITE failure. ( SYS.MESSAGE 040019 )
Does anyone have a complete list of what kinds of problems will throw this 
rror?
 >RUN CDS.BP X
   Program "X": Line 2, WRITE failure.
uv\errlog:
   Tue Jun 12 15:54:05  12848 cdstevenson Program "X": Line 2, Message[040019]

lthough I generated it here by attempting to write a record with a 
ystem delimiter in the Id:
    01 OPEN 'CDSTMP' TO F ELSE STOP 201
   02 WRITE '' TO F, 'ABC': <at> VM:'XYZ'
while I have UVCONFIG's param prohibiting that:
(Continue reading)

Charles Stevenson | 13 Jun 2012 01:59
Picon

Re: [U2] [UV] "Program "X": Line 2, WRITE failure. ( SYS.MESSAGE 040019 )

Another cause:

If the write is to a record that someone else has locked (shame on you 
for not explicitly locking it 1st), the 040019 error occurs on 20 minute 
timeout.  (That default can be changed.)
Search for "040019" on this list's archives.  There are several less 
than definitive discussions about it.

That's where I've encountered it.  Went on a wild goose chase recently 
looking for that cause until I found the value-mark-in-the-id problem 
also causes it.   David Jordan's sounds similar: mv data where 
single-valued expected.

How many others?

On 6/12/2012 3:01 PM, Charles Stevenson wrote:
> Does anyone have a complete list of what kinds of problems will throw 
> this error?
>
> >RUN CDS.BP X
>    Program "X": Line 2, WRITE failure.
>
> uv\errlog:
>    Tue Jun 12 15:54:05  12848 cdstevenson Program "X": Line 2, 
> Message[040019]
>
>
> Although I generated it here by attempting to write a record with a 
> system delimiter in the Id:
>
(Continue reading)

Charles Stevenson | 13 Jun 2012 04:36
Picon

Re: [U2] [UV] "Program "X": Line 2, WRITE failure. ( SYS.MESSAGE 040019 )

Here's from a similar discussion from 2005 below.   No solution then.

But I just thought of something I wish I'd thunk of 7 years ago.  I 
can't make a write cough up 040019 during this condition, but maybe 
someone else can build on on it:

For type-19, all "id"s hash to the same lock semaphore set for the lock 
table.  If the lock table isn't big enough, & you lock a lot of them 
(e.g., you forgot to release them by mistake) it is very easy to get this:

    READU threshold reached, lock on XYZ denied!

(The hashing for the lock table is similar in principle to file 
hashing.  The device, inode, & the target id's group number determine 
which lock semaphore applies.  For type-19 there is no  "group, so same 
semaphore for entire dir.)

cds

-----Original Message-----
From: Anmol Chandrakant Khopade
Sent: Tuesday, July 19, 2005 5:01 PM
To: u2-users <at> listserver.u2ug.org
Subject: [U2] DATABASE write problem

Hi, I am facing a problem wherein a "WRITE" operation to a type 19 file 
is failing in some cases. The call to STATUS() function within the ON 
ERROR clause returns error 40019. Strangely this problem does not occur 
for all the writes operations, but approximately 100 times (out of 60K 
write operations). The record id contains the current time, so it 
(Continue reading)


Gmane