Clear technical procedures for S 390, Midrange, UNIX, LAN, and PCs.
Management and legal advice cited extensively elsewhere
Dozens of case reports from leading companies and agencies
Over 200 easy-to-use forms and visual explanations
28 pre-tested Y2K surveys and worksheets
65 effort-saving Year 2000 checklists
51 clear, self-explanatory diagrams
55 authoritative charts and tables
33 explicit coding examples to emulate
The most extensive bound listing of Y2K related vendors, websites, and publications.

"The Compleat Manager chapter opens with four plain words-YOU CAN DO THIS. Given the use of this resource volume, I believe a good computer manager can. As a Hearst reporter of long standing, I am fascinated by my first chance to find out how IS departments can remedy the Year 2000 problem...Inexpensive automation is the big surprise in this book. Patrick Hagan explains why you don't have to purchase the new COBOL. Manuals from SyncSort and IBM reveal you already own an automated tool to create 'bridge' interfaces. The Air Force's chapter tells how to get a free book in which they rate hundreds of testing products. Sanford Feld's chapter shows how to protect your main computer. Sample questionnaires, forms, and checklists about including the outsourcing checklists of Cap Gemini, Paragon and Syspro." -Shirley Lembeck in the April, 1997, Information Executive.



Sample Content

Downloadable Sample Chapter

Click here for a sample chapter for this book: 0136465064.pdf

Congressional Statement.

Statement of Representative Stephen Horn, Chair, Subcommittee on Government Management, Information and Technology.

Preface.

I. CEO/CIO: THE CHALLENGE.

1. Top Ten List of Excuses Not to Address Year 2000 Issues, Dale F. (Doc) Farmer, SBC Warburg Corporate Audit.
2. Director’s Guide to the Year 2000, Dick Lefkon, Year 2000 Committee of AITP SIG-Mainframe.
3. The Millennium Rollover Is Not a Surprise, Dick Lefkon, New York University.
4. I’m Not Worried, Ernst & Young, LLP.
5. The Century Date Problem: How Bad Can It Be? Milt HabecK, Unbeaten Path International.
6. Actionable Caveats, Chris Casey, Bytewise Consulting, Inc., Ted Fisher, Sperduto & Associates, Inc.
7. Have You Selected These Seven Methods? Dick Lefkon, Year 2000 Committee of AITP SIG-Mainframe.
8. Four Primary Compliance Criteria, Yngvar Tronstad, Jan Peterson, Joe Ramirez, Jack Ashburner, Grant Robinson, Ascent Logic Corporation.
9. FIPS Publication 4D1 Change Notice, National Institute of Standards and Technology.
10. Proposed Draft Revised American National Standard X3.30, Representation of Date for Information Interchange, American National Standards Institute.
11. Product Certification and Year 2000 Infrastructure, Dick Lefkon, Year 2000 Committee of AITP SIG-Mainframe.
12. Millennium Rollover: The Year 2000 Problem, NIST Computer Systems Laboratory.
13. So You Can’t Program Your VCR? Harold Carruthers, Edward Jones & Co.
14. The Successful Year 2000 Project Office, Dick Lefkon, Year 2000 Committee of AITP SIG-Mainframe.
15. Year 2000: The End of IS? Gerhard Adam, Syspro, Inc.

II. CEO/CIO: SURVIVING FAILURE.

