Difference betn 32-bit OS and 64-bit OS

[rajesh_65]

Hi,

Wanted to know "HOW EXACTLY CAN ONE MAKE OUT IF A GIVEN HP-UX SYSTEM HAS A 32-BIT OS OR 64-BIT OS" ?

We believe "UNAME" and "GETCONF KERNAL_BITS" are not sufficient parameters to guage this.

Can someone please suggest?

[Joseph Loo]

hi,

if getconf KERNEL_BITS do not, how about sam -> Performance Montiro -> System Properties -> Under "Processor", Kernel Width Support or Under "Operating System", OS Kernel Width.

still unconvince, u may refer to this thread:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=19414

regards.

[Biswajit Tripathy]

"getconf KERNAL_BITS" should tell you if the h/w
is 32 or 64 bit.

"file /stand/vmunix" should tell you if the vmunix is
32 or 64 bit (for 32 bit, it should print PA-RISC1.1
executable; for 64 bit, it should print PA-RISC 2.0)

- Biswajit

[Indira Aramandla]

Hi Rajesh

To check if the OS is 32/64 bits
getconf KERNEL_BITS
will give you 32/64 info.

To see what your box can handle
getconf HW_CPU_SUPP_BITS

Here are a few comparisons of 32-bits and 64-bits.
In 64-bit OS you have larger process address space, concurrent execution of 64-bit and 32-bit applications, shared object mixed mode access.
In 32-bit OS, only 32 bits of process address space was available to the user. The 32-bit address space layout limited applications to:
1.00 GB process text, 90 GB process private data using SHARE_MAGIC, or, 1.90 GB process private data using EXEC_MAGIC, 1.75 GB shared object space, 25 GB user I/O
With 64-bits of address space now available, users can access, 4.00 TB process text, 4.00 TB private data, 8.00 TB shared object space. User I/O is 1/16 of 1.00 TB and is included within the 8.00 TB of shared object space.
To take advantage of the larger address space, applications must be recompiled as 64-bit executables. Existing 32-bit executables will continue to run as before and can be run concurrently with 64-bit executables. 32-bit and 64-bit applications will also be given the ability to access the same shared objects. Sharing the same object is referred to as "mixed mode access."
64-bit program can always open a large file, and can always extend a small file past 2 GB if the file system has been enabled for large files. The mechanisms described in the White Paper are unnecessary for 64-bit programs.

IA

[rajesh_65]

We built an application on an environment that showed '64' against getconf KERNAL_BITS and HW_CPU_SUPP_BITS, but when we ran the application on a "NEW" 64-bit environment, it resulted in a "SIGBUS error".

To check if it was the problem of the application itself, we ran it on an environemnt (similar) to the one where we had originally built it, but found that the application responded successfully.

What could be the possible reasons for this failure on the new environment?

Please let us know. Thanks.

[Indira Aramandla]

Hi Rajesh,

Did you recompile the application on the new 64-bit environment.

IA

[Darrel Louis]

Rajesh,

Check the lib/c patch level on the two servers.
It could be that the lib/c or ld patch level is different and causing the SIGBUS.

GL

Darrel

[rajesh_65]

Hi,

I haven't recompiled the application on new 64-bit environment, but i have compiled the application on other system with appropriate 64-bit flags (which should be ok, i gues).

And i think it is not mandatory to recompile the application on new 64-bit environment, please let me know if iam wrong here.

Hi Louis:
could you please let me know how to check patch level on two servers.

Rajesh

[Darrel Louis]

Rajesh,

To check your patch level, perform the following on each server:

List installed bundles:
swlist -l bundle

Check particular Patch:
swlist -l fileset|grep PHCO_12345
or
swlist -l fileset|grep -i lib

Good Luck Darrel

[rajesh_65]

Hi Louis,

Thank you very much for your time,

I found some patches which are not installed on new 64-bit system, and i have downloaded and installed,
but i could not found 'LdapUxClient.LDAP-C-SDK' library on our new 64-bit system, and tried to download it and to my surprice the search didnot give any result.
With out above library i once again tried to install and configure my 64- bit application, i received the same error(SIGBUS), So i just wanted to know what could be wrong.

Any kinf of help is appreciated.

Regards
rajesh