User guide

Introduction
4-2: Putting Data on EDA Servers
The
nn
number should match the
minor_rev
level that will result when you run
bom_upload
, the EDA analyst completes the BOM upload, and the files are
moved to the
/bay
dir
/dra/rel
release area (see below). For example, if the part had
been 300123-A.04, the directory would be 300123-A.05.
The PCN “Release” Area
EDA scripts allow you to use the
/bay
dir
/dra/2brel
area to submit data that will
eventually be placed into the
/bay
dir
/dra/rel
area.
The
/bay
dir
/dra/rel
area is controlled and maintained by the EDA group. If a file
is in this area, it does not mean that the file is “released to production.” It means
that we have a copy of data stored at a particular revision state, regardless of
whether or not it has been released to production.
These data storage directories are located in the
mech
,
docs
, and
programs
subdirectories under
/bay
dir
/dra/rel
, and they are named
PPP
000/
PartNumber
.
rev
(or
PartNumber.nn
) where
PPP
is the first three digits of the part
number. For example,
/bayeast/dra/rel/mech/300000/300123-A.05
.
A UNIX
cron
script examines the
/bay
dir
/dra/2brel
directories to match their
PartNumber.nn
subdirectories against these
/rel
subdirectories and the SAP
database, and it will, under certain specific conditions, move files from /
bay
dir
/
dra/2brel
to
/bay
dir
/dra/rel
. For example, files for programmable parts move as
long as the
nn
extension in
/2brel/programs/
PartNumber
.
nn
is higher than that
part number’s extension in
/rel/programs/
PPP
000/
PartNumber
.
mm
. For
mechanical parts, the
nn
extension must match the one in SAP.
Please note that all file naming conventions are case sensitive, for example,
PARTNUMBER.REVISION
and
PARTNUMBER.extension
are different.