16. Surviving the 21st Century, Ken Orr, The Ken Orr Institute.
17. The Y2K Bear Market of 1997 ??DO99, John Westergaard, Westergaard Online.
18. Prepare for Worse, Gregory Cirillo, Williams, Mullen, Christian & Dobbins, Ira Kasdan, Galland, Kharasch & Garfinkle, P.C.
19. You Can Lose Your House and Yacht, Warren Reid, WSR Consulting Group, LLC.
20. You Might Receive a OCO Grade, Tom Bachman Mitre, Stephen Horn and Carolyn Maloney, House Subcommittee on Government Management, Information and Technology, Dick Lefkon, New York University, Denis J. Reimer, General, United States Army Chief of Staff, Togo D. West, Jr., Secretary of the Army.
21. Nuclear Disaster and the Millennium Trojan Horse, Dick Lefkon, New York University.
22. Replacing Your Embedded Chips, Bill Payne, Kramer & Kent, Dick Lefkon Millennium Associates
23. Ignore the “New” Y2K Project Management at Your Peril, Dick Lefkon, Year 2000 Committee of AITP SIG-Mainframe.
24. How Do You Know Without Testing? Miro Medek, Mitretek Systems.
25. Are You Testing Enough? Dick Lefkon, Millennium Associates.

III. CEO/CIO: GETTING STARTED.

26. Software Conversion: Issues and Observations, Information Technology Association of America.
27. Metrics and Findings, Viasoft.
28. Surround Yourself with Solutions, Daniel Miech, Terasyssm, Inc.
29. Technical Solution Overview, Chris Casey, Bytewise Consulting, Inc., Ted Fisher, Sperduto & Associates, Inc.
30. Assessment Metrics Checklist, Micro Focus Limited.
31. New Development Initiatives, Jim Zetwick, Borden Foods Corporation.
32. Catastrophe or Opportunity? Cap Gemini America.
33. Project Tasks, Platinum Technology, Inc.
34. Year 2000 Firewall: Using an Inexpensive Time Machine, Judy Brand, JBG Pygmy Mainframes.
35. Starting the Assessment Process, Gerhard Adam, Syspro, Inc.

IV. CEO/CIO: THE COST.

36. Budget All Activities, Dick Lefkon, Year 2000 Committee of AITP SIG-Mainframe.
37. Five More Reasons Many Delayed, Michael Gerner, Unibol, Ltd.
38. Project Cost Estimating: Simple to Sophisticated, John Trewolla, Trewolla Technology Taskforce.
39. E-S-T-I-M-8-R, U. S. Department of Defense.
40. Capacity? Swap Consultant, Mainframe, Sanford Keith, Feld Bestbuilt Systems, IBM.
41. Global Economic Impact, Capers Jones, Software Productivity Research, Inc.

V. CEO/CIO: SENIOR MANAGEMENT APPROACHES, Chris Casey, Bytewise Consulting, Inc., Ted Fisher, Sperduto & Associates, Inc.

42. Enterprise Management Approach.
43. Year 2000 Scope and Impact.
44. Requirements, in Business Terms.
45. Board Room: Legal, Accounting, Marketing, Risk.
46. Getting from Awareness to Acceptance.
47. Perspective, Conflict, Commitment, Scope Creep.
48. Solution: Time, Cost, Risk.
49. Methodology Phase I: Non-Compliance Risks, Positives.
50. Phase II: Teams, Impact Analysis, Contingency.
51. Phase III: Reaping the Rewards.

VI. CEO/CIO: Y2K CONTRACTS.

52. Corporate Legal Issues, Jeff Jinnett Of Counsel, LeBoeuf, Lamb, Greene & MacRae, L.L.P.
53. Vendor Liability, Courtney H. Bailey, Esq. Finnegan, Henderson, Farabow, Garrett & Dunner, L.L.P.
54. Recommended Contract Language, General Services Administration.
55. Warranty and Compliance Agreement, Timothy Feathers, Hillix, Brewer, Hoffhaus, Whittaker & Wright, L.L.C., Year 2000 Compliance Agreement.
56. Challenges and Legal Aspects, Warren Reid, WSR Consulting Group, LLC.
57. Ten Action Items, Ira Kasdan Galland, Kharasch & Garfinkle, P.C.

VII. EXPERT: SEVEN METHODS.

