Dataset maintenance Utility (z/OS only)

Self-explanatory message.

This message is associated with the UDS utility. It indicates that an operation was directed to a specific direct access volume for a specific dataset and the dataset was not found on that volume.

UDS remains conversational and processing continues.

The appearance of this message indicates that either an entry was misspelled or the dataset was not found where it should have been found. Attempt to locate the dataset using a catalog search. If this fails, consult the individual responsible for the dataset and arrange to have the dataset restored.

This message indicates that a volume search operation was requested for a specific dataset and the dataset was not found on any currently mounted direct access volume.

UDS remains conversational and processing continues.

The appearance of this message indicates that either an entry was misspelled, the dataset was not found where it should have been found, or the volume containing the dataset was not mounted. Attempt to locate the dataset using a catalog search. If this fails, consult the individual responsible for the dataset and arrange to have the dataset restored or the correct volume mounted.

This message indicates that a request was entered for a specific direct access volume and the volume was not mounted.

UDS remains conversational and processing continues.

The appearance of this message indicates that either an entry was misspelled or the volume was not mounted. Arrange to have the correct volume mounted.

This message indicates that a request was entered for a specific direct access volume and the VolSer was entered incorrectly.

UDS remains conversational and processing continues.

Reenter the request and specify the correct volume name. Volume names are a maximum of six characters long.

This message indicates that a request was entered for more than one specific direct access volume. The number of volumes entered was larger then could be accommodated by the UDS request.

UDS remains conversational and processing continues.

Reenter the request and specify the correct number of volumes.

This message indicates that a request was entered to access a password protected dataset and an invalid password was given, or the desired dataset was in use by another job or user, or that is a VSAM dataspace.

UDS remains conversational and processing continues.

Reenter the request and specify the correct password.

A request was entered that required a volume entry and no volume entry was given.

UDS remains conversational and processing continues.

Reenter the request and specify the correct volume(s).

A request was entered for more than one specific direct access volume and the number of volumes entered was larger than could be accomodated by UDS. The maximum number of volumes that may be accomodated by UDS with one functional request is 20.

UDS remains conversational and processing continues.

Reenter the request and specify the correct number of volumes. If more than 20 volumes are required, renter the request specifying the additional volume(s).

A SCRATCH request was made against a dataset whose retention date has not expired.

UDS remains conversational and processing continues.

Reenter the request using the PURGE function instead of SCRATCH.

A CATLG, RECATLG, or CONNECT request was made and an invalid device type argument was specified, or the devicetype specified is ambiguous.

UDS remains conversational and processing continues.

Reenter the request specifying the correct device type argument.

A UDS function was requested and an invalid argument was specified.

UDS remains conversational and processing continues.

Reenter the request specifying the correct argument.

A (currently) unsupported UDS function was requested.

UDS remains conversational and processing continues.

Refer to the Com-plete Utilities Manual for the currently supported UDS functions.

A UDS function was requested, a required field or argument was omitted.

UDS remains conversational and processing continues.

Reenter the request and specify the correct argument(s). Refer to the Com-plete Utilities Manual for the currently supported UDS functions and their arguments.

A field or argument required for a UDS function was entered incorrectly.

UDS remains conversational and processing continues.

Reenter the request and specify the correct argument(s). Refer to the Com-plete Utilities Manual for the currently supported UDS functions and their arguments.

Self-explanatory message.

The datset name given to the ALLOC function already exists on the indicated volume.

UDS remains conversational and processing continues.

Reenter the request and specify the correct dataset name.

Additional information can be obtained regarding the requested function by entering a question mark (?).

UDS remains conversational and processing continues.

Reenter the request or enter the question mark (?) for help.

A UDS function was requested that required a specific direct access volume, which was not currently mounted.

UDS remains conversational and processing continues.

Contact the computer operator and arrange to have the correct volume mounted, then reenter the request.

A SCRATCH request was entered an unusual error condition occurred. The dataset to be scratched was NOT scratched.

UDS remains conversational and processing continues.

