023

Explanation
LNKLST or library lookaside (LLA) encountered an
error that prevented LLA from completing some processing. LLA issues
other contents supervision (CSV) messages with the abend code. When
more than one abend has occurred, LLA includes the original abend
and reason code in the message or messages it issues for the sequence
of abends.
The hexadecimal reason code that describes the cause
of the abend is one of the following: Code
Explanation
00000001
While LLA was copying directory entries from a LNKLST library
to build a new LLA directory, dynamic allocation or unallocation failed.
00000002
While LLA was copying directory entries from a LNKLST library
to build a new LLA directory, OPEN failed.
00000003
While LLA was building a new LLA directory, LLA found a partitioned
data set (PDS) directory block with a record key equal to X'0000000000000000'.
00000004
While LLA was building a new LLA directory, LLA found a PDS directory
block with an incorrect record key; the PDS directory block that contained
the final PDS directory entry did not have the correct record key
of X'FFFFFFFFFFFFFFFF'.
00000005
While LLA was building a new LLA directory, LLA found a PDS directory
entry with the name X'0000000000000000'.
00000006
While LLA was building a new LLA directory, LLA found a PDS directory
block whose given length was too small to contain an integral number
of PDS directory entries.
00000007
While LLA was building a new LLA directory, LLA found a PDS directory
block for which both of the following were true: The block did not contain the final directory entry in the directory
The block's record key differed from the name of the last PDS
directory entry in the block.

00000008
While LLA was building a new LLA directory, LLA had an I/O error.
00000009
While LLA was building a new LLA directory, LLA reached the physical
end of the PDS directory before finding the last PDS directory block.
The last block must have a record key of X'FFFFFFFFFFFFFFFF'.
0000000A
While LLA was building a new LLA directory, the directory for
an LLA-managed data set contained too many directory entries for LLA
to fit into its available virtual storage.
0000000B
LLA failed unexpectedly.
00000014
An I/O error occurred during LLA processing.
00000015
A media error occurred during LLA processing.
00000016
An error occurred during data set processing.
00000017
An error occurred during SMS processing.
00000018
SMS failed to obtain required resources.
00000019
An error occurred during LLA processing.
00000100
During LLA address space initialization processing, the ATTACH
of LLA's resource manager subtask failed.
00000101
LLA address space initialization processing determined that the
LLA fetch installation exit CSVLLIX1 was not reentrant.
00000102
LLA detected that its resource manager subtask abnormally ended.
00000103
LLA fetch installation exit CSVLLIX1 was AMODE 24.
00000201
While building a new LLA directory, LLA failed while making a
table of PDS or PDSE directory entries from the directory of an LLA-managed
data set.
00000202
LLA failed while building an index for a new LLA directory.
00000203
While building a new LLA directory, LLA found no modules in the
LNKLST.
00000204
LLA directory build processing of the list of data sets to be
managed by LLA failed unexpectedly.
00000205
LLA directory build processing failed because incorrect data was
detected while parsing the LLA parmlib member CSVLLAxx.
00000206
LLA directory build processing failed because LLA failed unexpectedly
while parsing the LLA parmlib member CSVLLAxx.
00000207
LLA directory build processing failed because LLA failed unexpectedly
while processing a refresh request for specific members of an LLA-managed
data set.
00000208
During LLA MVS™ operator command
processing, the user did not have proper security authorization facility
(SAF) and security product (RACF®)
authorization to an LLA parmlib data set resource.
00000401
Dynamic allocation (SVC 99) failed. LLA may have been: Allocating an LLA-managed data set to read its directory to build
a new LLA directory.
Allocating an LLA-managed data set to copy modules from it while
staging modules.
Allocating SYS1.parmlib or another parmlib data set to process
an LLA start or update request.
Unallocating a data set that LLA had previously allocated.