58. Date Windowing, Larry Baltezore, State of California.
59. Bridging: Fixed and Sliding Windows ???DFSORT, IBM.
60. Bridging: Fixed and Sliding Windows ???SyncSort MVS, SyncSort Incorporated.
61. New Windowing Method, Dick Lefkon, Year 2000 Committee of AITP SIG-Mainframe.
62. Procedural and Data Change, Andrew Eldridge, Complete Business Solutions, Inc., Robert Louton, GTE.
63. Change Strategies, Gerhard Adam, Syspro, Inc.
64. Dynamic Bridging, Viasoft.
65. Time Shifting, Don Estes, Don Estes & Associates.
66. Migration Strategies, Don Estes, Don Estes & Associates.
67. Reformatting Year-Date Notation, IBM.

VIII. EXPERT: DATE DETAILS.

68. Identifying 2-Digit-Year Exposures, IBM.
69. Technical Solutions, Michael Lips, Platinum Technology, Inc.
70. Embedded Dates, Richard Bergeon, Data Dimensions, Inc.
71. COBOL, Patrick Hagan, Project One Computer Consultants.
72. Date Routines, Harold Zbiegien, American Greetings Corp.
73. Extended Interval Aging, Jerome and Marilyn Murray.
74. Reengineering Your Software for the Millennium, William Brew Reasoning, Inc.

IX. EXPERT: EARLY TESTING.

75. Testing Techniques. IBM.
76. Implementation Issues Checklist, Micro Focus Limited.
77. What Can You Do for Microcomputers? Bryce Ragland, USAF.
78. Novell Products and the Year 2000, Tom Hartman, Novell.
79. UNIX Time, Richard Painter, Painter Engineering, Inc.
80. TICTOC/CICS, Isogon.
81. XPEDITER/Xchange, Gary Deneszczuk, Compuware Corp.
82. HourGlass 2000, Jerry Nelson, Mainware.

X. EXPERT: TEST TOOLS.

83. Don’t Need No Stinking Test Tools! Randall Rice, Rice Consulting Services, Inc.
84. capture End User Sessions, Platinum Technology, Inc.
85. File-AID/MVS, Compuware Corp.
86. Tool Categories, IBM.
87. Software Testing Technologies, Gregory T. Daich, Gordon Price, Bryce Ragland and Mark Daewood, United States Air Force.
88. Relational Test Data, Joseph Allegra, Princeton Softech, Inc.
89. Selecting Your Automated Test Tools, Dick Lefkon, Millennium Associates.

XI. MANAGER: USER SUCCESSES.

90. The First Two Year 2000 Factories, Dick Lefkon, Year 2000 Committee of AITP SIG-Mainframe.
91. The Y2K Project at BIAMAX S.A., Christos Andritsoyiannis, BIAMAX, S. A.
92. University of Florida, Robin Marrin, Information Systems, University of Florida,
93. White Paper ? SSA, Social Security Administration.
94. Project Plan Outline, Brenda McKelvey, Agriculture and Agri-Food Canada.
95. Leveraging the Experience of Others, Bill Wachel, The Greentree Group.
96. You DonOt Have to Face It Alone! Stan Price, Arizona Millennium Group.
97. User: Your First Three Steps, Dick Lefkon, Year 2000 Committee of AITP SIG-Mainframe.

XII. MANAGER: COMPLEAT Y2K MANAGER.

98. Project Planning, Gerhard Adam, Syspro, Inc.
99. Planning to Resolve Your Year 2000 Exposures, IBM.
100. USAF Compliance Checklist, U.S. Air Force.
101. Concurrent Phasing: Heart of the Y2K Factory, Dick Lefkon, Year 2000 Committee of AITP SIG-Mainframe.
102. Commitment Counts, Rita Tragesser, Germaine IndustrieS.
103. Project Management Office, USAA, Cesar Gonzalez, PMP, USAA.
104. Program Management Office in Action, Dick Lefkon, Year 2000 Committee of AITP SIG-Mainframe.
105. Century Date Compliance, Bill Goodwin, TickTickTick.
106. Standards, Dick Lefkon, Year 2000 Committee of AITP SIG-Mainframe.
107. Migration Weekend, IBM.
108. Conversion Methodology, N.T. Shivkumar, Curt Terwilliger, HCL America, Inc.
109. Assessment Guide, General Accounting Office.

