Conference azur::mcc

    Dave, et.al.,
    
    Forgive what I'm sure is a stupid question, but, when I look through
    the release notes and the distribution directory, I see no reference
    to MCCDIRvvu.% (the directory installation files) which are referenced
    in the DECmcc Installation manual for version 1.1 on page 1-12.
    
    So tell me, did the director kit get rolled into MCCBMSvvu.%, is
    the documentation wrong, am I looking in all the wrong places and
    asking all the wrong people all the wrong questions or what?
    
    wiped_out_in_washington_d_c

    timf
    
    P.S. - Thanks in advance...

	The DECmcc  DIRECTOR package is a subset (smaller package) than
	the DECmcc BASIC  MANAGEMENT  SYSTEM.   Internal to Digital, it
	doesn't seem to make  sense  to have a smaller, less functional
	package available on the net.    The  cost  to  you is the same
	(free).  If you really want  the  DIRECTOR package, you'll have
	to order it from SSB.

	JCE

Following the instructions in note 3.144 yields the following results:

> dcp -iv mccnix::~ftp/pub/mccbmsmipst127.tar /kits
dcp: can't open "mccnix::~ftp/pub/mccbmsmipst127.tar", No such file or directory
> dls mccnix::~ftp/pub/mccbmsmipst127.tar
dls: directory list failed, No such file or directory
> dls mccnix::~ftp/pub/mccbms120.release_notes
dls: directory list failed, No such file or directory
> dcp -iv mccnix::~ftp/pub/mccdtkmipst127.tar /kits
dcp: can't open "mccnix::~ftp/pub/mccdtkmipst127.tar", No such file or directory

    I suppose a similar TOOK::ELM_PAK will be avialable for the ELM stuff??
    (both AM and FM)
    -- thanx,
       Guy
    

    I am having problems copying the Ultrix DECmcc V1.2 kit files from
    mccnix::~ftp/pub/*.  I am getting errors from the "dcp" copy command:
    
    "... Can't Open File ... Permission Denied"
    
    Could somone check the files and make sure they have the correct
    permissions to be copied.
    
    Thanks.
    
    Paul
    

As indicated in the kit announcement, you can not use a wildcard copy.
You must copy the kits by explicit file name.

-- Erik

    Ok, I finally was able to copy the DECmcc BMS V1.2 kits for Ultrix from
    MCCNIX::~/ftp/pub (as described in reply .167, but I could not copy the
    PAK files.  The command came back with "no such file" errors.  Are the
    PAK files still located in that same directory?  Can you verify the
    correct filenames for me.  Where else can I find the Ultrix PAKs?
    
    By the way, what is MCC FDS?  Do I need to install this kit/PAK?
    
    Paul
    

The procedure for getting PAKs changed.  See note 3.177.

FDS the TCP/IP fault diagnostic package.  It is entirely optional
(and has its own PAK)

    What about Ultrix DECmcc DTK for customers ?

    I could get the temporary PAK for the BMS none for DTK.
    To-morrow, (even though I asked this PAK in mid-July)
    the DTK license will expire for most of my customers.

    Thanks to let me know when this one will be available externally.

    Florence
    TeMIP Support Project manager
    

    I can not find the MCCTK012 kits in [MCC_KITS.MCC_V12_SSB]. Have they
    been moved else where? Regards.

From:	TOOK::L_GROSSMAN   "DTN: 226-5318"  4-SEP-1992 11:32:51.55
To:	TOOK::MINTZ
CC:	
Subj:	RE: I: note 3.194 - looking for kits (was the toolkit ever there?)


The mcctk012 kits will not be placed in ppinc::dua0:[mcc_kits.mcc_v12_ssb]
until it officially goes to SSB.

				Larry

Tried twice to copy this file and got the same results both times:

COPY PPINC::DUA0:[MCC_KITS.EMS_V22_SSB]*.L DISK$APPL2:[KITS.MCCEMS]*/NOTIFY
%SYSTEM-F-FORCEDERROR, forced error flagged in last sector read

Directory DISK$APPL2:[KITS.MCCEMS]

MCCEMS022.L;2          2624/3168

Total of 1 file, 2624/3168 blocks.

You might want to double check your disk...

