Error

 

Code

Error Message and Description

 

 

-16

DATASET_ERROR_DATASET_NOT_CLOSED

 

An attempt was made to open the dataset without

 

closing it first.

-17

DATASET_ERROR_BUFLEN_SHORT

 

The buffer length specified by datasetGet is shorter

 

than the actual record length.

 

 

-18*

DATASET_ERROR_VOLUME_LABEL_INVALID

 

No standard volume label was found, or the contents

 

of the VTOC are illegal.

 

 

-19*

DATASET_ERROR_VTOC_INVALID

 

No VTOC found, or contents of VTOC are invalid.

 

 

-20*

DATASET_ERROR_VOLUME_NOT_DEFINED

 

The specified volume is not defined.

 

 

-21

DATASET_ERROR_INVALID_ARGUMENT

 

An argument of the function is invalid.

 

 

-22

DATASET_ERROR_NO_DATASET

 

No dataset was found.

 

 

-23*

DATASET_ERROR_NON_STANDARD_R0_EXIST

 

Nonstandard record 0 (R0) exists.

 

 

-24

DATASET_ERROR_INVALID_MODE

 

The mode argument of datasetOpen is not valid.

 

 

-25*

DATASET_ERROR_VOLUME_DEFINED_READ_ONLY

 

The open-system host tried to write to a read-only

 

volume.

 

 

-26

FAL_INTERNAL_ERROR

 

Internal error of FAL

 

 

-27*

DATASET_ERROR_END_OF_VOLUME

 

The end of volume was detected before the end of

 

dataset was detected.

 

 

-28

DATASET_ERROR_OVERFLOW

 

Data cannot be written because the dataset is full.

Recommended Action(s)

Make sure the requirements and restrictions specified in Chapter 6 are met. For example:

Dataset open and close must be used as a pair.

More than one dataset cannot be open within one process.

datasetOpen, datasetGetFileInformation, and datasetFindFirstFile cannot be used while the dataset is being accessed by datasetGetFileInformation or datasetFindFirstFile.

datasetGetFileInformation and datasetFindFirstFile cannot be used while the dataset is being accessed datasetOpen.

Make sure that the buffer area is larger than the dataset record length.

Make sure that volume initialization is complete and correct on the z/OS host. This error occurs when a system that does not support large files accesses a formatted volume from a system that supports large files. This error also occurs when a data partition size is incorrect for Solaris.

Make sure that the VTOC was created correctly on the z/OS host.

Make sure that the specified volume has been entered correctly in the FX volume definition file.

Make sure that the argument for the FAL function is correct.

Make sure that the dataset has been created correctly on the z/OS host.

Change the R0 track format to standard track format. FAL cannot write on tracks with nonstandard R0.

Make sure that the value of the mode argument for the datasetOpen function is either r (for read) or w (for write).

Make sure that the target dataset for an open- system write operation is on a 3390-3A/C volume.

Collect error logs file and error dump file. And make contact a maintenance staff. This error occurs when the open system does not have enough memory.

The open-system volume/partition size is smaller than the z/OS volume size. Make sure that the partition size is specified correctly on the open system. This error occurs when the open system disk is full or it exceeds a limitation for FXmto.

Check the size of the data to be written, and extend the size of the dataset as needed.

7-4

Troubleshooting

Hitachi USP V Cross-OS File Exchange User’s Guide

Page 192
Image 192
Hitachi MK-96RD647-01 manual Than the actual record length, Vtoc are illegal, Specified volume is not defined