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

Conference msgaxp::optical

Title:	Optical Products

Moderator:	TAPE::SENEKER

Created:	Wed May 04 1988
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	841
Total number of notes:	3218

822.0. "Installation of 3.4 question..." by CSC32::S_WASKEWICZ () Fri Apr 18 1997 15:45

    
         Is this the manifestation of the first documented "Known Problems"
    listed in the release notes?...or
    
    I was wondering why the default is [N] no, for the question
     
    during the installation of OSMS V3.4 (Vax Direct Connect flavor):
    "* Do you want to modify this WD$STARTUP_PKx.com file [N]:"
    
    The reason I ask is, I was helping a customer install V3.4, and when
    he used the default answer of NO, reasoning was that the file
    information that was printed looked OK to us and didn't seem to need 
    modification BUT the RZ device never got configured, and he was not 
    able to answer with the RZA device we had expected to see. 
         Since I had remembered that there was this thing with
    WD$STARTUP_PKx.com in the release notes, we aborted the install, went
    back and answered YES to that question.
         When we answered Yes, we were then given a list of questions
    about the SCSI ID's, as expected, based on the same output of
    the previous WD$STARTUP_PKx.com file.
    Lo and behold, the RZ device gets configured just fine, and all is
    well.
    
    Steve

T.R	Title	User	Personal Name	Date	Lines
822.1		TAPE::SENEKER	Head banging causes brain mush	`Fri Apr 18 1997 17:50`	17
	Steve, >>> Is this the manifestation of the first ..... Yes. >>> I was wondering why the default is [N].... I only had two options Yes/No, I choose N. I was hopefully assuming that this install procedure will be the same for at least a few releases so once the customer has the proper startup file built then "N" would be the best answer. Also, if the customer did a reinstall but the WD$STARTUP_PKx.COM files didn't need changing then it would be ok. Maybe my idea did not apply well in the real world of the customer. Rob
822.2	Thanks, I appreciate your insight	CSC32::S_WASKEWICZ		`Fri Apr 18 1997 19:06`	6
	No harm done, we'll just get the message out to answer YES, and then it'll proceed correctly. Thanks for the info. Steve
822.3	Cache default changes: OSMS 3.3 to 3.4	KERNEL::CLARK	STRUGGLING AGAINST GRAVITY...	`Tue Apr 22 1997 08:28`	23
	Should I add this here or start another string? Customer upgraded to osms 3.4 on openvms axp 6.2. The jukebox appeared to configure ok on restart (all wdxxx devices online/allocated, rzxxx device also online/allocated) but JBUTIL SHOW SLOT gave "UNKNOWN JUKEBOX TYPE". The customer was unable to mount the JBAxxx devices. After a bit of digging around I found that the customer had given the default answer (4 blocks) for the cachefile size, whereas his previous installation had used 256 blocks. I deleted the 256 block cachefiles, and re-installed using the default 4 blocks. Lo and behold...everything now worked. Moral to the story: On upgrade/re-install of OSMS, set cachefile size to previous install value, or delete the '.WRK' files and use the new default (save disk space). Dave
822.4	should be JKCONFIG-E-DIFFSIZE but...	TAPE::SENEKER	Head banging causes brain mush	`Tue Apr 22 1997 14:26`	8
	Dave, Thanks for the information. I tried to reproduce what happened but my system did the proper thing, which is the error message: %JKCONFIG-E-DIFFSIZE, existing workfile different size than specified Rob
822.5	Possible information shortage!	KERNEL::CLARK	STRUGGLING AGAINST GRAVITY...	`Wed Apr 23 1997 08:39`	10
	Rob... Thanks for the feedback. I'm not sure now if the customer saw this message, as my contact with the problem was remote (Prague!). I will enquire of the local service center if that information was ever identified by the customer. Dave.