CA-7 has a similar function to run "cross platform" work. It requires a "daemon" be running on the remote side. <WARNING type="plug">I like Co:Z Launcher from Dovetailed Technologies to do this. It only requires a standard SSH server on the remote end. And I can afford it (it is zero cost.) </WARNING>
-- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets® 9151 Boulevard 26 • N. Richland Hills • TX 76010 (817) 255-3225 phone • [email protected] • www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets® is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. –The Chesapeake Life Insurance Company®, Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Pommier, Rex R. > Sent: Monday, August 27, 2012 8:18 AM > To: [email protected] > Subject: Re: X86 server > > As far as "no batch" on non-mainframe platforms, I agree with you that > it is pretty much a matter of verbiage and available toolset. Having > worked with both AIX and HP-UX over the past 10 years, they don't have > the initiator concept. As coming out of the box, *NIX systems simply > throw work at the box until it is buried. Unless you specifically > "background" a task, when you run a script it ties up your terminal > session, whether it be for a transaction or a task that updates > millions of rows in a database. That is why many of the software > product vendors have their own schedulers built in. In addition, some > of the scheduler vendors run just fine in *NIX/Windows. BMC's Control- > M (I'm not endorsing it, just saying it has this capability) can run > schedules across the environment, with a job on the mainframe > triggering a job on another platform, then pass control back to a > mainframe job once the work is done on the other platform. > > Rex > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of McKown, John > Sent: Monday, August 27, 2012 8:03 AM > To: [email protected] > Subject: Re: X86 server > > The confusion about "no batch" may be because of a lack of something > akin to the "initiator" and SPOOL. Well, I guess the output part of the > "SPOOL" concept could be something like the files in /var/spool/lpq (in > my Linux) subdirectory. I'm not really UNIX literate about AIX, > Solaris, HP-UX, et al. On most Linux distros, there is definitely no > "initiator". There is "crontab" and "at" to schedule background tasks. > The only "job scheduling" software that I've ever heard of is "The > Portable Batch System" > http://en.wikipedia.org/wiki/Portable_Batch_System > I have no idea how this compares to something like CA-7 or Tivoli. Oh, > there is also "icron" to schedule background tasks based on creation, > update, or deletion of files. At least on Linux. I don't know if other > systems have the "inotify" interface. > > -- > John McKown > Systems Engineer IV > IT > > Administrative Services Group > > HealthMarkets® > > 9151 Boulevard 26 • N. Richland Hills • TX 76010 > (817) 255-3225 phone • > [email protected] • www.HealthMarkets.com > > Confidentiality Notice: This e-mail message may contain confidential or > proprietary information. If you are not the intended recipient, please > contact the sender by reply e-mail and destroy all copies of the > original message. HealthMarkets® is the brand name for products > underwritten and issued by the insurance subsidiaries of HealthMarkets, > Inc. –The Chesapeake Life Insurance Company®, Mid-West National Life > Insurance Company of TennesseeSM and The MEGA Life and Health Insurance > Company.SM > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] > > On Behalf Of Mark van der Eynden > > Sent: Sunday, August 26, 2012 11:46 PM > > To: [email protected] > > Subject: Re: X86 server > > > > > The elimination of batch which seems to be feasible on non- > mainframe > > > architectures alone is a killer. > > > > There is no elimination of batch, anywhere. > > > > It might go by another name, it might be 'hidden', but there's always > > batch. > > > > Remember to remind the auditors of that next time they come around > > asking batch scheduling questions. > > > > A lot of the 'other platform' people say 'there is no batch' because > > they know what a can of worms it is, or maybe they just do not equate > > 'scheduled tasks' as batch. > > > > One of the nearby SAP experts, with mainframe experience (this SAP is > > running on Unix), says SAP Batch is 'simply' a number of 'initiators' > > that run the next batch entry, there is no prioritization, no > classes, > > every thing just runs, causing all the imagined potential havoc. If > > the 'initiators' get 'clogged up' SAP will die within a few hours as > > batch is critical to its overall health. > > > > --------------------------------------------------------------------- > - > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to [email protected] with the message: INFO IBM-MAIN > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN > > The information contained in this e-mail may contain confidential > and/or privileged information and is intended for the sole use of the > intended recipient. If you are not the intended recipient, you are > hereby notified that any unauthorized use, disclosure, distribution or > copying of this communication is strictly prohibited and that you will > be held responsible for any such unauthorized activity, including > liability for any resulting damages. As appropriate, such incident(s) > may also be reported to law enforcement. If you received this e-mail in > error, please reply to sender and destroy or delete the message and any > attachments. Thank you. > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
