C S S C    N E W S L E T T E R                                                                                                                                                                                        Vol 2  No 8                                                   June 17, 1994   TABLE OF CONTENTS  1.0  IMPORTANT...PLEASE READ...re SITE INVENTORY REPORT  2.0  Upgrade of AXP VMS Ver 6.1  3.0  Target->Hotline  4.0  Calls received/answered by SCACAD, SCADM and SCSYS for May 1994  5.0  PSI's Individual Dialup Service (IDS)  1.0  IMPORTANT...PLEASE READ...re SITE INVENTORY REPORT       ATTENTION :  DIRECTORS and SUPERVISORS.  If you are going to       delegate this task - MAKE SURE that you pass this information onto       the person(s) doing the WORK around your site!             ===========  Deadline :  July 15th,  1994 ==========                                           Hello again,       Why it seems like it was just yesterday that I wrote to you all       requesting the last Site Inventory Report...  And in a FEW cases -       it was.  Well, here we are at yet another milestone - and another       SIP report is at hand.       Everyone knows what the SIP report is - our report back to Digital       on the software each site is using - and the hardware it's running       on.  The report is a contractual obligation with Digital - and one       which we ALL have to oblige.       Just so that you don't think I've never run one, I want you to know       that I have.  In fact, I ran the batch of the reports for Buffalo       State.  I covered the range of machines from the Buffalo       State/Support Center cluster, to the Pathworks servers and desk-top       workstations.  In all, I executed the routine on thirteen nodes       (which, because of clustering and LAVCs, covered twenty systems).        This awesome feat required less than one afternoon.  Most of that       time was spent obtaining passwords and copy the software between       systems.       What's that mean to you?  It means that I don't want to hear "But I       haven't got TIIIIMMMMEEEE for thaaaat!"         What WILL happen, is that you will request the DASC software from       GETSOFTWARE, copy it to each stand-alone machine (one copy to a       cluster or LAVC) and run the darn thing!               ===========  Deadline :  July 15th,  1994 ==========       TEETH.  That's the incentive we've been lacking - until now.         No software license PAKs will be available to sites that do not       return the Site Inventory Reports.  Not for new products, and not       for existing products (as the current PAKs expire).  You will still       be able to receive Digital software but the DASC software is the       only package that does NOT require a Digital License PAK.         AXP and ULTRIX (or OSF/1) users :       Digital does not have a version of the Site Inventory software for       your platforms.  If you have a cluster with one of these platforms,       the DASC software will fail too.  YOU STILL NEED TO SEND THE       INFORMATION!  The DASC software is simply a convenience.  We need       the following :	o	Site name.	o	DECnet name of the machine.	o	Machine type (3100,  7000 etc.)	o	Serial number.	o	Configuration :		      -	Amount of memory.		      -	Disks.	o	Digital software packages in use.		(The easiest way to get that is by using the License                 Management Facility.  From the SYSTEM account,  do a :			$ LICENSE LIST/FULL/OUTPUT=filename		 Then send us the file with the rest of the information.)	All reports are to be sent to SBSCVA::SCSYS (or SCSYS@SNYBSCVA).             ===========  Deadline :  July 15th,  1994 ==========       Just think, in the time it took you to read this letter, you could       have finished the report on one machine, and started another!       One more thing.  Did I mention that the deadline for the report is       July 15th, 1994?                           -----------------------------------------------       For those sites that HAVE been cooperating, we really appreciate not       having to baby-sit, and apologize for the NEED for this type of       letter.       Questions?  Send them to SCSYS@SNYBSCVA (or SBSCVA::SCSYS).       Comments?  Send them to your local CSSC advisory committee       representative.       Complaints?  You'll get plenty of those from your users - once your       PAKs expire!  Let's hope that this isn't necessary.                                                                                    Jerry Silverschatz  2.0  Upgrade of AXP VMS Ver 6.1		Notes on the upgrade of AXP VMS Ver 6.1       The Support Center's AXP-3800 is now running OpenVMS AXP Ver 6.1.       The upgrade to AXP 6.1 requires a Firmware upgrade.  The Firmware       upgrade is only distributed on CDROM, and the version we used was       "Alpha AXP Systems Firmware Update V2.8".  The upgrade went well       except for the following problems.	1.) The firmware jumper was in the ROM protect position.	We called Field Service to change the jumper and update the Firmware.	Recommendation: Call your local Field Service office to update	your Firmware on your AXP system, and have the local office bring	the Firmware Update CDROM.	2.) The OpenVMS AXP Operating System V6.1 also comes on a CDROM.	The CDROM is in a new format, and requires the CDROM disk.	3.) We were able to install AXP BASIC Ver 1.0 which requires	OpenVMS AXP Ver 6.1.	4.) We ran the IVP on Pascal and FORTRAN which were installed	under OpenVMS AXP Ver 1.5, with no problems.       Buffalo State College's AXP-7600 system is now running OpenVMS AXP       Ver 6.1.  The upgrade to AXP 6.1 requires a Firmware upgrade.  The       Firmware upgrade is only distributed on CDROM, and the version we       used was "Alpha AXP Systems Firmware Update V2.8".  After the       Firmware Update you can NOT boot OpenVMS AXP Ver 1.5, therefore, you       need the OpenVMS AXP Operating System V6.1 on a CDROM.	1.) The first problem we ran into was the shadow system disk on the	AXP system.  When we got into the installation section where it asked	for the disk to upgrade, we selected the old system disk.  The old 	system disk was still set up for shadowing, and was WRITE PROTECTED. 	Looking back in the installation guide you must bring down the 	AXP Ver 1.5 system and disable system disk shadowing.  Well we had 	just upgraded the Firmware on the AXP-7600 and could not boot the 	old system disk anymore.  The solution was to boot the OpenVMS AXP	Operating System V6.1 installation CDROM.  We selected option 2,	and at the DCL prompt performed the following:	$$$ mount/over=shadow_member $1$DUA110 AXPSYS	Note: This mounted the old AXP V1.5 system disk.        $ Help mount/over=SHADOW_MEMBERSHIP         Allows you to override the write protection of former shadow set         members.  When you mount a volume with this qualifier; the volume         shadowing generation number is erased.	  	====================== NEW Menu for Installs =====================    >>> Boot DKA0.0.0.14.0  -fl 0,0  --> CDROM OpenVMS AXP Version V6.1			                 Installation disk.        You can install or upgrade the OpenVMS AXP operating system. You can       also execute DCL commands and procedures to perform "standalone"       tasks, such as backing up the system disk.       Please choose one of the following:        1)  Install or Upgrade OpenVMS AXP Version V6.1        2)  Execute DCL commands and procedures        3)  Shut down this systemEnter CHOICE or ? to repeat menu: (1/2/3/?) 2	$$$  <<<--- New prompt.	====================== NEW Menu for Installs =====================  3.0  Target->Hotline       Sorry that Target was not available to be demonstrated at COA.        We're planning other methods to demonstrate this utility that the       CSSC will be using to relay questions/answers.  Our plan is to ask       three campuses to become trial sites for Target.  These sites will       be contacted within the next several weeks.  Complete documentation       on using Target will be forwarded to those involved.       In the meantime, all CSSC members can email SCACAD@SNYBSCVA with the       three names of their computing services staff who will be       responsible for the three Target->Hotline accounts.  Remember that       the three accounts will be HDxxxA, HDxxxB, and HDxxxC with xxx being       replaced with your site code.                                                              4.0  Calls received/answered by SCACAD, SCADM and SCSYS for May 1994                                        Vendor                                     supplied answers                   SCACAD      10         1 DSN                   SCADM       71         9 Oracle                   SCSYS       20  5.0  PSI's Individual Dialup Service (IDS)       As discussed at the CSSC Advisory Committee meeting at COA, below is       information about what we have been referring to as Nysernet POP       services.       PSI's Individual Dialup Service, or IDS, is available throughout the       United States via local phone numbers that enable PSINet leased line       SCS and CCS customers, as well as InterFrame customers who have       selected and paid for the IDS option, to access their "home"       computers.       These dialups are available for 300/1200/2400 baud access subject to       a simple registration form that is available upon written request or       by sending e-mail to ids-registration@psi.com (a PostScript form       will be returned).       The local dialups provide a reliable, error free, method for remote       staff, remote facilities, or travellers to access PSINet-connected       systems.       Listed below are the U.S. cities that have PSI/PSINet Dialup       Services.Akron, OH Ann Arbor, MIAlbany, NYAtlanta, GAAustin, TXBaltimore, MDBinghamton, NYBoise, IDBoston, MABuffalo, NYChicago, ILCincinnati, OHCleveland, OH Corning, NYColumbus, OHDayton, OHDallas, TXDenver, CODetroit, MIDublin, OHEugene, ORFort Wayne, INFredericksburg, VAGarden City, NYHarrisburg, PAHartford, CTHerndon, VAHouston, TXIndianapolis, InIslip, NY      Ithaca, NYJacksonville, FLLos Angeles, CAManchester, NHMiami, FLNewark, NJNew Haven, CTNew York, NYNorfolk, VAOlympia, WAOrlando, FLPhoenix, AZPhiladelphia, PAPittsburgh, PAPortland, MEPortland, ORPoughkeepsie, NYPrinceton, NJProvidence, RIRichmond, VARochester, NYSacramento, CASalem, ORSan Francisco, CASanta Clara, CASeattle, WASouth Bend, INSpokane, WAStamford, CTSunnyvale, CASyracuse, NYTampa, FLToledo, OHTrenton,NJTricities, WAUtica, NYUrbana, ILWashington, DCWestford, MAWhite Plains, NYWilmington, DLYakima, WAYoungstown, OH############################################################        Class B dialups for PSILink/Worldlink############################################################Another 150 cities are supported by PSILink/Worldlink through local dialups,send email to        classb-na-numbers@psi.comA list will be returned to you############################################################        X.25 International and TELENET/SPRINTNET Access############################################################International access is available through X.25 "PAD" accessat the following X.121 Address:  31106070013602.US TELENET/SPRINTNET Access is also available through the same addressor by typing "c psinet,ACCOUNTNAME"############################################################Copyright 1991.1993 Performance Systems International, Inc.All Rights Reserved.Rev. 5/6/94                                                                              Editor:  Betty Spencer                                                                                          SCACAD@SNYBSCVA

ITEC Home Page