00000500
Dynamic allocation or unallocation failed while LLA was staging
modules for an LLA-managed library into the virtual lookaside facility
(VLF) data space.
00000501
The LLA staging installation exit CSVLLIX2 was AMODE 24.
00000A00
While LLA was obtaining PDS directory entries for an LLA-managed
data set during a selective module refresh, BLDL returned with a return
code greater than 4.
00000A01
LLA directory refresh processing could not obtain sufficient storage
to hold all the PDS directory entries accumulated from selective LLA
directory refreshes.
00000A02
LLA directory update processing failed while reading the LLA parmlib
member CSVLLAxx, which contains the control statements needed to perform
the LLA directory update. The parmlib read routine detected that the
input parameter list contained incorrect data.
00000A03
LLA directory refresh processing failed unexpectedly while reading
the LLA parmlib member CSVLLAxx, which contains the control statements
needed to perform the LLA directory update.
00000A04
LLA directory refresh processing failed unexpectedly while parsing
the LLA parmlib member CSVLLAxx, which contains the control statements
needed to perform the LLA directory update.
00000A05
LLA was unable to refresh a PDSE library.
00000A50
LLA's cross memory directory access routine was entered with incorrect
parameters.
00000B00
LLA module staging processing did not convert a floating point
number to 64-bit unsigned binary because the number was less than
one.
00000B01
LLA module staging processing was unable to convert a floating
point number to 64-bit unsigned binary because the number was too
big to be represented by 64 bits.
00000B02
LLA module staging processing was unable to convert a floating
point number to 64-bit unsigned binary because the number was not
normalized.
00000B50
An incorrect LLPM parameter area has been passed to the LLA search
routine.
00000B51
The LLA search routine was called from a program which was not
running under an supervisor request block (SVRB).
00000B52
The LLA search routine was called with an incorrect DEB as input.
00000B53
The LLA search routine was called with an incorrect value in LLPPCNCT.
00000C00
The pointer to LLA's component trace buffer was outside of the
projected storage range for the buffer.
00000D00
LLA directory build processing failed unexpectedly while processing
the LLA parmlib member CSVLLAxx.
00000D01
LLA directory update processing failed while reading the LLA parmlib
member CSVLLAxx, which contains the control statements needed to perform
the LLA directory update. The parmlib read routine detected that the
input parameter list contained incorrect data.
00000D02
LLA directory refresh processing failed unexpectedly while reading
the LLA parmlib member CSVLLAxx, which contains the control statements
needed to perform the LLA directory update.
00000D03
LLA directory refresh processing failed unexpectedly while parsing
the LLA parmlib member CSVLLAxx, which contains the control statements
needed to perform the LLA directory update.
00000D05
LLA directory refresh processing failed unexpectedly while allocating
the LLA parmlib member CSVLLAxx, which contains the control statements
needed to perform the LLA directory update. The allocation was performed
using the IEFPRMLB service. A previous message issued by the IEFPRMLB
service accompanies this ABEND.
00000E01
While LLA was building a new LLA directory, dynamic allocation
or unallocation failed.
00000E02
While LLA was building a new LLA directory, OPEN failed.
00000E03
While LLA was building a new LLA directory, LLA found no data
sets to manage.
00000E04
While LLA was building a new LLA directory, LLA found that a data
set to be managed by LLA was not a PDS.
00000E05
While LLA was building a new LLA directory, LLA found that FREEZE
or NOFREEZE was specified for a non-LLA data set.
00000E06
During LLA MVS operator command
processing, the user did not have proper SAF and security product
(RACF) authorization to an
LLA-managed data set resource.
00000E07
While LLA was building a new LLA directory, LLA found that a data
set to be managed by LLA was a PDSE that was not known to be a load
library. Make sure that the data set was not empty and had at least
one program object in it.
00001200
The caller invoked an LLACOPY macro with an incorrect data control
block (DCB) parameter.
00001201
The caller invoked an LLACOPY macro with an incorrect DCB parameter.
The DCB does not point to a valid DEB.
00001202
The caller invoked an LLACOPY macro whose DCB references a data
set for which the user does not have proper SAF security (RACF) authorization.
00001203
The caller invoked an LLACOPY macro with a zero DCB parameter.
00001204
The caller invoked an LLACOPY macro with an incorrect level parameter
list or non-zero reserved fields.
00001205
The user invoked an LLACOPY macro while in problem state.
00001206
CSVLLCPY was called with an invalid DCB - data set not PDS(E).