This error condition indicates that the dataset to be scratched is currently inaccessible. One reason for this may be the dataset being enqueued to another user or job. In this case reenter the request when the enqueue has been released. If this is not case, the VTOC contents for the volume in question may be in error. Contact the System Programmer to determine the cause of the error.

If the dataset is not enqueued to another user or job, the VTOC entry for the dataset may be in error. Obtain a listing of the VTOC and determine the cause of the error. If the error persists, a direct access hardware problem my exist, either with the volume itself or with the disk unit.

A DISP request was entered and an unusual error condition occurred.

UDS remains conversational and processing continues.

This error condition indicates that the VTOC contents for the volume in question may be in error.Contact the System Programmer to determine the cause of the error.

The VTOC entry for the dataset may be in error. Obtain a listing of the VTOC and determine the cause of the error. If the error persists, a direct access hardware problem may exist, either with the volume itself or with the disk unit.

A DLTA (delete alias) request was entered and the aloas name to be deleted does not exist.

UDS remains conversational and processing continues.

This error may be caused because the alias name was mistyped. Correct the entry and reenter the request.

A BLDA (build alias) request was entered and the alias name to be created already exists.

UDS remains conversational and processing continues.

The alias name requested may have been incorrectly typed. Correct the entry and reenter the request.

A CATLG (catalog) request was entered and the index name required has not been created

UDS remains conversational and processing continues.

Build or created the appropriate index entry and reenter the request.

An invalid index structure was specified while creating an index or alias.

UDS remains conversational and processing continues.

Determine the appropriate index entry format and reenter the request.

A BLDX (build index) or DLTX (delete index) request was entered and an unusual error condition occurred.

UDS remains conversational and processing continues.

The catalog structure may be in error. Contact the System Programmer to determine the cause of the error.

Obtain a listing of the catalog and determine the cause of the error. If the error persists, a direct access hardware problem my exist, either with the volume itself or with the disk unit.

A BLDX (build index) or DLTX (delete index) request was entered and a higher level index structure could not be found.

UDS remains conversational and processing continues.

The catalog structure may be in error. Contact the System Programmer to determine the cause of the error.

Obtain a listing of the catalog and determine the cause of the error. Create the required higher level indexes and establish the correct index connections between volumes.

A DLTA (delete alias) or DLTX (delete index) request was entered for an index structure and one or more datasets are still cataloged using the index structure.

UDS remains conversational and processing continues.

Uncatalog the dataset(s) that are cataloged with the index structure and reenter the DLTA or DLTX request.

A request was entered to locate a dataset via the catalog and the dataset was not cataloged.

UDS remains conversational and processing continues.

This error may be caused by an incorrectly entered dataset name. Correct the dataset name and reenter the request.

A request was entered for a dataset and the dataset name was entered incorrectly.

UDS remains conversational and processing continues.

Correct the format of the dataset name and reenter the request.

A DISP request was entered and an unusual error condition occurred.

UDS remains conversational and processing continues.

The VTOC contents for the indicated volume may be in error. Contact the System Programmer to determine the cause of the error.

The VTOC entry for the dataset may be in error. Obtain a listing of the VTOC and determine the cause of the error. If the error persists, a hardware problem may exist, either with the volume itself or with the disk unit.

A Disp request was entered and an unusual error condition occurred.

UDS remains conversational and processing continues.

The catalog for the indicated volume may be in error. Contact the System Programmer to determine the cause of the error.

The catalog for the dataset may be in error. Obtain a listing of the catalog and determine the cause of the error. If the error persists, a hardware problem may exist, either with the volume itself or with the disk unit.

A catalog request was entered and the catalog could not be accessed.

UDS remains conversational and processing continues.

Retry the request. If the error persists, contact the System Programmer to determine the cause of the error.

Determine why the catalog cannot be accessed and correct the error.

A catalog request was entered and the index name required was not found.

UDS remains conversational and processing continues.

Build or create the appropriate index entry and reenter the request.

a BLDG (build generation) request was enter for a dataset and the dataset name was entered incorrectly.

UDS remains conversational and processing continues.

Correct the format of the dataset name and reenter the request.

