User guide

Processing of the Programmable Parts Directory
B-2: Behind the Scenes
Processing of the Programmable Parts Directory
BNE
cron
scripts (and BNW manual scripts) periodically scan
/bay
dir
/dra/2brel/
programs
for new subdirectories, e.g., 302690-A.00.
If they find one, the scripts send you email, and they try to transfer the program
parts to the same subdirectory in
/bay
dir
/dra/rel/programs/
PPP
000
, where
PPP
is the first three digits of the part number. If that new subdirectory already exists in
the
/rel
area, e.g.,
/bay
dir
/dra/rel/programs/302000/302690-A.00
, the transfer
doesn’t happen.
If the new subdirectory does
not
already exist in
/bay
dir
/dra/rel/programs
:
1.
It is moved into the
programs/
PPP
000
directory with a new owner (
root
).
Note:
Other conditions will also cause your part to remain in
/bay
dir
/dra/2brel/programs
: a part
with a release status of REL, or not found in SAP, or not submitted in a properly named
part.nn
directory, or not submitted in a directory, or without a known file type (see
Object Types for
Programmable Parts
on page 4-3).
2.
Checksums are extracted from the part’s device files. They are named
checksum
.
fus
and
checksum
.
xmt
for fuse and transmit, respectively. If no
transmission checksum is available, a file named NOXMT.
xmt
is created.
3.
A .
history
file is created in the new subdirectory with an
ls -lt
“long listing”
of the subdirectory contents prior to the transfer.
For example, where the program files for part 302852-A have been moved
into
/bay
dir
/dra/rel/programs
/302000/302852-A.01, and its checksums have
been generated:
caps% ls -als 302852-A.01
total 36
1 -rwxr-xr-x 1 relzar 67 May 6 15:02 .history
33 -rwxr-xr-x 1 root 32772 May 6 14:36 302852-A.rom
1 -rwxr-xr-x 1 root 117 May 6 15:03 7AFD52.fus
1 -rwxr-xr-x 1 root 117 May 6 15:03 NOXMT.xmt
4.
If successful, the script sends you email notice of the directory moved, the
generated checksums, and the transfer time. If you find a problem with the
information, please contact EDA.