DOCSLIB.ORG

1. Define CP Directory Entry for the SSLSERV Virtual Machine. 2

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
1. Define CP Directory Entry for the SSLSERV Virtual Machine. 2 ------------------------------------------------- ----------------- SSLSERV DIRECT ---------------- ------------------------------------------------- USER SSLSERV XXXXXXXX 128M 1G G ACCOUNT 200 TCPIP CPU 0 BASE CPU 1 1. Define CP directory entry for the IPL 100 SSLSERV virtual machine. IUCV ALLOW IUCV ANY MACHINE ESA 4 OPTION ACCT MAXCONN 1024 QUICKDSP SVMSTAT SHARE RELATIVE 3000 DEDICATE 06D2 06D2 DEDICATE 06D3 06D3 CONSOLE 0009 3215 T MDISK 0100 3390 startcyl 300 volume ------------------------------------------------- --------------- Hercules Linux Host ------------- ------------------------------------------------- [hercuser@zhost tape]$ wget -O- http://wotho.ethz.ch/sslserv/sslserv.agz | zcat >sslserv.aws --2011-12-21 14:31:53-- http://wotho.ethz.ch/sslserv/sslserv.agz Resolving wotho.ethz.ch... 82.130.118.35 Connecting to wotho.ethz.ch|82.130.118.35|:80... connected. HTTP request sent, awaiting response... 200 OK 2. Download and unpack the AWS Length: 51727413 (49M) [text/plain] tape containing the SSL server Saving to: `STDOUT' appliance. Use the procedure 100%[=======================================================>] 51,727,413 24.6M/s in 2.0s shown here or any other method 2011-12-21 14:31:55 (24.6 MB/s) - `-' saved [51727413/51727413] of choice. [hercuser@zhost tape]$ ls -l -rw-r--r-- 1 hercuser hercules 221814258 Dec 21 14:31 sslserv.aws [hercuser@zhost tape]$ ------------------------------------------------- ---------------- Hercules Console --------------- ------------------------------------------------- attach 06D2.2 LCS -n /dev/net/tun -m zv:ms:sl:hw:ad 192.168.118.116 HHCLC073I 06D2: TAP device tap2 opened 3. Attach an LCS device to your z/VM devinit 590 tape/sslserv.aws readonly=1 LPAR (if not already done through HHCTA004I 0590: tape/sslserv.aws is a AWS Format tape file your configuration file). Load the HHCTA066I 0590: option 'readonly' accepted. HHCTA010I 0590: Now Displays: " NT RDY " AWS tape and connect a tn3270 HHCPN098I Device 0:0590 initialized client to the Hercules console HHCTE009I Client 192.168.118.113 connected to 3270 device 0:0702 ------------------------------------------------- port. ---------------- OPERATOR Console --------------- ------------------------------------------------- 11:00:17 HCPRFC2264I Device 06D2 is available and online. 4. Logon user SSLSERV from your 11:00:17 HCPRFC2264I Device 06D3 is available and online. 11:02:49 GRAF 0702 LOGON AS SSLSERV USERS = 20 tn3270 client and attach the tape att 590 sslserv drive from the operator console. 11:04:03 TAPE 0590 ATTACHED TO SSLSERV 0590 ------------------------------------------------- ---------------- SSLSERV Console ---------------- ------------------------------------------------- LOGON SSLSERV 00: z/VM Version 5 Release 3.0, Service Level 0801 (64-bit), 00: built on IBM Virtualization Technology 00: There is no logmsg data 00: FILES: NO RDR, NO PRT, NO PUN 00: LOGON AT 11:02:49 MET SATURDAY 12/17/11 HCPVMI232E IPL UNIT ERROR; IRB 00404017 00000010 00200000 00800000 00: HCPGIR450W CP entered; disabled wait PSW 000E0000 00000232 TAPE 0590 ATTACHED TO SSLSERV 0590 Error messages 00: link maint 190 190 rr 00: DASD 0190 LINKED R/O similar to the green 00: i cms ones are expected DMSIND2015W Unable to access the Y-disk. Filemode Y (19E) not accessed z/VM V5.3.0 2008-05-22 15:06 and can safely be ignored. DMSACP113S A(191) not attached or invalid device address DMSWSP100W Shared Y-STAT not available Ready; T=0.04/0.05 11:06:13 ddr z/VM DASD DUMP/RESTORE PROGRAM ENTER: sysprint cons ENTER: in 590 tape ( leave ENTER: 5. Restore the SSL server appliance out 100 3390 to disk using the DDR utility. ENTER: restore all HCPDDR717D DATA DUMPED FROM SSLSRV TO BE RESTORED DO YOU WISH TO CONTINUE? RESPOND YES, NO OR REREAD: yes HCPDDR711D VOLID READ IS EMPTY DO YOU WISH TO CONTINUE? RESPOND YES, NO OR REREAD: Yes RESTORING SSLSRV DATA DUMPED 12/17/11 AT 09.51.27 GMT FROM SSLSRV RESTORED TO EMPTY INPUT CYLINDER EXTENTS OUTPUT CYLINDER EXTENTS START STOP START STOP 0 299 0 299 END OF RESTORE ENTER: END OF JOB Ready; T=0.23/4.87 11:07:50 system clear 00: Storage cleared - system reset. 00: det 190 00: DASD 0190 DETACHED 00: det 590 00: TAPE 0590 DETACHED 6. Tape drive and CMS system disk ------------------------------------------------- ---------------- Hercules Console --------------- are no longer needed, so clear the ------------------------------------------------- system and detach them. HHCTA010I 0590: Now Displays: "REWINDNG" HHCTA010I 0590: Now Displays: " READY " *FP* HHCTA010I 0590: Now Displays: "UNLOADNG" HHCTA101I 0590: AWS Tape tape/sslserv.aws closed HHCTA010I 0590: Now Displays: " " ------------------------------------------------- ---------------- SSLSERV Console ---------------- ------------------------------------------------- 7. IPL the SSL server appliance. 00: i 100 00: zIPL v1.3.2 interactive boot menu 00: 00: 0. default (SSL_Server) 00: 00: 1. SSL_Server 00: 00: Note: VM users please use '#cp vi vmsg <input>' 00: 00: Please choose (default will boot in 30 seconds): 00: Booting default (SSL_Server)... Linux version 2.6.9-78.EL (builder@c4s390x) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-10)) #1 SMP Mon Aug 4 00:28:36 EEST 2008 We are running under VM (64 bit mode) . The usual chatty Linux boot sequence . Detected 2 CPU's Boot cpu address 0 cpu 0 phys_idx=0 vers=FF ident=000111 machine=2097 unused=0000 cpu 1 phys_idx=1 vers=FF ident=000111 machine=2097 unused=0000 Brought up 2 CPUs . The usual chatty Linux boot sequence cont'd . dasd(diag): 0.0.0100: (4096 B/blk): 216000kB dasda:LNX1/ SSLSRV: dasda1 . The usual chatty Linux boot sequence cont'd . INIT: version 2.85 booting Welcome to CentOS release 4.7 (Final) . The green error . The usual chatty Linux boot sequence cont'd . messages are z90crypt: query_online -> Exception testing device 0 expected and can z90crypt: helper_scan_devices -> exception taken! safely be ignored. CentOS release 4.7 (Final) Kernel 2.6.9-78.EL on an s390x 8. After an automatic login a sslserv login: root (automatic login) password changed is requested. Changing password for user root. New UNIX password: new_password Enter the desired root password Retype new UNIX password: new_password twice. passwd: all authentication tokens updated successfully. [root@sslserv ~]# cd /etc/sysconfig/network-scripts [root@sslserv network-scripts]# cat skeleton_ifcfg-eth0 DEVICE=eth0 9. Change directory and display the ARP=yes skeleton LCS network BOOTPROTO=static configuration file. Cut and paste it BROADCAST=BBB.BBB.BBB.BBB HWADDR=XX:XX:XX:XX:XX:XX from the tn3270 session to your IPADDR=AAA.AAA.AAA.AAA GATEWAY=GGG.GGG.GGG.GGG local editor and edit it to match NETMASK=MMM.MMM.MMM.MMM your network configuration. Set NETTYPE=lcs NETWORK=NNN.NNN.NNN.NNN HWADDR to the unique address ONBOOT=yes used in the ATTACH LCS PORTNAME=0 SUBCHANNELS=0.0.xxxx,0.0.yyyy command in item 3. TYPE=Ethernet [root@sslserv network-scripts]# cat >ifcfg-eth0 DEVICE=eth0 ARP=yes BOOTPROTO=static 10. Paste the edited file line by line BROADCAST=192.168.118.255 HWADDR=zv:ms:sl:hw:ad back to your tn3270 session using IPADDR=192.168.118.116 the cat command. Terminate your GATEWAY=192.168.118.113 NETMASK=255.255.255.0 input with ¬d, the 3270 console NETTYPE=lcs equivalent of Ctrl-D. NETWORK=192.168.118.0 ONBOOT=yes PORTNAME=0 SUBCHANNELS=0.0.06d2,0.0.06d3 TYPE=Ethernet ¬d [root@sslserv network-scripts]# rm skeleton_ifcfg-eth0 rm: remove regular file `skeleton_ifcfg-eth0'? y [root@sslserv network-scripts]# cat ifcfg-eth0 DEVICE=eth0 ARP=yes 11. Remove the skeleton and display BOOTPROTO=static the configuration file just created BROADCAST=192.168.118.255 to verify it’s accuracy. HWADDR=zv:ms:sl:hw:ad IPADDR=192.168.118.116 GATEWAY=192.168.118.113 NETMASK=255.255.255.0 NETTYPE=lcs NETWORK=192.168.118.0 ONBOOT=yes PORTNAME=0 SUBCHANNELS=0.0.06d2,0.0.06d3 TYPE=Ethernet [root@sslserv network-scripts]# cd [root@sslserv ~]# ifup eth0 [root@sslserv ~]# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.169.118.115 * 255.255.255.255 UH 0 0 0 iucv0 12. Now you’re ready to bring the 192.168.118.0 * 255.255.255.0 U 0 0 0 eth0 network interface up. Display the 169.254.0.0 * 255.255.0.0 U 0 0 0 eth0 routing table and the interface default 192.168.118.113 0.0.0.0 UG 0 0 0 eth0 [root@sslserv ~]# ifconfig configurations. Don’t continue eth0 Link encap:Ethernet HWaddr zv:ms:sl:hw:ad until you’ve managed to get the inet addr:192.168.118.116 Bcast:192.168.118.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 green values to match your RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 desired network configuration. collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:336 (336.0 b) iucv0 Link encap:Serial Line IP inet addr:192.169.118.116 P-t-P:192.169.118.116 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MTU:9216 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:50 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) 13. Leave the tn3270 session logged in and continue using a shell lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 window on a (linux-)system, for inet6 addr: ::1/128 Scope:Host example on zhost. The only UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 requirement is that this system TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 can act as a secure shell client collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) and is able to connect to the SSL appliance.
Load more

