(remove trailing blanks)

[skip travis]

README.md

@@ -1,4 +1,4 @@
-![SDL Hyperion](/readme/images/image_header_herculeshyperionSDL.png)  
+![SDL Hyperion](/readme/images/image_header_herculeshyperionSDL.png)
 [![Build Status](https://travis-ci.org/SDL-Hercules-390/hyperion.svg?branch=master)](https://travis-ci.org/SDL-Hercules-390/hyperion)
 
 ## The [SoftDevLabs](http://www.softdevlabs.com) version of Hercules 4.x (Hyperion)
@@ -29,42 +29,42 @@ To find out more about this particular version of Hercules 4.x Hyperion, follow
 ## Additional README files
 
 ### Building Hercules
-[Building Hercules under AIX](readme/README.AIX.md)  
-[Building Hercules under BSD/OSX](readme/README.BSD.md)  
-[Budiling Hercules for OSX](readme/README.OSX.md)  
-[Building Hercules under 64-bit Windows](readme/README.WIN64.md)  
-OBSOLETE [Building Hercules with MinGW](readme/README.MINGW.md)  
-OBSOLETE [Building Hercules for Windows with Visual C](readme/README.MSVC.md)  
-[Hercules "External Packages"](readme/README.EXTPKG.md)  
-[HercIFC and Hercules as setuid root programs](readme/README.SETUID.md)  
-[HQA Build Scenarios](readme/README.HQA.md)  
-[How to build Hercules from SVN under Solaris](readme/README.SUN.md)  
-[Low-level Test Cases](tests/README.md)  
+[Building Hercules under AIX](readme/README.AIX.md)
+[Building Hercules under BSD/OSX](readme/README.BSD.md)
+[Budiling Hercules for OSX](readme/README.OSX.md)
+[Building Hercules under 64-bit Windows](readme/README.WIN64.md)
+OBSOLETE [Building Hercules with MinGW](readme/README.MINGW.md)
+OBSOLETE [Building Hercules for Windows with Visual C](readme/README.MSVC.md)
+[Hercules "External Packages"](readme/README.EXTPKG.md)
+[HercIFC and Hercules as setuid root programs](readme/README.SETUID.md)
+[HQA Build Scenarios](readme/README.HQA.md)
+[How to build Hercules from SVN under Solaris](readme/README.SUN.md)
+[Low-level Test Cases](tests/README.md)
 
 ### Mods
-[APL/360 mods](readme/README.APL360.md)  
-[ECPS:VM & Extended VM Assists](readme/README.ECPSVM.md)  
-[Hercules CMPSC "Compression Call" instruction support](/readme/README.CMPSC.md)  
-[Hercules Dynamic Modules (on Windows)](readme/README.DYNMOD.md)  
-[Preliminary 2703 BSC Support](readme/README.COMMADPT.md)  
-[RXVT4APL Mods](readme/README.RXVT4APL.md)  
+[APL/360 mods](readme/README.APL360.md)
+[ECPS:VM & Extended VM Assists](readme/README.ECPSVM.md)
+[Hercules CMPSC "Compression Call" instruction support](/readme/README.CMPSC.md)
+[Hercules Dynamic Modules (on Windows)](readme/README.DYNMOD.md)
+[Preliminary 2703 BSC Support](readme/README.COMMADPT.md)
+[RXVT4APL Mods](readme/README.RXVT4APL.md)
 
 ### Features and Operation
-[Customizable Hercules 3270 Logo](readme/README.HERCLOGO.md)  
-[Guest Access To Host IP Stack - The TCPIP (X'75') Instruction](readme/README.TCPIP.md)  
-[Hercules Automatic Operator](readme/README.HAO.md)  
-[Hercules CCKD64 Support](readme/README.CCKD64.md)  
-[Hercules Dynamic Loader](readme/README.HDL.md)  
-[Hercules Networking](readme/README.NETWORKING.md)  
-[Hercules PTT Tracing](readme/README.PTT.md)  
-[Hercules REXX Support](readme/README.REXX.md)  
-[Hercules Tape Support Enhancements SPE/Fixes](readme/README.TAPE.md)  
-[Host Resource Access Facility](readme/README.HRAF.md)  
-[S/370 Backport of select ESA/390 and z/Architecture instructions](readme/README.S37X.md)  
-[VMFPLC2 (VM) Formatted Tape Utility](readme/README.VMFPLC2.md)  
+[Customizable Hercules 3270 Logo](readme/README.HERCLOGO.md)
+[Guest Access To Host IP Stack - The TCPIP (X'75') Instruction](readme/README.TCPIP.md)
+[Hercules Automatic Operator](readme/README.HAO.md)
+[Hercules CCKD64 Support](readme/README.CCKD64.md)
+[Hercules Dynamic Loader](readme/README.HDL.md)
+[Hercules Networking](readme/README.NETWORKING.md)
+[Hercules PTT Tracing](readme/README.PTT.md)
+[Hercules REXX Support](readme/README.REXX.md)
+[Hercules Tape Support Enhancements SPE/Fixes](readme/README.TAPE.md)
+[Host Resource Access Facility](readme/README.HRAF.md)
+[S/370 Backport of select ESA/390 and z/Architecture instructions](readme/README.S37X.md)
+[VMFPLC2 (VM) Formatted Tape Utility](readme/README.VMFPLC2.md)
 
 ### Hercules Architecture
-[Hercules Input/Output Architecture](readme/README.IOARCH.md)  
+[Hercules Input/Output Architecture](readme/README.IOARCH.md)
 
 ### Issues
-[Unresolved Issues](readme/README.ISSUES.md)  
+[Unresolved Issues](readme/README.ISSUES.md)

cckddiag.c

@@ -573,7 +573,7 @@ char            pathname[ MAX_PATH ];   /* file path in host format  */
 
         switch(argv[0][1])
         {
-            case 'v':  
+            case 'v':
                     if (argv[0][2] != '\0')
                     {
                         syntax (pgm);

general3.c

@@ -3985,7 +3985,7 @@ VADR    effective_addr2;                /* Effective address         */
 /*-------------------------------------------------------------------*/
 /* EBE1 STOCFH - Store High On Condition                       [RSY] */
 /*-------------------------------------------------------------------*/
-DEF_INST( store_high_on_condition) 
+DEF_INST( store_high_on_condition)
 {
 int     r1, m3;                         /* Register number, mask     */
 int     b2;                             /* Base of effective addr    */

hscutl.c

@@ -1751,7 +1751,7 @@ DLL_EXPORT void gen_dasd_serial( BYTE* serial )
             buf[i] = '0' + (rand() % 10);
         buf[12] = 0;
     }
-    while (str_eq( buf, prev )); 
+    while (str_eq( buf, prev ));
     memcpy( prev,   buf, 12 );
     memcpy( serial, buf, 12 );
 }

readme/README.AIX.md

@@ -25,7 +25,7 @@ Autoconf/automake require some pre-requisites, such as gettext, info, m4, libsig
 The above is based on efforts done by Alexey Bozrikov [[email protected]], Harold Grovesteen [[email protected]] and Fish [[email protected]] on the [Hercules-390 Yahoo group](https://groups.yahoo.com/neo/groups/hercules-390) list during the month of October 2009.
 
 ## ToDo:
-The followings items are still remaining to do: 
+The followings items are still remaining to do:
   - Get SCSI tape working: resolve `<sys/mtio.h>` header & `struct mtget` issue(s).
 ```
 #if defined( HAVE_STRUCT_MTGET_MT_GSTAT )

readme/README.CCKD64.md

@@ -7,7 +7,7 @@
 2. [Conversion to CCKD64](#Conversion-to-CCKD64)
 3. [Procedure](#Procedure)
 4. [Additional Information](#Additional-Information)
-  
+
 ## About CCKD64
 Version 4.2 of SDL Hercules Hyperion introduced support for very large Compressed CKD (CCKD) dasd image files, called CCKD64, which can be much larger than 4GB in size.
 
@@ -27,13 +27,13 @@ It is critical the dasd images being converted not have any errors before they a
 
 Using the 'convto64' utility to convert existing CCKD files to the CCKD64 format is recommended over using dasdcopy64 as it is not only significantly faster than dasdcopy64 but is also able to convert individual CCKD shadow files as well (which dasdcopy64 cannot currently do).  That is to say, if you already have a CCKD format base dasd image file with one or more shadow files associated with it, dasdcopy64 can only copy the base image plus all of its shadow files to a single new CCKD64 base image file (i.e. the shadow files are automatically "merged" during the copy operation, resulting in a single CCKD64 BASE dasd image output file).  The 'convto64' utility however, directly converts base images -OR- shadow files individually, resulting in a new CCKD64 format base image or CCKD64 format shadow file.  It does NOT "merge" them together and, as previously mentioned, is significantly faster than dasdcopy64 too.  It is the recommended way to convert existing CCKD dasd images to the new CCKD64 format.
 
-In addition to the new 'dasdinit64' and 'dasdcopy64' utilities, there are also corresponding CCKD64 versions of:  
-'cckdcdsk' check disk utility called 'cckdcdsk64'  
-'cckdcomp' utility called 'cckdcomp64'  
-'cckdswap' called 'cckdswap64'  
-'cckddiag' diagnostic utility called 'cckddiag64'  
-'dasdconv' utility called 'dasdconv64'  
-'dasdload' utility called 'dasdload64'  
+In addition to the new 'dasdinit64' and 'dasdcopy64' utilities, there are also corresponding CCKD64 versions of:
+'cckdcdsk' check disk utility called 'cckdcdsk64'
+'cckdcomp' utility called 'cckdcomp64'
+'cckdswap' called 'cckdswap64'
+'cckddiag' diagnostic utility called 'cckddiag64'
+'dasdconv' utility called 'dasdconv64'
+'dasdload' utility called 'dasdload64'
 
 The existing dasdls, dasdcat, dasdpdsu, dasdisup, and dasdseq utilities do not have any specialized CCKD64 versions.  However, all of them do support the new CCKD64 file format in addition to the existing CCKD file format; they just don't have separate executable names ending in '64' as they have all been updated to support either of the two formats automatically.
 

readme/README.COMMADPT.md

@@ -111,13 +111,13 @@ x x x x 1 1 0 0 : EON
 x x x x 1 1 0 1 : SEP
 ```
 
-In order to perform an outgoing call, the data must follow these specifications:  
-        `N[N[N]]SEPN[N[N]]SEPN[N[N]]SEPN[N[N]]]SEPN[..[N]][EON]`  
-Where N is any dialing number from 0 to 9 and SEP is the separator.  
+In order to perform an outgoing call, the data must follow these specifications:
+        `N[N[N]]SEPN[N[N]]SEPN[N[N]]SEPN[N[N]]]SEPN[..[N]][EON]`
+Where N is any dialing number from 0 to 9 and SEP is the separator.
 
 The 4 first group of digits represet the IP address.  The last group represent a TCP port number.
-For example (* is the SEP character representation):  
-        `192*168*0*1*8888 : will issue a TCP connection to 192.168.0.1 port 8888`  
+For example (* is the SEP character representation):
+        `192*168*0*1*8888 : will issue a TCP connection to 192.168.0.1 port 8888`
 The EON is optional. If it is present, it must be the last character of the dial data.
 
 ## Bugs, Caveats

readme/README.ECPSVM.md

@@ -92,15 +92,15 @@ To determine the feature names, type `ecpsvm enable ALL`.  All of the enabled fe
 The ecpsvm command is NOT case sensitive.
 
 ## Determining if the assist is used by VM
-Use the 2 following CLASS A commands:  
-`CP QUERY CPASSIST`  
-`CP QUERY SASSIST`  
+Use the 2 following CLASS A commands:
+`CP QUERY CPASSIST`
+`CP QUERY SASSIST`
 
 Both queries should return `ON`.
-Also use the following CLASS G Command:  
-`CP QUERY SET`  
+Also use the following CLASS G Command:
+`CP QUERY SET`
 2nd line should indicate:
-`ASSIST ON SVC TMR`  
+`ASSIST ON SVC TMR`
 
 ## Technical information
 The CP Assists provides the VM System Control Program (SCP) with various microcoded instructions to shorten the supervisor pathlength. All microcoded instructions are privileged instructions and have an opcode of E6xx. They are native representation of what the SCP would do in a similar case. For all cases where the assist is not able to correctly assist the SCP, the E6xx instructions resolve to a no-op, thus leaving the responsibility of the task to the original CP code.
@@ -166,14 +166,14 @@ Therefore, CP will fairly quickly abend because it will find some of the control
 
 This updated version of the ECPS:VM support provides the capability to operate with or without the FREE/FRET trap in effect.  The assist can automatically determine at IPL time whether it needs to operate with the trap or without the trap.  If the trap is enabled, all of the supported assists listed above are enabled.
 
-It is still possible to use ECPS:VM without any additional support for the FREE/FRET trap by simply specifying:  
-`ECPSVM YES NOTRAP`  
+It is still possible to use ECPS:VM without any additional support for the FREE/FRET trap by simply specifying:
+`ECPSVM YES NOTRAP`
 in the Hercules configuration file.  In this case, the assists that cannot operate with the trap in effect will automatically be disabled as before.  This means that the DISP1, DISP2, FREEX, and FRETX assists will be disabled.  If the trap is not present, all assists are enabled and NOTRAP has no meaning.
 
-Otherwise, regardless of whether the FREE/FRET trap is present, ECPS:VM will attempt to operate with all assists enabled with or without the trap when specifying:  
-`ECPSVM YES`  
-    or  
-`ECPSVM YES TRAP`  
+Otherwise, regardless of whether the FREE/FRET trap is present, ECPS:VM will attempt to operate with all assists enabled with or without the trap when specifying:
+`ECPSVM YES`
+    or
+`ECPSVM YES TRAP`
 
 (`ECPSVM YES` and `ECPSVM YES TRAP` are functionally equivalent.)
 

readme/README.EXTPKG.md

@@ -5,9 +5,9 @@
 ## Contents
 1. [Overview](#Overview)
 2. [Linux](#Linux)
-3. [Building the External Packages for a Windows-based Hyperion](#Building-the-External-Packages-for-a-Windows-based-Hyperion)  
-  3a. [Summary of the steps involved](#Summary-of-the-steps-involved)  
-  3b. [Detailed Instructions](#Detailed-Instructions)  
+3. [Building the External Packages for a Windows-based Hyperion](#Building-the-External-Packages-for-a-Windows-based-Hyperion)
+  3a. [Summary of the steps involved](#Summary-of-the-steps-involved)
+  3b. [Detailed Instructions](#Detailed-Instructions)
 
 ## Overview
 This version of Hercules 4.x Hyperion links with several "external package" static libraries.
@@ -26,11 +26,11 @@ Each external package is built separately from the Hercules emulator and then "i
 
 Currently, there are four such external packages this Hercules 4.x Hyperion links with.  These packages are the "crypto", "decNumber", "SoftFloat", and "telnet" packages.  Each of these package names correspond to an existing subdirectory of Hyperion.  Over time additional Hercules functionality will be moved out of the emulator into their own separately maintained and built external package repositories, eventually reducing the Hercules emulator to just its core functionality: accurate emulation of the System/370, ESA/390, and z architectures.
 
-The four repositories for the external packages can be located at these URLs:  
-[https://github.com/sdl-hercules-390/crypto](https://github.com/sdl-hercules-390/crypto)  
-[https://github.com/sdl-hercules-390/decNumber](https://github.com/sdl-hercules-390/decNumber)  
-[https://github.com/sdl-hercules-390/SoftFloat](https://github.com/sdl-hercules-390/SoftFloat)  
-[https://github.com/sdl-hercules-390/telnet](https://github.com/sdl-hercules-390/telnet)  
+The four repositories for the external packages can be located at these URLs:
+[https://github.com/sdl-hercules-390/crypto](https://github.com/sdl-hercules-390/crypto)
+[https://github.com/sdl-hercules-390/decNumber](https://github.com/sdl-hercules-390/decNumber)
+[https://github.com/sdl-hercules-390/SoftFloat](https://github.com/sdl-hercules-390/SoftFloat)
+[https://github.com/sdl-hercules-390/telnet](https://github.com/sdl-hercules-390/telnet)
 
 The procedure for building each of the external packages is outlined further below.  More information about each of the packages can be found in a README document within each of their respective repositories.
 
@@ -68,15 +68,15 @@ Place these files into your local 'bin' directory (or if you don't have such a d
 
 Adjust the "ExtPkgs.cmd.ini" as needed for your system (e.g. `cpu = arm`).
 
-4.  Now clone and build the external packages by making the package install directory your current directory and issuing the `ExtPkgs`(*) command to clone, build and install all of the packages at once directly into your installation directory:  
+4.  Now clone and build the external packages by making the package install directory your current directory and issuing the `ExtPkgs`(*) command to clone, build and install all of the packages at once directly into your installation directory:
        chdir  \extpkgs
        ExtPkgs.cmd      CLONE   c  d  s  t        (see footnote at end)
 
 Depending on the speed of your system it may take anywhere from a couple of minutes to several minutes to finish building all of the packages.
 
-5.  Update your "LIB" and "INCLUDE" environment variables (on Linux this would be your "LIBRARY_PATH" and "CPATH" variables) to point to the directory where your packages were just installed:  
-        setx LIB "%LIB%;\extpkgs\lib"  
-        setx INCLUDE "%INCLUDE%;\extpkgs\include"  
+5.  Update your "LIB" and "INCLUDE" environment variables (on Linux this would be your "LIBRARY_PATH" and "CPATH" variables) to point to the directory where your packages were just installed:
+        setx LIB "%LIB%;\extpkgs\lib"
+        setx INCLUDE "%INCLUDE%;\extpkgs\include"
 
 6.  Build Hercules as normal.  (self explanatory)
 

readme/README.HAO.md

@@ -17,11 +17,11 @@ To use the Hercules Automatic Operator facility, one first defines a "rule" cons
 The Hercules Automatic Operator facility is **only** for those messages issued **by Hercules** to its HMC (hardware console). It **cannot** be used for whatever messages the guest operating system may issue to any of its terminals. It is only a **Hercules** automatic operator and **not** a "VSE", "MVS", "VM", etc, automatic operator!
 
 ## Defining a rule
-To define a HAO rule, enter the command:  
-    hao  <tgt>  
-to define the rule's "target" match pattern (a simple regular expression), followed by the command:  
-    hao  <cmd>  
-to define the rule's associated panel-command.  
+To define a HAO rule, enter the command:
+    hao  <tgt>
+to define the rule's "target" match pattern (a simple regular expression), followed by the command:
+    hao  <cmd>
+to define the rule's associated panel-command.
 
 The target pattern is a simple regular expression value as defined by whatever regular expression support your supported host build platform happens to support. For Windows it must be a Perl Compatible Regular Expression (PCRE).
 For other supported build platforms it might be some other supported regular expression syntax. Check your host platform's programming documentation for further details.

readme/README.HDL.md

@@ -14,15 +14,15 @@
 The dynamic loader is intended to supply a loading and linking mechanism, whereby routines, commands, instructions and functions can be dynamically added to hercules, without the need to rebuild or even restart hercules.
 
 ## Commands
-The loader can be controlled by the following hercules commands:  
+The loader can be controlled by the following hercules commands:
 ```
 ldmod <module list>    - Load modules named in module list
 rmmod <module list>    - Unload modules named in list
 lsmod                  - List all modules and entry points
 lsdep                  - List all dependencies
 ```
 
-The ldmod statement may also appear in the hercules configuration file.  
+The ldmod statement may also appear in the hercules configuration file.
 ```
 configuration statement:
 modpath <pathname>     - Specifies where modules are loaded from
@@ -32,7 +32,7 @@ modpath <pathname>     - Specifies where modules are loaded from
 The loader has 2 basic functions: module load and module unload.
 
 ###  Module load
-`int hdl_load(char *name, int flags);`  
+`int hdl_load(char *name, int flags);`
 Where name is the module name, this name may include the path.  If no path is given then the module is loaded from the default library search order.  Note that this is different from the standard search order.
 
 Flags may be one of the following:
@@ -45,15 +45,15 @@ Flags may be one of the following:
 This function returns a zero value when the load is successful.
 
 ### Module unload
-`int hdl_dele(char *name);`  
+`int hdl_dele(char *name);`
 Where name is the name of the module that is to be unloaded.
 This function returns a zero value when the unload is successful.
 
 ## Resolving Symbols
-`void * HDL_FINDSYM(char *symbolname);`  
+`void * HDL_FINDSYM(char *symbolname);`
 This function will return the entry point of symbolname or zero when the symbol cannot be resolved.
 
-`void * HDL_FINDNXT(current_entry point);`  
+`void * HDL_FINDNXT(current_entry point);`
 This function will return the previous entry point.
 That is, the entry point which was current before the entry point as identified by current_entry point was registered.