Anyone have Moved from VMS to WINDOWS?

[brian_matthewsbrian matthews]

in addition to the DOS at command there is also the enhanced XP schtasks 
command, aswell as the standard scheduler windows interface.

Another great approach to creating .cmd/.bat command fies, to run either 
interactively via minimised DOS windows or in batch, is to write them in 
quiz to a disc report file - this enables the user specific parameters to be 
picked up from a userID-Key parameter table/record. This is much easier than 
all that let/put quick designer proc stuff.  Very slack example below,

let t_comfile = "c:\comfiles\" + logonid + sysdate + systime + ".cmd"

if not setsystemval ("comfile",t_comfile)
then error "screen ..id... bad comfile sysval set "

let t_userid = logonid
let  t_cmdfile_setup = "cmd /c c:\cmd-do-qzn.cmd " + t_userid
run command = t_cmdfile_setup

c:\cmd-do-qzn.cmd  contains below,

set idkey=%%1                           ; can be up to %%8
quiz auto=c:\qzfiles\write-a-cmd.qzc

c:\qzfiles\write-a-cmd.qzc contains below,

cancel clear
set rep dev dis name $comfile
acc user-parafile
choose userID systemvalue "idkey"
final footing &
"set up env vars..." skip &
"quiz or atp calls..." skip &
"command-line-3" skip &
"command-line-n" skip &
...

let  t_cmdfile_run = "cmd /c " + t_comfile
run command = t_cmdfile_run

regards Bri,

>From: Jeff Hoffman <wonicon@optushome.com.au>
>To: powerh-l@lists.sowder.com
>Subject: Re: Anyone have Moved from VMS to WINDOWS?
>Date: Thu, 10 Mar 2005 09:25:29 +1100
>
>At 08:38 AM 09-03-05 -0500, Etienne wrote:
> >Hi,
> >
> >We have a application running on OpenVms with RMS files and some COBOL
> >programs also. We have a customer that would like to have this 
>application
> >running on a Windows server.  We never worked with Powerhouse on Windows 
>so
> >we do not know where the difficulties will be...
> >
> >Anyone ported a complete system from VMS to Windows?  If yes, where were 
>the
> >difficulties...
> >
> >Thanks!
>
>Hi
>
>We converted from VMS/RMS to WINDOWS/MSql Server, we had a lot of batch
>processing and generated shell scripts within quick screens.
>
>The DB was created using the output from qshow then tweeked online.
>
>The data was loaded by using qtp to create tab delimit files suitable for
>using with sql's bcp (was not documented but still exists) from a batch
>script run from a dos window.
>
>One problem was creating fixed length records from dos commands for use in
>PH, and also to create variable length records created from PH for the
>script files (this was needed as dos does not have a terminator for ending
>an environment varaible so when creating a script file from PH by default
>the env variable includes the trailing spaces). We wrote a C++ program to
>do these conversions (does not need the .net shit, and worked on all our
>PC's).
>
>Conversion was just a trudge but was faily simple. The problems came on
>testing where we found VMS allowed non unique updates and syntax could be
>lax, MS  Sql required unique keys and fully qualified syntax
>eg under VMS we could output xxx alias yyyy, under Windoz we has to unclude
>the access qualifiers on the output statement. BTW the runtime errors where
>not very helpfull, so if you get some strange ones, check the full syntax
>is used on output statements.
>
>Printing was a problem, but was solved but printing to a file then printing
>the file from dos, this was we could keep out PCL control commands. We
>created a printer manager (in PH) to handle deferred printing.
>
>We created out own batch processing system, but running online was
>preferrable and simpler to manage and at the time nobody was familiar the
>the 'at' command and users where not familiar with managing dos batch 
>queues.
>
>Every body has been happy with the result,
>BUTTTTTTT check how you wish to implement it, 2 basic otptions
>  - run on individual PC's in which case you have to licence each and every
>PC and re verify licencing if you change PC's
>  - run on a citrix or windows server in which case only the server has to
>be licenced still need the same number of liceneces but easier to manage.
>
>Anyway ours is working.
>
>LOL
>
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>+ Jeff Hoffman                          + e-mail: wonicon@optushome.com.au  
>+
>+ Director                              +                                   
>+
>+ WoniCon Pty Ltd   (ABN 93 083 502 630)+                          ,-_|\    
>+
>+ 21 Prices Circuit                     + voice: +61 2 9542 1527  /     \   
>+
>+ Woronora    NSW     2232              + fax:   +61 2 9576 7029  \_,-._*   
>+
>+ AUSTRALIA                             + mobile: 040 790 3929         v    
>+
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
>+
>= = = = = = = = = = = = = = = = = = = = = = = = = = = =
>Mailing list: powerh-l@lists.sowder.com
>Subscribe: "subscribe" in message body to powerh-l-request@lists.sowder.com
>Unsubscribe: "unsubscribe <password>" in message body to 
>powerh-l-request@lists.sowder.com
>http://lists.sowder.com/mailman/listinfo/powerh-l
>This list is closed, thus to post to the list you must be a subscriber.

_________________________________________________________________
Express yourself with cool new emoticons http://www.msn.co.uk/specials/myemo