Recommended publications
  • VALIDATED PRODUCTS LIST 1992 No.2
    NISTIR 4820 (Supersedes NISTIR 4739) VALIDATED PRODUCTS LIST 1992 No. 2 Programming Languages Database Language SQL Graphics GOSIP POSIX Security Judy B. Kailey U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technoiogy Computer Systems Laboratory Software Standards Validation Group Gaithersburg, MD 20899 “QC — TOO .U56 4820 NIST 1992 N I STIR 482 (Supersedes NISTIR 4739) ' O VALIDATED PRODUCTS LIST 1992 No.2 Programming Languages Database Language SQL Graphics GOSIP POSiX Security Judy B. Kailey U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Computer Systems Laboratory Software Standards Validation Group Gaithersburg, MD 20899 April 1992 (Supersedes January 1992 Issue) U.S. DEPARTMENT OF COMMERCE Barbara Hackman Franklin, Secretary TECHNOLOGY ADMINISTRATION Robert M. White, Linder Secretary for Technology NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY John W. Lyons, Director FOREWORD The Validated Products List (formerly called the Validated Processor List) is a collection of registers describing implementations of Federal Information Processing Standards (FTPS) that have been validated for conformance to FTPS. The Validated Products List also contains information about the organizations, test methods and procedures that support the validation programs for the FTPS identified in this document. The Validated Products List is updated quarterly. lii ' " M'- v^,.^.:v;/i'fr•i•:‘fey^^?4 .•:, .V.' ini‘,r^f' isfc'^feV VihV'’, !iV.V I t: 4 #> vm- 'at' Mil! .M'? Of'S8r'»'' SIVS 'V-tv. ','V ..(Vi feiii yA ' r' ' '4: ,. = r,: 0 r^'-' ".V.^l , ;‘ • » JjTT ;»»!£ ... •':«5(4i ' |i“' T" •.(''’'ia\.':l'"' f*l, r-’i"' i'-" '.:"::'.".vi ';... '('?. .;r'H vl. '' ' " .. i.” -' f-j'" , '' '(^ • '.v;.» .
    [Show full text]
  • Hercules General Information
    Hercules System/370, ESA/390, z/Architecture Emulator Hercules – General Information Version 3 Release 06 Contents Contents ........................................................................................................................................................2 Figures...........................................................................................................................................................7 Tables............................................................................................................................................................9 1. Preface .............................................................................................................................................10 1.1 Edition information ........................................................................................................................10 1.2 What this book is about.................................................................................................................10 1.3 Who should read this book ...........................................................................................................10 1.4 What you need to know to understand this book..........................................................................10 1.5 How to use this book.....................................................................................................................10 1.6 Revision Notice .............................................................................................................................10
    [Show full text]
  • The MVS 3.8J Tur(N)Key System
    Terminal CUU0C0 Date 10.11.13 Time 20:00:00 ************ **** ***** || ** ** ** ** ** ||| ** ** ** ** ** |||| ** ** ** || || |l _,,,---,,_ ** ** ** || || ZZZzz /,'.-'`' -. ;-;;, ** **** || || |,4- ) )-,_. ,( ( ''-' ** ***** || || '---''(_/--' `-')_) ** ** ** || || |||||||||| ** ** ** ||||||||||| The MVS 3.8j ** ** ** || Tur(n)key System ** ** ** || ****** **** *** |||||| TK3 created by Volker Bandke [email protected] TK4- update by Juergen Winkelmann [email protected] see TK4-.CREDITS for complete credits MVS 3.8j Level 8505 Logon ===> RUNNING TK4- The MVS 3.8j Tur(n)key 4- System OS/VS2 MVS 3.8j Service Level 8505 Tur(n)key Level 4- Version 1.00 User’s Manual November 2013 ********************************************************************** * * * This User’s Manual applies to the MVS 3.8j Tur(n)key 4- System. * * * ********************************************************************** * * * MVS 3.8j Tur(n)key 4- ("TK4-") is a ready to use OS/VS2 MVS 3.8j * * system built specifically to run under the Hercules System/370, * * ESA/390, and z/Architecture Emulator. It is an extension of the * * original MVS Tur(n)key Version 3 System ("TK3") created by Volker * * Bandke in 2002. See Appendix A for credits and copyrights. * * * * Note: TK4- does not claim to be a new release of the original TK3 * * system, hence its name is TK4-, not TK4. * * * ********************************************************************** * * * Jürgen Winkelmann, [email protected], November 2013 * * * **********************************************************************
    [Show full text]
  • MTS on Wikipedia Snapshot Taken 9 January 2011
    MTS on Wikipedia Snapshot taken 9 January 2011 PDF generated using the open source mwlib toolkit. See http://code.pediapress.com/ for more information. PDF generated at: Sun, 09 Jan 2011 13:08:01 UTC Contents Articles Michigan Terminal System 1 MTS system architecture 17 IBM System/360 Model 67 40 MAD programming language 46 UBC PLUS 55 Micro DBMS 57 Bruce Arden 58 Bernard Galler 59 TSS/360 60 References Article Sources and Contributors 64 Image Sources, Licenses and Contributors 65 Article Licenses License 66 Michigan Terminal System 1 Michigan Terminal System The MTS welcome screen as seen through a 3270 terminal emulator. Company / developer University of Michigan and 7 other universities in the U.S., Canada, and the UK Programmed in various languages, mostly 360/370 Assembler Working state Historic Initial release 1967 Latest stable release 6.0 / 1988 (final) Available language(s) English Available programming Assembler, FORTRAN, PL/I, PLUS, ALGOL W, Pascal, C, LISP, SNOBOL4, COBOL, PL360, languages(s) MAD/I, GOM (Good Old Mad), APL, and many more Supported platforms IBM S/360-67, IBM S/370 and successors History of IBM mainframe operating systems On early mainframe computers: • GM OS & GM-NAA I/O 1955 • BESYS 1957 • UMES 1958 • SOS 1959 • IBSYS 1960 • CTSS 1961 On S/360 and successors: • BOS/360 1965 • TOS/360 1965 • TSS/360 1967 • MTS 1967 • ORVYL 1967 • MUSIC 1972 • MUSIC/SP 1985 • DOS/360 and successors 1966 • DOS/VS 1972 • DOS/VSE 1980s • VSE/SP late 1980s • VSE/ESA 1991 • z/VSE 2005 Michigan Terminal System 2 • OS/360 and successors
    [Show full text]
  • MVS Tools & Tricks
    MVS Tools & Tricks BY SAM GOLOB Retro MVS Computing would bet that five years ago, no one As an aside, I would also like to point out and 574 contain more collected utilities I could have predicted the enormity of that Hercules is a great boon for MVS that work on MVS 3.8. this development. As most revolutionary retirees and for MVS people who do not To find out more about the Hercules ideas go, this one started as someone’s have access to an MVS system. It used to be and MVS 3.8 improvement effort, go to dream and was developed into a workable impossible to work with MVS unless you the Hercules-390 news group at solution to the extent that (even though not had a mainframe or an expensive P/390 at www.yahoogroups.com. The spin-off many people might admit it) it is on the your disposal, and as soon as you would H390-MVS news group is useful as well. verge of making a major impact in the lives leave a company, all substantial MVS work These sites contain downloadable files of MVS systems programmers. would have to stop. Now, it is possible for and programs. This idea, which is not completely in iso- you to set up a complete “turnkey MVS Some of the user-written MVS utilities lation, is the free Linux-based S/390 system” on your home PC in less than 15 written for MVS 3.8 that are new will also instruction simulator called Hercules. minutes under Windows and be able to work on OS/390 and z/OS systems, so we Hercules has been ported to Windows and access TSO.
    [Show full text]
  • Hercules V3.13.0
    Hercules System/370, ESA/390, z/Architecture Emulator Hercules – General Information Version 3 Release 13 Hercules System/370, ESA/390, z/Architecture Emulator Hercules – General Information Version 3 Release 13 First Edition, May 06, 2018 HEGI031300-00 Hercules Emulator V3.13 – General Information Page 2 Contents Contents ........................................................................................................................................................ 3 Figures ......................................................................................................................................................... 10 Tables .......................................................................................................................................................... 12 1. Preface ................................................................................................................................................. 13 1.1 Edition information ........................................................................................................................ 13 1.2 What this book is about ................................................................................................................. 13 1.3 Who should read this book ........................................................................................................... 13 1.4 What you need to know to understand this book .......................................................................... 13 1.5 How to use this book ....................................................................................................................
    [Show full text]
  • Hercules – "Mainframe Iron in Software"
    Hercules – "mainframe iron in software" Jeff Savit Disclaimer • Everything in this presentation is Jeff's opinion, and not that of his employer or anybody else, probably. – So, what else is new? • Also, I am not a lawyer, so don't take anything I say as gospel if it has a legal implication. Or, even if it doesn't What is Hercules? • Software implementation (emulator) of mainframe hardware: – S/370, ESA/390, z/Architecture – a variety of I/O devices • About 110 kloc of multi-threaded C • Open sourced, portable, based on gcc – By Roger Bowler, Jay Maynard, Jan Jaeger, Greg Smith, Volker Bandke, David "Fish" Trout, and other volunteers Why? • If you don't have access to the Real Thing • If you have access to the Real Thing, but in- office time just isn't enough • Development • Hobbyist "retrocomputing" • Major geek value: surprise your friends by showing them MVS on your laptop Hercules Runs on: • Windows 98, NT, 2000 using Cygwin – Provides Unix APIs Herc uses, esp: threads – Go to sources.redhat.com/cygwin • Linux (including Linux/390) – So, you can run Linux under Hercules under Linux under... • Solaris • iMac OS/X • (Rumored) Alpha, OS/2 Emulated Architectures • S/370 – Uniprocessor only • S/390, ESA • z/Architecture (64-bit) • Architecture selected via configuration file or console command Emulated Devices • Local non-SNA 3270 • Printer/console (1052, 3215) • Card reader/punch (2501, 2540, 3505, 3525) • Printer (1403, 3211) • Tape (3420, 3480) • DASD: (3310, 3370, 9336; 2311, 2314, 3330, 3350, 3375, 3380, 3390) • CTCA and networking
    [Show full text]
  • Hercules – User Reference Guide
    Hercules System/370, ESA/390, z/Architecture Emulator Hercules – User Reference Guide Version 3 Contents 1. Preface .............................................................................................................................................13 1.1 Edition information ........................................................................................................................13 1.2 What this book is about.................................................................................................................13 1.3 Who should read this book ...........................................................................................................13 1.4 What you need to know to understand this book..........................................................................13 1.5 How to use this book.....................................................................................................................13 1.6 Revision Notice .............................................................................................................................13 1.7 Readers Comments ......................................................................................................................14 1.8 Legal Advice..................................................................................................................................14 1.9 Trademarks...................................................................................................................................14 1.10 Acknowledgements
    [Show full text]
  • Hercules Installation Guide
    Hercules System/370, ESA/390, z/Architecture Emulator Hercules – Installation Guide Version 3 Release 07 Hercules System/370, ESA/390, z/Architecture Emulator Hercules – Installation Guide Version 3 Release 07 Fourth Edition, November 30, 2012 HEIG030700-03 Hercules Emulator - Installation Guide Page 2 Contents Contents ........................................................................................................................................................ 3 Figures ........................................................................................................................................................... 6 Tables ............................................................................................................................................................ 9 1. Preface ................................................................................................................................................. 10 1.1 Edition information ........................................................................................................................ 10 1.2 What this book is about ................................................................................................................. 10 1.3 Who should read this book ........................................................................................................... 10 1.4 What you need to know to understand this book .......................................................................... 10 1.5 How to use this book ....................................................................................................................
    [Show full text]
  • New Users of Hercules Wanting a VM/CMS Environment by Greg Hartwig (Greg at Hartwig Dot Com), 2004-08
    New Users of Hercules Wanting a VM/CMS Environment by Greg Hartwig (greg at hartwig dot com), 2004-08 I've just gotten through setting up a VM/CMS environment using Hercules as a new user and I found that there seems to be some holes in the documentation. Maybe it was just me, but much of the documentation assumed that I knew stuff that I didn't. So I wanted to write this guide to help others go through this. I hope this is helpful. Installation and setup Installation The first step would be to install Hercules. This will give you a big, empty (fake) IBM mainframe on your desktop but no sofware for it whatsoever. The next step is to get some software! Several operating systems are available (VM, MVS, MVT, Linux), but I'm concerned with VM/CMS here. The good news is that when you're done, you will have a functioning VM and CMS operating system to play with! The bad news is that it's VM/370 R6 from around 1977. That means no XEDIT, no REXX, no EXEC2 even. You will have to become familiar with the EDIT editor and the original EXEC language. Besides Hercules, you will need a 3270 terminal emulator. These are available for every platform (tn3270, x3270, etc.). You will need this to connect to your mainframe. You will probably also need a telnet program. I've gotten by without using telnet but it's a good idea to get that set up also while you're at it.
    [Show full text]
  • Celebrating 50 Years of Campus-Wide Computing
    Celebrating 50 Years of Campus-wide Computing The IBM System/360-67 and the Michigan Terminal System 13:30–17:00 Thursday 13 June 2019 Event Space, Urban Sciences Building, Newcastle Helix Jointly organised by the School of Computing and the IT Service (NUIT) School of Computing and IT Service The History of Computing at Newcastle University Thursday 13th June 2019, 13:30 Event Space, Urban Sciences Building, Newcastle Helix, NE4 5TG Souvenir Collection Celebrating 50 Years of Campus-wide Computing – 2019 NUMAC and the IBM System/360-67 – 2019 NUMAC Inauguration – 1968 IBM System/360 Model 67 (Wikipedia) The Michigan Terminal System (Wikipedia) Program and Addressing Structure in a Time-Sharing Environment et al – 1966 Virtual Memory (Wikipedia) Extracts from the Directors’ Reports – 1965-1989 The Personal Computer Revolution – 2019 Roger Broughton – 2017 Newcastle University Celebrating 50 Years of Campus-wide Computing The IBM System/360-67 and the Michigan Terminal System 13:30–17:00 Thursday 13 June 2019 Event Space, Urban Sciences Building, Newcastle Helix Jointly organised by the School of Computing, and the IT Service Two of the most significant developments in the 65 year history of computing at Newcastle University were the acquisition of a giant IBM System/360-67 mainframe computer in 1967, and subsequently the adoption of the Michigan Terminal System. MTS was the operating system which enabled the full potential of the Model 67 – a variant member of the System/360 Series, the first to be equipped with the sort of memory paging facilities that years later were incorporated in all IBM’s computers – to be realized.
    [Show full text]
  • Kermit User Guide
    KERMIT USER GUIDE Seventh Edition Christine Gianone, Editor Columbia University Center for Computing Activities New York, New York 10027 May 26, 1988 Copyright (C) 1981,1988 Trustees of Columbia University in the City of New York Permission is granted to any individual or institution to use, copy, or redistribute this document so long as it is not sold for profit, and provided this copyright notice is retained. PREFACE Page 1 PREFACE Kermit is the name of a protocol for transferring files from one computer to another over ordinary asynchronous terminal connections. Kermit programs have been written for many different computers, and in general any two computers that have Kermit programs can exchange sequential files correctly and completely. This manual gives a brief and general overview of what Kermit is and how to use it, but consists mostly of detailed instructions for use and installation of specific Kermit programs. For a more detailed introduction to Kermit, complete with illustrations, diagrams, and tutorials, consult the book Kermit, A File Transfer Protocol, by Frank da Cruz, Digital Press, Bedford MA (1987), ISBN 0-932376-88-6, DEC order number EY-6705E-DP (phone 1-800-343-8321). The Kermit book describes Kermit in detail, from the points of view of the beginner, the user, the computer professional who must install Kermit programs or support their use, and the programmer who wishes to write new Kermit implementations. Also included are general introductions to computers, data communications, and file organization, plus a detailed troubleshooting guide, bootstrapping hints, and various appendices and tables. The latter half of the book is taken up by a complete description of the Kermit file transfer protocol, with programming examples in the C language, plus some analysis and comparisons of Kermit with other popular protocols such as Xmodem.
    [Show full text]