PowerHouse Migration from VMS 7.10g2 to Windows/SQL Server 8.41

[Jones, Chad E.]

To answer your question in number 4, you can use the setx command to set a system variable.  http://support.microsoft.com/?kbid=263105

Chad



From: "Joe Boyle" <atla38@dsl.pipex.com>
To: <mail@kevinerne.co.uk>, <powerh-l@lists.sowder.com>
Subject: RE: PowerHouse Migration from VMS 7.10g2 to Windows/SQL Server 8.41 
Date: Tue, 24 May 2005 13:28:44 +0100

I know quite a few who have this environment in place but I have no idea if
any of them access this list.

As for issues, and off the top of my head,
1. 
there is no POW so you have to work at the pdl source code level when making
dictionary changes
2. 
there are no mailboxes
3. 
I think that administrators have to queue batch jobs via the AT command (or
scheduler or schtasks); but there is nothing to stop you having access to
the ATed command files in order to add your own processing requirements
4.
as far as I know there are only two levels of environment variable - system
and user - and cater for both symbols and logicals; if anyone knows how to
write a DOS command to create a system level environment variable I would be
delighted to here about it - I recall that I could only ever create user
level ev's.
5.
presumably there are lots of OS system calls to simulate lexical functions,
but I assume there are manuals on Windows programming calls
6.
You will need to make lots of use of the autocommit syntax so look it up
early on :) unless you already on Sybase or rdb

Regards, Joe.


-----Original Message-----
From: powerh-l-admin@lists.sowder.com
[mailto:powerh-l-admin@lists.sowder.com] On Behalf Of Kevin Erne
Sent: 24 May 2005 12:19
To: powerh-l@lists.sowder.com
Subject: PowerHouse Migration from VMS 7.10g2 to Windows/SQL Server 8.41 

Has anyone attempted this ?
Any pitfalls or limitations ?