Item Subject: Message text
> I've been trying to stay out of this one...but I can't keep my fingers
> shut.  I was at that same IPROF meeting.  All the issues were aired.
> There wasn't consensus in the room among the SIGSYSMAN members as to what
> the ideal solution would be.  Several people thought HP had a resonable
> position to defend.  So, based on the input in that meeting, some decisions
> were changed and a new policy was drafted.  The most productive discussion
> at this point would be to identify the problems with the password process
> (as several posters have pointed out) and to try to get them fixed.  Why
> rehash the same issues that were raised at IPROF?  If the owners of this
> policy weren't swayed during IPROF (when they were fairly well blasted
> by the audience), I don't think there's much hope of them changing their
> minds now.
 
Wearing my SIG/SysMan chairman's hat:
 
I agree with what Mike has posted above.  We did come to an agreement last year
which respected HP's interest in their diagnostics, while still allowing access
to the diagnostics for customers who are paying HP support.
 
The only exceptions I'm aware of at this time are:
 
1) IOTT doesn't work even with the diagnostic password.
 
2) Although the codeword procedure is a pain, there was agreement to work
towards an easier way.  Perhaps keying the diagnostics off of the HP Predictive
Support password, which is automatic.
 
As far as the post from Stan earlier, I am unable to confirm any restriction in
using ODE/MAPPER in place of IOMAP.  I just tried it on one of my 9x8 systems
running X.50.20 with no problem.
 
If there are any other concerns which are not highlighted, please let me know
since I'm following up on this mid-February with some WCSO folks.
 
Regards,
/isaac