1 1 - GENERAL NOTES + _______ _____ - MTS Distribution 6.0 - April 1988 - Note: Installations receiving this distribution of MTS should + ____ obtain approval from the University of Michigan Computing Center before distributing any part of the distribution to any installation other than one of those listed at the end of these notes. In addition some parts of the distribution are copyrighted, either by the University of Michigan or by other organizations. Conditions on the use of copyrighted material vary, but distribution or redistribution to installations other than those listed at the end of these notes is often restricted. - 0 In addition to the general information contained in this writeup, there are two other writeups which give more specific information about installing MTS, one for new and one for existing installations. A hardcopy of the appropriate writeup is included with your distribution tapes; both are available on the tapes as components 461/34 and 461/35. 0 MTS, the Michigan Terminal System, is distributed using three types + _ _ _ of tapes: (1) Dump/Restore tapes for a single-pack MTS system designed to be used as the base system for new installations or for testing and conversion for existing installations, (2) a tape with several utility programs that can be used with the Dump/Restore tapes to build a single-pack system at new installations where no working version of MTS is available, and (3) tapes generated by the MTS *FS program which contain the source, object, command, data, and print files for the system. The Dump/Restore tapes are unlabeled, the utility tape uses standard labels (VOL=MTSUTL), and the *FS tapes are "Volume Label Only" tapes which must be mounted using the keyword LBLTYPE=VLO (VOL=6.0T1, VOL=6.0T2, ...). 0 Throughout the distribution, reference is made to the components of the distribution. Generally these references consist of a 3- or 4-digit component number, usually followed by a slash and a subcomponent number. For example, the MTS accounting system has been assigned component number 104. However, the accounting system actually has many "pieces" and so it consists of well over 100 subcomponents, beginning with number 104/1. From distribution to distribution, a component will almost always have the same number, but subcomponent numbers may be changed. Thus, for example, something may have been distributed on D5.1D with the number 104/15, while on D6.0 it may be 104/16 (this could happen if a subcomponent containing an update were inserted between source and object). 1 2 - New component numbers are assigned by each MTS installation in ranges. The number of a component doesn't necessarily indicate which installation is responsible for its maintenance (there is an installation code for that), just which installation originally assigned the number. 0 The installation assignment ranges are as follows: 0 Range Code Installation Name 0 0001-0999 UM University of Michigan 1000-1199 UBC University of British Columbia 2000-2199 UNE University of Newcastle upon Tyne 2200-2399 UD University of Durham 3000-3199 UQV University of Alberta 4000-4199 WSU Wayne State University 4200-4399 RPI Rensselaer Polytechnic Institute 4400-4599 SFU Simon Fraser University 4800-4999 RIO CNPq/CBPF/GPD (Rio de Janeiro) 9000-9999 UM Used for redistributions only 0 The *FS tapes are generated by the MTS *FS program based on information contained in a data file (known as a driver file), each line of which describes a component (or subcomponent) of the system. Each component has a name, an optional subcomponent name, an installation code, a type code (source, object, MTS commands, etc.), a location (the file name or tape from which it was obtained), a contact person at the installation principally responsible for its maintenance, a locally responsible person (optional), an optional disk name (which gives the file name, if any, on the Dump/Restore pack where this component is also located), and an optional revision level. 0 If a file name in the disk name field has the string "@E" appended, an empty file is moved to the test pack. This is handy for log files which are usually not included on the *FS tapes, but which must be present on the test pack. File names in the disk name field may also include suffixes of the form "@UM" to indicate that the file is to be included on the UM test pack, but is not normally sent out on the standard distribution test pack. 0 Revision level "C" denotes subcomponents which have been changed in the UM production system since they were last distributed. Subcomponents with revision level "N" are new components that have never been distributed. Revision level "U" denotes subcomponents that have been distributed since D5.1 (either on D5.1A, D5.1B, D5.1C, D5.1D) but are unchanged since distributed. Subcomponents with no revision level are those that went out on a regular distribution (D5.1) but haven't changed since then. 0 The driver file editor program, *DEDIT (461/7), may be used to manipulate a driver file. Indexing information is kept in the driver file, which makes the line numbers in the driver file and its associated comment file very important. Care should be used when copying or + ____ changing the file. Finally, only a D5.1 or later version of *DEDIT should be used to change the D6.0 driver file. 0 In the distributed driver file, the local persons, when given, are 1 3 - UM people for non-UM components; other installations should use *DEDIT to fill in its own local names for components assigned to other installations. In this way, a printout may be produced (using the *DEDIT PLIST command) for each programmer, showing the components for which he or she is responsible. This is also a convenient way to inform other installations of who is currently responsible for various components at your installation. 0 Some of the components in the driver file have the letters "UNSP" in the field that indicates the person who is responsible for the component. The ID UNSP exists on the University of Michigan system to provide a common location from which unsupported programs and subroutines can be made available. Most UNSP software is not actively supported by the University of Michigan Computing Center. This means that there are no guarantees about its reliability, performance, or continued availability. UNSP software has received a minimal amount of testing to insure that it operates correctly for most common cases. 0 A number of "dummy" driver file entries have been added for components from other MTS installations that are not installed as part of the production system at UM. These entries are simply an aid in assigning component numbers. 0 As *FS generates the distribution tapes, it adds additional information to each line in the driver file, such as the name of the distribution tape on which it has written the component (tapes are named 6.0Tn), the file number on the distribution tape, a unique name for the component (known as the FS name), information about the file size or tape blocking information if the component was obtained from a regular (non-FS) tape, and the time and date when the file was saved. 0 Components may be obtained from the *FS tapes using the *FS RESTORE command, either by reference to the FSname or to the file number. In distribution mode, if the RESTORE command is given with the parameters "(m) (n) filename", where filename is the name of a driver file which was + ________ used to construct the FS tape, that RESTORE command and all subsequent RESTORE commands which have "(m)" or "(m) (n)" as parameters will use as the new name the original name given in the driver file in columns 59-117. For example, to restore a file with the UM name FDEV:MAKEFILE (on tape 6.0T6, file 1), run *FS in distribution mode from the ID FDEV on the tape 6.0T6. Assuming that you have previously restored the D6.0 driver file to file name DIST:DRIVER, the following command will cause the file to be restored to the name specified in the driver file location field: 0 RESTORE (1) (1) DIST:DRIVER 0 Starting with the D5.0 version, *FS generates checksum information as it saves files on the distribution tape. Previous versions of *FS should accept this checksum information even though they don't normally generate it themselves. 0 Beginning with D5.1, *FS writes tape blocks longer than 4096 characters. However, the D5.1 *FS tapes were generated using an old version of *FS and so do not have long blocks. D6.0 was generated using the D5.1 version of *FS and has long blocks which cannot be read by 1 4 - pre-D5.1 versions of *FS. 0 A printed copy of the driver file listing is included in the distribution. Additional copies of this listing may be printed using the LIST command in *DEDIT. The listing is ordered by component number and includes descriptive comments about each component. The driver file and its associated comment file are on the *FS tapes and on the Dump/Restore pack (in the files DIST:DRIVER and DIST:COMM). 0 A printed copy of the driver file index is also included. It provides an alphabetized list of the components, facilitating use of the driver file listing (which is in numerical order). Additional copies of the index may be printed by copying the appropriate file to *PRINT*. The index is component 461/30 (DIST:INDEX6250 on the Dump/Restore pack). 0 The following components are new since D5.1D (June 1986): 0 539, 641, 705, 930-976 1122-1127, 1140-1146, 1177 4259-4264 1 5 - HIGHLIGHTS OF SIGNIFICANT CHANGES + __________ __ ___________ _______ - ACCOUNTING-RELATED ITEMS + __________________ _____ 0 The following fields have been added to the accounting record since D5.1: - accounting management-level ID - cumulative sums for network, remote message, special forms, and phototypesetter usage, surcharges and royalties - fields for file storage have been expanded from half-words to full-words - Julian times changed to clock units and epoch. 0 The ACCOUNTING subcomponent ACCCONVERT, which calls the ACCCNVRT subroutine, can be used to convert to the current version accounting records. 0 Accounting management has been changed to use the extended accounting file *ACCOUNTINGX instead of *PROJECT and *PRJDIRECTORY (which are still used). The extended accounting file can be generated with the ACCOUNTING subcomponent LVLCONVERT. 0 The statistics records have been changed to allow multiple records per signon. The files created and destroyed information has been deleted. The network optional section has been enhanced; and optional sections for special forms, remote messages, surcharges and royalties, and phototypesetter have been added. The units for VMI have been changed from page-milliseconds to page-seconds. The BILLING subcomponent STACNVRT subroutine can be used to convert statistics records to the current version. - TEXTFORM + ________ 0 Only the object of the version of TEXTFORM currently running at UM is included in this distribution. This does not include the POSTSCRIPT OD. Complete source and updates are distributed directly from UQV. - *FS + ___ 0 The new version of *FS uses variable length blocking on tapes. The current *FS program formats tapes as U(4096), that is, blocks of 4096 or fewer bytes. The new version formats tapes depending on the density of the tape used. The formats are: 8 page blocks ( U(32767) ) for 6250 bpi tapes 4 page blocks ( U(16384) ) for 1600 bpi tapes 1 page blocks ( U(4096) ) for 800 bpi tapes 1 6 - CATALOG REFORMAT + _______ ________ 0 The file system catalog was changed after D5.1 in two significant ways. 0 1) The time and date of the last change to a file's data was added to the information kept in the File Descriptor in the catalog. Previously, only the date of the last change (whether that was a catalog change or a data change) was kept. Users can now use $Filestatus to determine when data last changed: $Filestatus FILE Lastdatachange 0 The entire catalog had to be reformated in order to make this change. The file FILE:FDMOD (482/55) can be used to do the reformatting. 0 2) A flag was added to the File Descriptor to indicate whether the file was to have a Program Product Charge calculated whenever the file was used. (See the Program Product Charge, component 882.) This change did not require a catalog reformat, but one bit was designated for this function in the File Descriptor. - XA + __ 0 MTS can run under the 370 and 370-XA architectures. Under 370-XA, each task is limited to an address space of sixteen megabytes, but all real storage on the machine will be used to support virtual storage. MTS does not (yet) run run under IBM's ESA-370 architecture. - NAMED ADDRESS SPACES + _____ _______ ______ 0 MTS provides Named Address spaces, a facility similar to IBM's Discontiguous Saved Segment support under VM, to allow tasks to share preloaded programs and data. A program may be loaded into a Named Address Space (or NAS) at system IPL-time and then added to or deleted from a task's virtual storage as needed. - EXPANDED STORAGE + ________ _______ 0 MTS will use expanded storage as a high-speed cache to minimize I to DASDI. The cache is store-through; all writes go immediately to disk. However, disk reads will be satisfied from the cache if possible, thereby cutting down the number of real disk I operations required. - VECTOR FACILITY + ______ ________ 0 User programs running under MTS can make use of IBM's vector facility. MTS saves and restores the vector registers for each task, if necessary, and makes the vector instructions available to a job as part of the standard 370 instruction set. - *MESSAGES and FSM + _________ ___ ___ 0 A change was made to the structure of *MESSAGES. Previously, it was not 1 7 - possible to have a message number greater than 2,147,482. By reorganizing the format of *MESSAGES, the limit is increased by a factor of 1000 to well over 2 billion. Distribution 6.0 includes a new version of the Message subroutines and utilities which examine *MESSAGES so that they use the new format. 0 For similar reasons, archive files produced by FSM were constructed in such a way that they could not archive messages numbered beyond 2,147,482. A change was made so that FSM could archive much larger message numbers. FSM now recognizes old files and asks the user to translate such files before allowing access to an archive file. - MTS ENVIRONMENT + ___ ___________ 0 1) Command macro processing is now active by default. To disable, one must $SET MACROS=OFF. The system command macro library, *CMDMACLIB, contains one macro, named MACROLIB, which can be used to easily attach other macro libraries to the MTS environment. To attach a command macro library contained in a file named "CMDMACLIB", issue >MACROLIB CMDMACLIB. 0 2) Notices of incoming electronic mail are posted on the terminal of the recipient. These notices are called MAILCALLs. This feature can be deactivated by issuing $SET MAILCALL=OFF. 0 3) The "execution begins" message and the "execution ends" message now give the same information in interactive and batch mode. 0 4) Most CLSs (Command Language Subsystems) accept a question mark as a wildcard character in the same way that $FILESTATUS does. For example, you can now: $DESTROY A?B $EDIT DOC.?? :ALTER "1987"1988" $RENAME OLD.?.? NEW.?.? 0 New CLSs were added: $FILEMENU (component 876), $MAKE (component 869), $FTP (File Transfer Protocol - component 4263), $DUPLICATE (component 855), $FSM (Full Screen Message - component 1106), $HELP (component 845). 0 6) The Editor defaults to PATTERNS=ON now. Use the Editor command SET PATTERNS=OFF to get the old behavior. 0 7) Some additional $SET options: 0 ERRPROMPT=ON/OFF determines whether MTS should prompt for replacement when it encounters an error. 0 DISPATCH=ON/OFF determines whether immediate messages (dispatches) will be accepted. 0 MAILCALL=ON/OFF determines whether the user should be notified when a new message arrives in his/her mailbox. 0 HELPMODE=Line/Screen determines whether information printed from the $HELP CLS should come out in line mode or whether it should attempt to use full screen mode. 1 8 - NewFileAccess(NFA)=OFF/ determines what access a newly-created file should have. For example: $SET NFA="UNLIMITED W010, READ OTHERS" - FILESAVE + ________ 0 The FileSave process now uses labelled tapes and the Mount subroutine. Changes to *RESTORE were also made to accomodate this change. - CODING CONVENTIONS + ______ ___________ 0 The writeup in COPY:CC*PX (1054/6) describes the current MTS Coding Conventions and gives the history of the other conventions previously in use. 0 All the resident system components which were previously using the old coding conventions have been upgraded to use the current MTS Coding Conventions (most notably, the Disk Manager, the Subtasking Monitor, the Unit Check routines). Most of the post-IPL loaded components which were using the old coding conventionshave also been upgraded to use the current conventions (the Resource Manager and all the Plus CLSs for example). Some notable exceptions are the Edit and Messagesystem subroutines. - RESOURCE MANAGER + ________ _______ 0 The distributed MTS system now contains the Resource Manager which is distributed from UBC. The distributed system does not use the Resource Manager as a spooler for printing, but does use it for Bitnet Support. - NETWORK SUPPORT + _______ _______ 0 The distributed MTS system has support for both the Merit network and the UBCNet network. The installation into the distributed MTS system of the Resource Manager, the Message Multiplexor (MM), the DSPDSR, and the DSP layer of the RM provided the hooks for the UBCNet network. 0 The Mount subroutine, however, is set up to work with the Merit Network, though it has hooks for the UBC HIM. Future plans call for Mount to support both networks; a Mount which works with UBCNet may be obtained from the University of British Columbia, in the meantime. 0 Note that many components of the Merit Network are included in D6.0. However, the Merit folks did not review all their components so this cannot be considered to be an official distribution of the Merit Network. - HIM SUPPORT + ___ _______ 0 The Host Interface Machine (HIM) has been installed at the University of Michigan. The HIM was developed at the Univeristy of British Columbia. The MTS-side software which supports the HIM was developed jointly by the 1 9 - Rensellaer Polytechnic Institute and the University of British Columbia. The 6.0 distribution of MTS contains support for the HIM, which includes the HIM I package, the UDP, TCP, and TLNT DSPs, and the FTP CLS and server. - MTS STARTER SYSTEM + ___ _______ ______ 0 The MTS Starter System is comprised of the basic components of a beginning MTS system. Some of the things done for this Starter setup include: 0 1) Special accounting records have been set up for necessary shared user IDs and for a set of 100 private user IDs. 0 2) CKID has been set up for the shared IDs. 0 3) An initial set of Autostart jobs have been scheduled. 0 4) An initial userdirectory with "Systems Group Fire Fighters" has been created. 0 5) A set of tables which can be used to configure a virtual machine under VM for MTS is included. 0 The DIST:NEWSYS*WF (461/34) writeup describes the Starter System in more detail. - NEW DISK SUPPORT + ___ ____ _______ 0 Changed DASDI to use "Read Device Characteristics" command to determine the size of the disk being formated. This gives us support for any disk supporting this command including: 3380s (Ds and Es have been tested; Js and Ks should work but have never been tested) CMS minidisks (untested) The old FBA disk support has been rejuvenated. 0 MTS now supports internal 9370 disks (9335s have been tested; we have not tested 9332 support). - EXPANDED STORAGE SUPPORT + ________ _______ _______ 0 UMMPS and CONFIG now support IBM's expanded storage. 0 The PDP has been modified to use expanded storage as a primary paging device. This was tested but never used in the production system. 0 The disk manager was modified to use expanded storage (instead of real storage) for the disk cache. TABLES entries can be used to control both the type (XSTORE or REAL) and sizes (min, max, default) of the cache. 1 10 - DSR CHANGES + ___ _______ 0 MTS no longer has a device list following the DSECT. Many DSRs had to be changed to handle this. The biggest change is that the FDUBLN field now points to an FCB instead of containing the LDN for the device. The LDN is obtained from the FCB as are most of the flags in the old device list. - PPC + ___ 0 MTS now contains a program product charging mechanism (component 882) that allows programs to be "surcharged" based on any GUINFO item. The activation of PPC is based on a bit in the file descriptor and a table of charges (in *PPCHARGES at UM). No changes to the program product are required to utilize this feature. - NETWORK SERVERS + _______ _______ 0 MTS now supports a third connection type - Servers (the other two types are Terminal and Batch). Network connections become Server connections when the DSR returns the server name from WAITFOR. 0 For PUBLIC servers, this name is looked up in a table (in the file *NETSERVERS (944/3) at UM). The table contains the name of the server command file ($SOURCEd after the project and user sigfiles), the name of the CCID to charge (if any), and a number of flags. 0 For PRIVATE servers, the system expects a LOGON record containing the above information. 0 See the new write-up on Servers (944/8) for more information. - NO SEPARATE PAGING AND SPOOL PACKS + __ ________ ______ ___ _____ _____ 0 Both HASP and the PDP use files on regular disk packs instead of separate packs. This removes the need for TSS DASDI and SAM packs. - MOUNT COMMAND + _____ _______ 0 The D6.0 version of $MOUNT has minor changes to cope with the new UBC FSUB rewrite, major changes to work with the UNE tape catalog support, and related changes to the format of the PDN table for the tape catalog support. Also, this version has changes related to the No Device List version of MTS. Support for mounting HIM devices and "intertask" pipes has also been added. 1 11 - STARTER SYSTEM ERRORS + _______ ______ ______ 0 The following files appear on the test pack but shouldn't: 0 *PDP8RTN FILE:FILERTNS.REA RSTR:FSRELAB*OA - this is not on the tapes and doesn't work - The Driver File says that the following files are on the test pack but they aren't and they don't need to be. 0 ETC:RMQIF SYS:JSTCMD SYS:HASPRECEIPTS UNSP:PAS.SB.LOG - The following files appear on the test pack but their contents are outdated. However, the versions on the FS tapes are correct. 0 DIST:GENNOTES*WF (461/33) - the document that you are reading DIST:OLDSYS*WF (461/35) - 0 BUG FIXES + ___ _____ 0 Bugs have been fixed in the following files after the tapes were written: 0 *SIGSETUP ETC.:CNVTEREP TRAK 0 The fixes are included in Appendix A. Since this is part of the file DIST:GENNOTES*WF (461/33) on D6.0, they can also be found there. Note that the printed output in Appendix A is not quite right (underscores cause problems, for example, and some lines are truncated) but the file mentioned above contains the correct source for the updates. 1 12 - DESCRIPTION OF THE DRIVER FILE LISTING + ___________ __ ___ ______ ____ _______ - The following is a description of the driver file listing produced by the LIST and PLIST commands in *DEDIT (461/7). A printed copy of the listing is included in the distribution. For each component (or subcomponent), two or three lines of output are printed, followed by any comments associated with the component. - LINE 1 + ____ _ - Num - component number and subcomponent number (if any) + ___ R - revision level (if any) of the component or subcomponent: + _ C, N, U or a blank for D6.0 Component Name - name of the component + _________ ____ Subname - name (if any) of the subcomponent + _______ Type - component type as follows: + ____ B - Binary (BTK=TeX-generated DVI file) C - MTS Commands CM=Command Macros CML=Command Macro Library CE=Commands Editor D - Data DF=$MAKE Dependency File DQL=Definitions Library for Plus H - Help Information HC=CLParser format HF=FSHelp format L - Listing (Same extensions as used for Source) LE - Linkage Editor commands LML - Load Module Library M - Messages (program message file) O - Object OC=unlinkedited OE=linkedited OL=library OV=MVS load modules in VSS format P - Printed Output PL=Line Printer-ready PP=Page Printer-ready S - Source code SA=Assembler SAL=Assembler Source Library SB=Web SC=C Language SE=Reduce SF=Fortran SF6=*FTN (FORTRAN 66) SF7=VS/FORTRAN (FORTRAN 77) SG=GOM SI=ICON SJ=AlgolW 1 13 - SL=LISP SN=Cobol SP=PL1 S3=PL360 SQ=PLUS SQL=Plus Source Library SR=CLparser Grammar S4=Ratfor SS=Spitbol SS4=Snobol4 S*=Snostorm SW=Pascal SX=XPL SY=YACC SZ=Prolog U - Update Deck UC=*CDUPDATE UE=$EDIT UI=*IEBUPDAT UU=*UPDATE UB=WEB Update W - Writeup Input WF=FORMAT WT=TEXT360 WLK=LaTeX WTK=TeX WX=TEXTFORM X - Xerox 9700 XF=form definition XJ=Job Description Library XT=Font Definition G - "Goodness" code + _ G=Good, O=OK, S=Shaky (has bugs), B=Bad (needs rewrite) S - Save control + _ Blank means normal "#" means not distributed "@" means information incomplete "=" means temporary hold ">" means very large component Location - file or tape from which the component was obtained. For + ________ tapes, the first parameter is the rack number, the second and third are the volume name (if labeled) and the tape ID (if different from the volume name), followed by an optional parameter "VLO", denoting a volume-label-only tape. Then follow keywords for the label type, blocking format, and DSNAME (if any). File - the file number if the component was obtained from tape + ____ (optional for labeled or *FS tapes). 1 14 - LINE 2 + ____ _ 0 6250 Tape - name of 6250 BPI distribution tape on which the + ____ ____ component was saved 6250 File - *FS file number on the 6250 BPI distribution tape + ____ ____ FS Name - FS name assigned to component as it was saved + __ ____ Ver - *FS version number assigned to component as it was saved + ___ Ftype - the file type (LINE or SEQ) + _____ LRECL - the maximum record length of the component + _____ Size - the size of the component (in pages if the DevT field is + ____ PAGE, in tracks if DISK) DevT - the device type from which the component was obtained + ____ (PAGE for non-FS tapes and files, DISK for items obtained from older (before the page-formatted file system) *FS tapes) Inst - installation code for the installation responsible for + ____ maintenance Person - the person responsible for the component at the + ______ installation given in the SHARE field Local Per - the person responsible for the component at the + _____ ___ local installation Date and Time - date and time component was saved + ____ ____ - 0 LINE 3 + ____ _ 0 1600 Tape - name of 1600 BPI distribution tape on which the + ____ ____ component was saved 1600 File - *FS file number on the 1600 BPI distribution tape + ____ ____ 0 NOTE: Currently there are no MTS installations requiring 1600 BPI tapes, so no 1600 BPI version of D6.0 was written when the original version was sent out. A 1600 BPI version will be generated later if it becomes necessary. 0 Disk Name - name of the file (if any) on the Dump/Restore test + ____ ____ pack where the component is located (the save control field controls whether it is also on the *FS tapes). One of four modifiers may be added to this field: @E indicates that the file is to be empty when it is moved to the Dump/Restore pack; @UM indicates that the file is to go be included on the UM Dump/Restore test, but is not normally sent out on the standard distibution pack; @MN indicates the file is a Merit Network file; and @ST indicates that the file is part of the MTS Starter System which includes special accounting files and user documentation, such as *GENDOC, for example. 1 15 - USE OF DASDI and DISKCOPY + ___ __ _____ ___ ________ 0 The disk format in use in MTS for the MTS file system is VAMX. It is slightly different than the TSS VAM2 format that was used in the MTS file system for many years or the old VAMX format which was used by several MTS installations when they first began using 3350 type disks. The SAM disk format can be used by HASP for its spool pack(s), though MTS 6.0 HASP has been upgraded to use MTS files as spool extents. 0 The MTS DASDI and DISKCOPY programs are provided to initialize and restore disks. The MTS DASDI program (component 598) may be used to initialize VAM2 and VAMX format disks. The program uses RDC (read device characteristics) so that it should initialize any VAM2 or VAMX format disks. It has been tested with the following devices: 2301, 3330-I, 3330-II, 7330, 3340, 3344, 3350, 3370 , 3375, 3380, 6280, 9332, 9335, and VM minidisks. 0 The MTS DISKCOPY program (component 724) may be used to dump, restore, or copy VAM2 and VAMX format disks. DISKCOPY can be used on any disk which can be DASDId with the following exceptions: 2311 and 2314 disks require proper unit check routines to be developed. Diskcopy does not write track 0 (the label) for FBA devices. 0 These programs are located in the files FILE:DASDI*OA (598/3) and FILE:DISKCOPY*OA (724/3) and are included on the *FS distribution tapes, the Starter System Dump/Restore tapes, and the utility tape. They require a working version of MTS to run. For existing MTS installations, this should be no problem. New installations must use a special version of MTS that will work without a disk subsystem to run these programs (see the instructions for new installations for details (461/34)). 0 MTS file system volumes are normally labeled MTS001, MTS002, etc. and must be VAMX (VX) format. The public volume number for the first pack in the system must be 1 and go up by one for each additional pack. No two packs at an installation should have the same volume label and the + ___ same public volume number. If you are running DASDI or DISKCOPY on your production system, the SLOW option may be used to keep the program from monopolizing the disk system. 0 The MTS DASDI program will initialize a pack in either VAM2 or VAMX format. Directions for running DASDI are given in the MTS Operator's Manual (592) and in the writeup in FILE:DASDI*WF (682/6). 0 The following example initializes the pack on D001 as a VAMX pack with volume label MTS501 and public volume 1. The underlined lines are input. 0 $run file:dasdi*oa+copy:sysdefs prot=off + ____ __________________________ ________ Execution Begins MTS DASDI PROGRAM (VERSION). ENTER INPUT LINE: Dddd llllll Vx #/PAGING/PRIVATE pars ... d001 mts501 vx 1 slow ipl + ____ ______ __ _ ____ ___ D001 CURRENTLY LABELED AS "NEW001". PLEASE CONFIRM. ok + __ PAT TO BE WRITTEN ON PAGES X'009178' THRU X'00918A'. NEXT? 1 16 - $endfile + ________ Execution Terminated - The MTS DISKCOPY program may be used to copy VAM2 and VAMX disk data from pack to pack as well as to and from tapes. The program will not convert VAM2 format data to VAMX format or vice-versa. It will copy from one disk type to another (3330 to 3350 or 3330-11 to 3330-1 for example) as long as the "to" volume is large enough to hold all of the data and there is sufficient space in the PAT for any relocation entries needed. 0 Instructions for running DISKCOPY may be found in the writeup in FILE:DISKCOPY*WF (724/4). The following example shows a tape-to-disk restore. The underlined lines are input. 0 $run file:diskcopy*oa+copy:sysdefs prot=off Execution begins Enter "FROM" device type (DISK/TAPE): tape + ____ Enter tape device or pseudo-device names(s): >T908 + _____ Enter "TO" device type (DISK/TAPE): disk + ____ Enter device name and volume label (Dxxx MTSyyy): d008 mts501 + ____ ______ Enter options (SLOW, SWAP, IPL): slow swap ipl + ____ ____ ___ Volume copied: 29453 data pages copies, 2 relocations Enter "FROM" device type (DISK/TAPE): $endfile + ________ Execution terminated 0 The SLOW option keeps the program from monopolizing the disk system. The SWAP option causes the volume label on the "TO" device to be replaced with the volume label from the "FROM" device (in a disk-to-disk copy both labels would be changed). The IPL option causes any IPL records to be copied. IPL records are always included on a disk-to-tape copy, but are not normally included on a tape-to-disk or disk-to-disk copy. These IPL records should not be confused with the IPLAREA data used by the IPLREADER, both types of IPL data are needed. More than one tape device may be specified at a time, but this is not required even when the Dump/Restore data spans more than one tape reel. 1 17 - PATCHING THE SYSTEM + ________ ___ ______ - Patching Shared Memory + ________ ______ ______ 0 Find out where the deck to be patched is loaded by checking a current map, by checking the file SEG2:S2MAP, or by using the LOADINFO CLS (enter the MTS command "$INFO" from a privileged user ID, i.e., an ID that can set PROT=OFF). 0 Use the System Status Routine (SSRTN) command 0 DISPLAY loc[+disp[+disp ...]] [n] 0 to display memory and the SSRTN command 0 MODIFY loc[+disp[+disp ...]] value[[,]value ...] 0 to change it. For example 0 DISPLAY 218500+6DBA 0 MODIFY 218500+6DBA 47F0 0 These SSRTN commands are legal from the 3270 operator's console when prefixed with a slash (/), as input to the JOBS job which may be run from any operator's console, or as input to the $SYSTEMSTATUS command when signed on using a privileged MTS user ID. For a complete description of these and the other privileged SSRTN commands see the MTS Operator's Manual (component 592). 0 SDS or PEEK may also be used to modify shared memory when used from a privileged ID. In addition, the supervisor commands DIS and MOD may be used to display and modify routines loaded into unpaged memory (segment 0), but these commands are not legal when issued from a 3270 operator's console. 0 The IPLREADER has commands which allow a system to be patched at IPL time. See the IPLREADER description (1021/13) for more information. - Patching the System Object Deck + ________ ___ ______ ______ ____ 0 Using RAMROD (MTS:RAMROD), CREATE a new system from the current + ______ system or GET a previously created system which has not yet been + ___ made current, but which will become the current system after the patches are made. RMRD:RAMROD*PF (1019/23) contains a description of the use of RAMROD. Enter enough comments so that other people can tell what you've been up to. You will have been prompted for comments if you created a new system, otherwise you may use the ANNOTATE command to add comments. + ________ 0 Add REP cards to the deck(s) using the PATCH command. + _____ 0 RENAME the new system with the correct version name and make it CURRENT. + _______ 1 18 - For example: 0 # $Run mts:ramrod # Execution begins Using file "MTS:ROD" Proceed. ~ list current UG117 created from UG057 23:06:01 08-11-77 08-11 23:00 REPLACED UMMPS TO FIX BUG IN GETSTK//SETSTK (MTA) ~ create newsys from ug117 ~ Enter comments : ? 08-24 21:05 Just an example (DLB) ? ~ Done. ~ patch taskstat ~ Address Esdid Text : ? 30 01 58F0 just an example patch (DLB) ? ~ Enter comments : ? 08-24 just an example patch ? ~ REP 000030 0158F0 example patch 21:15:25 08-24-77 W163 ~ OK ? ok ~ Done. ~ rename newsys ug247 ~ "NEWSYS" is a system. ~ ** RENAME system "NEWSYS" as "UG247" : ~ OK ? ok ~ Done. ~ current ~ There are 3 IPL files with prefix "*IPL. " ~ Loading system "UG247" ~ LOAD: Resident: 1000-27D80 UMLOAD Psect: 58000 Pageable: 6C000-ACD90 End: AFFFF Contents of IPL file "*IPL.2": UL177 ENTRY=26E08 PSECT=100008 VIRTUAL=58000...ACD90 WRITTEN BY ID MTA. AT 06:24:38 07-17-77 COM 07-14 20:00 CHANGED CONFIG.CARD TO GIVE MORE SPACE TO SEGMENT 0 FOR BIG MACHINES COM 07-14 21:59 REPLACE TASKSSTAT, MINOR CHANGES. COM 07-15 13:35 NEW TABLES TO ADD MORE JOB TABLES. COM 07-17 06:20 REPLACED PDP WITH WHAT I HOPE IS THE D4.0 VERSION. ~ ** Write system "UG247" to IPL file "*IPL.2": ~ OK ? ok ~ System "UG247" has been written to IPL file "*IPL.2" ~ IPL file stacked has been pushed. ~ System "UG247" is now the current system. ~ "UG247" : Released. ~ System "UG247" has been Frozen. ~ Done. ~ stop # Execution terminated - 1 19 - Remember to Produce an Update to the Source + ________ __ _______ __ ______ __ ___ ______ 0 It seems almost silly to mention this, but .... - Patching Decks Loaded by PISTLE + ________ _____ ______ __ ______ 0 Decks loaded into shared VM by PISTLE (the post-IPL system loader) can be patched in memory as described above. REP cards are added to the files from which PISTLE loads the object, generally using *OBJUTIL's PATCH command. It is a good ideato use PISTLE without specifying PAR=NOTEST to make sure the patched version will load. 0 PISTLE can also be used to load complete new versions of a deck into shared VM so long as all references to the module are made using a low core symbol table rather than external references that are already resolved, i.e., if the IPL option is not used to load it. PISTLE allows the automatic replacement of symbols in the low core symbol table LCSYMBOL; other low core symbol tables must be patched by hand. 0 The PISTLE writeup in UMPS:PISTLE*WP (component 559/14) describes how to use this facility. - 1 20 - PRINTED DOCUMENTATION IN THE DISTRIBUTION + _______ _____________ __ ___ ____________ - The following lists all of the paper-copy documentation included in D6.0. Of course, all of the documents listed below are available on the *FS tapes except for those marked with an asterisk (*), which indicates that only a paper copy was shipped (no machine readable copy is available). In addition, there are many more writeups on the *FS tapes for which paper copies have not been shipped. Using the MTS editor on the driver file to match for the letters "W" or "P" in column 45 will produce a complete list of all the machine readable documentation. 0 Printed copies of many items have been omitted from this distribution for existing installations when machine readable versions are available on the *FS tapes or when the material has not changed from that included in the previous distribution of MTS. If your installation needs a printed copy of any of the omitted items, send a request to: 0 Suzan Alexander The University of Michigan Computing Center 535 W. William Street Ann Arbor, MI 48103 USA - Printed copies of the following items are included with D6.0 for both new + ___ and existing installations. + ________ 0 461/27 Driver file listing (*DEDIT LIST command output) 461/30 Driver file index (6250 BPI ; a listing sorted by component names which serves as an index for 461/15. 461/33 General Notes, what you are reading now 461/34 Installation instructions for New Installations. 461/35 Installation instructions for Existing Installations. 711/1 List of current CCMemos. * 461/38 UM Machine Configuration Chart. * 711/15 Computing Center Newsletter (v15n7 through v3n9). * 711/16 Permission to reproduce Computing Center publications. 0 Printed copies of the following items are included with D6.0 for new + ___ installations only, but are available to existing installations upon request. 0 004/14 TABLES 370 writeup. 004/16 TABLES XA writeup. 387/44 HASP Operator's Guide. 387/47 HASP Notes. * 387/92 HASP Remote 360/20 Operator's Guide. * 387/93 HASP Remote 360/non-20 Operator's Guide. * 387/94 HASP Remote 1130/1800 Operator's Guide. * 387/95 HASP Remote System/3 Operator's Guide. * 387/96 HASP 2780 Remote Workstation Operator's Guide. * 461/39 TSS DASDI instructions. 468/15 Description of D6.0 System Object Deck. 1 21 - 592 MTS Operator's Manual. * 673/23 Documentation to supplement the machine readable documentation for the FLECS FORTRAN preprocessor. 711/2 List of Computing Center Publications and the publications themselves. * 711/17 MTS Reference Summary. 1021/13 Documentation for the IPLREADER and friends. 1019/23 Documentation for the RAMROD System Maintenance Utility. 0 The following items are not automatically included with D6.0 of MTS for either existing or new installations, but copies are available upon request. 0 * 583/06 Documentation for the KWIC (583) program. * 584/04 Documentation for the QUIC (584) program. * 646/02 Audio tapes of 33 system lectures given by the UM staff during 1973. 1 22 - COMPONENTS WHICH DEPEND ON THE SYSTEM CONFIGURATION + __________ _____ ______ __ ___ ______ _____________ 0 1. The TABLES assemblies (468/8-11) depend almost completely on the hardware configuration being used. It is described in separate write-ups (004/14 and /16). 0 2. There are two disk file backup processes available to save files on tape: the weekly FILE SAVE and the daily online FILE SAVE. There are command files associated with the weekly file save which will have to be changed at each installation so that they indicate correctly which disk volumes are to be saved. See the driver file comments for these components (067). 0 3. The distributed system pages to disk through the Disk Manager. If it is desired to add 2305 or 4305 paging devices, then INIT:INITCMD (097/5) should be changed to run INIT:FMT2305 (97/36) to initialize 2305s (or 4305s). 0 4. The PDP (044) assumes by default that paging to disk is done through the Disk Manager. If you intend to use dedicated disks as paging disks, the PDP must be reassembled. If you intend to use more than four 3805 devices or if you intend to use 2305s, you must also reassemble the PDP. The PDP will automatically grab any 3805 that is online and use it when it is started so if it is not to be used, OFFLINE it before the PDP is started (before giving the reason for reloading). The PDP can be reassembled to automatically use any 3330 disks that are labeled with the prefix "PAG" (e.g., PAG001) and that are labeled as PAGING packs. The PDP has also been assembled to assume two 2305s but they will not work properly since the number of slots per device is set to 8. Sites using 2305s will need to reassemble the PDP with NOSLOTS set to 3 (the only number of slots for which the 2305s will work properly). For this reason, all 2305s should be offline before the PDP is started. Note: The PDP has an assembly parameter which determines whether 2301s or 2305s are to be used; the distributed version assumes 2305s. It can be reassembled for 2301s. The PDP can also be reassembled with the 3805 support removed, making it a bit smaller. 0 5. MOUNT (101) includes support for mounting paper tape readers and punches, audio response units, floppy disks, intertask pipes, HIM devices, and connections on the Merit Computer Network in addition to magnetic tapes. Assembly parameters allow support for these other (non mag tape) devices to be deleted. Support for the Adage Graphics terminal may be included, but UM doesn't have one so this code has never been fully tested. 0 6. In MTSBATCH (957) the subroutine NEXTJOB will do a binary read from a 2540 or 2501 when it is looking for the next job in a batch stream. Since a 2540 without binary feature ("card image" feature) will accept the command and treat it as an EBCDIC read, NEXTJOB will never find a job. This affects only non-HASP batch (rarely, if ever, used). 0 7. HASP (387) contains several assembly parameters that depend on the machine configuration. A separate description of these, which wasn't changed for D6.0 and which is somewhat out of date, is 1 23 - included in component 387/47. Both HASP and the HASPLING (388) have assembly parameters related to RJE support. The HASP master source and distributed object contains no RJE support. 0 8. TAPERTN (135) - the magnetic tape routines - has several assembly parameters (see comments in the source). In addition, the local system name used in the data set labels generated by MTS is obtained from the CIINAME field in the CNFGINFO table described above. 0 9. The 2741 Device Support Routine (038) has a built-in table of the device names of hardwired 2703/1270 lines. All other lines are assumed to be dial-up. This table should be updated and *2741RTN (038/3) reassembled as appropriate. 0 10. The file COPY:SECTIONS*SAL (4215/3) has global set symbols for various hardware and software features. In most cases, this file is copied by system components which are dependent on these features. 0 11. The 3270 DSR (629) has several global set symbols that may be used to tailor the DSR for use at a given installation. 0 12. The GRAB3270 table (629/17) has entries for a fixed number of displays. It will work for fewer, but must be reassembled if more displays are allowed to GRAB and FLIP. 1 24 - LISTINGS IN THE DISTRIBUTION + ________ __ ___ ____________ - Listings have been included on the *FS tapes for the following components of the system. - Comp._Name 5.1_Comp. 5.1_Tape, 6.0_Comp. 6.0_Tape, + _____ ____ ___ _____ ___ _____ ___ _____ ___ _____ number file_# number file_# + ______ ____ _ ______ ____ _ 0 MTS 0042/4 5.1T1 #22 0042/6 6.0T1 #88 UMMPS MP 0045/4 5.1T1 #30 0045/21 6.0T6 #968 UMMPS 370 0045/4 5.1T1 #30 0045/22 6.0T6 #969 UMMPS 4K 0045/4 5.1T1 #30 0045/23 6.0T6 #970 UMMPS 64 0045/4 5.1T1 #30 0045/24 6.0T6 #971 CONFIG 370 0046/4 5.1T1 #38 0046/5 6.0T1 #117 CONFIG XA 0046/4 5.1T1 #38 0046/6 6.0T1 #118 GUINFO 0198/4 5.1T1 #208 0198/7 6.0T1 #744 LLXU 0354/4 5.1T1 #265 0354/4 6.0T1 #1114 PLIMIT 0464/4 5.1T1 #324 0464/4 6.0T1 #1307 CMDSTAT 0531/4 5.1T1 #550 0919/4 6.0T4 #1426 RSF 0578/4 5.1T1 #636 0578/4 6.0T2 #639 FSUB 0635/4 5.1T1 #759 0635/4 6.0T2 #930 CMDS 0636/3 5.1T1 #762 0636/4 6.0T2 #934 DSRS 0637/4 5.1T1 #765 0637/4 6.0T2 #938 USUB 0638/4 5.1T1 #768 0638/4 6.0T2 #942 DSRI 0639/4 5.1T1 #771 0639/4 6.0T2 #946 TBLS 0829/4 5.1T2 #694 0829/4 6.0T3 #1368 PROFORT 0847/2 5.1T2 #882 0847/2 6.0T4 #208 GATE 4000/4 5.1T3 #317 4000/4 6.0T6 #851 - 1 25 - PEOPLE LIST FOR THE UNIVERSITY OF MICHIGAN COMPUTING CENTER + ______ ____ ___ ___ __________ __ ________ _________ ______ - The following is a list of UM Computing Center people whose names appear in the "person" field of the driver file listing. All correspondence should be addressed to: 0 The University of Michigan Computing Center 535 W. William Sreet Ann Arbor, MI 48103 USA 0 ALEXANDER Alexander, Suzan AUPPERLE Aupperle, Kathy BOLLETTINO Bollettino, Laura (MERIT) BOSLEY Bosley, Kevin BURLING Burling, Steven R. B MOORE Moore, Brian CASHMAN Cashman, Brian CONTO, Conto, Richard (MERIT) C MOORE Moore, Chris DONNELLY Donnelly, Stephen M. DWB Boettner, Donald W. D BODWIN Bodwin, Diane L. EMERY Emery, Allan R. ENGLE Engle, Charles F. FLANIGAN Flanigan, Larry K. FLOWER Flower, David S. FRONCZAK Fronczak, Edward J. GLUSKI Gluski, Kari GOLD Gold, Steve GOODRICH Goodrich, Andy HARDING Harding, Leonard J. HYDE Hyde, Dan J BODWIN Bodwin, James M. KNOPPER Knopper, Mark (MERIT) LANG (Language Group - See SWARTZ) LEVER Lever, Chuck LIFT Lift, Gail H. MANUAL (see SALISBURY) MARTZ Martz, Paul MTA Alexander, Michael T. MTS (see BURLING, J BODWIN, BOSLEY, MTA) PIRKOLA Pirkola, Gary C. PLUMMER Plummer, Chris RAMANUJAN Ramanujan, Chitraleka RIOLO Riolo, Rick ROTHWELL Rothwell, Steven SALISBURY Salisbury, Richard A. SCHNEIDER Schneider, Eric (MERIT) SELL Sell, Jon SNYDER Snyder, Dave SUN Sun, Dave SWARTZ Swartz, Fred G. TAYLOR Taylor, Eric 1 26 - TIFFANY Tiffany, L. Bernard TOPOL Topol, Susan UNSP (see SELL) VALERIO Valerio, Thomas WHIPPLE Whipple, David WOLFSON Wolfson, Genie R. YOUNG Young, Howard B. - 0 Correspondence related to the administration of the UM Computing Center should be sent to the director: 0 Dr. Carolyn Autrey-Hunley, Director The University of Michigan Computing Center 535 W. William Street Ann Arbor, MI 48103 USA 0 Telephone (313) 936-2773 1 27 - DISTRIBUTION 6.0 INITIAL MAILING LIST + ____________ _ _ _______ _______ ____ 0 The following is a list of persons to whom the initial shipments of MTS Distribution 6.0 have been sent. - RIO LCC - CNPQ 6250 BPI Attn: Jayme S. P. Goldstein R. Lauro Muller, 455 22290 - Botafoga - Rio de Janeiro R.J. - BRAZIL 0 RPI Office of Computer Services 6250 BPI ATTN: Garance Drosehn Rensselaer Polytechnic Institute Troy, NY 12181 0 SFU Computing Centre 6250 BPI ATTN: Peter Howard Simon Fraser University Burnaby, B. C. V5A 1S6 CANADA 0 UBC Computing Centre 6250 BPI ATTN: Ron Hall 6356 Agricultural Road University of British Columbia Vancouver, B. C. V6T 1W5 CANADA 0 UD Computer Unit 6250 BPI Science Laboratories ATTN: Mike Ellison South Road University of Durham Durham DH1 3LE ENGLAND 0 UNE Computing Laboratory 6250 BPI ATTN: John Law The University Newcastle upon Tyne NE1 7RU ENGLAND 0 UQV Computing Services 6250 BPI ATTN: Garry Jackson The University of Alberta Edmonton, Alberta T6G 2H1 CANADA 0 WSU Computing Services Center 6250 BPI ATTN: Tom Stevenson Wayne State University 5925 Woodward Ave., Room 284 Detroit, MI 48202 1 28 - Goddard Space Flight Center 6250 BPI ATTN: Jordan Alpert Code 616 Greenbelt, MD 20771 0 Hewlett-Packard CCC ATTN: Randy Rumbaugh 3000 Hanover Street 20CH Palo Alto, CA 94304 0 McGill University Hospitals 6250 BPI ATTN: Clifford Kuhl C/O ST Systems Southfield, MI 0 MM Computer Laboratory 6250 BPI ATTN: Rich Wiggins Michigan State University East Lansing, MI 48824 1 29 - APPENDIX A + ________ _ 0 Bug Fix for *SIGSETUP + ___ ___ ___ _________ 0 . . New (D6.0) base for SIGSETUP*SQ created on Wed Apr 1388. egin sensedatatype. . Inst.: UM. By : Steve Burling. Date : Mon Apr 2588. . + _ _ sensedatatype:. Getting SenseDataType out of MTS*SQL now, and + _ _ _ _ SnsForTerminal. is bigger than 255 bytes. The result of this is that + _ _ sigsetup. was providing a 255 byte buffer, but claiming the buffer was. longer, and this screwed up MTS, since it would clobber the. following storage, and if $LOGging was in effect you'd get a. PGNT in LOG. Provide a suitably sized buffer. . 1 30 - y '%Include(ReturnControlBlockType);' + _ _ _ 1 31 - y ' ' %Include(Fill); 1 32 - y 'definition Primary;' .................elete ' variable SenseInfo + _ is FixedString,' variable SenseInfo is character(ByteSize(SenseDataType, + _ _ _ _ _ SnsForTerminal)), ............................elete ' SenseInfo := + _ _ _ Substring(B255, 0, ByteSize(SenseInfo));' Fill(SenseInfo, + _ _ _ ByteSize(SenseInfo), " "); end sensedatatype. + _ _ _ _ =================================================================. . ==== Rolled to here at UM on Mon Apr 2588 by Steve Burling ====. ) 1 33 - Bug Fix for TRAK + ___ ___ ___ ____ 0 . . New (D6.0) base for TRAK*SA created on Thu Apr 1488. 1 34 - sourcemargin=1-72egin CLEARFLG. . Inst.: UM. By : James M. Bodwin (for + _ MTA). Date : Wed Apr 2788. . CLEARFLG: Clear the type field before ORing the new one in. 1 35 - y 'RTHREE USING BCB,R3' NI BCBFLAG,X'FF'-BCBTYPEMASK Clear the old type end CLEARFLG. =================================================================. . ==== Rolled to here at UM on Wed Apr 2788 by James M. Bodwin ====. ) 1 36 - Bug Fix for ETC.:CNVTEREP + ___ ___ ___ _____________ 0 . . New (D6.0) base for CNVTEREP*SA created on Fri Apr 2288. 1 37 - sourcemargin=1-72egin MDRType. . Inst.: UM. By : Mike Alexander. Date + _ _ : Tue Apr 2688. . MDRType: Get the MDR record type code from the device + _ characteristics correc. 1 38 - y ' IF ATYPE,EQ,25 Then look for device char.' 1 39 - y ' IF R2,LT,R0' 1 40 - ' MVC LRBODEVT+3(1),2+41(R2) OBR RECORD IDENT' MVC LRBHSW2(1),2+40(R2) MBR RECORD IDENT end MDRType. + _ =================================================================. egin CHPIDV. . Inst.: UM. By : Mike Alexander. Date : Tue Apr + _ 2688. . CHPIDV: The IBM manual had the sense of the "CHPID Valid" + _ bit backwards, app. 1 41 - y 'OBRREC MVI HDRTYP,HDRUC0 OBR RECORD' .elete ' OI LRBHSW2,LRBOCPV CHPID valid' 1 42 - y ' STC R1,LRBOSCUA' ELSE , OI LRBHSW2,LRBOCPV CHPID not valid 1 43 - y 'GENERICOBR MVI HDRTYP,HDRUC0 OBR RECORD' elete ' OI LRBHSW2,LRBOCPV CHPID valid' 1 44 - y ' STC R1,LRBOSCUA' ELSE , OI LRBHSW2,LRBOCPV CHPID not valid 1 45 - y 'OBRTYPE EQU TAPEOBRSAVE+4*(R0-R14+16)+3 TYPE CODE IN R0' elete ' OI LRBHSW2,LRBOCPV CHPID valid' 1 46 - y ' STC R1,LRBOSCUA' ELSE , OI LRBHSW2,LRBOCPV CHPID not valid elete ' OI LRBHSW2,LRBOCPV CHPID valid' 1 47 - y ' STC R1,LRBOSCUA' ELSE , OI LRBHSW2,LRBOCPV CHPID not valid end CHPIDV. + _ =================================================================. . ==== Rolled to here at UM on Tue Apr 2688 by Mike Alexander ====. egin Addr. . Inst.: UM. By : Mike Alexander. Date : Thu Apr 2888. . Addr: Get some addressibility without using register 13 as a base, since that. doesn't work. . 1 48 - y 'CNVTEREP CSECT' ......................elete ' USING SA,R13' 1 49 - y "RDSTTIME SERCOM ' Enter starting time (e.g. 8:20 Jan 13)'" elete " PMSG ' The part following ',(IN,FLEN=TDLEN),' was ignored'" L R2,=A(IN) PMSG ' The part following ',(0(R2),FLEN=TDLEN), @ ' was ignored' 1 50 - y "RDEND SERCOM ' Enter ending time'" ...elete " PMSG ' The part following ',(IN,FLEN=TDLEN),' was ignored'" L R2,=A(IN) PMSG ' The part following ',(0(R2),FLEN=TDLEN), @ ' was ignored' elete " MVI IN,C' '" L R2,=A(IN) MVI 0(R2),C' ' 1 51 - y 'YORN GUSER IN,LEN,EXIT=END' ..........elete ' TR IN(5),0(R1)' 1 52 - " CLC =C'OK',IN" TR 0(5,R2),0(R1) CLC =C'OK',0(R2) elete " CLI IN,C'Y'" CLI 0(R2),C'Y' .................elete " CLI IN,C'N'" CLI 0(R2),C'N' ..............................elete ' USING SA2,R13' . elete ' USING SA2,R13' 1 53 - y 'FNDBASE2 LH R0,BASEPATH GET BASE ADDRESS' elete ' TRT ASENSE+4(1),ONEBIT IS THERE A GOOD ID?' L R2,=A(ONEBIT) TRT ASENSE+4(1),0(R2) IS THERE A GOOD ID? 1 54 - y 'BASEOFLO DS X =1 IF TABLE HAS OVERFLOWED' elete "ONEBIT TRTAB (X'80',X'40',X'20',X'10',X'08',X'04',X'02',X'01',1)" 1 55 - '*' 1 56 - y 'TAB3420 EQU *' .......................elete ' SPACE 5' 1 57 - 'IN DS XL256 INPUT AREA' 1 58 - y 'FMTVSTUFF DS 4H' 1 59 - y ' SPACE 5' IN DS XL256 INPUT AREA SPACE 5 1 60 - y 'BASETBL DS (BASECNT)XL(BASELEN) TABLE FOR BASE ADDRESSES' 1 61 - y " DC X'FE'" * ONEBIT TRTAB (X'80',X'40',X'20',X'10',X'08',X'04',X'02',X'01',1) end Addr. =================================================================. . ==== Rolled to here at UM on Thu Apr 2888 by Mike Alexander ====.