> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN