Dataset maintenance Utility (z/OS only)

Overview of Messages

UDS0000 | UDS0001 | UDS0002 | UDS0003 | UDS0004 | UDS0005 | UDS0006 | UDS0007 | UDS0008 | UDS0009 | UDS0010 | UDS0011 | UDS0012 | UDS0013 | UDS0014 | UDS0015 | UDS0016 | UDS0017 | UDS0018 | UDS0019 | UDS0020 | UDS0021 | UDS0022 | UDS0023 | UDS0024 | UDS0025 | UDS0026 | UDS0027 | UDS0028 | UDS0029 | UDS0030 | UDS0031 | UDS0032 | UDS0033 | UDS0034 | UDS0035 | UDS0036 | UDS0037 | UDS0038 | UDS0039 | UDS0040 | UDS0041 | UDS0042 | UDS0043 | UDS0044 | UDS0045 | UDS0046 | UDS0047 | UDS0048 | UDS0049 | UDS0050 | UDS0051 | UDS0052 | UDS0053 | UDS0054 | UDS0055 | UDS0060 | UDS0100 | UDS0101 | UDS0102 | UDS0103 | UDS0104 | UDS0105 | UDS0106 | UDS0107 | UDS0108 | UDS0109 | UDS0110 | UDS0111

UDS0000	---> return code was $1
Explanation:	Self-explanatory message.

UDS0001	DSN not found on indicated Volume
Explanation:	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.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	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.

UDS0002	Not found online.
Explanation:	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.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	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.

UDS0003	Volume(s) not online.
Explanation:	This message indicates that a request was entered for a specific direct access volume and the volume was not mounted.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	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.

UDS0004	VOLUME must be less than seven characters.
Explanation:	This message indicates that a request was entered for a specific direct access volume and the VolSer was entered incorrectly.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Reenter the request and specify the correct volume name. Volume names are a maximum of six characters long.

UDS0005	Too many Volumes entered.
Explanation:	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.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Reenter the request and specify the correct number of volumes.

UDS0006	Invalid password, dataset in use, or in a VSAM dataspace
Explanation:	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.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Reenter the request and specify the correct password.

UDS0007	No volumes entered.
Explanation:	A request was entered that required a volume entry and no volume entry was given.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Reenter the request and specify the correct volume(s).

UDS0008	20 volume maximum exceeded.
Explanation:	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.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	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).

UDS0009	Retention date has not expired
Explanation:	A SCRATCH request was made against a dataset whose retention date has not expired.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Reenter the request using the PURGE function instead of SCRATCH.

UDS0010	Devicetype specified is invalid or ambiguous
Explanation:	A CATLG, RECATLG, or CONNECT request was made and an invalid device type argument was specified, or the devicetype specified is ambiguous.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Reenter the request specifying the correct device type argument.

UDS0011	Invalid or unauthorized operand field
Explanation:	A UDS function was requested and an invalid argument was specified.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Reenter the request specifying the correct argument.

UDS0012	(Yet) unsupported function requested
Explanation:	A (currently) unsupported UDS function was requested.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Refer to the Com-plete Utilities Manual for the currently supported UDS functions.

UDS0013	field missing
Explanation:	A UDS function was requested, a required field or argument was omitted.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	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.

UDS0014	field too long
Explanation:	A field or argument required for a UDS function was entered incorrectly.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	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.

UDS0015	NewDSN
Explanation:	Self-explanatory message.

UDS0016	Dataset name already exists
Explanation:	The datset name given to the ALLOC function already exists on the indicated volume.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Reenter the request and specify the correct dataset name.

UDS0017	Enter '?' for HELP
Explanation:	Additional information can be obtained regarding the requested function by entering a question mark (?).
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Reenter the request or enter the question mark (?) for help.

UDS0018	Required volume not online
Explanation:	A UDS function was requested that required a specific direct access volume, which was not currently mounted.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Contact the computer operator and arrange to have the correct volume mounted, then reenter the request.

UDS0019	Bad return code from scratch / rename
Explanation:	A SCRATCH request was entered an unusual error condition occurred. The dataset to be scratched was NOT scratched.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	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.
System programmer info:	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.

UDS0020	Bad return code from OBTAIN
Explanation:	A DISP request was entered and an unusual error condition occurred.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	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.
System programmer info:	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.

