BackPak H4.00 Troubleshooting and Messages Manual

Messages
53 BackPak H4.00 Troubleshooting & Messages
Number Text Explanation Action
3137 Error computing MVS
dataset allocation for
disk %s, EZX volume
%s. %s
Internal error. Contact the Product
Support.
3138 MVS dataset %s
allocated for transfer
through EZX volume %s
for %s.%s %s. %s
Successful lock of MVS
dataset when processing
a mount request.
None.
3139 Estimated data size to
send (%s MB) requires
the creation of %ld MVS
datasets. Maximum
number of datasets %s
is %ld. EZX volume %s
for %s.%s.
Unable to create MVS
dataset able to contain
the specified TRFSIZE.
Be sure the FILEID
allows creating a group
of datasets (ends by
".EZX")
Revise the maximum
allocation configured in
the Domain
configuration,
DataStore tab.
3140 Estimated data size to
send (%s bytes)
exceeds the capacity of
the %ld existing MVS
dataset(s) %s (%ld
tracks, %s bytes). EZX
volume %s for %s.%s.
(MVS time %s)
The transfer is rejected
because the TRFSIZE
specifies a size
exceeding the capacity
of MVS datasets to write
Recreate the MVS
datasets and revise
TRFSIZE.
Remove the TRFSIZE
parameter to disable
this validation.
3141 The total size (%ld
tracks, %s bytes) of %ld
existing MVS dataset %s
exceeds the estimated
data size to receive (%s
bytes). EZX volume %s
for %s.%s. (MVS time
%s)
The transfer is rejected
because the TRFSIZE
specifies a size that can
not contain the capacity
of MVS datasets to read
The MVS dataset
tested size is the
allocated size, not the
used size.
Use SPACE = (,RLSE)
when writing the MVS
dataset to release
unused space.
Revise TRFSIZE.
Remove the TRFSIZE
parameter to disable
this validation.