Skip to content

CC/370 v1.6.3

Latest

Choose a tag to compare

@github-actions github-actions released this 14 Oct 18:22
· 6 commits to main since this release
802dde1

CC/370 (cc370) 1.6.3 is a patch release of the host-native MVS 3.8j toolchain. It fixes how as370 assembles and dasm370 disassembles MVCK, MVCP and MVCS. The compiler, the linker and the other tools are unchanged from 1.6.2 apart from the version they report. It is a drop-in for 1.6.2; the requirements are unchanged (LIBC/370 >= 2.3.0, maclib370 >= 1.0.0).

Read this first: what a caller can see

  • Who needs it: anyone who writes MVCK, MVCP or MVCS in assembler source, typically cross-memory or key-switching code in an SVC. These three carry two registers in their second byte, R1 (the true length) and R3 (the key), written D1(R1,B1),D2(B2),R3. as370 1.6.2 and earlier treated R1 as a length, stored it minus one across the whole byte and ignored R3. The machine then read the length and the key from the wrong registers -- in MVCK 16(4,10),32(11),7 the byte became 03, length from register 0 instead of 4 and key from register 3 instead of 7 -- and the assembly still ended with rc 0.
  • What 1.6.3 does: R1 and R3 are assembled as the Principles of Operation define them. The IBM assembler of MVS 3.8j (Assembler XF) does not know these three instructions, so there is no IBM object to compare against; the encoding follows the architecture.
  • New errors: a missing R3 now stops with severity 12; an R1 or R3 outside 0-15, or an omitted R1, with severity 8. Before, they assembled silently.
  • Reassemble any module that uses these instructions. Code that wrote them as DC X'D9..' to work around the defect can now use the mnemonics.
  • dasm370 shows the two registers as well: D943 2000 5000 now reads MVCK 0(4,2),0(5),3 instead of MVCK 0(68,2),0(5). A disassembly reassembles to the same bytes in both versions.
  • TPROT was never affected.

Fixed: before and now

source 1.6.2 1.6.3
MVCK 0(4,2),0(5),3 D903 2000 5000, rc 0 D943 2000 5000
MVCK 16(4,10),32(11),7 D903 A010 B020, rc 0 D947 A010 B020
MVCP 0(4,2),0(5),3 DA03 2000 5000, rc 0 DA43 2000 5000
MVCS 0(4,2),0(5),3 DB03 2000 5000, rc 0 DB43 2000 5000
MVCK 0(4,2),0(5) (no R3) D903 2000 5000, rc 0 severity 12

Install

curl -fsSL https://github.com/mvslovers/cc370/releases/latest/download/install.sh | sh

With Homebrew (macOS, Linux):

brew trust mvslovers/tap            # once
brew install mvslovers/tap/cc370    # cc370 and, as its dependencies, libc370 and maclib370
brew upgrade mvslovers/tap/cc370    # an existing install

Or the pieces, all listed in SHA256SUMS:

file what
cc370-1.6.3-{darwin,linux}-{amd64,arm64}.tar.gz the toolchain for one host
cc370_1.6.3_{amd64,arm64}.deb Debian/Ubuntu; depends on libc370-dev (>= 2.3.0) and maclib370 (>= 1.0.0)
cc370-1.6.3.{x86_64,aarch64}.rpm Fedora/RHEL; requires libc370-devel and maclib370 the same way
install.sh the installer above
ml01-0001-0.pdf, ml01-0002-0.pdf CC/370 User's Guide and Command Reference, Draft edition, for 1.6.3

Full changelog

Fixed

  • as370/dasm370: MVCK, MVCP and MVCS encode their two registers
    (#947). These three carry R1 and R3 in the second byte, written
    D1(R1,B1),D2(B2),R3. as370 took the R1 subscript for a length, wrote it
    minus one across the whole byte and never read R3: MVCK 0(4,2),0(5),3
    came out D903 2000 5000 where the machine needs D943 2000 5000, at
    rc 0. A missing R3 now fails at severity 12, and an R1 or R3 outside 0-15
    at severity 8. dasm370 decoded the same byte as a length, so a disassembly
    now reads MVCK 0(4,2),0(5),3 instead of MVCK 0(68,2),0(5); the bytes
    reassemble unchanged either way. Assembler XF does not know these three
    instructions, so their encoding follows the Principles of Operation.
    TPROT was not affected.