A CATLG (catalog) request was entered and the datase name was already cataloged.

UDS remains conversational and processing continues.

Correct the dataset name and reenter the request.

A site user exit, UDSEX1, can be used to check authorization to use UDS functions. An unexpected error occurred while trying to load UDSEX1.

UDS is abnormally terminated and an online dump is taken.

Contact the System Programmer to determine the cause of the error.

The UDS security user exit routine, UDSEX1, is loaded into the thread region of UDS when this utility is initially invoked. Examine the online dump to determine the cause of the error.

SVC 32, the allocation SVC, was issued by UDS and returned an error.

UDS remains conversational and processing continues.

Retry the operation; If the error persists, contact the System Programmer to determine the cause of the error.

This message may be caused by a hardware problem. Retry the operation. If the error persists, contact the hardware maintenance personnel.

A request was entered to allocate a dataset and an invalid DSORG value was specified.

UDS remains conversational and processing continues.

Correct the format of the DSORG argument and reenter the request.

A request was entered to allocate a dataset and an invalid RECFM value was specified.

UDS remains conversational and processing continues.

Coorect the format of the RECFM argument and reenter the request.

A request was entered to allocate a dataset and an invalid fifth argument was specified for the space definition.

UDS remains conversational and processing continues.

Correct the format of the argument andreenter the request.

A request was entered and a non-numeric value was entered for a numeric argument.

UDS remains conversational and processing continues.

Coorect the format of the argument and reenter the request.

A BLDX (Build index) or DLTX (delete index) reuqest was entered and a higher level index structure could not be found.

UDS remains conversational and processing continues.

Retry the request. If the error persists, this may indicate the catalog structure is in error. Contact the System Programmer to determine the cause of the error.

Obtain a listing of the catalogand determine the cause of the error. Create the required higher level indexes and establish the correct index connections between volumes.

A request was entered to allocate a dataset and the values entered for the primary allocation and the number of directory entries are conflicting.

UDS remains conversational and processing continues.

Correct the arguments and reenter the request.

A request was entered to allocate a dataset and the value specified for the primary allocation was zero - a non-zero value is expected.

UDS remains conversational and processing continues.

Correct the arguments and reenter the request.

A request was entered to allocate a dataset and no space remains in the Volume Table of Contents (VTOC) to contain the requested entry.

UDS remains conversational and processing continues.

Contact the System Programmer to remove dataset(s) from the volume.

Scratch one or more datasets from the indicated volume.

A request was entered to allocate a dataset and there is not enough space available on the direct access volume to contain the dataset being requested.

UDS remains conversational and processing continues.

Contact the System Programmer for assistance.

Scratch one or more datasets from the indicated volume.

A request was entered to allocate a dataset and an invalid record length argument was specified.

UDS remains conversational and processing continues.

Correct the record length argument and reenter the request.

A CVOL request was entered and the indicated control volume did not contain a catalog.

UDS remains conversational and processing continues.

This may indicate that the volume requested is in error. If not, contact the System Programmer for assistance.

Obtain a VTOC listing of the volume, determine the cause of the error. Create the required entries (or catalog).

A request was entered to allocate a dataset and an invalid sixth argument was specified for the space allocation request.

UDS remains conversational and processing continues.

Specify 'ROUND' as the sixth argument or omit it at all.

A request was entered and 'LIST' was specified as an argument. LIST may be specified as an operation, but not as an argument.

UDS remains conversational and processing continues.

Reenter the request, omitting 'LIST' from the arguments.

The UDS security user exit routine, UDSEX1, is not linked in with the utility or is not available on COMPLIB.

UDS will terminate.

Contact your System Programmer for assistance.

Either link UDSEX1 with UDS, or make it available in COMPLIB.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

An LSPACE macro was unsuccessfully issued to get the free space information for a disk.

The UDS function is terminated

Inform SAG support about the returncode and the z/OS version.

Self-explanatory message.

The CSI interface gave a returncode (R15) > 0. UDS is terminated.

If the problem is reproducible inform Software Ag Support.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.