DSM/SCM Event Management Programming Manual

Event Messages
DSM/SCM Event Management Programming Manual529844-003
5-94
3009 ZPHI-EVT-UNKNOWN-OSSFL-RECTYPE
3009 ZPHI-EVT-UNKNOWN-OSSFL-RECTYPE
The A7CINFO file contains a record for an OSS file with an invalid file type.
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 has an invalid file
type. DSM/SCM supports only file types of Regular File, Directory, Symbolic Link, Hard
Link, or FIFO.
Effect. The activity finishes with warnings. The DSV is not processed as part of the
current input.
Recovery. This 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>
which has an OSS file type other than Regular File,
Directory, Symbolic Link, Hard Link, or FIFO. DSV skipped,
processing continues.