Conference 7.286::fddi

                            DRAFT - SALES UPDATE ARTICLE
			    ============================    
    Contact:  George Nielsen
              226-5510
              DELNI::G_NIELSEN
              LKG1-2/W06
    
    SUBJECT:  DEC FDDIcontroller 700 DEFZA-CA Retires
    
    Effective immediately, the DEC FDDIcontroller 700 (DEFZA-CA) is retired,
    that is, moved to maintenance only.   


						  Last	    Last
						  Order	    Ship
    Model No.	Description			  Date	    Date    Migration
    ---------	------------------------------  --------  --------- ---------

    DEFZA-CA    TURBOchannel to FDDI Adapter	1-APR-94  24-JUN-94   (1)
		supporting STP and TW copper
		medias.

    NOTES: 

    Every effort must be made to redirect all FDDI copper media requirements
    to the DEFTA-UA which supports the ANSI Std Unshielded Twisted Pair
    (UTP) CAT 5 copper PMD Standard.

    It should be understood that due to a limited supply of on-the-shelf
    DEFZA-CAs (no additional units can be built), every effort must be
    made to update all outstanding quotations to reflect the DEFTA-UAs 
    instead of the DEFZA-CAs.  All new FDDI copper requirements must be
    satisfied with the DEFTA-UA.

    Remember, the DEFTA-UA utilizes DMA transfers on both transmit and 
    receive, whereas, the DEFZA-CA only utilizes DMA transfers on receive.  
    In terms of system overhead, particularly in server applications, the 
    DEFTA-UA provides superior performance.  

	No DEFZA-CA quotes should be issued without first verifying 
	product availability.

	No DEFZA-CA orders should be entered without first verifying
	product availability.

    The DEFTA-UA can be used with the new DEF6U Six Port DEChub 900
    module, as well as, other ANSI FDDI UTP PMD Compliant concentrator, 
    hub, or switch product.

    The DEFTA-UA operating system support will become available in April.
    Contact the author or specific operating system product manager for 
    details on schedules.

    

    

    Please be advised that the recently released TURBOchannel adapters:
    
    	DEFTA-AA SAS MMF
    	DEFTA-DA DAS MMF
    	DEFTA-UA SAS UTP
    
    are ONLY supported on OSF/1 at this time, and that there are MANDATORY
    OSF/1 patches required prior to using the adapters.  The patches are:
    
    Digital OSF/1 V1.3 with patches.osf-v1.3-27may94.tar.z patch kit
    Digital OSF/1 V2.0 with patches.osf-v2.0-27may94.tar.z patch kit
    Digital OSF/1 V3.0 or later
    
    Use of the -AA/-DA/-UA on any other operating system can result in
    unreliable operation, including data corruption.
    
    OpenVMS and ULTRIX have not yet committed to providing patches.  Feel
    free to harass them directly.  Current discussions suggest DEC-94.
    
    Also, Dennis Majikas has assumed product management for the TURBOchannel 
    FDDI adapters - SCHOOL::MAJIKAS
    
    Regards
    
    George

Hi!
	We're now 4 months later.  Any update on when patches will be available
for OpenVMS?

	Also, can someone fill me in on why, according to the OpenVMS SPD,
DEFTA's are not supported on Model 700 and 900 systems?  The SPD claims that the
DEFZA is.  Isn't the DEFZA end-of-life at this point?

	If this is a "because it hasn't been qualified yet" issue that's fine as
I need this configuration to test DECnet/OSI.  As long as I can plug it onto the 
TurboChannel connector and it is the right form factor I should be all set.
Provided I can also get the required patches for VMS...

	Thanks!
		David

    Try contacting Linda Duffell at STAR::DUFFELL.  I know she works on the
    OpenVMS drivers for DEFEA and DEFPA, so she probably knows about DEFTA
    support.
    
    /l

>>	We're now 4 months later.  Any update on when patches will be available
>>for OpenVMS?

The DEFTA/DEFEA drivers in V6.2 expected to ship Feb '95 have the workaround
to do unaligned buffer copies for transmit requests for those revisions of the
DEFTA/DEFEA afflicted with the early version of the cost-reduced PDQ chip.

