Table of Contents
2 Assistance from CSSC members
3 Advisory Committee - Executive Board
3.1 Advisory Committee
3.2 Executive Board
5 Support Center Functions
5.1 Objectives and Purpose
5.2 Improvements to services by CSSC support staff
5.3 Attainment of goals by Support Center staff
5.4 E-Mail Volume (by subject) for SCACAD, SCSYS and SCADM
5.5 GETSOFTWARE requests
6 Hardware Configuration
6.4 Training Center
6.5 VAX 4000
7.4 Third Party Software
7.5 LAIP, BANNER, LMX software
9 Advisory Committee Members
9.1 Voting Members
9.2 Ex Officio Non-voting Members
10 Advisory Board Meeting Notes
11 Executive Board Meeting Notes
11.1 September 15, 1993
11.2 November 8, 1993
11.3 February 1, 1994
11.4 April 13, 1994
12 CSSC Support/Services Ad Hoc Committee Report
13 Available Software
13.1 Digital Software
13.2 Oracle Products
13.3 Joiner Products
Appendix A CSLG, April 1994
Appendix B GETSOFTWARE, May 25, 1994
Appendix C SITE INVENTORY SURVEY by campus
Involvement of all CSSC members in Support Center issues will be a main focusthis coming fiscal year. Remember you are not just a number but you are "owners"of the Common SUNY Support Center. If we all participate, we can all reap thebenefits.
o Help is needed getting site licenses on software, such as, TGV, Executive Software and upgrading existing licenses. To offer your help, contact SCACAD@SNYBSCVA.o Documentation that would be enjoyed by other campuses is something we all should be sharing with each other. Please contact SCACAD@SNYBSCVA so that your documentation can be showcased in CSSC's DOC utility.o Cooperation is mandatory that patches which are available through DSN not be downloaded by CSSC members but requested through SCSYS.o If any information has changed in regard to the CSSC Advisory Committee as published in this Annual Report, please contact SCACAD@SNYBSCVA to report changes.
The Advisory Committee met at the 1993 Fall COA and the 1994 Spring COA
See 9.1 for listing of all Advisory Committee members.
3.2 Executive Board
The Advisory Committee elected the Executive Board as follows:
Name; Campus; Term(s)
Paul Voninski, Chair; Oswego; 7/1/94 to 6/30/97
Bill Davis; Geneseo; 7/1/94 to 6/30/96
Ruedi Lienhard; Syracuse HSC; 7/1/94 to 6/30/96
Eric Wilson; Oneonta; 7/1/94 to 6/30/95
Bob Wilbert; Farmingdale; 7/1/94 to 6/30/95
The Executive Board will meet with Advisory Committee members during the Fall 1994 COA and Spring 1995 COA meetings. The Executive Board met on 9/15/93, 11/8/93, 2/1/94 and 4/13/94. Notes from these meetings are attached for reference.
. . . . . . . . . . . . . . . . . . . . . . .Date hired
Jerry Craven, Operations, 12/ 7/89
Dave Massaro, Systems/Communications, 1/18/90
Betty Spencer, Academic, 2/ 5/90
Jerry Silverschatz, Systems/Communications, 2/ 5/90
Rob Smith, Administrative, 1/ 4/90
Linda Delaney, Secretarial, 11/16/92
This staff is supervised and backed up by staff at Buffalo State College in therespective areas. In addition a Digital Consultant, providing assistance ingetting the Support Center started, was acquired using the procedures in theSUNY-DIGITAL Agreement (CM00224). We plan to continue to use the DigitalConsultant as long as the current contract provisions make it fiscally possible.
DirectorVacant Linda Delaney, SecretarySystems and Data CommunicationsJoel Swisher, Manager CSSC Staff (SCSYS) Dave Massaro, Systems Programmer Jerry Silvershatz, Systems Programmer Buffalo State College Computing Services Support Kevin Foley, Systems Programmer Paul Bentkowski, Systems Programmer Paul Bardak, Sr. Programmer/Analyst Daniel Blachaniec, Lead Programmer/Analyst DEC support Joseph Weber, Digital Academic Computing ServicesMary Ann Meyer, Manager CSSC Staff (SCACAD) Betty Spencer, Sr. Programmer/Analyst Buffalo State College Computing Services Support Barbara Metivier, Sr. Programmer/Analyst Badria Qadir, Programmer/Analyst Marie Unson, Programmer/AnalystAdministrative Information Systems CSSC Staff (SCADM) Robert Smith, Sr. Programmer/Analyst Buffalo State College Computing Services Support Marcell Harrington, Sr. Programmer/Analyst Romney Taylor, Sr. Programmer/AnalystOperationsAnn Dennis, Manager, Central Operations CSSC Staff Jerry Craven, Senior Computer Operator Kathy Pohl, Senior Computer Operator Buffalo State College Computing Services Support Margaret Banak, Computer Operator Alfred Cappello, Computer Operator Paul Fronckowiak, Senior Computer Operator
The following is taken from the By-laws and comments as to the activities thathave been done in these areas:
5.1 Objectives and Purpose
The purposes for which the Common SUNY Support Center was formed are:
a. To provide a medium for sharing of knowledge among its member institutions for academic instruction and research and admin- istrative information systems.
Comment: The SUNY Training Center has assisted with this task very well, and the training they have provided has been excellent. In addition the Electronic Mail (EM) and various listservers have assisted with this task. When the Support Center staff has been at various training sessions and meetings, we have been able to share mutual concerns.
The CSSC newsletter is still receiving a great response. Fourteen issues were published in 1993 since its inception date of March 4, 1993 and seven issues have been published in 1994 covering areas such as Third Party AXP software, special CSSC software prices, CSLG software, Site Inventory Surveys, Support Center position openings and count of calls received by SCACAD, SCADM and SCSYS.
CWIS (Campus-Wide Information Service) is still available on the Support Center's system to allow Support Center members access to BSINFO, provides information about facilities; DOC, user documentation; SOFTWAREA, software available for CSSC clients; MOTD, system message of the day; NOTES, access to conferences, listservers on DECNotes; and VMS HELP.
BBOARD continues to record various listservers in DECNotes. Today, there are over forty-eight "mail" lists being logged so that members do not have to store list messages in their own disk space.
Digital's CD-ROM documentation for VMS and Ultrix is available over SUNYnet. Directions were sent to each campus' software license manager for access capability.
DECUS tapes have been made available through three CDROMs to all Support Center campuses. Each campus is required to access a special username which will permit access to these CDROMs.
Questions received by SCACAD and replies given have been compiled and stored in the SCACAD conference in DECNotes on the Support Center machine (SBSCVA). With the upcoming use of Target->Hotline for logging Support Center questions, past questions/answers can be reviewed in this application.
Some of the Support Center staff have participated in the Training Center's Wizard Seminars. In addition some CSSC staff have been instructors and made video tapes for the Training Center members and SICAS Center members.
The Training Center and Support Center are planning on using SUNYsat for updates and other information to be presented to their members.
b. To provide requested computer services and facilities including staff, software, equipment, and communications. Among the services include:
1. Copy (distribute) all agency or group licensed software to the member institutions in a timely manner.
Comment: There currently exists a DCL routine which allows campuses to retrieve software over SUNYnet (using DECnet) without intervention of Support Center personnel. This routine, GETSOFTWARE, is started in a "captive account" (usercode) when each site's Software License Manager logs in to the Support Center's system with a special usercode assigned to them. GETSOFTWARE allows each License Manager to review what software is available for down loading, their site information, what jobs they have submitted for software down loading, etc. For a total count of all products transferred from GETSOFTWARE, see "4.6 GETSOFTWARE requests" in this report.
See Appendix A for the April 1994 CSLG listing and Appendix B for a listing of all software that is available via GETSOFTWARE.
The CSSC is trying to get packs on a quarterly basis but haven't been successful because of order problems within Digital.
This distribution method has been working very well. The SICAS Center (located at the College at Oneonta) has been using this for distribution of the SCT Banner software. The SUNY Library Support Center (SLSC) is planning on using this routine for distribution of the LAIP software.
SUNYnet has made the distribution and collection of information possible. Without SUNYnet additional support staff would definitely be needed in addition to more funds for long distance phone calls (including extra for phone tag).
2. Serve as software support liaison in accordance with agency or group maintenance agreements.
Comment: There are three main areas where member sites can submit questions - Academic Support (SCACAD@snybscva), Administrative Support (SCADM@snybscva), and Systems/Communications Support (SCSYS@snybscva). The following are the numbers of questions / problems by area received From July 1, 1993 to June 30, 1994:
Academic Support 214
Administrative Support 633
System/Communications Support 730
3. Serve as a networking hub for services such as DECnet, BITNET and Internet access and to provide alternate path connections to SUNY Central.
Comment: Currently we are the hub for about 25 campuses. When the Joiner software (JNET) is installed on member VAXs, additional systems will be added. The current plan is to have each site VAX "linked" to each other and to have the Support Center linked by the gateway to the non-SUNY BITNET mail traffic. If a campus feels they do not have a system of the size needed to support these links or prefer not to support same, they can have one connection to the CSSC and use this for all other mail connections.
4. House all on-line documentation and Self-Paced Instruction (SPI) courses for access by member institutions.
Comment: Training Center members have access to all of Digital's Computer Based Instructional (CBI) materials on the Support Center's system. In addition "DOC" and "BSINFO" are routines containing information and documentation available for member institutions.
5. Provide a small level of remote VAX computer services for conversion work, training, and access to all software for testing and demonstrations.
Comment: Each campus has assigned a Username manager to assign and monitor usernames on the Support Center system. A routine was developed to allow these managers to assign, change, and delete usernames on the Support Center system. This was one of the original goals to allow members to be independent on the Support Center facilities available to members.
Any member campus may request a usercode on the Support Center system for any person at their site. Since this is on the same cluster as Buffalo State College's system, users have access to any software which is on either system. Some campuses are using software available for this purpose.
The Support Center's system and Buffalo State College's VAX 3400 and VAX 4000 are used for all VMS training at the SUNY Training Center. Currently there is a terminal server supporting Digital VT 340 terminals for training. It is planned that, during the next year, we will be able to add PCs and VAXstations for training at this facility. This will allow for additional training in such products as Pathworks, WordPerfect, dBASE, etc.
The Support Center now has a DEC 3000 Alpha machine being used to test Oracle software and DEC OpenVMS OSF/1.
LAIP is sharing the CSSC system while they are converting to an Alpha machine. Over the next year the configuration will be worked out with the SUNY LAIP Support Center staff and the Executive Board of the CSSC.
The CSSC Executive Board is looking for longterm directions as to the type of equipment that is needed for the Support Center.
6. Serve as a disaster backup facility for the member institutions.
Comment: The Executive Board is looking into a plan where campuses will be assisted in the development of a disaster backup facility for their campus. This is headed by Ruedi Lienhard. We have a unique opportunity to work together to make disaster backup easier for all of us if we agree to some common system setups.
During the past year, Buffalo State College and the Support Center made plans for campuses which might not be able to get off their A10 in the time frame they planned. Facilities were tested so that a campus could go through their VAX and then to the Support Center VAX to the A10 at Buffalo State College. This was tested and could have been implemented if needed.
One member used Support Center facilities to work on their conversion prior to their system being available. The campus used these facilities for Banner training of their users and started their conversion. There were a few problems that were worked out; and this is a function that should be performed during a disaster at a member site.
7. Serve as a demonstration/test center for various Local Area Network (LAN) techniques.
Comment: Lan-type questions, especially regarding Pathworks, have been frequent but we normally have been handling only routine-type questions. We are looking for future directions in this R&D area. LAN-type questions have been difficult to respond appropriately to because of the different PC standards. In this next year, the CSSC will conduct a study of PC's at CSSC member campuses that are known to work with Pathworks.
8. Maintain all required records consistent with a Support Center and as required by vendor or agency contracts.
Comment: The CSSC is going to be re-working the way in which campuses provide information about which systems have what software running on them. We need more cooperation from most sites. We believe this new method will assist the campuses in providing the required information for vendors.
Most of the information is kept in electronic form and will be used as the basis for the reporting requirements. A complete description of the required information is in the CSLG / ESL plans distributed to member campuses at the Fall 1992 COA.
9. Annually publish, to the membership, a complete list of all distributed and supported products with current version numbers and the name of the support person for each product.
In addition to the above areas, the Support Center has assisted campuses inobtaining information on various topics such as terminal emulators, keyboardmapping, system configurations, SUNY-DIGITAL Agreement (CM00224) problems, campusnetworking questions, etc.
5.2 Improvements to services by CSSC support staff
SCACAD produced fourteen issues of the CSSC Newsletter in 1993 and seven issues, so far, in 1994. The newsletter is a main source of communication from the Support Center staff to all Support Center members. Many timely subjects, in 1994 alone, have been discussed such as articles of interest, announcement of the AXP purchase, retirement of All-in-1 V2.3, status on Site Inventory Program, new software available in GETSOFTWARE, position openings in the Support Center, Third party AXP software, Pathworks V5 Migration Guide, CSLG listing, special CSSC software prices, Migrating programs to the AXP machine and calls received/answered by SCACAD, SCADM and SCSYS.
Three DECUS CDROMs are still available to the Support Center members. Currently running are Collection 9, Spring 1991; 10, Fall 1991; and 11, Spring 1992. If the Support Center members wish to access one of the other three CDROMs (Collection 6, Fall 1989; 7, Spring 1990, and 8, Fall 1990) that can be accommodated.
The DOC facility has been an ongoing process for the Support Center. Documentation for the VAX, third-party software, the DECUS tapes and networking have been maintained and continue to grow monthly. All Support Center campuses have been asked to send documentation that might benefit other campuses.
A SCACAD conference is kept in DECNotes in which questions received by the SCACAD account and answers given are displayed for Support Center campuses. Work is currently underway to develop use of Target->Hotline for logging Support Center questions and answers.
A training session at Cornell's Super Computer facility was attended by the SCACAD support person in September 1993. Also a presentation was given at the Fall Wizard on the use of Digital's DSN databases by Support Center members.
Listserver conferences have been included in DECNotes through the bboard facility. This allows users to view discussion groups in another source besides their Mail directory. Any campus who wishes to include a list discussion group into the Support Center's machine DECNotes are welcomed to send in their suggestions. Many campuses have asked for the bboard program so they can put Bitnet discussion groups into their own DECNotes. SCACAD has sent information on getting bboard and has offered help in getting it to run.
Made modifications to the GETSOFTWARE system to offer AXP OpenVMS software. Also, are getting close to offering Ultrix VAX, Ultrix RISC and OSF/1 software thru the current GETSOFTWARE system, but from CDs attached to an Ultrix RISC system here.
We have spent time developing code to allow us to hopefully offer the capability to allow a CSSC site to direct GETSOFTWARE products to more than one system type. Currently, GETSOFTWARE products go to a single VMS system at a CSSC site. We are looking to allow the SCxxxLM user at the CSSC site direct software to one of a few registered systems, to eliminate the need for the CSSC site to get software on one system, and copy it to other systems. Details need to be worked out as to the extent of what will be offered.
Began looking into AXP systems for supporting CSSC sites. The 3000/800 has arrived for this purpose.
We have been involved in PHASE V research, testing and troubleshooting for DECNET. This includes having gone thru a week long class, and testing with Morrisville.
We did a WIZARD presentation on system performance and tuning, and have helped a couple sites with specific system performance issues.
We have done some preliminary system setup work anticipating the implementation of TARGET software use by CSSC sites.
We are currently involved in the search process for an additional CSSC staff person in the systems area. We are hoping for a mid-late summer start date for this position.
Since the Oracle component of the Common SUNY Support Center was organized in 1990, we have worked to achieve our primary two-pronged objective. The operational objective was to promptly reply via email to questions from campuses, while strategically preempting questions by providing consulting, training, and documentation on distributed ORACLE products to our client schools.
Over the past year we have made significant commitments in two areas:
1. Supporting ORACLE on UNIX, specifically SunOS, Solaris, and the AIX system of the RS6000.
2. Strategic consulting and training for Administrative Application Development, specifically ORACLE's CASE development method supported by their CASE tools, CASE*Dictionary, CASE*Designer, and CASE*Generator.
ORACLE's CDE product set (e.g. Forms 4.0, Oracle GLUE) will represent a similar challenge during the coming year.
Historically, the Support Center has been able to handle about 90% of their incoming calls without a subsequent call to ORACLE. Calls to ORACLE for direct technical support have increased so that we now handle about 85% of calls without a call to ORACLE. This increase has been due to the expanding number of both operating system platforms (e.g. Solaris) and new ORACLE products (e.g.ORACLE office) being used by client schools on these platforms. As in the past, the majority of calls to ORACLE are for software upgrades or direct CSSC informational calls without a previous campus question.
Significant progress has been made in three areas with ORACLE's:
1. Client/Server technology
As an example, the CASE tools are being used on SunOS client machines using a Solaris Server. VAX workstations are also being used against VAX servers and the Solaris server.
2. The Parallel Server
The Parallel Server allows multiple nodes in a VAX cluster to share a common ORACLE database. Users may be distributed across nodes based upon available system resources. Currently, our development database is shared across six VAX nodes. Each node may be a client or a server to any other. This has proven to be a very effective environment.
3. ORACLE7's declarative data integrity features
Declarative data integrity is a means to enforce logical relationships among record types within the database itself, rather than through application code. For example, students may not be assigned to classes until those classes have been scheduled.
The current HRMS project being developed by the CSSC will implement these features on the new Digital Alpha AXP platform.
As client schools grow in appreciation of these features and their functions, we are positioned to continue a high level of support.
In response to the CSSC Executive Board minutes on February 1, 1994 under 4. Quality Assessment, which appears later in this document, SCADM has several comments:
The CSSC has received few comments on its services recently. Two suggestions noted: quicker forwarding of Oracle questions directly to Oracle support staff;
We have a couple of procedures that have been in place for about four months on non-VMS platforms (e.g. MVS, UNIX). When a call is received the call is posted directly to the ORACLE Real Time Support System (RTSS) with instructions to call the person from whom the call was received. If necessary, SCADM is conferenced on the call. If the call is level 1 (i.e. production system down) or level 2 (i.e. important features unavailable) the person who initiated the call receives the assigned ORACLE Technical Assistance Request (TAR) number and is invited to contact ORACLE directly by phone referencing the TAR number. This has worked fairly well, However, it should be noted that ORACLE's turnaround time may still be a day or two.
better mechanism for faster distribution of CD-based software products.
SCADM only receives one copy of ORACLE software on CDROM. Until we get equipment to duplicate these disks, we circulate the disks among schools for copying and installation. Usually each school has kept the disks two to four weeks. This window is probably reasonable since the DBA may not be ready to install as soon as the disks arrive. However, we are working to shorten this window.
5.3 Attainment of goals by Support Center staff
1. The CSSC will respond to a request for assistance within one hour.
All Support Center staff try diligently to reply within an hour only if it is to inform the sender that the message has been received and further time is needed to look into the question.
2. If multiple electronic dialogues are required for a request/response, each dialogue exchange will be incorporated into the previous message sequence set.
All Support Center staff keep a log of all messages received and sent and send this along with the current message going out.
3. Where appropriate, the CSSC will indicate what reference sources were used in developing the response. Where possible, reference sources are mentioned.
4. Severity levels included in assistance requests. Four levels of severity have been established and one of these levels should be applied in conjunction with requesting assistance from the CSSC. The CSSC will respond to requests for assistance on a first-in first-out basis within descending order of severity level: 1) system down 2) sub-system down 3) developmental 4) information.
Severity levels are seldom included in messages sent from member campuses. This issue may have to be discussed at the next Support Center committee meeting.
5.4 E-Mail Volume (by subject) for SCACAD, SCSYS and SCADM
By Subject ------------1993----------------- ---------------1994-------------- Subject Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun TotAllin 1 1 1 3 1 6 3 2 2 20 Allin1Alpha 3 1 1 1 6 AlphaApplications 2 1 3 2 1 9 ApplicationsBitnet 1 1 2 BitnetBookreader 3 3 BookreaderC 1 1 1 1 1 5 CCBI Courseware 1 1 CBICDROM 1 1 CDROMDCLfast 1 1 DCLfast DEC Notes 2 1 1 1 1 2 5 1 1 2 17 Dec NotesDECUS 1 1 DECUSDocumentation 1 2 1 1 5 DocumentationDSN 1 1 1 DSNEmulators 1 1 2 EmulatorseXcursion 1 1 1 1 2 2 2 1 2 13 eXcursionExec Sftware 3 1 4 Exec SftwareFortran 2 2 FortranGetsoftware 1 1 2 GetsoftwareGopher 1 1 GopherInternet 4 1 2 4 1 11 Internet Lanserver 1 1 LanserverListservers 1 3 1 1 6 ListserversMAC 1 2 1 1 1 1 1 8 MACOS2 1 1 OS2Pathworks 8 11 9 1 2 3 2 1 37 PathworksPrinting 2 1 2 1 6 PrintingSupercmptr 1 1 SupercmptrTape IO 2 1 1 4 Tape IOTarget 1 1 2 TargetTCPWare 1 2 3 TCPwareUltrix 1 1 2 UltrixUseraccounts 2 6 1 1 1 2 2 2 17 VAX miscVAX misc 1 3 2 2 1 1 3 1 14 VMS CommandsVMS Mail 1 1 VMS MailWordPerfect 1 1 2 WordPerfect ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ Total 14 20 29 27 10 18 18 17 25 11 10 15 214 Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May JunCommon SUNY Support CenterTotal questions received by SCADM (July 1, 1993 - June 30, 1994) By Product ------------1993----------------- ---------------1994-------------- Subject Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Tot3GL 1 1 1 2 2 2 9 3GLBAN 3 2 10 15 BANCASE 1 1 CASEDBA 23 28 19 56 21 14 33 23 57 52 57 47 430 DBAFORM 3 14 1 6 11 8 8 5 4 3 63 FORMMACOR 1 1 2 MACORMENU 1 2 1 2 6 MENUNET 7 8 7 3 3 1 2 5 36 NETPCORA 1 3 6 10 PCORASQR 7 3 19 6 2 2 2 45 SQRSRW 1 1 SRWTXT 5 1 8 1 15 TXT ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ Total 35 29 39 72 33 28 52 54 79 61 71 80 633 Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May JunCommon SUNY Support CenterTotal questions received by SCSYS (July 1, 1993 - June 30, 1994) By Subject ------------1993----------------- ---------------1994-------------- Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Tot3rd Party Prod 2 2 3rd PartyAll in 1 1 1 3 2 1 8 All in 1AXP 1 1 AXPVMS Backup 2 2 1 1 6 VMS BackupBookReader 2 2 2 1 1 1 1 10 BookReaderBUGs 3 1 1 1 1 7 BUGsDCL 1 2 2 1 1 1 8 DCLDCLFAST 2 2 DCLFASTDECmail 1 1 3 1 1 1 8 DECmailDECnet 1 2 2 3 8 DECnetDNS DQS DTS 1 1 1 1 3 7 DNS DQS DTSDSN 1 1 4 14 2 1 2 25 DSNeXcursion 1 1 2 eXcursionGETSOFTWARE 3 6 6 5 7 1 1 9 13 1 4 4 60 GETSOFTWAREGoldMail 1 1 1 3 GoldMailHardware 5 1 5 1 1 2 1 2 18 HardwareHITMAN 1 1 2 HITMANJNET/PMDF 3 5 3 3 4 3 5 5 7 7 45 JNET/PMDFLAIP 1 1 1 2 5 LAIPLAT 2 4 1 6 3 5 2 4 2 29 LATLicense 5 2 1 3 4 3 5 4 3 1 31 LicenseLicense Mgrs 1 2 5 1 2 3 3 1 2 2 3 25 License Mgrs.MOTIF 2 1 2 5 MOTIFNetworking 3 1 1 1 6 NetworkingNotes-(VAX) 1 1 1 3 Notes-(VAX)OSF1 1 1 OSF1Patches 1 9 2 2 4 2 3 5 2 1 4 35 PatchesPathworks 4 8 3 1 1 3 5 6 10 1 2 44 PathworksPerformance 1 1 1 3 PerformancePrinting 2 1 3 1 1 6 1 2 2 19 PrintingRemote Dev Fac 1 1 Remote Dev FacSecurity 1 2 1 4 SecuritySNA 4 1 1 1 7 SNASYSMGMT 8 18 12 5 7 8 11 12 15 7 3 6 112 SYSMGMTTCP 3 3 TCPUCX 1 3 2 1 3 2 1 13 UCXULTRIX 3 9 2 8 5 4 5 1 37 ULTRIXGen. Upgrades 1 1 2 Gen. UpgradesVMS Upgrades 1 1 1 2 1 2 7 2 1 18 VMS UpgradesWordPerfect 1 1 1 3 WordPerfectXterminal 1 1 2 Xterminal ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ Total 51 87 45 55 55 36 62 63 93 26 20 37 7305.5 GETSOFTWARE requests
The count of products transferred from GETSOFTWARE (by Month) for the period July 1993 through June 1994:
1993Jul 87Aug 103Sep 151Oct 187Nov 96Dec 1141994Jan 118Feb 187Mar 210Apr 149 May 95Jun 186 -----Total 1683
6.2 VAX/VMS VAX 6000 model 610 128 MB HSC 70 SA650 TA906.3 VAX/Ultrix MVII 32mb 450MB disk TK506.3 OpenVMS/AXP 30006.4 Training Center
In addition Buffalo State College has a VAX 3400 which has been used for training by the SUNY Training Center when course offerings are such that privileges are needed which may cause the cluster to go down. When in this mode the VAX 3400 does not affect the operation of the cluster. Buffalo State College originally acquired this machine to test their software prior to installation on the cluster. This arrangement appears to be sufficient for the functions described herein.
6.5 VAX 4000
A VAX 4000 was installed in the summer of 1991. The purpose of this system was to replace the VAX 3400 and to provide enhanced functionality. Note: this system will only be used under the VMS operating system.
The Support Center Executive Board and the LAIP Program have an agreement with LAIP to upgrade the 6410 that was the Support Center's machine (5.1) to a 6610 and be used on a shared basis between the LAIP Program and the Support Center.
A list of current software available from Digital through the CSLG/ESL is referenced in the X-DECTEI-L conference in DECNotes (see note 90.17) and also appears in the appendix.
The Joiner Agreement with SUNY has been going well. Currently the Support Center is a host site for about 25 BITNET campuses. The member campuses have had few or no problems with installation and on-going maintenance with BITNET "links" which the CSSC sends out whenever changes are needed.
The Support Center currently supports and distributes Oracle software Version 6 and Release 7 for the following platforms:
DIGITAL: OpenVMS, OpenVMS AXP IBM: AIX, MVS and VM SUN: SunOS, Solaris, HP: HP-UX Data General NETWARE (Release 7 only) MACINTOSH (CDE Tools and V6 only) OS/2 (Release 7 only) DOS (V6 only) WINDOWS: (CDE Tools)The PC versions of Oracle are only distributed with the initial distribution. Campuses are to obtain PC Oracle support from Oracle directly.
7.4 Third Party Software
license support doc media Oracle for mainframes SUNY Central(1) | X | vendor | X Oracle Server SUNY Central | X | vendor | X Oracle for PC SUNY Central |vendor | vendor | X PMDF X | X | X | X DCLFast X (3) | X | vendor | X Goldmail X (3) | X | X | X Hitman X | X | vendor | X Jnet (2) X | X | vendor | vendor PVI (Precision Visual) X | X | X | X RMS Edit X (3) | X | vendor | X Remote Device Facility X (3) | X | vendor | X TCPware X (3) | X | vendor | X WordPerfect vendor |vendor | vendor | X QVT X | X | vendor | XX = provided through CSSC (1) Contact SUNY Central for one-time license fee. (2) for most campuses. (3) Contact CSSC for license fee7.5 LAIP, BANNER, LMX software
While we do not support LAIP, BANNER, LMX software, we do distribute it
8 BudgetThe following tables represents the financial plan for 94-95. Differences fromthe financial plan presented to the members in the Fall 1989 are:o the number of campuses is now set at 25 State Operated and 10 Community Colleges. o the actual staff costs are included as of 6/30/94.o additional funds are allocated to the area of supplies, phone, travel, etc. to reflect projected costs.o Hardware lease costs are actual costs. o Merger of the CSSC/Training Center budgets As per CSSC By-laws, each member is required to have proper training through the SUNY Training Center or an equivalent training plan as determined and accepted by the Common SUNY Support Center Executive Board. To facilitate this training requirement, each CSSC member institution can pay fees for membership in the SUNY Training Center directly to the CSSC (see Table on Page 25). The Training Center membership fee has two components: (1) annual fee, and (2) training points. Training points can be used to pay tuition/fees for courses and other training activities formally offered through the SUNY Training Center. (Exceptions will require prior approval of the Training Center Director.) SUNY Training Center fees for a full member of CSSC are $7,000 for FY 94/95, i.e., $2,000 annual fee and 5,000 training points. Each component of the membership fee will be prorated at 55% for limited CSSC members.
9 Advisory Committee Members9.1 Voting MembersAlbany Isabel Nirenberg Assistant Director, Computing Services Voice 518-442-3736 FAX 518-442-3697 EM sysiln@albanyAlfred Dennis Kelsey Acting Vice President, Administrative Affairs Voice 607-587-4177 FAX 607-587-3298 EM KelseyDH@snyalfvaBrooklyn HSC Robert Losonsky Assistant Manager, Computing Systems and Services Voice 718-270-2431 FAX 718-270-3319 EM Losonsky@snybkadmBroome CC Grant Newton Director, Computer Center Voice 607-778-5011 FAX 607-778-5119 EM email@example.comBuffalo Dave L. Cummings Assistant Director, Computing Services Voice 716-878-4206 FAX 716-878-4235 EM CumminDL@snybufvaUniv at Buffalo Frank Rens Associate Director, Academic Services Voice 716-645-3574 FAX 716-645-5972 EM firstname.lastname@example.orgCanton Robert R. Hayden University Database Administrator Voice 315-386-7150 FAX 315-386-7930 EM HaydenRR@snycanvaCayuga CC Martin J. Wisniewski Associate Dean Voice 315-255-1743 ext 220 FAX 315-255-2050 EM Wisniewski@snycayvbCentral Bruce Briggs Director of LAN Services Voice 518-443-5548 FAX 518-443-5809 EM briggsbd@snycenvaCobleskill Daniel Sidebottom Manager, Computer Services Voice 518-234-5337 FAX 518-234-5333 EM SideboDR@snycobvaCorning CC Bill Manual Director, Computing Services Voice 607-962-9412 FAX EM ManuelWC@scccvc.corning-cc.eduCortland Martin Coolidge Director, Administrative Computing Services Voice 607-753-2501 FAX EM Martin@snycorvaDelhi Richard W. Nabinger Senior Staff Associate Voice 607-746-4354 FAX 607-746-4208 EM NabingRW@snydelvaEmpire State Curtis King Director, Computer Services Voice 518-587-2100 FAX 518-587-5404 EM cking@snyescvaFarmingdale Robert J. Wilbert Director, Computer Center Voice 516-420-2167 FAX 516-420-2698 EM WilberRJ@snyfarvaFashion InstituteHerbert Wood Executive Director, Administrative Computer Center Voice 212-760-7719 FAX EM WoodHH@snyfitva Finger Lakes CC John Taylor Academic Systems Manager Voice 716-394-3500 ext 301 FAX 716-394-5005 EM sflcva::taylorjmGenesee CC Mary Jane Heider Manager of Academic Computing Voice 716-343-0055 ext 363 FAX 716-343-4334 EM HeiderMJ@snybscvaGeneseo William H. Davis Director, Computing & Media Services Executive Board Member Voice 716-245-5577 FAX 716-245-5005 EM Davis@geneseoHerkimer County CCDennis Olds System Administrator Voice 315-866-0300 FAX 315-866-7253 EM shccva::dfoldsJamestown CC Joseph Ciesielski Computer Center Director Voice 716-665-5220 FAX EM ciesieja@sunyjccLibrary Services Carey Hatch LAIP Technical Manager Voice 518-443-5577 FAX EM HatchCB%slscva@snycenvmMohawk Valley CC Francine M. Zammiello Educational System Specialist Voice 315-792-5304 FAX 315-792-5696 EM francine@snymvccMorrisville Jean L. Boland Director, Computer Services Voice 315-684-6053 FAX 315-684-6453 EM BolandJL@snymorvaOld Westbury Ronald C. Johnston Director, Computer Center Voice 516-876-3149 FAX 516-876-3209 EM Johnston@snyoldvaOneonta Eric H. Wilson Director, Computing Services Voice 607-436-2539 FAX 607-436-2107 EM WilsonEH@snyonevaOswego Paul Voninski Director, Academic Computing Executive Board Member Chair Executive Board Voice 315-341-3055 FAX 315-341-3143 EM Voninski@oswego.oswego.eduPlattsburgh Tom Mercadante Co-ordinator of Applications Development Voice 518-564-3013 FAX 518-564-7827 EM MercadTF@snyplavaPotsdam Bruce E. Buchanan Director, Central Computing Voice 315-267-2089 FAX 315-267-2318 EM BuchanBE@snypotvaRockland CC Karen DeMauro Director, Administrative Data Processing Voice 914-574-4770 FAX 914-356-8744 EM srccva::kdemauroSICAS Rosanne Murphy Director, SICAS Center Voice 607-436-2039 FAX 607-436-2038 EM murphyre@snysicvaStonybrook Charles Bowman Associate Director, Computer Services Voice 516-632-6245 FAX 516-632-9086 EM cbowman@sbccmailSyracuse HSC Ruedi Lienhard Director, Computer Center Executive Board Member Voice 315-464-5426 FAX 315-473-5561 EM Lienhard@snysyrv1Training Center Sharon Gallagher Director, SUNY Training Center Voice 315-464-4079 FAX 315-464-7303 EM Gallaghe@snysyrv1Utica/Rome Allan Steinhauer Manager, Administrative Computing Voice 315-792-7440 FAX EM XACS@sunyit.edu9.2 Ex Officio Non-voting Members17 Campus Vice Presidents Group Dr. Edward Kumar Vice President, Administration SUNY College at Brockport Voice 716-395-2129 FAX 716-395-2401 EM ekumar@brockvmaAssociate Vice Chancellor for Information Technology Charles R. Blunt Associate Vice Chancellor, Information Technology SUNY Central Administration Voice 518-443-5550 FAX 518-443-5799 EM Bluntcr@snycenvmSUNY Training Center Sharon M. Gallagher Coordinator, SUNY Training Center Voice 315-464-5426 FAX 315-464-5561 EM Gallagsm@snybufva Raney Ellis SUNY College at Plattsburgh Chair, SUNY Training Center Voice 518-564-3013 FAX 518-564-7827 EM elliswr@snyplavaSUNY Computing Officer Association (COA) Executive Council Member To be addedHost Campus Representative Ronald N. Brown Jr. Associate Director, Computing Services SUNY College at Buffalo Voice 716-878-4611 FAX 716-878-4235 EM BrownRN@snybufva10 Advisory Board Meeting Notes10.1There were no Advisory Board Meeting notes for this past fiscal year. Only one meeting was held and that was in conjunction with an Executive Board meeting.
11 Executive Board Meeting Notes11.1 September 15, 1993
Present: Ron Brown, Bill Davis, Sharon Gallagher, Ruedi Lienhard, John Phillipo,Paul Voninski, Bob Wilbert, Eric Wilson
Common SUNY Support Center Executive Board
Meeting Minutes - September 15, 1993
SUNY College at Buffalo
The meeting was called to order by the Chair, Paul Voninski, at approximately 10a.m.
Minutes of the CSSC Executive Board meeting of March 4, 1993 were approved asamended.
Minutes of the Common SUNY Support Center (CSSC) Executive Board meeting of June6, 1993 were approved without change.
Minutes of the CSSC Advisory Committee meeting of June 8, 1993 were approved asamended.
1.a.In response to a membership inquiry a discussion took place regarding distribution of Oracle software from the CSSC. Some difficulty has been encountered as a result of Oracle changing their distribution media from magnetic tape to CD-ROM.
John Phillipo made a motion that the CSSC investigate the acquisition of CD-ROM duplication hardware if this will solve the Oracle distribution problem. CSSC to report their findings at the Fall 1993 COA.
Discussion - the CSSC will duplicate CD-ROMs only to some reasonable level i.e., two or three per campus.
Motion unanimously approved.
The CD-ROM format issues must be investigated. Both Ron Brown and Vince Kugler have been working with Oracle personnel regarding distribution and contract amendments needed regarding SUN and UNIX distribution.
l.b.It was noted that Oracle 7 is available from GETSOFTWARE. In response to a member inquiry it was stated that new software is usually made available on GETSOFTWARE within two weeks of arrival at CSSC. Arrival at CSSC could be significantly different from vendor product announcemcnt of availability.
l.c.Discussion has been going on with Oracle representatives regarding distribution of the Oracle product. The issue remains open with both parties (SUNY and Oracle).
Discussion turned to Oracle version/s supported at CSSC as well as the SICAS Center. The SICAS Center has not, as of this date, committed to supporting multiple versions of Oracle at the same time. John Philippo recommended we request this issue be placed on the SICAS Mini-Conference agenda scheduled for 10/4 and 10/5/93.
l.d.In response to a member comment it was noted that the terms and condition of the agreement between SUNY and DEC (CM00224) are not consistent with the terms and conditions of the CSLG and ESL programs. This is being worked on but has caused delay in receipt of DEC PAKs. Temporary PAKs have been requested from DEC. If Alpha PAKs cannot be read on Open VMS VAX, we have a problem.
A question was posed - is the CSSC supposed to support DEC OSF/1 in addition to ULTRIX. At this time it appears that CSSC support will be needed for VMS VAX, VMS AXP, ULTRIX and DEC OSF/1. This area needs further discussion and evaluation.
The CSSC is in need of an Infoserver, a workstation running VMS AXP and a second workstation platform with DEC OSF/1.
l.e.A CSSC member indicated there was a need for more communication with and from the Support Center. The Executive Board agrees. It was recommended and agreed that a CSSC-L LISTSERV be established and a CSSC Gopher be established for retention of approved CSSC minutes and annual reports.
l.f.A CSSC member suggested "after-hours support" be considered from the Center. The Support Center suggested that, in the event of a planned after-hours activity, a campus should provide prior notification to the CSSC and appropriate support arrangements would be made available. Ron Brown suggested CSSC staff be provided with pagers. In the event of an unplanned emergency, call Buffalo State College computer operations (phone ?) and they will page a CSSC staff member.
l.g.A CSSC member noted the need for increased and improved Pathworks support. Pathworks support is complicated by the variety of PCs and network interface cards in use. The issue of what NICs and PCs should be supported was discussed.
There was general agreement that a standard PC/NIC configuration should be identified and supported. This would allow for differentiation of PC/NIC problems from Pathworks problems. A campus must be able to replicate a problem on this "standard" configuration. This "standard" configuration is ------???
l.h.A member queried, can the CSSC support Alpha? Response: the CSSC does not have an Alpha processor. What size Alpha does the Support Center need, one large or many small? When will the first campus run Banner on Alpha?
Motion: To request CSSC staff study the issue of acquiring a small Alpha machine for testing and determination of initial VMS support issues. Further, to report back to the Executive Board with a recommendation at the Fall '93 COA.
Motion Seconded. Motion Approved.
l. A discussion took place regarding continued use and support of TCPWare from Process Software, Inc. It appears that Process Software is moving too slowly on including Gopher client/server services in their TCP/IP services for VMS. Is there interest in switching to a competitive product i.e., TGV Multinet? There was no resolution to drop TCPWare.
Ron Brown distributed an updated membership/financial statement. Income exceed expenses by approximately $150,000. John Philippo recommended $50,000 be used to purchase an Alpha processor, $75,000 be placed in a hardware reserve fund and $25,000 be used to support an additional staff at the CSSC.
Discussion took place regarding services and non-member campuses.
Sharon Gallagher noted that we might be approaching the facilities management or system management area of interest from one or more campuses. Sharon suggested we consider running a pilot program with Optometry to determine time and cost of providing these types of services.
A discussion took place regarding thc level of services that might be offered from the CSSC. It is apparent that the level of services now offered from the CSSC has increased substantially since its inception. The important issue is what services should be supported by the CSSC in the near and long-term future and what costs are appropriate. An ad hoc advisory group was created to investigate this area. Bob Wilbert agreed to chair a group consisting of additional Advisory Committee members.
3. Annual Report
A draft of the 1992-93 CSSC Annual Report was distributed to the Executive Board. Executive Board members are to review the draft and forward any changes, within one week, to the SCACAD account at CSSC.
A discussion took place of Oracle/Banner versions to be supported by the CSSC and SICAS Center.
Motion was made - To prepare an Oracle/Banner version upgrade plan to be presented to the Computer Center Advisory Board (CCAB) of SICAS program and that this plan be presented at a CCAB meeting forthcoming in early October, 1993.
Motion seconded. Motion approved.
There was interest expressed in the CSSC bccoming a full NYSERNet member with POP capabilities. All members of CSSC could use the POP. Payment for hourly charges would be the responsibility of thc individual user. Issue will be presented to the Advisory Committec.
The SUC Buffalo LAIP cluster hardware is expected to move to an Alpha processor in near future. Syracuse HSC is looking at the need for an Alpha machine within several months.
a. Apple Computer Inc. will not consider an agreement with CSSC for Mac TCP/IP. A comment was made that cost will increase next year for this product - buy now.
b. Microsoft - Negotiations with SUNY have failed. The Foundation at University at Buffalo has a contract with Microsoft and OGS is in the negotiation process.
c. Discussions with Claris are in progress.
d. Borland and Jim Greenberg remain in discussion.
e. DEC hardware maintenance contract for SUNY. A bidding activity is required. OGS plans to go to bid on DEC hardware maintenance with intention to have a new contract by March 1994.
8. Fall COA
Meeting dates were noted and plans initiated for Executive Board and Advisory Committee meetings.
9. Meeting with CSSC Staff
The Executive Board met with CSSC staff and others from Buffalo College. Executive Board members toured the CSSC hardware facility.
Discussion with CSSC staff included the following:
Rob Smith indicated thc number of supported Oracle platforms has increased from 2 to 13, i.e. multiple UNIX platforms along with VM, MVS and VMS. Rob also noted the number of supported sites has increased.
Paul Voninski indicated that perhaps we should not support some of the products currently supported.
Comments were made on what level of CHIPCOM support is needed; what levels of networking do we intend to support; what levels of DEC VMS services should we be supporting, i.e. facilities management, LAIP VMS, other; what CD-ROM duplication resources do we support.
It is apparent that confusion exists regarding the scope of support provided by the CSSC. Ron Brown suggested that we have a loss of focus as a result of additional campuses becoming members of CSSC and the type of campuses currently supported. A policy statement is needed from the Executive Board regarding scope of services.
Motion: To move forward with the search to fill a new position in the CSSC that will be funded from recent income and be self-sustaining from new income. The new position must be approved by the Advisory Committee at Fall '93 COA before hiring can take place.
Motion seconded. Motion approved.
The meeting was adjourned at 4:25 p.m.
11.2 November 8, 1993
The meeting was called to order at 7:15 p.m.
Common SUNY Support Center Executlve Board
Meeting Minutes - Monday, November 8,1993
Quality Inn, Syracuse, New York
CSSC and Training Center board members present: Charles Blunt, Ron Brown, BillDavis (recording), Raney Ellis, Sharon Gallagher, Jim Greenberg, Bill Manuel,Tom Mercadante, John Philippo, Mike Pisa, Paul Voninski (presiding), and EricWilson. Guests: Dave Cummings, Ann Dennis, and Michael Sher.
Training Center futures
Sharon Gallagher presented her concerns about continued funding for the SUNYTraining Center. Diminishing CCUP contributions to the Training Center willforce closing at the end of this fiscal year unless alternative funding is found.Funding for the Training Center is about 50% campus-based and 50% from CCUP. Buteven the 50% campus-based component comes mostly from campus CCUP money. As CCUPends, both funding streams end. In lieu of alternative funding, Gallagherproposes moving some Training Center functions to the CSSC.
1. Proposal Summary
a. Demand for services of both the Training Center and the CSSC are growing rapidly because of the breadth of services provided.
b. 50% of Training Center resources are allocated to keeping CSSC programs going. Brown and Gallagher propose moving this component of training to the CSSC. They propose moving all 4 Training Center support staff to the CSSC. This resolves Training Center funding problems, and at the same time adds badly needed staff to the CSSC.
c. The HSC/Syracuse Training Facility would be closed, or maintained with nonTraining Center funding. Rent at HSC/Syracuse is currently $3OK annually.
d. It would be desirable to announce changes to staff and clients by February 1,1994, if such changes are deemed necessary, and to complete a transition by next fiscal year. This will require a decision by early December.
a. Although the original mission of the Training Center was to support the CCUP transition, rapidly changing technology means we're always in "transition" -- the need for training is ongoing.
b. Can we maintain/fund the Training Center on its original administrative/ CCUP base while we develop and nurture new faculty and academic funding streams to support the Center? The Training Center is an especially important resource for FACT and LAIP, yet neither program can contribute significantly to Training Center funding.
c. What other backup plans or options exist? This seems to present an opportunity to think afresh about support and training needs within SUNY. For example, do we need a full-time manager of combined training and support operations? Should training still be centralized, or should we take road shows to campuses?
d. Each of the 3 support centers was originally conceived as a self-sustaining entity. Even apart from the revenue they generate, the support centers are valuable SUNY resources providing useful services to the campuses. As such, they may merit ongoing, "institutional" funding streams.
3. Actions proposed
a. A subcommittee consisting of two members of each board and one member from Central will draft a proposal to be submitted to the two executive boards on December 1,1993. The committee will consist of Bill Davis and Eric Wilson from the CSSC, Raney Ellis and Mike Pisa from the Training Center, John Philippo from Central, Ron Brown and Sharon Gallagher.
b. SICAS and LAIP advisory committees should be included in the discussions.
c. Proposals should include financial projections where possible.
d. After revision and approval of the proposal by the joint executive boards, the proposal will be presented to the joint advisory boards on December 2,1993.
Support Center Budget and Staffing Review
Ron Brown distributed membership packets and reviewed contents with the board.
Membership is rapidly growing. In addition to new members listed in the information packet, Rockland CC will be joining. The much larger membership base is placing great demands on existing shff. Additional shff are required.
a. Financial picture is very good because of increased revenue from new members. We should be able to add the staff needed to support the larger membership, add needed hardware, and perhaps slightly reduce membership fees.
b. All CC payments are made to an IFR account. Ron Brown has arranged a reduction of overhead fees charged against this IFR from 16% to 9%.
a. Is the CSSC to continue its role as a hot backup site for emergency response for the campuses? If so, we need to revisit the hardware issue: does the CSSC have appropriate hardware for this role?
b. The CSSC will be required to support the VAX/Alpha platform, initially for the OpenVMS operating system, and perhaps in the future for OSF/1. Several Banner campuses and all new LAIP installations plan to install VAX/Alpha machines soon. The CSSC will need to purchase Alpha hardware if we expect them to support it. While it may be possible to purchase both OpenVMS and OSF machines under the current budget, OpenVMS is a higher priority. The CSSC should submit a request for purchase of an appropriate Alpha/OpenVMS machine, for approval by the board.
c. It is increasingly common for software and documentation to be distributed on CD-ROM. The CSSC should investigate the contractual, financial, and technical aspects of implementing CD-ROM duplication and distribution services for member campuses.
4. Discussion of Role of CSSC
a. It is important for us to clarify and prioritize what the CSSC will support, what it won't, and what it costs. It would be very valuable to have a discussion with the entire advisory committee about what is needed from the CSSC. Bob Wilburt's committee is charged with exploring these issues.
b. Overall goal is to increase services, increase membership, and decrease cost. The CSSC is on-track toward achieving this strategic goal: membership and revenue are up; this makes possible a modest increase in staff, and strategic hardware acquisitions in support of new services. At the same time, the cost to each campus might actually decrease.
The meeting was adjourned at 9:30 p.m.
11.3 February 1, 1994
The meeting was called to order at 10:07 a.m.
Common SUNY Support Center Executive Board
Meeting Minutes - February 1, 1994
SUNY HSC Syracuse
(Amended and Approved)
Present: Charles Blunt, Ron Brown, Bill Davis (recording), SharonGallagher (Training Center), Carey Hatch (LAIP), Ruedi Lienhard, RoseanneMurphy (SICAS) Paul Voninski (presiding), Robert Wilbert, Eric Wilson.
1. Update on John Philippo's Medical Condition
John's condition continues to improve. Support from his friends and colleagues across the state has been overwhelming.
2. Staff Update
Ron Brown updated the board on two new CSSC staff positions. A search committee has been formed, job advertisements are scheduled, search will close April 1, staff will join CSSC by mid-May. The positions will be at rank SL-3 or SL-4 in the following areas: systems and communications, for VMS, Unix, and OSF/1; Oracle support, with emphasis on mainframe IBM and Sun platforms.
The addition of new CSSC members from the LAIP program has significantly increased workload. The new staff positions will more evenly distribute this added load, should improve response times, and will perhaps allow for new services for LAIP campuses.
The VAX-to-Alpha transition beginning at many campuses will also increase the workload at the CSSC; this may not be the best time to significantly increase membership or range of services offered. Robert Wilbert's sub-committee is charged with exploring an appropriate scope of activities and services for the CSSC. Can we broaden the scope and still retain the cost effectiveness of the CSSC?
3. Budget and Membership Update
We have one new member campus: Finger Lakes CC, as a DEC-only member. Both FLCC and the University at Albany require RISC/Ultrix support. A small refurbished machine was purchased to provide this support.
Under current by-laws, member campuses need to give the CSSC notice of 1 year to withdraw. In order to get an accurate projection of future membership, Voninski will send e-mail to member campuses summarizing rates established in the December 2, 1993 joint meeting of advisory boards. Gallagher will forward this rate information to Voninski for inclusion in the mailing.
Charles Blunt discussed the status of integration of the SUNY Training Center and the CSSC as it effects the budget. The Training Center has been asked to vacate its space at HSC Syracuse. Relocation adds to the cost of continuing the Training Center. What options are available? Possible collaboration with NYSERNet, and regionalization of services to Buffalo and Albany were discussed.
It was discussed and agreed that the CSSC produce a 5-year plan of direction. At the CSSC Advisory Board Meeting scheduled for the SUNY Technology Conference June 6-8 in Syracuse, we will issue a call for volunteers to draft a 5-year plan. This sub-committee will likely consist of 1 or 2 members of the CSSC Executive Board, several members of the CSSC Advisory Board, and representatives from LAIP, SICAS, and the Training Center.
4. Quality Assessment
The CSSC has received few comments on its services recently. Two suggestions noted: quicker forwarding of Oracle questions directly to Oracle support staff; better mechanism for faster distribution of CD-based software products. There is also some confusion among the membership about the CSSC's role in SUNY-wide contracts. Although CSSC staff were prominently involved in establishing some contracts, all contracts are administered at Central and not by the CSSC.
A DEC 3000 Alpha machine will be delivered soon to the CSSC. This will facilitate support of Alpha systems and application software.
5. Support Issues Committee
Robert Wilbert reported to the board on the Support Issues Committee. The group has drafted a charge, solicited comments, and begun discussion of scope and level of service. They will be investigating support boundaries appropriate for software and versions, hardware platforms, operating systems, network software, CSLG/ESL software, 3rd party products, facilities management products, and future direction. They are also elaborating varied levels of support, such as (1) unsupported; (2) distribution only; (3) ...plus installation support; (4)...plus general support; (5)...plus full technical support.
The Support Issues Committee suggests we implement a procedure to survey CSSC member campuses every 4 months with a well-structured survey . The survey would be used to establish and maintain an appropriate support matrix for the CSSC, as well as to provide timely quality assessment of CSSC services. Wilbert suggests a standing committee of 3 campus representatives, 1 of whom is on the executive board of the CSSC, to oversee the survey process.
General discussion of the Support Issues Committee report followed.
6. LAIP Issues
Carey Hatch reports that LAIP is quickly deploying Alpha VAXes: 7 are in the field, 3 of which are in production. The growing Alpha base will require CSSC familiarity with the Alpha platform. LASG has announced reorganization of the database clusters. The new plan calls for fewer, larger clusters. Buffalo will move to an Alpha 4000-610 to host the larger proposed cluster.
7. Educational Technology Initiative
Charles Blunt briefed the board on the Educational Technology Initiative (ETI). Since University-wide support centers (such as the Training Center, CSSC, and SICAS Center) are critical to the Institution's mission, these may fall under the scope of the ETI and may be considered for ETI funding.
8. SICAS Issues
Roseanne Murphy presented software upgrade paths for Oracle and Banner for migration to current versions and to Alpha (where applicable). After discussion, it was decided that the board will publish a recommended "grid" for the supported upgrade path, and will notify members and affiliated support centers if this path changes. Blunt will ask Oracle for appropriate base version (6.036.7) and degree of support (delivery of 6.036.7 either from Oracle, or indirectly from SCT).
9. Board Elections
Paul Voninski's seat on the board is up for election. Voninski will secure nominations and ask Bruce Ristow of Geneseo to conduct the election for the 3-year term.
10. Other Business
It was suggested that 2 representatives from the board attend DECUS for information gathering and to make contacts preliminary to work on the SUNY/DEC contract renewal.
The meeting was adjourned at 2:50 p.m.
11.4 April 13, 1994
Location: SUNY Training Center, HSC Syracuse
CSSC Executive Board
Accepted as Corrected
April 13, 1994
Attending: Paul Voninski (Chair), Bill Davis, Eric Wilson, Ruedi Lienhard, Bob Wilbert, Chuck Blunt, Sharon Gallagher, Ron Brown, Raney Ellis, Bill Manuel, Michael Sher, Carol Thomas
The meeting was called to order at approximately 10 a.m.. This CSSC ExecutiveBoard meeting was a joint meeting with the SUNY Training Center Executive Board.
1. Sharon Gallagher provided an update on the status of the Training Center (TC). Sharon distributed a spreadsheet which illustrated revised funding source and funding distribution information. A letter from Dr. James Hall, SUNY Vice Chancellor for Educational Technology, indicated that the Office of Educational Technology would commit $140,000 in direct support of the Training Center. Funding needed from the CSSC to support the TC has increased from $196,000 to $223,500. Sharon also identified a work distribution plan for Training Center staff. The spreadsheets reflected a recharge by program for the SICAS Center, LAIP and FACT. The Office of Educational Technology will be going to these programs seeking fiscal support for the Training Center.
Sharon commented on the new Training Center location at 550 East Genesee Street. Negotiations were continuing relative to the lease for this location.
The CSSC full membership charge for FY94-95 will include 20 days of training from the Training Center.
A new role and direction for the Training Center was discussed. The perception and responsibility of the Training Center must change to reflect a new role as a University-Wide program supporting training. Raney indicated that training at the SUNY, regional or campus level must be a coordinated effort to produce an effective University-Wide result.
A Training Center long-term plan will be drafted by January, 1995 and distributed for review by appropriate offices and staff.
2. Chuck Blunt directed a discussion on his memorandum of April 11, 1994 to the CSSC and Training Center Executive Boards. Chuck described some of the recent organizational changes at Central which involved the Office of Educational Technology. Computer Operations (Bob Lunden) now reports to Mr. Anslow's area. Tom Neiss has a new position as Director of Network Planning and Development. Mary Ann Corsetti has been appointed as Director of Contract Development, which reflects Central's more aggressive position towards SUNY-wide volume contracts. A position, Director of Information Technology Planning has been established and an Affirmative Action search will be initiated. These three latter positions and two incumbents will report to John Philippo, Assistant Vice Chancellor for Technology, Planning and Development.
Chuck's memorandum of April 11 was a "Proposal to Evolve Operations in Support of University-Wide Programs." Evolution of the CSSC and Training Centers to provide University-Wide services is consistent and compatible with The Educational Technology Initiative sponsored by the Office of Educational Technology.
Chuck proposes that OET support the transition of the CSSC and TC into University-Wide support centers. OET proposes to support "one time" and "start-up costs" associated with the transition process if continuing costs are sustained by member fees.
Chuck has requested that both Executive Boards participate in developing the new roles of the two centers. Careful examination should be given to:OET funding of full-time Directors at each center Collaboration between OET and Executive Boards to advance educational technology Joint (OET and two centers) efforts to plan, initiate and extend activities supporting University-Wide endeavors.3. Ron Brown initiated discussion relative to the Common SUNY Support Center. Ron indicated that the Affirmative Action search to fill two new CSSC positions should get started in May, 1994. No unusual expenses were expected for the remainder of FY93-94. Based upon a full-time membership charge of $26,000, projected income and expenses for FY94-95 indicate a modest surplus. Projections for FY95-96 and FY96-97 suggest an income stream which is adequate to meet currently known expenses and support modest growth.
4. The Ad Hoc committee report on CSSC Services and Support reflected no change from the material presented at the February, 1994 Executive Board meeting. Bob Wilbert recommended that the report developed by the committee be presented to the Advisory Committee at the COA meeting in June, 1994. Bob recommended that the Ad Hoc committee be re-constituted as a standing committee of the CSSC. Further, because of the compound effect of:rapidly changing technology in relationship to hardware, operating systems, software and compatibility the interest and integral nature of support and service in evolving the CSSC and TC to University-Wide centers and the changing as well as more diverse constituency being supported from the CSSC that we re-evaluate the number of members on a standing committee along with individuals appointed. The standing committee should be prepared to propose its program at Fall '94 COA.5. A discussion of the relationship of Oracle, Banner, Open VMS VAX and Open VMS Alpha took place. The SICAS Center has proposed a migration path for these entities inclusive of a timetable of events for 1994 and 1995 (see attached).
6. Format and content of the next FY93-94 Annual Report was discussed. It was agreed that only summary information relative to service requests placed to the CSSC be included in the report. Service requests per campus will not be published in the report.
7. The SUNYCard program was reviewed in relationship to potential impact upon CSSC, TC and SICAS. No major impact is anticipated at any of the centers noted.
A universal SUNY identifier was discussed. There are apparent differences in opinion in the use of a campus identifier versus a SUNY identifier. This is an issue that BOA must address. Resolution of this identifier issue is not expected to be part of the SUNYCard program structure but will be delayed and addressed by a separate group.
The SUNYCard RFP has been sent to vendors.
8. Renewal activity associated with the SUNY/DEC contract CM00224 is at a standstill. Apparently DEC is going through some reorganizational changes and this is delaying renewal discussion.
Discussion on CM00129 will be initiated in the near future.
Claris is offering a new university program with software discount levels dependent upon quantity of units purchased. Discount break points are at 1,000, 2,500 and 5,000 units. All Claris software is included in this new program.
Discussion followed on the new role of contract development and administration from OET. The UB Micro Store was suggested as a prototype model to assist in establishment of a program.
Executive Software has offered a discount program on their software to the CSSC. The program is initiated with a trial discount of 40 percent offered until 7/31/94. If purchases total $40,000 or more, the 40 percent discount will continue. If $40,000 in purchases is not achieved, discount is reduced to 25 percent. Maintenance/support is offered at 15 percent of list-purchase price.
9. Increased participation by CSSC members is needed. This area becomes more important as technology grows, diversification of environment's increases and the CSSC transitions to a University-Wide support and service facility.
The discussion moved to the role of a full-time Director for the CSSC. Chuck Blunt has requested a recommendation for or against establishing this position. The Acting Director of Computing Services at SUC Buffalo will draft a position paper and submit to the CSSC Executive Board.
10. The Spring '94 COA meeting was discussed. Nominations and election of Chair of Advisory Committee and Executive Board needed for term of office 7/1/94 to 6/30/95.
The Executive Board will meet next at 7 p.m. on 6/5/94 at the Sheraton Liverpool.
The CSSC and TC agreed to maintain a booth at COA.
11. The NYSERNet calling card issue was revisited. This PSI service could provide local dial service with TELNET connect to CSSC Buffalo and set host to local campus. There is a one-time fee of $25 per card plus time charges to the user. Cost to the CSSC is $9,000 annually.
12. This was the last meeting of the Executive Board that Paul Voninski will chair. Paul will be in China when the next meetings of the Advisory Committee and Executive Board take place in June, 1994.
Paul, many thanks for your efforts and interest as Chair of the Common SUNY Support Center Advisory Committee and Executive Board of these past years.
The Executive Board has unanimously consented to allow you to take the minutes at the next Executive Board meeting you attend.
13. The meeting adjourned at about 2:30 p.m. Some members of the Executive Board visited the new TC facilities after adjournment.
Respectfully submitted, Robert J. Wilbert
12 CSSC Support/Services Ad HocCommittee Report, 6/8/94
There seems to be agreement that:- The CSSC cannot be all things to all members. - There is a need to itemize those areas which the CSSC membership wants supported, i.e., a menu of services. - There is a need to categorize the level of support, per product, that the CSSC is expected to provide. - There should be a taxonomy of support levels established which is published to the CSSC members. - There is a need to formalize the direction the CSSC membership wishes the CSSC to take. - There is a need for a periodic review of the services rendered by the CSSC to its constituency. - There is an interest that member campuses, in addition to the CSSC, be more active in providing support services to the CSSC membership. - There is an interest that the scope of services offered by the CSSC be limited or constrained to some specific set of platforms. - There appears to be the implication that member campuses should become, with some products, more self reliant. - It is apparent that our decisions might have impact upon other groups, i.e. SICAS, Training Center, LAIP, FACT and, therefore, we must take these groups into consideration in our recommendations. - There is an interest to develop a process which maintains currency of products supported. - To define and recommend a process whereby the CSSC is guided by its membership in determining the services to be provided. Further, this process must reflect the change which continually occurs in technology, the University and member campuses. Further, the process must include a mechanism to evaluate the quality of services rendered. - In the area of itemizing CSSC supported products, as a starting point, I suggest, we use the GETSOFTWARE list to identify current areas (products) of common interest. This initial list should be reviewed and modified as we collectively agree. Subsequently, the list should be presented to the membership for their input. The end result should be a comprehensive list of products and platforms reflecting not only presently supported products but, perhaps, inclusive of products no longer supported as well as potential future support products. - In the area of categorizing level of support, the product item list noted above should be extended to include a support level for each product identified. - The taxonomy of support levels include: 1. No longer supported by CSSC or member campuses. 2. CSSC support for product distribution only. 3. CSSC support for product distribution and installation. 4. CSSC support for product distribution, installation and limited/general technical support. ("limited/general" needs more precision). 5. CSSC *member* support for installation and limited/general technical support. 6. CSSC support for product distribution, installation and full technical support. 7. Possible CSSC or member support in future. CONSIDERATION: Some relationship between support level and training needs should be made. - I suggest the need to formalize CSSC direction be accomplished by periodic survey of the membership. Further, I suggest, that a standing committee of three members be established to modify and update survey requests, as well as analyze responses and recommend a support/service direction to the CSSC Executive Board. The standing committee would be composed of one CSSC Executive Board member and two people from the current CSSC Advisory Committee membership. Advisory Committee membership should be from campuses not represented on the CSSC Executive Board. I ask that you consider a four month interval between surveys. This area is a little more complex than might be initially perceived. Let's say we start with an updated GETSOFTWARE list. When we pose a question to a CSSC member campus regarding local campus interest in a product, how do we utilize or accommodate the value of a response. We might consider a simple point value system using a scale of 1 thru 5, where 5 is the highest level of interest. If we look at current CSSC membership, this may create some problems. Campus X who is a partial CSSC member for Oracle running on a VM platform might have little interest in VMS-related software. However, the CSSC does have a commitment to campus X and the multitude of VMS members cannot be allowed to negate an Oracle only commitment. A similar condition may develop where campus Y has contracted for VMS support from the CSSC and not Oracle. Also, some equitable solution must evolve where the interest of other SUNY support centers are taken into consideration. It would appear that a more complex evaluation scheme is needed along with the categorization of mandated products versus discretionary product support. CONSIDERATION: This area requires extensive review and development. Example:Product MANDATED DISCRETIONARY Item 1 numerical value 2 numerical value n - The periodic review of services rendered can be incorporated into the above survey. The same standing committee would have responsibility for distribution, collection and analysis of the survey/responses. The standing committee would report its findings to the CSSC Executive Board. I also suggest you consider seeking assistance from an independent professional educator in the development and analysis of survey material. - Consistent with several responses to my earlier e-mail, I suggest we consider a more proactive position from CSSC member campuses in providing support to the general membership. I offer for your consideration: 1. How do we identify that adequate expertise exists to allow a campus or individual to become a CSSC participating member service provider? 2. How should a CSSC participating member service provider be compensated? To campus? To individual? 3. How are services rendered by a CSSC participating member service provider evaluated? - Should the scope of CSSC services be limited; if yes, how do we identify the boundaries? Or, do we change our original perception, intent and implementation of the 17-campus CSSC and view a new CSSC as a University support/service facilitator. Will limiting CSSC services have an impact on existing and future University programs? Facilities management may fall into this area. Facilities management, to me, means the full operational/management responsibility for an information technology facility. There may be on-site responsibility as opposed to remote management. The managed entity might be a small community college, a LAIP site (non-cluster node), or a small specialized college. If we review the cost savings that have been accomplished as a result of establishing the CSSC and other University-wide programs and reasonably project that similar savings can be achieved by broadening membership in existing programs and adding additional University-wide programs, there is little question, in my mind, that the 17-campus perception of the CSSC should change and become a University support center. The difficult task is to incorporate the university support concept into the process we are developing. - How do we make campuses more self reliant? We can do this in several ways. We can increase the number of products in the distribution and installation support category (see above), and decrease the number of products with limited or full technical support. We can be demanding in regard to campus required training on a product. We can implement and pursue a procedure whereby the CSSC refuses to support some lower level of service request question from a campus. We must necessarily be cautious with the last approach. We should not place the burden of refusal upon the CSSC. Remember, this is a member driven support facility; therefore, it is our responsibility to establish guidelines for the CSSC staff to follow. I think I have adequately commented on the need to be sensitive in ourrecommendations with regard to other University groups, i.e., SICAS, LAIP, FACTand the Training Center. I believe a process to maintain currency of supported products and evaluationof services rendered is embedded in the survey, committee structure and reportingfrequency noted earlier. If there are additional components essential toestablishing a process, let me know. Assuming there is agreement on the above, our next task is to formalize anddetail our recommendation for review by the CSSC Executive Board and presentationto the CSSC Advisory Committee. What do we need to do? - Establish support product items list. - Establish a mechanism for campus ranking of each product on the support product item list. - Determine a method of categorizing a support item to a taxonomy classification. - Determine a method of taking individual campus rankings/responses and translating them into something meaningful and equitable regarding CSSC support/services. - Develop survey content for quality of services rendered. - Develop method to analyze survey responses to quality of services rendered.Some general administrative items and thoughts: 1. Is what I have outlined above adequate to pursue in detail,i.e. anything missing? 2. Don't let my outline inhibit your creative thoughts. 3. Event Timetable - Fall '94 COA Implementation Plan. Robert Wilbert, Chair13 Available Software13.1 Digital SoftwareFor a complete list of software products available sign on the CSSC system(sbscva) and type: SOFTWAREA. Directions will then be given to get a list ofall software products available.13.2 Oracle Products Our UNIX platforms to-date are HP-UX, Solaris, SunOS, and IBM's AIX forRS6000. We have also delivered an entire Data General ORACLE product (also UNIX)set at UB. The basic ORACLE product set is also availabe for MAC, OS/2, andNetware. The Cooperative Development Environment (i.e. CDE) product set has alsobeen delivered to several schools. AXP ALPHA OpenVMS Current Product Availability*******************************************************************************CURRENT Alpha AXP OpenVMS U.S. PRODUCT RELEASES (as of 2/4/94)*******************************************************************************PRODUCT V6 Migration V7PROD V7 BETA------- ------------ ------- -------RDBMS 184.108.40.206 220.127.116.11transaction 18.104.22.168 with n/aprocessing option PL/SQL 1.0.38Distributed Option n/a 22.214.171.124Procedural Option n/a 126.96.36.199 with PL/SQL 2.0.17Parallel Server Option n/a 188.8.131.52CDE Oracle Book 1.0.5 Oracle Forms 184.108.40.206 Oracle Graphics 220.127.116.11 Oracle Reports 18.104.22.168CRT 22.214.171.124.3MultiLingual Option 1.0.12 1.0.14Oracle Data Query 126.96.36.199Oracle*Mail 188.8.131.52 184.108.40.206 (includes VMS Mail Gateway)Oracle Terminal 220.127.116.11.3 18.104.22.168.3Pro*ADA 1.4.13 1.5.9Pro*C 1.4.13 1.5.9Pro*COBOL 1.4.13 1.5.9Pro*FORTRAN 1.4.13 1.5.9Pro*PASCAL 1.4.13 1.5.9SQL*Forms 22.214.171.124.2 126.96.36.199.2SQL*Loader 188.8.131.52SQL*Menu 184.108.40.206.2 220.127.116.11.2SQL*Report 18.104.22.168.2SQL*ReportWriter 22.214.171.124.3 126.96.36.199.4SQL*Net V1 188.8.131.52 184.108.40.206SQL*Net Async 220.127.116.11 18.104.22.168SQL*Net DECnet 22.214.171.124 126.96.36.199SQL*Net TCP/IP 188.8.131.52.5 184.108.40.206.5 (Certified on: Wollongong Pathway 1.1(runtime) TGV MultiNet 3.2 DEC TCP/IP Services 3.0-16)SQL*Net VMS Mailbox 1.2.8SQL*Net V2 220.127.116.11SQL*Net DECnet 18.104.22.168SQL*Net TCP/IP 22.214.171.124 (Certified on Wollongong Pathway 1.1(runtime))SQL*Plus 126.96.36.199.2 188.8.131.52.2Util 1.5.10*** Note that current versions on standard VMS are V184.108.40.206 and V220.127.116.11 ***************************************************************** * ORACLE7 for MVS Product Set * * Current Release Levels * * with 18.104.22.168.41 maintenance tape * ***************************************************************** Product Release Level Notes --------------------------------------------------------------------- ORACLE7 Server 22.214.171.124.33 ORACLE7 Maintenance 126.96.36.199.41 * Procedural Option * Distributed Option * PL/SQL 188.8.131.52.0 * CICS Attach 2.0.57 * CICS Attach 2.1.0 2 Precompilers Pro*C 1.5.10 * 1 Pro*COBOL 1.5.10 * Pro*FORTRAN 1.5.10 * Pro*PL/I 1.5.10 * Pro*ADA 1.5.10 * 2 SQL*Forms Version 2 184.108.40.206.52 SQL*Forms Version 3 220.127.116.11.56 * SQL*Menu Version 4 4.1.16 SQL*Menu Version 5 18.104.22.168.56 * Oracle*Mail (server only) 22.214.171.124.50 * Oracle*Terminal 126.96.36.199.55 * Case*Dictionary 188.8.131.52.0 * SQL*Plus 184.108.40.206.1 * SQL*QMX 220.127.116.11.51 SQL*TextRetrieval (TSO Blockmode) 18.104.22.168.57 * SQL*Report 22.214.171.124.51 SQL*ReportWriter 126.96.36.199.55 Oracle Reports 188.8.131.52 * 2 SQL*Net 1.7.2 SQL*Net 3270 184.108.40.206.0 SQL*Net APPC/LU6.2 client 220.127.116.11.6 * SQL*Net APPC/LU6.2 manager 18.104.22.168.6 * SQL*Net DECnet 22.214.171.124.1 SQL*Net DECnet master task 126.96.36.199.0 SQL*Net TCP/IP (IBM) 188.8.131.52.6 * SQL*Net TCP/IP (KNET) 184.108.40.206.0 SQL*Net TCP/IP (IBM) master task 220.127.116.11.6 * SQL*Net TCP/IP (KNET) manager 18.104.22.168.1 SQL*Net TCP/IP TCPaccess 22.214.171.124.0 SQL*Net TCP/IP TCPaccess manager 126.96.36.199.1 SQL*Net VTAM LU0/LU2 188.8.131.52.0 SQL*Net VTAM master task 184.108.40.206.0 SQL*Net 220.127.116.11.41 * APPC KNET TCP/IP IBM TCP/IP SNS TCP/IP NOTES: ------ 1 - Supports IBM C/370 and SAS/C. 2 - Developers Release * - New or updated within this product set ***************************************************************** * ORACLE for MVS Version 6.0 Product Set * * Current Release Levels * * and SQL*Net 18.104.22.168 tape * ***************************************************************** Product Release Level Notes --------------------------------------------------------------------- RDBMS Base 22.214.171.124.60 RDBMS Maintenance 126.96.36.199.61 * Transaction Processing Option 188.8.131.52.61 * PL/SQL 184.108.40.206.0 SQL*Loader 1.1.9 CICS Attach 2.0.56 * Precompilers Pro*C 1.4.14 * 1 Pro*COBOL 1.4.14 * Pro*FORTRAN 1.4.14 * Pro*PL/I 1.4.14 * SQL*Forms Version 2 220.127.116.11.52 SQL*Forms Version 3 18.104.22.168.55 * SQL*Menu Version 4 4.1.16 SQL*Menu Version 5 22.214.171.124.55 * Oracle*Mail (server only) 126.96.36.199.50 Oracle*Terminal 188.8.131.52.54 Oracle Applications 9.3.7 3 (RDBMS 6.0.37 and higher) CASE*Dictionary 184.108.40.206 CASE*Generator 220.127.116.11 SQL*Plus 18.104.22.168.54 * SQL*QMX 22.214.171.124 SQL*TextRetrieval (TSO Blockmode) 126.96.36.199.56 * SQL*Report 188.8.131.52.51 SQL*ReportWriter 184.108.40.206.52 SQL*Net 220.127.116.11 * SQL*Net 3270 18.104.22.168.0 SQL*Net APPC/LU6.2 client 22.214.171.124.0 SQL*Net APPC/LU6.2 manager 126.96.36.199.5 * SQL*Net DECnet 188.8.131.52.1 * SQL*Net DECnet master task 184.108.40.206.0 SQL*Net TCP/IP (IBM) 220.127.116.11.5 * SQL*Net TCP/IP (KNET) 18.104.22.168.0 SQL*Net TCP/IP (IBM) master task 22.214.171.124.4 * SQL*Net TCP/IP (KNET) manager 126.96.36.199.1 SQL*Net TCP/IP TCPaccess 188.8.131.52.0 SQL*Net TCP/IP TCPaccess manager 184.108.40.206.1 SQL*Net VTAM LU0/LU2 220.127.116.11.0 SQL*Net VTAM master task 18.104.22.168.0 NOTES: ------ 1 - Supports IBM C/370 and SAS/C. 2 - Beta 3 - Certified with Oracle MVS RDBMS 6.0.37 and higher * - New or updated within this product set______________________________________________________________________ CURRENT PRODUCTS FOR ORACLE FOR VMProduct Version(s)------- ----------Database and Utilities STANDARD ORACLE7 22.214.171.124.0 PROCEDURAL OPTION 126.96.36.199.0 DISTRIBUTED OPTION 188.8.131.52.0 MULTI-LINGUAL OPTION 184.108.40.206.0 SQL*LOADER 220.127.116.11.0 SQL*DBA 18.104.22.168.0 (line mode) SQL*DBA 22.214.171.124.0 (Beta version) IMPORT/EXPORT 126.96.36.199.0 PL/SQL 188.8.131.52Precompilers Pro*C 1.5.9 Pro*COBOL 1.5.9 Pro*FORTRAN 1.5.9 Pro*PL/I 1.5.9 Pro*REXX 1.7Networking SQL*Net APPC/LU6.2 184.108.40.206.3 SQL*Net APPC/LU6.2 220.127.116.11 (Beta version) SQL*Net TCP/IP (IBM) 18.104.22.168 SQL*Net TCP/IP (IBM) 22.214.171.124 SQL*Net TCP/IP (KNET) 126.96.36.199 SQL*Net 3270 188.8.131.52Toolset Oracle*Terminal 1.0.10 PL/SQL 184.108.40.206 SQL*Plus 220.127.116.11 SQL*Forms 18.104.22.168 SQL*Menu 22.214.171.124 SQL*QMX 126.96.36.199 SQL*Report 188.8.131.52 SQL*Reportwriter 184.108.40.206 ToolKit 220.127.116.11 ToolKit 2.0.7 SQL*Net Availability UpdatePlease note:1. No other 3rd party networking packages and versions of these 3rd partynetworking packages other than the ones listed in this bulletin are supportedby the corresponding SQL*Net product.SQL*Net Version 1=================Notes:1. SQL*Net V1 can only talk to SQL*Net V1. It cannot talk to SQL*Net V2.2. SQL*Net V1 can run against a V6 or V7 database.Product O/S Ver/Status Supported Packages part #------- --- ---------- ------------------ ------SQL*Net for A/UX*******************************************************************************SQL*NetAppleTalk A/UX 18.104.22.168.7 Apple A/UX v3.0 Avail. with Oracle7 Server for A/UX onlySQL*Net TCP/IP A/UX 22.214.171.124.1 Apple A/UX v3.0 Avail.with Oracle7 Server for A/UX onlySQL*Net for DOS*******************************************************************************SQL*Net 3270 DOS v126.96.36.199 IBM 3270 Emulation Prog.V3.0 1750-v1.2 DCA IRMA DCA IRMA II DCA IRMA III DOS v188.8.131.52 Available from WW Supp. prod patchSQL*Net APPC DOS v184.108.40.206 IBM APPC/PC v1.11 8020-1191 ** SQL*Net APPC for DOS will be obsoleted 12/93.SQL*Net Async DOS v220.127.116.11 not applicable 5595-0892SQL*Net DECnet DOS v18.104.22.168 TCI Community DOS A10787-1 v3.0.1 only Digital PathWorks for DOS v4.1SQL*Net IPA DOS v22.214.171.124.0 OSI stack of ICL, Boldon Junees, Finefox & Network Designers Ltd. For Shipment, contact EUROMAN, the Dublin manufacturing centerSQL*NetNamed Pipes DOS v126.96.36.199 LAN Manager v2.0, v2.1, v2.2 Avail w/ORACLE Server for OS/2 or WW Support v188.8.131.52 Lan Manager v2.0, v2.1, v2.2 prod patch Avail from WW Support v184.108.40.206A LAN Manager v2.0, v2.1, v2.2 prod patch Avail from WW Support V3 Install Req'dSQL*Net NetBIOS DOS v220.127.116.11 IBM LAN Support Program 90549-0892 IBM OS/2 v1.3 and 2.0 Avail. standalone or w/ORACLE Server for OS/2 v18.104.22.168A IBM LAN Support Program V3 Install required IBM OS/2 v1.3, v2.0 Avail. - ORACLE7 Server for OS/2 (Lan Server Edition) - WWSSQL*Net SPX DOS v22.214.171.124 Novell NetWare v2.1,v3.11 A10114-2 Avail standalone, w/ORACLE Server for OS/2 or ORACLE Server for NetWare v126.96.36.199A Novell NetWare v3.11 V3 Install required Novell Wkst. Kit for DOS and Windows V2.0 Avail. - ORACLE7 Server for OS/2 (NetWare Edition) - ORACLE7 Server for NetWare - WWSSQL*Net TCP/IP DOS v188.8.131.52 Digital Pathworks for DOS A11037-4 TCP v4.1 ** Supported with SQL*Net TCP for DOS(3COM) driver v184.108.40.206 Excelan LAN WorkPlacev3.5 A11037-4 Novell LWP v4.0,4.01,4.1 Novell LAN WorkGroup (convert utility not necessary) v220.127.116.11 FTP PC/TCP v2.04 - v2.2 A11037-4 v18.104.22.168 Hewlett-Packard ARPA 2.0,2.1 A11037-4 v22.214.171.124 Microsoft TCP v1.0 A11037-4 ** Supported with SQL*Net TCP for DOS(3COM) driver v126.96.36.199 Sun PC/NFS v3.5,4.0,4.0a,5.0 A11037-4 v188.8.131.52 Wollongong runtime TCP A11037-4 v1.1, v1.2 (Wollongong Pathway Access v2.0,v2.1) v184.108.40.206 3Com 3+Open TCP w/DPA v1.1 A11037-4 v1.2 or v2.0 v220.127.116.11 Ungermann-Bass TCP v16.5 A11037-4 ** SQL*Net TCP/IP for DOS (Interlan) will be obsoleted as of 6/1/93. We will continue to support this software for 12 months but it will not be bundled in with the production SQL*Net TCP product. The latest version shipped was v18.104.22.168. It supports Interlan TCP Gateway v1.3 and v1.4.SQL*Net TCP/IP DOS v22.214.171.124.3 ScaNet (part # 9202-22-1) For shipment, contact EUROMAN, the Dublin manufacturing center. ** ScaNet nics can be obtained from Cray Networks.SQL*Net VINES DOS v126.96.36.199 Banyan VINES v4.0 (Bundled w/ ORACLE Server for VINESSQL*Net for Mac*******************************************************************************SQL*NetAppletalk Mac v1.5/prod Available with Mac Server 6143-0792 v188.8.131.52 V184.108.40.206 System 7, 7.1 V3 Install req'd Avail. - standalone or w/ Oracle7 Server for A/UXSQL*Net Async Mac v1.5/prod not applicable 9548-0492 v220.127.116.11.4SQL*Net DECnet Mac v1.5/prod TSSNet v2.4 9545-0293 v18.104.22.168.5 Pathworks for Mac v1.1SQL*Net TCP/IP Mac v1.5 prod A10774Clients v22.214.171.124.7 Apple MacTCP v1.1 (System 7) Apple MacTCP v1.1.1 (System 7, 7.1) v126.96.36.199.7 Novell TCPort v2.2 Both work with System 7 & OFM 2.0 v188.8.131.52.8 Apple MacTCP v1.1 (System 7) V3 Install req'd Apple MacTCP v1.1.1 (System 7, 7.1) Avail. - standalone - w/ Oracle7 Server for A/UXSQL*Net TCP/IP Mac v1.5/prod Apple MacTCP v1.1 (System7) 90784-0492Servers Apple MacTCP v1.1.1 (System7, 7.1)SQL*Net for NT*******************************************************************************SQL*NetNamed Pipes NT v184.108.40.206 Windows NT v3.1Client and Server Avail now w/ Oracle7 Server for Windows NTSQL*Net TCP/IP NT v220.127.116.11 Windows NT v3.1Client and Server Avail. now w/ Oracle7 Server for Windows NTSQL*Net for NetWare*******************************************************************************SQL*Net SPX NW v18.104.22.168 NetWare 3.11Client and Server Available w/Oracle7 Server for NetWare v6.0.36 and v7.0.15 v22.214.171.124 Available from Support v126.96.36.199 NetWare 3.11, 3.12, 4.01 Available w/Oracle7 Server for NetWare v7.0.15 shipping 11/93SQL*Net TCP/IP NW v188.8.131.52 NetWare 3.11, 3.12, 4.01 A10625-1Client and ServerSQL*Net for OS/2*******************************************************************************SQL*Net APPC OS/2 v184.108.40.206 IBM OS/2 EE v1.3 5846-1191Clients v220.127.116.11 IBM OS/2 EE v1.3 or prod. patch IBM OS/2 Extended Services v1.0 or IBM Communications Manager/2 v1.0, v1.1 Available from WW Support v18.104.22.168 IBM OS/2 EE v1.3 or prod. patch IBM OS/2 Extended Services v1.0 or IBM Communications Manager/2 v1.0, v1.1 Available from WW SupportSQL*Net APPC OS/2 v22.214.171.124 IBM OS/2 EE v1.3 5847-1191Servers v126.96.36.199 IBM OS/2 EE v1.3 or prod. patch IBM OS/2 Extended Services v1.0 or IBM Communications Manager/2 v1.0, v1.1 Available from WW Support v188.8.131.52 IBM OS/2 EE v1.3 or prod. patch IBM OS/2 Extended Services v1.0 or IBM Communications Manager/2 v1.0, v1.1 Available from WW SupportSQL*Net Async OS/2 v184.108.40.206 not applicable 9522-0692Clients v220.127.116.11/ supports OS/2 v2.x prod patch Available from WW SupportSQL*Net Async OS/2 v18.104.22.168 not applicable 9521-0692Servers (OS/2 v1.3) v22.214.171.124/ supports OS/2 v2.x prod patch Available from WW SupportSQL*Net DECnet OS/2 v126.96.36.199 Digital Pathworks for 90342-1091Clients OS/2 v2.0 & DEC PCSA v1.1 (supporting OS/2 v1.x) Digital Pathworks for OS/2 v2.0b (supporting OS/2 v1.x, v2.x) v188.8.131.52/ Avail from WW Support prod patchSQL*Net DECnet OS/2 v184.108.40.206 Digital Pathworks for 90341-1091Servers OS/2 v2.0 & DEC PCSA v1.1 (supporting OS/2 v1.x) Digital Pathworks for OS/2 v2.0b (supporting OS/2 v1.x, v2.x) v220.127.116.11 Avail from WW Support prod patchSQL*NetNamed Pipes OS/2 v18.104.22.168/prod LAN Manager v2.0,2.1,2.2 (OS/2 v1.3)Client and Server Avail w/Oracle Server for OS/2 or WW Support v22.214.171.124/ Available from WW Support prod patch (OS/2 v1.3)SQL*Net NetBIOS OS/2 v126.96.36.199/prod IBM OS/2 Extended Edition 90550-0892Client and Server v1.3 (OS/2 v1.3) or IBM Extended Services v1.0 or IBM LanServer v2.0 (OS/2 v1.3 & 2.0) or IBM Lan Server v3.0 (OS/2 v2.x) Avail standalone or w/Oracle Server for OS/2 v188.8.131.52/prod Avail from WW Support v184.108.40.206/prod IBM OS/2 Extended Edition V1.3 (V3 Install IBM LAN Server v1.3, 2.0, 3.0 Req'd) IBM Extended Services V1.0 Avail. - Oracle7 Server for OS/2 (Lan Server Edition) - WWS v220.127.116.11/prod Avail from WW SupportSQL*Net SPX OS/2 v18.104.22.168/prod Novell NetWare v2.1, v3.11 90541-0492Client and Server OS/2 v1.3 and 2.x Avail standalone, w/Oracle Server for OS/2 or Oracle Server for NetWare v22.214.171.124 same as above. Available from WW prod patch Support v126.96.36.199/prod Novell NetWare v3.11 (V3 Install NetWare OS/2 Requester V1.3 revF Req'd) for OS/2 V1.3 NetWare OS/2 Requester V2.0 for OS/2 v2.x Avail. - Oracle7 Server OS/2 (NetWare Edition) - Oracle7 Server for NetWare - WWSSQL*Net TCP/IP OS/2 v1.1 5845-1192Clients v188.8.131.52 3Com 3+Open TCP v1.1, 1.2 v184.108.40.206 IBM TCP v1.2, v1.2.1 (Both drivers support OS/2 v1.x, v2.x)SQL*Net TCP/IP OS/2 v220.127.116.11 ScaNetClients For Shipment, contact EUROMAN,the Dublin manufacturing centerSQL*Net TCP/IP OS/2 v1.1 5844-1292Servers v18.104.22.168 3Com 3+Open TCP v1.1, 1.2 v22.214.171.124 IBM TCP v1.2, v1.2.1 (Both drivers support OS/2 v1.x, v2.x)SQL*VDM OS/2 v126.96.36.199 OS/2 2.1SQL*Net for Windows*******************************************************************************Note: Windows for WorkGroups is supported by SQL*Net if the 3rd party networking software that SQL*Net is running on top of supports it. However, it is still under consideration whether or not the Oracle Windows tools (the CDE tools) are supported with Windows for WorkGroups.SQL*NetNamed Pipes WIN v188.8.131.52 Microsoft Lan Manager 90804-0393 v2.1, 2.1a, v2.2 v184.108.40.206B Microsoft Lan Manager v2.1, 2.1a, v2.2 Avail. - Oracle7 Server for Windows NT - WWSSQL*Net SPX WIN v220.127.116.11 Novell NetWare v3.11 90798-0393 and NetWare WorkStation Kit v2.0 v18.104.22.168 Available from Support A14120-1 prod patch v1.1.2 NetWare Client for MS Windows, A14151-1 V3.01 (bundled with NetWare v3.12 and with NetWare Client for DOS/Windows V1.01)SQL*Net TCP/IP WIN v22.214.171.124 JSB Virtual Socket Library A10403-5 3COM 3+Open TCP v1.1, v1.2, v2.0, - v2.1(winsock) Beame & Whiteside TCP/IP v3.0 Digital Pathworks DOS 4.1 (TCP/IP) Frontier Tech Super-TCP v3.0(winsock) FTP PC/TCP v2.1,v2.11, - v2.2(via FTP V1.06 winsock) HP ARPA Service for DOS v2.0 , v2.1 Microsoft TCP/IP v1.0 (bundled w/ Lan Manager v2.2) NetManage Chameleon TCP v3.1, - v3.11 (winsock) Novell LWP for DOS v4.0,4.0.1, - v4.1 (convert utility not needed) Sun PC-NFS v3.0, 3.5, 4.0a, - v5.0 (winsock) Wollongong Pathway Access v2.0, - 2.1 Ungermann-Bass 16.5, 16.6 IBM TCP v126.96.36.199 (winsock) ** We do NOT support all winsock compliant TCP vendors, only vendors that are listed above. Driver is Wisock v1.1 compliant.SQL*NET VERSION 2=================Notes:1. SQL*Net V2 can only talk to SQL*Net V2. It cannot talk to SQL*Net V1.2. SQL*Net V2 can only run against a V7 database. It cannot run against a V6 database.Note: SQL*Net + a protocol adapter is needed for SQL*Net V2.Product O/S Ver/Status Supported Packages part #------- --- ---------- ------------------ ------SQL*Net for OS/2*******************************************************************************SQL*Net(gen) OS/2 v2.0.15/prod n/a A13636-1ClientsSQL*Net(gen) OS/2 v2.0.15/prod n/a A13647-1ServersMultiProtocolInterchange OS/2 v2.0.15/prod IBM OS/2 V2.x A13641-1SPXAdapter OS/2 v2.0.15/prod A13644-1TCP/IP Adapter OS/2 v2.0.15/prod IBM TCP for OS/2 v1.2 A13645-1 or laterSQL*Net for Windows*******************************************************************************SQL*Net(gen) WIN 2.0.14/prod n/a A13065-1SPX Adapter WIN 2.0.14/prod Novell NetWare v3.11, A13067-1 Novell NetWare Workstation Kit for DOS and Windows v2.0TCP/IP Adapter WIN 2.0.14/prod JSB VSL v2.0 A10366-1 3COM 3+Open TCP v1.1, v1.2, v2.0, - v2.1(winsock) Beame & Whiteside TCP/IP v3.0 Digital Pathworks DOS 4.1 (TCP/IP) Frontier Tech Super-TCP v3.0(winsock) FTP PC/TCP v2.1,v2.11, - v2.2(via FTP V1.06 winsock) HP ARPA Service for DOS v2.0 , v2.1 Microsoft TCP/IP v1.0 (bundled w/ Lan Manager v2.2) NetManage Chameleon TCP v3.1, - v3.11 (winsock) Novell LWP for DOS v4.0,4.0.1, - v4.1 (convert utility not needed) Sun PC-NFS v3.0, 3.5, 4.0a, - v5.0 (winsock) Wollongong Pathway Access v2.0, - 2.1 Ungermann-Bass 16.5, 16.6 IBM TCP v188.8.131.52 (winsock) ** We do NOT support all winsock compliant TCP vendors, only vendors that are listed above. Driver is Winsock v1.1 compliant13.3 Joiner Products
The Joiner product is Jnet NJE. This runs under DECnet and has interfaces forVMSmail and ALL-in-1 mail. Vince Kugler has distributed forms to campuses tofill out and return before this software can be distributed.
ITEC Home Page