ISO8859-1 , 8
_ * 5 ;
( d
Z s
]
@ h P & E ! g
Z g
! %9 D &% 'j (a ) !J ) " * #A , $ - %8 / & 1 'L 2 ( 5F )5 7' *E 8] +k : ,b = ?r | C 3 H~ B H I H > I? ` I~ I } J
L_ M N%
N O S > Te U \ V X Y F [ \ m \ 6 ] = ]P ] O ^N _ g e f < g g h j= k l%
m m } n
f p` q m r s s t| u= 6 v7 wn x7 x i y X { = {^ { |5 / 6 |
! : * \ c "
# @ . d
% "
! q ; " e ? 0 * / 7 = g J z " = != " ' # $N % & P 'Q (' N ) v * +R ,) $ - N .. / ( ( ? Q L / K ? Y
) g w
~ d k ] W
< Z u e ? 8 x - = Ĥ b Ŧ h
A ( G j ˲
A 6 5 @ A v Ӹ Y Ԟ > R K G h M X 8 b & L - h
< Z
J
_ > T N = I y
%
Y 6
i D t S # 6 w O \ S [ # p &m
4 )libct_ffdc.a Status: An FFDC Environment does not exist for
this process. This process cannot record failure information to the
FFDC Error Stack.
libct_ffdc.a Attention: No resource name was provided to the %1$s
routine. No resource name was recorded in the report generated by
this routine, but the record was made.
libct_ffdc.a Attention: The %1$s routine received incomplete
information about the the source code file reporting the incident.
Default information was provided bythis routine on behalf of the
caller.
libct_ffdc.a Attention: The %1$s routine was unable to copy the
contents of the file %2$s to the %3$s directory. Do not discard
the original copy of this file.
libct_ffdc.a Attention: No System Log message was provided to the %1$s
routine. No message was recorded in the System Log report generated
by this routine, but a record was made in the System Log.
libct_ffdc.a Attention: No details on the incident were provided to the
%1$s routine. The detailed data section of the report made by
this routine has been omitted, but the report was recorded.
libct_ffdc.a Attention: The %1$s routine was provided a value for
detail data size that appears invalid. As a result, this routine
used the maximum length permitted for detail data. This may result
in some extraneous and unrelated information being recorded in the
record generated by this routine.
libct_ffdc.a Attention: Both a detail data field and a detail data file name
were provided to the %1$s routine. This routine only accepts
either a detail data field or a detail data file. The detail data
file was ignored in the record generated bythis routine, and the
detail data field was used instead.
libct_ffdc.a Attention: A valid pointer was not provided to the
%1$s routine to permit this routine to return the FFDC
Error Identifier of the recording. This routine cannot return
the identifier for this record, but the record was made.
libct_ffdc.a Attention: An unique FFDC Error Identifier was not
generated by the %1$s routine. The report has been made despite this
condition.
libct_ffdc.a Attention: The %1$s routine could not record
informtion on this incident to the System Log. A report was filed
in the Error Log for this incident.
libct_ffdc.a Attention: An unknown Log Event Type was provided to the
%1$s routine. Valid Log Event Types are:
FFDC_EMERG
FFDC_ERROR
FFDC_STATE
FFDC_PERF
FFDC_TRACE
FFDC_RECOV
FFDC_DEBUG
The value FFDC_DEBUG was substituted for this value in the report
generated by this routine, giving this record the lowest severity
indication available.
libct_ffdc.a Attention: An invalid FFDC Error Identifier was provided
to the %1$s routine.
libct_ffdc.a Attention: Insufficient information was provided to
identify a cataloged message to the %1$s routine.
This message information is used to describe the nature of the
incident that is being recorded to the FFDC Error Stack. As a
result, the description will be displayed using the default
message text. Users viewing the FFDC Error Stack contents in
other locales will not be able to translate this message into
the language used for that locale, meaning that the user may not
be able to understand the information recorded by this
application.
libct_ffdc.a Attention: The %1$s routine did not receive a default
message to use as a description for this incident in cases where
the cataloged message decription cannot be obtained. If the FFDC
Error Stack contents are viewed on a node where the message
does not exist, or if the FFDC Error Stack contents are viewed
when the message catalog is missing, no description information
will be presented for this entry. Users may not be able to
understand the nature of the incident without a description, which
limits the usefulness of the entry to the system administrator.
libct_ffdc.a Attention: Insufficient information was provided to
identify a cataloged message to the %1$s routine,
and no default message was supplied. Because of these
omissions, no decription information was recorded for this
incident to the FFDC Error Stack, and no description information
will be presented for this incident when the FFDC Error Stack
contents are viewed. Users may not be able to understand the
nature of the incident without a description, which limits the
usefulness of the entry to the system administrator.
FFDC Environment inherited from a previously established environment
libct_ffdc.a Attention: The information submitted for recording to the
FFDC Error Stack exceedes the record length of %1$d bytes. The
information has been truncated to fit the record size limit. Some
important diagnostic information may have been lost in the process.
Errors may occur when this information is displayed later with the
fcstkrpt command. This record size limit includes the detecting
file information, the message catalog information, the description
message, substitutional parameters to the description message, as
well as the details of the condition. In the future, record less
information, or make use of the detail data file option.
2615-000 %1$s
2615-001 libct_ffdc.a Error: The parameter passed to the library
routine fc_init_stack is not valid. The valid values are:
FC_STACK
FC_TRACE
FC_CREAT
FC_INHERIT
This process cannot make recordings to the FFDC Error Stack.
2615-002 libct_ffdc.a Error: %1$s is not supported by this version of
the %2$s routine.
2615-003 libct_ffdc.a Error: Options %1$s and %2$s cannot be combined
as options to the %3$s routine. This process cannot make recordings
to the FFDC Error Stack.
2615-004 libct_ffdc.a Error: Cannot inherit an FFDC Environment
because an FFDC Environment has not been previously established.
This process cannot make recordings to the FFDC Error Stack.
2615-005 libct_ffdc.a Error: Cannot create or inherit an FFDC
Environment, because an FFDC Environment already exists for this
process. fc_init_stack may have been attempted several times by
this process. Examine the source code for errors.
2615-006 libct_ffdc.a Error: The FFDC Environment for this process
appears to be corrupted. The FFDC Environment is not usable.
This process cannot make recordings to the FFDC Error Stack.
2615-007 libct_ffdc.a Error: Failure in allocating memory. An FFDC
Environment cannot be established. This process cannot make
recordings to the FFDC Error Stack. Check this process for memory
leak problems, and check the system for processes hoarding memory.
2615-008 libct_ffdc.a Error: An FFDC Environment cannot be
established for this process. This process cannot make recordings
to the FFDC Error Stack. This process will also be unable to
obtain FFDC Failure Identifiers for reports it makes to the
Error Log. This failure occurred because this library could not
locate any network adapter information in the Object Data
Manager (ODM), or the library could not modify the execution
environment of the process, or the operating system could not
provide a temporary pipe for this library call. Verify that space
available in the /tmp file system, which can cause problems in
creating pipes, and notify the system administrator if /tmp
appears to be near its capacity. Otherwise, contact the system
administrator and have the administrator verify that at least one
network adapter is defined in the ODM at the time that this
process executes.
2615-009 libct_ffdc.a Error: The FFDC Environment could not be
established. An FFDC Error Stack File appears to exist already for
this process in the %1$s directory. This process cannot make
recordings to the FFDC Error Stack.
2615-010 libct_ffdc.a Error: The FFDC Error Stack directory
%1$s cannot be accessed. The directory may be missing, unmounted,
or permissions may have been changed on the directory. Contact the
system administrator and report this problem. This process cannot
make recordings to the FFDC Error Stack at this time.
2615-011 libct_ffdc.a Error: An unexpected failure occurred in the
routine %1$s. This process cannot make recordings to the FFDC
Error Stack at this time. Contact the IBM Customer Support Center
for assistance in resolving this failure.
2615-012 libct_ffdc.a Error: An FFDC Environment does not exist for
this process. This process cannot record failure information to the
FFDC Error Stack.
2615-013 libct_ffdc.a Error: The %1$s routine could not record
information on this incident to the System Log. No incident report
was filed by this routine.
2615-014 libct_ffdc.a Error: The FFDC Error Stack file
%1$s cannot be accessed. The file may be missing, corrupted, or,
permissions may have been changed on the file to prohibit access.
Contact the system administrator and report this problem. This
process cannot make recordings to the FFDC Error Stack at this
time.
2615-015 libct_ffdc.a Error: The name reserved for the FFDC Error Stack
file:
%1$s
is the name of an existing directory. Ask the system administrator
to ensure that system users are not creating subdirectories in the
directory:
%2$s
If this problem occurs in multiple applications, contact the system
administrator to have the problem reported to the IBM Customer
Support Center.
2615-016 libct_ffdc.a Error: The FFDC Error Stack file
%1$s
cannot be created. Permissions on the directory have been changed
to prohibit creation of files in this directory. Contact the
system administrator and report this problem. This process cannot
make recordings to the FFDC Error Stack at this time.
2615-017 libct_ffdc.a Error: Insufficent space exists in the file
system containing the directory:
%1$s
to create an FFDC Error Stack file. This routine attempted to
reserve and FFDC Error Stack file of a minimum size of %2$d
bytes while leaving at least five percent of the file system
capacity available. The FFDC Error Stack file could not be reserved
under these constraints. This application cannot record information
to the FFDC Error Stack until more space becomes available in the
file system.
2615-018 libct_ffdc.a Error: Unable to lock the file:
%1$s
for exclusive use. The file may have been removed by another
application, or another application may have locked this file for
use and become hung. This process is unable to record incident
information to the FFDC Error Stack at this time.
2615-019 libct_ffdc.a Error: Unable to open the FFDC Error Stack file:
%1$s
The file may have been removed by another application, or the file
permissions may have been altered on the file to prohibit this
application from opening the file. Permissions on the directory
containing this file may have changed to prohibit files within it
to be modified. This application cannot record information to the
FFDC Error Stack at this time. Error code from open() system call:
%2$d.
2615-020 libct_ffdc.a Error: Unable to update the control information
within the FFDC Error Stack file:
%1$s
The file may be corrupted, or this problem can indicate an internal
error in the FFDC library software. This process should consider
the FFDC Error Stack unusable. Verify that the file exists and can
be viewed using the fcstkrpt command. If fcstkrpt fails to indicate
an error with the FFDC Error Stack file, contact the system
administrator to have this problem reported to the IBM Customer
Service Center. Error code from the write() library call: %2$d.
2615-021 libct_ffdc.a Error: Unable to relinquish exclusive access to
the FFDC Error Stack file:
%1$s
This process should consider the FFDC Error Stack unusable. Other
ancestor and descendent processes may find it impossible to use
the FFDC Error Stack if they also have FFDC Environments
established. Report this problem to the system administrator.
Do not attempt to use the FFDC Error Stack from this process.
Error code from the lockf() library call: %2$d.
2615-022 libct_ffdc.a Error: The FFDC Error Stack file:
%1$s
appears to have been corrupted. The internal routine that detected
this condition is:
%2$s
This application should consider the FFDC Error Stack unusable, and
should not attempt to make any more recordings to the FFDC Error
Stack.
2615-023 libct_ffdc.a Error: Unable to record incident information to
the FFDC Error Stack file:
%1$s
The file may be corrupted, or this problem can indicate an internal
error in the FFDC library software. This process should consider
the FFDC Error Stack unusable. Verify that the file exists and can
be viewed using the fcstkrpt command. If fcstkrpt fails to indicate
an error with the FFDC Error Stack file, contact the system
administrator to have this problem reported to the IBM Customer
Service Center. Error code from the write() library call: %2$d.
2615-024 libct_ffdc.a Error: Unable to set the read-write file pointer
within the FFDC Error Stack file:
%1$s
to offset position
%2$d
The file may be corrupted, or this problem can indicate an internal
error in the FFDC library software. This process should consider
the FFDC Error Stack unusable. Verify that the file exists and can
be viewed using the fcstkrpt command. If fcstkrpt fails to indicate
an error with the FFDC Error Stack file, contact the system
administrator to have this problem reported to the IBM Customer
Service Center. Error code from the write() library call: %3$d.
2615-025 libct_ffdc.a Error: Unable to create or inherit an FFDC
Environment. This process environment has been set to prevent the
creation or inheritance of FFDC Error Stacks. The system
administrator or other privileged user has set this control.
While this process remains capable of recording information to
the Error Log and the System Log through the FFDC
interfaces, this process is not capable of using an FFDC Error
Stack. Contact the system administrator if an FFDC Error Stack
is required by this process, and ask to have this FFDC function
restored to the process environment.
fcinit: Usage information:
fcinit [-l] | [-s{c|i}] | [-h]
Options:
-h Displays syntax and usage information
-l Permits the process to record information to
the Error Log. This option does not need
to be specified with the '-si' or '-sc'
options, since these options also permit the
process to make use of the Error Log.
-sc Establish an FFDC Environment that include an
FFDC Error Stack. If an FFDC Error Stack has
not been previously established by an ancestor
process, an FFDC Error Stack will be created.
-si Establish an FFDC Environment that include and
FFDC Error Stack, if an FFDC Error Stack was
previously established by an ancestor process.
If an FFDC Error Stack was not previously
established, an FFDC Error Stack will not be
included in the FFDC Environment for this process.
fcinit is used by scripts to establish an FFDC Environment, which
allows a process and its descendants to record information about
noteworthy incidents for later analysis in problem determination
efforts. This FFDC environment may contain an FFDC Error Stack
if the command is issued with either the -sc or the -si options.
Using an FFDC Error Stack, a process can determine how incidents
in threads or children processes can cause related incidents in
other threads or parent processes. An FFDC Error Stack cannot
be used a process establishes an FFDC Environment for itself
using the -sc options, or by inheriting an FFDC Environment
containing an FFDC Error Stack from its parent using the -si
option. Once an FFDC Environment with an FFDC Error Stack is
established, the script can use the fcpushstk command to
record incident information to the FFDC Error Stack. Scripts can
also make use of the Error Log and the System log by
using the fclogerr command when this type of FFDC Environment
is established.
When issued without any options, fcinit establishes an FFDC
Environment which permits the script to record information to
the Error Log and the System Log using the fclogerr
command. Because an FFDC Error Stack is not included in the
FFDC Environment in this case, the script cannot make use of
an FFDC Error Stack or the fcpushstk command.
fcinit: FFDC Environment successfully established.
fcinit: Unable to establish an FFDC Environment for this process.
2615-501 fcinit Error: The '%1$c' option was specified more than
once.
2615-502 fcinit Error: Unknown option specified - '%1$c%2$c'.
2615-503 fcinit Error: Cannot specify both the '%1$c' and the
'%2$c' options to this command.
2615-504 fcinit Error: Cannot obtain information about this
process from the operating system. This indicates an internal
problem with this command. Error code from getprocs() is %1$d.
Contact the IBM Customer Support Center to report this problem.
2615-505 fcinit Error: This command is being executed in its
own shell. This command should be executed within the current
shell, so that the command can alter the current shell's process
environment. To do this in Korn or Bourne Shells, use this
command as follows:
. fcinit
To do this from a C Shell, use the command as follows:
source fcinit
2615-506 fcinit Error: Cannot inherit an FFDC Environment
because an FFDC Environment has not been previously established.
This process cannot make recordings to the FFDC Error Stack.
2615-507 fcinit Error: Cannot create or inherit an FFDC
Environment, because an FFDC Environment already exists for this
process. fcinit may have been attempted several times by
this process. Examine the use of this command for possible
repititious use.
2615-508 fcinit Error: The FFDC Environment for this process
appears to be corrupted. The FFDC Environment is not usable.
This process cannot make recordings to the FFDC Error Stack.
2615-509 fcinit Error: Failure in allocating memory. An FFDC
Environment cannot be established. This process cannot make
recordings to the FFDC Error Stack. Check this process for memory
leak problems, and check the system for processes hoarding memory.
2615-510 fcinit Error: An FFDC Environment cannot be
established for this process. This process cannot make recordings
to the FFDC Error Stack. This process will also be unable to
obtain FFDC Failure Identifiers for reports it makes to the
Error Log. This failure occurred because this library could not
locate any network adapter information in the Object Data
Manager (ODM), or the library could not modify the execution
environment of the process, or the operating system could not
provide a temporary pipe for this library call. Verify that space
available in the /tmp file system, which can cause problems in
creating pipes, and notify the system administrator if /tmp
appears to be near its capacity. Otherwise, contact the system
administrator and have the administrator verify that at least one
network adapter is defined in the ODM at the time that this
process executes.
2615-511 fcinit Error: The FFDC Environment could not be
established. An FFDC Error Stack File appears to exist already for
this process in the %1$s directory. This process cannot make
recordings to the FFDC Error Stack.
2615-512 fcinit Error: The FFDC Error Stack directory
%1$s cannot be accessed. The directory may be missing, unmounted,
or permissions may have been changed on the directory. Contact the
system administrator and report this problem. This process cannot
make recordings to the FFDC Error Stack at this time.
2615-513 fcinit Error: An unexpected failure occurred in the
routine %1$s. This process cannot make recordings to the FFDC
Error Stack at this time. Contact the IBM Customer Support Center
for assistance in resolving this failure.
2615-514 fcinit Error: Unable to create or inherit an FFDC
Environment. This process environment has been set to prevent the
creation or inheritance of FFDC Error Stacks. The system
administrator or other privileged user has set this control.
While this process remains capable of recording information to
the Error Log and the System Log through the FFDC
interfaces, this process is not capable of using an FFDC Error
Stack. Contact the system administrator if an FFDC Error Stack
is required by this process, and ask to have this FFDC function
restored to the process environment.
fcteststk: Usage information:
fcteststk [ -h ] | [ -q ]
Options:
-h Displays usage information for this command.
-q Quiet mode - suppresses output from this
command.
The fcteststk command is used by a script to determine if an FFDC Environment
has been established for the process. If an FFDC Environment is
established for this process, the exit code from this command will
be set to a zero value. Any other exit code indicates that an FFDC
Environment has not been established for this process, and the
process is unable to record information to the FFDC Error Stack.
For information on establishing an FFDC Environment for a process,
consult the usage information for the fcinitstk command.
fcteststk: An FFDC Environment has been established for this process.
fcteststk: This process has not established an FFDC Environment.
This process is not permitted to record information to the FFDC Error
Stack.
fcteststk: Error detected. Cannot determine if an FFDC
Environment has been established for this process.
2615-551 fcteststk Error: Too many options specified.
2615-552 fcteststk Error: Unknown option specified - '%1$c'.
2615-553 fcteststk Error: The FFDC Environment for this process
appears to be corrupted. The FFDC Environment is not usable.
This process cannot make recordings to the FFDC Error Stack.
2615-554 fcteststk Error: An unexpected failure occurred in the
routine %1$s. This process should assume that the FFDC Environment
has not been established for this process, and that the process may
be unable to establish an FFDC Environment. Contact the IBM
Customer Support Center for assistance in resolving this failure.
fclogerr: Usage information:
fclogerr -e -t
-i [ -q ] [ -r ]
[ -s ] [ -v ]
[ -p ]
[ -l ]
[ -a ]
[ -b ]
[
{
-d[,, ...]
-x[,, ...]
-y[,, ...]
} | -f
]
fclogerr -h
Notes on these options:
* The '-q' option executes the command in 'quiet' mode,
which restricts the command from displaying warning
messages.
* If the '-d' option is specified, the '-x' and '-y'
options must also be specified, and must contain the same
number of arguments as the '-d' option.
* Each '-d', '-x', and '-y' argument indicates the
characteristics of the same positional argument in the other
options. The first type in the '-x' argument list indicates
the type of the first '-d' argument, and the first '-y'
length indicates the length of the first '-d' argument. The
second '-x' and and '-y' arguments indicate the
characteristics of the second '-d' argument, and so on.
* Up to 9 detail data items can be provided through the '-d'
option
fclogerr is used by a script to record information about failures
and noteworthy incidents to the System Log and the Error Log.
This information should provide detailed information about the
incident that can be used by problem analysis efforts to identify
the incident, its cause, and the actions that should be taken in
response to this incident.
fclogerr: Error detected. Because failures were detected, this
command did not attempt to record information to the System Log
and the Error Log.
2615-601 fclogerr Error: Unknown option specified - '%1$c'.
2615-602 fclogerr Error: The %1$s option has been specified more
than once. The option can only be specified once to this command.
Information will not be recorded to the System Log or to the
Error Log.
2615-603 fclogerr Attention: The 'i' option was not provided to this
command, or the file name provided as an argument to the 'i' option
is not a valid file name. The command cannot obtain the code number
of the Error Log template to be used in this recording.
The command will use its own Error Log template to record this
information:
Error Log Template Label: %1$s
Identifier of this template: %2%x
2615-604 fclogerr Attention: Unable to open the file:
%1$s
Because the file cannot be opened, fclogerr will use the errlogger
command to record information to the Error Log.
Error from fopen() system call 2615-605 fclogerr Attention: Unable to locate the symbolic name:
%1$s
in the file:
%2$s
fclogerr cannot obtain the code number of the Error Log template
to be used in this recording. The errlogger command will be used to
record information to the Error Log.
2615-606 fclogerr Attention: A detail data item in the '-d' argument
list does not have a corresponding data type listed in the '-x'
argument list. The remaining detail data items will be treated as
ALPHA data.
2615-607 fclogerr Attention: A detail data item in the '-d' argument
list does not have a corresponding length listed in the '-y'
argument list. The remaining detail data items will be treated as
ALPHA data.
2615-608 fclogerr Attention: The data type indicator %1$s is not a
supported data type for this command. The supported data type
indicators are:
DEC
HEX
ALPHA
The detail data item for this data type will be recored as ALPHA
formatted information.
2615-609 fclogerr Attention: An unknown Log Event Type was provided
to this command:
%1$s
Valid Log Event Types are:
FFDC_EMERG
FFDC_ERROR
FFDC_STATE
FFDC_PERF
FFDC_TRACE
FFDC_RECOV
FFDC_DEBUG
The value FFDC_DEBUG was substituted for this value in the report
generated by this routine, giving this record the lowest severity
indication available.
2615-610 fclogerr Attention: The caller provided both a detail data
field using the '-d' option, and a detail data file using the '-f'
option. This command only accepts either a detail data field or
a detail data file. The detail data file will be ignored in the
record generated bythis routine, and the detail data field will
be used instead.
2615-611 fclogerr Attention: No System Log message was provided to
this command. No message was recorded in the System Log report
generated by this routine, but a record was made in the System Log.
2615-612 fclogerr Attention: This command could not record
information on this incident to the System Log.
2615-613 fclogerr Attention: This command was unable to copy the
contents of the following file:
%1$s
to this directory:
%2$s
Do not discard the original copy of this file.
2615-614 fclogerr Error: An unexpected failure occurred in the
routine %1$s. Error code value is %2$d.
Contact the IBM Customer Support Center for assistance in resolving
this failure.
2615-615 fclogerr Attention: Incomplete information was provided for
the source code file reporting this incident. Default information
was provided by this command on behalf of the user.
2615-616 fclogerr Attention: No resource name was provided to this
command, or the command user failed to provide the 'r' option to
this command. No resource name was recorded in the report
generated by this routine, but the record was made.
2615-617 fclogerr Attention: The command user provided a value for
detail data size that appears invalid. As a result, this routine
used the maximum length permitted for detail data. This may result
in some extraneous and unrelated information being recorded in the
record generated by this routine.
2615-618 fclogerr Attention: No details on the incident were provided
to this command. The detailed data section of the report made by
this routine has been omitted, but the report was recorded.
2615-619 fclogerr Attention: An unique FFDC Failure Identifier could
not be generated for the report filed by this command. fclogerr
created the incident report anyway.
fcdispfid: Usage Information:
fcdispfid [-q] | -h
Options:
-h Displays information command usage
-q Quiet mode - suppresses warning messages
fcdispfid is used by a script to display an FFDC Error Identifier
to the script's client, using a specific message for this purpose.
The client can examine the standard output of this command and
obtain the FFDC Error Identifier. This identifier is contained in
message number 2615-000, and is the sole item of information
presented in that message.
2615-651 fcdispfid Error: An option or an FFDC Error Identifier
argument is required.
2615-652 fcdispfid Error: Unknown option specified - '%1$c'.
2615-653 fcdispfid Error: An invalid FFDC Error Identifier was
provided to this command. No FFDC Error Identifier is displayed
to standard output.
2615-654 fcdispfid Error: An unexpected failure occurred in the
routine %1$s. Contact the IBM Customer Support Center for
assistance in resolving this failure.
fcstkrpt: Usage information:
fcstkrpt { [ -a ] [ -d | -p | -r ]
{
-f FFDC_Failure_Identifier [-i] |
-s FFDC_Error_Stack_file
}
} | -h
Options:
-a Display all information for each record selected for
display from the specified FFDC Error Stack. If this
option is not provided, the command displays a brief
summary for each record selected.
-d Display all records in the specified FFDC Error
Stack, in order from the oldest record to the newest.
This option cannot be used with the '-i', '-p', or
'-r' options.
-f Specifies an FFDC Failure Identifier contained within
the FFDC Error Stack to be examined. 'fcstkrpt' uses
this identifier to locate the proper FFDC Error Stack
to examine. Either the '-f', the '-s', or the '-h'
options must be specified.
-h Displays assistance information for this command. No
further processing is performed. Either the '-h',
the '-f', or the '-s' option must be specified.
-i Instructs the command to display the information
recorded for a specified FFDC Failure Identifier
only. If this option is not provided, information is
displayed for all records within the specified FFDC
Error Stack. This option can only be used if the
'-f' option is also specified.
-p Displays all records in the specified FFDC Error
Stack, ordering the information by parent and child
process relationship. Records from the FFDC Error
Stack are presented in an order that reflects the
parent and child relationship of all processes that
recorded information to this FFDC Error Stack. This
option cannot be used with the '-d', '-i', or '-r'
options.
-r Displays all records in the specified FFDC Error
Stack, ordering the information by related
incidents. Records that are associated with other
records in the FFDC Error Stack are displayed
together. This is the default selection for the
command. This option cannot be used with the '-d',
'-i', or '-p' options.
-s Specifies the name of a specific FFDC Error Stack
file to be examined. Either the '-s', '-f', or the
'-h' options must be specified.
'fcstkrpt' is used to examine the contents of an existing FFDC Error
Stack. The command offers two levels of detail while displaying
the contents of an FFDC Error Stack:
* A brief level of detail, showing the time when an
incident was logged, the name of the process that
logged the incident, and a brief description of
the incident that was logged
* A fully detailed report, including the FFDC Failure
Identifiers associated with an entry, FFDC Failure
Identifiers of related entries, fully expanded time
and recording process information, full description
of the incident, and diagnostic information recorded
for the incident.
'fcstkrpt' permits one of four possible views for this information:
* Display the contents of the FFDC Error Stack in the
order in which they were recorded, from the earliest
record to the latest record. This view is used when
the full contents of the file are desired.
* Display the contents of the FFDC Error Stack,
displaying related records together. This view is
useful when the FFDC Error Stack is being examined
to determine the root cause of a problem, or in
understanding how an incident may have caused other
incidents to occur. This view is the default.
* Display the contents of the FFDC Error Stack,
ordering the output by parent and child process
relationship. This view is useful when examining
the effects of a incident on the process and its
ancestor or decendent processes.
* Display information for a specific FFDC Failure
Identifier only. This view is useful when examining
a specific failure condition.
This command processes only one FFDC Error Stack at a time. To
examine multiple FFDC Error Stacks, a separate 'fcstkrpt' command
must be executed for each FFDC Error Stack to be examined. To
specify which FFDC Error Stack to examine, specify one of the
following items of information:
* The name of the file where the FFDC Error Stack is
stored. This may be an absolute or relative file
path name. If a relative path name is used, it is
assumed to be relative to the directory
%1$s
* An FFDC Failure Identifier that was stored to the
FFDC Error Stack. 'fcstkrpt' will extract the FFDC
Error Stack location information from this identifier.
'fcstkrpt' examines FFDC Error Stacks that reside only on the
local system. To examine FFDC Error Stacks on remote systems,
execute the 'fcstkrpt' command on the remote system.
FFDC Error Identifier:
%1$s
FFDC Error Identifier:
unknown
Associated FFDC Error Identifier:
%1$s
Remaining record contents appear to be corrupted. Unable to display
remaining record information.
Process Name: %1$s
Process Identifier: %1$d
Parent Process Identifier: %1$d
Process Thread Identifier: %1$d
Detecting File Information:
File Name: %1$s
File Version Code: %1$s
Licensed Programming Product: %1$s
Location Within the File: %1$d
Description:
Details:
Details:
%1$s
Stack Format Version One
Stack Format Version Unknown - possibly future version
Interpreting contents in Version One Compatibility Mode
Stack Control Information:
Records begin at file offset %1$d
Current write position file offset %2$d
The earliest record in the file is at offset %3$d
Stack file size is %4$d
Stack has wrapped at least once
------------------------------------------------------------
Recording Process Information:
Timestamp: %1$s Description:
%1$s
TIMESTAMP PROCESS DESCRIPTION
%1$.2d%2$.2d%3$.2d%4$.2d%5$.4d %6$-16.16s %7$s
2615-701 fcstkrpt Error: Memory allocation failure. Exiting.
2615-702 fcstkrpt Error: Unexpected failure detected in the
%1$s routine. Error code is %2$d.
Note the full text of this failure message, and contact the IBM
Customer Support Center to report the problem.
2615-703 fcstkrpt Error: At least one command option must be
specified.
2615-704 fcstkrpt Error: The '%1$c' option has been specified more
than once. This option can only be specified once, and accepts
only one argument. Processing of this command has ceased. Please
correct the usage of this command and reissue the command with the
proper options.
2615-705 fcstkrpt Error: Unknown option specified - '%1$c'.
Processing of this command has ceased. Please correct the usage of
this command and reissue the command with the proper options.
2615-706 fcstkrpt Error: Both the '%1$c' and '%2$c' options have
been specified to this command. These options cannot be used
together. Processing of this command has ceased. Please correct
the usage of this command to specify only one of these two
options, and reissue the command with the proper option.
2615-707 fcstkrpt Error: The '%1$c' option was specified to this
command, but the '%2$c' option was not specified. Both options
must be provided when using the '%1$c' option. Processing of this
command has ceased. Please correct the usage of this command to
provide both options, and reissue this command.
2615-708 fcstkrpt Error: The FFDC Error Identifier
'%1$s'
was created by a later version of the FFDC software. To examine
the information stored for this identifier, use an 'fcstkrpt'
command of the same or later version.
2615-709 fcstkrpt Error: The FFDC Error Identifier
'%1$s'
specifies an entry stored in the following node's Error Log:
Cluster Name: %2$s
Node Number: %3$d
2615-710 fcstkrpt Error: The FFDC Error Identifier
'%1$s'
does not reference an FFDC Error Stack entry. Please verify that
the data item above is indeed an FFDC Failure Identifier and has
been enterred correctly. Use the fcdecode command listed below,
to find where the failure incident may be recorded:
fcdecode %1$s
2615-711 fcstkrpt Error: The FFDC Error Identifier
'%1$s'
specifies an FFDC Error Stack in the following location:
Cluster Name: %2$s
Node Number: %3$d
2615-712 fcstkrpt Error: Unable to locate or open FFDC Error Stack file
%1$s.
2615-713 fcstkrpt Error: The command experienced an unexpected
failure in the %1$s routine. Failure code from this
routine was %2$d. Note the conditions present when this command
was executed, and contact the system administrator. System
administrators should contact the IBM Customer Support Center
to report this failure.
2615-714 fcstkrpt Error: The FFDC Error Identifier
'%1$s'
did not provide a valid name for an FFDC Error Stack. Please
verify that the FFDC Error Identifier was specified correctly.
Correct any error in the specification of the FFDC Error
Identifier, and attempt this command again.
2615-715 fcstkrpt Error: The FFDC Error Identifier
'%1$s'
references an FFDC Error Stack that does not exists on this node.
The FFDC Error Stack may have existed at one time, but the stack
may have been removed since the time that the FFDC Error Identifier
was created. fcstkrpt cannot provide any information on the
incident associated with this FFDC Error Identifier.
2615-716 fcstkrpt Error: This command requires that either the
'-%1$c' option or the '-%2$c' option be specified. Please correct
the usage of this command and execute the command again with the
proper options.
2615-717 fcstkrpt Error: The FFDC Error Identifier
'%1$s'
references an FFDC Error Stack that was created on a remote system.
fcstkrpt cannot provide any information on the incident associated
with this FFDC Error Identifier. Use the 'fcdecode' command to
determine where the FFDC Error Stack for this identifier was created.
2615-718 fcstkrpt Error: Unable to lock the FFDC Error Stack file
for exclusive use. The file may have been removed by another
application, or another application may have locked this file for
use and become hung. Unable to generate a report for this FFDC
Error Stack file at this time.
2615-719 fcstkrpt Error: The FFDC Error Stack file appears to be
corrupted. Ending the report of the FFDC Error Stack file
contents at this point.
2615-720 fcstkrpt Error: The FFDC Error Identifier
'%1$s'
references an FFDC Error Stack that cannot be accessed by this
user. The FFDC Error Stack file may have been created by another
system user, and the user running the fcstkrpt command does not
have sufficient system privileges to access files created by that
user. To obtain information for this FFDC Failure Identifier,
have a more privileged system user attempt this command. fcstkrpt
cannot provide any information on the incident associated with
this FFDC Error Identifier.
2615-721 fcstkrpt Error: The FFDC Error Stack file
'%1$s'
cannot be accessed by this user. The FFDC Error Stack file may
have been created by another system user, and the user running
the fcstkrpt command does not have sufficient system privileges
to access files created by that user. To obtain information for
this FFDC Failure Identifier, have a more privileged system user
attempt this command. fcstkrpt cannot provide any information on
the incident associated with this FFDC Error Identifier.
fcdecode: Usage information:
fcdecode identifier[,identifier,...] | -h
If more than one identifier is provided to this command, each
individual identifier must be separated by a comma with no
intervening white space between the identifiers and the comma.
fcdecode interprets one or more First Failure Data Capture (FFDC)
failure identifiers, and displays the information contained within
these identifiers. This information includes the Internet address
of the node where the identifier was generated, the time that the
identifier was generated, and where the incident report for this
identifier is recorded. With this information, users can track an
FFDC failure identifier to the system where it was generated to
obtain details about the incident that was reported with this
identifier.
Information for First Failure Data Capture identifier
%1$s
Generated by the local system
Generated on a remote system with the following Internet
address:
%1$s
Generated %1$s
Recorded to the Error Log using template %1$x
Recorded to an First Failure Data Capture Error Stack on
the remote node
Recorded to the First Failure Data Capture Error Stack
stored in the file
%1$s/%2$s
Attention: This identifier was generated by a newer version
of the First Failure Data Capture utilties. If the previously
listed node is part of this system's operational cluster, this
may indicate that nodes within this cluster are utilizing different
levels of the RSCT Cluster Utilities.
Attention: This identifier references an FFDC Error Stack
file that no longer exists on this system.
To obtain the Error Log information for this entry, issue
the following command on the local system:
%1$s errpt -a -j %2$x -s %3$.2d%4$.2d%5$.2d%6$.2d%7$.2d | more
Search this output for an Error Log entry that contains the
following ERROR ID code:
%8$s
To obtain the Error Log information for this entry, issue
the following command on the remote system:
%1$s errpt -a -j %2$x -s %3$.2d%4$.2d%5$.2d%6$.2d%7$.2d | more
Search this output for an Error Log entry that contains the
following ERROR ID code:
%7$s
Recorded to the local System Log (syslog) using:
syslog facility: %1$s
syslog priority: %2$s
Recorded to the System Log (syslog) on the remote node
using:
syslog facility %1$s syslog priority%2$s
Recorded to a First Failure Data Capture Error Stack,
stored in one of the following files
%1$s/%2$s
2615-751 fcdecode Error: Unknown option specified - '%1$c'.
2615-752 fcdecode Error: No options or First Failure Data Capture
failure identifiers were provided as arguments to this command.
2615-753 fcdecode Error: More than one list of First Failure Data
Capture failure identifiers was detected. This command accepts a
single list of FFDC failure identifiers only. The initial list of
FFDC failure identifiers detected was:
%1$s
The next list of failure identifiers detected was:
%2$s
The most common reason for this failure is that white space is
accidentally inserted by the command user between the FFDC failure
identifiers. When specifying more than one FFDC failure
identifier to fcdecode, these identifiers must be presented in
a single list, separated by commas with no white space between the
failure identifiers and the commas. Please correct the usage of
this command and issue the command again.
2615-754 fcdecode Error: The following identifier is not in the
the proper format for a First Failure Data Capture failure
Identifier:
%1$s
Verify that the identifier was entered correctly, and includes all
characters from the First Failure Data Capture failure identifier.
Issue this command once again with the correct identifier.
2615-755 fcdecode Error: The following First Failure Data Capture
failure identifier cannot be interpreted:
%1$s
This identifier was generated by an application using a later
version of the First Failure Data Capture utilties, which has
revised the format used within First Failure Data Capture failure
identifiers. This fcdecode command is part of an earlier version
of the First Failure Data Capture utilities, and cannot interpret
the revised format of the identifier. Contact the system
administrator to ensure that all systems within this operational
cluster are executing the same version of the RSCT Cluster
Utilities software.
2615-756 fcdecode Error: An unexpected failure occurred within the
routine:
%1$s
Failure code from this routine:
%2$d
This failure indicates a problem with the First Failure Data
software. IBM Customer Support should be informed of this failure,
and the IBM Customer Support Center should be contacted to resolve
this problem. Make a note of the command that was issued,
including all options and arguments, and save a copy of this
command's output. Contact the system administrator to report this
problem to the IBM Customer Support Center. System administrators
should consult the problem determination information for First
Failure Data Capture for assistance on reporting this failure.
2615-757 fcdecode Error: The following First Failure Data Capture
Failure Identifier is invalid:
%1$s
This identifier cannot be properly decoded. A portion of the
identifier may have been entered incorrectly, or the identifier
may have become corrupted. Verify that the identifier was
entered correctly.
fcpushstk: Usage information:
fcpushstk [-a associated_FFDC_Error_Identifier]
[-r resource_name] [-l product_name]
[-s detecting_file_name] [-v file_version]
[-p position_in_detecting_file] [-q]
[-d detail_data_string |
-f detail_data_file_name]
[-c message_catalog_file_name
-m message_set_number
-n description_message_number
[-o param[,param,...]]]
default_description_message
fcpushstk -h
Notes on these options:
* The '-q' option executes the command in 'quiet' mode,
which restricts the command from displaying warning
messages.
fcpushstk is used by a script to record information about failures
and noteworthy incidents to the FFDC Error Stack. An FFDC
Environment must have been previsously established by the script,
using the fcinitstk command. The information recorded to the FFDC
Error Stack should provide detailed information about the
incident that can be used by problem analysis efforts to identify
the incident, its cause, and the actions that should be taken in
response to this incident.
fcpushstk: Error detected. Because failures were detected, this
command did not attempt to record information to the FFDC Error
Stack.
2615-801 fcpushstk Error: Unknown option specified - '%1$c'.
2615-802 fcpushstk Error: The %1$s option has been specified more
than once. The option can only be specified once to this command.
Information will not be recorded to the FFED Error Stack.
2615-803 fcpushstk Attention: The caller provided both a detail data
field using the -d option, and a detail data file using the -f
option. This command only accepts either a detail data field or
a detail data file. The detail data file will be ignored in the
record generated by this routine, and the detail data field will
be used instead.
2615-804 fcpushstk Attention: Incomplete information was provided for
the source code file reporting this incident. Default information
was provided by this command on behalf of the user.
2615-805 fcpushstk Error: An FFDC Environment does not exist for
this process. This process cannot record failure information to the
FFDC Error Stack.
2615-806 fcpushstk Error: The FFDC Environment for this process
appears to be corrupted. The FFDC Environment is not usable.
This process cannot make recordings to the FFDC Error Stack.
2615-807 fcpushstk Error: The FFDC Error Stack directory
%1$s cannot be accessed. The directory may be missing, unmounted,
or permissions may have been changed on the directory. Contact the
system administrator and report this problem. This process cannot
make recordings to the FFDC Error Stack at this time.
2615-808 fcpushstk Error: The FFDC Error Stack file
%1$s cannot be accessed. The file may be missing, corrupted, or,
permissions may have been changed on the file to prohibit access.
Contact the system administrator and report this problem. This
process cannot make recordings to the FFDC Error Stack at this
time.
2615-809 fcpushstk Error: The name reserved for the FFDC Error Stack
file:
%1$s
is the name of an existing directory. Ask the system administrator
to ensure that system users are not creating subdirectories in the
directory:
%2$s
If this problem occurs in multiple applications, contact the system
administrator to have the problem reported to the IBM Customer
Support Center.
2615-810 fcpuststk Error: An unexpected failure occurred in the
routine %1$s.
This process cannot make recordings to the FFDC Error Stack at this
time. Contact the IBM Customer Support Center for assistance in
resolving this failure.
2615-811 fcpushstk Error: Insufficent space exists in the file
system containing the directory:
%1$s
to create an FFDC Error Stack file. This routine attempted to
reserve and FFDC Error Stack file of a minimum size of %2$d
bytes while leaving at least five percent of the file system
capacity available. The FFDC Error Stack file could not be reserved
under these constraints. This application cannot record information
to the FFDC Error Stack until more space becomes available in the
file system.
2615-812 fcpushstk Error: Unable to lock the file:
%1$s
for exclusive use. The file may have been removed by another
application, or another application may have locked this file for
use and become hung. This process is unable to record incident
information to the FFDC Error Stack at this time.
2615-813 fcpushstk Error: Unable to update the control information
within the FFDC Error Stack file:
%1$s
The file may be corrupted, or this problem can indicate an internal
error in the FFDC software. This process should consider
the FFDC Error Stack unusable. Verify that the file exists and can
be viewed using the fcstkrpt command. If fcstkrpt fails to indicate
an error with the FFDC Error Stack file, contact the system
administrator to have this problem reported to the IBM Customer
Service Center. Error code from the write() library call: %2$d.
2615-814 fcpushstk Attention: No resource name was provided to this
command through the '%1$c' option. No resource name was
recorded to the FFDC Error Stack report generated by this
routine, but the incident was recorded.
2615-815 fcpushstk Attention: This command was not provided with a
default message to use as a description for this incident in
cases where the cataloged message decription cannot be obtained.
If the FFDC Error Stack contents are viewed on a node where the
message does not exist, or if the FFDC Error Stack contents are
viewed when the message catalog is missing, no description
information will be presented for this entry. Users may not be
able to understand the nature of the incident without a
description, which limits the usefulness of the entry to the
system administrator.
2615-816 fcpushstk Attention: This command was not provided with
complete information to identify a cataloged message that
desribes the nature of the incident being recorded to the FFDC
Error Stack. As a result, this desription will be presented
using the default message text. Users viewing the FFDC Error
Stack contents in other locales will not be able to translate
this message into the language used for that locale, meaning
that the user may not be able to understand the information
recorded by this application.
2615-817 fcpushstk Attention: The caller provided both a detail data
field and a detail data file to this command. This command
only accepts either a detail data field or a detail data file.
The detail data file was ignored in the record generated by this
command, and the detail data field was used instead.
2615-818 fcpushstk Attention: The command was not able to generate
an unique FFDC Error Identifier for the report it filed. The
report has been made successfully.
2615-819 fcpushstk Attention: The command was unable to copy the
contents of the file:
%1$s
to the directory:
%2$s
Do not discard the original copy of this file. The name of the
original copy of has been recorded to the FFDC Error Stack, and
future problem determination efforts may require access to this
file.
2615-820 fcpustsk Attention: The information submitted for recording to the
FFDC Error Stack exceedes the record length of %1$d bytes. The
information has been truncated to fit the record size limit. Some
important diagnostic information may have been lost in the process.
Errors may occur when this information is displayed later with the
fcstkrpt command. This record size limit includes the detecting
file information, the message catalog information, the description
message, substitutional parameters to the description message, as
well as the details of the condition. In the future, record less
information, or make use of the detail data file option.
2615-821 fcpushstk Attention: No details about the incident were provided
to this command, either in the form of a detail data string or in
the form of a detail data file. The detailed data section of this
report was omitted, but the report was successfully recorded.
Records that do not contain details can be difficult to understand
or use effectively in problem analysis efforts. Ensure that the
command was used correctly, and that the '-d' or '-f' options were
not accidentally omitted.
fcreport: Usage Information:
fcreport -h | [-a] FFDC_Failure_Identifier
Options:
-a Generates a detailed report for each indicent
report found in the chain of related incidents
-h Displays usage information for this command
fcreport permits the command user to obtain information about an
incident and any other incidents associated with it. The command
obtains the incident information for a specified First Failure
Data Capture Failure Identifier. If this information indicates that
another incident is related to this one, fcreport searches for the
related report and displays that report as well. The command
continues to search for related incidents until no further related
incidents are referenced. This permits the command user to obtain
the full chain of events leading to a specific incident, to
understand how a particular incident occurred on the system.
fcreport Status: Cannot obtain any information for First Failure
Data Capture Failure Identifier %1$s
===========================================================================
fcreport Status: End of report for First Failure Data Capture
Failure Identifier %1$s
fcreport Status: The following First Failure Data Capture Failure
Identifier:
%1$s
was generated on a node using the following Internet address:
%2$s
This node cannot be contacted to obtain the information recorded
for the specified identifier. The node may not be active at this
moment, or the Internet address may no longer be valid.
fcreport Status: Information for %1$s
---------------------------------------------------------------------------
TIMESTAMP RESOURCE DESCRIPTION
%1$-15.15s %2$-16.16s %3$s
2615-851 fcreport Error: Unknown option specified - '%1$c'.
2615-852 fcreport Error: The following identifier is not in the
the proper format for a First Failure Data Capture failure
Identifier:
%1$s
Verify that the identifier was entered correctly, and includes all
characters from the First Failure Data Capture failure identifier.
Issue this command once again with the correct identifier.
2615-853 fcreport Error: The following First Failure Data Capture
failure identifier cannot be interpreted:
%1$s
This identifier was generated by an application using a later
version of the First Failure Data Capture utilties, which has
revised the format used within First Failure Data Capture failure
identifiers. This fcdecode command is part of an earlier version
of the First Failure Data Capture utilities, and cannot interpret
the revised format of the identifier. Contact the system
administrator to ensure that all systems within this operational
cluster are executing the same version of the RSCT Cluster
Utilities software.
2615-854 fcreport Error: The First Failure Data Capture failure
identifier:
%1$s
was recorded to an FFDC Error Stack file which no longer exists on
this system. This command is unable to generate a report for this
FFDC Failure Identifier. The FFDC Error Stack file was most likely
removed as part of normal system maintenance. In the future, try
to obtain information on FFDC Failure Identifiers in a more timely
fashion.
2615-855 fcreport Error: An unexpected failure occurred in the
routine %1$s
Unexpected return code: %2$d
This process cannot make recordings to the FFDC Error Stack at this
time. Contact the IBM Customer Support Center for assistance in
resolving this failure.
2615-856 fcreport Status: The following First Failure Data Capture
Failure Identifier:
%1$s
was generated on a node using the following Internet address:
%2$s
This node cannot be contacted to obtain the information recorded
for the specified identifier. The node may not be active at this
moment, or the Internet address may no longer be valid. Another
possible reason for this condition is that the First Failure Data
Capture Failure Identifier may not have been stated correctly to
this command. A typographical error in specifying this value may
cause the 'fcreport' command to incorrectly interpret the identifier,
causing it to yield an erroneous Internet address. Verify that
the First Failure Data Capture Failure Identifier was specified
correctly.
2615-857 fcreport Error: Failure in allocating memory. This command
cannot obtain further information on incidents related to the
First Failure Data Capture Failure Identifier:
%1$s
If this command is being invoked from a script, check the script
source code for possible memory leaks. Also check the system for
processes hoarding memory, and report this problem to the system
administrator.
fccheck: Usage Information:
fccheck [-q] [-h]
Description of options:
-h Displays help information for this command
-q Disables diagnostic output messages from
this command - the command sets an exit
status code to indicate the results of the
test
fccheck performs basic checks on the First Failure Data Capture
(FFDC) utilities. These checks include tests on the directories
used by the FFDC utilities to store FFDC Error Stacks and dump
files to see if conditions exist that might prevent the creation
of Error Stacks or dump files by FFDC. When the '-q' option is
not specified, 'fccheck' indicates the results of its test to the
standard output device, and sets an exit status code to reflect
the most severe condition it detected if any such conditions were
detected. When the '-q' option is used, 'fccheck' does not display
diagnostic output, but does set an exit status code to reflect the
most severe condition it detected. Please notice that 'fccheck'
only tests the local system's environment for conditions that might
interfere with the operation of the FFDC utilities. This command
does not run diagnostic procedures on the FFDC utilities
themselves. If 'fccheck' does not indicate any problems with the
local system's operational environment but the FFDC utilities
fail, consult the FFDC problem determination documentation for
assistance on performing further problem determination for the FFDC
utilities.
fccheck Status: Creation and use of FFDC Error Stacks has been
expressly disabled in the current execution environment. Any
processes created in the current execution environment cannot
create their own FFDC Error Stacks, or inherit use of existing
FFDC Error Stacks.
fccheck Status: The directory where the the FFDC utilities would
store FFDC Error Stack data on this system cannot be accessed:
%1$s
The permissions on one or more directories in this directory
path name may have been changed to prohibit normal users from
accessing the contents of these directories. Report this
problem to the system administrator for resolution. System
Administrators should ensure that the directory permissions in
this path name are set as follows:
/var owner: bin group: bin permissions: 0755
/var/adm owner: bin group: bin permissions: 0755
/var/adm/ffdc owner: root group: system permissions: 0777
/var/adm/ffdc/stacks owner: root group: system permissions: 1777
fccheck Status: One or more directories in this following path
name do not exit on the local system:
%1$s
The file system that contains this directory may have been
unmounted, or one of the directories may have been removed.
Contact the system administrator to report this problem.
System administrators should ensure that the file
systems containing these directories have been mounted, and that
all directories in this path name exist with the following
permissions:
/var owner: bin group: bin permissions: 0755
/var/adm owner: bin group: bin permissions: 0755
/var/adm/ffdc owner: root group: system permissions: 0777
/var/adm/ffdc/stacks owner: root group: system permissions: 1777
fccheck Status: There is not enough space available in the file
system containing the following directory:
%1$s
to create FFDC Error Stacks. The FFDC utilities attempt to create
FFDC Error Stacks in this directory while ensuring that at least
5 percent of the file system space remains available after the
Error Stack file has been created. Not enough space exists in
the file system containing this directory to permit the FFDC
utilities to create an FFDC Error Stack of %2$d bytes and still
retain the 5 percent available space margin. Notify the system
administrator of this problem. System administrators should use
the 'fcclear' command to remove old or unneeded FFDC Error Stacks
and dump files, and should also examine this file system for any
old or large files that can be safely removed.
fccheck Status: The directory where the FFDC utilities would store
dump files on the local system:
%1$s
cannot be accessed. The permissions on one or more directories in
this directory path name may have been changed to prohibit normal
users from accessing the contents of these directories. Report
this problem to the system administrator for resolution. System
Administrators should ensure that the directory permissions in
this path name are set as follows:
/var owner: bin group: bin permissions: 0755
/var/adm owner: bin group: bin permissions: 0755
/var/adm/ffdc owner: root group: system permissions: 0777
/var/adm/ffdc/dumps owner: root group: system permissions: 1777
fccheck Status: One or more directories in this following path
name:
%1$s
does not exist on the local system. The file system containing
this directory path name may have been unmounted, or one of the
directories may have been removed from the system. Contact the
system administrator to report this problem. System
administrators should ensure that the file systems containing
these directories have been mounted, and that all directories
in this path name exist with the following permissions:
/var owner: bin group: bin permissions: 0755
/var/adm owner: bin group: bin permissions: 0755
/var/adm/ffdc owner: root group: system permissions: 0777
/var/adm/ffdc/dumps owner: root group: system permissions: 1777
fccheck Status: There is not enough space available in the file
system containing the following directory:
%1$s
to create detail data files. The FFDC utilities attempt to create
dump files in this directory while ensuring that at least
5 percent of the file system space remains available after the
dump file has been created. Not enough space exists in
the file system containing this directory to permit the FFDC
utilities to create a dump file and still retain the 5 percent
available space margin. Notify the system administrator of this
problem. System administrators should use the 'fcclear' command
to remove old or unneeded FFDC Error Stacks and dump files, and
should also examine this file system for any old or large files
that can be safely removed.
fccheck Status: All checks completed. Examine the previous status
output for possible FFDC problem conditions, and take the recommened
actions listed in these messages.
fccheck Status: All tests completed.
2615-901 fccheck Error: Unknown command option '%1$c'
2615-902 fccheck Error: An unexpected internal failure was detected
within the 'fccheck' command while it was executing its tests.
This failure must be reported to the IBM Customer Support Center
for resolution. Please make a note of the conditions present on
the local system at the time this failure occurred, make a
permanent record of the output generated by this command, and
contact the system administrator to have the problem reported to
the IBM Customer Support Center. System administrator should
consult the FFDC problem determination documentation for assistance
on reporting this problem to the IBM Customer Support Center.
Name of internal routine: %1$s
Return code from internal routine: %2$d
2615-903 fccheck Error: This command is not able to query the
operating system for information about the file system containing
the following directory:
%1$s
This information should be available for a local file system
sthrough the operating system. If this directory resides on a
local file system, this may indicate a problem with the operating
system. Contact the system administrator and report this problem.
fcclear: Usage Information:
fcclear -h |
{
[-d detail_data_file[,detail_data_file,...]
[-D detail_data_file[,detail_data_file,...]
[-f FFDC_Failure_Identifier[,FFDC_Failure_Identifier,...]
[-F FFDC_Failure_Identifier[,FFDC_Failure_Identifier,...]
[-s FFDC_Error_Stack_file[,FFDC_Error_Stack_file,...]
[-S FFDC_Error_Stack_file[,FFDC_Error_Stack_file,...]
}
Options:
-d Specifies the name of one or more detail
data files to be removed. The file names
may be absolute or relative path name.
If more than one file name is provided,
each file name must be separated by a comma
(,) with no intervening white space.
-D Specifies the name of one or more detail
data files to be retained. The file names
may be absolute or relative path name.
If more than one file name is provided,
each file name must be separated by a comma
(,) with no intervening white space.
-f Specifies one or more FFDC Failure
Identifiers. The files storing these
identifiers are removed, if they reside on
the local system. If more than one
identifier is provided, each identifier
must be separated by a comma (,) with no
intervening white space.
-F Specifies one or more FFDC Failure
Identifiers. The files storing these
identifiers are retained. If more than one
identifier is provided, each identifier
must be separated by a comma (,) with no
intervening white space.
-s Specifies the name of one or more FFDC Error
Stack files to be removed. The file names
may be absolute or relative path name.
If more than one file name is provided,
each file name must be separated by a comma
(,) with no intervening white space.
-S Specifies the name of one or more FFDC Error
Stack files to be retained. The file names
may be absolute or relative path name.
If more than one file name is provided,
each file name must be separated by a comma
(,) with no intervening white space.
-t Indicates that any FFDC Error Stack files
and detail data files not meeting any other
selection criteria that are older than the
specified number of days should be removed.
fcclear is used to remove FFDC Error Stack files and detail data
files from the local system. The command permits the command user
to specify a selection criteria for the file that are to be
removed:
- Detail data files of a specific name (the -d option)
- Detail data files except for a specific set (the -D
option)
- FFDC Error Stack files containing information for
a set of FFDC Failure Identifiers (the -f option)
- FFDC Error Stack files except those containing
information for a set of FFDC Failure Identifiers
(the -F option)
- FFDC Error Stacks of a specific name (the -s option)
- FFDC Error Stacks except for a specific set (the -S
option)
The 'root' user may remove any FFDC Error Stack or detail data files
on the local system. Other users can only remove FFDC Error Stack
and detail data files that they created.
2615-951 fcclear Error: At least one option is required to execute
this command.
2615-952 fcclear Error: Unknown command option '%1$c'
2615-953 fcclear Error: The '%1$c' option has been specified more
than once.
2615-954 fcclear Error: A numeric value is required as an argument
to the '-%1$c' option.
2615-955 fcclear Error: The options provided to this command have
specified that the same file should be retained and removed from
the system. To avoid taking the wrong action, 'fcclear' will
terminate without removing any files from the local system. The
most common source of this failure is that the command user
provided an FFDC Failure Identifier that is stored in an FFDC
Error Stack file that was specified by another FFDC Failure
Identifier, or referenced by name to another command option. Test
all FFDC Failure Identifiers with the 'fcdecode' command. Ensure
that none of the FFDC Failure Identifiers to be removed are stored
in FFDC Error Stack files that are to be retained, and vice versa.
Also ensure that all of the file names or FFDC Failure Identifiers
provided as command arguments are entered correctly.
2615-956 fcclear Error: An unexpected internal failure was detected
within the 'fcclear' command. This failure must be reported to
the IBM Customer Support Center for resolution. Please make a
note of the conditions present on the local system at the time
this failure occurred, make a permanent record of the output
generated by this command, and contact the system administrator
to have the problem reported to the IBM Customer Support Center.
System administrator should consult the FFDC problem determination
documentation for assistance on reporting this problem to the IBM
Customer Support Center.
Name of internal routine: %1$s
Return code from internal routine: %2$d
2615-957 fcclear Error: The following directory has been detected to
be in error:
%1$s
The directory either does not have the correct access permissions,
been removed, or references a file instead of a directory. This
command is unable to remove any files from this directory. Contact
the system administrator to report this problem. System
administrators should verify that the file system containing this
directory is mounted and that the directory does exist. If the
directory does exist, ensure that the permissions on the directory
are set to permission code 1777, and any further security on this
directory permits access to the directory for normal users.
Normal users should have sufficient permissions granted to allow
them to remove First Failure Data Capture Error Stacks and detail
data files that they have created in this directory.
2615-958 fcclear Error: The file name is not valid.