RE: At the risk of sounding like an AS/400 rah-rah...

Come on Joe: 

>hold, 
Uncheck the "Enabled" box on the scheduled task.

>release, 
Check the "Enabled" box on the scheduled task.

>modify 
Change anything on the properties page.

>immediately execute 
Right click and select "run"

And remember, this is the "basic" jobscheduler out of the box. I'm sure no
one on the list has ever paid for Robot or IBM's more advanced job scheduler
on their iSeries.

I will say, I do miss _very much_ the ability to hold a RUNNING job. I can
change the priority to a low level, but there have been times I wish I could
have outright held a running job.

-Walden

------------
Walden H Leverich III
President
Tech Software
(516) 627-3800 x11
(208) 692-3308 eFax
WaldenL@TechSoftInc.com
http://www.TechSoftInc.com 

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)
 

-----Original Message-----
From: Joe Pluta [mailto:joepluta@PlutaBrothers.com] 
Sent: Friday, January 17, 2003 3:41 PM
To: Midrange Systems Technical Discussion
Subject: RE: At the risk of sounding like an AS/400 rah-rah...


> From: bdietz@3x.com
>
> Actually winders NT and up (200 and XP) have a scheduler built in.

Cool!  I'm having a little trouble finding the options that allow you to
hold, release, modify or immediately execute the batch jobs, though.  Same
with the Unix stuff.  Probably because they don't exist.

Most of the schedulers for the PC-based OS's are pretty limited in their
capabilities, but that's simply a reflection of the evolution of the OS.
While OS/400 has been from its very inception all about handling business
applications, the PC OS's are primarily single user systems or multi-user
text processors.

Unix is closer to being able to handle business applications than Windows
because at least Unix was built for multi-user processing.  Windows was a
single-user multi-tasker, which "evolved" into a multi-user OS.

In both cases, though, scheduling is seen as more of a "system
administration" function than an operations function.  In fact, the concept
of a system operator is sort of foreign to most Unix/NT shops.  Rather than
having a subset of daily business operations that can be easily run by an
operator with minimal training, you instead have a bunch of technical
commands (cron, at, ...) that require somebody with some relatively in-depth
knowledge to use.

It's this philosophical divergence that really differentiates the IBM
midrange from the more technical OS's.  And if don't agree with that most
simple of comments, please send your responses to /dev/nul.

>smile<

Joe



_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.