s390guy/vm370

vm370's Issues

MAINT PROFILE EXEC needs reasonable additions

For building nuclei and basic edit maneuvering, please consider adding the common customizations to PROFILE EXEC on MAINT's 191 disk. Thanks!

CP SPOOL PUN *
CP SPOOL PRT *
CP SET PF12 RETRIEVE
CP SET PF3 IMMED FILE
CP SET PF7 IMMED UP 8
CP SET PF8 IMMED DOWN 8

CMS edit artifact issue

The best way to describe this one is to perform the following steps: (I did this in maint)

1. type FLIST
2. press PF10 (in my case twice to select USER DIRECT)
3. press PF11 (to edit the file)
4. once in edit type DOWN 20
5. type QUIT

You should now see the bottom line from the bottom of the edit screen on the FLIST panel. In my case it was
"USER $TEMP$ NOLOG"

Screen shot attached

Re-address VMCE DASD (split from issue #12)

@BobBolch opined:

I had planned to consolidate the Community Edition 3350s on a single string
of addresses from 140-14F.
I see that the tk4- setup uses those addresses. It is easy to change the
tk4- setup? Could we wall off
a set of addresses (with some spares) to be used for a tk4- guest? Maybe I
should use
something else for VM disks (6A0-6BF?).

Bob

Originally posted by @BobBolch in #12 (comment)

MAINT 494 disk damaged

The MAINT 494 minidisk seems to be damaged. It mounts okay and you can list files on it, but copying anything off of the minidisk results in a DMSCPY error on (presumably) any file accessed:

ACC 494 A
DEFINE T3350 as 100 cyl 15
FORMAT 100 Z
(YES, TMP100)

copy * * a = = z (oldd
DMSCPY901T UNEXPECTED ERROR AT 021A4A: PLIST 'RDBUF ASMIF EXEC A1' AT 023494, BASE: 020000, RC 3.
Ready(00256); T=0.01/0.01 18:27:08

copy * text a = = z
DMSCPY901T UNEXPECTED ERROR AT 021A4A: PLIST 'RDBUF DMKACO TEXT A1' AT 023494, BASE: 020000, RC 3.
Ready(00256); T=0.01/0.02 18:28:16

copy * macro a = = z
DMSCPY901T UNEXPECTED ERROR AT 021A4A: PLIST 'RDBUF LDRST MACRO A1' AT 023494, BASE: 020000, RC 3.

copy DMSLDR AUXR60 A1 = = z
DMSCPY901T UNEXPECTED ERROR AT 021A4A: PLIST 'RDBUF DMSLDR AUXR60 A1' AT 023494, BASE: 020000, RC 3.

(it's also mislabeled, but since the disk is mostly useless at this point, thats not worth complaining about :) )

Offer of Update GCC HELPCMD and GCC HELPCMD2

For your consideration. If I need to put this in another format, or another place, please let me know.

GCC HELPCMD
******************************************************************************
GCC                                                                    CMS EXEC
 
Use the GCC command to compile and assemble a C source file using the GNU C
compiler.  Then use the LOAD and START commands to run the program:

   gcc hello
   load hello
   start

The format of the GCC command is:
+----------+------------------------------------------------------------------+
| GCC      | [fn [ft|C [fm|A]]] [( [options]                                  |
|          | options:                                                         |
|          |    ASM|NOASM     CSECT|NOCSECT     KEEP|NOKEEP     LIB fn        |
|          |    OS|CMS        PARM fn                                         |
+----------+------------------------------------------------------------------+
where:
 
fn [ft [fm]]
         identifies the C source file to be compiled.  ft defaults to C and fm
         defaults to A.
 
Options:
 
ASM|NOASM
         specifies whether the ASSEMBLE output file from the C compiler is to
         be assembled or not.  ASM is the default.
 
CSECT|NOCSECT
         specifies that the blank CSECT statement produced by GCC is to be
         given a label. NOCSECT is the default.  CSECT is required only when
         building a library of C routines.
 
KEEP|NOKEEP
         specifies whether or not the assembler output files from the C
         compiler are to be kept or erased.  NOKEEP is the default.
 
LIB fn   specifies the runtime library with which the program is to be
         compiled.  GCC will link and access the appropriate disk containing
         the C header files.  Two runtime libraries are available:
         GCCLIB  uses only "native" CMS functions for system services.  Using
                 this library it is possible to write programs that may be
                 loaded into resident memory as extensions of the CMS nucleus.
                 For example, you can open CMS files directly by name.
 
                 Ensure GCCLIB is in your list of GLOBAL TXTLIBs to run your
                 compiled progam.  Type HELP GCCLIB for more information.
 
         PDPCLIB uses simulated OS functions for system services, just like
                 FORTRAN or PL/I.  For example, you must use the FILEDEF
                 command to identify CMS files to your program.
 
                 Ensure PDPCLIB is in your list of GLOBAL TXTLIBs to run your
                 compiled progam.
 
         LIB PDPCLIB is the default.
 
OS|CMS   OS is shorthand for LIB PDPCLIB.  CMS is shorthand for LIB GCCLIB.
 
PARM fn  specifies a file of type PARM containg arguments to pass to GCC.  By
         default 'GCC PARM *' is used.  The fn PARM file may be RECFM F|V,
         and the LRECL may be anything less than 32767 characters in length.

 
For more details, type HELP GCC ( MORE

------------------------------------------------------------------------------
For your consideration ...

Would the 'fn' of 'PARM fn' be better off looking for the 'fn' found in the
EXEC when it is executed?

Such as:

GCC ZIP C A

would then search for ZIP PARM * ?
------------------------------------------------------------------------------
******************************************************************************

GCC HELPCMD2
*******************************************************************************
GCC                                                                    CMS EXEC
 
Usage Notes:
 
1.  To compile a C program called HELLO C A, type
       GCC HELLO
    To run the program, you must have the appropriate TXTLIB specified.  Use
    the GLOBAL command to do this:
       GLOBAL TXTLIB PDPCLIB
    Now you can load and run the program:
       LOAD HELLO
       START
    Alternatively you can create a module of your program:
       LOAD HELLO
       GENMOD HELLO
    Now you can invoke the program by typing its name:
       HELLO
 
2.  If your program does any I/O you must use the FILEDEF command to define
    those files to your program.  Then in the program refer to the ddname you
    specified on the FILEDEF command.  For example, if in your C program you
    code:
       fopen("DD:TEST", "w");
    You would need to issue this FILEDEF command before running the program:
       FILEDEF TEST DISK TEST DATA A (LRECL 80 RECFM V
 
3.  The source code for the GCC compiler and runtime libraries is on the
    GCCCMS userid disks.
 
4.  An alternate runtime library called GCCLIB is available for C programs.
    This runtime library lets you code C programs that directly access CMS
    system services.  Type HELP GCCLIB for more information.

-------------------------------------------------------------------------------
For your consideration. I do not know which of the following is correct, but
it would be helpful for the user to know.
 
The following options can be placed in the file 'fn PARM *' referenced by
the 'PARM fn' option on the command line. The fn PARM file may be
RECFM F|V, and the LRECL may be anything less than 32767 characters in
length.

(
The options MAY exist on multiple records.
-or-
The options MUST exist on one record.
)

(
The continuation character is identified as '|'.
-or-
There is NO continuation charcter.
)
-------------------------------------------------------------------------------

Options: 
  -pass-exit-codes         Exit with highest error code from a phase 
  --help                   Display this information 
  --target-help            Display target specific command line options 
  (Use '-v --help' to display command line options of sub-processe s) 
  -dumpspecs               Display all of the built in spec strings 
  -dumpversion             Display the version of the compiler 
  -dumpmachine             Display the compiler's target processor 
  -print-search-dirs       Display the directories in the compiler's search
                           path 
  -print-libgcc-file-name  Display the name of the compiler's companion library 
  -print-file-name=<lib>   Display the full path to library <lib> 
  -print-prog-name=<prog>  Display the full path to compiler component <prog> 
  -print-multi-directory   Display the root directory for versions of libgcc 
  -print-multi-lib         Display the mapping between command line options and 
                           multiple library search directories 
  -print-multi-os-directory Display the relative path to OS libraries 
  -Wa,<options>            Pass comma-separated <options> on to the assembler
  -Wp,<options>            Pass comma-separated <options> on to the
                           preprocessor
  -Wl,<options>            Pass comma-separated <options> on to the linker 
  -Xlinker <arg>           Pass <arg> on to the linker 
  -save-temps              Do not delete intermediate files 
  -pipe                    Use pipes rather than intermediate files 
  -time                    Time the execution of each subprocess
  -specs=<file>            Override built-in specs with the contents of <file> 
  -std=<standard>          Assume that the input sources are for <standard> 
  -B <directory>           Add <directory> to the compiler's search paths 
  -b <machine>             Run gcc for target <machine>, if installed 
  -V <version>             Run gcc version number <version>, if installed 
  -v                       Display the programs invoked by the compiler 
  -###                     Like -v but options quoted and commands not executed 
  -E                       Preprocess only; do not compile, assemble or link 
  -S                       Compile only; do not assemble or link 
  -c                       Compile and assemble, but do not link 
  -o <file>                Place the output into <file> 
  -x <language>            Specify the language of the following input files
                           Permissable languages include: c c++ assembler none
                           'none' means revert to the default behavior of
                           guessing the language based on the file's extension 
 
Options starting with -g , -f, -m, -O, -W, or --param are automatically 
 passed on to the various sub-processes invoked by CP.  In order to pass 
 other options on to these processes the -W<letter> options must be used.

Additional information on gcc can be found at:
https://gcc.gnu.org/onlinedocs/gcc-3.2.3/gcc/index.html
*******************************************************************************

... Mark S.

FLIST screen locked after quit from EE of one file

Perhaps this also solves the weirdness that happens when you enter EE to edit a file from FLIST, and then QUIT it. It leave some remaining text at the bottom of the screen, and the terminal is locked for a while and pressing RESET and/or CLEAR, or PA1 etc, does not help.
If this update doesn't fix that, at least I told you about it :)

Multiple versions of RSCS MEMO

HELP WELCOME ( MORE directs the reader to a version of the RSCS MEMO file on the MAINT 09F disk. A newer version of the file is on the MAINT 5E5 disk, in the VM/370 Community Edition Version 1 Release 1.1 system. Update HELP WELCOME ( MORE to reference the new version and remove the older version of the RSCS MEMO file..

New VMCE disks initialized differently

Jay Maynard ran into a Hercules issue specific to his environment.
I initialized the new disk volumes using -bz2 instead of -z in dasdinit.
He did not have the bz2 support generated into his Hercules.
For consistancy, all the disk volumes should have been initialized with the
same parameters.

Shadow Disks Contain Dada

Normally the shadow disks are distributed as blank. Then users can simply back up the shadow disks.

The PASCAL Compiler is down-level

http://bernd-oppolzer.de/job9.htm

the actual compiler which can be downloaded from the site mentioned above is version number 2021.01
(year and month of release)
and I am working on the 2021.03 release. The compiler is still MUCH better than the 2017 version,
it now has strings, static variables with initialization at compile time and much more, and IMO
it now can be considered a competitor to IBMs Pascal/VS (although it still has some bugs, probably).
In contrast to IBMs Pascal, it works on other platforms like Windows and Unix etc., too (same Pascal
variant, no difference in the language, P-Code files can be ported between platforms). And MVS ...
If you give it a try and find severe errors (which I don't know yet), I will try to fix them as soon as possible.

DMKSNT entry for CMSTEST saved segment has wrong cylinde number

Align config with MVS TK4-

MVS.DIRECT.TXT
MVS.CONF.TXT

One of the first things I change with any of the older sixpack releases is to change the MVS config to support IPLing TK4- under VM/370 - it works pretty well, but I've always wondered where the default configuration in the sixpack comes from.

Here is a small diff to vm370ce.conf and USER DIRECT that configures the system to use TK4-'s dasd config out of the box. All you need to do is create a directory named "mvs" under the VM370CE home dir, and unzip the TK4- distribution into it.

I should write up some simple instructions on IPLing TK4- under VM/370 and shutting it down (the standard procedures work fine, but running it as a VM doesn't trigger TK4-'s nice automatic scripting stuff).

Joe

USER DIRECT nitpicking

This is more of an issue for me personally than the community, but I'll put it here for comment. The user directory is a hot mess. Well, maybe a lukewarm mess. At least a tepid mess. Attached is a USER DIRECT for comment that includes the following organizational changes:

1. Language users (ALGOL, FORTRAN, ETC) converted to NOLOG if they're just owning minidisks
2. Consistent linking of MAINT 19D for user interactive accounts
3. Reformatting MDISK lines to support 4 digit starting cylinder and lengths for MDISKS on 3380 DASD
4. Standardized common entries across accounts (order/formatting of OPTIONS/IPL/LINK/SPOOL lines)
5. Inclusion of MVS changes for TK4- as a client from issue# 12
6. Documenattion (such as it is) on how to use the DOSVS user entry
7. "Arbitrary" MDISK numbering of VM volumes (like in $ALLOC$ and MAINT) mapped to proper addresses (virt cuu = real cuu)

USER.DIRECT.TXT

NUCXDROP command missing

Someone who will remain nameless forgot to generate the NUCXDROP MODULE on Community Edition V1R1.0

You might not miss it. Since NUCXLOAD isn;t there, only self-loading Nucleus Extensions work in VM/370.
NUCXLOAD is going to need relocatable MODULE support to match VM/SP and later, although I am testing
a NUCXTEXT command that will load and relocate TEXT files and establish a Nucleus Extension from them.

In the meantime, use these steps to generate the NUCXDROP MODULE.

LOGON MAINT
VMSETUP CMS
LOAD DMSNXD ( CLEAR ORIGIN TRANS
GENMOD NUCXDROP MODULE A2
ACCESS 190 Z
COPY NUCXDROP MODULE A = = Z2 ( OLDDATE
RELEASE Z
DEFINE STOR 16M
IPL 190 CLEAR
SAVESYS CMS
ERASE NUCXDROP MODULE A2

Add SFBROWSE utility to VM/CE

Source is on the H390 downloads area. Rene Ferland is writing a HELP file.

Floating Point Errors with SDL Hercules 4.3.0.10296-

There is a bug in the above Hercules which affects Floating Point and causes the SNTPARS EXEC to fail

. Disable ECPS disp1 and disp2 e.g.

ecpsvm disable disp2 disp2

a fix is available but currently requires you to build Hercules.

Corrupting MODULE files, DMSITP141T

Trying to track down a DMSITP141T problem.

I have a few C toyols (toy tools), mostly useless except for the challenge of
it.

One, cbrain (and esoteric programming language) is the focus today, but I can
reproduce a similar problem with this smaller C program.

This is using GCCLIB and GCCCMS from VMCE V1R1M0.

Something triggers badness, that can cause permanent problems with the MODULE.

First the smaller program and sample run. The problems depends on which CMS
routine is called.

/* Call CMS */

#include <stdio.h>
/* #include <cmssys.h> */

int main(int argc, char *argv[]) {
    int rc;

    rc = __cmscmd("LISTFILE PROFILE EXEC *", 1 /*CMS_COMMAND*/);
    fprintf(stderr, "Got: %d\n", rc);
    if (argc > 1) {
        fprintf(stderr, "Trying: '%s'\n", argv[1]);
        rc = __cmscmd(argv[1], 11 /*CMS_CONSOLE*/);
        fprintf(stderr, "Got: %d\n", rc);
    }
    return rc;
}

This is a simple program, only takes a single argument, for demonstration.

gcc callcms (cms
Ready; T=0.49/0.77 16:19:55
load callcms
Ready; T=0.02/0.05 16:20:01
genmod callcms
Ready; T=0.01/0.01 16:20:05
q txtlib
TXTLIB   = GCCLIB   CMSLIB   PLILIB   FORTLIB  TSOLIB
Ready; T=0.01/0.01 16:20:12

And a run. The first call to CMS is LISTFILE PROFILE EXEC, works fine,
multiple times in a row. But other commands are triggering DMSITP141T. I'll
use DIR (and remove some of the output).

callcms dir
PROFILE  EXEC     A1
Got: 0
Trying: 'dir'
Filename Filetype Fm  Format    Recs Blocks    Date     Time   Label
CALLCMS  C        A1  V    64     17      1  04/12/21   13:24  CMS191
CBRAIN   C        A1  V   138    241     13  04/14/21    3:48  CMS191
...
TRIALS   TEXT     A1  F    80      9      1  04/10/21   12:08  CMS191
FIRST    WORK     A1  F    80      2      1  03/23/21    9:23  CMS191
44 files, 3,786 blocks: 3,028,800 bytes.
DMSITP141T OPERATION EXCEPTION OCCURRED AT 980002 IN ROUTINE CALLCMS.
CMS

So that's a minimal example. What's next is more in depth C, but actually
worse in outcome. A genmod module becomes corrupt and stays ccorrupt.

gcc cbrain (cms
Ready; T=13.16/16.68 16:25:56
load cbrain
Ready; T=0.02/0.08 16:25:57
genmod cbrain
Ready; T=0.01/0.02 16:26:01
cbrain pbhello
Hello cbrain niarbc olleH
q
Ready; T=0.01/0.02 16:26:11
cbrain pbhello
Hello cbrain niarbc olleH
q
Ready; T=0.01/0.02 16:26:21

Now, after some programs, in particular MECAFF routines, but there are others.

EE cbrain helpcmd

Immediately causes the CBRAIN MODULE to trip, every time. Across logins,
across shutdown and restart...

Ready; T=0.03/0.06 16:29:43
cbrain pbhello

DMSITP141T OPERATION EXCEPTION OCCURRED AT 020002 IN ROUTINE CBRAIN.
CMS

Need to reload and run another genmod to get back to a usuable MODULE.
Note: no recompile, just a load and genmod.

load cbrain
Ready; T=0.02/0.10 16:30:49
genmod cbrain
Ready; T=0.01/0.02 16:30:53
cbrain pbhello
Hello cbrain niarbc olleH

First, not sure what is causing the DMSITP141T, and worse I'm unclear how
running program can corrupt a different MODULE file on disk.

Minor fixups for CMSBATCH

• currently, minidisks 192 and 195 have labels BAT191 and BAT192, reformat the minidisks with labels BAT192 and BAT195;

  • add a file BATPROF EXEC on minidisk 192 containing (as is, with lower case and blank line):

    &CONTROL OFF NOMSG
    &BEGTYPE
    CMS Batch Facility

    &END
    &EXIT

    This will eliminate a harmless but annoying error message at the beginning of the CMSBATCH spooled console output, and replace it with a more natural title.

Provide command to display file lines in hex

Provide a command to create a file which will list lines from a specified file in both character and hexadecimal format.

The command author will supply:

1. Source code and build instructions.
2. HELP file

Note: Versions in a high level language are likely to be much faster than versions written in BREXX.

Unpack Directory has blanks in file name

This can be a pain.

Exit from EDIT or SUBSET results in MORE...

Incorrect records read or written when record number specified on EXECIO

When a record number is specified on an EXECIO DISKR or DISKW operation, the same record is read repeatedly. The specified record should be the record read or written first, then subsequent files records should be read or written.

H390-VM Wiki page needs updates

The main paragraph on the Wiki page should be moved to the "Home" page for H390-VM ...

Under "Available versions" -- this page seems very out-of-date. I see no mention of the new VM Community Edition.

Update help files as needed for language compilers that we include in VMCE

Some of the languuage processors ( like FORTRAN or PLC) are missing help files. Determine which help files are needed and include them.

NUCXDROP module is missing from

Someone who will remain nameless forgot to generate the NUCXDROP MODULE on Community Edition V1R1.0
You might not miss it. Since NUCXLOAD isn;t there, only self-loading Nucleus Extensions work in VM/370.
NUCXLOAD is going to need relocatable MODULE support to match VM/SP and later, although I am testing
a NUCXTEXT command that will load and relocate TEXT files and establish a Nucleus Extension from them.
In the meantime, use these steps to generate the NUCXDROP MODULE.

LOGON MAINT
VMSETUP CMS
LOAD DMSNXD ( CLEAR ORIGIN TRANS
GENMOD NUCXDROP MODULE A2
ACCESS 190 Z
COPY NUCXDROP MODULE A = = Z2 ( OLDDATE
RELEASE Z
DEFINE STOR 16M
IPL 190 CLEAR
SAVESYS CMS
ERASE NUCXDROP MODULE A2

MVS dasd 149 missing from vm370ce.conf

The Hercules configuration file vm370ce does not contain this comment:

#0149 3350 mvs/dasd/smp001.149

in the definitions for the TK4- system configuration under VM.

The configuraton file will be updated in the next release. In the meantime, add the
entry manually, when the MVS dasd definitions are uncommented.

Reword message issued when GCCLIB segment within virtual machine

The current message is:
Segment GCCLIB address must be higher that virual machine memory size.

1. Correct "virual"
2. The "must be" sounds like the GCCLIB code won't work. It works fine. The message wording should be an informational message that tells the user that GCCLIB will be loaded inside the user virtual machine, and not shared.

Running DOSVS in the Community Edition

DOS/VS VIRTUAL MACHINE INITIAL SET UP

---

1. Download the DASDs of George Shedlock's 5-pack:
   http://dosvs.31bits.net/DOSVS_5Pack_V1.0-full.zip
   Unzip the file and put the emulated DASDs in the "disks" folder of VM/370 CE

2. Update vm370ce.conf for those DASDs:

   09A0 3350 disks/DOSR34.3350.CCKD
   09A1 3350 disks/PWRR34.3350.CCKD
   09A2 3350 disks/WORK01.3350.CCKD
   09A3 3350 disks/VSAM01.3350.CCKD
   09A4 3350 disks/OPTLB1.3350.cckd

   (use the indicated addresses and the lower case for OPTLIB1).

3. IPL VM/370 CE normally;

4. Logon to MAINT and edit USER DIRECT A to change the DOSVS directory entry:

   a) remove the VIRT=REAL option
   b) replace IPL 190 by IPL CMS
   c) add the line:

   LINK MAINT 19D 19D RR

   Save the file, and update the directory:
   direct user

   Then, logoff of MAINT;

5. Logon to DOSVS and create two files:
   a) NOTHING JCL A, containing

   // JOB NOTHING
   /&

   (This nothing job will be run at IPL and will ready the card reader of DOS/VS)

   b) DOSIPL EXEC A, containing
   CP SPOOL PUNCH *
   PUNCH NOTHING JCL A ( NOH
   CP SPOOL PUNCH OFF
   IPL 360

   (The exec will put the nothing in the virtual card reader before the IPL)

The virtual machine is now ready for the IPL of DOS/VS.

IPL OF DOS/VS R34

---

1. Logon to DOSVS and, at the Ready prompt, run the DOSIPL EXEC. Type
   dosipl
   followed by ENTER once. Don't do anything on this (logon) console anymore.
   Be sure that it is in RUNNING state.

2. Open a new 3270 connection, press the CLEAR key and dial DOSVS at the address 01F:
   dial dosvs 01f (followed by ENTER)
   You should get the message:
   DIAL DOSVS 01F
   DIALED TO DOSVS 01F
   Press ENTER an other time. You should get the message:

   0I04I IPLDEV=X'360',VOLSER=DOSR34,CPUID=...
   0I03A SPECIFY SUPERVISOR NAME

   This 3270 is now the operating console of DOS/VS.

   To answer message 0I03A, type:

   $$a$sup1 (and press ENTER twice). When you get the message:

   0I10A GIVE IPL CONTROL COMMANDS
   then type the sequence of commands below (in lower case), each one followed by ENTER :
   set

   0I71I READ DEVICE TYPE FOR SYSLOG INSERTED IN SYSLOG PUB
   dpd

   BG 1T00A WARM START COPY OF SVA FOUND
   keep

   BG 1I00A READY FOR COMMUNICATIONS
   stop
   batch f1

   0D07D ENTER RESPONSE
   F1
   assgn sysin,sysres
   F1 1T20I SYSIN HAS BEEN ASSIGNED TO X'360
   press the ENTER key
   (many messages displayed)

   0D07D ENTER RESPONSE
   BG
   assgn sysin,reader

   0D07D ENTER RESPONSE
   F2
   assgn sysin,reader
   0D07D ENTER RESPONSE
   F4
   assgn sysin,reader
   0D07D ENTER RESPONSE
   F3
   assgn sysin,reader

   0D07D ENTER RESPONSE
   F2

   assgn sysin,reader

   BG 1T20I SYSIN HAS BEEN ASSIGNED TO X'00C'
   0D07D ENTER RESPONSE
   BG

   Press ENTER and do the same for F2, F4 and F3

   Once you have the messages:

   F1 1Q34I BG WAITING FOR WORK
   F1 1Q34I F2 WAITING FOR WORK
   F1 1Q34I F4 WAITING FOR WORK
   F1 1Q34I F3 WAITING FOR WORK

   and the messages regarding the NOTHING job, enter the command:

   r rdr,*xx
   l lst,all

The IPL of DOS/VS is complete and the system is ready for work.

SHUTDOW OF DOS/VS R34

---

7. To shutdown the system, type the commands, at the DOS/VS console:
   pend

   0D07D ENTER RESPONSE
   F1

   /&

   0D07D ENTER RESPONSE
   F2

   unbatch

   0D07D ENTER RESPONSE
   F4

   unbatch

   0D07D ENTER RESPONSE
   F3

   unbatch

   0D07D ENTER RESPONSE
   BG

   rod

   0D07D ENTER RESPONSE
   F1

   unbatch

   0D07D ENTER RESPONSE
   BG

   stop

Then, at the DOSV/VS login console, type:

#CP logoff

This will drop the dialed console and logoff the DOS/VS virtual machine.

Duplicate Assmelber on S-Disk Should Be Removed

It seems that ASMAHL and ASSEMBLE modules on the S-Disk are identical.

q time
TIME IS 01:16:24 GMT SUNDAY 11/21/21
CONNECT= 25:14:01 VIRTCPU= 000:00.51 TOTCPU= 000:01.43
Ready; T=0.01/0.01 01:16:24
xcompare asmahl module s assemble module s
 
COMPARISON COMPLETED - RETURN CODE IS     0.
Ready; T=0.01/0.01 01:16:28

If that is the case ASMAHL should be removed as the name conflicts with an IBM licensed product, and we don't need to get in hot water with them.

https://www.ibm.com/docs/en/zos/2.1.0?topic=cms-invoking-assembler

l assemble * * ( date
Filename Filetype Fm  Format    Recs Blocks     Date    Time
ASSEMBLE MODULE   S2  V  8192      3     11  07/22/05   12:50
ASSEMBLE HELPCMD  U2  V    79    206     14  06/09/09   18:12
ASSEMBLE HELPCMD2 U2  V    79     63      5  06/09/09   18:12
Ready; T=0.01/0.01 01:13:13
l ASMAHL * * ( date
Filename Filetype Fm  Format    Recs Blocks     Date    Time
ASMAHL   MODULE   S2  V  8192      3     11  07/22/05   12:50
Ready; T=0.01/0.01 01:13:22
l ifox00 * * ( date
Filename Filetype Fm  Format    Recs Blocks     Date    Time
IFOX00   MODULE   S2  V  2904      3      4  07/22/05   12:59
Ready; T=0.01/0.01 01:13:38

Hercules control file should use ARCHLVL statement

The Hercules control file statement 'ARCHMODE' is deprecated.
Future versions should use ARCHLVL instead. ARCHMODE is currently not accepted by HERCGUI.

Help has wrong version

HELP for CPCMDS and CMSCMDS both display 'VM/370 Release 6 "Sixpack" '.

EXECIO does not accept STRING parameter with no operand

'EXECIO 1 DISKW HEXCHAR LISTING A1 0 V (string '

This line is accepted on VM/SP and later but not in the Community Edition of EXECIO,
We need to determine the results produced when this syntax is used, and update the
implementation to match the IBM version.

"SET CMSTYPE HT" and "SET CMSTYPE RT"

I would like to request that the "SET CMSTYPE HT" and "SET CMSTYPE RT" commands be available for Brexx execution in future releases of VM/370 CE

Many thanks!
Larry

Add DMSHRC CNTRL and CMSHRC MACLIB to the CMS 190 disk

This library and control file should be on the system disk to allow compilation of programs from IDs other than MAINT. This makes the most up to date versions of system macro and contrl blocks to be available to any user. If the VM system manager creates modifications to system control blocks, then they should add DMSLCL CNTRL and DMSLCL MACLIB to the S disk.

Components like the GCC runtime and the BREXX interpreter need system information but are not constructed on the MAINT ID.

We will correct this in the next Community Edition release.

Linux script may kill X3270 sessions it did not start

he script "vm370ce.sh" fires two x3270 instances and, at the end, there is pipe sequence to kill all the x3270 instances, even they are not related to the execution of the system. There is a command line parameter (-once) that does just that:

-once Causes x3270 to exit after a host disconnects. This option has
effect only if a hostname is specified on the command line.

The loopback address works as a hostname. I tested the change and it worked well.

TAPEMAP HELP not found on MAINT 19D

There is in V1R1M1, no help for the 1993 version of TAPEMAP on MAINT 19D .

TAPEMAP 191 has a TAPEMAP HELPCMS file, with filemode 1, and in a crunch that could be copied to MAINT 19D with filemode 2, but ... there are , I think, script commands that should be processed before that?

.CS 1 ON
TapeMap describes the contents of a tape.

Note: TapeMap requires that a tape drive be attached to your userid.  If tape
drives are not available to CMS users at your installation the TAPEMAP command
cannot be used under CMS.
.CS 1 OFF
.CS 2 ON

Misc HELP files need updating

HELP CMSCMDS:

does not list some new commands (DISKMAP, EXPLOIT, IDENTIFY)

FSHELP:

does not list some new commands (DISKMAP, EXPLOIT, IDENTIFY, MATCH)

HELP DISKMAP (MORE:

A line is longer than 80 characters which messes up display on some terminals.

HELP GCCLIB:

States version as 0.7.1, dated 21 Feb 2020. Does not appear to cover the
version of GCCLIB installed on VM/CE.

Refers to the now defunct H390-VM Yahoo group.

HELP IDENTIFY:

Typographical error - timezoe.

HELP IDENTIFY (MORE:

A line is longer than 80 characters which messes up display on some terminals.

HELP NUCXDROP:

States that NUCXDROPping a non-existant extension causes an abend 0001
which is not true for the updated version of DMSNXD provided with VM/CE.

HELP REXX:

Seems to refer to a different version of BREXX than the one installed in VM/CE.
It says version 2.1.9 dated 22 Feb 2020 while DMSREX VERSION says:
BREXX Version 0.9.13

HELP REXX (MORE:

Refers to the now defunct H390-VM Yahoo group.

GCCLIB MEMO U:

Refers to the now defunct H390-VM Yahoo group and is missing the example.
May contain other inaccuracies.

Next VM/370 Sixpack Release

Add your thoughts about this below. Note attachments work

REXXTEST EXEC has ADDRESS SYSTEM instead of ADDRESS COMMAND

REXXTEST EXEC has ADDRESS SYSTEM instead of ADDRESS COMMAND. This was changed in bREXX to correspond to VM/CMS usage. This makes the "CP QUERY TIME" call fail.

Add Mike Ward's DISASM port to VMCE

This command disassembles binary programs back to source. Mike is modernizing it and extracting the source code for distribution on the Community Edition.

DISCARD CMS command with no operands gives specification exception

Using the DISCARD CP command prefix on it's own results in a PROG CHECK.
Ready; T=0.01/0.02 00:21:05
DISCARD
DMSITP143T SPECIFICATION EXCEPTION OCCURRED AT 0178D6 IN SYSTEM ROUTINE
, RE-IPL CMS.
CP ENTERED; DISABLED WAIT PSW '00020000 4001B636'

OSBASIC and FORTRAN 191 disks misnamed

OSBASIC's 191 disk as been labeled "TST" for as long as I can remember there being a sixpack around. It seems to build and work properly, so there's no need (I think) for it to remain labeled as a test volume, that user should own the minidisk as OSB191 for more traditional naming.

FORTRAN's 191 disk is also named TST as well.

I don't know how to make this like a "walk your dog first" priority, it's not a big deal, but still worth the quick change maybe?

MAINT 092 minidisk is unused

That midisk is a leftover from the merge of the Community Edition changes onto the Sixpack 1.3 level system.
We will remove it in the next deliverable.

Alternate Nucleus Space

Seeing how HRC075DK adds "alternate nucleus support", it would be great if some free space is available on some disk to make use of this feature. Maybe even two such spaces, if possible.
As I understand it, there can be only one nucleus per DASD so that limits the options.

As for documentation, I think the following is sufficient.

In the MAINT MEMO, which already discusses how to build a nucleus, a paragraph can be added. It should probably tell you to change DMKSYS ASSEMBLE in the proper way (since I assume one would first create a nucleus for the alternate space, test if for a while, and then regenerate it for the normal nucleus space). In particular which space(s) are available, or where to find this information.

As far as I understand it, such a change plus the normal nucleus building plus installing steps would do the trick. I'm currently trying to check in DMKSAV if that also sets up the target disk so you can IPL from it. My remaining knowledge of 370 assembler is really really rusty though :) If it doesn't do this, one would need instructions how to do this oneself.

Thanks for making VM/370 so nice for us poor users who think they know something :)

Bogus error messages from SCAN utility

The SCAN utility issues bogus error messages when no files exist
matching the file specification provided, when no disk is accessed as
A and in other unusual but otherwise benign circumstances.

potentially disasterous typo in RSCS MEMO on MAINT 5E5

"vmfload cpload dmtlcl" in RSCS MEMO B should say "vmfload dmtload dmtlcl"

Add UTS support in the same skeleton manner as TK4- and DOSVS

Opening this one for comments, but if there's interest, I'll do it. I pretty much have it done already.

I'd like to add skeleton support for Amdahl UTS in the same way we have for TK4- and DOSVS in the current release - unzip the distribution into the VMCE home dir, and the config and DIRECT will have proper pointers to "just work(tm)" if the DASD is there.

I have this set up on my system now, including a couple of lines of cuteness in AUTOLOG1 that will CP ATTACH the necessary UTS volumes and autostart UTS if the volumes exist, but will ignore all of it if the UTS DASD isn't attached.

If this is anything anyone other than me would want, I can post the diffs here for consideration.

Update HELP WELCOME and HELP WELCOME ( MORE

The output from these help commands is the same as in the Sixpack 1.3 version and was never updated for VM Community Edition. More up to date versions must be developed.

Additional information in MAINT MEMO

MAINT MEMO tells you how to re-build the CP and CMS nucleus... if you already know how to use the update system. Some reference to more information about how that works would be appreciated. Maybe it is also possible to add some skeleton files to start with, where you just need to add some lines, with helpful comments guiding you.

I wanted to practice the nucleus building procedure, without any local changes, and already step 2 failed (vmfmac dmklcl dmklcl) because *** DMKLCL EXEC NOT FOUND ***. I have no idea what to substitute to just build the system as-is. Because I found a DMKHRC EXEC I tried vmfmac dmhrcl dmkhrc, and it did something seemingly without errors, but who knows, maybe I just destroyed my system.

I sure hope I don't have to repeat step 3 by hand for every source file!

Operation exception when FORMAT used and drive letter in use

Attempting to CMS FORMAT a disk using an already in use drive letter
results in an operation exception.