I generalized this so it can be used in a recall statement. To implement, I
created a I-desc subroutine that is called from a I-desc in a dictionary
that I can deliver (in my case SYS.DICT).
For example:
SORT VOC WITH F1 = Q]F] AND @ID = [PDA] 32.64BIT USING DICT SYS.DICT
The interesting line in
What happens if BITS = 32 or 64? Could that happen? In that case, neither of
First two cases would hit, RESULT would still be a 32 or 64.
George
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Mike Hulls
Sent:
If you wanted a quick glance at a file with out running a program, And if
your careful and have root or admin access you can use filepeek.
The only thing you need is the first page, then 'q' to quit.
Default mode will tell you.
# /usr/uv/bin/filepeek VOC
filepeek status:
Active file
Thanks guys. That should put me on the right track. I have a few big
files that probably need to be moved to 64 bit to future proof them.
On Sat, Jan 5, 2013 at 9:29 PM, Allen Egerton aeger...@pobox.com wrote:
John,
Following up on Marc's reply. Open the file, then do a status on the
UVFIXFILE is a good command for this.
If the file is 32bit it works (maybe just trace group 1).
If the file is 64bit it does not work, but emits an error message and sets
@SYSTEM.RETURN.CODE to -1.
___
U2-Users mailing list
Anyone know of a command that will tell you what type of file you are
dealing with Universe as it relates to 32 or 64 bit files?
ANALYZE.FILE doesn't seem to give that info
--
John Thompson
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
John,
I don't remember which one but I believe it's one of the STATUS atributes.
After OPENing the file your can do a STATUS of the file variable and one of
these tells you if the file is 64bit. I had to do a program a few months ago
to find all 32 bit files that were nearing the 2gb limit and
