|
NonStop Batch Job Scheduler for Guardian & OSS
|
|
 MultiBatch is a powerful & maintainable batch processing environment designed to exploit the HP NonStop server architecture for the Guardian & OSS operating systems. All job status data can be relayed to a Windows server for graphical & tabular charts, management reports & Real-Time tracking.
|
|
- Overview
- Features
- Advantages
- Screens
- Comparison
- MI Reports
- O S S
- Demos
- Requires
- Latest
HP NonStop Batch Scheduler - Overview
MultiBatch is a powerful, maintainable Batch Processing environment specifically designed to exploit the HP NonStop server platform architecture both for the Guardian and Open System Services (OSS) operating systems. It allows parallel batch processing with calendar and conditional logic to occur in a single processor or multi-processors concurrently. Batch processing can be invoked locally or across an entire NSK network.
MultiBatch is a maintained, future-proofed product compatible with all HP NonStop system ranges (including the HP NonStop SuperCluster, Itanium and latest Integrity series). The NonStop scheduling software employs strict fault-tolerant techniques and multi-tiered job dependency structuring for the robust and efficient execution of batch schedules.
MultiBatch is used by some of the largest financial and central banking organisations in the HP NonStop user community. It is reliably used in contingency situations to provide an ordered and optimised strategy for site switching during Disaster Recovery and for more general NSK closedown and start-up maintenance procedures.
MultiBatch can also be used to provide an accelerated method for the activation of XPNET ATM and POS networks. For example, making use of concurrent start-up approaches, local or networked XPNET environments can be initiated in parallel by PATHWAY, Logical Node, Class or Station Priority in order to safeguard agreed SLAs.
The MultiBatch product comes equipped with an intuitive GUI interface (PATHWAY screens version also available) for batch schedule configuration and status reporting. Optional extensions allow for certified integration with industry leading Enterprise Management solutions including HP Operations Center (formerly OpenView Operations), BMC Performance Manager (formerly Patrol) and TIVOLI as well as remote alerting using mobile SMS and email.
All job status data can be relayed to a Windows server for both graphical and tabular reporting for Management Reports and Real-Time graphical tracking.
Integrated monitoring, reporting and management of batch schedules are available, including the following features :
- Pathway and / or GUI interfaces
- Batch tracking
- Run Guardian and Open System Services (OSS) applications within the same batch schedule
- NetBatch conversion utility available
- Automated Calendaring and Scheduling
- High performance parallel batch
- Network control transparent
- Simultaneous job execution
- Supports object parameters to ease maintenance in global schedule updates for multiple jobs
- A migration tool can be used to convert batch schedules between nodes for easy replication in a multi-node environment
- Optional checkpoint / restart
- Dynamically amend the start time of job(s) e.g. /- 1 hour
- SNMP gateways available
- 3 levels of job hierarchy, 2 levels of dependency
- Secure execution shell
- Fully EMS compatible
Advantages :
Basically, there are a number of advantages to using MultiBatch in preference to NetBatch and these are summarised below :
Maintenance & Development
NetBatch is a mature product and will not be subject to further development. New facilities and functionality are still being developed for MultiBatch, driven by customer requirements.
Interface
NetBatch has either a command line or Pathway interface. MultiBatch has both of these and a GUI.
Scheduler
NetBatch controls the execution of a batch schedule and relies heavily on a JCL to control the actual jobs within a schedule. MultiBatch controls the execution of each element of a batch schedule. Individual jobs and their elements are more visible within MultiBatch. The attributes of each job within the schedule can be viewed and altered using MultiBatch application screens and all changes are subject to the appropriate security clearance and are recorded in an audit log. NetBatch jobs can be amended using an editor and are thus not subject to any security vetting or auditing.
Failures
NetBatch again relies on a complex JCL to detect failures in the elements of a schedule. Because MultiBatch controls each element of a batch schedule the detection of failures and the restarting of a schedule at the correct point is a simple matter.
Parallel Processing
Once again, NetBatch relies on the JCL for parallel processing and monitoring whilst it is an easy task to configure a MultiBatch schedule to handle this.
Reporting
NetBatch status information is written to a log file or spooler, making it difficult to integrate with a 3rd party enterprise manager. MultiBatch writes status information in the form of EMS events, allowing monitoring by 3rd party tools. Additionally, it is closely integrated with other products from ITL for more in-depth monitoring. In addition to the above, a migration tool is available that will allow a NetBatch schedule to be converted to a MultiBatch schedule.
Click here to view sample MultiBatch screenshots.
HP NonStop Batch Job Scheduling Comparison :
Both HP’s NetBatch and Insider Technologies Ltd’s MultiBatch products are designed to provide a Batch Scheduler for the HP NonStop server environment. Both products do accomplish this, however each uses a different methodology to achieve its aim, resulting in each product having quite different capabilities.
NetBatch and MultiBatch both consist of a PATHWAY interface to a scheduling engine, as well as a command line utility. The MultiBatch product also includes a GUI. NetBatch requires the user to develop and maintain a JCL, written in NBEXEC or TACL, to control the sequencing of jobs. This requires knowledge of both these products and will incur a maintenance overhead.
Although MultiBatch can use both TACL and NBEXEC as executors, natively there is no MultiBatch JCL. All job run parameters, sequencing and dependencies are maintained by the MultiBatch application. The user only requires knowledge of MultiBatch and the batch schedule.
Both products have a calendar facility, enabling automation to be controlled on a time/date basis. Whilst NetBatch applies this control to the batch executor, MultiBatch is the executor, and thus applies this control to the batch jobs themselves.
Although both products have been around for some time, MultiBatch is still being enhanced, with new facilities and features being developed. Insider Technologies Ltd. have no plans for stopping development or withdrawing support. HP classes NetBatch as a ‘Mature’ product, hence no further development or enhancement will be undertaken.
| Competitive Points |
Comments |
NetBatch |
MultiBatch |
| Single point of operations control across the EXPAND network |
|
N |
Y |
| Requires no command-line syntax to configure / initiate jobs |
|
N |
Y |
| GUI available for operational control and status tracking |
|
N |
Y |
| GUI available for batch job configuration |
|
N |
Y |
| GANTT style job status / progress GUI (MCP) |
|
N |
Y |
| GUI available for user configuration management and security control |
|
N |
Y |
| Calendaring facility, includes holidays, etc. specification |
|
Y |
Y |
| GUI available for calendar set-up and management |
|
N |
Y |
| Job control integrity check (pre-run) |
|
N |
Y |
| Application / Job API to start / stop control jobs by application |
|
N |
Y |
| Job dependency checks (job release control) |
|
Y |
Y |
| Device dependency checks |
|
Y |
N |
| Designed and coded for NonStop (Fault Tolerant running) |
|
Y |
Y |
| TMF transaction protected "safe auto-recovery from fail" facility |
Jobs may be safely auto-restarted after failure of a CPU |
N |
Y |
| Able to launch work to be managed by TACL control program / file |
|
Y |
Y |
| Job streams may be run in parallel |
|
Y |
Y |
| Job steps within streams maybe run in parallel |
|
N |
Y |
| Able to launch Open System Services (OSS) programs |
|
Y |
Y |
| Able to accept OSS filenames of full-length |
|
Y |
Y |
| Does not require Shell or Shell Knowledge to launch OSS jobs |
|
N |
Y |
| Security audit log of changes |
|
N |
Y |
| Optional block-mode green-screen supplied as standard for fast bulk entry |
|
N |
Y |
| Ability to prepare a virtual copy of the schedule |
|
N |
Y |
MultiBatch can be provided with an optional Mangement Information Reports module (MCP). This is installed on a nominated MS Windows Server platform with SQL Server 2005. All job related data is stored in the SQL database detailing all batch schedule metrics, e.g. job run times, key jobs.
Users can also script their own reports using the MS Reporting Services tool with SQL Server 2005. This provides a very extensible solution for MI reports for all HP NonStop platforms including Integrity and Blade technologies.
Examples:
HP NonStop Batch Scheduling - MultiBatch Job Run Times
This MultiBatch report provides a bar chart showing the job run times of the specified job id. Additional details are provided in the associated table.
The report allows a user to specify a Start & End Date/Time range; HP NonStop Node name; MultiBatch BMON Process Id; Job Id.
A user can also report on all jobs and/or all BMON processes by specifying 'All' (without quote marks) in the parameter fields.
The line graph and associated table contains the run time (in seconds) of how long the job has taken to 'run'.
Note: There are various reasons for the job 'completion', e.g. the job may have completed successfully, abended, aborted by operator or reached maxtime and aborted. The report is based on the various types of 'completion' events and not just on the MultiBatch 'job complete' event.
The 'Event Text' column contains the MultiBatch EMS event text which will show the reason for the job 'completion'.
HP NonStop Batch Scheduling - MultiBatch Report Key Jobs
This MultiBatch report provides a line graph to show the start & end points of a specified Unit and Job, respectively. These specified values are for key jobs which a user expects to have Started and Completed by a certain time.
The report allows a user to specify a Start & End Date/Time range; HP NonStop Node name; MultiBatch BMON Process Id and the id of the 'start' Job.Segment.Unit and the id of the 'end' Job.
Two additional parameters are required for completion: Batch Hour & Batch Min. A user must specify in these two fields, an expected (or usual) Start Time for the Job.Segment.Unit. For example, if the specified Unit of 'JOBA.AA.01' usually starts ar 15:30, then specify 15 in the Batch Hour field and 30 in the Batch Min field.
The line graph will display two lines, one for the 'start' job.segment.unit and one for the 'end' job. If the 'start' time of the specified Unit differs from the value entered, e.g. 15:30 has been specified but on a particular day the specified Unit actually started at 15:15, then the line graph and associated table will show the differences in start time.
The associated table will show JOB Id1 and its actual start time, with a column showing any + or - differences from the specified 'Usual Start Time'. JOB Id2 is displayed in the table, followd by the 'duration' in minutes, between the start of JOB Id1 and the end of JOB Id2.
Minimum Windows Hardware Requirements for
MultiBatch MS Management Information Reports
For optimum performance, it is recommended that the minimum specification of your hardware and software is as follows :
- Windows Server 2000 / 2003 / 2008 with the latest service packs
- Microsoft SQL Server 2005 / 2008 with the latest service packs
- Microsoft Internet Information Services (IIS) for the Sentra/MultiBatch Web client interface
- Internet Explorer version 6 or 7 for the Sentra Web client interface
- Pentium 2 GHz Processor
- 4 Gb RAM recommended
- SCSI interface (SCSI2 Ultra-Wide recommended)
- 10 GB Single Drive for operating system and SQL Server software
- *40 GB Single Drive for the SQL server database (RAID 0+1 recommended)
- 20 GB Single Drive for the SQL server log file (RAID 0+1 recommended)
- Graphics resolution 1024 x 768 recommended
- 17" or larger colour monitor is also recommended
The above specification is for guidance only. The specification of your Windows server will be dependent on your individual MultiBatch reporting needs. Please contact the Insider Technologies Helpdesk for assistance in establishing the specification of your server.
SQL Server Versions Supported by Sentra/MultiBatch (also install Microsoft SQL Reporting Services)
The Sentra/MultiBatch database is compatible with the following variants of SQL Server :
- 2005 / 2008 Standard Edition
- 2005 / 2008 Enterprise Edition
- 2005 / 2008 Developer Edition*
- 2005 / 2008 Express – the default installation on the CD uses SQL Express with Advanced services, so that SQL Reporting Services is available
* Some SQL editions include a concurrent workload governor. Performance degrades when more than five queries are executed concurrently. Sentra/MultiBatch will work with these versions of SQL Server but performance may be unacceptably slow and its installation is not recommended for high volume usage.
SQL Express editions support databases with a limited maximum size (4Gb for SQL Express 2005). Users who anticipate large database storage requirements should consider installing the Enterprise edition of Microsoft SQL Server, or contact Insider Technologies for advice.
MultiBatch HP NonStop Batch Scheduler and Open System Services (OSS)
The MultiBatch product has been enhanced to allow users to execute hp NonStop Open System Service (OSS) programs from BMON (Batch Monitor Process).
There are no OSS components to install; Insider has taken advantage of a procedure call that allows GUARDIAN programs, i.e. BMON, to spawn OSS processes.
A general principle of the new functionality is that everything else about the MultiBatch product remains unchanged.
- You create a BMON, JOB and SEGMENT record before creating an OSS step.
- You then run the PREPARE to create the OSS step configuration. OSS steps can be included / excluded based on days of the week or a calendar.
- You issue a BUILD command to load an OSS step into a BMON.
- You can still use DS-EventTimer to start an OSS step.
- OSS status is still logged to a maximum of 2 log files, one of which can be the MBSTREAM program.
- BMON’s do not need to be exclusively Guardian or OSS. For example a Guardian job can be dependent on an OSS job and vice-versa.
- Progress can be monitored via the PATHWAY status screens updated by the Watcher program or by Reflex (see Reflex for monitoring HP NonStop Batch Schedules and PowerPoint - 1.6MB).
You can only configure an OSS step via the PATHWAY screens; there is no GUI support at the current release.
The security matrix enables you to map existing facilities to both Guardian and OSS requirements. For example on the security class screen;
The CST setting covers configuring Guardian steps (CST) and OSS steps (COS).
Likewise the assign class (Guardian) and corresponding FD class (OSS), and the parameter (Guardian) and corresponding environment variable class (OSS) are mapped to the CAS and CPA settings respectively.
The remainder of this tab provides some screenshots taken from the PATHWAY screens used to configure a simple UNIX sleep (DELAY) command as an example.
NOTE: This example can be loaded from a MultiBatch transit file.
Create a BMON, Job, and Segment record in the hierarchy before your OSS step.
Create the OSS step on screen COS.
In this simple example we will be configuring a 45 second delay or sleep command. We need to configure the executable name (sleep), start-up arguments (45) and the working directory (/bin/) using the two ‘basic’ overlays.
If you want to configure defines, then the existing defines overlay can be used.
You also have the ability to configure file descriptors and environment variables which are the equivalent of Guardian file assignments and parameters.
Once the BMON has been ‘PREPARE'd’, the following configuration file is generated for our example OSS STEP.
When the BMON is built, then you can enquire on the status and configuration of the OSS step using BCOM.
The progress of the schedule is logged to EMS.
Errors are also reported to EMS. Error 4002 = No such pathname exists or missing executable.
|
| Name |
Demonstration |
View |
MultiBatch Demonstration
(ZIP - 1.25Mb) |
This demonstration focuses on the MultiBatch Control Point (MCP) which is a set of integrated configuration and management facilities accessed through a single user interface.
|
 |