XIII. MANAGER: OUTSOURCING.

110. Negotiating Your Remediation Contract, Gregory Cirillo, Williams, Mullen, Christian & Dobbins.
111. Questionnaires, John Rovito, Paragon.
112. Product Questionnaire, Gerhard Adam, Syspro, Inc.
Biographies.
Directory.
1996 Original Announcement of Best Practices Book, Kathryn Jennings, AITP SIG-Mainframe, Association of Information Technology, Professionals Membership Application.

Preface

Preface

If you are 35 and reading this book at midnight of 1999, you will suddenly qualify for retirement on some pension systems. And if you're 82 or 83 years old at that time, some college selection computers will be eager to bring you in as a standard age first-year student.

In a nutshell, that's the Year 2000/Y2K/Millennium computing crisis: Because most mainframe programs and machines—from Eisenhower through Clinton—stored and used only a two-digit year (97, not 1997), the year after O99 is O00. Take your age, subtract it from 00 and use a sign-free number, and you'll see how the example just described makes sense. If you don't believe me, how do you account for the 104-year-old woman in Minnesota who recently was sent a letter inviting her to join a pre-school there?

Your core Y2K mission is to make your computer systems run right and make their external interfaces conform to (probably) the new FIPS and ANSI date standards reproduced in the first chapter of this book. Your non-IS people will learn to replace non-conformant embedded chips, so that, in March of this “surprise” leap year, your security systems won't automatically seal off the entryways every Friday, thinking it is a Saturday.

Many goofy and amusing stories, often true, can be told about Year 2000 Computing. But it is very serious business. The cost of making the world's information systems work right will rival the cost of the U.S. Savings and Loan debacle—slightly smaller if you consider just the fixes, but larger if you include the damage and displacement costs to those who don't fix. A single parts factory shutdown recently stopped all General Motors manufacturing for months, so don't suppose that you can fix your systems and ignore whether or not your business partners fix theirs. And offsite code conversion has its savings limits, as you'll expend greater effort setting the inventory, baselining it onsite with confidential data, and retesting.

Can a company change its systems to be Year 2000 conformant? Mostly, yes! I reported on having done this in 1984, and others may have done it earlier and just not reported it. (Having a non-production “time machine” test computer helped.) That company-wide change was in the securities business, and we treated the Y2K need as though it was an inflexible regulatory requirement with noncompliance penalties in both cash and reputation. So should you.

Have organizations known about Y2K for a long time? Most certainly. For instance, attendees at my 1991 Y2K awareness paper presentations at the “Safe Computing” and “National Computer Security” conferences later told me they'd carried the alert back to their own companies, agencies and armed service branches.

Is there a lot of time left? Unfortunately not, and two precedents come to mind. After AIDS was recognized as a general-population threat in 1985, it took eleven years of significant funding to bring forth medicines that can reduce its virus concentrations in the human body. But the U.S. metric conversion—of cost to manufacturing similar to Year 2000 for computing—was never completed, even though given a generous 20 years deadline. Year O00 is approaching much faster, and most suggest you finish before O99. Should conducting this Millennium war be left entirely to the “soldiers?” Probably not. Programmer/analysts generally reserve highest professional respect for those of greatest expertise, but several of the Y2K gurus gossiping over the Internet don't just want systems to work right and interfaces to carry a four-digit year: They won't rest —until every man, woman and child around the globe— also says “1998” instead of OO98.

