Are you certain that the dbpause finished? We've had cases here where
our backup scripts would hang on the dbpause command. Those cases were
not random however. They all happened after a file system full event.
When a file system is full and a UniData write occurs that results in a
file being
Hi,
I am backing up to a different partition which is about 5 times size of
the database partition, when you manually check the partition for the
backup files is always complete but the server will still be in a pause
state. I have 2 different servers in 2 different location and one is fine
I was thinking along those same lines Brian
But what it actually does is completely ignore the line as if it were not
present.
If you do a VLIST in fact, it generates *no* object code for that line
whatsoever.
I thought that was odd, but hey I can deal with it.
-Original Message-
Somewhere along the road the Universe engineers dropped the need to DIMENSION
the array again.
What I did was simply remove the offensive looking line, and after testing the
subroutine, it's working normally.
In other words, it's using the passed array.
This came up because the subroutine,
Of course, today's engineering failings are comparable to those from 30
years ago. :-)
Bill
- Original Message -
*From:* br...@brianleach.co.uk
*To:* 'U2 Users List' u2-users@listserver.u2ug.org
*Date:* 7/26/2012
I have a XSD file from a vendor -- mapped it to our data file -- XML is
squirting out via XMAP commands in BASIC... Everything seems hunky-dory...
But it was not working with the vendor's routines -- just found that the
'xsd' has
xsd:sequence
at the start of the 'group' - and the mapping
If the new size was bigger, it would populate those cells that were sent,
ie a (10) array sent would fill cells 1 - 10 of the (12) array
Theoretically f the new size was smaller, it would fill the array then put
the remaining ones into either the last or the zero cell depending on which
flavour,
Nope that doesn't happen :)
The line is simply ignored as if it were not even there.
If you make it bigger, then try to list past the end, the runtime blows up.
If you make it smaller, you can still address the end cells normally.
It's really as if the line isn't present. Don't ask me why it
