DSM/SCM Event Management Programming Manual

Event Messages
DSM/SCM Event Management Programming Manual529844-003
5-97
3012 ZPHI-EVT-OSSFL-IN-REL-PATHNM
3012 ZPHI-EVT-OSSFL-IN-REL-PATHNM
The A7CINFO file contains an OSS file with a relative path name.
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 contains an OSS file with a relative path (the path does
not start with a slash “/” character). DSM/SCM does not allow relative path names.
Effect. The activity finishes with warnings. The DSV is not processed as part of the
current input.
Recovery. The relative OSS file must be removed from the pax archive file and a new
DSV generated. 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> contains invalid file <3>
with a relative path name. Relative path names are not
allowed by DSM/SCM. DSV skipped, processing continues.