This same driver (DEFTA only) built for V6.1 is in qual.  This hasn't been
a big priority but its in progress and I expect it will be available as a
TIMA kit in about a month.  Meanwhile, I'll be happy to give out this driver.

>>	Also, can someone fill me in on why, according to the OpenVMS SPD,
>>DEFTA's are not supported on Model 700 and 900 systems?  The SPD claims that the
>>DEFZA is.  Isn't the DEFZA end-of-life at this point?

The DEFTA is supported.  The SPD should be updated.

- Dick

re -.1 hi Dick,

>This same driver (DEFTA only) built for V6.1 is in qual.  This hasn't been
>a big priority but its in progress and I expect it will be available as a
>TIMA kit in about a month.  Meanwhile, I'll be happy to give out this driver.

it's been a month and I can't find the driver kit in tima. Several defta-ua
have been sold here for AlphaStations and we need the driver for AXP VMS 6.1.

greg

    
    ANY NEWS?
    I'm also having a customer with DEFTA-UA problems on VMS AXP 6.1
    A pointer to the new driver (VMS 6.2) would be highly appreciated.
    
    thanks eva
    

For Alpha VMS, the name of the TIMA kit is AXPLAN02_061 although it
appears that this has been superceded by a later one called AXPLAN03_061.
This contains SYS$FCDRIVER.EXE with support for all flavors of the DEFTA.
V6.2 has complete support as well.

For VAX VMS, the DEFTA-FA is the only module supported primarily because
the autoconfiguration code only recognizes the device type for the DEFTA-FA.
The driver would also need to be updated to provide support for the modified
PDQ chip on the DEFTA variants and that driver is not ready.  It is planned
to be done sometime in calendar year 1995.

Dick Stockdale
VMS LAN drivers

    
    Any update ?
    
    When will OpenVMS VAX support the DEFTA-AA ?
    
    Thanks,
    EG
    

An update would be appreciated!!!

    
    When will OpenVMS VAX support the DEFTA-AA ?
    
	Also, will it ever work with VMS 5.5-2?

thanks

rick
    

This is an unofficial patch file that should allow use of the DEFTA-AA,
DEFTA-UA, DEFTA-DA in VAX systems running VAX/VMS version V6.0, V6.1,
V6.2, V7.0.

$!
$! VAX/VMS DEFTA driver patch to add support of DEFTA-AA, DEFTA-UA, DEFTA-DA.
$!
$!                VAX/VMS Version V6.0, V6.1, V6.2, V7.0
$!
$! +------------------------- IMPORTANT NOTE ---------------------------+
$! |                                                                    |
$! |      Requires DEFTA-AA, DEFTA-UA, DEFTA-DA with fixed PDQ chip.    |
$! |                                                                    |
$! |      Using the existing DEFTA driver without a fixed PDQ chip      |
$! |      result in undetected data corruption.  This is not just a     |
$! |      chance of data corruption - it is a guarantee of data         |
$! |      corruption.  You MUST verify that the PDQ chip is the         |
$! |      correct version.                                              |
$! |                                                                    |
$! |      The fixed PDQ chip is the large chip on the module labelled   |
$! |      DC7223 with a Digital part number just above the chip number. |
$! |      The part number is 21-34812-04.  The previous version was     |
$! |      21-34812-03.                                                  |
$! |                                                                    |
$! +--------------------------------------------------------------------+
$ TYPE SYS$INPUT

This patch command file patches:

    SYS$LOADABLE_IMAGES:SYSLOA46.EXE
    SYS$LOADABLE_IMAGES:SYSLOA49.EXE

This allows the DEFTA-AA, DEFTA-UA, DEFTA-DA to be recognized by
VAX/VMS autoconfiguration.

