> On Dec 18, 2018, at 9:20 PM, Larry Baker wrote:
>
> My 2ยข from the Way Back Machine:
>
> I don't know what programmer's used before Fortran. But, all these OS/360
> features (and, likely earlier IBM OS's) were accessible from Fortran, the
> first commercially available high-level
On 18/12/18 13:56, Armistead, Jason wrote:
Maybe a brief discussion of this topic could be added to the SIMH FAQ. It
seems like a key piece of information to help others kick-start their attempts
to run VMS/OpenVMS under SIMH.
concur and agree.
Dott. Piergiorgio.
Paul Koning mailto:paulkon...@comcast.net>>
> To: Phil Budne mailto:p...@ultimate.com>>
> Cc: dave_list_a...@verizon.net <mailto:dave_list_a...@verizon.net>,
> cl...@ccc.com <mailto:cl...@ccc.com>, simh@trailing-edge.com
> <mailto:simh@trailing-edge.com&g
>
> Message: 3
> Date: Mon, 17 Dec 2018 23:52:05 -0500
> From: Brian mailto:b_li...@patandbrian.org>>
> To: SIMH@trailing-edge.com <mailto:SIMH@trailing-edge.com>
> Subject: Re: [Simh] Transferring the licence file to the VAX emulator
> - THE FIX
> Mes
, 17 December 2018 11:52 PM
To: SIMH@trailing-edge.com
Subject: [External] Re: [Simh] Transferring the licence file to the VAX
emulator - THE FIX
On 12/17/18 8:28 AM, Brian wrote:
OK, thanks to all who helped. As I found from a website to which I was
directed, and as Mark also said, the solution
On 12/17/18 8:28 AM, Brian wrote:
OK, thanks to all who helped. As I found from a website to which I was
directed, and as Mark also said, the solution was to copy the file off
the CD-ROM and then
SET FILE/ATTRIBUTE=(RFM=STM) VMSLICENCES.COM
Then run the commands again, and it all worked
On 2018-12-17 22:54, Paul Koning wrote:
On Dec 17, 2018, at 3:04 PM, Johnny Billquist wrote:
Actually, VMS don't natively have any record terminators for text files.
So lines terminated by CR, LF, CR+LF or whatever, are all wrong.
Huh? For VMS, "native" is any file format that RMS32
> On Dec 17, 2018, at 3:04 PM, Johnny Billquist wrote:
>
> Actually, VMS don't natively have any record terminators for text files.
> So lines terminated by CR, LF, CR+LF or whatever, are all wrong.
Huh? For VMS, "native" is any file format that RMS32 supports. In VMS V1,
that means either
On 2018-12-17 21:34, Phil Budne wrote:
I wasn't saying RMS was anything new to the world in general, but that
VMS was the first system to make it the preferred way to access disks.
DEC was not always thus.
I'm pretty sure my first exposure to RSX-11M was using F11ACP, I don't
think RSX was BORN
I wasn't saying RMS was anything new to the world in general, but that
VMS was the first system to make it the preferred way to access disks.
DEC was not always thus.
I'm pretty sure my first exposure to RSX-11M was using F11ACP, I don't
think RSX was BORN with RMS as the primary method of file
On Mon, 17 Dec 2018 20:16:19 -, Johnny Billquist
wrote:
And then I have my possibly very sneaky alternative: TECO. TECO usually
swallows and does the right thing for very many things, and if not, it's
very easy to correct, and then let TECO write the file out, and you'll
have a
yeah true, variable with fixed headers, you're right there I remember that
now, been a while :-)
On Mon, 17 Dec 2018 20:04:31 -, Johnny Billquist
wrote:
Actually, VMS don't natively have any record terminators for text files.
So lines terminated by CR, LF, CR+LF or whatever, are all
ahh good old ISAM, yeah I wrote something similar on a commodore pet
system that I was tasked with writing a hospital lab data analysis suite
for in the early 80s. It had the ability to random access the FDD's so it
made sense to tag and allocate blocks rather than have to rewrite
On 2018-12-17 18:40, Paul Koning wrote:
On Dec 17, 2018, at 12:29 PM, Clem Cole wrote:
The problem is the license manager code you are running into is expecting an
RMS file, not a Stream I/O. In the old days, the idea of 'access methods' was
the natural ways OS's did I/O and RMS was
I try one more time on list, but if you want to discuss more, let's go
off-list.
On Mon, Dec 17, 2018 at 2:56 PM Paul Koning wrote:
>
> Not unique to VMS nor even to DEC.
I agree - that is exactly what I was saying. It was the way I/O was done
in the 60s - which seems to have had a rebirth as
Actually, VMS don't natively have any record terminators for text files.
So lines terminated by CR, LF, CR+LF or whatever, are all wrong.
The natural format is variable length records with implied CRLF. Which
means that on the disk, the records are prefixed by a length, and no CR
or LF are
> On Dec 17, 2018, at 2:44 PM, Phil Budne wrote:
>
> Clem Cole wrote:
>> In the old days, the idea of 'access
>> methods' was the natural ways OS's did I/O and RMS was VMS's answer.
>
> Using RMS as the primary way to do file access was dain bramage unique
> (at DEC) to VMS, no?
Not
A couple other hints: Notepad++ or Notepadqq converts the feeds quite
easily and I have found that on some Linux distros that you have to widen
the Terminal Window or the license will truncate causing problems.
Ray
On Mon, Dec 17, 2018, 2:31 PM Mark Pizzolato DCL will handle the Stream file
Clem Cole wrote:
> In the old days, the idea of 'access
> methods' was the natural ways OS's did I/O and RMS was VMS's answer.
Using RMS as the primary way to do file access was dain bramage unique
(at DEC) to VMS, no? Maybe some fancier versions of RSX-11M double
plus good went that way
DCL will handle the Stream file just fine AS LONG AS the file attributes
explicitly identify the correct Stream record attributes. DIR/FULL will
display the current record format.
If the file was transferred in binary mode, it will likely end with "Fixed
length 512 byte records". Even if
From: Paul Koning
Sent: Monday, December 17, 2018 12:40
That's odd, I thought that (on VMS) you didn't have any choice about using
RMS.
Well, not unless doing raw block I/O.
That is how I recall it; it was RMS or else use ACP/XQIOP block I/O.
Stream is one of the formats supported by
the issue here tho is more that the license file is in fact a DCL script
and not input into LMF itself, and DCL doesn't handle the stream-LF files
it'll just barf on command line input too long...
On Mon, 17 Dec 2018 17:40:04 -, Paul Koning
wrote:
On Dec 17, 2018, at 12:29 PM,
> On Dec 17, 2018, at 12:29 PM, Clem Cole wrote:
>
> The problem is the license manager code you are running into is expecting an
> RMS file, not a Stream I/O. In the old days, the idea of 'access methods'
> was the natural ways OS's did I/O and RMS was VMS's answer. Since today's
>
The problem is the license manager code you are running into is expecting
an RMS file, not a Stream I/O. In the old days, the idea of 'access
methods' was the natural ways OS's did I/O and RMS was VMS's answer.
Since today's programmers tend to have grown up with C/C++/Java and stream
I/O, you
> I really don't want to have to enter all the licence data
> interactively, or fix a couple of thousand line endings in the editor!
> There must be SOME way of getting the file onto a new setup?
>
> Thanks for any assistance,
>
> Brian.
As others have indicated, you need to install the licenses
From: Brian
To: SIMH@trailing-edge.com
Subject: [Simh] Transferring the licence file to the VAX emulator
Maybe I've forgotten more about the VAX than I think. WHAT
does it expect to see as a line terminator?
Probably nothing. The 'natural' format would have been
RMS VAR-CR records (if I
FWIW,
I've been running simh for ages and periodically I forget to renew my hobbyist
licenses before they expire. It happened again just last week. I usually go
through the following song and dance routine in this scenario:
1. Get new hobbyist licenses in attached .COM file
2. Transfer from
Likely the issue is that the *nix system presents the text file as
stream-LF format which VMS won't understand as a standard text file which
it would expect to be CR-LF terminated records. VMS convert utility would
be able to fix that as already mentioned, tho you may need to tell it what
I'm pretty sure I used VMS CONVERT to fix the licence file.
Another easy way is to use FTP, if you have a server available.
This is vaguely how I did it:
Get an existing file that is a VMS text file:
$ ANAL/RMS/FDL/OUTPUT=XYZ textfile
This creates a file called XYZ.FDL that describes the
Make iso image with license paks and attached it to SIMH. It worked great for
me.
Tim
-Original Message-
From: Simh On Behalf Of Brian
Sent: Monday, December 17, 2018 9:02 AM
To: SIMH
Subject: Re: [Simh] Transferring the licence file to the VAX emulator
On 12/17/18 8:44 AM, Wilm
On 12/17/18 8:44 AM, Wilm Boerhout wrote:
> Brian schreef op 17-12-2018 om 14:28
>
> [snip]
>> I really don't want to have to enter all the licence data
>> interactively, or fix a couple of thousand line endings in the editor!
>> There must be SOME way of getting the file onto a new setup?
>>
>>
Brian schreef op 17-12-2018 om 14:28
[snip]
I really don't want to have to enter all the licence data
interactively, or fix a couple of thousand line endings in the editor!
There must be SOME way of getting the file onto a new setup?
Thanks for any assistance,
Brian.
What usually works for
Hi all,
Please bear with me for what I'm sure is a beginner question, but it
has me beat. :(
I've set up SIMH, built it all, got my kits for OpenVMS and have
installed the system. So far, so good.
The problem I'm having is in getting the licence file I received under
the Hobbyist scheme onto
33 matches
Mail list logo