UDS0021	Alias does not exist
Explanation:	A DLTA (delete alias) request was entered and the aloas name to be deleted does not exist.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	This error may be caused because the alias name was mistyped. Correct the entry and reenter the request.

UDS0022	Alias has datasets cataloged
Explanation:	A BLDA (build alias) request was entered and the alias name to be created already exists.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	The alias name requested may have been incorrectly typed. Correct the entry and reenter the request.

UDS0023	Index not built
Explanation:	A CATLG (catalog) request was entered and the index name required has not been created
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Build or created the appropriate index entry and reenter the request.

UDS0024	Inconsistent catalog structure
Explanation:	An invalid index structure was specified while creating an index or alias.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Determine the appropriate index entry format and reenter the request.

UDS0025	Bad return code from index
Explanation:	A BLDX (build index) or DLTX (delete index) request was entered and an unusual error condition occurred.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	The catalog structure may be in error. Contact the System Programmer to determine the cause of the error.
System programmer info:	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.

UDS0026	Higher level index does not exist
Explanation:	A BLDX (build index) or DLTX (delete index) request was entered and a higher level index structure could not be found.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	The catalog structure may be in error. Contact the System Programmer to determine the cause of the error.
System programmer info:	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.

UDS0027	Index has alias or dataset(s) cataloged
Explanation:	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.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Uncatalog the dataset(s) that are cataloged with the index structure and reenter the DLTA or DLTX request.

UDS0028	Not cataloged
Explanation:	A request was entered to locate a dataset via the catalog and the dataset was not cataloged.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	This error may be caused by an incorrectly entered dataset name. Correct the dataset name and reenter the request.

UDS0029	Syntax error in DSN
Explanation:	A request was entered for a dataset and the dataset name was entered incorrectly.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Correct the format of the dataset name and reenter the request.

UDS0030	Bad return code from LOCATE
Explanation:	A DISP request was entered and an unusual error condition occurred.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	The VTOC contents for the indicated volume may be in error. Contact the System Programmer to determine the cause of the error.
System programmer info:	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.

UDS0031	Bad return code from CATALOG
Explanation:	A Disp request was entered and an unusual error condition occurred.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	The catalog for the indicated volume may be in error. Contact the System Programmer to determine the cause of the error.
System programmer info:	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.

UDS0032	Catalog not available
Explanation:	A catalog request was entered and the catalog could not be accessed.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Retry the request. If the error persists, contact the System Programmer to determine the cause of the error.
System programmer info:	Determine why the catalog cannot be accessed and correct the error.

UDS0033	Index not found
Explanation:	A catalog request was entered and the index name required was not found.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Build or create the appropriate index entry and reenter the request.

UDS0034	Generation DSname invalid
Explanation:	a BLDG (build generation) request was enter for a dataset and the dataset name was entered incorrectly.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Correct the format of the dataset name and reenter the request.

UDS0035	Already cataloged
Explanation:	A CATLG (catalog) request was entered and the datase name was already cataloged.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Correct the dataset name and reenter the request.

UDS0036	Error loading security user exit 'UDSEX1'
Explanation:	A site user exit, UDSEX1, can be used to check authorization to use UDS functions. An unexpected error occurred while trying to load UDSEX1.
System action:	UDS is abnormally terminated and an online dump is taken.
Terminal operator info:	Contact the System Programmer to determine the cause of the error.
System programmer info:	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.

UDS0037	Bad return code from SVC 32
Explanation:	SVC 32, the allocation SVC, was issued by UDS and returned an error.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Retry the operation; If the error persists, contact the System Programmer to determine the cause of the error.
System programmer info:	This message may be caused by a hardware problem. Retry the operation. If the error persists, contact the hardware maintenance personnel.

UDS0038	Invalid value for DSORG
Explanation:	A request was entered to allocate a dataset and an invalid DSORG value was specified.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Correct the format of the DSORG argument and reenter the request.

UDS0039	Invalid value for RECFM
Explanation:	A request was entered to allocate a dataset and an invalid RECFM value was specified.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Coorect the format of the RECFM argument and reenter the request.

UDS0040	Fifth value must be CONTIG, MXIG, or ALX
Explanation:	A request was entered to allocate a dataset and an invalid fifth argument was specified for the space definition.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Correct the format of the argument andreenter the request.