I created a new version of ppinc::mcc_public:[ems_v22_ssb]mccems022.L

I will log a field service call if this happens again.

I logged a Field Service call for PPINC for as soon as possible.

PPINC will therefore be unavailable some in the next day or two!

Once the device is fixed I will make sure all the savesets are
again readable.

    The ELM pak is due to expire, per the last note.
    
    I have done a dump of this note, to try and find where I send mail for
    this specific PAK.  There's TK, EMS, etc., etc., etc.  I am not a
    network or MCC guru, so all these names look alike to me.  It's bad
    enough that the license expire on a regular and very annoying basis,
    requiring re-installation.  But it's worse when I have to expend
    considerable time hunting for the different and individual accounts
    listed in this conference and figure out who I contact for a new
    license.  And I'm on the same net segment as the MCC system, so I have
    fast access.  Those folks in GIA must really have a problem...
    
    Please, would you start a separate note to list all accounts for PAKS? 
    Give the e-mail address for requesting each PAK by product?

    re. .199
    
    If you are looking for a PAK for internal use you can get it
    off of VTX.
    
    The temporary PAKs were for external sites to give them ELM before it
    was available from SSB.  As ELM is now available from SSB you
    shouldn't have any need for the temporary PAKs.        
    
    Regards,
    
    Bob

    The vms kit is protected
    
    dir PPINC::DUB0:[MCC_KITS.MCC_V12_MUP]
    
    Directory PPINC::DUB0:[MCC_KITS.MCC_V12_MUP]
    
    *.*;*              no privilege for attempted operation
    
    Total of 1 file, 0 blocks.
    

    Hi all,
    	can someone check the security setting on :
    		PPINC::DUB0:[MCC_KITS.MCC_V12_MUP]
    
    I've just tryed to copy the new kit but ... no access :
    
  >  $ dir PPINC::DUB0:[MCC_KITS.MCC_V12_MUP]MCCDIR012.A
  >  %DIRECT-E-OPENIN, error opening
  >  PPINC::DUB0:[MCC_KITS.MCC_V12_MUP]MCCDIR012.A;*
  >  as input
  >  -RMS-E-PRV, insufficient privilege or file protection violation
    
    		thanks' & bye
    			Stefano
   

    I don't know what the problem is with the BMS kit on PPINC but
    there is a BMS 1.2.3 kit location in Europe in case anyone wants to
    heat up the link over the weekend.
    
    

The problem with the BMS V1.2.3 kit is not with the bits on PPINC;
rather, there are problems in the installation.  There is some
discussion of these problems in other notes in the conference.

Please do not propogate any kits you have any further; it will make
it hard for us to track which kit is where.

-- Erik

    Regarding note 3.202.  Is the problem with BMS 1.2.3 limited to the 
    installation?  The reason I ask is I have  installed BMS V1.2.3, ELM AM 
    1.2.1 and TSAM 1.0.2 on a system that I'll be using for a customer demo.
    I have limited time available to do a reinstall but, I don't want
    any surprises during the demo.
           
    Do I have to reinstall if everything looks functional?  
    

On VMS, the problem was limited to the upgrade feature of the
installation procedure.  If your installation looks OK, you
should not need to re-install.

    Please check is seems not completely available (D to F) ...
    
Directory TENERE::EMA$PUBLIC:[KIT_V12]

MCCBMS012.A;3            738/738      7-NOV-1992 08:41:22.00      [0,0]    
MCCBMS012.B;3           1458/1458     7-NOV-1992 08:41:45.00      [0,0]    
MCCBMS012.C;3          17216/80280    7-NOV-1992 08:42:56.00      [0,0]    
MCCBMS012.D;3              0/1026     7-NOV-1992 09:10:11.00      [0,0]    
MCCBMS012.E;3              0/3186     7-NOV-1992 09:10:35.00      [0,0]    
MCCBMS012.F;3              0/1224     7-NOV-1992 09:12:24.00      [0,0]    
MCCBMS012.G;3              0/2862     7-NOV-1992 09:13:39.00      [0,0]    

