Download CA Dispatch Message Guide - support CA

CADDSPL
CADD344S
SAPx taskid Unable to access type Block for GetBL-S
x is the SAPI suffix
type is Data or Index
taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)
Reason:
The SAPI task received an error when accessing or updating an internal data space
control block for a given JES data set. Messages CADD360I, CADD361I and CADD362I,
which follow the current message or the previous CADD330I message, give more
information about the JES data set.
A dump is taken and the task is interrupted. This is an internal error.
Action:
Contact Technical Support.
CADD345I
SAPx taskid LDS full - Process in Stand by for...
x is the SAPI suffix
taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)
Reason:
The SAPI task detected an LDS full condition when writing a block in the data space for a
given JES data set. Messages CADD360I, CADD361I and CADD362I, which follow the
current message or the previous CADD330I message, give more information about the
JES data set. The process is placed on standby.
Action:
The LDS full condition can be reset either by cleaning the LDS or adding a new append
LDS.
Daily process, manual deletes and/or archiving can be used to clean the LDS. These
operations can be run with the SAPI task on standby. When the LDS full condition is
reset, the SAPI task will automatically resume the process.
In the event that a new append must be added, the CADDSPL must be stopped. Either
the Stop,IMMED command for the SAPI task followed by a Close command or a direct
Close,IMMED command can be used. When CADDSPL is down, run the CADDUTIL utility
to add the new append LDS and restart the CADDSPL. The SAPI task will resume the
interrupted process.
66 Message Guide