System action
If the LLA address space ends because of this
error, the system usually attempts to restart LLA in another address
space. LLA issues one or more of the following messages: CSV222I,
CSV226E, CSV227I, CSV247I.
If the failed LLA address space had
not become active and had been created to recover from a prior LLA
address space failure, the system issues message CSV218E without restarting
LLA.
Specific system actions for each reason code are as follows: Code
System Action
00000001
This error was preceded by an abend for which LLA took an SVC
dump and recorded the error in logrec data set. If SVC 99 itself failed,
LLA issues abend X'023', reason code X'00000401',
and message CSV224I. If this error occurred during an initial LLA
directory build, LLA also issues abend X'023', reason code X'00000201',
to end its address space.
00000002 through 00000019
DFSMS may
take an SVC dump.  LLA records this error in the logrec data set.
The indicated library will not be processed. LLA issues message CSV221I
or CSV247I, which contains this reason code in its message text. If
this error occurred during an initial LLA directory build, LLA also
issues abend X'023', reason code X'00000201', to
end its address space.
00000100
LLA takes an SVC dump and records this error in the logrec data
set. The next system action depends on what release you are using;
for MVS/SP 3.1,
the LLA address space ends.  For MVS/SP 3.1.0 or higher, LLA continues processing
without its resource management subtask until it determines if the
reattach threshold has been reached.  If the threshold has not been
reached, LLA attempts to reattach the subtask. Otherwise, LLA continues
processing without its resource management subtask.
00000101
LLA initialization issues message CSV232I, and continues processing
as if CSVLLIX1 was not installed in the LNKLST.
00000102
LLA's resource management subtask abnormally ends, and then the
LLA address space also abnormally ends.
00000103
LLA initialization issues message CSV232I, and continues processing
as if CSVLLIX1 was not installed in the LNKLST.
00000201
For dynamic allocation errors, LLA issues message CSV224I; for
PDS related I/O errors, LLA issues message CSV225I, for PDSE related
errors, LLA issues message CSV247I. In any case, LLA issues message
CSV221I to show how far the LLA directory build had progressed prior
to the error, and includes a reason code that identifies the specific
error. Then, if the error occurred during an LLA directory refresh,
LLA issues CSV217I and keeps the old directory active. Otherwise,
the LLA address space ends.
00000202, 00000204, 00000206, 00000207
For the original abend that LLA detected, LLA takes an SVC dump
and records the error in the logrec data set. LLA then issues this
abend.  If the error occurred during initial build processing, LLA
ends its address space.  Otherwise, LLA keeps the old directory active.
00000203
LLA takes an SVC dump and records the error in the logrec data
set. Then, if the error occurred during an LLA directory refresh,
LLA issues CSV217I and keeps the old directory active. Otherwise,
the LLA address space ends.
00000205
LLA issues message CSV235I, CSV236I.  If the error occurred during
an LLA directory refresh, LLA issues message CSV217I and keeps the
old directory active. Otherwise, the LLA address space ends.
00000208
If the error occurred during an LLA directory refresh, LLA issues
CSV217I and keeps the old directory active.  If the error occurred
during an initial directory build, LLA issues abend X'023',
reason code 204, to end its address space.
00000401
LLA issues message CSV224I, which includes dynamic allocation's
specific error and information codes.  LLA takes an SVC dump and records
the error in logrec data set. LLA's subsequent actions depend on the
task LLA was performing when the dynamic allocation was requested: For MVS/SP 3.1,
if LLA was allocating a data set to read its directory to build a
new directory, then LLA issues message CSV221I.  If the error occurred
during an LLA directory refresh, LLA also issues message CSV217I and
keeps the old directory active.  If the error occurred during an initial
directory build, LLA issues abend X'023', reason code X'00000201',
to end its address space.
For MVS/SP 3.1.0e
or higher, if LLA was allocating a data set to read its directory
to build a new directory, then LLA issues message CSV241I. If the
error occurred during an LLA directory refresh, LLA also issues message
CSV217I and keeps the old directory active. If the error occurred
during an initial directory build, LLA issues abend X'023',
reason code X'00000204', to end its address space.
If LLA was allocating a data set to copy modules from it while
staging modules, then LLA does not stage modules from this library.
If LLA was allocating a parmlib data set to process a start LLA
request, LLA issues message CSV235I, CSV236I, and does not start the
LLA address space.
If LLA was allocating a  parmlib data set to process a LLA refresh
request, LLA issues message CSV235I, CSV236I and keeps the old directory
active.
If LLA was unallocating a data set that it had previously allocated,
then LLA takes no further action.

