Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 22 MAY 2002 07:53:51AM Martyn Hodgson wrote:

I've inherited a system that uses ARev. I know quote a bit about the application and the data in it. I've created a number of reports in Easywriter that I use on an ad hoc basis. I've now got a requirement to run some of these at set times. I'd like to be able to write a dos command script that I can schedule, that simply:

starts my application

opens easywriter

specifies the target file

choses the required report from the libarary

runs and prints the report

closes the application

(ideally) returns a result code that I can trap

Can I do this?

Cheers

Martyn


At 22 MAY 2002 11:01AM Dave Harmacek wrote:

I suggest you create a system of programs and specification tables in ARev. This spec tables are so you can easily change what program and/or report is run. The programs actually run the reports.

Then, when this is running from the Command window you can make a USER who has a STARTUP command that starts this program for you. Then the command line in your DOS side is: e.g. AREV OTTO /X /M4096

where OTTO is this special user.

There is no way for Arev commands/programs to run directly from a DOS command line without some trick like this.

Dave


At 22 MAY 2002 05:36PM Matt Sorrell wrote:

Martyn,

We had a similar requirement, and we wrote a simple scheduler type program. We use a dedicated indexer, and we wrote a post-index process that is attached just to the indexer login. It checks a table for jobs, and determines if they should be run or not. These jobs have associated VOC table entries that are executed.

It works very well for us. If you are interested, I can probably email you the source code.

HTH,

msorrel@greyhound.com

Greyhound Lines, Inc.


At 22 MAY 2002 08:13PM Curt Putnam wrote:

Dave's approach is the easiest if the reports are few in number and the world doesn't end if the reports don't run.

The dedicated job server approach is better if the report volume strains a single station and/or there needs to be notification of the failure of critical jobs.


At 23 MAY 2002 10:43AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:

Martyn, we'd endorse Dave Harmacek's approach, but would also use a DOS command line parameter which was equivalenbt to the report @ID required. This would mean the minimum of code, and the ability to schedule processes from the operating system.

If you want to access the DOS command line from RBASIC, you can use the following AREV object to create $DOSCMDLINE, then add an AREV user whose voc-based login script calls a program which runs the report nominated on AREV.EXE's DOS command line.


A =\02000000000000000000EB4A90000000\
A := \00000000000000000000000000000000\
A := \00000000000000000000000000000000\
A := \00000000000000000000000000000000\
A := \00000000000000000000000000000000\
A := \000000240000B462CD212EC706580000\
A := \008EC3BF8100BE1100268A053C0D741C\
A := \3C0A74183C0074142E833E580064740C\
A := \2E8804462EFF06580047EBDD1E8CCA8E\
A := \DABE11002E8B0E5800B40FFC2EFF1E0A\
A := \0057F3A45F2E8B0E580033C033D2B410\
A := \2EFF1E0A001FCB\

OPEN 'BP' TO BP.FILE THEN
  WRITE A TO BP.FILE,'$DOSCMDLINE'
END

The Sprezzatura Group

[i]Celebrate CeBIT with Sprezz Local![/i]

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/dc405eea1019c2a188256bc100415ade.txt
  • Last modified: 2024/01/04 21:00
  • by 127.0.0.1