When RCVBIRD is run the AA to ZZ data is extracted and set up as RCVpppp### in /edx/AIRPEX/ABI/SPOOL/BROKERS (pppp is the partner code. File /edx/AIRPEX/ANSI/SPOOL/PARTNERS is used in the process.) DLBIRD is then used to process the data into the appropriate btas files. Message "wrapper" is 996 E-MAIL Messages: e-mail messages should be sent to bird@ In /usr/lib/aliases there is an entry for bird "|/bms/bin/birdmail" There is a directory /home/bird with the copies of the received mail as bird.nnnnn where nnnnn is a process number. Add to script to append to a history file named YYYYMMDD put process number and msg in history file e-mail is processed to a file MAILnnnnn in /edx/AIRPEX/ABI/SPOOL/BROKERS When DLBIRD is run it first goes through any MAIL* files and breaks them up into RCVMAIL### files. These are then processed along with the ANSI files. DLBIRD: This program processes the file in /edx/AIRPEX/ABI/SPOOL/BROKERS If it is able to process all data in a file it deletes it. If it is 7501 or not supported it ignores it. If it is STAT but can not process all the data, it saves it in SAVE dir The current status of the processing is: 7501 MSGs - Not Supported Program will write info to a file BIRD.IN Info is From Broker, From "File" number, Importer EIN, Cust # if possible, space for JSC File# After DLBIRD runs, exec to DLBRD75 which will find all the 7501 msgs and process them if cust# and file# are in BIRD.IN If entries in BIRD.IN without file#, cust#, send e-mail to tony. If all records can be processed, delete it. If not move it to SAVE STAT MSGs EN Records - Processed to ENTRY, ENTRY.DESC ENTRY.EDI has our file#, 20 Char Originator Ref No. DT Records - Processed to various files Rx Records - Processed by DLRLPR at the end of DLBIRD MI Records - FIRMS code updated RM Records - Not Supported MSGS MSGs - Not Supported JI MSGs - Not Supported JR MSGs - Not Supported NR MSGs - Not Supported Implementing 7501 Messages: 1 - File Numbers 2 - Importer Customer Numbers 3 - Consignee, Invoicee Customer Numbers 4 - Create WS because can't get 7501 printing info from message. 5 - Some info for W/W only on the 7501. This is a problem. 6 - ADD/CVD data is only on 7501