UNIVERSITY OF CHICAGO Information Systems Policy Policy Number 1 Title/Description - AUTHORIZED USES OF PUBLIC ACADEMIC COMPUTING FACILITIES Effective Date: 8/1/84 Replaces No.: 3/1/84 Applies to: All Academic Computing Facility Users Computing resources at Loyola are shared by a large community of students, faculty, and staff. The following rules are designed to assist in the equitable sharing of these resources, and apply to all computers supported by Academic Computing Services, including public microcomputers: I. Serious Violations: A. Using another user's computer ID for fraudulent purposes such as copying that user's files or giving you [ed: yourself?] access to his/her files is prohibited. In areas where cheating is at issue, student conduct policies also apply. B. Any action which would intentionally jeopardize the availability or integrity of the system is forbidden. C. Attempting to defeat the computer's security system or to use system management facilities without authorization is prohibited. D. Having a computing center advisor write code for you when it is forbidden by an instructor is prohibited. E. Altering or copying software licensed to Loyola University of Chicago without authorization is prohibited. This includes all microcomputer software. II. Authorized Uses: Authorized uses of the computer are listed in the Usermemo, "Authorized Uses of the Computer." Other applications are prohibited, particular using the computer for personal monetary gain. III. Violations: A. Occasional use of computer terminals for game playing may be allowed under the category "Personal computing for the purpose of improving computer literacy" in the USES Usermemo. Unless the game playing is required for a class, such as "Introduction to Computing," you must restrict your use of games to off-peak hours (other than 9 AM to 9 PM weekdays) and must immediately yield terminal to another authorized non-game user. B.Using offensive words to name computer variables and datasets and in the text of terminal messages is prohibited. C. Use of any userid other than your own is a violation, and may be a "serious violation," see above. (Use of another user's subaccount is allowed when doing work on that user's project, however. You may be required to show identification to verify that you are using the correct userid. A userid which is found to have been used by other than its rightful owner will be suspended. IV. Matters of Courtesy: A. Datasets should be kept as small as possible and be deleted if not needed. Unless it is absolutely necessary, do not run more than two simultaneous batch jobs. B. Terminal sessions should be kept to less than one hour if there are users waiting. C. Hogging a terminal just to display job status while others are waiting to use one is strongly discouraged. D. You should be polite when interacting with other users. Scarcity of computer or physical resources may make this difficult, but that is when courtesy is also most critical, especially to first-time users. E. If you do not need a job run on the day you submit it or it uses more than a minute of CPU time and the queues are filled submitting it in CLASS=O (oh) will cause it to be run overnight. This will speed turn-around for those who are waiting. V. Penalties: Violators of these rules are subject to cancellation of subaccounts and userids. Severe and repeated violations are subject to the Code of Student Conduct, the Code of Faculty Conduct, or Personnel Policies, for students, faculty, and staff, respectively, and may result in dismissal from the University. LOYOLA UNIVERSITY OF CHICAGO Information Systems Policy Policy Number 2 Title/Description - RULES OF ETHICAL CONDUCT FOR COMPUTER USE Effective Date: February 1984 Replaces No.: July 1980 Applies to: All Computer Users Computing resources at Loyola are shared by large community of students, faculty, and staff. The following rules are designed to assist in the equitable sharing of these resources, and apply to all computers supported by Academic Computing services, including public microcomputers: 1. Serious Violations: A. Using another user's computer ID for fraudulent purposes such as copying that user's files or giving you [cd: yourself?] access to his/her files is prohibited. In areas where cheating is at issue, student conduct policies also apply. B. Any action which would intentionally jeopardize the availability or integrity of the system is forbidden. C. Attempting to defeat the computer's security system or to use system management facilities without authorization is prohibited. D. Having a computing center advisor write code for you when it is forbidden by an instructor is prohibited. E. Altering or copying software licensed to Loyola University of Chicago without authorization is prohibited. This includes all microcomputer software. 2. Authorized Uses: Authorized uses of the computer are listed in the Usermemo, "Authorized Uses of the Computer." Other applications are prohibited, particular using the computer for personal monetary gain. 3. Violations: A. Occasional use of computer terminals for game playing may be allowed under the category "Personal computing for the purpose of improving computer literacy" in the USES Usermemo. Unless the game playing is required for a class, such as "Introduction to Computing," you must restrict your use of "Introduction to Computing," you must restrict your use of games to off-peak hours (other than 9 AM to 9 PM weekdays) and must immediately yield a terminal to another authorized non-game user. B. Using offensive words to name computer variables and datasets and in the text of terminal messages is prohibited. C. Use of any userid other than your won is a violation, and may be a "serious violation"; see above. Use of another user's subaccount is allowed when doing work on that user's project, however. You may be required to show identification to verify that you are using the correct userid. A userid which is found to have been used by other than its rightful owner will be suspended. 4. Matters of Courtesy: A. Datasets should be kept as small as possible and be deleted if not needed. Unless it absolutely necessary, do not run more than two simultaneous batch jobs. B. Terminal sessions should be kept to less than one hour if there are users waiting. C. Hogging a terminal just to display job status while others are waiting to use is strongly discouraged. D. You should be polite when interacting with other users. Scarcity of computer or physical resources may make this difficult, but that is when courtesy is also most critical, especially to first-time users. E. If you do not need a job run on the day you submit it or it uses more than a minute of CPU time and the queues are filled, submitting it in CLASS=O (oh) will cause it to be run overnight. This will speed turn-around for those who are waiting. 5. Penalties: Violators of these rules are subject to cancellation of subaccounts and userids. Severe and repeated violations are subject to the Code of Student Conduct, the Code of Faculty Conduct, or Personnel Policies, for students, faculty, and staff, respectively, and may result in dismissal from the University. LOYOLA UNIVERSITY OF CHICAGO Information Systems Policy Policy Number 3 Title/Description - Computer Resource Allocation Effective Date: 4/27/87 Replaces No.: 5/1/84 Applies to: All IBM Computer Users The Vice President for Information Systems is responsible for providing and managing computing resources for the entire university. This policy establishes the mechanism under which computing resources will be managed. Description: The Resource Allocation System (RAS) is the management and reporting system for CPU usage on CPU-A (academic, information center, program development and testing), and on batch usage on CPU-B (production and CICS). A CICS reporting interface will be added beginning in Fiscal Year 1988. Reports: The resource allocation system has two major elements: a report component and an allocation component. A usage report is generated for each batch job or TSO/VAM online session at session termination. This report lists the CPU costs in service units and dollars for the associated computer activity. A summary of usage-to-date is also provided. Each month, listed account administrators receive a summary of all CPU service charges for the preceding month and of usage-to-date. These account administrators are usually department heads/department chairpersons. Additional summary reports are also sent to Directors/Deans and division Vice Presidents. If requested, a detailed transaction summary may be printed for any account. This reporting system functions similarly for CPU-A and CPU-B. CPU Allocations: The second component of RAS is an allocation system. The allocation component functions only on CPU-A. The rationale is that activity on CPU-A is discretionary, and may be increased or decreased under direct user control. CPU-B (production) usage increases only on the installation of new/changed application systems. These changes occur under Information Systems control. Information Systems monitors the capacity of CPU-B and will defer new application installations if sufficient CPU power is not available. Computer resources are allocated on a fiscal year basis. Departments request CPU-A computer resource units (KSUs) using budget form IS during March and April of each year. Departmental resource unit requests are subject to the normal budget approval process: department head, component head, and corporate officer. Requests are summarized and presented to the Systems and Computers Steering Committee at the June meeting for approval. The Steering committee insures sufficient resources exist to service the CPU requests and that usage is within the pre-established targets. Usage Control: The CPU-A allocation component of RAS functions on a departmental basis. At the beginning of each University fiscal year, all account usage is cleared and each department is allocated a pool of CPU service units (KSUs). As long a total departmental usage from all accounts remains under the fiscal year KSU allocation computer usage is not impeded. However if the KSU pool is exhausted, Information Systems begins to take steps that will eventually lead the suspension of all computer access for the entire department: (1) Warning letters are sent at the following usage levels: 80, 90 and 100% of allocation. A copy is sent to the next higher level administrator with a KSU transfer form. (2) If warnings are ignored and usage exceeds 100% of allocation, all new account and logonid creation activity is suspended for that department. The rationale is to allow existing work to continue, but prohibit new projects/users from accessing the system. (3) Finally, at the 125% usage level, all departmental accounts will be suspended. This will only be done by a Information Systems staff member after notification of the department. In the over two years of RAS operation, only one department has been "shut-down". The entire RAS system is driven by online ISPF dialogs (full screen programs) allowing users to create accounts, check balances, request detailed reports, validate/invalidate accounts and transfer KSU's interactively. LOYOLA UNIVERSITY OF CHICAGO Information Systems Policy Policy Number 4 Title/Description - Employee Off-Premises Use Of Computer Equipment Effective Date: April 1987 The following terms and conditions shall govern the removal of certain Loyola-owned or leased computer equipment from the University premises and the use of said equipment off premises: 1. All Loyola's equipment removed from the University's premises shall remain the property of Loyola. 2. The employee shall use Loyola's equipment solely for purposes relating to Loyola University business. The employee shall not lend, lease, or sell Loyola's equipment or any part thereof to any other person, firm, or corporation. 3. Loyola's equipment shall be returned to the University premises within one (1) working day after a verbal and/or written request to do so has been issued from the employee's direct supervisor or department chairperson at Loyola. 4. The employee agrees to take reasonable care of Loyola's equipment. The employee further agrees to file a report with the local law enforcement agency, in the event Loyola's equipment is either lost or stolen. 5. If reasonable care is taken and the employee is not negligent, no liability on the part of the employee shall arise from the malfunction or failure of Loyola's equipment while in the employee's possession off premises. 6. There shall be no liability on the part of Loyola arising from consequential damages resulting from the malfunction or failure of Loyola's equipment. 7. Signature approval for off-premises computer use by an employee shall be granted by the department dean or chairperson on an "Off-Premises Use of Computer Equipment Agreement" (page 2). Completion and signature of this Agreement by the employee implies understanding of and compliance with the aforelisted terms and conditions. LOYOLA UNIVERSITY OF CHICAGO OFF-PREMISES USE OF COMPUTER EQUIPMENT AGREEMENT The terms of this Off-Premises Use of Computer Equipment Agreement are those same terms and conditions as outlined in Information Systems Computer Use Policy Number 3, "Off-Premises Use of Computer Equipment". These terms and conditions shall commence as of the date set forth below and shall continue in effect until terminated by either party upon five days prior written notice to the other and return of Loyola's equipment to the University's premises. The Off-Premises Use of Computer Equipment Agreement shall continue to apply to all Loyola's computer equipment off premises prior to the effective date of such termination. This agreement will notify University security that the following item . . . with a serial number of and Loyola equipment inventory control number (if available) of may be removed from Loyola's premises if the agreement has been properly signed and dated. EMPLOYEE LOYOLA UNIVERSITY OF CHICAGO BY: BY: TITLE: TITLE: DATE: DATE: LOYOLA UNIVERSITY OF CHICAGO Information Systems Policy Policy Number 5 Title/Description - Computer Network Effective Date: 3/24/87 Replaces No.: Original Applies to: Computer Network Users 1. Network architecture. Information Systems has established high speed fiber optic and copper communication links between major University buildings at all four campuses. The protocol used on these links is IBM SNA, or EtherNet at the Medical Center. A. Ethernet is only supported at the Medical Center. The preferred network protocol for Medical Center applications that access non-IBM systems is Ethernet. B. IBM SNA protocol support will be provided and will be recommended for applications that primarily access the IBM mainframes. C. Information systems will install and maintain all inter-building and inter-campus network connections. D. New network protocols other than Ethernet or SNA will require Information Systems approval. 2. Network access. All three campuses are linked by high speed T1 (1.544 mb) leased data lines. Each campus has a primary network control center and high speed fiber optic and/or copper links to most major buildings. Network control centers and networked buildings are: Medical Center Network control: Building 104 (Hospital) and Building 105 (Dental School). Linked buildings: High speed links operate in corridor B connecting Building 106 (outpatient), Building 107 (Surgical) and Buildings 117 and 54 (Clinics/offices). An IBM SNA link exists in the Corridor E buildings. ICC Network control: ICC Building, all floors served. A. The cost of access to the network from other buildings must be borne by the connecting user. B. All new building connections will be installed and maintained by Information Systems. C. Switched service (dial-up/PBS) will be provided to support remote network users. Lake Shore Network control: Crown Center Linked buildings: Mertz Hall, Damen Hall, Cudahy Library, Cudahy Science, Flanner Hall, Williams Bldg., Champion Hall. Water Tower Network control: Siedenburg Hall Linked buildings: Lewis Towers, Marquette Center, Law School, 840 and 830 N. Wabash, 14 E. Chestnut, 10 E. Pearson. 3. Network connection. Connection to the SNA or Ethernet (Medical Center only) networks in supported buildings will be provided by Information Systems. The cost of any controllers (SNA) or terminal servers (Ethernet) will be provided by Information Systems. User departments will be responsible for the cost of cabling to the nearest terminal server/controller. A. Connection requests are made via the Terminal Service Request Form available from Data Communications (531-3025). B. Data Communications will provide maintenance and trouble-shooting on network components and links. C. Users will insure that connected equipment is compatible with the network. a. PC's with direct EtherNet/SNA connections must be approved by Information Systems. b. PC LAN gateways should conform to Loyola LAN standards. 4. Network resources. All Ethernet users will have access to the Academic VAX mainframe. All SNA users will have access to the IBM Academic mainframe. Access to other resources will depend on the user's application. A. Information Systems cannot authorize access to application data of departmental computing resources. Each department with computer based application information will designate a person as the security liaison. This person will be able to authorize access to network resources. A directory of liaisons will be available on the general resource processors. B. Data with a broad institutional impact should be stored on one or both of the general resource processors. C. Legitimate requests to access local information should not be denied. 5. Network Interfaces. An interface will exist between the IBM SNA and the DEC Ethernet networks. Applications on the IBM system may be accessed through EtherNet. The reverse is not generally true, although data may be transferred between IBM and DEC processors. A. Users should be connected to the network that will support the majority of their requests (Ethernet/SNA). B. With approval from Information Systems for special cases, users can be connected to both Ethernet and SNA networks (e.g. PC w/Ethernet board and 3278 emulator). 6. Departmental and local area networks (LAN's). A. Currently supported LAN hardware media for new installations are: StarLan (AT&T and Western Digital), and Token-Ring (IBM). B. The standard LAN operating system is Novell's Advanced Netware 86/286/386 using the IPX protocol. C. LAN PC's connection to the VAX system can be accomplished in three ways: Individual nodes with direct RS232 cabling to a DECNET terminal server/controller. A LAN Asynchronous Communications Server with 1-12 connections to a DECNET terminal server/controller. This enables all LAN nodes to access the VAXs. A LAN Gateway with direct interface to VAX via existing infra-structure, allowing all LAN nodes access to the VAX network. This option is under development by Information Systems and should be available in 1987. D. LAN PC's connection to the SNA network can be accomplished in three ways: Individual PC's using a 3278 emulator and directly connected to a 3274. The supported emulators are IBM and Attachmate. LAN Gateways connected directly to a 37X5 communications controller. The gateways serves as a 3274 and each node on the LAN can emulate a 327X terminal. The supported gateway products are IBM and Novell (NAS). PCs on LANs already connected to the VAX Network (as outlined in 6 C.) can gain access to the SNA network via the VAX. E. Separate LANS may be bridged using Novell's internal or external bridge software. The bridges may be user supplied network cable (for short distances between networks) or the Ethernet infra-structure provided by Information Systems. The bridges on the Ethernet cable must use Ethernet network boards. F. Configuration, and installation requests for departmental LANs should be made to Academic Computing and information Center Services. ACS/ICS Technical Services will provide installation, maintenance and trouble-shooting services of LAN components, gateways, and bridges. LOYOLA UNIVERSITY OF CHICAGO Information Systems Policy Policy Number 6 Title/Description - Copyright Laws and Software License Agreements Effective Date: April 1987 Replaces No.: April 1986 Applies to: All Computer Users Loyola University and its community are bound ethically to respect the rights of software developers and legally to abide by the structures of federal copyright laws and the Illinois Software License Enforcement Act that took effect on July 1, 1986. This Act States, in part, that opening a package of software constitutes agreement to comply with all provisions imposed by the developer of the software. It also reinforces the prerogative of a software developer to: limit a user's rights to copy software; define the uses for which software may be copied; dictate the number of copies that can be made. The Act states: A person who acquires a copy of computer software will be conclusively deemed to have accepted and agreed to those provisions of the license agreement (listed on pages 2 and 3) if: (1) A written legend or notice is affixed to or packaged with the copy of computer software and states clearly that use of the copy of computer software will constitute acceptance of the terms of the accompanying license agreement, or that the opening of a sealed package, envelope or container in which the copy of computer software is contained will constitute acceptance of the terms of the accompanying license agreement; and (2) The legend or notice is affixed to or packaged with the copy of computer software in such a manner that the legend or notice is clearly and consipicuously visible so as to be readily noticeable to a person viewing the copy of software and related packaging; and (3) The legend or notice is prominently displayed in all capital letters and in language which is readily understandable; and (4) The legend or notice states clearly that a person who receives the copy of computer software and does not accept and agree to the terms of the accompanying license agreement may, within reasonable time, return the unused, unopened copy of computer software to the party from whom it was acquired, or to some other identified party, for a full refund of any money paid for the copy; and (5) The terms of the accompanying license agreement must be clearly and conspicuously stated in the license agreement in language which is readily understandable, and the license agreement must be attached to or packaged with the computer software or copy thereof in such a manner that the terms are readily noticeable before the act which is deemed to constitute acceptance occurs; and (6) The person acquiring the copy of computer software takes such action as is stated in the legend or notice to constitute acceptance of and agreement to the terms of the accompanying license agreement. (7) No agreement relating to use, return, resale, copying, decompiling, disassembly or other right related to the computer software has been entered into between the person acquiring the computer software and person holding the title thereto. (8) The computer software has not been developed according to the acquirer's specifications or otherwise custom-made either by an outside vendor or an internal department of the acquirer. A person who acquires a copy of computer software that fulfills the requirements listed in items (1) through (5) above, and who fulfills the requirements listed in items (6) through (8) above will be deemed to have accepted the following terms of the Illinois License Software Enforcement Act: (1) Provisions for the retention of title to the copy of computer software by a person other than the person acquiring the software. (2) If title to the copy of computer software has been retained, provisions for the prohibition of any copying of the copy of computer software for any purpose, limitations on the purposes for which copies of the computer software can be made, or limitations on the number of copies of the computer software which can be made. (3) If title to the copy of computer software has been retained, provisions for the prohibitions on translating, decompiling, disassembling, or creating derivative works based on the computer software. (4) If title to the copy of computer software has been retained, provisions for prohibitions on further transfer, assignment, rental, sale or other disposition of that copy or any other copies made from that copy of the computer software. (5) If title to the copy of computer software has been retained, provisions for prohibitions on further transfer, assignment, rental, sale or other disposition of that copy or any other copies made from that copy of the computer software. (6) Provisions for the automatic termination without notice of the license agreement if one of the foregoing provisions of the license agreement is breached. (7) Provisions for award of reasonable attorneys' fees and court costs to the prevailing party in any action or proceeding brought in connection with an alleged breach of one of the foregoing provisions of the license agreement. LOYOLA UNIVERSITY OF CHICAGO Information Systems Policy Policy Number 7 Title/Description - Computing Resource Procurement Effective Date: April 1987 Replaces No.: April 1987 Applies to: All Computer Purchases 1. To procure computing software or hardware using existing department funds A. For requisitions totaling less than $500.00" 1. Employ ordinary department channels for processing a Loyola purchase requisition. B. For requisitions totaling $500.00 or more but less than $7,500.00: 2. Submit completed purchase requisition to one of the following for review and approval: - Director, Academic Computing Services/Information Center Services - Assistant Directors, Academic Computing Services - Associate Director, Information Center Services - Computing Center Manager, Water Tower Campus C. For requisitions totaling $7,500.00 or more: 1. After determining needs, prepare an itemized and detailed Loyola purchase requisition. 2. Submit completed purchase requisition to the following for review and approval: - Vice President, Information Systems 2. To procure computing software or hardware without existing department funds A. Contact one of the following for technical advice: - Communications Manager, Computing Support, Medical Center Campus (regarding mainframe terminals or mainframe data communications) - Computing Center Manager, Water Tower, or Academic Computing Services Assistant Director, Lake Shore (regarding PC hardware or software for academic use, or mainframe academic software) - Information Center Services Manager, Lake Shore (regarding PC hardware or software for administrative use, word processors, or other office support hardware or software) - Systems Development Director, Maywood (regarding administrative software or new systems development) B. Prepare, with assistance of one of the above a "Budget Request for Computer Hardware and Software" form (copy attached). C. Submit request through normal budget requesting channels D. Direct to Vice President, Informations Systems, for review and recommendation to appropriate budget authority. E. If funding is approved, one of the following will have signature and budget control authority, and requested items will be ordered and installed after consultation with requesting office. - Assistant Vice President for Computing (for all mainframe hardware and software and all data communications lines and equipment) - Director, Academic Computing Services/Information Center Services (for all microcomputer hardware and software) F. Because of substantial added costs, microcomputer orders with direct mainframe connections require approval of both: - Assistant Vice President for Computing - Director, Academic Computing Services/Information Center Services