═══ 1. Help for Batch Manager version 3.0 ═══ The purpose of "BATCH MANAGER" is to provide a vehicle to submit, monitor, and control jobs (OS/2 and DOS command files and executables) under the IBM OS/2 operating system. Three job queues are provided and the user can control the status of these queues. This product is patterned after other OS/2 products and is designed to be SAA/CUA compliant. "BATCH MANAGER" is translatable. Consult the vendor for details. The sub-system provides the following functions:  Submission and execution of jobs, either immediately or delayed to a later time/date. The jobs can be submitted either from this user interface, from the OS/2 command line using the BMSUBMIT facility provided by this sub-system or by using the OS/2 "drag and drop" facility to drop a job(s) (.CMD, .BAT or .EXE) upon the Monitor. Jobs can be submitted for either a single or recurring execution.  Control over the status of the queues which are responsible for controlling jobs.  Control over the status of the jobs, such as cancel, hold, release, change queue, change priority, etc. When "BATCH MANAGER" is started, two programs will be visible either on the desktop or in the minimized window viewer:  Batch Manager Monitor - The graphical user interface which allows the user to control the actions of the Batch Manager, including submitting and updating jobs, cancelling, requeuing, etc.  Batch Manager Scheduler - The program which actually manages the queues and jobs. Users communicate with the scheduler either by using the monitor or the Command Line Interface.  Command Line Interface The BM Scheduler must be started as a foreground session using BMSTART2.CMD in order to process applications with screen/keyboard I/O. (This is the default startup procedure after "BATCH MANAGER" is installed.) To run the scheduler as a detached process use BMSTART.CMD In this case jobs submitted to "BATCH MANAGER" cannot have any screen/keyboard I/O capability, and the scheduler will not be visible on the desktop. In either case the full path to the directory where "BATCH MANAGER" is installed must be provided as a parameter, e.g.: BMSTART2.CMD C:\MBABATCH A journal of all "BATCH MANAGER" activity is maintained in BMJOB.LOG in the "BATCH MANAGER" work directory (e.g., C:\MBABATCH). The log can be viewed from the Options Action Bar Choice. It is the users responsibility to clear this file on a regular basis. The log file is copied to a back-up version of the file (BMJOB.BAK) whenever "BATCH MANAGER" is initiated. A queue file is maintained by the "BATCH MANAGER" Scheduler for each of the three job queues (BMQUEUE1.DAT, BMQUEUE2.DAT, and BMQUEUE3.DAT). These files are read by the Scheduler at startup in order to restore the queues to the status existing when "BATCH MANAGER" was closed. In the event that a hardware or software problem causes "BATCH MANAGER" to terminate while a job(s) is active it may be necessary to delete these files before restarting "BATCH MANAGER". This action is usually required if the user has the following entry in the 'CONFIG.SYS' file: SET RESTARTOBJECTS=STARTUPFOLDERSONLY The product is licensed for use on a single OS/2 computer. For full terms of licensing, consult the license agreement accompanying the product package. Address any other questions, including pricing, to the vendor (see "About..." under the HELP action-bar-choice. This facility is typically executed at each computer and the jobs controlled by the individual user. The installation process adds "BATCH MANAGER" startup details to the 'STARTUP.CMD' file so that "BATCH MANAGER" is initiated when the user boots the computer. If "BATCH MANAGER" is terminated for any reason it can be restarted using either of the commands detailed previously. The BM Monitor, which is the Graphical User Interface (GUI) for the facility, is a window programmed around OS/2's "Presentation Manager." The window consists of the following action bar choices:  QUEUE - Provides the means to control the status of the queues.  JOB - Provides the means to control the actions of the job(s), including submitting and updating jobs, cancelling, requeuing, etc.  OPTIONS - Provides the means to display the Job Execution Log and suppress the end of job execution display and/or beep.  HELP - Provides guidance throughout facility. Pertinent pop-up windows are invoked as required to guide the user through the selected action. The main window displays the job queues, along with the jobs submitted to each queue. Each job is listed by Job Id, Job Name (as submitted by the user), scheduled Start Date, scheduled/actual Start Time, Job Status (Active, Pending, Holding, Delayed). A code is also displayed indicating whether the batch job is Single or Recurring (repetitive). The "BATCH MANAGER" queues are refreshed automatically whenever activity occurs. Because of this, the screen is always current. JOB FILES To submit a job, the user must submit a user specified job file (.CMD, .BAT or .EXE). This file must exist prior to job submission and must contain the full file\directory path name (no default directories are assumed) for any file specified in this command file. The 'EXIT' statement in a .CMD file may cause a return error message from OS/2 at the end of the job execution even though the the job is actually executed successfully. SUBMITTING JOBS FROM OS/2 COMMAND LINE The Command Line Interface is provided as an alternative for users to manage jobs and queues without interacting with the Graphical User Interface. This is primarily used to enable job submission from an external source (e.g., another user application or command procedure).  Command Line Interface  BMSUBMIT - submit new jobs  BMCHSTAT - change job status  BMJOB - get job status  BMLIST - list all jobs  BMGETQ - get the current status of queues  BMCHQ - change queue status  BMTERM - terminate the Scheduler  TERMPID - terminate a process JOB COMPLETION Upon completion of the batch job, a beep is sounded and a dialog box is displayed notifying the user whether or not the batch job was successfully executed. The user can remove the dialog by pressing the Ok button or the dialog will remove itself after 60 seconds. The user can suppress the beep and/or the dialog from the Options Action Bar Choice. A journal of all job completion messages is maintained in BMJOB.LOG in the "BATCH MANAGER" work directory (e.g., C:\MBABATCH). The log can be viewed from the Options Action Bar Choice. It is the users responsibility to clear this file on a regular basis. MESSAGES When a job is completed, a variety of messages may appear in the BMJOB.LOG) to indicate completion status; either ERROR or NO ERRORS. Some OS/2 Termination and Return Codes may also be displayed. Consult IBM OS/2 documentation for their meaning (e.g., "OS/2 Control Program Programming Reference"). SHUTDOWN If a batch job is ACTIVE in the job queue, the user will be unable to close the "BATCH MANAGER" Monitor and Scheduler. Should the computer SHUTDOWN (either through the OS/2 Desktop or power failure, the active batch job will abort execution). COMPUTER CLOCK Execution of "BATCH MANAGER" is based on the computer's clock. Should the you wish to change the settings on the clock, the user is advised to first HOLD the queues before changing the clock. After the clock has been changed, the user can then RELEASE the queues. Note: It may be necessary to UPDATE the time settings for the various jobs in the queues. Use the UPDATE/REQUEUE JOB window to update the time/date settings of each job before RELEASING the queues. TRADEMARK ACKNOWLEDGEMENTS IBM, OS/2, SAA, CUA are registered trademarks of the International Business Machines Corporation. ═══ 2. Help for Queue ABC ═══ Use the Queue action-bar-choice (ABC) to manage the queues. The pull-down-choices for individual queues are available only after you have selected a queue. (If you are using a mouse, click on the queue to select it. If you are using a keyboard, press the Up or Down Arrow key and ENTER to select it.) The following pull-down-choices are provided:  Hold queue  Release queue  Hold all queues  Release all queues ═══ 3. Help for Hold Queue PDC ═══ Use the Hold Queue pull-down-choice (PDC) to change the status of the selected queue so none of the jobs in it can be executed. This choice is not valid if the queue is already being held. Holding a queue when a job is executing (ACTIVE) does not stop the job. The job is allowed to finish, but the next job in the queue cannot start. Use Release queue to allow the jobs in the queue to execute. ═══ 4. Help for Release Queue PDC ═══ Use the Release Queue pull-down-choice (PDC) to change the status of a queue HOLDING so that jobs in it can be executed. This choice is valid only if the queue is HOLDING. Releasing a queue allows the jobs in the queue to be executed. Use the Job pull-down-choices if you want to change the order jobs are executed. ═══ 5. Help for Hold all Queues PDC ═══ Use the Hold All Queues pull-down-choice (PDC) to change the status of the all queues so no jobs can be executed. This choice is not valid if all the queues are already being held. Holding a queue when a job is executing (ACTIVE) does not stop the job. The job is allowed to finish, but the next job in the queue cannot start. Use Release all queues to allow the jobs in all the queues to execute. ═══ 6. Help for Release all Queues PDC ═══ Use the Release All Queues pull-down-choice (PDC) to change the status of all queues HOLDING so jobs can be executed. This choice is only valid if any queues are HOLDING. Releasing a queue allows the jobs in the queue to be executed. Use the Job pull-down-choices if you want to change the order jobs are executed. ═══ 7. Help for Hold all Jobs PDC ═══ Use the Hold all Jobs pull-down-choice (PDC) to change the status of the jobs in all the queues. All the jobs are held so they cannot be executed. Jobs submitted after this will not be held. If the jobs are already HOLDING, this choice has no effect. Active jobs will continue executing. ═══ 8. Help for Release all Jobs PDC ═══ Use the Release all Jobs pull-down-choice (PDC) to change the status of any jobs HOLDING in all queues. All the held jobs are released so they can be executed. If there are no jobs HOLDING, this choice has no effect. ═══ 9. Help for Cancel all Jobs PDC ═══ Use the Cancel all Jobs pull-down-choice (PDC) to remove all the jobs from all the queues. When you select this choice, a message is displayed asking you to confirm cancellation of the jobs. You cannot recover canceled jobs. You have to submit the jobs again if you want to execute them. Note: This cancels ALL jobs including active jobs. ═══ 10. Help for Job ABC ═══ The Job action-bar-choice (ABC) is used to control the action of job(s). A job identification number is created when you submit a batch job to the queue (whether ACTIVE, PENDING, DELAYED, or HOLDING). Use the following pull-down-choices (PDC) to control the execution of a job. These choices (except Submit new job) are available only after you have selected a job. (If you are using a mouse, click on the job or queue to select it. If you are using a keyboard, press the Up or Down Arrow keys to select it.)  Submit new job  Update/requeue job  Job details  Hold job  Release job  Cancel job  Hold all jobs  Release all jobs  Cancel all jobs ═══ 11. Help for Job Details PDC ═══ Use the Job Details pull-down-choice (PDC) to display the details of the selected job. ═══ 12. Help for Cancel Job PDC ═══ Use the Cancel Job pull-down-choice (PDC) to remove the selected job from the queue. If the job is executing, it is stopped. Note: Cancelling a recurring job will cancel all future executions of this job. To restart a recurring job, the user will have to use the SUBMIT PDC and reset the parameters. When you select this choice, a message is displayed, asking you to confirm cancelling the job. ═══ 13. Help for Hold Job PDC ═══ Use the Hold Job pull-down-choice (PDC) to change the status of the selected job so it does not execute. If the job is executing when you hold it, this choice has no effect. Holding one job does not affect the other jobs in the queue; they are executed as usual. Use RELEASE when you want to allow the job to execute. ═══ 14. Help for Release Job PDC ═══ Use the Release Job pull-down-choice (PDC) to change the status of the selected job so it can be executed. ═══ 15. Help for Submit new Job PDC ═══ Use the Submit new Job pull-down-choice (PDC) to invoke a pop-up window to initiate a new job. Note: This will be the same window as used under the Update/requeue job pull-down-choice. ═══ 16. Help for Update/Requeue Job PDC ═══ Use the Update/Requeue Job pull-down-choice (PDC) to invoke a pop-up window to change the variables associated with a job and/or to requeue the job. Note: This will be the same window as used under the Submit new Job pull-down-choice. ═══ 17. Help for Options ABC ═══ The Options action-bar-choice (ABC) is used to access the "BATCH MANAGER" Options. Use the following pull-down-choices (PDC) to select the desired option:  Display job log  Job end options ═══ 18. Help for Display Job Log PDC ═══ Use the Display Job Log pull-down-choice (PDC) to display the log of all activity since the log was last cleared. Use the Clear pushbutton to clear the current job log file. ═══ 19. Help for Job End Options PDC ═══ Use the Job End Options pull-down-choice (PDC) to suppress/activate the end of job execution display and beep. ═══ 20. Help for Help ABC ═══ The Help action-bar-choice (ABC) is used to access the various CUA compliant Help facilities. Help index General help Using help Keys help About... ═══ 21. Help for Using Help PDC ═══ Use the Using Help pull-down-choice (PDC) to describe all of the available help facilities. In general, help is provided for every action-bar-choice, pull-down choice, and other selections. ═══ 22. Help for General Help PDC ═══ This pull-down-choice is used to display general help text regarding the use of this facility. ═══ 23. Help for Keys Help PDC ═══ Use the Keys Help pull-down-choice (PDC) to access the standard help keys. The list of keys is arranged in groups.  HELP KEYS to get help.  SYSTEM KEYS to switch between programs.  WINDOW KEYS to move around in a program window.  POP-UP WINDOW KEYS to make a selection in a pop-up window.  EDITING KEYS to make changes in a pop-up window. When two key names are joined by a plus sign (+), use these two keys together. Hold down the first key and press the second key. HELP KEYS F1 Get help. F11 Go to the help index (from within any help window). Esc Cancel help. Alt+F4 Close the help window. Alt+F6 Go to/from help and programs. Shift+F10 Get help for help. SYSTEM KEYS Alt+Esc Switch to the next program, including full-screen programs. Alt+Tab Switch to the next windowed program. Ctrl+Esc Switch to the Task List. WINDOW KEYS F3 Close a program window. F10 Go to/from the action bar. Arrow keys Move among choices. End Go to the last choice in a pull-down. Esc Cancel a pull-down or the system menu. Home Go to the first choice in a pull-down. PgUp Scroll the contents of the window up one page. PgDn Scroll the contents of the window down one page. Underlined letter Move among the choices on the action bar and pull-downs. Alt Go to/from the action bar. Alt+F4 Close the window. Alt+F5 Restore the window. Alt+F7 Move the window. Alt+F8 Size the window. Alt+F9 Minimize the window. Alt+F10 Maximize the window. Ctrl+PgDn Scroll the contents of the window right one page. Ctrl+PgUp Scroll the contents of the window left one page. Shift+Esc or Alt+Spacebar Go to/from the system menu. Shift+Esc or Alt Go to/from the system menu of a text window. POP-UP WINDOW KEYS Enter Complete the pop-up window. Esc Cancel the pop-up window. Spacebar Set a check box on/off or perform the task described on the selected pushbutton. Tab Move to the next entry field or check box. EDITING KEYS Backspace (left arrow delete) Delete the character to the left of the cursor. Del Delete the character to the right of the cursor. End or Ctrl+Right Arrow key Move to the end of a field. Home or Ctrl+Left Arrow key Move to the beginning of a field. ═══ 24. Help for Help Index PDC ═══ This pull-down-choice is used to display the Help Index. The help index lists all of the titles of the available help information. ═══ 25. Help for About the Vendor PDC ═══ Use the About the Vendor pull-down-choice (PDC) to access the name and address of the vendor. ═══ 26. Help for Job Details ═══ This panel displays the following job details:  The Job Identification number.  The Job Name (as assigned by the user).  The Joe Queue - The queue controlling the job.  The Job Priority - The job execution priority.  The Start Date - either scheduled or actual.  The Start Time - either scheduled or actual.  The status of the job (ACTIVE, PENDING, DELAYED, or HOLDING).  The Single/Recurring indicator. A job may be submitted to execute either once (single) or repetitively (recurring).  The Recurring Period - if applicable.  The Elapsed Time - if the job is active.  The name of the command file (.CMD, .BAT or .EXE) used to execute the job. Press OK to exit the panel. ═══ 27. Help for Job Termination Details ═══ This panel appears when a job is terminated. It displays the following details:  The Queue Name  The Job Identification number.  The Job Name (as assigned by the user).  An End of job message This advises whether the job completed with errors or not. Press OK to close the panel. It will remove itself after 60 seconds if no action is taken. ═══ 28. Help for Submit/Update/Requeue Job ═══ This panel is used to either submit a new job, update the parameters for an existing job, and/or requeue an existing job. To SUBMIT a new job, the user must enter the following:  Enter Job Name - enter a user defined name to identify the job. If this field is left empty, the job file name will be used as the job name.  Enter Command File Name - Submit the name of a valid OS/2 or DOS command file or EXE to execute the job. The user can either enter the full directory\path\file name directly in the data field or select from the DIRECTORY and FILE selection lists shown. Note: If an invalid job file is given, an error message will be displayed. THE JOB FILE MUST PROVIDE FULL DIRECTORY\FILE PATHS; DEFAULTS ARE NOT ASSUMED. Note: The total text length for command file name and optional parameters must not exceed 123 characters.  The user can specify optional parameters for the job to be executed; e.g., a file name which needs to be passed to the job. If no parameters are needed, leave this field blank.  Select the desired queue from the queue selection list. Note: Queue 1 is the default.  Select the required job priority from the priority selection list. Note: Regular priority is the default.  Indicate if the job is to be executed SINGLE or RECURRING Single means one execution of the job; Recurring means to execute the job repetitively.  For single jobs, enter the starting date and time. The default is to execute immediately. The user can override this by submitting a date as YYYYMMDD (Year/Month/Day); for example: 19951211 = December 11, 1995. Time is submitted as HH:MM (Hours/Minutes) using a 24 hour clock; for example; 14:30 = 2:30 pm; 09:00 = 9 am.  For recurring jobs, the user must select the frequency of the job from the selection list of variables shown, and provide the starting time as HH:MM (Hours/Minutes). Note: The starting date is not specified for a recurring job.  Multiple recurring jobs with same starting time can be submitted by selecting several recurring periods at one time in the selection list; e.g., Monday, Wednesday, Friday. To UPDATE/REQUEUE a job, the current job parameters are displayed on the panel. The user can change them as required. Press OK to confirm selections and execute accordingly. Press Cancel to quit without saving. ═══ 29. Help for About the Vendor ═══ This panel displays the name and address of the vendor. ═══ 30. Help for Job Log Display ═══ This panel displays the details of all "BATCH MANAGER" activity that has occurred since the log was last cleared. Use the Clear pushbutton to clear the current job log file. Each entry in the log shows the following information: Date and Time Shows the actual date and time the action took place. Queue Name The name of the Queue involved in the action. Job ID and Name The Job ID and Name if the action involves a job. Details A message showing the action taken. Portions of the log can be copied to the clipboard for use in user reports by selecting the required details and using the Copy ABC. Alternatively the log file can be copied and edited by the user. ═══ 31. Help for About the Vendor Demonstration Version ═══ This panel displays the name and address of the vendor and identifies a demonstration version of the product. ═══ 32. Help for End of Demonstration ═══ This panel is displayed when the demonstration version has either passed the 30 days or 30 jobs have been executed. It displays the name and address of the vendor. ═══ 33. Help for Job End Options ═══ This panel is used to display and change the current settings for the end of job execution display and beep. End of job display and beep Activates a display and beep when a job finishes executing. End of job display only Activates a display and no beep when a job finishes executing. End of job beep only Activates a beep and no display when a job finishes executing. No display or beep Suppress both the display and beep when a job finishes executing. Press Ok to confirm selection. Press Cancel to quit without saving. ═══ 34. Help for Command Line Interface ═══ OS/2 "BATCH MANAGER" provides a series of command line interfaces as an alternative way for users to submit/monitor batch jobs and manage the queues without interacting with the Graphical User Interface. The functions are as follows:  BMSUBMIT - submit new jobs  BMCHSTAT - change job status  BMJOB - get job status  BMLIST - list all jobs  BMGETQ - get the current status of queues  BMCHQ - change queue status  BMTERM - terminate the Scheduler  TERMPID - terminate a process ═══ 35. Help for BMSUBMIT - Submit New Job ═══ The BMSUBMIT.EXE is provided as an alternative for users to submit jobs without interacting with the Graphical User Interface. This is primarily used to enable job submission from an external source (e.g., another user application or command procedure). Execute the BMSUBMIT program with the following calling format: Calling Format: (The arguments in brackets are optional) BMSUBMIT CMDFile ["JobName"] [/JobStatus] [StartDate StartTime] [/SingleRecurring] [/RecurringPeriod] [/QueueNumber] [/JobPriority] [+CmdArg] ARGUMENT DESCRIPTION -------------------- ------------------------------------------------------ CMDFile The command file name with full path JobName The name of this job starting with an alphabetical character (up to 30) JobStatus /TP (pending is the default), /TD (delayed), /TH (hold) StartDate StartTime YYYYMMDD HHMM, the default is current time /SingleRecurring /S (single is the default), /R (recurring) /RecurringPeriod /1 (every day), /2 (every other day) /3 (every Sunday), /4 (every Monday) /5 (every Tuesday), /6 (every Wednesday) /7 (every Thursday), /8 (every Friday) /9 (every Saturday), /10 (First Day of Month) /11 (2nd day of Month), /12 (3rd Day of Month) /13 (4th day of Month), /14 (5th Day of Month) /15 (6th day of Month), /16 (7th Day of Month) /17 (8th day of Month), /18 (9th Day of Month) /19 (10th day of Month) /20 (11th Day of Month) /21 (12th day of Month) /22 (13th Day of Month) /23 (14th day of Month) /24 (15th Day of Month) /25 (16th day of Month) /26 (17th Day of Month) /27 (18th day of Month) /28 (19th Day of Month) /29 (20th day of Month) /30 (21st Day of Month) /31 (22nd day of Month) /32 (23rd Day of Month) /33 (24th day of Month) /34 (25th Day of Month) /35 (26th day of Month) /36 (27th Day of Month) /37 (28th day of Month) /38 (29th Day of Month) /39 (30th day of Month) /40 (Last Day of Month) ═══ 36. Help for BMCHSTAT - Change Job Status ═══ The BMCHSTAT.EXE allows users to change the status of previously submitted batch jobs. Execute the BMCHSTAT program with the following calling format: Calling Format: (The arguments in brackets are optional but at least one optional parameter must be specified.) BMCHSTAT JobId [/JobStatus] [StartDate StartTime] [/SingleRecurring] [/RecurringPeriod] [/QueueNumber] [/JobPriority] ARGUMENT DESCRIPTION -------------------- ------------------------------------------------------ JobId The Job Id /JobStatus The desired job status /TP (pending, default) /TD (delayed) /TH (hold) /TR (release) StartDate StartTime The required start date and time YYYYMMDD HHMM (default is current time) /SingleRecurring The job type /S (Single, default) /R (Recurring) /RecurringPeriod The Recurring Job Period /1 (every day), /2 (every other day) /3 (every Sunday), /4 (every Monday) /5 (every Tuesday), /6 (every Wednesday) /7 (every Thursday), /8 (every Friday) /9 (every Saturday), /10 (First Day of Month) /11 (2nd day of Month), /12 (3rd Day of Month) /13 (4th day of Month), /14 (5th Day of Month) /15 (6th day of Month), /16 (7th Day of Month) /17 (8th day of Month), /18 (9th Day of Month) /19 (10th day of Month) /20 (11th Day of Month) /21 (12th day of Month) /22 (13th Day of Month) /23 (14th day of Month) /24 (15th Day of Month) /25 (16th day of Month) /26 (17th Day of Month) /27 (18th day of Month) /28 (19th Day of Month) /29 (20th day of Month) /30 (21st Day of Month) /31 (22nd day of Month) /32 (23rd Day of Month) /33 (24th day of Month) /34 (25th Day of Month) /35 (26th day of Month) /36 (27th Day of Month) /37 (28th day of Month) /38 (29th Day of Month) /39 (30th day of Month) /40 (Last Day of Month) /QueueNumber /Qn (n is 1 thru 3, default is 1) /JobPriority /J (n is 1 thru 4, default is 2) /J1 - Idle Time (lowest) /J2 - Regular (default) /J3 - Time Critical (highest) /J4 - Server Note: A JobId of 0 (zero) can be used to identify all jobs in the queues. This can be used to Hold/Release/Cancel all jobs. ═══ 37. Help for BMJOB - Get Job Status ═══ The BMJOB.EXE allows users to get the status of a single job. Execute the BMJOB program with the following calling format: BMJOB JobId ARGUMENT DESCRIPTION -------------------- ------------------------------------------------------ JobId JobId as displayed by BMLIST. ═══ 38. Help for BMLIST - List all Jobs ═══ The BMLIST.EXE allows users to list the status of all jobs in the queues. Execute the BMLIST program with the following calling format: BMLIST The output format is as follows: COLUMN DESCRIPTION ------ ----------- JID Job Id Job Name The name of the job Job Status The Job Status P (pending) D (delayed) H (hold) A (active) Start Date The Job start Date YYYYMMDD Start Time The Job Start Time HHMM C/J Job File Type C (OS/2 Command File) J ("PRIDE" INFORMATION FACTORY Job) R/S Type of Job S (Single) R (Recurring) P Recurring Time Period Execute Time Elapsed Execution Time (active jobs only) Queue The name of the job queue. Priority The job priority. ═══ 39. Help for BMGETQ - Get Status of all Queues ═══ The BMGETQ.EXE allows users to get the status of the job queues. Execute the BMGETQ program with the following calling format: BMGETQ The output format is as follows: COLUMN DESCRIPTION ------ ----------- Queue Name The name of the job queue Queue Stat The queue status A (active) H (hold) *************************************************************** ═══ 40. Help for BMCHQ - Change Queue Status ═══ The BMCHQ.EXE allows users to change the status of a job queue. Execute the BMCHQ program with the following calling format: BMCHQ QueueNumber NewStatus ARGUMENT DESCRIPTION -------------------- ------------------------------------------------------ QueueNumber 1, 2 or 3. Status A (active) H (hold) ═══ 41. Help for BMTERM - Terminate Scheduler ═══ The BMTERM.EXE allows users to terminate the "BATCH MANAGER" scheduler. Note: This only terminates the Scheduler, not the Monitor. It is intended for use only when the Monitor is not running, and the Scheduler is running in background mode. The Scheduler will not terminate if any jobs are active. In this situation cancel any active jobs before executing this function. Execute the BMTERM program with the following calling format: BMTERM ═══ 42. Help for TERMPID - Terminate a Background Process ═══ The TERMPID.EXE allows users to terminate a current process. It can be used if a job submitted to "BATCH MANAGER" has got into a loop and is ignoring a CANCEL request from "BATCH MANAGER". Execute the TERMPID program with the following format: TERMPID Pid ARGUMENT DESCRIPTION -------------------- ------------------------------------------------------ Pid Process ID number in decimal. ═══ 43. Help for Confirm cancel all jobs message box ═══ This message box asks the user to confirm that all jobs are to be cancelled. Press Ok to continue or Cancel to cancel the request. ═══ 44. Help for Confirm cancel job message box ═══ This message box asks the user to confirm that the selected job is to be cancelled. Press Ok to continue or Cancel to cancel the request. ═══ 45. Help for No Job Selected message box ═══ This message box informs the user that no job has been selected. Press Ok to return to the main window and select the desired job. ═══ 46. Help for BATCH MANAGER not idle message box ═══ This message box informs the user that there are active jobs so "BATCH MANAGER" has not been closed. Any active jobs must be cancelled before closing "BATCH MANAGER". Press Ok to return to the main window. ═══ 47. Help for Confirm Clear log message box ═══ This message box asks the user to confirm the clear log request. Press Ok to continue or Cancel to cancel the request. ═══ 48. Help for Confirm Close Batch Manager Message Box ═══ This message box asks the user to confirm the close Batch Manager Request. Press Ok to continue or Cancel to cancel the request.