vm_cms_survival_guide []

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== VM/CMS Survival Guide ======

===== Introduction =====

This is a brief introduction to basic concepts and commands for using the [[http://www.livingcomputers.org|LCM+L]]'s [[IBM 4361]] midrange computer system. 

The 4361 runs the [[VM/SP]] virtual machine operating system. 

VM is basically two components:

  * The Control Program (CP) which controls the real hardware and provides a virtual machine (VM) for each user, and 
  * The single user [[wp>Conversational_Monitor_System|Conversational Monitor System]] (CMS) which runs in a VM to provide the user environment (shell to you UNIX/Linux types).

===== And Now, a Word From the Vendor =====

IBM has published an introductory document, [[http://www.vm.ibm.com/devpages/HUGENBRU/BASICS.PDF|The Basics of Using z/VM]].(([[wp>Z/VM|z/VM]] is a later edition of the VM family, updated for a 64-Bit [[wp>POSIX]] world.)) This gives a short overview of VM in general.

The VM user environment has not changed extensively between VM/SP 5 and z/VM, but there are few differences to point out between the 4361 and the environment described in the document:

  * The 4361 is a 32-bit machine with a 24-bit (16 megabyte) address space.
    * MVS/XA, MVS/ESA, and z/OS guests (all descendants of [[wp>MVS]]) cannot run under VM/SP.
    * No supported version of [[wp>Linux]] or [[wp>Unix]] guests can run under VM/SP.
    * VM/SP does not have a POSIX shell or related utilities
  * You cannot switch between sessions at the ''LOGON'' screen.
  * VM/SP 5 only supports minidisks for storage; it does not support:
    * SFS (Shared File System)
    * BFS (Byte File System)
    * NFS (Network File System)
  * VM/SP supports the ''CP TRACE'' command, but not as documented in the presentation. (Enter ''HELP CP TRACE''.)
  * VM/SP does not support the ''CP TERM MORE'' command.

Now go read the IBM introduction. We'll wait.

===== Connecting to the 4361 =====

==== Secure Shell (ssh) ====

You can connect to LCM+L's 4361 with Secure Shell (ssh). 

''ssh ibm4361@tty.livingcomputers.org''

Once you have connected to the 4361, you can follow the instructions on this page starting with the section "Log-on Procedure".

The PA2 3270 terminal key (for clearing the screen) is mapped to **Ctrl-A 2** (Control-A followed the number 2) when connecting with ssh.

(ssh is available as part of the OpenSSH package for MacOS, *BSD and Linux operating systems, or PuTTY for Microsoft Windows.)

==== 3270 Terminal Emulator ====

The VM/CMS system was originally designed to be accessed from a [[wp>3270|3270]]-compatible terminal. Today, since 3270 hardware is rare, you will probably use 3270 emulator software.

[[http://x3270.bgp.nu|x3270]] is a free open source software suite of 3270 terminal emulator tools by Paul Mattes and others. It includes clients for X11 (x3270; for Unix, Linux, *BSD, etc.), MS Windows console  (wc3270), and others.

[[http://x3270.bgp.nu/download.html|Download]] an appropriate package and follow the instructions to install it on your system.

=== Session set-up ===

== Where to connect == 
^ Host Name | tty.livingcomputers.org |
^ TCP Port | 24 |

== Terminal Sizes ==
On most platforms you can specific the model of terminal emulator if you start the program from the command line.  The model is composed of two parts:

  - The model number:
    - ''3278'' are monochrome terminals. These were the most common type when real 3270 terminals roamed the land.
    - ''3279'' are color terminals.  VM/SP has good support for them, and are generally preferred when using modern terminal emulators.
  - The model suffix, which specifies the screen size:
    - ''2'' is the classic 80 columns by 24 lines. 
    - ''3'' is 80 columns by 32 lines. 
    - ''4'' is 80 columns by 43 lines. This is useful for editing. 
    - ''5'' is 132 columns by 27 lines. This is useful for reviewing listings.

Thus for a color terminal sized 80x43, the full model is specified as ''3279-4''.

== Unix (Linux, *BSD, Mac, ...) ==

You can login via ''x3270'' from via a terminal window the X-Windows menus:

  - Using a ''xterm'' or other terminal window:
    - run ''x3270 --model 3279-4 tty.livingcomputers.org 24''
  - Using X Windows menus: 
    - In your X session, run ''x3270''. 
    - From the **Connect** menu click **Other...**.
    - In the "x3270 Connect" window, enter the following Hostname: ''tty.livingcomputers.org:24'' 
    - Click **Connect**. (The host will automatically be added to the **Connect** menu for future sessions.)

You can also install and use the more limited text window version, ''c3270''; this will be limited by the size of the window it runs in:

  - ''c3270 --model 3279-4  tty.livingcomputers.org 24''

== MS Windows ==

  - Run the wc3270 Session Wizard.
  - On the Overview menu, select "1. Create new session (new)".
  - Enter the configuration parameters from the table below.
  - Answer "y" to "Create session file '...'?". 
  - Optionally, answer "y" to "Create desktop shortcut?".
  - Return to the Overview menu and select "8. Quit (quit)".

===== Log-on Procedure =====
==== If We Tell You Nothing Else ... ====

First things first: 

  * Figure how your terminal emulator sends ''PA2'' to the host.  For example, the default x3270 mapping is ''Alt-2''.  This is because ...
  * ... Once connectted to VM, to clear the screen, use host key ''PA2''. This clears all but the input area at the bottom of the screen.

You'll also need to know how your emulator sends:

  * ''ENTER'' (usually your ''ENTER'' or ''RETURN'' key)
  * ''PA2''
  * ''PF1'' through ''PF12''
  * ''RESET'' (often Alt-R)
  * ''^'' (Insert Mode) (by default, 3270 terminals overwrite)
==== Connect and Log-on ====

Start your 3270 terminal emulator and connect to the LCM+L's 4361.

You'll be rewarded with a screen like the one below, which is the front end [[wp>IBM_3270#Controllers|terminal controller]] emulator for the 4361.


{{ ::4361-flex-menu.jpeg?800 |}}

Put an ''X'' on any device, and press ''ENTER''. You'll be rewarded with the VM Login screen:

**Note**: If this icon, {{:vm-cursor-err.png?nolink&70|}}, on the bottom line of your terminal, it means you tried to input data when the cursor was not located in an input field on the terminal screen. Press ''TAB'' to move the cursor to the next input field.

{{ ::4361-lcm_l-logo.jpeg?800 |}}

Enter your Userid & Password (use ''TAB'' to move the cursor to the next input field), press ''ENTER'' and you're off to the races.

===== Your CMS Session =====

After you log-in, your terminal will look something like this:

{{ ::cms-ready-scr-sect.png?800 |}}

The terminal screen is divided into four areas:

**A**: System output. Commands you input to CMS are echoed here, and all system output is printed.

**B**: User input. This is the only input area on the default CMS screen.

**C**: System status

**D**: Terminal status

When you see the ready prompt (''Ready; T=0.21/0.38 02:40:57'' in the screen shot above, but yours can be customized), type commands into the user input area followed by ''ENTER'', and CMS will try to fulfill your every desire.

==== System status ====

The system status area indicates the state of your CMS session and what kind of input the system is expecting from you. The following messages may be displayed:

| ''RUNNING'' | CMS is waiting for you to type a command. This is the most common message. |
| ''MORE...'' | The system is pausing in the middle of multi-screen output to give you a chance to read. After one minute the next screenful of output will be displayed. If you are ready for the next screen of output before then, press ''PA2'' If you need more than one minute to read the current screen, press ''ENTER'' to go to HOLDING state. To discard the rest of the output, enter the command ''HT'' (for Halt Type). |
| ''HOLDING'' | The system is waiting for you to read the current screen of output. Press PA2 to continue. |
| ''VM READ'' | CMS or another VM program has requested input from you and is waiting for your answer. |
| ''CP READ'' | CP (the virtual machine hypervisor running underneath CMS) is waiting for a command. If you were previously working in CMS or a program you ran from CMS and got interrupted accidentally, try entering the command ''BEGIN'' and you may be able to restore your session. If that doesn't work, ''#CP IPL CMS'' will restart CMS, but you may lose the work you were doing before the interruption. |
| ''NOT ACCEPTED'' | You entered a command when the system wasn't ready. Press ''Reset'' |

===== File System =====
Resources, including disk, are allocated by CP among users as disks and links defined by the user directory, a file maintained by the system administrator. Disks can be dedicated in their entirety to a single user((A disk or other device might be dedicated for a complex multiple users guest system like [[wp>MVS]], [[wp>MUSIC/SP]] [[wp>Michigan_Terminal_System|MTS]], or a VM running under VM.)), or divided into disks for smaller users. Such smaller disks are called minidisks.  Common minidisks are listed below.

^  Common Name  ^  Device Address  ^  Detailed Description  ^
^ System Disk \\ (S-Disk) |  190  |The [[wp>Conversational_Monitor_System|CMS]] operating system and basic system programs are located on this disk. |
^ User A-disk |  191  | The personal writable disk of the user.                  |
^ D-Disk      |  192  | A work disk which is automatically formatted if it is writable and unformatted.  |
^ G-Disk      |  19C  | On the LCM+L 4361, it is read only and contains games. |
^ Y-Disk      |  19E  | An extension of the S-Disk, this contains utilities which are not part of the base system.  For example, on the 4361 it contains compilers, ''IND$FILE''((''IND$FILE'' performs transfers via a 3270 terminal emulator)), the client interface  for the real-time monitor ''SMART''((''SMART'' shows system activity, similar to ''top'' on UNIX or ''Task Manager'' on Windows. It is invoked by the user command ''VMC'', or more easily via the ''VMCSMART EXEC''.)), useful editor macros, and other utilities. |
^ Help Disk   |  19D  | The location for system help files. This is automatically accessed, usually at file mode Z, when needed by the Help system. |

As noted above, access to others' disks are done by link definitions in the system directory. Each disk in the directory may have one or more link passwords.  If a disk is that is not defined as attached to your VM has a password for a mode, you may link it via a user command.  

^ Mode((If the second letter is omitted, and the primary link mode is rejected because others linked to the disk, the link will fail.)) ^ Abbreviation ^  Detailed Description  ^
^  RR  |  Read/Read  | Attach to the disk read/only (R/O) if no one is linked to it, else attach to the disk R/O. |
^  WR  |  Write/Read  | Attach to the disk writable if no one is linked to it, else attach to the disk R/O. Generally, not used in favor of ''MR''.  | 
^  MR  |  Multi-write/Read  | Attach to the disk writable if no one is writing to it, else attach to the disk R/O. |
^  MW  |  Multi-write/Write  | Attach to the disk writable if no one is writing to it, else attach to the disk writable anyway.  Using this mode will __**destroy**__ a CMS-formatted disk.  So forget you were told this option exists.|

===== Files =====

==== File Names ====

=== Overview ===

A file on a CMS file system is described in three parts, separated by spaces. All three parts are required.

^ Component ^ Abbreviation ^ Description ^
^ file name  |  fn  | The one to eight character name of the file.((Files with a single unique instance for each user on their A-Disk often use the user id as the name, such as ''SNOWHITE NAMES A1'' and ''SNOWHITE NETLOG A1''.)) |
^ file type  |  ft  | The one to eight character type of the file. See below for a list of important types. |
^ file mode  |  fm  | The two-character mode of the file. The first character is the alphabetic letter of the disk, the second character a number between 0 and 6, described below. |

=== Type ==
Like Windows, the function of a file on CMS is defined by its type. Common types are listed below.

^  File Type \\ (Executable files \\ are in //italics//) ^ Description ^
^  ASSEMBLE \\ BASIC \\ C \\ COBOL \\ FORTRAN \\ PLI | Source files for programs |
^  //EXEC// | An executable (human readable) script. The language may be [[wp>CMS_EXEC|EXEC]], [[wp>EXEC_2|EXEC 2]], or [[wp>REXX]] |
^  LISTING | The printable output from a compiler or other program. |
^  MACLIB | Multiple source files organized into a single file, used as source includes for source programs. |
^  //MODULE// | An executable binary program. |
^  SYNONYM | A list of user command synonyms and acceptable abbrevations. |
^  SCRIPT | A source file for the [[wp>SCRIPT_(markup)|SCRIPT Markup language]] used for formatting text. |
^  TEXT | Object code. They are linked into runnable MODULES.((Files of type TEXT are not human readable text and not directly executable -- if not compiling programs, pretend you didn't see them.)) |
^  TXTLIB | Multiple text (object) files organized into a single file, used as object code includes for compiled programs.|
^  VMARC | Like a ZIP or TAR files on other platforms, this is file an archive for files on VM.  It is specifically formatted to a standard format of 80 byte records to allow binary transfer via foreign systems, VM readers, RSCS, and IND$FILE without corrupting the data. |
^  //XEDIT// | An executable (human readable) script executed by the [[wp>XEDIT]] editor. Supports the same languages as EXEC. |
=== Mode Number ==

As noted above, file modes consist of the letter of the disk the file resides on, and number further defining a file.

^ Number ^ Definition ^ Description
^  0  |  Private  | The file is only visible to the current user with write access. |
^  1  |  Normal  | The file is visible to all users. This is the default mode for most files created. |
^  2  |  Public  | The file is visible when accessed with a filter, such as ''ACCESS 19E Y/S * * Y2''. System disks are generally automatically accessed this way. |
^  3  |  Temporary  | The file is deleted after open for reading. Useful for things like intermediate steps in compile procedures. |
^  4  |  OS specific  | The file is written according to special rules for OS emulation. |
^  5  |  Normal (alternative)  | The file is the same as file mode 1, but visually set apart by their number. Often used for generated LISTING files. |
^  6  |  Update \\ in-place  | Normally, an update to a file occurs by allocating a new block on the disk and writing it. With mode 6, the original block is rewritten.((Use with care. This mode can corrupt the file or the entire disk if CMS crashes before the file is closed.))|
===== Useful Commands =====

Enter ''HELP //command//'' at the command prompt on most of the commands below.  Most commands can be abbreviated, and ''CP'' can usually be omitted.

^ Name ^ Description ^
^ DIRMAINT | Change your password and set other account parameters. Use ''DIRM ?'' for the complete list of ''DIRMAINT'' subcommands.|
^ COPYFILE | Copy files |
^ ERASE | Delete files |
^ FILELIST((''FILELIST'' uses XEDIT, which makes it slower than ''FLIST''.  However, XEDIT never gets confused by terminal sizes which don't match what the system was originally configured for.)) | Display files in a scrollable display |
^ FLIST((''FLIST'' is a compiled program, which makes it faster ''FILELIST''.  However, ''FLIST'' can be confused by non-standard terminal sizes.))    | Display files in a scrollable display |
^ GAME | Display games menu. This command has no help topic. |
^ HELP  | With no operands, lists a a top-level menu of topic areas. |
^ LISTFILE | List files at the terminal |
^ CP LOGOFF | Terminate your session |
^ NAMES    | Edit your address book, which is used by ''TELL'', ''NOTE'' and ''SENDFILE'' |
^ NOTE     | Send an email to another user on the local machine. |
^ CP QUERY NAMES((For help on this, enter ''HELP CPQUERY NAMES''.)) | Display list of currently connected users. | 
^ CP QUERY VIRTUAL((For help on this, enter ''HELP CPQUERY VIRTUAL''))  | Display configuration of your virtual machine |
^ RDRLIST  | Display the contents of your virtual reader |
^ RENAME   | Rename files on a disk (will not move between disks |
^ SENDFILE | Send a file to another user |
^ TELL     | Send a message to another user |
^ XEDIT    | Edit a file |

In addition, compilers for the following languages are available: Assembler (''ASSEMBLE''), BASIC, C, COBOL, FORTRAN, PL/I (''PLI''). (Where not otherwise noted, the compilers are invoked by their language name.)  Not all of those have HELP files.
===== XEDIT Text Editor =====

For its environment, XEDIT is both an easy to use and powerful editor.  It's primary lack is no cut-and-paste, but modern terminal emulators can do client-side pasting which is not visible to the mainframe.

However, this power does require a good explanation, so this humble author defers to IBM on the topic; see [[http://www.jmit.com/vm/docs/hcsd9b10-XEDIT-Users-Guide.pdf|XEDIT Users Guide for z/VM]] for a proper overview of XEDIT.

**Note:** Most XEDIT examples show a prefix area with equal signs to the left of the screen, a scale across the middle of the screen, 
and the current line in the middle of the screen as well.  
The LCML4361 profile, which resides on the Y-Disk, changes this appearance to reduce the fixed "chrome"; it also 
moves the current line up, and provides line numbers in a //right// hand prefix area out of the way. 

You can move current line back to the middle and turn on the left prefix area and scale by entering the following commands in XEDIT:

  SET CURLINE ON M
  SET PREFIX ON
  SET SCALE ON 

You can permanently customize the appearance by creating your own ''PROFILE XEDIT A'', or simply editing the file on the Y-DISK and changing the file mode to A (''SET FMODE A'') before you save it. 
===== EXEC Scripts =====

==== Types of Scripts ====

File of type ''EXEC'' or ''XEDIT'' can be one of three languages:

  * [[wp>REXX|Rexx]] (Restructured Extended Executor), released with VM/SP 3 in 1982, is a block structured, high-level programming language. The first line of a Rexx program on CMS must begin with a C-style comment (''/* */'').
  * [[wp>EXEC_2|EXEC 2]], released with VM/SP 1981, is an enhanced version of EXEC, with longer tokens, ability to communicate with commands such as GLOBALV and EXECIO, and other enhancements.  The first line of an EXEC2 program must start with ''&TRACE''.
  * [[wp>CMS_EXEC|EXEC]] dates back to 1966 and the original [[wp>CP-67]] System, and based on even older facility for [[wp>CTSS]] .  It's famous for truncating tokens in strings to eight characters, which is rather annoying if your last name is "Cowlishaw".  All EXEC and XEDIT files which are not flagged by their first line as Rexx or EXEC2 programs are processed as ''EXEC'' programs.

==== Rexx Help ====

See [[#for_further_reading|For Further Reading]] below for the primary IBM references and other resources on Rexx.  
The addition information on Rexx on the 4361 itself:

  * Enter ''HELP REXX'' to get a basic feel of the language
  * Browse the ''KENDRA XEDIT Y'' to see a sample of the code.
==== EXEC and EXEC2 help ====

For help on the earlier scripting languages, enter:

  * ''HELP EXEC MENU''
  * ''HELP EXEC2''

The ''MENU'' is needed for EXEC but not the other languages because there is an ''EXEC'' command which, not surprisingly, runs ''EXEC'' files.
===== Compilers & Interpreters =====

=== Modern Compilers ===

As of this writing, two modern (to the 1980's) compilers are installed on the 4361:

  * C (''GCC'') NOTE, be sure to ''HELP GCC'' for details on increasing VM STORAGE
  * VS FORTRAN Version 2 (''FORTVS2'')
  * PL/I Optimizing Compiler (''PLIOPT'')

===  Not-so Modern Compilers ===

Older compilers, most dating to the original OS/360 era, are also installed:

  * COBOL
  * FORTRAN G (''FORTRANG'')
  * FORTRAN H (''FORTRANH'') 
  * PL/F (''PLIF'')

=== Linkers ===

All the compilers run ''TEXT'' (object) files, which need to be combined with run-time libraries and saved as executable ''MODULE'' files.  Various sample scripts will do this for simple programs:

  * ''GENCOBOL''
  * ''GENFORTG''
  * ''GENFORTH''
  * ''GENFORTV''
  * ''GENGCC''  
  * ''GENPLIF'' 
  * ''GENPLIOP''

For a more detailed example of linking a program and running it, see [[vm_cms_fortran]]
==== Interpreters ====

Rounding out the language processors are interpreters, which were primarily oriented towards educational environments:

  * ''BASIC''
  * ''FORTH''
  * PL/C for CMS (''PLCT'')
  * ''SNOBOL4'' 
  * WATFIV FORTRAN (''WATFIV'')

These do not generate ''TEXT'' files with object code, but instead run the translated programs immediately. 


===== For Further Reading =====

==== Introduction ====
Most the links in section are PDF files, many cases scanned copies of the original IBM manuals loaded to the site [[http://bitsavers.org/]].

==== Core VM/SP Specific Manuals ====

**Note:** Where VM/SP Release 5 manuals are not available, other releases are used as listed.  For release 6, most differences are minor and/or obvious, for example the new for release 6 Shared File System was supported. Usually, an appendix in each newer manual lists the differences from release 5.

^  Title  ^  <html>&nbsp;&nbsp;Retrieved&nbsp;&nbsp;</html>  ^  Description / Comments  ^
^ [[http://bitsavers.org/pdf/ibm/370/VM_SP/Release_3.0_Jul83/SC19-6210-2_CMS_Users_Guide_Release_3_Sep83.pdf|VM/SP CMS User's Guide Release 3]]|18-07-2018|CMS User Guide, **release 3**.  \\ \\ **Note:** This describes how to use ''CMSBATCH'', which is _not_ covered in the Command Reference.|
^ [[http://bitsavers.org/pdf/ibm/370/VM_SP/Release_5_Dec86/SC19-6209-4_VM_SP_CMS_Command_Reference_Release_5_Dec86.pdf|VM/SP CMS Command Reference Release 5]]|18-07-2018|The command reference for CMS commands.  \\ \\ **Note:** Does not include ''CP'' commands; for that, see below.|
^ [[http://bitsavers.org/pdf/ibm/370/VM_SP/Release_6_Jul88/SC19-6211-05_VM_SP_CP_General_User_Command_Reference_Release_6_Jul88.pdf|VM/SP CP General User Command Reference
Release 6]]|18-07-2018|The command reference for CP commands, **release 6.** |
^ [[http://bitsavers.org/pdf/ibm/370/VM_SP/Release_6_Jul88/SC24-5220-04_VM_SP_Rel_6_Editor_UG_Jul88.pdf|VM/SP System Product Editor User's Guide Release 6]]|18-07-2018|User guide for XEDIT, **release 6.** |
^ [[http://bitsavers.org/pdf/ibm/370/VM_SP/Release_6_Jul88/SC24-5221-05_VM_SP_Rel_6_System%20Product%20Editor%20Command%20and%20Macro%20Ref_Aug88.pdf|VM/SP System Product Editor Command and Macro Reference Release 6]] |18-07-2018|Command Reference for XEDIT, **release 6.** |
^ [[http://bitsavers.org/pdf/ibm/370/VM_SP/Release_6_Jul88/SC24-5239-03_VM_SP_Rel_6_Interpreter_Jul88.pdf|VM/SP System Product Interpreter User's Guide Release 6]]|18-07-2018|Rexx User Guide, **release 6.** |
^ [[http://bitsavers.org/pdf/ibm/370/VM_SP/Release_6_Jul88/SC24-5239-03_VM_SP_Rel_6_Interpreter_Jul88.pdf|Vm/SP System Product Interpreter Reference Release 6]]|18-07-2018|Rexx Reference, **release 6.**|
^ [[http://bitsavers.org/pdf/ibm/370/VM_SP/Release_5_Dec86/SC19-6209-4_VM_SP_CMS_Command_Reference_Release_5_Dec86.pdf|VM/SP EXEC2 Reference Release 5]]|18-07-2018|Reference for the older EXEC 2 language. |
^ [[http://www.bitsavers.org/pdf/ibm/370/VM_SP/Release_1/SC19-6209-0_VM_SP_CMS_Command_and_Macro_Reference_Sep80.pdf|VM/SP CMS Command and Macro Reference]]|16-12-2018|Early version of the CMS Command Reference above, but also includes CMS Assembler Macros for programming.  **release 1.**|
^ [[http://bitsavers.org/pdf/ibm/370/VM_SP/Release_5_Dec86/SC24-5286-0_VM_SP_CMS_for_System_Programming_Release_5_Dec86.pdf|VM/SP CMS for Systems Programming Release 5]]|18-07-2018|A guide to CMS for heavy hitting IBM Assembler Programmers. \\ \\ It will bring out your inner CMS geek or send you screaming. (Or both.)|
^ [[http://bitsavers.org/pdf/ibm/370/VM_SP/Release_5_Dec86/SC24-5288-0_VM_SP_System_Facilities_for_Programmers_Release_5_Dec86.pdf|VM/SP System Facilities for Programming Release]]|18-07-2018|Like the guide to CMS above, a guide to CP for heavy hitting IBM Assembler Programmers. \\ \\ It will bring out your inner CP geek or send you screaming. (Or both.)|

==== Other VM related documents ====

^  Title  ^  <html>&nbsp;&nbsp;Retrieved&nbsp;&nbsp;</html>  ^  Comments  ^
^ [[http://bitsavers.org/pdf/ibm/370/VM_SP/|Bitsavers VM/SP manual archive]] | 07-18-2018 | Index to All VM files collected by the archive. If looking for a particular manual and it's not found under [[http://bitsavers.org/pdf/ibm/370/VM_SP/Release_5_Dec86/|Release 5 Dec86]], look to the newer and older releases for a near match. |
^ [[http://www.bitsavers.org/pdf/ibm/360/os/call_360/CALL_360_BASIC_Reference_Handbook_1970.pdf|CALL/360: BASIC Reference Handbook]] | 12-14-2018 | |           
^ [[http://publibfp.boulder.ibm.com/epubs/pdf/afbu2002.pdf|VS FORTRAN Version 2 Programming Guide for CMS and MVS]]|07-18-2018 | |
^ [[http://www.vm.ibm.com/devpages/HUGENBRU/BASICS.PDF|The Basics of Using z/VM]]|07-18-2018| Introduction referenced at the top of this guide. |
^ [[http://rexxla.org/rexxlang/Rexx_Programmers_Reference.pdf|Rexx Programmer's Reference]]|07-18-2018|Third partry Rexx reference from the [[http://rexxla.org/|The Rexx Language Association]]|
^ [[http://www.snee.com/bob/opsys/part5vmcms.pdf|VM/CMS. Fake Your Way Through Minis and Mainframes.]]| 07-18-2018 | Third party tutorial on CMS |
^ [[http://chiclassiccomp.org/docs/content/computing/IBM/Mainframe/OS/VM/198605_VM%20CMS%20User%20Guide%20and%20Reference%20Manual.pdf|VM/CMS User Guide and Reference Manual]] |07-18-2018 | Another (less useful) third party tutorial on CMS |
^ [[http://bitsavers.org/pdf/ibm/370/VM_SP/Release_4_Dec84/GC20-1838-4_VM_SP_General_Information_Release_4_Jun84.pdf|VM/SP General Information Release 4]]|18-07-2018|General overview, not very useful in the LCML environment.  For **Release 4**. |
User Tools

Site Tools

Page Tools