Total of 7 files, 19412/90774 blocks.
    
    Cheers,
    	~~Gabus~~

    
    
    
    	Gabus,
    
    
    
    	I restarted a spool on .c,.d,.e,.f,.g.
    
    
           Thanks for the indication
    
    
    			Catherine
    		

    I started a copy a  few days ago when the kit was announced again and
    just went to use it and found that I had received all of the .A and .B
    files, about 100 blocks short of the entire .C file, and none of
    .D, .E, .F, and .G.
    
    The error message in the top version of the FTSV log file was "Data
    Overrun" and retries exceeded.
    
    I just started the copy again.  It copied the first file and got a data
    overrun error early in the second file.  I released the job and it is
    going again.
    
    Is everything ok on PPINC?

If you Spool a kit you might want to try more retries than the default.  Our
area (area 4) is very buisy at times. Also it should be better overnight.

    The failure the other day would have been over a few nights before it
    gave up.
    
    It just happened to me again.  It got to block 80192 out of 80280 on
    the .C file and would not go past.  The job went to PAUSED each of
    about 5 tries with:
    
    	%FTSV-E-READERR, error reading PPINC::DUB0:[MCC_KITS.MCC_V12_MUP]MCCBMS012.C;3
    	-RMS-F-SYS, QIO system service request failed
    	-SYSTEM-W-DATAOVERUN, data overrun
    
    I finally reduced the network block count on my system before releasing
    the job again and it proceded - ie:
    
    	$ set rms/net=3/system
    
    I have it set /net=127 normally.
    
    I think something must be wrong on PPINC.

I am also getting the same error as .29 when I try to copy the EMS kit.  
Unfortunately, I cannot set the RMS (no privs).  Any assistance would be 
most appreciated.

Regards,
Chip

Hi,

Can anyone tell me where I can find a "DECMCC-BMS" license for installing
the DECMCC BMS V1.2.3 on an Ultrix system. I've searched the lkg database
and cannot find it.

Is "DECMCC-BMS" the license I need, or does it have another name ?

Thanks for any help you can give me,

Cheers,

jvg...

According to note 3.199, VTX PAK should provide you with a DECMCC-BMS PAK.

Hi,

As documented in 3.205 I have sent mail to PPINC::BMS_PAK requesting a PAK for
Polycenter Network Manager 200 (DECmcc BMS). After 24 hours no response - can I
use my existing V1.2 DECmcc BMS paks to run V1.3?

Ian Pratt

PPINC, which hosts both the PAK mailer and the kits, has been overwhelmed with 
requests in the last 24 hours.  So badly that we can't even log in to
re-tune the system.  If it does not settle down shortly, the system
will be taken down briefly to re-adjust.

No, V1.2 PAK will not work with T1.3 code.

-- Erik

    When you send out the PAKS (.-1, PPINC::BMS_PAK), why not send them
    in the form of an executeable command file?  

Attempting to install the T1.3 kit, I got the following notice:
                            WARNING

   DECmcc T1.3.0 requires at least Motif V1.1.3

   All windowing interfaces to DECmcc will not function
   normally and will not be supported.

I aborted the installation, since it's not clear whether I could install Motif
afterward.  My questions:

- can I install DECmcc and then upgrade to Motif when I find the kit?
- can you provide a pointer to the kit (I've found a couple labelled
	DECW$MOTIF011, but don't know if that's 1.1.3 or greater)
- why isn't this in the Release Notes (if not the installation guide)?

If does not matter if you install motif before or after installing the kit.
The important thing is that it is installed BEFORE running the Iconic Map
V1.3.

The VMS kit for internal folks is at bulova::decw$public:[decw$motiff011.kits].

This kit is for the Digital product VMS DECwindows Motif V1.1 which is
equivalent to the OSF product OSF/Motif V1.1.3.

We will try to add more information to the installation guide.

Verna

Hi,
	I cannot seem to finsd the ULTRIX kit in the place
specified in the note with the pointer.