00000500
If SVC 99 itself failed, LLA issues abend X'023', reason
code 401, and message CSV224I.  LLA's subsequent actions depend on
what release you are using. For MVS/SP 3.1, this error was preceded by an
abend for which LLA took an SVC dump and recorded the error in the
logrec data set. LLA's resource manager subtask ends, causing the
LLA address space to end.
For MVS/SP 3.1.0e or higher, LLA's resource manager
subtask ends and LLA continues processing without its resources management
subtask until it determines if the reattach threshold has been reached.
 If the threshold has not been reached, LLA attempts to reattach the
subtask.  Otherwise, LLA continues processing without its resource
management subtask.

00000501
LLA issues message CSV232I, and continues processing as if CSVLLIX2
was not installed in the LNKLST.
00000A00 through 00000A05
LLA takes an SVC dump and records the error in the logrec data
set. Then, LLA issues message CSV217I, and does not perform the requested
LLA refresh.
00000A50
If the caller is LLA or BLDL, the caller takes an SVC dump and
records the error in the logrec data set. Then, the caller ends the
LLA address space with an abend 312.
00000B00 through 00000B02
LLA takes an SVC dump and records the error in the logrec data
set. Then, LLA's resource manager subtask ends, and LLA also issues
abend X'023', reason code X'00000102', to end its
address space.
00000B50, 00000B51, 00000B52, 00000B53
If the caller is BLDL, the caller takes an SVC dump, records the
error in the logrec data set. and abends the caller with a X'212' abend.
 If the caller is LLA, the caller takes an SVC dump, records the error
in the logrec data set, and provides the module using program fetch.
00000C00
LLA takes an SVC dump and records the error in the logrec data
set. Then, LLA trace is deactivated, and LLA continues without component
trace capabilities.
00000D00, 00000D01, 00000D02, 00000D03
LLA takes an SVC dump and records the error in the logrec data
set. If the error occurred during an LLA directory refresh, LLA issues
message CSV217I and keeps the old directory active.  Otherwise, the
LLA address space ends.
00000E01
LLA issues message CSV224I, which includes dynamic allocation's
specific error and information codes.  If the error occurred while
allocating the data set, LLA issues message CSV241I which includes
the name of the data set which could not be allocated.  If the error
occurred during an LLA directory refresh, LLA also issues message
CSV217I and keeps the old directory active.  If the error occurred
during an initial directory build, LLA issues abend X'023',
reason code X'204' to end its address space.
00000E02
LLA issues message CSV240I, which includes the name of the data
set which could not be opened.  This error is preceded by an abend
for which LLA takes an SVC dump and records this error in the logrec
data set.  If the error occurred during an LLA directory refresh,
LLA also issues message CSV217I and keeps the old directory active.
 If the error occurred during an initial directory build, LLA issues
