The upgrade procedure only impacts internal X.25 drivers.
The figure below illustrates how the SAM and PAD Services user space
programs are dependent on the product's upper interfaces
(X.25 configuration files and BSD Sockets). These modules are not
affected by the upgrade procedure. This is why PAD Services users
can be certain that their applications will operate properly with
X.25 Streams.
Users of PAD Services interact with X.25 software through
the X.29 PAD Services module. Configuration and system administration
tasks are performed through SAM.
Maintenance considerations |
 |
Although SAM is able to configure all PAD Services parameters,
after a system reboot or shutdown it cannot re-start the PAD Services
daemon processes (x29server, x29printd and x29uucpd). You can start these daemons manually or you
can set up your system to have them run automatically at reboot.
Using padem |
|
The padem (PAD Emulation) program uses the BSD API to send outbound
call request packets. X.25 Classic sends outbound call requests (via padem) to the first card in the system. X.25 Streams
sends call requests to any card that is available at connection
time.
HP recommends that you identify which card padem will use
by specifying it in your X.29 configuration file, or by entering
its name at the padem prompt (refer to your padem man pages for more on this).
Printable version
