EMS Messages
Spooler FASTP Network Print Processes Manual — 427528-006
B - 112
FASTP EMS 512 Text Messages
Cause.
FASTPX25 could not extract the TLAM response from the SPI buffer using the
SSGET 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.
512
proc-num
is the process number (CPU, PIN) of the process.
device-name
is the Spooler device name.
token-name
is the name of the token.
%
nnnnnn
is the octal return code from the SSGETTKN procedure.
This message can be generated by FASTPXNS or FASTPX25 only.
For FASTPXNS, the cause, effect, and recovery are as follows:
Cause.
FASTPXNS could not retrieve the specified token from the SPI buffer using
the SPI SSGETTKN 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.
proc-num
DEV:
device-name
SPI SSGETTKN
token-name
Error:
%
nnnnnn