abend X'023', reason code X'204' to end its address
space.
00000E03
If the error occurred during an LLA directory refresh, LLA also
issues message CSV217I and keeps the old directory active.  If the
error occurred during an initial directory build, LLA issues abend X'023',
reason code 204 to end its address space.
00000E04
LLA issues message CSV242I, which includes the name of the data
set which is not a PDS. If the error occurred during an LLA directory
refresh, LLA also issues message CSV217I and keeps the old directory
active. If the error occurred during an initial directory build, LLA
issues abend X'023', reason code X'204' to end its
address space.
00000E05
LLA issues message CSV245I, which includes the name of the data
set for which FREEZE or NOFREEZE was specified. If the error occurred
during an LLA directory refresh, LLA also issues message CSV217I and
keeps the old directory active.  If the error occurred during an initial
directory build, LLA issues abend X'023', reason code X'204',
to end its address space.
00000E06
If the error occurred during an LLA directory refresh, LLA issues
CSV217I and keeps the old directory active.  If the error occurred
during an initial directory build, LLA issues abend X'023',
reason code 204, to end its address space.
00000E07
LLA issues message CSV242I which includes the name of the data-only
or empty PDSE.  If the error occurred during an LLA directory refresh,
LLA also issues message CSV217I and keeps the old directory active.
If the error occurred during an initial directory build, LLA issues
abend X'023', reason code X'00000204' to end the
address space.
00001200
LLACOPY abends.
00001201
LLACOPY abends.
00001202
LLACOPY abends.
00001203
LLACOPY abends.
00001204
LLACOPY abends.
00001205
LLACOPY abends.
00001206
LLACOPY abends.

Operator response
Contact hardware support.

System programmer response
Follow the system programmer response
for any messages issued to the console or the job log and for any
accompanying abends.
If the problem persists and the program
is not in error, search problem reporting data bases for a fix for
the problem. If no fix exists, contact the IBM® Support Center. Provide the following: All printed output and output data sets related to the problem.
The program listing for the job.
The JCL for the job.
The Logrec data set error record.

Programmer response
Follow the application programmer response
for accompanying CSV messages issued both to the console and the system
log (SYSLOG). Follow the application programmer response for any other
accompanying abends.
For the reason codes below, do the following: Code
Response
00000101
Make sure that the LLA fetch installation exit, CSVLLIX1, is reentrant,
and then link edit the exit again.
00000103
Make sure that the LLA fetch installation exit, CSVLLIX1, is AMODE
31 or AMODE ANY, and then link edit the exit again.
00000203
Verify that the catalog for the LNKLST data sets is valid and
has not been overlaid.
00000208
Ensure that the person who issues the LLA operator command has
proper RACF authorization (update)
to the LLA-managed data sets.
00000501
Make sure that the LLA staging installation exit, CSVLLIX2, is
AMODE 31 or AMODE ANY, and then link edit the exit again.
00000A00
Follow the programmer response for CSV217I, and see the logrec
data set, which may contain information on specific I/O errors. If
no specific I/O error is evident, then stop and restart LLA.
00000A01
Follow the programmer response for CSV217I, and issue a complete
LLA refresh.
00000A50 through 00000B02
Restart LLA.
00000B50, 00000B51, 00000B52, 00000B53
Respond to any related messages that appear in the system log
(SYSLOG) and to any related abends.  Follow the programmer response
for a X'212' abend.
00000C00
To regain component trace capabilities, stop and then restart
LLA.
00000E03
Verify that the parmlib members specifying the list of data sets
LLA is to manage is correct.  Follow the programmer response in for
messages CSV217I or CSV218I.
00000E06
Ensure that the person who issued the LLA operator command has
proper RACF authorization (update)
to the LLA-managed data sets.
00000E07
Eliminate the PDSE data-only library from the specified parmlib
member.
00001200
Correct the DCB input parameter for the LLACOPY macro.  Make sure
that the input DCB has been opened and that the DCB is not being overlaid.
 Run the job step again.
00001201
Correct the DCB input parameter for the LLACOPY macro.  Make sure
that the input DCB has been opened, and that the DCB is not being
overlaid and points to a valid DEB.  Run the job step again.
00001202
Ensure that the invoker of the LLACOPY macro has sufficient RACF authority to the data sets
described by the LLACOPY input DCB. Run the job step again.
00001203
Correct the DCB input parameter of the LLACOPY macro.  The input
DCB must be a valid opened DCB. Run the job step again.
00001204
Ensure that all reserved fields are zero.  Ensure that the macro
library used to compile or assemble the program invoking LLACOPY corresponds
to the target environment. Run the job step again.
00001205
Ensure that the invoker of the LLACOPY macro is supervisor state.
Run the job step again.
00001206
Ensure that the input DCB represents a PDS or PDSE. Run the job
step again.

Source
Contents supervision (CSV)