Re: OfficeVision job scheduler

Well, you could secure WRKJOBSCDE and then have an adopted program do a
WRKJOBSCDE SCDBY(&USER).
Or you could name the jobs by group, example WRKJOBSCDE JOB(G01*).  We have
a few hundred jobs in our scheduler and this works quite nice for us.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin



                    Jeff Crosby
                    <jlcrosby@dilgardfo       To:     midrange-l@midrange.com
                    ods.com>                  cc:
                    Sent by:                  Fax to:
                    midrange-l-admin@mi       Subject:     Re: OfficeVision job 
scheduler
                    drange.com


                    02/21/2002 07:24 AM
                    Please respond to
                    midrange-l






gcrane@johansonmfg.com wrote:

> If you are not doing any OV function like data merge, why not show them
> WRKJOBSCDE...need to break the ice somehow and this may be the golden
> opportunity.    Less resources used (I should think) if you just use
WRKJOBSCDE.
> I think OV scheduling was available on the S/36....I believe we used it
then and
> quickly migrated ot WRKJOBSCDE once we knew it existed.  Now it is only
used if
> we are doing a job that requires OV400 like the data merge to an OV
document.
> all else is from WRKJOBSCDE.

One reason _not_ to do this is security.  By using the Officevision
Calendar Scheduler (OCS), each user was restricted to his/her jobs.
With WRKJOBSCDE, everybody could see everyone else's jobs.  We actually
had to get the Advanced Job Scheduler from IBM to be able to duplicate
this ability in OCS.

--
-Jeff

The opinions expressed are my own and not necessarily
the opinion of my company.  Unless I say so.

_______________________________________________
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/cgi-bin/listinfo/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.