ATM and SST Year 2000
Compliance
|
| Product code | Name | Version | Year 2000 ready | Change |
| BFVE026-0000 | NCR ISO-async licence |  |
July 10, 1998 | |
| BFVE026-S03E | NCR ISO-async (M+D) - EV | |
July 10, 1998 | |
| BFVE066-S03E | DAM software (full function) | |
July 10, 1998 | |
| BFVE067-S03E | DAM software (strict version) | |
July 10, 1998 | |
| BFVE079-0000 | Logigab gener. (L+M+D) V2/V1 migration | |
July 10, 1998 | |
| BFVE080-0000 | Logigab generator (L+M+D)- V2 | |
July 10, 1998 | |
| BFVE090-0000 | Telecom procedure for XMEM-S0 (licence) | |
July 10, 1998 | |
| BFVE090-S03E | Telecom procedure for XMEM-S0 (M+D) | |
July 10, 1998 | |
| BFVE090-S03F | Telecom procedure for XMEM-S0 (M+D) | |
July 10, 1998 | |
| BFVE101-0000 | IconAuthor-OS2 | |
||
| BFVE102-0000 | IconAuthor Windows-NT | |
||
| BFVE107-0000 | Basic Software DOS licence | |
July 10, 1998 | |
| BFVE107-S23E | Basic Software REL 4.2 (M+D) | |
July 10, 1998 | |
| BFVE107-S33E | Basic Software DOS V4.02.03 (M+D) | |
July 10, 1998 | |
| BFVE107-S43E | Basic Software DOS V4.02.04 (M+D) | |
July 10, 1998 | |
| BFVE109-S23E | Autoconfiguration tool (M+D) | |
||
| BFVE109-S23F | Autoconfiguration tool (M+D) | |
||
| BFVE112-0000 | PSAB SST applic.builder L+M+D | N/A (1) | Oct. 12, 1998 | |
| BFVE115-AA00 | Remote Loading On PC (licence) | (2) |
Oct. 12, 1998 | |
| BFVE115-SAAE | Remote Loading On PC (M+D) | No (3) | Oct. 12, 1998 | |
| BFVE115-SAAF | Remote Loading On PC (M+D) | No (3) | Oct. 12, 1998 | |
| BFVE122-0000 | TCP/IP licence | |
||
| BFVE122-S0AE | TCP/IP (M+D)- EV | |
||
| BFVE122-S0AF | TCP/IP (M+D) -FV | |
||
| BFVE140-0000 | Basic Software DOS (licence )- V2-02 Minicash/Miniprint | |
||
| BFVE140-S23E | Basic Software DOS (M+D) EV - V2-02 | |
||
| BFVE150-0000 | Logigab Applications Generator (L+M+D) | No (3) | Oct. 12, 1998 | |
| BFVE156-0000 | OAK configurator (L+M+D) | |
||
| BFVE168-0000 | OAK basic appli services (LIC) | |
||
| BFVE168-S03E | OAK basic appli services . (L+M+D)EV | |
||
| BFVE168-S03F | OAK basic appli services . (L+M+D)FV | |
||
| BFVE169-0000 | OAK dialog generator (LIC) | |
||
| BFVE169-S03E | OAK dialog generator (L+M+D)EV | |
||
| BFVE171-0000 | OAK WAN/V24 (L+M+D) EV | |
||
| BFVE172-0000 | OAK WAN/V32 (L+M+D) EV | |
||
| BFVE173-0000 | OAK WAN/ISDN (L+M+D) EV | |
||
| BFVE174-0000 | OAK LAN/Ethernet (L+M+D) EV | |
||
| BFVE175-0000 | OAK communications services (LIC) | |
||
| BFVE176-0000 | Basic Software OS/2 - licence V1-02 | |
||
| BFVE176-S03E | Basic Software OS/2 (M+D) V1-02 | |
||
| BFVE177-0000 | Basic Software OS/2 - licence V2-00 | |
||
| BFVE177-S03E | Basic Software OS/2 (M+D) V2-00 | |
||
| BFVE300-S03E | WNT Basic Software | |
July 10, 1998 | |
| BFVE301-S03E | WNT OAK IconAuthor | |
July 10, 1998 | |
| BFVE304-S03E | WNT OAK Basic Application Service Providers | |
July 10, 1998 | |
| BFVE305-S03E | WNT OAK WOSA/XFS Service Providers | |
July 10, 1998 | |
| BFVE306-S03E | WNT OAK Transactional Dialog Generator | |
July 10, 1998 | |
| BFVE307-S03E | WNT OAK WAN/V24 | |
July 10, 1998 | |
| BFVE308-S03E | WNT OAK WAN/ISDN | |
July 10, 1998 | |
| BFVE309-S03E | WNT OAK LAN/Ethernet | |
July 10, 1998 | |
| EXSE001-0000 | OS/2 WARP | 3.0 | No (4) | Update |
| EXSE002-0000 | WINDOWS NT | 4.0 | (5) |
Update |
| EXSE003-0000 | WINDOWS NT | 4.0 | (5) |
Update |
| SUC2123-101 | SNA-SDLC procedure (M+D) | |
||
| SUC2123-202 | SNA-SDLC procedure (M+D) | |
||
| SUC2124-101 | SNA-X25 procedure (M+D) | |
||
| SUC2124-202 | SNA-X25 procedure (M+D) | |
||
| SUC2125-101 | V2 X25 procedure (M+D: French) | |
||
| SUC2125-202 | V2 X25 procedure in (M+D: English) | |
||
| SUC2126-101 | V2 TGX25 procedure (M+D: French) | |
||
| SUC2126-202 | V2 TGX25 procedure (M+D: English) | |
||
| SUC2177-101 | V2 VIP7700 procedure (M+D: French) | |
||
| SUC2177-202 | V2 VIP7700 procedure (M+D: English) | |
||
| SUC2423 | SNA-SDLC procedure (license) | |
||
| SUC2424 | SNA-X25 procedure (license) | |
||
| SUC2425 | X25 procedure license | |
||
| SUC2426 | TGX25 procedure license | |
||
| SUC2477 | VIP7700 procedure license | |
||
| SUS2402 | MS-DOS | 3.3 or higher | (6) |
Update |
(1) Developpers are responsible for ensuring
that the applications they develop by means of this product (including source-code and
library) are Year 2000 ready.
(2) Ensure that the software application related to this generic licence is Year 2000
ready.
(3) The Year 2000 readiness requires a migration to a new server application available in
1Q99. For more information, please contact your local Sale representative.
(4) Year 2000 readiness requires the installation of the Fix Pack XR_W032 for WARP 3.0.
For more details, please see IBM website.
(5) Year 2000 readiness requires the installation of Windows NT 4.0 Service Pack 4
downloadable from Microsoft
website.
(6) Year 2000 ready when running in conjunction with a Year 2000 ready Bull
software application.
Index
Without frames: [ ATM and SST compliance overview | Software
applications | Communications and related software and
licences | Bull Questar 14xx | Bull Questar 24xx | Bull Questar
34xx | Athena | Atlas | Cathi | Europa | Hector | Heracles | Minicash / Miniprint / Twincash | Paris
| Ulysse | Bull Year 2000 overview
]
With frames: [ ATM and
SST compliance overview | Bull Year 2000 overview
]...and use the navigation bars.
Notice
Bull is making every effort to provide accurate and explicit
information on the Year 2000 readiness of its products. The information on this page
reflects the current results of our compliance tests and may be updated as testing
continues. Please see the Bull Year 2000 Compliance Overview for
an explanation of the terms used and our commitments.
Year 2000 Information and Readiness Disclosure Statements
Information contained on Bull past and present
Year 2000 Internet Website pages regarding products and services offered by Bull are
"Year 2000 Readiness Disclosures" as defined by the Year 2000 Information and
Readiness Disclosure Act of 1998, (The United States of America's Public Law 105-271, 112
Stat. 2386) enacted on October 19, 1998. Bull Year 2000 Internet website pages have been
and will continue to be our primary mechanism for communicating year 2000 information.
Trademarks
Any trademarks referenced in this document are the property
of their respective owners.