MultiBatch Set-up Overview
(ZIP - 2Mb) |
This demonstration of the MultiBatch GUI provides an overview of setting up the jobs, segments and units of a batch schedule that enable the scheduler to provide optimised parallel processing for a batch run.
|
 |
Configure a MultiBatch Schedule
(1.7Mb) |
This demonstration of the MultiBatch GUI provides a more in-depth demonstration of configuring a MultiBatch schedule starting with setting up a BMON.
|
|
MultiBatch Step Configuration
(ZIP - 1.1Mb) |
This MultiBatch STEP demonstration shows how a fourth level in the job, segment, unit hierarchy can be called upon for creating a very low level job dependency.
|
|
MultiBatch Audit Trail
(ZIP - 1.3Mb) |
All actions in the MultiBatch schedule are audited and all records can be accessed from the MultiBatch GUI.
|
|
MultiBatch Sentra Query
(ZIP - 3Mb) |
A demonstration of using Sentra for querying MultiBatch status. ITL's Sentra can be integrated for extensive MI reporting if required.
|
|
MultiBatch Sentra Status
(873Kb) |
Sentra can also provide the status of any MultiBatch schedule as well as comprehensive querying and Management Information reporting.
|
|
|
Hardware and software pre-requisites for the MultiBatch product are detailed below:
• HP NonStop (ServerNet or Integrity platforms)
• Guardian D38 Operating System (or above)
• TMF
• Pathway (TS/MP)
• TCP/IP (if using the MultiBatch GUI interface only)
MultiBatch is installed using a menu driven TACL macro for easy deployment. The macro will perform checks and output the results of each stage of the MultiBatch product install so that if problems are encountered they can be resolved easily.
Windows Platform for GUI Install
(not required if using the MultiBatch Pathway Green Screen interface):
• Modern Pentium PC Specification
• 32Mb on-board RAM
• 20Mb free hard disk space
• Minimum 17” monitor recommended
• Graphics Resolution: 1027 x 768 x 16 minimum
• Windows XP, Vista, 7
For MultiBatch management information reports, a Windows Server will be required with Microsoft SQL Server installed. Click the MI Reports tab to view hardware and software requirements for the MultiBatch MI plug-in.
Latest News :
MultiBatch Version 9.3G released
H06.20 accredited
Extensions:
- BCOM - history / FC functions
- MBSTREAM - caters for up to 30,000 alias names
- MBCSV - export batch schedule to a spreadsheet
- MBUSERHK - review and maintain MB security database
- WATCHER - alternate collector option
- User Authentication Check - alert if user if does not exist
Insider Technologies has successfully completed a HP NonStop Blade accreditation test exercise at the HP offices at Wood Street, London. The testing took place between December 17th and 19th 2008.
The ITL product successfully accredited was ;
MultiBatch
The mainframe class Batch scheduler for the HP NonStop environment.
The hp NonStop 'Blade Ready' version of the software is ;
MultiBatch, version 9.3F4
The software is available from December 22nd 2008.
The version of the Blade operating system that the product was verified against was ;
J06.04
For further information about the Insider Technologies Blade accreditation program, please contact the Insider Help Desk on +44 (0) 161 876 6606 or use our contact page.
For more information about the MultiBatch product - Contact Us.
OSS Batch Schedules and MultiBatch - Security
OSS Batch Schedules and MultiBatch - Assigns and Params
OSS Batch Schedules and MultiBatch - Configure the OSS Schedule
OSS Batch Schedules and MultiBatch - Configuration Screens
OSS Batch Schedules and MultiBatch - Configuration Screens
OSS Batch Schedules and MultiBatch - Environment Variables
OSS Batch Schedules and MultiBatch - File Descriptors
OSS Batch Schedules and MultiBatch - Configuration File
OSS Batch Schedules and MultiBatch - Configuration Enquiry
OSS Batch Schedules and MultiBatch - EMS Output
OSS Batch Schedules and MultiBatch - EMS Output Error
Reflex monitors Guardian and OSS Batch Schedules
Reflex monitoring WebSphere MQ on HP NonStop (and OSS)
MultiBatch Batch Job Scheduler - Event-Timer AT Schedule Screenshot
The security matrix enables you to map existing facilities to both Guardian and OSS requirements. For example on the security class screen;
Likewise the assign class (Guardian) and corresponding FD class (OSS), and the parameter (Guardian) and corresponding environment variable class (OSS) are mapped to the CAS and CPA settings respectively.
Create a BMON, Job, and Segment record in the hierarchy before your OSS step.
In this simple example we will be configuring a 45 second delay or sleep command. We need to configure the executable name (sleep), start-up arguments (45) and the working directory (/bin/) using the two ‘basic’ overlays.
In this simple example we will be configuring a 45 second delay or sleep command. We need to configure the executable name (sleep), start-up arguments (45) and the working directory (/bin/) using the two ‘basic’ overlays.
You also have the ability to configure file descriptors and environment variables which are the equivalent of Guardian file assignments and parameters.
You also have the ability to configure file descriptors and environment variables which are the equivalent of Guardian file assignments and parameters.
Once the BMON has been ‘PREPARE'd’, the following configuration file is generated for our example OSS STEP.
When the BMON is built, then you can enquire on the status and configuration of the OSS step using BCOM.
The progress of the schedule is logged to EMS.
Errors are also reported to EMS. Error 4002= No such pathname exists or missing executable.
Reflex for MultiBatch and NetBatch Scheduler Monitoring
Reflex can be used for monitoring both Guardian and Open System Services (OSS) Batch Job Schedules on the HP NonStop platform (Integrity, Itanium, ServerNet and Blades).
Reflex monitoring WebSphere MQ on HP NonStop (and OSS)
Reflex provides auto-detection of WebSphere MQ components (Queue Managers, Queues and Channels) on HP NonStop (and OSS) as well as status monitoring and detailed information at a single click.
IBM WebSphere MQ V5.3 Extended to the HP NonStop Server Platform
At a glance :
WebSphere MQ for HP NonStop Server V5.3 (5.3.1.4) enriches WebSphere MQ. It includes:
- Functional equivalence to other WebSphere MQ V5.3 platforms
- Availability on the HP NonStop Server S-series and NonStop Integrity Server (32-bit) architectures
- Full enablement of the Java(TM) Message Service (JMS) application programming interface: embedded classes for Java and JMS support with improved performance and packaging
- A Publish/Subscribe function, which simplifies the task of getting business messages and transactions to a wide, dynamic, and potentially large audience in a timely manner
- Scalability and usability improvements over the previous MQSeries® offering
- Improved MQ workload balancing (through clustering)
- Improved national language support (for example, code page GB18030 for use in the People's Republic of China)
- SSL security authentication facilities
- Four out of five customers who buy inter-application messaging choose WebSphere MQ, according to WinterGreen Research, Inc.1.
Overview
WebSphere® MQ for HP NonStop Server V5.3 builds on the success of WebSphere MQ, the market-leading provider of message-oriented-middleware (MOM) software for application connectivity. WebSphere MQ brings enhanced security, better and more flexible management and tuning capability, and added features to enhance cross-platform consistency.
For common security problems, WebSphere MQ provides:
- Symmetric key cryptography to prevent eavesdropping
- The hash function to prevent tampering
- Digital certificates, asymmetric keys, and certificate revocation lists to prevent impersonation
These security features are implemented using a port of the OpenSSL cryptographic software, provided by IBM with this release.
General MQ operation is significantly enhanced by a process management rules database that enables sophisticated, yet easy-to-use control over the unique multiprocessor architecture of a WebSphere MQ queue manager running on HP NonStop Server.
Most components now run in the Open System Services (OSS) environment of HP NonStop Server, enabling the use of multi-threaded agent processes. This feature can enable a more efficient, scalable implementation for typical mixed workloads.
Reliability and data integrity are enhanced with the introduction of a fault-tolerant Execution Controller process-pair. Components critical to data storage retain their fault-tolerant capabilities, and critical databases remain in the transactional Guardian file system.
The use of OSS, plus other enhancements (including data link libraries), also results in a more consistent set of interfaces to WebSphere MQ on HP NonStop Server, while continuing to support all existing languages and environments. Support for the new Itanium-based HP NonStop Integrity Server is also provided.
Connects applications reliably and affordably
Connects nearly everything to almost anything, reducing IT complexity
Provides IBM's industry-leading messaging middleware at an affordable price
Enables fast and easy installation and deployment: Gets you up and running in minutes and in production within hours, without specialist training
Offers scalability and flexibility for growth
Provides seamless growth for your software as your business needs evolve
Is compatible with WebSphere MQ on many platforms
Takes advantage of a portfolio of product extensions to deliver additional capabilities fast
Speeds solution development and reduces support costs
Simplifies networking interfaces, cuts application development time, and enables design and code reuse
Is supported by more than 3,000 certified professionals
Supports key platforms with the industry's de facto messaging standard
Runs on the HP NonStop Server S-series and NonStop Integrity Server (32-bit) platforms
Extends the WebSphere MQ family MultiBatch Batch Job Scheduler - Event-Timer AT Schedule Screenshot
Time based scheduling is provided within the MultiBatch product. Batch jobs can be configured to run 'AT' a given time of a day, e.g. AT 21:00 DAILY. Once this job has completed successfully, dependent jobs will then execute. An alternative option is to configure jobs to execute regularly at a fixed interval, this is known as the 'EVERY' facility, e.g. EVERY 30 MINUTES.
HP NonStop Batch Scheduling - MultiBatch Job Run Times
HP NonStop Batch Scheduling - MultiBatch Report Key Jobs
HP NonStop Batch Scheduling - MultiBatch Job Run Times
This MultiBatch report provides a bar chart showing the job run times of the specified job id. Additional details are provided in the associated table.
The report allows a user to specify a Start & End Date/Time range; HP NonStop Node name; MultiBatch BMON Process Id; Job Id.
A user can also report on all jobs and/or all BMON processes by specifying 'All' (without quote marks) in the parameter fields.
The line graph and associated table contains the run time (in seconds) of how long the job has taken to 'run'.
Note: There are various reasons for the job 'completion', e.g. the job may have completed successfully, abended, aborted by operator or reached maxtime and aborted. The report is based on the various types of 'completion' events and not just on the MultiBatch 'job complete' event.
The 'Event Text' column contains the MultiBatch EMS event text which will show the reason for the job 'completion'.
HP NonStop Batch Scheduling - MultiBatch Report Key Jobs
This MultiBatch report provides a line graph to show the start & end points of a specified Unit and Job, respectively. These specified values are for key jobs which a user expects to have Started and Completed by a certain time.
The report allows a user to specify a Start & End Date/Time range; HP NonStop Node name; MultiBatch BMON Process Id and the id of the 'start' Job.Segment.Unit and the id of the 'end' Job.
Two additional parameters are required for completion: Batch Hour & Batch Min. A user must specify in these two fields, an expected (or usual) Start Time for the Job.Segment.Unit. For example, if the specified Unit of 'JOBA.AA.01' usually starts ar 15:30, then specify 15 in the Batch Hour field and 30 in the Batch Min field.
The line graph will display two lines, one for the 'start' job.segment.unit and one for the 'end' job. If the 'start' time of the specified Unit differs from the value entered, e.g. 15:30 has been specified but on a particular day the specified Unit actually started at 15:15, then the line graph and associated table will show the differences in start time.
The associated table will show JOB Id1 and its actual start time, with a column showing any + or - differences from the specified 'Usual Start Time'. JOB Id2 is displayed in the table, followd by the 'duration' in minutes, between the start of JOB Id1 and the end of JOB Id2.
|
|
|
|
|
|
|
|