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

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

785.0. "File not found? Trying to register a DS500" by ADO75A::SHARPE (C is bliss?) Tue Mar 12 1991 05:28

$ manage/enter
DECmcc (V1.1.0)

MCC> register terminal ados01 addr=08-00-2b-09-12-42,type=ds500

Terminal_Server ADODEM_NS:.ados01
AT 12-MAR-1991 16:52:21

The requested operation cannot be completed
                      MCC Routine Error = %RMS-E-FNF, file not found
MCC>

What does this mean? ...

The DS500 seems to be the only thing the parser will accept here.

Regards
Richard Sharpe
T.RTitleUserPersonal
Name
DateLines
785.1SCRPIO::LIZBICKITue Mar 12 1991 14:2922

    Richard -

    The problem you are seeing is due to the fact that the Terminal Server
    AM attempts to create an image file for a DS500 upon registration, if
    the image file does not already exist.  It does this by copying the
    image file shipped with the DECserver 500 software (SYS$COMMON:[DECSERVER]
    DS5TSV.SYS) to the new file.  It appears to me that you do not have
    the DECserver 500 software installed on the system?
    
    The fact that the Terminal Server AM returns the error and does not
    complete the registration is a bug (it has been entered as a QAR).
    The TSAM code will be fixed in the future to complete the registration
    whether an image file was created or not.

>> The DS500 seems to be the only thing the parser will accept here.

    I don't understand what you mean by this.  Are you saying that you
    cannot register any other terminal server type?

					Lynne
785.2Help suggests that decserver_500 is the keywordADO75A::SHARPEC is bliss?Tue Mar 12 1991 22:2220
Lynne,

Thanks for your answer ... 

There is a DS200 that I can use.

>>>> The DS500 seems to be the only thing the parser will accept here.
>>
>>    I don't understand what you mean by this.  Are you saying that you
>>   cannot register any other terminal server type?
>>
>>					Lynne

What I meant here is that the help info suggests that the keyword is 
DECSERVER_500, but DS500 is the actual thing to use.

Thanks
and
Regards
Richard Sharpe
785.3SCRPIO::LIZBICKIWed Mar 13 1991 16:5214
   The keys in the online help (ie, DECSERVER_500, etc) are used to 
   contain specific information on the particular terminal server type.
   I've noticed that they are all capitalized, and I can see how this may
   lead a user to believe that these are the keyword values you can use for
   the Type attribute.  Do you think it would be helpful if the on-line help 
   displayed "DECserver_100",  etc, instead of "DECSERVER_100"?

   The correct information on values for the Type attribute can currently
   be found in the on-line help under ENTITY TERMINAL_SERVER CHARACTERISTICS 
   TYPE.  Also, they are documented in the TSAM Use document for the 
   Register directive.

						Lynne
785.4Help uses capitalization from input fileTOOK::CALLANDERFri Mar 15 1991 13:039
The on-line help is built from the .help files you supplied, or supplied
by any other AM/FM/PM writer. To change the capitalization, simply change
all references to it in the on-line .help input files.

Unluckily I can not tell from your note where this definition currently 
exists. If you specify (like it is in the NODEx help, I will put a priority
5 qar in for you suggesting that they change it and your reasoning why.

jill
785.5MCC_TS_AM.HELPSCRPIO::LIZBICKIFri Mar 15 1991 20:3310

   Jill - 

   The problem is in the Terminal Server AM on-line help.  If people think
   that the help keys DECSERVER_100, etc should be DECserver_100, etc, since
   they are not used as keywords (ie, they are not enumerated values), I
   will go ahead and have our doc writer make the change...
	
					Lynne