|
|
 |
|
|
|
register |
bbs |
search |
rss |
faq |
about
|
|
|
meet up |
add to del.icio.us |
digg it
|
|
|
|
415 to 510 area code split prefix data
NOTICE: TO ALL CONCERNED Certain text files and messages contained on this site deal with activities and devices which would be in violation of various Federal, State, and local laws if actually carried out or constructed. The webmasters of this site do not advocate the breaking of any law. Our text files and message bases are for informational purposes only. We recommend that you contact your local law enforcement officials before undertaking any project based upon any information obtained from this or any other web site. We do not guarantee that any of the information contained on this system is correct, workable, or factual. We are not responsible for, nor do we assume any liability for, damages resulting from the use of any information on this site.
: 415 to 510 area code split prefix data. 415-xxx-yyyy to 510-xxx-yyyy
: where xxx equals:
:
:SUM 44999
204 208 210 215 222 223 224 226 228 229 231 232 233 234 235 236 237 238 245 246
248 251 253 254 256 261 262 263 268 271 272 273 275 276 277 278 283 284 287 293
294 295 297 302 308 313 317 339 351 352 356 357 370 372 373 374 376 420 422 423
425 426 427 428 429 430 436 437 438 439 443 444 446 447 448 451 452 455 458 460
462 463 471 475 481 482 483 484 486 487 489 490 498 515 516 521 522 523 524 525
526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 547 548 549 551 559
562 568 569 577 581 582 596 598 601 602 603 606 609 613 614 618 620 623 624 625
631 632 633 634 635 636 638 639 642 643 644 645 646 649 651 652 653 654 655 656
657 658 659 667 670 671 672 674 675 676 678 680 682 683 684 685 686 687 689 704
706 708 709 713 716 717 718 724 727 729 732 733 734 735 736 741 743 745 746 748
754 757 758 762 763 769 778 779 782 783 784 785 786 787 790 791 792 793 794 795
796 797 798 799 801 803 810 814 815 819 820 823 825 827 828 829 830 831 832 833
834 835 836 837 838 839 840 841 842 843 845 846 847 848 849 862 865 866 867 869
874 881 884 886 887 888 889 891 893 895 901 910 930 932 933 934 935 937 938 939
942 943 944 945 946 947 975 977 987 ***
:END
415/510 AREA CODE SPLIT
Effective Sept. 2, 1991
The 415 area code covers the San Francisco Bay Area, from Marin County,
San Francisco, San Mateo County, Santa Clara County, Alameda County,
Contra Costa County and parts of Santa Cruz County.
Pacific Bell will split area code 415 into two area codes 415/510
starting Sept. 2, 1991. There will be a five-month period from Sept. 2,
1991 to Jan 27, 1992, when both the new and old ways of completing
calls will continue to work. Beginning January 27, 1992, calls dialed
with the incorrect Area Code will not be completed. A recording will
explain the new dialing procedures and the call will need to be
re-dialed using the correct Area Code.
Why are new Area Codes being introduced?
An increase in population, coupled with the rapid growth of a variety
of services -- such as data, fax, pagers, and cellular/mobile
telephones -- has reduced the supply of available telephone numbers.
Here are some things to consider in planning for this change:
Revise Printed Materials. Check your personal as well as business
records to be sure your correct Area Code appears on items such as:
Brochures, Business Cards, Labels/Product Packaging, Invoices,
Personal Directories and Stationery.
Reprogram Equipment. Update electronic that works with your telephone
line such as:
Any telephone equipment that you lease or own that requires
reprogramming and/or manufacturer adjustments, automatic dialers,
burglar alarms, Cellular/Mobile telephones, Customer-owned pay
phones, Fax machines, Modems, Pagers, Speed call lists, telephone
systems with automatic call routing capabilities, and finally all
computerized mail/phone lists.
By using the prefix listing contained in this file, you may customize a
program to update all of your mail/phone list databases. A programmer
will have to install such a program to your system.
FORMAT OF "PREFIX.LST" FILE:
All lines with byte position one as a value of : is a remark and should
be ignored.
End of list marker is :END and lines below the end of list marker
should not be scanned. Also, the end of prefix list is also marked by
a *** as the final string prefix.
The :SUM marker is a 16 bit (decimal) check sum of all bytes (including
spaces, [assuming 7 bit ASCII] excluding returns/line feeds ) of all
bytes in the prefix data area and also marks the beginning of this data
area. Input the data line into a string variable. If the data line is
less than 80 bytes, pad bytes with nulls to the 80th byte. Sum each 16
bit block (2 bytes). At any time the sum exceeds 16 bits (>65535)
truncate or subtract the 17th bit (-65536). Follow the BASIC example
below.
Prefix list is formatted as 20 (3 byte) prefixes on each line separated
by one space. They are in numerical order from left to right, top to
bottom, and also should be verified for accuracy.
With both the checksum method and the prefix order verification, the
prefixes can be trusted. If you find this file to be corrupted, or have
any questions regarding this file, please call the BBS below. Your
questions can be directed to the sysop.
PROGRAMMING LOGIC:
A program can be designed to scan all records in a file that contains
telephone number fields. 415-xxx where xxx equals any of the prefixes
in the PREFIX.LST file should be changed to 510-xxx. The seven digit
prefix and number will remain the same. Use a substring scan using the
record data prefix as the substring contained anywhere in the
PREFIX.LST data lines. If true, change the area code to 510. Be sure
to recognize a nulled or spaced area code. Only change these records
if you are processing spaced area codes in the 415 area, assuming that
there is no need to specify area code 415 within the 415 area.
Good Luck.
BASIC CHECKSUM EXAMPLE: (Please note file handling is system dependant)
100 OPEN "prefix.lst" on #1
110 IF EOF(1) THEN GOTO 500 : REM END OF FILE?
120 INPUT #1,Z$ : REM READ DATA LINE FROM FILE INTO Z$
130 X$=MID$(Z$,1,1) : REM GET FIRST BYTE OF Z$ PLACE IN X$
135 IF X$=":" THEN GOTO 200 : REM IS X$=":" ? YES-- GOTO 200
140 Z=LEN(Z$) : REM GET LENGTH OF Z$, PLACE IN Z
145 IF Z>80 THEN GOTO 510 : REM LINE EXCEEDS 80 CHARACTERS, (ERROR)
150 IF Z=80 THEN GOTO 160 : REM CONDITION, END OF PAD?
152 Z$=Z$+CHR$(0) : REM PAD Z$ WITH NULL UNTIL Z=80
154 GOTO 140 : REM LOOP UP FOR NEXT PAD
160 FOR I=1 TO Z STEP 2 : REM 16 BIT (2 BYTE) CHECKSUM BLOCKS
162 X$=MID$(Z$,I,1) : REM GET HIGH BYTE FROM Z$ STARTING AT I
164 X1=ASC(X$) : REM CONVERT TO ASCII, PLACE IN X1
166 X$=MID$(Z$,I+1,1) : REM GET LOW BYTE FROM Z$ STARTING AT I+1
168 X2=ASC(X$) : REM CONVERT TO ASCII, PLACE IN X2
170 SUM=SUM+(X1+(X2*256)) : REM ADD CHECKSUM
172 IF SUM>65535 THEN SUM=SUM-65536 : REM EXCEEDS 16 BIT?
174 NEXT I : REM NEXT 16 BIT BLOCK
176 GOTO 110 : REM LOOP UP TO READ NEXT LINE
200 X$=MID$(Z$,1,4) : REM GET FIRST 4 CHARACTERS OF : LINE
204 IF X$=":END" THEN GOTO 500
206 IF X$=":SUM" THEN GOTO 210
208 GOTO 110
210 X$=MID$(Z$,6,5) : REM GET CHECKSUM FROM FILE, PLACE IN X$
212 FSUM=VAL(X$) : REM SET FSUM TO THE VALUE OF X$
214 GOTO 110
500 CLOSE #1
502 PRINT "PROGRAM BYTE CHECKSUM = ";SUM
504 PRINT " FILE BYTE CHECKSUM = ";FSUM
506 IF SUM<>FSUM THEN PRINT "ERROR, CHECKSUM DOES NOT MATCH. FILE CORRUPT."
508 END
510 PRINT "ERROR, A LINE EXCEEDS 80 CHARACTERS. FILE CORRUPT."
512 GOTO 500
999 END
Please distribute this file! This is an information age aid that
everyone in data base management will need!
James Driskill
San Leandro, CA
(415/510) 430-2865 (BBS - 2400/8/1/N)
|
|
|
To the best of our knowledge, the text on this page may be freely reproduced and distributed.
If you have any questions about this, please check out our Copyright Policy.
totse.com certificate signatures
|
|
|
About | Advertise | Bad Ideas | Community | Contact Us | Copyright Policy | Drugs | Ego | Erotica
FAQ | Fringe | Link to totse.com | Search | Society | Submissions | Technology
|
|
|
|
|
|
