After poking at Mercurial on and off for a while, I've gotten a repo
working to my satisfaction.  Here's my notes in case it can benefit
someone.

Mercurial tips for VMS (8.3)

Got Python by downloading two lda disk images: http://www.vmspython.org/
Put them on ods-5 volume like this node1::dsa300:[uuser]

In my login.com

$! mercurial (and python things)
$ define/trans=conc lda1 dsa300:[uuser.lda1.]
$ define/trans=conc lda2 dsa300:[uuser.lda2.]
$ @lda1:[000000]lib_logicals
$ @lda2:[000000]python_logicals
$ @python_vms:setup
$ @mercurial_root:[vms]setup
$ define/trans=conc etc DSA300:[UUSER.LDA2.Mercurial.etc.]
$ define tmpdir "/dsa300/uuser/tmp"
$ set proc/parse=extend
$ define op_repo DSA300:[UUSER.OP_REPO]
$ cstmlf :== convert/fdl=op_tools:stmlf.fdl

Setup repository as follows (upper and lower case can matter, I
wanted
all directory and file names to be upper case)

$ CREATE/DIR OP_REPO
$ SET DIRECTORY/VERSION=1 [.OP_REPO]
$ set def op_repo
$ hg init

Prepare a directory tree of files under [.PROD...] for intial load,
Then
set attributes with a script.

$ SET FILE/VERSION=1 [.PROD...]
$ DIR/OUTPUT=STMLF.COM/COL=1/NOHEAD/NOTRAIL [.PROD...]
Edit up stmlf.com with some clever learn sequences to make commands
like:
$ cstmlf DSA300:[UUSER.PROD.TOOLS]SUBMIT_ME.COM -
        DSA300:[UUSER.PROD.TOOLS]SUBMIT_ME.COM
$ @stmlf
$ BACKUP/LOG [.PROD...] [.OP_REPO...]   ! files into the empty repo
$! make all the directories in the repo have version limit of one
$ SET DEF OP_REPO
$ SET DIREC/VERSION=1 [.*]

Repo ready,  time for Mercurial commands

$ set def op_repo
$ hg stat ! show all files with ? meaning unknown status
$ hg add
$ hg commit -m "Initial load"
$ hg serve ! if you want web access

Notes:
STMLF attribute doesn't seem too much problem.  Just make sure a new
file
to be added is set that way.  Editing and creating a new version
preserves this, the files work fine as command files and data files.

Point your browser to http://NODE1.DOMAIN.COM:8000/

Mercurial info available at: http://mercurial.selenic.com/

Jojimbo wrote 2011-04-14 17:23:

Just a minor question...

> Got Python by downloading two lda disk images: http://www.vmspython.org/
> Put them on ods-5 volume like this node1::dsa300:[uuser]
>
> In my login.com
>
> $! mercurial (and python things)
> $ define/trans=conc lda1 dsa300:[uuser.lda1.]
> $ define/trans=conc lda2 dsa300:[uuser.lda2.]
> $ @lda1:[000000]lib_logicals
> $ @lda2:[000000]python_logicals

Now, the two pre-built kits are ready-to-use as-is.
The code above seems to say that you copied everything
from the disks to some other directory (?).

I have always simply done :

$ ld CONNECT util:[python]jfplib0004a.dsk lda1:
$ ld CONNECT util:[python]jfppy0020A.dsk lda2:
$ mount/system lda1: JFPLIB0004A
$ mount/system lda2: JFPPY0020A
$ @lda1:[000000]lib_startup
$ @lda2:[000000]python_startup

There is no need for any other ODS5 volume.

Now, maybe Mercurial needs this, but I didn't thought so.
I havn't used the Mercurial kit, but a lot of other
pre-installed stuff on the LD disks.

Is it performance reasons that makes you to copy the
LD-disks contents ?

Jan-Erik.



> $ @python_vms:setup
> $ @mercurial_root:[vms]setup
> $ define/trans=conc etc DSA300:[UUSER.LDA2.Mercurial.etc.]
> $ define tmpdir "/dsa300/uuser/tmp"
> $ set proc/parse=extend
> $ define op_repo DSA300:[UUSER.OP_REPO]
> $ cstmlf :== convert/fdl=op_tools:stmlf.fdl
>
> Setup repository as follows (upper and lower case can matter, I
> wanted
> all directory and file names to be upper case)
>
> $ CREATE/DIR OP_REPO
> $ SET DIRECTORY/VERSION=1 [.OP_REPO]
> $ set def op_repo
> $ hg init
>
> Prepare a directory tree of files under [.PROD...] for intial load,
> Then
> set attributes with a script.
>
> $ SET FILE/VERSION=1 [.PROD...]
> $ DIR/OUTPUT=STMLF.COM/COL=1/NOHEAD/NOTRAIL [.PROD...]
> Edit up stmlf.com with some clever learn sequences to make commands
> like:
> $ cstmlf DSA300:[UUSER.PROD.TOOLS]SUBMIT_ME.COM -
>          DSA300:[UUSER.PROD.TOOLS]SUBMIT_ME.COM
> $ @stmlf
> $ BACKUP/LOG [.PROD...] [.OP_REPO...]   ! files into the empty repo
> $! make all the directories in the repo have version limit of one
> $ SET DEF OP_REPO
> $ SET DIREC/VERSION=1 [.*]
>
> Repo ready,  time for Mercurial commands
>
> $ set def op_repo
> $ hg stat ! show all files with ? meaning unknown status
> $ hg add
> $ hg commit -m "Initial load"
> $ hg serve ! if you want web access
>
> Notes:
> STMLF attribute doesn't seem too much problem.  Just make sure a new
> file
> to be added is set that way.  Editing and creating a new version
> preserves this, the files work fine as command files and data files.
>
> Point your browser to http://NODE1.DOMAIN.COM:8000/
>
> Mercurial info available at: http://mercurial.selenic.com/

> Is it performance reasons that makes you to copy the
> LD-disks contents ?
>
> Jan-Erik.

More like office politics.   I didn't want to mount the LD devices
because then our local control freak manager type might have noticed.

Regards, Jim

Jojimbo wrote 2011-04-14 18:12:
>
>> Is it performance reasons that makes you to copy the
>> LD-disks contents ?
>>
>> Jan-Erik.
>
> More like office politics.   I didn't want to mount the LD devices
> because then our local control freak manager type might have noticed.
>
> Regards, Jim

So what if he noticed ? Are you not allowed to run Python ?

Anyway, it seems as you do know that Python can be runed
directly from the LD disks... :-)

Jan-Erik.

On Apr 14, 9:32=A0am, Jan-Erik Soderholm <jan-erik.soderh...@telia.com>
wrote:
> Jojimbo wrote 2011-04-14 18:12:
>
>
>
> >> Is it performance reasons that makes you to copy the
> >> LD-disks contents ?
>
> >> Jan-Erik.
>
> > More like office politics. =A0 I didn't want to mount the LD devices
> > because then our local control freak manager type might have noticed.
>
> > Regards, Jim
>
> So what if he noticed ? Are you not allowed to run Python ?
>
> Anyway, it seems as you do know that Python can be runed
> directly from the LD disks... :-)
>
> Jan-Erik.

Well, to be exact, I was forbidden to use Perl but when I suggested
Python she didn't know what it is so I took that blank look as
permission if I didn't get caught.  I was also informed that we didn't
need any source code control because "things don't change much" but I
disagreed and set up Mercurial for my own use.

The LD images have certainly been very useful.

Regards, Jim