The following versions of the DEFTA are supported by FCDRIVER.EXE:

  DEFTA-FA, all versions
  DEFTA-AA, only versions with PDQ chip 21-34812-04 and later.
  DEFTA-UA, only versions with PDQ chip 21-34812-04 and later.
  DEFTA-DA, only versions with PDQ chip 21-34812-04 and later.

  The fixed PDQ chip is the large chip on the module labelled
  DC7223 with a Digital part number just above the chip number.
  The part number of the fixed chip is 21-34812-04.  The previous
  version was 21-34812-03.

$ ver = "''f$getsyi("version")"
$ ver = f$edit(ver,"COMPRESS,TRIM")
$ set def sys$loadable_images:
$ if ver .eqs. "V6.0" then goto patchv60
$ if ver .eqs. "V6.1" then goto patchv61
$ if ver .eqs. "V6.2" then goto patchv62
$ if ver .eqs. "V7.0" then goto patchv70
$ write sys$output "? Patch is valid only for V6.0, V6.1, V6.2, V7.0"
$ exit
$ patchv60:
$ patch sysloa46.exe
verify/inst 0ce0+206-30
"movl #08,r2"
exit
dep/byte .+1=06
e/i .-1
update
exit
$ patch sysloa49.exe
verify/inst 0b48+206-30
"movl #08,r2"
exit
dep/byte .+1=06
e/i .-1
update
exit
$ exit
$ patchv61:
$ patchv62:
$ patchv70:
$ patch sysloa46.exe
verify/inst 0ce0+206
"movl #08,r2"
exit
dep/byte .+1=06
e/i .-1
update
exit
$ patch sysloa49.exe
verify/inst 0b48+206
"movl #08,r2"
exit
dep/byte .+1=06
e/i .-1
update
exit
$ exit

    Re .12
    
    Is it possible to make a patch version for VMS 5.5-2 ?
    One of my customer need to stay on 5.5-2 and they have bought
    the DEFTA-AA
    
    Thanks
    Sunny

I assume the customer is running V5.5-2H4 since V5.5-2 doesn't have DEFTA
support at all.  Here is an updated patch.  You might have to edit it to
modify the version that is being checked for as I'm not sure what version
string is returned by the GETSYI for V5.5-2H4.

- Dick

        ======================================================

This is an unofficial patch file that should allow use of the DEFTA-AA,
DEFTA-UA, DEFTA-DA in VAX systems running VAX/VMS version V5.5-2H4, V6.0,
V6.1, V6.2, V7.0.

$!
$! VAX/VMS DEFTA driver patch to add support of DEFTA-AA, DEFTA-UA, DEFTA-DA.
$!
$!            VAX/VMS Version V5.5-2H4, V6.0, V6.1, V6.2, V7.0
$!
$! +------------------------- IMPORTANT NOTE ---------------------------+
$! |                                                                    |
$! |      Requires DEFTA-AA, DEFTA-UA, DEFTA-DA with fixed PDQ chip.    |
$! |                                                                    |
$! |      Using the existing DEFTA driver without a fixed PDQ chip      |
$! |      result in undetected data corruption.  This is not just a     |
$! |      chance of data corruption - it is a guarantee of data         |
$! |      corruption.  You MUST verify that the PDQ chip is the         |
$! |      correct version.                                              |
$! |                                                                    |
$! |      The fixed PDQ chip is the large chip on the module labelled   |
$! |      DC7223 with a Digital part number just above the chip number. |
$! |      The part number is 21-34812-04.  The previous version was     |
$! |      21-34812-03.                                                  |
$! |                                                                    |
$! +--------------------------------------------------------------------+
$ TYPE SYS$INPUT

This patch command file patches:

    SYS$LOADABLE_IMAGES:SYSLOA46.EXE
    SYS$LOADABLE_IMAGES:SYSLOA49.EXE

This allows the DEFTA-AA, DEFTA-UA, DEFTA-DA to be recognized by
VAX/VMS autoconfiguration.

The following versions of the DEFTA are supported by FCDRIVER.EXE:

  DEFTA-FA, all versions
  DEFTA-AA, only versions with PDQ chip 21-34812-04 and later.
  DEFTA-UA, only versions with PDQ chip 21-34812-04 and later.
  DEFTA-DA, only versions with PDQ chip 21-34812-04 and later.

  The fixed PDQ chip is the large chip on the module labelled
  DC7223 with a Digital part number just above the chip number.
  The part number of the fixed chip is 21-34812-04.  The previous
  version was 21-34812-03.

