** ** ****** ** ** ******** ** ** ***** ** ** ** * ** ** ** *** ** ** ** ** ** * ** ** ** * **** **** ** * ** ** ** ** ** **** ** ** ** ** ** *** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** * ** ** ** ** ** ****** ** ** ** ***** ***** ** ** ** ****** ****** ***** ** **** ******** ****** ****** ** ** ** ** * ** ** * ** ** ** ** ****** **** ** ** ** ** **** ****** ** ** ** ** **** ** ** ** ** ** ** ** ** ** ** ** ** * ** ** ** ** ** ** ** ** ****** ***** ** **** ** ****** ** ** **** KY REGISTER **** KY REGISTER **** KY REGISTER **** KY REGISTER *** MAY 1992 TABLE OF CONTENTS UKCC Short Courses . . . . . . . . . . . . . . . . . . . . . . . 42 Reminder to All Users . . . . . . . . . . . . . . . . . . . . . . 139 MVS Archiving . . . . . . . . . . . . . . . . . . . . . . . . . . 158 New Macintosh Virus . . . . . . . . . . . . . . . . . . . . . . . 176 Everything You Want to Know About Computer Viruses . . . . . . . 195 Prime Bulletin Board . . . . . . . . . . . . . . . . . . . . . . 467 Suggestions . . . . . . . . . . . . . . . . . . . . . . . . . . . 572 Services Directory . . . . . . . . . . . . . . . . . . . . . . . 860 ********************************************************************** UKCC SHORT COURSES The following short courses are free to all UK faculty, staff, and students, but preregistration is required. If you register for a course and then find that you can't attend, please cancel your registration by calling 257-UKCC. Failure to do so may jeopardize your right to register for future UKCC short courses. There are two ways you can register, depending on the class: * You can register online -- some classes require online registration. Just enter VIEW UKCC SHORTCOURSE or VIEW FACTS SHORTCOURSE on your CMS account and follow the menus. * You can register by calling 257-UKCC (this is Voice Mail Exchange; your registration will be confirmed by phone within five days). Many of these classes don't require any knowledge or experience with any computer system. If there are prerequisites for a particular class, they'll be listed in the class description. If you have questions about class content or bypassing prerequisites, call the instructor for that class. INTRODUCTION TO VM/CMS AND XEDIT May 19 and 20 3:00 to 5:00 p.m. 106 McVey Hall A basic introduction to interactive use of the IBM 3090, this class presumes no previous knowledge of the IBM or any other computer system. You'll learn how to access the computer, how to create and manage files on your account, and how to use online tools such as CALENDAR and VIEW. You'll also learn how to use the CMS text editor, Xedit, to create and modify individual files. This course will be taught in two two-hour sessions. Both sessions will provide hands-on practice of the commands that are covered. You'll be given a class computer account which will remain active for the duration of the course. Your instructor will be Chris Corman, 257-2243, chris@ukcc.uky.edu. INTRODUCTION TO ELECTRONIC MAIL ON THE IBM 3090 May 21 3:00 to 5:00 p.m. 106 McVey Hall An introduction to the MAIL command on the IBM 3090, this class is for the beginner. You'll learn how to create mail files and send them to other users on the IBM 3090 as well as to users on the Prime and Wang systems. We'll also cover the use of BITNET to communicate with individuals at other academic centers around the world, and you'll learn how to read incoming mail and some techniques for storing old mail. We'll discuss how to create and maintain a NAMES file of individuals with whom you frequently correspond. You'll learn the log on sequence and some basic CMS background before we begin the discussion of MAIL. This class presumes no previous knowledge of the IBM 3090 or any other computer system. You'll be given a CMS account for the duration of the course and will receive hands-on instruction for all the commands covered. Your instructor will be Chris Corman, 257-2243, chris@ukcc.uky.edu. INTRODUCTION TO VISUAL COMPUTING May 18, 20, and 22 1:30 to 3:30 p.m. 104 McVey Hall This three-session course will introduce you to the fundamental concepts of computer graphics: for presentation, publication, visualization, CAD, etc. Techniques and software systems on a variety of platforms (PC's, UNIX workstations, the IBM 3090 mainframe) will be demonstrated and explained. Typical applications will be examined, and hands-on practice sessions will be provided. No prior computing experience is required; your instructor will be Bob Williamson, 257-2227, robertt@ukcc.uky.edu. INTRODUCTION TO SAS May 27 and 28 3:00 to 5:00 p.m. 106 McVey Hall SAS is a collection of powerful and flexible data management and statistical analysis procedures that allow you to create and analyze libraries of data files on the IBM 3090. This two-session course will emphasize simple data manipulation and general syntax, and is designed for new and inexperienced SAS users. CMS and Xedit knowledge is prerequisite. Your instructor will be Lorinda Wang (ukc333@ukcc.uky.edu, 257-2204), and online registration is required for this course. ********************************************************************* REMINDER TO ALL USERS When you log onto your userid, there is a line of text that tells you the last time someone successfully logged onto your account. The line looks something like this: ACFVLD137I userid LAST SYSTEM ACCESS AT time ON date FROM terminal address This message is displayed for your protection; be sure to read it every time you log onto your account. If you see that someone has logged onto your account after you last logged on, change your password immediately and then contact the UKCC Security Officer, Jack Coffman, at 257-2273, uka051@ukcc.uky.edu, 218 McVey Hall. Make it a habit to check this message each time you log on. ****************************************************************** MVS ARCHIVING MVS archiving celebrates its second anniversary on June 6, 1992. It is run near the beginning of each month and writes each data set which hasn't been referenced in six months to tape, and erases it from the disk. The tapes expire after two years, so the first batch of data archived two years ago will expire this June. There are several ways you can check if any of your data has been archived (data not referenced since December 1989). First of all, you may contact a Consultant at 257-2249, 107 McVey Hall. There are also two files on the Public disk to help with this; make the disk available with the PUBLIC command, and then look at ARCDSNRP and ARCDSNRE. Each has a filetype of JOB. ARCDSNRP prints a report of what's been archived; ARCDSNRE can be used to do a restore. Be sure to specify the MVS logonid in your job. ****************************************************************** NEW MACINTOSH VIRUS INIT-84 is a newly discovered virus that affects machines that are booted on any Friday the 13th. The new anti-viral programs that can protect your Mac from this virus are: Virex 3.7 (commercial) Disinfectant 2.7 (shareware) GateKeeper 1.2.5 (shareware) VirusDetective 5.0.3 (shareware) The UKCC offers free copies of the latest versions of anti-viral software in 107 McVey Hall; just bring a blank diskette. For more information about viruses, contact Jack Coffman at 257-2273, uka051@ukcc.uky.edu. ****************************************************************** EVERYTHING YOU WANTED TO KNOW ABOUT COMPUTER VIRUSES, BUT WERE AFRAID TO ASK: PART ONE This month we'll be publishing the first in a series of articles about computer viruses. For more information about viruses, contact Jack Coffman at 257-2273, uka051@ukcc.uky.edu. What are computer viruses (and why should I worry about them)? The term "computer virus" tends to be used to cover many sorts of computer programs that hide their true (malicious) function and try to spread onto as many computers as possible. While the definitions of the various types of computer viruses (and other malicious software) in this document are certainly useful, it can still be worth keeping a "fuzzy" definition of "computer virus," since preconceived notions as to what a virus is, and what it it exactly does, can lead to a false sense of security. These software pranks are very serious; they are spreading faster than they are being stopped, and even the least harmful of viruses can have serious consequences. For example, a virus that stops a computer and displays a message, in the context of a hospital life-support computer, could be fatal. Even those who created the viruses could not stop them if they wanted to; it requires a concerted effort from computer users to be "virus-aware." What different types of PC viruses are there? Generally, there are two main classes of viruses: the first class describes file infectors which attach themselves to individual programs that are easily copied/transferred between computers. These attack .COM and .EXE programs, though some will infect other classes of program capable of execution (e.g., .DB* and .WK* files). Others can infect any program for which execution is requested such as .SYS, .OVL, .PRG, and .MNU programs. Generally, all file infector viruses will infect either .COM or .EXE programs or both. Common examples are Jerusalem, Sunday, Vienna, 4096, or Whale. The second class is system infectors: those viruses which infect executable code found in specific locations either on a disk or in memory. On DOS systems, for example, most of these viruses infect the Master Boot Record on fixed disks, the DOS Boot Record on both fixed and floppy disks, or the system files (IO.SYS or MSDOS.SYS). Examples include Brain, Stoned, Empire, Azusa, and Michelangelo. Finally, a few viruses are able to infect both (the Tequila virus, for example). What are the symptoms and indications of a virus infection? There are all kinds of symptoms which virus authors have written into their programs, such as messages, music, and graphical displays. These "payloads" may include deleting files, or other destruction. Viruses try to do a lot of spreading before they deliver their payload, but there can be symptoms of virus infection before this, and it is important to use this opportunity to spot and eradicate the virus before any destruction. The main indications are changes to file sizes and contents, changing of interrupt vectors (on a PC), and the unaccounted use of RAM (but, of course, viruses try to hide such effects). On a PC it can be very worthwhile looking at the amount of RAM known to the CHKDSK program, which should be 655,360 bytes (or at least a multiple of 16,384 bytes); boot sector infections are often easily identified to the trained eye (or to heuristic checkers such as CHECKOUT). These symptoms, along with longer disk activity and strange behavior from the hardware, can also be caused by genuine software, or by harmless prank programs, or by hardware faults. The only foolproof way to determine that a virus is present is for an expert to analyze the assembly code contained in all programs and system areas, but this is usually impracticable. Virus scanners go some way towards that by looking in that code for known viruses; some will even try to use artificial intelligence to spot viral activity, but this is usually only reliable for boot sectors. It is wise to arm yourself with the latest anti-viral software, but also to pay close attention to your system: look particularly for any change in the memory map or configuration as soon as you start the computer. For users of MS-DOS 5.0, the MEM program with the /C switch is very handy for this. If you have DR-DOS, use MEM with the /A switch; if you have an earlier version, use CHKDSK or the commonly available PMAP or MAPMEM utilities. You don't have to know what all the numbers mean, only that they change. How many different types of viruses are there? It is not possible to give an exact number because new viruses are being created literally every day. Furthermore, the different anti-virus researchers use different criteria to decide whether two viruses are different or the same. Some count two viruses as two different ones if they differ by at least one bit in their non-variable code; others group the viruses in families, and do not count the closely related variants in one family as different viruses. As of March 1992, there were about 1,200 different IBM PC viruses, about 150 Amiga viruses, about 30 Macintosh viruses, several Atari ST viruses, and a few Apple II viruses. How do viruses spread so quickly? This is a very complex issue. Most viruses don't spread very quickly. Those that do spread widely are able to do so for a variety of reasons. A large target population (i.e., millions of compatible computers) helps, as well as a large virus population, a vendor whose quality assurance mechanisms rely on, for example, outdated virus scanners, and users who gratuitously insert new software into their systems without making any attempt to test for viruses. All of these things are factors. What steps should be taken in diagnosing and identifying viruses? Most of the time, a virus scanner program will take care of that for you. Running it often and on new disks will help identify problems early! If you run into one that the scanner doesn't identify, or doesn't properly clean up for you, first verify that the version you are using is the most recent, and then get in touch with one of the reputable anti-virus researchers and send a copy of the infected file to them, after they ask you to send it. What is a trojan horse? A trojan horse is a program that does something the programmer intended, but that the user would not approve of if he knew about it. Thus, a virus is a particular case of a trojan horse, which is able to spread to other programs (i.e., it turns them into trojans, too). What are stealth viruses (and what's special about them)? Every virus makes changes to executable code; hence, every virus can be detected by checking all executable code in a system for discrepancies between presumed and actual contents. A stealth virus camouflages the changes it has made from detection by other programs, usually by monitoring the system functions used by programs to read files or physical blocks from storage media, and forging the results of such system functions suitably. However, in order to practice "stealth," the virus must be resident in memory. In every "stealth" virus seen so far, this residence is detectable, often easily. Example: One of the oldest MS-DOS viruses, Brain, a boot sector infector, monitors physical disk-I/O and re-directs any attempt to read a Brain-infected boot sector to the disk area where the original boot sector is stored. Countermeasures: To gain unadulterated access to storage media, a clean system is needed so that no virus is present to interfere with its operation. Thus, the system should be built from a trusted, clean master copy before any virus-checking is attempted; this is "the golden rule of the trade." With MS-DOS, boot from your original DOS diskettes (i.e., DOS Startup/Program diskettes from a major vendor that have been write-protected since their creation), and then use only tools from original diskettes until virus-checking has completed. What are polymorphic viruses (and what is special about them)? In order to eradicate a virus infection, all instances of a particular virus in various places (program files, boot records, etc.) have to be found and identified. A program to accomplish this task is called a virus scanner. A polymorphic virus tries to escape virus scanners by producing varied (yet fully operational) copies of itself. One method to evade signature-driven virus scanners is self-encryption with a variable key; however, these viruses (e.g., Cascade) are not termed polymorphic, as their decryption code is always the same and thus can be used as a virus signature even by the simplest, signature-driven virus scanners. One method for a polymorphic virus is choosing among a variety of different encryption schemes requiring different decryption routines: only one of these routines would be plainly visible in any instance of the virus (e.g., the Whale virus). A signature-driven virus scanner would have to exploit several signatures (one for each possible encryption method) to reliably identify a virus of this kind. A more sophisticated polymorphic virus (e.g., V2P6) will vary the sequence of instructions in its copies by interspersing it with "noise" instructions (e.g., a No Operation instruction, or an instruction to load a currently unused register with an arbitrary value), by interchanging mutually independent instructions, or even by using various instruction sequences with identical net effects (e.g., subtract A from A, and move 0 to A). A simple-minded, signature-based virus scanner would not be able to reliably identify this sort of virus; rather, a sophisticated "scanning engine" has to be constructed after thorough research into the particular virus. The advent of polymorphic viruses has rendered virus-scanning an ever more difficult and expensive endeavor; adding more and more search strings to simple scanners will not adequately deal with these viruses. What is the best protection policy for my computer? There is no best anti-virus program. In fact, there is no program that can magically protect you against all viruses. But you can design a whole anti-virus protection strategy and build multiple layers of defense. There are three main kinds of anti-virus detectors, plus several other means of protection, such as hardware write-protect methods. 1) Monitoring programs: these look for viral activity when it happens, such as attempts to write to another executable file, reformat the disk, etc. Examples include FluShot+ (PC) and GateKeeper (Macintosh). 2) Scanners: Most look for known virus strings (byte sequences known to occur in certain viruses, but not in good software), but some use artificial intelligence or heuristic techniques to recognize viral code. They may also include virus removers. Examples are Dr. Solomon's Anti-Virus Toolkit, FRISK's F-Prot, McAfee's VIRUSCAN (all PC), and Disinfectant (Macintosh). 3) Integrity (change-of-state) checkers: These take a snapshot of code, and periodically compare code with the original and (what is supposed to be) uninfected snapshot. Examples include V-Analyst (commercial, BRM Technologies, Israel) and Integrity Master (shareware), both for the PC. In addition, there are mixtures and variations on these approaches, such as resident scanners (e.g., VShield, VIRSTOP) and heuristic search versions (e.g., SCANBOOT). Of course, these are only a few examples. All of them can find their place in the protection against the computer viruses, but you should appreciate the limitations of each method, along with system-supplied security measures that may or may not be helpful in defeating viruses. Ideally, you would arrange a combination of methods that cover the loopholes between them. A typical PC installation might include a protection system on the hard disk's master boot record to protect against viruses at load time (ideally, this would be hardware or in BIOS, but software methods such as DiskSecure and PanSoft's Immunise are pretty good). This would be followed by resident virus detectors loaded as part of the machine's startup (config.sys or autoexec.bat), such as FluShot+ and/or VirStop together with ScanBoot. A scanner such as F-Prot or McAfee's Scan should be put into autoexec.bat to look for viruses as you start up, but this may be a problem if you have a large disk to check (or don't reboot often enough). Most importantly, new files should be scanned as they arrive on the system. If your system has DR-DOS installed, you should use the PASSWORD command to write-protect all system executables and utilities. If you have Stacker or SuperStore, you can get some improved security from these compressed drives, but also a risk that those viruses stupid enough to directly write to the disk could do much more damage than normal; using a software write-protect system (such as provided with Disk Manager or Norton Utilities) may help, but the best solution (if possible) is to put all executables on a disk of their own, protected by a hardware read-only system that sounds an alarm if a write is attempted. If you do use a resident BSI detector or a scan-while-you-copy detector, it is important to trace back any infected diskette to its source; the reason why viruses survive so well is that usually you cannot do this because the infection is found long after the infecting diskette has been forgotten with most people's lax scanning policies. Organizations should devise and implement a careful policy, that may include a system of vetting new software brought into the building and free virus detectors for home machines of employees, students, etc., who take work home with them. Getting More Information VIRUS-L is a moderated, digested mail forum for discussing computer virus issues; comp.virus is a non-digested Usenet counterpart. Discussions are not limited to any one hardware/software platform; diversity is welcomed. Contributions should be relevant, concise, polite, etc. (The complete set of posting guidelines is available by FTP on cert.sei.cmu.edu or upon request.) Please sign submissions with your real name. Send contributions to virus-l@ibm1.cc.lehigh.edu (that's equivalent to virus-l at lehiibm1 for BITNET folks). Information on accessing anti-virus documentation and back issue archives is distributed periodically on the list. Administrative mail (comments, suggestions, and so on) should be sent to krvw@cert.sei.cmu.edu Editor's Note: This article was adapted from the VIRUS-L digest, volume 5, issue 70. ****************************************************************** PRIME BULLETIN BOARD 1. Why isn't the job sheet on VIEW not being updated every week? Having this information online is more convenient than having to physically go to the Employment Office. >>>Thanks for the reminder; we'll notify the people responsible for updating the job sheet on VIEW. 2. How do I identify a terminal with problems if it doesn't have any identification number? >>>In the past the networking people have tried placing various things on the terminals to identify them (stickers on the front, tags on the cabling on the rs232 connection, etc.), but they are always removed and/or defaced. Your best bet would be to either use the LIST NAMES command from the network prompt to get the name of the terminal. If the terminal's condition prevents this, get the names of the terminals next to the bad terminal and use those to indicate the bad terminal. Also, if you are at a site that has a consultant on duty, you can report the terminal problem directly. 3. MCV111 is not printing, nor is it showing up in the spool list. >>>This seems to be a bad network connection. As soon as the NIU for that printer and five of the other terminals in 111 McVey is repaired, the network connection can be checked and repaired. Thanks for keeping us informed. 4. All of the terminals on the table near the door in 111 McVey are slow; three or four character spurts every 30 seconds or so. >>>Networking checked this out and removed the NIU that was causing the problem. There aren't any spare NIUs available to replace the bad one, so the terminals and printer MCV111 connected to it are unusable until the NIU is repaired. We're working on it. 5. Someone is using the computer for games, and the sounds of phasers on overload are very distracting. >>>Any disturbances that take place in any of the PC labs should be reported to one of the lab's consultants. We've forwarded a copy of your complaint to the appropriate people. 6. There is a lack of laser printers available to Prime users. This is very frustrating for the student. I am aware of budget cuts, but is it fair for the students to suffer? One laser printer is just not enough. >>>The laser printer was not functioning properly and was sent to maintenance to be fixed during spring break and has not been returned yet. We are trying to get additional laser printers, and we appreciate your patience and understanding. 7. My account quota was decreased from 750 records to 700; I received no mail or other notiification of this change in advance. Was this due to something that I did, or is this a mistake? >>>We'll take a look at this, but in the meantime, you should start cleaning up unused/old/useless stuff in your account. 8. How can I use FINGER to check when a user logged on? When I use FINGER USERID, it only shows that the user is not logged on. >>>The UKCC node does not report any information other than the user being logged on or off. If the user is logged on, it will give the device number but nothing else. 9. Does the TALK command work? >>>The TALK command is not installed because it was a local tool, i.e., Unix systems have a TALK that works over the internet to other machines. There are already multiple talk-type programs on UKPR. 10. When LESSing a file, instead of pressing the Spacebar or Return, I press the H key. LESS gives me the error message "*help>primos.text>less.hlp unable to open." >>>Thanks for letting us know. HELP for LESS is now available when you press the H key while in LESS. 11. I use LAC to see who can access my directory, and to see someone's userid. Does the message "LUR" mean that that user can access all the files in my directory? >>>We checked the access for your userid, and this is what we found. ACL protecting "": SYSADM: ALL YDU00: ALL .SERVICE: ALL .TCP_FTP$: ALL .UKCC: LUR $REST: U This means that you, the system administrator, the printers, and FTP have access to your space, as well as the consulting group having LIST, ATTACH, and READ access to your space. Anyone else can only ATTACH. This is the default protection for all userids and cannot be altered. ****************************************************************** SUGGESTIONS 1. Update items listed in View more often. Some items are very old and should be deleted. Others, like jobs, are never current. When you use an electronic information system you would think you would be receiving new and current information. >>>Thanks for the reminder; we'll notify the people responsible for updating the information on View. 2. All the short courses on View are old. When will the new course list be shown? I'm interested in the VM/CMS and SAS courses. >>>We are currently scheduling several short courses during May and June. The VIEW UKCC SHORTCOURSE list has been updated. 3. The grant information on View shows "not available." Is there some way to find out more? >>>Thank you for your comments. Problems with the grant listings should be directed to UKRF. Send mail to Anne Fream (UKR200), or call her at 257-2861. 4. Under VIEW ANNOUNCE, the listing for the Master Plan indicates that comment sheets and other such materials are available. This is not the case. Furthermore, the Master Plan is available on a two-hour reserve; I doubt if anyone can read and understand the entire document in two hours. With such a diverse population here at the University, why was it necessary to request outside assitance? >>>Thanks for bringing this to our attention; we'll look into it. 5. Is it possible to set up a file that shows important dates, such as first and last day of classes for each of the terms/sessions, campus holidays, finals week for each term, drop/add dates, and other pertinent dates that are usually printed in the schedule book? >>>Good idea; we'll contact the people responsible for this information. 6. Why not make NOTR the default on the 111 McVey laser printer? Those who want the sheet can ask for it. >>>Thanks for the suggestion. We've considered this in the past, and we'll look into it again. 7. I would like to do a WHOIS for a user at UT Knoxville. Is there a way? (I do not know the node name.) >>>You can find a BITNET node name by sending a message to BITNODES: TELL BITNODES FIND knoxville Use any part of the name that you think will identify the site; "Knoxville" would probably be better than "Tennessee," for example. BITNODES will return a list of node names that match your request. To get more information about a particular node, use: TELL BITNODES NODE nodename where "nodename" is a BITNET node name. BITNODES will return details about the node, including the name and address of the postmaster. 8. Does the UKCC have Unix facilities? How I can use it on UKCC? >>>The UKCC does have a Unix machine available (AIX on the IBM 3090); just contact the User Accounts Services Office at 257-2212 or 257-2217 for information about opening your own AIX account. 9. When I connect from UKnet to UKCC and get one of the new RS6000/MPG ports, I find that the LOGOFF HOLD command no longer retains my UKCC connection but rather drops me back to UKNet. When connecting through an older 7171 port, the HOLD option works as expected. Can this option be made to work with the newer RS6000/MPG ports as well? Thanks. >>>Yes, LOGOFF HOLD does not work with the RS/6000 ports. The reason is that the new ports come in as logical devices, and the HOLD option doesn't work for logical devices (by design). It works fine for real devices like the 7171 ports. We'll look into it and see if there is anything we can do. 10. When I access UKCC from home, sometimes I connect to one of the new ports which identifies itself as UKCCT. There is a problem with the screen. It does not completely wipe out a line as it prints a new line over top of it. Therefore the screen quickly becomes illegible. This is NOT a problem, however, when I exit a program (such as when I exit VIEW or MAIL altogether). At those times, the screen blanks out instantaneously. A second problem: the echo seems very sluggish as I type this. The terminal type that I use is ADM3A (for an old Kaypro console). I can get around the problem by logging on as a TYPETERM, but in that case I can't use the screen commands (PF keys). The old UKCC ports worked fine. >>>This may be a problem with the ADM3A terminal type definition; the UKCCT ports should work the same way as the UKCC ports. We'll check into it. 11. The new RS/6000 log on servers inevitably hang during my attempts to log on to UKCC from a remote PC. This happens right after I respond to the request for terminal type (I specify either a tvi950 or a vt100). I sure hope this can be fixed before all the old 7171s are gone! >>>Check and see if the parity is set correctly for Kermit or whatever terminal program you use on your PC. It should be "none" rather than "even." If the NIU is set to no parity (as most of them are), then set the PC or terminal to no parity. Otherwise, it may work for some things but not for others. Contact Herman Collins at 257-2256 or sysherm@ukcc.uky.edu if you need more help or information. 12. In case you haven't been pestered about this already, UK's license with SAS has apparently expired according to the warning on the SAS output log. Thought someone over there might want to look into this. >>>Thanks; we've taken care of this. 13. Periodically in CMS, when I try to execute CALENDAR or VIEW I get the following message: DMSITP141T Addressing exception occurred at AD0000 in routine MENUEXEC and end up having to re-IPL CMS before I can do anything else. Is there anything that I can change that would limit the result to having the command not work instead of requiring an IPL to fix it? >>>Is there anything you run before CALENDAR or VIEW when they fail? Something, a large something probably, is clobbering the Xmenu segment that they use. Sometimes these conflicts can't be resolved, but NUCXDROP MENUEXEC after the thing causing the segment problem will cause a fresh Xmenu to be loaded when it is needed. 14. As I understand, if a data set on rental disk is not used for six months, it will be copied to tape and deleted from the disk. But if the data set is cataloged and I know the name of the data set, I can still access it (it is retrieved automatically). My question is: How can I get the name of the data set if it has been archived? I don't think it shows up on MAPRENT. >>>There are two files on the Public disk to help with this; make the disk available with the PUBLIC command, and then look at ARCDSNRP and ARCDSNRE. Each has filetype of JOB. ARCDSNRP prints a report of what's been archived. ARCDSNRE can be used to do a restore. Be sure to specify the MVS logonid in your job. 15. I've got a large data set with about 200,000 records in which I need to change just certain strings from one occurrence to a new occurrence. These will only need to be updated once, although a program will be run against the updated files an unspecified number of times. The data set is on tape under MVS. What is the best way to go about changing it? >>>A Consultant in 107 McVey Hall will be glad to help you with this. 16. When I type STATUS from CMS, it is no longer giving me any information on my jobs. Instead, it tells me that I have no active jobs on MVS. This, I know, is false in most cases. It started doing this yesterday. Is there a quick way for anyone to fix this? >>>Thanks for reporting the problem; we've fixed it. 17. Is there any reason not to IPL CMS7? >>>CMS 7 is available for testing. It isn't a production environment; not everything works, things are changing, and there isn't any consulting available. Disconnected userids running CMS 7 may be forced off without notice when updates are made to the software. CMS 7 probably won't be put into production. We are working on CMS 8 now, and it will probably become available over the summer. 18. How do I send a file with lines 110 in length to the Wang? The UKCC mailer truncates the record length before I even send it. >>>There's currently no way to e-mail a file with lines longer than 80 characters to the Wang. You may be able to FTP it; contact a Consultant in 107 McVey Hall for more information. 19. I need to print out a document with more than 132 columns. I have done what I thought I needed to do, yet it doesn't work. I first create a file that has LRECL of 203 (column one for CC characters) on MVS. I then ship it to my reader and accept it. On CMS the file is complete. The column one CC characters show up and my LRECL is 203. Then I say "PRINT / (OV" - the file is sent to my reader. So when I check it in my reader, the CC characters are gone, but I have been chopped down to an LRECL of 132 (not including the CC cloumn, since it isn't displayed here). I tried to print the file by saying "OUTPUT / (pagedef ll202." Why isn't the "PRINT / (OV" sending all 203 columns to my reader? How do I get around this? Thank you. >>>OV is an option for LIST38PP files, those generated for the IBM 3800 page printer and coded in its page description language. Pagedef LL202 does not work from CMS; you must print the job from MVS. Use a job like the following: //PRTLONG JOB ,'yourname' ..INC ACF information if necessary //* //* The following output statements define form layouts, the //* pagedef specifies the line length. The longer the line the //* smaller the characters. //* //* Only the one you use should be de-commented. //* //LONG OUTPUT FORMDEF=STD,PAGEDEF=LL164 //*ONG OUTPUT FORMDEF=STD,PAGEDEF=LL202 //*ONG OUTPUT FORMDEF=STD,PAGEDEF=LL219 //*ONG OUTPUT FORMDEF=STD,PAGEDEF=LL292 //STEP1 EXEC PGM=CJSPREP //SYSPRINT DD SYSOUT=A //SYSUT2 DD SYSOUT=A,DCB=(RECFM=F,LRECL=300,BLKSIZE=300), // OUTPUT=*.LONG,DEST=CENTRAL //SYSUT1 DD * ..INC filename filetype (V /* If you need more help, contact a Consultant in 107 McVey Hall, 257-2249. 20. Can someone please tell me what I need to do to set up a global variable file that will allow a signature on my mail? >>>What you do under RiceMail (the mailer on CMS) is generate a file that contains all the lines you want in the signature. Then add the following code to your MAILUSER XEDIT profile. /* a personal profile */ Arg Mode . Select When (Mode="INITIAL") Then Do End When (Mode="READ") Then Do End When (Mode="SEND") Then Do "MACRO SETMAIL SIGNATURE AUTO" "MACRO SETMAIL SIGNATURE.FILE filename SIGNATUR" /* Be sure to specify your filename in the line above */ /* Also specify the filetype if it is not SIGNATUR */ End When (Mode="MENU") Then Do End Otherwise Nop End 21. I have a data set named "UK.UK05836.TEST" on rental disk. I tried to run a program to give read access to another account MSHAN00, but I was not successful. Is there anything wrong with this program? I appreciate any help you may provide. >>>Try putting 16 *'s after UID(. You can delete a lot of blanks between TEST and UID(. 22. I'm authorized to request 30 MB virtual storage, and sometimes need to. Doing this from within Helper, however, causes the program to crash hard and burn. The only way to recover is to request a forced logoff. Can this be fixed? >>>There certainly is something wrong with large machines and Helper. We can easily reproduce the problem, so it may be easy to fix. In this case, "large" probably means anything bigger than 12 megabytes. In the meantime, about all you can do is restrict yourself to smaller machines while using Helper. 23. You need to set Helper so that Kermit won't choke when the user is logged on remotely through a Series1 protocol converter (i.e., a RISC 6000), and yet will still work when the connection is through a 7171. Outside of Helper, Kermit seems to handle either type of connection with no problem. >>>Helper has problems determining what's on the other end in some cases. It's on the list of things that need attention. 24. I would like to know after I FTP a software named foo.tar.Z or foo.Z, how can I uncompress it and then run it? >>>When you connect to UKCC or ukcc.uky.edu, you are connecting to our CMS machine. We do have a facility for uncompressing .Z files, but a binary or tar file for a non-CMS machine may not do you much good. A Consultant in 107 McVey Hall can help with this. ****************************************************************** UKCC SERVICE DIRECTORY McVey Service E-Mail Address Phone Hall Vice President, Information Services Eugene R. Williams DPS128@UKCC 257-3609 Assoc. VP, University Computing Services Dr. Douglas Hurley HURLEY@UKCC 257-2900 128 Director, Communications Services Doyle Friskney DOYLE@UKCC 257-6225 Director, Center for Computational Sciences Dr. John Connolly CONNOLLY@UKCC 257-8737 324 Director, Academic User Services Dr. Robert S. Tannenbaum RST@UKCC 257-2900 128 Director, Distributed Services Janet Baynham DPS108@UKCC 257-1535 120 Director, Information Resources Dr. Jon Hesseldenz UKA045@UKCC 257-3904 230D Academic Consulting Services Wayne Beech WAYNE@UKCC 257-2238 117 CMS Consulting Bob Crovo CROVO@UKCC 257-2258 109 Complaints Sue Myers SMYERS@UKCC 257-2257 121 Consultant for Remote Sites Wanda Dixon WANDA@UKCC 257-2206 115 Consulting Consultant on Duty SUGGEST@UKCC 257-2249 107 Database - IDMS Rick Chlopan DBA003@UKCC 257-2218 211D Data Center 257-2222 61 Data Entry Frank McCormick OPFRANK@UKCC 257-2216 72 Desktop Publishing Consulting Marguerite Floyd EDITOR@UKCC 257-2219 205 Disk Rental Janet Hyatt HYATT@UKCC 257-2212 130 Larry Johnson JOHNSON@UKCC 257-2217 130 Facilities Operations Joe Williams UKA048@UKCC 257-2231 122 FACTS Center FACTS@UKCCC 257-2275 100 Graphics Consultation Bob Williamson ROBERTT@UKCC 257-2227 207 Information Center Judy Kisil UKA041@UKCC 257-2241 222 Instructional Software Wayne Beech WAYNE@UKCC 257-2238 117 Local Area Networks Gary Porter PORTER@UKLANS 257-5267 Machine Room OPONDUTY@UKCC 257-2222 59 Management Information Systems Forrest Hahn UKA006@UKCC 257-2260 219 Memos and Manuals Consulting Room 257-2249 107 Micro Lab 257-6100 Network/Telecommunications UKT101@UKCC 257-2229 New Accounts Janet Hyatt HYATT@UKCC 257-2212 130 Larry Johnson JOHNSON@UKCC 257-2217 130 Numerical Analysis Consulting Anne Leigh ANNE@UKCC 257-2205 109B Optical Scanner - NCS Chris Corman CHRIS@UKCC 257-2243 109 Bob Crovo CROVO@UKCC 257-2258 109 Passwords Janet Hyatt HYATT@UKCC 257-2212 130 Larry Johnson JOHNSON@UKCC 257-2217 130 Prime Information Steve Stanley STEVE@UKPR 257-2237 207 Program Documentation/Libraries Consulting Room 257-2249 107 Publications Office Marguerite Floyd EDITOR@UKCC 257-2219 205 Refunds Consulting Room 257-2249 107 SAS and SPSS Consulting Lorinda Wang UKC333@UKCC 257-2204 109B Emmanuel Okorley OKORLEY@UKCC 257-3238 109 Security & Disaster Recovery Jack L. Coffman UKA051@UKCC 257-2273 218 Tapes to Borrow, Tape Storage Data Center 257-2222 61 Tours of UKCC 257-2900 User Account Services Janet Hyatt HYATT@UKCC 257-2212 130 Larry Johnson JOHNSON@UKCC 257-2217 130 Vectorization Consulting Anne Leigh ANNE@UKCC 257-2205 109B ************************************************************************* UNIVERSITY COMPUTING ADVISORY COMMITTEE RESEARCH COMPUTING SUBCOMMITTEE Kumble R. Subbaswamy, Chair, 1994 Gregory W. Brock, 1992 Graeme Fairweather, 1993 Robert A. Lodder, 1993 Judith G. Shelling, 1993 Carolyn Brock, 1994 James M. McDonough, 1994 ex officio Delwood Collins John W. Connolly Doyle Friskney Douglas E. Hurley Robert S. Tannenbaum David S. Watt Student (1) INSTRUCTIONAL COMPUTING SUBCOMMITTEE Merrill W. Packer, Chair, 1994 Joel M. Lee, 1992 David J. Shippy, 1992 Anthony Q. Baxter, 1993 Robert L. Fehr, 1993 John E. Christopher, 1994 Kevin S. Kiernan, 1994 ex officio Doyle Friskney Douglas E. Hurley Louis J. Swift Robert S. Tannenbaum VC Academic Affairs, MC VC Academic Affairs CCS Undergraduate Student (1) ADMINISTRATIVE COMPUTING SUBCOMMITTEE Jack B. Jordan, Chair, 1994 David Carter, 1992 Sue Fosson, 1992 Ken Clevidence, 1993 Karen T. Combs, 1993 Randall W. Dahl, 1993 Joan McCauley, 1993 Dale R. Austin, 1994 Daniel L. Fulks, 1994 Nancy Ray, 1994 Walter F. Skiba, 1994 ex officio Doyle Friskney Jon Hesseldenz Roseann Hogan Douglas E. Hurley MC - vacant CCS - vacant *********************************************************************