On D3/Linux I just schedule nightly/weekend jobs in D3 via "cron" and
it works great - but I don't really have that option under D3/NT. So I
think I have to schedule repeating jobs via the BACKGROUNDS file
(yes?). Yet I'm finding the D3 background processor change/edit
interface damn near impenetrable...gotta be the worst interface
design since [fill in your favorite horror story GUI here]

The following is a job in the BACKGROUNDS file item - just a simple
program - FREDS_DUMP - that I can run from TCL, and I want to run
automatically in the XB account every night at around 4AM. But it
doesn't seem to be kicking off. What's the trouble and how might I fix
it??

thanks
Pick Guy

001 DM
002 2
003 n
004 FREDS_DUMP
005 R
006 15486
007 14520
008 1
009
010 N]y]y]y]y]y]N
011
012
013 13995
014 60726
015
016
017
018
019
020 492
021
022
023 131
024 I
025 XB
026 T

On May 25, 10:16*pm, Pickteam <pickteamsoftw... (AT) gmail (DOT) com> wrote:

Which version?

It's a simple question and answer interface. Not pretty, but not
difficult to manage, IMO. At least that's how it is on 7.5.3.

Did you answer (Y)es when asked "Ok to start this background job (Y/
N)?" at the end of the create/edit process?

Do you see a phantom running as user dm, account dm that represents
the background scheduler?

Does the command "background ?" list your job with a status of
"Enabled"?

--
Kevin Powick

The Backgrounds components were written in the 80's and then (as the
code says) hacked into AP in the 90's. I have to laugh because the Z
command (ZS, etc) is simple enough but I'm sure someone asked for a
front-end to it and apparently this was the response. I think I've
mentioned a few times here that it's probably best to leave silly
stuff like this to the open market than the DBMS vendors. Someone
with a free weekend could probably do a lot better and with a pretty
GUI too.

If you like operating at TCL but don't like the 'background' program,
the source is in dm,bp. There's nothing hidden, and the door has
always been open for people to hack on that code - as long as you
don't expect PS/RD/TL to support it, and as long as you don't publish
the code or variants.

If you need to schedule activities in D3 then just do what you're
doing with cron in *nix and use the Windows Task Scheduler (or any of
a thousand freeware tools) to fire off d3tcl commands.

Now might also be a good time to mention the G option on the Compile
verb, which creates object code that can be run right from Windows.
"What?" you say? That's just like jBase! Surprise surprise...

Finally, I have freeware on my website called mvExec which allows you
to run a command on any MV system from anywhere in your network - even
over the internet. So you can schedule a job on your local PC with
whatever tool you wish, and it will run on your server (*nix or
Windows) in U2, QM, Reality, mvBase, D3, jBase, etc. Note that the
output can be pulled back to the localhost too, so for example you can
setup a process on a client PC to poll the server and pull back
current sales data into a local CSV every hour. You do need a
non-dedicated license for mv.NET to use this (it won't interrupt your
other activities). If you already have mv.NET somewhere, then accept
the free gift with my regards. If not, please contact me.

HTH
Tony Gravagno
Nebula Research and Development
TG@ remove.pleaseNebula-RnD.com
Nebula R&D sells mv.NET and other Pick/MultiValue products
worldwide, and provides related development services
remove.pleaseNebula-RnD.com/blog
remove.pleaseNebula-RnD.com/freeware
Visit PickWiki.com! Contribute!
http://Twitter.com/TonyGravagno

It has been a while since I looked into the control records for the
background processes.

Check line 24, I believe that is an eye. If I remember things right
that means the item is being acted upon and is in 'Interactive' mode.
At least in linux, this would mean that the background phantom
processor started working with the control record but could not
complete the job, of the phantom crashed. Change this to a 'Q' to
allow the phantom to continue processing the record.

hth

Dale


On May 25, 7:16*pm, Pickteam <pickteamsoftw... (AT) gmail (DOT) com> wrote:

My "love" of backgrounds is such that I simply find it easier to write
a proc or macro that sleeps until a set time (4am in your case), does
it's work, and then fires itself off again with a Z command

Added bonuses include the fact that you can "see" runtimes with a
simple LIST-JOBS command ... and the same command can also give you
visual conformation that process is still "alive"

Low tech I know, but terribly effective and very easy to understand

On May 26, 7:58*am, Ross Ferris <ro... (AT) stamina (DOT) com.au> wrote:
Backgrounds are often given too much importance...

No man is an Iland, intire of it selfe; every man is a peece of the
Continent,
a part of the maine; if a Clod bee washed away by the Sea, Europe is
the
lesse, as well as if a Promontorie were, as well as if a Mannor of
thy friends
or of thine owne were; any mans death diminishes me, because I am
involved in
Mankinde; And therefore never send to know for whom the bell tolls;
It tolls
for thee.

On May 28, 2:15*am, Mike Preece <mich... (AT) preece (DOT) net> wrote:
Job donne - in the background

Z

On May 27, 9:28*pm, Mike Preece <mich... (AT) preece (DOT) net> wrote:

Gone the way of the Fishman, Mike?

--
Kevin Powick

On May 28, 3:10*am, Kevin Powick <kpow... (AT) gmail (DOT) com> wrote:
Well - I don't work. Is that right?

On May 28, 3:15*am, Mike Preece <mich... (AT) preece (DOT) net> wrote:
Grater minds thin I