DSM/SCM Event Management Programming Manual

Event Messages
DSM/SCM Event Management Programming Manual529844-003
5-98
3013 ZPHI-EVT-ARCH-FNAME-NOT-IN-A0C
3013 ZPHI-EVT-ARCH-FNAME-NOT-IN-A0C
The A7CINFO file contains an OSS file that refers to a nonexistent pax archive file.
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 A7CINFO file contains a record for an OSS file that came from a pax
archive file that is not in the DSV. There is no record in the A0CINFO file for the pax
archive file.
Effect. The activity finishes with warnings. The DSV is not processed as part of the
current input.
Recovery. The missing pax archive file must be added to the DSV and CNFGINFO
run for the DSV to add the missing file to the A0CINFO file. 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> is missing from the A0CINFO file in DSV
<2>. According to the A0CINFO file, <1> contains OSS file
<3>. DSV skipped, processing continues.