$ ver = "''f$getsyi("version")"
$ ver = f$edit(ver,"COMPRESS,TRIM")
$ set def sys$loadable_images:
$ if ver .eqs. "V5.5-2H4" then goto patchv552h4
$ if ver .eqs. "V6.0" then goto patchv60
$ if ver .eqs. "V6.1" then goto patchv61
$ if ver .eqs. "V6.2" then goto patchv62
$ if ver .eqs. "V7.0" then goto patchv70
$ write sys$output "? Patch is valid only for V5.5-2H4, V6.0, V6.1, V6.2, V7.0"
$ exit
$ patchv552h4:
$ patch sysloa46.exe
verify/inst 0bd0+204
"movl #08,r2"
exit
dep/byte .+1=06
e/i .-1
update
exit
$ patch sysloa49.exe
verify/inst 0b80+204
"movl #08,r2"
exit
dep/byte .+1=06
e/i .-1
update
exit
$ exit
$ patchv60:
$ patch sysloa46.exe
verify/inst 0ce0+206-30
"movl #08,r2"
exit
dep/byte .+1=06
e/i .-1
update
exit
$ patch sysloa49.exe
verify/inst 0b48+206-30
"movl #08,r2"
exit
dep/byte .+1=06
e/i .-1
update
exit
$ exit
$ patchv61:
$ patchv62:
$ patchv70:
$ patch sysloa46.exe
verify/inst 0ce0+206
"movl #08,r2"
exit
dep/byte .+1=06
e/i .-1
update
exit
$ patch sysloa49.exe
verify/inst 0b48+206
"movl #08,r2"
exit
dep/byte .+1=06
e/i .-1
update
exit
$ exit

    Thanks a lot.
    
    Sunny

A customer has got an DEFTA-UA (for his DEC3000) and mentioned that it came with
a piece of paper saying that it required OpenVMS/Alpha V6.1-1H2 for proper
operation and also that it would not work with V6.2.

This is in contradiction to .9, which says:

� For Alpha VMS, the name of the TIMA kit is AXPLAN02_061 although it
� appears that this has been superceded by a later one called AXPLAN03_061.
� This contains SYS$FCDRIVER.EXE with support for all flavors of the DEFTA.
� V6.2 has complete support as well.

Can anyone resolve this confusion ?

Thanks in advance,
Hans.

.9 is correct.

- Dick

    Hi there, 
    
    I have some MCS guys complaining that the patch in 1221.12 , 1221.14 is not
    "official" and they therefore don't want to use it, which is causing
    much nashing of teeth amoung the sales team dealing with it. Why is the
    patch unofficial, are there any official ones in the meantime, does it
    work okay?
    
    Thanks for any info.
    
    Kevin Mannerings
    ESSC Galway dtn 822 4320

>>Why is the patch unofficial, are there any official ones in the meantime, does it
>>work okay?
    
Its unofficial because the real fix will not be VAX/VMS until V7.1.

There are no official ones in the meantime and the probability that there
will be one before V7.1 is about as close to nil as you can get.  If someone
doesn't want to use it, they can wait or obtain a DEFTA-FA.

It works, assuming that the version of the PDQ chip is really verified (if it
isn't verified, the result is undetected data corruption).

Customers are better off with the fixed modules (as described in the patch)
because of the performance implications of a driver workaround.

- Dick

    Does anybody has a list of references where we have already implemented
    this unofficial patch ?
    
    It seems a bit tricky to implement this patch in a production
    environment. If we have a problem due to the patch, who will take the
    responsibility ?

>>    It seems a bit tricky to implement this patch in a production
>>    environment. If we have a problem due to the patch, who will take the
>>    responsibility ?

The solution then is to use DEFTA-FA modules which don't need the patch.  Or
wait until V7.1 comes out.

- Dick