UDS0041	Non-numeric data in field
Explanation:	A request was entered and a non-numeric value was entered for a numeric argument.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Coorect the format of the argument and reenter the request.

UDS0042	Index not found in catalog
Explanation:	A BLDX (Build index) or DLTX (delete index) reuqest was entered and a higher level index structure could not be found.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	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.
System programmer info:	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.

UDS0043	Directory space larger than primary allocation
Explanation:	A request was entered to allocate a dataset and the values entered for the primary allocation and the number of directory entries are conflicting.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Correct the arguments and reenter the request.

UDS0044	Primary space is zero
Explanation:	A request was entered to allocate a dataset and the value specified for the primary allocation was zero - a non-zero value is expected.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Correct the arguments and reenter the request.

UDS0045	VTOC full
Explanation:	A request was entered to allocate a dataset and no space remains in the Volume Table of Contents (VTOC) to contain the requested entry.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Contact the System Programmer to remove dataset(s) from the volume.
System programmer info:	Scratch one or more datasets from the indicated volume.

UDS0046	Space requested not available
Explanation:	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.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Contact the System Programmer for assistance.
System programmer info:	Scratch one or more datasets from the indicated volume.

UDS0047	Invalid record length
Explanation:	A request was entered to allocate a dataset and an invalid record length argument was specified.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Correct the record length argument and reenter the request.

UDS0048	Catalog not found on indicated volume
Explanation:	A CVOL request was entered and the indicated control volume did not contain a catalog.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	This may indicate that the volume requested is in error. If not, contact the System Programmer for assistance.
System programmer info:	Obtain a VTOC listing of the volume, determine the cause of the error. Create the required entries (or catalog).

UDS0049	Sixth field must be 'ROUND'
Explanation:	A request was entered to allocate a dataset and an invalid sixth argument was specified for the space allocation request.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Specify 'ROUND' as the sixth argument or omit it at all.

UDS0050	List type operand invalid
Explanation:	A request was entered and 'LIST' was specified as an argument. LIST may be specified as an operation, but not as an argument.
System action:	UDS remains conversational and processing continues.
Terminal operator info:	Reenter the request, omitting 'LIST' from the arguments.

UDS0051	Security module not found
Explanation:	The UDS security user exit routine, UDSEX1, is not linked in with the utility or is not available on COMPLIB.
System action:	UDS will terminate.
Terminal operator info:	Contact your System Programmer for assistance.
System programmer info:	Either link UDSEX1 with UDS, or make it available in COMPLIB.

UDS0052	Please enter TRK, CYL or average block size
Explanation:	Self-explanatory message.

UDS0053	Value for BLKSIZE incorrect
Explanation:	Self-explanatory message.

UDS0054	Operation aborted
Explanation:	Self-explanatory message.

UDS0055	Bad return code from LSPACE
Explanation:	An LSPACE macro was unsuccessfully issued to get the free space information for a disk.
System action:	The UDS function is terminated
System programmer info:	Inform SAG support about the returncode and the z/OS version.

UDS0060	Error calling the CSI interface.
Explanation:	Self-explanatory message.
System action:	The CSI interface gave a returncode (R15) > 0. UDS is terminated.
System programmer info:	If the problem is reproducible inform Software Ag Support.

UDS0100	Unknown function given
Explanation:	Self-explanatory message.

UDS0101	DSN operand missing
Explanation:	Self-explanatory message.

UDS0102	VOLUME operand missing
Explanation:	Self-explanatory message.

UDS0103	NEWNAME operand missing
Explanation:	Self-explanatory message.

UDS0104	DEVICE operand missing
Explanation:	Self-explanatory message.

UDS0105	ALIAS operand missing
Explanation:	Self-explanatory message.

UDS0106	INDEX operand missing
Explanation:	Self-explanatory message.

UDS0107	NUMBER operand missing
Explanation:	Self-explanatory message.

UDS0108	NEWVOL operand missing
Explanation:	Self-explanatory message.

UDS0109	Unknown PF-key used
Explanation:	Self-explanatory message.

UDS0110	Invalid fetch request
Explanation:	Self-explanatory message.

UDS0111	Access to requested function disallowed
Explanation:	Self-explanatory message.