VSI OpenVMS Forum

I reached out to Tim Sneddon, but haven't heard back from him yet, so I forged ahead. I have released MMK V5.1-1 that will run on X86_64, in addition to VAX, Alpha, and I64.

The X86_64 version was compiled using the native C compiler under OpenVMS V9.2-1:

VSI C X7.4-785 (GEM 50X65) on OpenVMS x86_64 V9.2-1

I made modifications to a number of the files in the MMK github repository. Those changes have not been fed back to github yet, as I want to coordinate that with Tim.

You can download MMK V5.1-1 from the Process Software freeware archive:

MMK V5.1-1 @ Process Software Freeware Archive

I supply both VMSINSTAL and PCSI kits. The current sources are included in the .F saveset, if you want my modified sources.

These kits will install and run on VAX V6.1 or higher, Alpha V6.2 or higher, I64 V8.2 or higher, and X86_64 V9.2-1.

I've made a few of the freeware packages available for X86_64, so far. I hope to add more in the coming months.

Search the FILESERV for packages that run on x86_64

This is really nice to see available as an installable kit. I was happy enough with managing to build it myself, but this makes things a lot cleaner.

EDIT: Spoke too soon. Upon installing on x86_64 V9.2-1 and logging out and back in I get this.
%DCL-W-ACTIMAGE, error activating image MMK
-CLI-E-IMAGEFNF, image file not found HELDEN$DKA0:[SYS0.SYSCOMMON.][SYSEXE]MMK.EXE;

EDIT: Spoke too soon. Upon installing on x86_64 V9.2-1 and logging out and back in I get this.
%DCL-W-ACTIMAGE, error activating image MMK
-CLI-E-IMAGEFNF, image file not found HELDEN$DKA0:[SYS0.SYSCOMMON.][SYSEXE]MMK.EXE;

That's what it looks like when you didn't execute SYS$STARTUP:MMK_STARTUP.COM.

HTH,
Martin

P.S.: Thanks Hunter!

Thanks, pocketprobe and Martin!

Martin is correct, of course. You'll get that error if you don't run @sys$startup:mmk_startup.com.

I heard from Tim overnight. He has my changes now, and I expect they'll get added to the GitHub repository before too long.

Hunter

Oh cool. It does work perfectly after running SYS$STARTUP:MMK_STARTUP.COM.
Sorry about that, I still have much to learn about VMS.

Thanks again.

When I ported V5.1-1 to X86_64, I overlooked some builtin symbols that I didn't know existed (MMSVAX, MMSALPHA, etc). That resulted in MMSIA64 being defined on X86_64, and no MMSX86_64 symbol.

I've fixed that problem. I also fixed a problem that prevented MMK on VAX from issuing commands longer than 255 characters.

I have released MMK V5.1-3 for VAX, Alpha, I64, and X86_64. The .ZIP file includes both VMSINSTAL and PCSI kits.

https://vms.process.com/scripts/fileser ... rv.com?MMK

Hello goathunter,
I have downloaded the xip file, thank you! Now - sorry for ignorance - I would like to install MMK and I am confused not knowing how to do it.
Best,
Mike

I just use:

$ unzip mmk
$ @compile

to build and:

$ mmk :== $disk:[dir]mmk.exe

to define command.

sms wrote: ↑

Wed Nov 01, 2023 10:22 pm

Code: Select all

> I just use:
> [...]

   Starting with what, exactly?


   If I were starting with the "mmk.zip" which is currently available at
the link provided above, then I'd unpack the zip archive, and use either
the PCSI scheme ("PRODUCT INSTALL MMK") or the VMSINSTALL scheme
("@ SYS$UPDATE:VMSINSTAL.COM" (and answer the questions)).

   As it says in mmk051.release_notes:

[...]
   4.12   Packaging

          The MMK software package is now shipped in binary form
          (as well as source) in both VMSINSTAL and POLYCENTER
          Sotware Installation (PCSI) kits.
[...]

Ooops.

That is how I do with the old MMK kit I have and use.

I had not noticed that it had changed.

My mistake. Sorry.

Added in 6 minutes 2 seconds:
@Hunter

Any chance that we could get an "old style" ZIP as well?

The global instal with VMSINSTAL and PROD INSTAL are fine for VSI products, server products and other stuff that either by nature are required to be global or has a high likelihood of being wanted to be global.

But a lot of utilities and tools do not fall in that category. And I really think it is nice not to spam VMSINSTAL and PROD INSTAL with them, allow unpriviliged users to install them in a subdir of their account or install multiple versions in different directories etc..

MMK fall in the latter category.