HP XP P9500 Storage - Manual (Page 150)

Recommended Action Error Condition
If you specified your own code conversion table, make sure that the file name
and path are correct. FCU may also report code conversion table errors when
the Data Exchange volume definition file contains both mainframe and OPEN-x
Data Exchange volumes. Keep the FXoto volume definition file separate from
the FXmto/otm volume definition file.
FCU reports code conversion
table errors.
Error Codes and Messages
The error information returned by the datasetGetLastError function includes the FAL error
information defined in the dataset.h file.
Table 65 on page 150 lists and describes the FAL error
codes and provides instructions for resolving each error condition. In Table 65 on page 150, the error
codes marked by an asterisk (*) may also be reported when I/O access contention occurs. If the
cause of the error cannot be identified as described in
Table 65 on page 150, check for illegal I/O
access contention for the Data Exchange volume between the mainframe and open-system hosts.
The FAL error logs for UNIX are /tmp/fal_error and /tmp/fal_error.bak, and /tmp/
fal_dump
and /tmp/fal_dump.bak. The FAL logs for Windows systems are c:\fal_error
and c:\fal_error.bak, and c:\fal_dump and c:\fal_dump.bak.
NOTE:
Error codes with a negative value are FAL errors. Error codes with a positive value are system errors.
UNIX system error codes are defined in the standard error file errno.h.
Table 65 FAL Error Codes
Recommended Actions Error Message and Description Error Code
Make sure that the VSN in the Data Ex-
change volume definition file is correct.
DATASET_ERROR_INVALID_VOLUME
The actual VSN and the VSN specified in the Data Exchange
volume definition file do not match. -7*
Make sure that the actual dataset name and
the specified dataset name are the same.
You can use the MF-File list command in
the FCU Help menu or the VTOC dump data
on the mainframe host to check the dataset
name.
DATASET_ERROR_DATASET_NOT_FOUND
The target dataset was not found.
-8
Make sure that the dataset was created
correctly on the mainframe host.
DATASET_ERROR_NOT_SUPPORTED
The data format is not supported.
-9
Make sure that the device emulation type
(LVI) is correct in the Data Exchange volume
definition file. The supported LVIs are 3390-
3A, -3B, and -3C.
DATASET_ERROR_DEVICE_TYPE_NOT_SUPPORTED
The device emulation type is not supported.
-10*
Check the DO type using the MF-File list
command in the FCU Help menu or the
VTOC dump data on the mainframe host. DATASET_ERROR_DSORG_NOT_SUPPORTED
The dataset organization type is not supported.
-11
Troubleshooting 150