# ftp beacon.lkg
Connected to beacon.lkg.dec.com.
220 beacon.mcc.dec.com FTP server (ULTRIX Version 4.1 Sat Jul 25 03:22:50 EDT 1.
Name (beacon.lkg:sdj): anonymous
331 Guest login ok, send ident as password.
Password:
230 Guest login ok, access restrictions apply.
ftp> cd pub
550 pub: No such file or directory.
ftp> get pub/mcrbmst130.tar mcrbmst130.tar
200 PORT command successful.
550 pub/mcrbmst130.tar: No such file or directory.


Help please

Cheers Simon....

Check note 3.205 again; there was a correction posted.
The files are in beacon:~ftp; you don't need to specify the "pub".

    Was the DECelms point product taken out when ELM AM and ELM FM were
    added to DECmcc/VMS?
    
    If a customer wants DECelms and is licensed for EMS, can they get it
    free of charge?
    
    -Thanks,
     Dan

    
    I've installed the Alarm manager from note 3.206 on my system running
    DECmcc v1.2 (The release notes don't mention the minimum version of
    DECmcc needed, point 14 on page 4 is not so clear).
    During installation I got some errors, but the installation and IVP
    were succesfull.
    If I now try to start the alarm manager with '$mc mcc_alarm_mgr' I get
    the following error:
    
    BHT362> mc MCC_ALARM_MGR.EXE
    %DCL-W-ACTIMAGE, error activating image DECW$XLIBSHR
    -CLI-E-IMGNAME, image file
    BHT362$DKA300:[SYS0.SYSCOMMON.][SYSLIB]DECW$XLIBSHR.E
    XE
    -SYSTEM-F-SHRIDMISMAT, ident mismatch with shareable image
    
    The installation log is listed below:
    
The following products will be processed:

  MCCALMMGR V1.0


        Beginning installation of MCCALMMGR V1.0 at 17:08

%VMSINSTAL-I-RESTORE, Restoring product save set A ...
%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.

   ************************************************************
   *                                                          *
   *               DECmcc Alarm Manager IFT0.3                *
   *                                                          *
   *                  DECmcc Option Package                   *
   *                                                          *
   * * Enter a `?` at any prompt for additional information * *
   ************************************************************



* Do you want to run the DECmcc Alarm Manager IVP after installation [YES]?


The Dictionary update lasts approximately 60-75 Minutes

* Do you want to update the DECmcc Dictionary [YES]?

If this is a new installation, a dictionary load can be used
instead of an update, reducing the load to 5-10 Minutes.


* Is this a new installation [NO]? y

The Help File update lasts approximately 5-10 Minutes

* Do you want to update the DECmcc Help File [YES]?

   The files will now be copied to the appropriate directories
   and help and dictionary files updated.

   These updates can be done on the MCC_COMMON or MCC_SPECIFIC
   dictionary and help files. The default is to use the search
   list defined by MCC_SYSTEM to check for specific and then
   common versions of these files.
    

* Which files should be updated [MCC_SYSTEM]:


   VMSINSTAL asks no additional questions.


   Updating DECmcc dictionary and parse tables
          (5-10   minutes for new installation)
          (60-75  minutes for updates)


   Updating DECmcc help files (5-10 minutes)

DECmcc Help File Builder
Component Version:  V1.2.0

Cleaning up any intermediate files...
Processing file VMI$ROOT:[MCC]MCC_ALARMS_FM.HELP
Processing file VMI$ROOT:[MCC]MCC_ALARM_MGR.HELP
Processing file VMI$ROOT:[MCC]MCC_BRIDGE_AM.HELP
Processing file VMI$ROOT:[MCC]MCC_CIRCUIT_AM.HELP
Processing file VMI$ROOT:[MCC]MCC_COLLECTION_AM.HELP
Processing file VMI$ROOT:[MCC]MCC_CONC_AM.HELP
PProcessing file VMI$ROOT:[MCC]MCC_DNA4_AM.HELP
Processing file VMI$ROOT:[MCC]MCC_DNA5AM_HELP.HELP
Processing file VMI$ROOT:[MCC]MCC_DOMAIN_FM.HELP
Processing file VMI$ROOT:[MCC]MCC_ENET_AM.HELP
Processing file VMI$ROOT:[MCC]MCC_EXPORTER_HELP.HELP
Processing file VMI$ROOT:[MCC]MCC_FDDI_AM.HELP
Processing file VMI$ROOT:[MCC]MCC_FDDI_FM.HELP
Processing file VMI$ROOT:[MCC]MCC_GENERAL_HELP.HELP
Processing file VMI$ROOT:[MCC]MCC_HISTORIAN_HELP.HELP
Processing file VMI$ROOT:[MCC]MCC_KERNEL_AM.HELP
Processing file VMI$ROOT:[MCC]MCC_NOTIFICATION_FM.HELP
Processing file VMI$ROOT:[MCC]MCC_PA_BRIDGE_FM.HELP
Processing file VMI$ROOT:[MCC]MCC_PA_FM.HELP
Warning - Duplicate Key: 2PAPA
Warning - Duplicate Key: 2PAPAzCHAR
Warning - Duplicate Key: 2PAPAzCHARzCOMPONENTzIDENTIFICATION
Warning - Duplicate Key: 2PAPAzCHARzCOMPONENTzVERSION
Warning - Duplicate Key: 2PAPAzSHOW
Warning - Duplicate Key: 2PAPAzSHOWzCHAR
Warning - Duplicate Key: 2PAPAzTEST
Warning - Duplicate Key: 2PAPAzTESTzEXAMPLES
PrProcessing file VMI$ROOT:[MCC]MCC_STM_FM.HELP
Processing file VMI$ROOT:[MCC]MCC_TCPIP_AM.HELP
Processing file VMI$ROOT:[MCC]MCC_TS_AM.HELP
Sorting character cell help topics.
Sorting windows help topics.
Verifying hierarchy...
    Verifying for character cell
Unable to find parent topic <EXP_RMON>, for <ENTITY SNMP EXP_RMON statistics eth
erStatsTable STATISTICS> topic
Unable to find parent topic <RMON>, for <ENTITY SNMP RMON statistics etherStatsT
able STATISTICS> topic
    Verifying for windows
Unable to find parent topic <EXP_RMON>, for <ENTITY SNMP EXP_RMON statistics eth
erStatsTable STATISTICS> topic
Unable to find parent topic <RMON>, for <ENTITY SNMP RMON statistics etherStatsT
able STATISTICS> topic
Processing file(s)....
MCC help files updated.
MCC help files updated.
Cleaning up any intermediate files...
%VMSINSTAL-W-NOFILE, New file MCC_FDICTIONARY.LOG  does not exist.
%VMSINSTAL-W-NOFILE, New file MCC_FDICTIONARY.BPT  does not exist.
%VMSINSTAL-E-BADSPEC, File spec  MCC_DECWINDOWS_HELP.TOP  cannot be parsed
%VMSI%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

   Beginning DECmcc Alarm Manager IVP



   The IVP for DECmcc Alarm Manager will now be run.

DECmcc (V1.2.3)

DECmcc (V1.2.3)


MCC 0 ALarm Manager
AT  5-JAN-1993 17:19:27

Test Successful

DECmcc (V1.2.3)


Rule_Template DECTOWN:.template1
AT  5-JAN-1993 17:19:35
Create successfully completed.

Rule_Template DECTOWN:.template2
AT  5-JAN-1993 17:19:35

Create successfully completed.

Rule_Template DECTOWN:.template3
AT  5-JAN-1993 17:19:36

Create successfully completed.

Rule_Template DECTOWN:.template4
AT  5-JAN-1993 17:19:36

Create successfully completed.

Rule_Template DECTOWN:.template5
AT  5-JAN-1993 17:19:37

Create successfully completed.

Rule_Template DECTOWN:.template6
AT  5-JAN-1993 17:19:38

Create successfully completed.

Rule_Template DECTOWN:.template7
AT  5-JAN-1993 17:19:38

Create successfully completed.

Rule_Template DECTOWN:.template8
AT  5-JAN-1993 17:19:39

Create successfully completed.

Rule_Template DECTOWN:.template1
AT  5-JAN-1993 17:19:39

Partial registration success. Please retry later to complete the registration.
        Reason for Partial Registration = No attributes in the specified group
                                          for this entity.

Rule_Template DECTOWN:.template2
AT  5-JAN-1993 17:19:43
     Partial registration success. Please retry later to complete the registration.
        Reason for Partial Registration = No attributes in the specified group
                                          for this entity.

Rule_Template DECTOWN:.template3
AT  5-JAN-1993 17:19:45

Partial registration success. Please retry later to complete the registration.
        Reason for Partial Registration = No attributes in the specified group
                                          for this entity.

Rule_Template DECTOWN:.template4
AT  5-JAN-1993 17:19:47

Partial registration success. Please retry later to complete the registration.
        Reason for Partial Registration = No attributes in the specified group
                                          for this entity.

Rule_Template DECTOWN:.template5
AT  5-JAN-1993 17:19:49
Partial registration success. Please retry later to complete the registration.
        Reason for Partial Registration = No attributes in the specified group
                                          for this entity.

Rule_Template DECTOWN:.template6
AT  5-JAN-1993 17:19:51

Partial registration success. Please retry later to complete the registration.
        Reason for Partial Registration = No attributes in the specified group
                                          for this entity.

Rule_Template DECTOWN:.template7
AT  5-JAN-1993 17:19:53

Partial registration success. Please retry later to complete the registration.
        Reason for Partial Registration = No attributes in the specified group
                                          for this entity.

Rule_Template DECTOWN:.template8
AT  5-JAN-1993 17:19:55

Partial registration success. Please retry later to complete the registration.
        Reason for Partial Registration = No attributes in the specified group
                                          for this entity.

   DECmcc Alarm Manager Knowledge base installed.  To view installed templates
   enter the following commands:
        $ MANAGE/ENTER
        MCC>  SHOW RULE_TEMPLATE * all characteristics
        MCC>  exit


   DECmcc Alarm Manager IFT0.3 Installation Successful



   Completing DECmcc Alarm Manager IVP


        Installation of MCCALMMGR V1.0 completed at 17:19


        VMSINSTAL procedure done at 17:20



What is going wrong?
    
    -Geert-
    

    Are you running MOTIF on this system??  

    the alarm manager requires motif, I didn't even think to remember
    to state that. Sorry about that, I will update the release notes
    for the next release (due out in a few weeks).
    
    If you don't have motif I can set up a public account where you
    can play with the alarm manager remotely using a set display. If
    this would be useful please call.
    
    jill
    

    oh, and thanks for the install dump.  All of the warnings you
    received are okay. We are still cleaning up the installation
    procedures and IVP.  
    
    BTW the partial registration has to do with how the alarm manager
    FM is handling the show identifiers. This should be fixed in the
    next release so that complete registration (and show rule_template
    *) will work correctly.
    
    

    I've installed Motif v1.1 and now the Alarm manager is working.
    
    Thanks for the reply.
    
    -Geert-
    

    Hi,
    
    Is it possible to get a pointer to where the Development
    Toolkit of DECmcc FT 1.3?
    
    Thanks, 
    Orna.
    

Hi,

I can't copy the alarm manager.

>> $ spool copy PPINC::DUB0:[MCC_KITS.MCC_ALMMGR_IFT]MCCALMMGR010.A []
>> %FTSV-I-JOBID, FTSV Job-Id is 252, Job Name is FTSV_0252
>> Job FTSV_0252 (queue SYS$BATCH, entry 749) started on SYS$BATCH
>> $
>> FTSV Job 252 (FTSV_0252) finished at 09:33:02
>> COPY PPINC::DUB0:[MCC_KITS.MCC_ALMMGR_IFT]MCCALMMGR010.A DKA100:[KITS.MCC_ALARM_
>> MGR]
>> %RMS-E-PRV, insufficient privilege or file protection violation

Please set the protections right.

Thanks,

/-/	Henk.

    $ dir/siz/dat PPINC::DUB0:[MCC_KITS.MCC_ALMMGR_IFT]MCCALMMGR010.A
    
    Directory PPINC::DUB0:[MCC_KITS.MCC_ALMMGR_IFT]
    
    MCCALMMGR010.A;3   no privilege for attempted operation

    This protection problem has been fixed.
    
    Joe

Hi,

I've searched this notes conference, and looked at the mccnix::~ftp/pub
directory, but could not find a DECmcc DTK V1.2a (or V1.2.3). Is there
such a version for this ? If so, could you please let me know the location.

This is for a customer who is a field test site for TeMIP. He would like to
get hold of this kit before the end of this week.

Thanks,

Jack van Gorkum...

Not yet available, sorry.  There are some administrative problems holding
us up at the SSB, and until they are resolved we can't release the kit.

-- Erik

    Any responce to note 4.51 would be greatly appreciated. Customer is
    waiting for the latest DTK kit.
    
    Thanks,
    
    Jack...
           

    What is the DTK kit? Are you sure you are asking in the right place?
    
    Also, this is NOT the place to be asking for stuff that is holding
    up a customer. There are formal channels for that.
    
    s/rob

dcp -iv beacon::~ftp/pub/mcrbms130.tar .
dcp: can't open "beacon::~ftp/pub/mcrbms130.tar", No such file or directory

While we're about it, can you please compress the tar files to reduce
copying time across the network?

PJDM

Re .57:

>
>While we're about it, can you please compress the tar files to reduce
>copying time across the network?
>

	The tar files contain setld compatible subsets that are already 
	compressed, so compressing them would not help.

	Regards.

	Pierre.

RE: .55 - Check out the latest kit announcements in note 3.
	It includes a pointer to the toolkit (DTK).

Contact Joe (TOOK::) Oconnor for details on customer availability.

Re: .57 - Pierre is correct.  The contents of the tar file are
	already compressed.  I'll see what I can find out about
	the copy problem.

-- Erik

    
    RE: .57
    
    To use dcp to copy files from beacon you must use
    
    dcp -iv beacon::'~ftp/filename.
    
    The login directory for ftp is ftp/pub
    
    Sorry for the confusion.
    
    
    Joe

    
        MAKO1 and bhub (the systems that have the ELM kits) will be down
        Thursday afternoon and Friday (5/6 and 5/7) so they can be moved.
        They should be back up by Friday evening.
    
        Sorry for the inconvenience.
    
        -Bob

    Hi,
    
    	I saw the note in 3.237 about the notification kit for 1.3 on VMS.
    Is the ULTRIX version available ? Reason I'm asking is that the
    customer ordered it and 1.2a has arrived, not 1.3. Timescales are fairly
    tight and I was hoping to pull it off the net but cannot find it
    anywhere. Any pointers etc. would be very welcome ! 
    
    	On the same subject is it available anywhere ? The latest CD
    distribution has the 1.3 Polycenter Network Manager 200 but the
    historina/notification options are still at 1.2/1.2a. Confusing for us,
    let alone the customer !!
    
    Cheers,
    
    		Euan         

See note 5165 for discussion of the availability of this kit,
and the contents of the CDs.

-- Erik

    Just a quick note to anybody who had trouble copying yesterday
    TAY2 where beacon and ppinc are located was experiencing a lot
    of power problems.  Both systems are up now.
    
    
    Joe

    Where can the paks now be found for DECmcc (basic kit)??
    
    		Thanks  Ron
    

>    Where can the paks now be found for DECmcc (basic kit)??

For internal use you get the PAKs via VTX ISPAK. If you don't have VTX
on your machine, contact somebody who has an ALL-IN-1 account.

*Robert

Hi,

	a lot of DECnet/OSI based End-Systems are now on Easynet, which are 
	all very dependent on correct address information in the namespace.

	I have checked ANCHOR has the new address for PPINC (55.165), but
	the DNA$Node Object of that node shows the old address towers.
	So, DECnet/OSI Systems are not able to reach PPINC using its name.

DNS> show link .dna_nodesynonym.ppinc dns$linktarget
                                SHOW
                            SOFTLINK  DEC:.dna_nodesynonym.ppinc
                                  AT  15-DEC-1993:18:55:56
                      DNS$LinkTarget = DEC:.LKG.PPINC
DNS> show obj DEC:.LKG.PPINC
                                SHOW
                              OBJECT  DEC:.LKG.PPINC
                                  AT  15-DEC-1993:18:56:04
                     DNA$NodeSynonym = ppinc
                    DNA$Towers (set) = :
                   Tower  1 Floor 1  = 01 13    (null)
                   Tower  1 Floor 2  = 02       00 13           ncacn_dnet_nsp
                   Tower  1 Floor 3  = 04       (null)
>>>>>>             Tower  1 Floor 4  = 06       49 00 04 aa 00 04 00 d6 11 20 


	Could somebody please inform the EasyNet-DNS Coordinator (whoever it is)
	to correct this problem ?


	Thanks.

	ralf.

Reply to 4.68:

See note 3.241: Decnet Phase V access is now working.