Conference bulova::decw_jan-89_to_nov-90

    The device driver macro definitions were inadvertently left off the
    V5.1 kit. I'll forward this to someone who might be able to get you
    the right bits.

    Re : .1

>   The device driver macro definitions were inadvertently left
>   off the V5.1 kit.

    How can we get the definition file(s) please ?
    [ "We" = customers as well as myself ]

    Thanks
    Frank

The driver definitions are in sys$library:decw$driver.mlb provided by the decwindows v2 kit. - Bill

    Yes, but that isn't the official route for getting the stuff to
    existing v1 customers, is it.
    
    Take it up through the escalation paths to CSSE...
    
    - ���

    Re : .3   Bill, thanks for the information.

    Re : .4

    Andy,

      I'm aware of the normal escalation paths and I have an SPR ready to
    send but for two points :

      1) Several products specify that "Thou shalt not submit SPRs on
         known problems" in their support plans, I doubt that DECwindows
         is any different. This is a known problem. It will be fixed.

      2) It will do no good for anyone to return an SPR closure of "Thank
         you for your continued interest in Digital products. The problem
         you have reported will be corrected in the  next release of this
         product". That would be the expected (and fairly understandable)
         response.

      I don't particularly want to fend off this call for the customary 60
    days just to hand over a totally useless "answer" at the end of that
    time.

      The SPR I have written includes the request to ship the .MLB to this
    customer and such others that require it until v2 is released. I believe
    that is a reasonable solution but wanted to sound out the problem in
    case there is provision for this already.

    Thanks,
    Frank

    [ Have also referenced this in DECWINDOWS_PROGRAMMING ]

    Read my fingers: I didn't say "submit an SPR" I said "contact CSSE".
    
    - ���

    Re : .6

>   Read my fingers: I didn't say "submit an SPR" I said "contact CSSE".

    Wrong. You said "Take it up through the escalation paths to CSSE..."
    
    The escalation paths are CLDs (for particularly critical calls) and
    SPRs for the other 95%. The only other way I contact CSSE is through
    the VMSSPT hotline and, (no offence intended) it has been less than
    useful to me in the past as the reply has been "Submit an SPR or
    CLD" after a delay. [ Please note : this is not criticism of any
    of the involved groups, merely responding to a pedantic response. ].
    That is why I try the unofficial path of Notes. That is why I ask.
    [ That is why I get ratty at Andy :-) ]

    If there is a new hotline or a similar method, please let me know.
    If there is a focus person in CSSE (US/Europe/UK/anywhere) for
    DECwindows, again, please let me know. [I can be mailed on the above
    node if it's easier than cluttering up this conference].

    Thanks
    Frank    

    Yes there is a focus person for DECWINDOWS in CSSE/VMS. His name is Bob
    (CSSE32::) Fraser.

    Andy
    CSSE/VMS

I'm the support engineer in the CSSE DECwindows Support Group.  We just became
aware of this problem this week, and that's because Bob Fraser was contacted by
someone.  In the future, if you have a bug to report and you're a CSC person,
call our hotline.  If you're not a CSC person, call your CSC, they'll call us.
We'll do our best to get you a fix.

Sometimes, a problem report will come in by mail or phone and it's something
that would require a source code fix.  We would then ask for an SPR or CLD so
that it'd get tracked and worked properly.  Proper problem escalation will get
the job done better and quicker.

I'm currently building a VMSinstal kit to provide this file.  It will be
made available to all CSCs through the normal patch distribution system (VOID).
The CSCs will, in turn, make this available to customers and internal people.
I expect to release this software on Monday, 17 July.

Bob Lembree, CSSE/VMS Support Group

    Thanks Bob,
    
    ���
    
    

I have a copy of the library (I got it from Rueven (.0)), but could not find 
it on a VMS 5.3 system.

Did the macro library make it into the 5.2/V2 distribution?