BackPak H4.00 Troubleshooting and Messages Manual

Messages
49 BackPak H4.00 Troubleshooting & Messages
Number Text Explanation Action
3108 MountId: %s. Volume
%s. Equal sign missing
after keyword '%s' in
the mount message of
TAPE DEFINE..
A load request is
rejected because an
unexpected content of
the TAPE DEFINE.
Check the bbox-secure
syntax in the TAPE
DEFINE comment.
EZX product: be sure
to use the
EZX_START_XFER
macro to build the
TAPE DEFINE.
3109 MountId: %s. Volume
%s. MVS Dataset name
'%s' exceeds 44
characters in the mount
message of TAPE
DEFINE.
The DSN of an MVS
dataset is limited to 44
characters
Check the execution of
the EZX_START_XFER
macro that must be
run to build the TAPE
DEFINE.
3110 MountId: %s. Volume
%s. MVS Conversion id
'%s' exceeds %d
characters in the mount
message of TAPE
DEFINE
The conversion
specification is limited to
12 characters.
Check the execution of
the EZX_START_XFER
macro that must be
run to build the TAPE
DEFINE.
3111 MountId: %s. Volume
%s. MVS Dataset name
(DSN=) is missing in the
mount message of TAPE
DEFINE.
A TAPE DEFINE asking
for a virtual volume
created for EZX
operation was not
correctly created by the
EZX_START_XFER
macro.
Check the execution of
the EZX_START_XFER
macro that must be
run to build the TAPE
DEFINE.
3112 %ld MVS datasets %s
ready for transfer
through EZX volume %s
for %s.%s %s. (%ld
tracks, %s bytes). %s.
(MVS time: %s)
The EZX_START_XFER
macro prepared
successfully the MVS
datasets for the
transfer, eventually
created them.
None.
3113 MountId: %s. EZX MVS
Agent reject the transfer
through EZX volume
%s. %s.
The execution of the
EZX_START_XFER
macro or the processing
of a mount request for
EZX is rejected by the
EZX MVS Agent.
Check the error text
returned by MVS at the
end of this message.
Check the MVS
console.
Verify the
EZX_START_XFER
macro parameters.