HP-UX Aries PA-RISC and s800

[cheesytime]

Hello folks,

We are trying to migrate a couple old applications to our brand new infinity box.

I noticed that on HP-UX 10.20 most stuff that lies on /usr/bin will show as

s800 shared executable dynamically linked

while other bins will show as

PA-RISC1.1 shared executable -not stripped

Why do you have s800 binaries on the 10.20 system?

What is the difference between s800 and PA-RISC1.1 binaries and why do we have both on this box?

Does aries run the s800 and the PA-RISC binaries or only those binaries that file will show as PA-RISC?

Below is some usefull information that might help answer this question:

model:
9000/803/D220

B.10.20 A 9000/803 2012416907

[Jeff_Traigle]

I had D-classes running 10.20 at a previous job a few years back. If I remember correctly, 10.20 was not an integrated distribution. There was separate media for servers (s800) and workstations (s700). My guess is that the binaries you see as s800 were compiled specifically for the server distribution.

As for Aries running s800 binaries on Integrity (not infinity) servers, I have no idea.

[Steven E. Protter]

Shalom,

Aries is the system designed to run PA-RISC compiled binaries on IA-64 Itanium systems without recompile.

The performance penalty in our tests was 70%.

PA-RISC 1.1 binaries are merely binaries compiled with those libraries and standards so they will run on a system that supports PA-RISC binaries.

SEP

[cheesytime]

The question is:

On our 10.20 why do we see all s800 binaries and not PA-RISC1?

Does Aries will run the s800? I take the s800s as RISC binaries as well, right?

Thanks

[James R. Ferguson]

Hi:

The term "s800" represented the "800 Series" of *servers* for the HP9000 family of PA-RISC processors. There was a "700 Series" which were the workstations.

The designation between S800 and PA-RISC1.1 binaries is meaningless to Aries.

http://docs.hp.com/en/B2355-60130/Aries.5.html

Regards!

...JRF...

[cheesytime]

Thanks for the quick answers, you guys are just there!

I need to come up with a report explaining the following:

What are exactly PA-RISC1.0 binaries on our 10.20 system?

What are exactly s800 binaries on our 10.20 system and why these are NOT PA-RISC if we have PA-RISC processor?

PA-RISC1.0, PA-RISC2.0 and s800 will be run by Aries, correct?

Thank you

[James R. Ferguson]

Hi (again) Andrew:

You need not worry. See this document for more information on the terms used:

http://docs.hp.com/en/B2355-90655/ch01s01.html

Among other details, see the section titled "ARIES LIMITATIONS" in:

http://docs.hp.com/en/B2355-60130/Aries.5.html

Regards!

...JRF...

[Dennis Handly]

>s800 shared executable
>PA-RISC1.1 shared executable

The first is PA 1.0, which is forward compatible on 10.20. It was named s800 to distinguish it from s300 or s500. That was before there were multiple versions of PA-RISC.
Note: 10.10 was the last release on PA 1.0 hardware.

So s800 is shorthand for PA-RISC1.0.

>Jeff: My guess is that the binaries you see as s800 were compiled specifically for the server distribution.

No, it indicates that these are executables that would run on PA 1.0, 1.1 and 2.0 boxes.
It is easier to only have one version, if not performance critical.

[rick jones]

While 10.20 was not "supported" on PA-RISC 1.0 based systems, many of the build mechanisms employed for 10.20 still produced PA1.0 binaries, which is why 10.20 (heck, perhaps even 11.0) still had some PA1.0 (as already pointed-out, called s800) binaries in it.