EMS Messages
Spooler FASTP Network Print Processes Manual — 427528-006
B - 114
FASTP EMS 512 Text Messages
Cause.
FASTPXNS could not initialize the SPI buffer using the SPI SSINIT procedure.
This error indicates FASTPXNS is having difficulty obtaining the Ethernet address of
the TLAM controller. This address is obtained using the SPI interface to TLAM through
the SCP process (usually $ZNET).
Effect.
The device is placed offline.
Recovery.
To correct the problem:
Ensure that the SCP process is running correctly.
Check that the following command works correctly:
SCF INFO SERVICE $
lan
.#L18023
where
lan
is the name of the TLAM IOP.
If your installation doesn’t use $ZNET, check that you have added a DEFINE=SCP
statement before running the Spooler Supervisor.
If the error persists, contact your service provider as described in
Troubleshooting and
Reporting Problems
on page 8-1.
For FASTPX25, the cause, effect, and recovery are as follows:
Cause.
FASTPX25 could not initialize the SPI buffer using the SSINIT procedure.
FASTPX25 uses this information to verify that the X25AM SU is configured to use an
SVC.
Effect.
If FASTPX25 cannot obtain this information, it assumes that the SU uses an
SVC and attempts to print.
Recovery.
If your print job is unsuccessful, check the following:
Ensure that the SCP process is running correctly.
If your installation doesn’t use $ZNET, check that you have added a DEFINE=SCP
statement before running the Spooler Supervisor.
If the error persists, contact your service provider as described in
Troubleshooting and
Reporting Problems
on page 8-1.