Should, then, techies be excluded from the deliberations? Again, no. The CIO sets the strategic course, the Y2K manager devises and executes the plan, but the house expert and soldier programmer/analysts should all also be involved in the planning phases for two reasons: (1) Collectively, they know most skeletons and closets; no outsourcing will as quickly catch dates passed in FILLER fields. And (2) morale must be one of your centerpieces or you'll find skeleton/closet expertise peeling away as each new month adds another dollar or two onto Y2K coder and manager hourly rates. This book truly represents the state of the art, both for do-it-yourself and for choosing a vendor to help if that's your desire. IBM, GUIDE, SIM, IMF, IMC, ACM, IEEE, AITP/DPMA, and nearly every recognized top professional in this field have permitted their best Y2K work to be reprinted here so that your corporation or agency will have available the knowledge to accomplish this organization-survival mission.

These pages contain at least half the information you'll need to make decisions and take action. Once you absorb respectively the sections for CEO/CIO-expert-manager, you'll know how to obtain any further information needed. You'll also be able to defend yourself from vendors who truly believe they have another solution. You'll also be better at separating hard data from fluff at www sites such as dod.mil, gsa.gov, y2klinks.com, and year2000.command limiting your (212) 539-3072 Editor's Advice inquiries.

If you had the extra millions or billions, you might be tempted to ignore and outsource the whole issue. Unfortunately, this is not a standard oranges-and-tangerines order, and it won't work just to throw three darts at a vendor list and select the best bid. that's because the solution paths (both outsourced and in-house) differ markedly from each other, and you can't choose if you don't know. For each application, you'll need to decide among date expansion, “smart” century, century, window, date shift in code or data, dropping/replacing the app, or not fixing it this century.

Most technical and management books present one consistent approach. Even where excellent, that viewpoint will work only accidentally for your Y2K effort because of the diversity of distinct cures. The present volume lays out at least three different well-stated solutions to each Y2K issue. To enable this, we ran a four-month public competition for “Year 2000 Best Practices” papers. To publicize its completion, we are presenting a series of two-day Y2K conference free to user organizations, ever since the first edition was published in autumn of 1996.

Even before being revised and expanded, that book was welcomed into the personal libraries of most Year 2000 practitioners; was heavily cited and excerpted in well-known Year 2000-related publications; was the technology resource for expert testimony to joint hearings of the U.S. House of Representatives Subcommittees on Science/Technology and Government Management; and contained material explicitly cited in expert testimony before the U.S. Senate Banking Committee.

With this “final report” in hand, you'll see that Y2K isn't Nobel Prize stuff—just a prohibitively large set of familiar tasks. The best way to use this compendium is to get people bearing the titles CEO/CIO-expert-manager into a room for a series of meetings. Except for the start-up, all the planning meetings follow your usual format; but at the first meeting, each job title takes on the commitment to absorb a roughly equal slice of this book and at the next meeting to distribute/discuss a typed summary of aspects of our content which are specific to your organization.

For most solutions, running this management-intensive effort under your established successful process will be a good way to proceed: You'll have the ongoing ability to triage nonessential conversions away from critical ones. And, when the inevitable bulge arises, you can divert reliable resources from non-Y2K efforts—not be forced to start inventing the wheel near the scheduled end of your path. Large organizations without an established “funnel” will want to set up a distinct (Y2K) project office.

Remember that AITP used to be named DPMA, Data Processing Management Association. Our task as IS management is — literally — to rescue our organizations. All the co-authors and editors, including the initial project sponsors at AITPOs Special Interest Group for Mainframe Computers, want you to succeed!

Dick Lefkon



Updates

Submit Errata



More Information



InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Privacy Notice

Overview

Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security

Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children

This site is not directed to children under the age of 13.

Marketing

Pearson may send or direct marketing communications to users, provided that

Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
Such marketing is consistent with applicable law and Pearson's legal obligations.
Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out

Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

As required by law.
With the consent of the individual (or their parent, if the individual is a minor)
In response to a subpoena, court order or legal process, to the extent permitted or required by law
To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
To investigate or address actual or suspected fraud or other illegal activities
To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links

This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020

Email Address

Year 2000: Best Practices for Y2K Millennium Computing

Book

About

Features

Description