HP 3000 Manuals HP 3000 Manuals
HP Software Integration Sockets/iX Enhancements
by Le Hong
Cooperative Computing Systems Division
HP Sockets/iX is customer-installable. Prior to installation, you should
install and configure the system for NS LAN. HP Sockets/iX must be
installed in the HPSKTS account.
HP Sockets/iX requires the use of the loopback feature of HP Network
Services to operate. This feature is started by issuing the command:
:NETCONTROL NET=LOOP;START
prior to issuing the command:
:NSCONTROL START
HP Sockets/iX revision A.03.00 uses four network port addresses. These
port addresses default to 5719, 5720, 5721, and 5732. If you are using
these port addresses for other purposes, HP Sockets/iX lets you specify
the port addresses you want it to use when executing the SMD.PUB.HPSKTS
program. Refer to Chapter 3 of the HP Software Integration Sockets
System Administrator's Manual (92568-90002) for more details.
The following list contains information about account capabilities, group
capabilities, and file access permissions for the HP Sockets/iX product.
After installing the HP Sockets/iX product, one account and twelve groups
are generated on your system. They are:
Account: HPSKTS
CAP=AM,AL,GL,PS,ND,SF,BA,IA,PM,PH,MR
ACCESS=(R,W,X:ANY;A,L:AC)
Since this account has the PM capability, you must have a password
for it.
Groups : H.HPSKTS
CAP=BA,IA
ACCESS=(R:ANY;L,W,A,X,S:GU)
Groups: INTERNAL.HPSKTS
CAP=BA,IA
ACCESS=(R,W:ANY;A,L,S,X:AC)
Groups: LIB.HPSKTS
CAP=BA,IA
ACCESS=(R:ANY;W,A,L,X,S:GU)
Groups: PUB.HPSKTS
CAP=BA,IA,PM,PH,MR
ACCESS=(R,X:ANY;W,A,L,S:AC)
Groups: REF.HPSKTS
CAP=BA,IA
ACCESS=(R:ANY;W,A,L,S,X:AC)
Groups: TUTORIAL.HPSKTS
CAP=BA,IA
ACCESS=(R:ANY;W,A,L,S,X:AC)
Groups: TVALIDAT.HPSKTS
CAP=BA,IA
ACCESS=(R,X,W,A,L,S:GU)
Groups: VALIDATE.HPSKTS
CAP=BA,IA
ACCESS=(R:ANY;X,W,A,L,S:GU)
Groups: TUTDICT.HPSKTS
CAP=BA,IA
ACCESS=(R:ANY;W,A,L,X,S:AC)
Groups: REFDICT.HPSKTS
CAP=BA,IA
ACCESS=(R:ANY;W,A,L,X,S:AC)
Groups: CONFIG.HPSKTS
CAP=BA,IA
ACCESS=(R:ANY;W,A,L,X,S:GU)
Groups: TCONFIG.HPSKTS
CAP=IA,BA
ACCESS=(R,W,A,L,X,S:GU)
The following user is created:
User: MGR.HPSKTS
CAP=AM,AL,GL,ND,SF,BA,IA
Other Requirements and Dependencies
These are other requirements and dependencies of HP Sockets.
Network.
MPE/iX machines and HP-UX machines in the same HP Sockets domain must be
connected by the same LAN. MPE/iX machines must have Network Services
(NS) software installed. Loopback must be initiated for the MPE/iX
system by executing the NETCONTROL NET=LOOP;START command prior to
issuing the ;NSCONTROL START command. Both of these commands require NM
capability and may need to be issued from the operator's console.
HP-UX.
HP Sockets/iX revision A.03.00 is fully compatible with HP Sockets/UX
revision A.03.00, HP Sockets/iX revision A.02.00, and the NetIPC version
of HP Sockets/UX revision A.02.00. It is not compatible with revisions
of HP Sockets previous to A.02.00.
HP Sockets version compatability between MPE/iX and HP-UX.
The next section contains detailed information on the compatibility
between HP Sockets versions on MPE/iX and HP- UX.
Revision A.03.00 of HP Sockets will run on:
* An HP3000/900 with version 4.0 or 4.7 of the MPE/iX operating
system
* An HP9000/300, 400, 600, 700, or 800 with version 8.x or 9.x of
the HP-UX operating system
Both HP3000s and HP9000s can exist in a single HP Sockets domain because
the A.03.00 NetIPC version of HP Sockets/iX interoperates with the
A.03.00 BSD sockets version of HP Sockets/UX.
Coexistence of Nodes A.02.00 and A.03.00.
This section summarizes when A.02.00 nodes and A.03.00 nodes can coexist
in the same HP Sockets domain.
When there are any HP-UX nodes in the domain and any of the HP-UX nodes
run revision A.03.00:
* If there are any MPE/iX nodes in the domain, you must roll all the
HP-UX and MPE/iX nodes to HP Sockets revision A.03.00. HP Sockets
revision A.02.00 cannot be used.
* If all HP-UX nodes continue to run A.02.00 but any MPE/iX nodes
run revision A.03.00, there may still be an MPE/iX node running
revision A.02.00. All HP-UX nodes must run the NetIPC version.
* If there are no HP-UX nodes in the domain, only MPE/iX nodes, some
of the MPE/iX nodes can run revision A.03.00 while others run
revision A.02.00.
In any case, nodes running revision A.02.00 will not be able to access
the new functionality provided on the nodes running revision A.03.00.
Revision A.03.00 will not interoperate with HP Sockets revisions A.01.00,
A.01.10, or A.01.11.
Software
If you want to use the data manipulation capability of HP Sockets, at
least one MPE/iX machine must have the following software installed:
- HP C/iX language compiler
- Link Editor
If your MPE/iX system is used for developing HP Sockets application
adapters in FORTRAN, COBOL, or Pascal, you must install compilers for
those languages.
RINs.
You must configure enough Resource Identification Numbers (RINs) for your
MPE/iX system. HP Sockets/iX uses seven local RINs.
Job Limit.
HP Sockets programs (including the HP Sockets Management Daemon, SMD) run
in one job. You may have to adjust the job limit for your MPE/iX system.
Sessions.
Each program started by using the SpStartProcess call uses one session.
You may need to adjust the number of sessions allowed according to the
number of processes used in your HP Sockets domain.
File Descriptors.
Each program calling SpInit on an MPE/iX node uses two message files, one
for normal messages and one for message or file notification and process
stopping. For each such program, you must allow three file descriptors
for HP Sockets: one for each of the two message files, and one for the
mapped file that gets checked (by reading a flag), to see whether HP
Sockets is running.
Post Installation
In order to use HP Sockets/iX, the HP Sockets Management Daemon (SMD)
must be running. We recommend that you start the SMD by streaming the
job file STARTSMD.PUB.HPSKTS after the network services have been
started. The job file contains the following lines:
!job startsmd,mgr.hpskts/sapphire;pri=cs
!run smd.pub.hpskts
!eoj
Change the passwords to the passwords you set on the HPSKTS account and
MGR user. For more information about administering the HP Sockets
systems, please refer to the HP Software Integration Sockets System
Administrator's Manual (92568-90002).
Make sure that networking has been started before running the SMD and
that loopback has been started. Typical commands to do this are:
:NETCONTROL NET=LAN1;START
:NETCONTROL NET=LOOP;START
:NSCONTROL START
You need NM capability to execute these commands and they may need to be
given from the operator's console. Do not issue the corresponding
NETCONTROL ...;STOP commands until HP Sockets/iX has been shut down, and
you have killed SMD by executing KILLSMD.PUB.HPSKTS.
Upgrade Instructions
This is the procedure to upgrade a system currently running HP Sockets
revision A.02.00 to revision A.03.00. In general, HP Sockets provides an
upgrade mechanism only for systems running the previous revision of HP
Sockets (A.02.00 in this case). Normally, customers with HP Sockets
revisions older than the previous one might have to remove any files
associated with the old revision and install the latest revision from
scratch; however, HP Sockets revision A.03.00 provides an upgrade
mechanism for customers running HP Sockets revisions previous to A.02.00.
1. Install revision A.03.00 of HP Sockets as described in either the
HP Software Integration Sockets Installation Guide for HP-UX or
the HP Software Integration Sockets Installation Guide for MPE/iX.
2. Revalidate configuration files validated with revision A.02.00 if
you want to use the new functionality provided by revision
A.03.00.
3. Modify MPE/iX command files for the new Command Processor
functionality. New functionality is provided by several of the
commands in the Command Processor for revision A.03.00. In order
to allow access to this new functionality, additional questions
are associated with these Command Processor commands. If you have
existing HP Sockets Manager (smain) command files (on MPE/iX), you
need to modify them.
If you do not want to make use of the new functionality from your
existing script or command files, you may merely add the -V2option
on the command line when you invoke the Command Processor (cp)
from inside the HP Sockets Manager (smain). This causes the same
questions to be asked as for revision A.02.00, with defaults taken
for new functionality.
Alternatively, you could modify your script and command files to
include answers to the new questions. The Command Processor
commands affected are displaybuf, enterbuf, init, and readq.
For more details, refer to the "Command Processor Commands"
section in the "Testing" chapter of the HP Software Integration
Sockets Programmer's Manual.
Information for Upgrade from A.02.00 to A.03.00.
This is information about upgrading to HP Sockets revision A.03.00.
* The format of certain HP Sockets spool files changed for HP
Sockets revision A.03.00, requiring that a rollover program be run
to convert older files into the new format.
On MPE/iX, the rollover program does not run automatically during
the installation process. You must run it manually if you want to
convert the old format files to the new format. If the contents
of the old format files are unimportant, you can delete them
before starting up HP Sockets revision A.03.00.
To run the rollover program, you must first have the Sockets
Management Daemon (SMD) program running. To run the rollover
program on MPE/iX, you must be logged on to the HPSKTS account on
MPE/iX. The spool file rollover program requires the name of the
spool directory (or group.account for MPE/iX) containing the spool
files to be rolled.
run SPOOLRL3.PUB.HPSKTS;info="<spool directory>"
Run the rollover program on MPE/iX manually with the following
parameters after HP Sockets is installed, or else delete the old
format files before starting up revision A.03.00 of HP Sockets.
While logged on to the HPSKTS account:
run SPOOLRL3.PUB.HPSKTS;info="INTERNAL.HPSKTS"
* As described in the HP Sockets Access Routine Reference Manual,
most of the HP Sockets access routines have IList and OList
parameters, which are arrays of ten integers. The most convenient
way to declare these arrays in adapters is as follows:
In C: int IList[SpLIST_SIZE], OList[SpLIST_SIZE];
In Pascal: IList, OList : SpIntArray;
In FORTRAN: integer IList(SpLIST_SIZE), OList(SpLIST_SIZE)
In COBOL: Ilist-Table and Olist-Table are predefined for
the user.
Declaring these arrays to have fewer than ten elements may have
worked in the past. For HP Sockets revision A.03.00, undefined
and unexpected results may occur if you declare these arrays too
small. In particular, some of the access routines now attempt to
zero out all ten of the elements of OList. If OList is declared
to contain fewer than ten elements, other data will be
overwritten.