DSM/SCM Event Management Programming Manual
Event Messages
DSM/SCM Event Management Programming Manual—529844-003
5-99
3014 ZPHI-EVT-ARC-FN-NOT-TO-ZOSSUTL
3014 ZPHI-EVT-ARC-FN-NOT-TO-ZOSSUTL
A pax archive file referenced by an A7CINFO file is not placed in the ZOSSUTL TSV.
ZPHI-TKN-FILE-NAME
is the pax archive file that contains the invalid file record.
ZPHI-TKN-INT-SVNM
is the name of the DSV where the error occurred.
ZPHI-TKN-ABS-OSS-FILENAME
is the name of the invalid OSS file.
Cause. The pax archive file referred to by records in the A7CINFO file must be placed
in the ZOSSUTL TSV. This pax archive file must have specified the ZOSSUTL TSV to
create the A7CINFO file. The destination TSV for the pax archive file changed since
the A7CINFO file was created.
Effect. The activity finishes with warnings. The DSV is not processed as part of the
current input.
Recovery. Use CNFGINFO to change the TSV for this pax archive file to ZOSSUTL.
For help completing the correct CNFGINFO processing, contact the product vendor.
Because the DSV is skipped, you must bring the DSV into DSM/SCM as a separate
input. You can then assign both inputs to the same input group through the Planner
Interface. If the input is an RVU or SPR, contact your service provider and provide all
relevant information:
•
Descriptions of the problem and accompanying symptoms
•
Details from any generated messages
•
Supporting documentation such as the $ZPHI EMS logs and trace files (if
requested by your service provider)
If your local operating procedures require contacting the Global Customer Support
Center (GCSC), supply your system number and the numbers and versions of all
related products as well.
Tokens
ZPHI-TKN-FILE-NAME <1> token-type ZSPI-TYP-STRING
ZPHI-TKN-INT-SVNM <2> token-type ZSPI-TYP-SUBVOL
ZPHI-TKN-ABS-OSS-FILENAME <3> token-type ZSPI-TYP-STRING
Message Text
pax archive file <1> in DSV <2> is not placed in the ZOSSUTL
TSV. According to the A7CINFO file, <1> contains OSS file
<3>. DSV skipped, processing continues.