[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference csc32::consolemanager

Title:POLYCENTER Console Manager
Notice:Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:CSC32::BUTTERWORTH
Created:Thu Aug 06 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1541
Total number of notes:6564

1109.0. "Patch index ?" by 52336::STRATMAN (Peter Stratman @VBO) Mon Nov 27 1995 10:33

The directory PCMSVR::$1$DKB500:[ECO] which contains patches to V1.6 has been
mentionned in several notes. Could engineering or product support please
provide an index to these patches describing what problems they fix ?

Thanks,
Peter.
 
T.RTitleUserPersonal
Name
DateLines
1109.1insufficient privilege or object protection violation ???19584::JFRAZIERWhat color is a chameleon on a mirror?Wed Nov 29 1995 10:2810
Not very handy...


$dir/siz=all/date PCMSVR::$1$DKB500:[ECO]

Directory PCMSVR::$1$DKB500:[ECO]

*.*;*              insufficient privilege or object protection violation

Total of 1 file, 0/0 blocks.
1109.252621::MURODThu Nov 30 1995 09:4911
      
       Hi, Peter.

  The directory PCMSVR::$1$DKB500:[ECO] contains:

   CFS_33122   - fixed problem ACCVIO in CONSOLE MONITOR mode.

   NSI_111_SMG - fixed problem of CONSOLE MONITOR hang.


		Murod.
1109.3Re. 1109.152621::MURODThu Nov 30 1995 09:508
    
     For 19584::JFRAIZER.


   It's  O.K. now.


	Murod.
1109.4Which one idoes include the other ?48219::DEGAGEFri Dec 01 1995 07:269
	About .2 ...

The patch CFS_33122 is the most recent one .Does it mean that it includes
the patch NSI_111_SMG ?
In other words if one customer wants to have corrections of the two problems,
what does he do ??

Thanks a lot.
Marielle Degage   CSC France
1109.5You are right.52621::MURODSun Dec 03 1995 02:275
       Hi, Peter.

   You are perfectly right. Your customer may use the patch CFS_33122.

		Murod.
1109.6confused...52336::STRATMANPeter Stratman @VBOMon Dec 04 1995 07:469
    Sorry, I'm confused.

    The *111* kit contains more than 10 images, just to fix 1 bug ?

    Also, I have the impression that these kits do not follow general
    engineering rules and guidelines for patch generation. Why is this ?

    Thank you,
    Peter.
1109.7it's not a kit52621::MURODTue Dec 05 1995 03:296
   Hi, Peter.

 1. It's not a kit - it's a simple fix.
 2. The problem is related to all images. That why you have more then 10 images.

	Murod.
1109.8and the other question ?52336::STRATMANPeter Stratman @VBOTue Dec 12 1995 05:0517
Thanks, Murod.

How about my other question ? 

>Also, I have the impression that these kits do not follow general
>engineering rules and guidelines for patch generation. Why is this ?

If there is no official ECO process in use, I'd at least like to see
a file supplied with the kit saying what architecture it is used for,
what patches it includes, how it can be mixed/matched/superceded with
others, whether it is offical/supported, etc.

Hey, we're trying to support our customers' production environments with
this stuff !

Thank you,
Peter.
1109.9This is not a kit52621::MURODWed Dec 13 1995 02:527
   Peter,
 
  THIS IS NOT A KIT OR NEW ECO.
 New ECO will be released soon (end of Jan 96).
 The new ECO will follow the 204 standard.

 	Regards, Murod. 	
1109.10But...52336::STRATMANPeter Stratman @VBOThu Dec 14 1995 13:4415
    Murod,

    Ok, I understand that these are not kits or ecos. I also much appreciate
    having the "fixes ?", since they solve our very real problems.

    What I'm concerned about is that we're giving these fixes to customers
    and that some of us may do so blindly without telling customers that
    these fixes are "not so official". If there is any risk involved in
    installing them, that should be known. So an "install at your own risk"
    notice should at least be included, or some other safeguard that gets
    us out of trouble if a big bug is introduced (it HAS been known to
    happen before  :^) )...

    Thank you for your help,
    Peter.
1109.1154831::MICHIELShttp://brsadv.bro.dec.com/cockpit/Mon Jan 08 1996 06:0327
I agree with Peter that we urgently need some information on the stuff
in PCMSVR::$1$DKB500:[ECO]

Currently we find in there:

NSI_111_SMG.DIR;1    16-NOV-1995 02:52:55.00
CFS_33122.DIR;1      24-NOV-1995 04:30:44.00
CFS_119.DIR;1        18-DEC-1995 08:21:22.00
CFS_121.DIR;1        24-DEC-1995 09:14:44.00
CFS_32368.DIR;1      27-DEC-1995 09:22:05.00
CFS_125.DIR;1         1-JAN-1996 11:52:08.00


What solves what?
    
Can we give these kits/ecos/fixes to customers or is this not recommended?
    
I propose that notes is used as a channel to announce new versions 
of these kits, with a short description of the fixes implemented.
Or didn't I look on the rigth place?

    
Thanks and best regards,


Johan
    
1109.1229067::BUTTERWORTHGun Control is a steady hand.Mon Jan 08 1996 19:3011
    The reason that none of these kits are documented is because they are
    not "official kits". The savesets with the CFS prefix are named
    that way becuase that is the case number of the IPMT they are
    related to.  The goal here was to make available to the field the latest 
    and greatest bugfixes etc. to ease the load on the folks in the
    trenches that are catching the heat from customers. This precluded doing 
    a lot of the "nice" things like a list of fixes etc. Those will of course 
    be in the ECO2 kit per DEC STD 204.
    
    REgards,
       dan