NetBatch Manual Abstract This manual describes NetBatch, an HP NonStop™ software product that automates job scheduling, startup, and management on HP NonStop S-series system and HP Integrity NonStop NS-series system. The manual contains a product overview, software installation instructions, and planning, setup, and usage guidelines for NetBatch objects. The manual also contains descriptions of NetBatch commands and object attributes. Product Version NetBatch D30.
Document History Part Number Product Version Published 142530 NetBatch D30 August 1998 522460-001 NetBatch D30 February 2002 522460-002 NetBatch D30 May 2002 522460-003 NetBatch D30 September 2005 522460-004 NetBatch D30, H01 January 2007
NetBatch Manual Glossary Index Figures What’s New in This Manual xiii Manual Information xiii New and Changed Information About This Manual xvii Audience xvii Organization xvii Further Reading xix Notation Conventions Abbreviations xxiv Tables xiii xx 1.
1. NetBatch Introduction (continued) Contents 1. NetBatch Introduction (continued) Job Scheduling and Startup 1-8 Job Tracking, Control, and Termination NetBatch High-PIN Capabilities 1-12 1-9 2.
Contents 3. Scheduler Planning, Configuration, and Management (continued) 3.
4. Job Planning, Submission, and Management (continued) Contents 4. Job Planning, Submission, and Management (continued) Displaying Job Status 4-42 Altering Job Attributes 4-44 Overriding Job Dependencies, Timing Attributes, and Selection Priority Suspending and Reactivating Job Processes 4-45 Stopping and Deleting Jobs 4-46 Dealing With Job Output 4-47 4-44 5.
6. Commands (continued) Contents 6.
6. Commands (continued) Contents 6.
6. Commands (continued) Contents 6. Commands (continued) SWITCHCPU SCHEDULER Command SWITCHLOG SCHEDULER Command SYSTEM Command 6-195 VOLUME Command 6-196 ! Command 6-198 ? Command 6-200 6-192 6-193 7.
7. Attributes (continued) Contents 7.
7. Attributes (continued) Contents 7. Attributes (continued) TAPEDRIVES Scheduler Attribute 7-110 TEMPORARY Attachment-Set Attribute 7-112 TERM Job Attribute 7-114 VOLUME Job Attribute 7-116 WAIT Job Attribute 7-118 WAITON Job Attribute 7-119 A. Messages Message Types A-2 Error Messages A-2 Informational Messages A-2 Warning Messages A-2 Message Descriptions A-3 B.
C. National Language Support Contents C.
Figures (continued) Contents Figures (continued) Figure 4-10. Figure 4-11. Figure 4-12. Figure 4-13. Figure 6-1. Figure 6-2. Figure 6-3. Figure 6-4. Figure 6-5. Figure 6-6. Figure 6-7.
Tables (continued) Contents Tables (continued) Table 6-4. Table 6-5. Table 6-6. Table 6-7. Table 6-8. Table 6-9. Table 7-1. Table 7-2. Table 7-3.
What’s New in This Manual Manual Information NetBatch Manual Abstract This manual describes NetBatch, an HP NonStop™ software product that automates job scheduling, startup, and management on HP NonStop S-series system and HP Integrity NonStop NS-series system. The manual contains a product overview, software installation instructions, and planning, setup, and usage guidelines for NetBatch objects. The manual also contains descriptions of NetBatch commands and object attributes.
Changes to the G06.27 Manual What’s New in This Manual • • • Changed the range of job numbers for systems running G-series RVUs on pages 4-13, 6-187, A-23, and Glossary-5. Changed the consideration on DST explaining how next-runtime is calculated after DST on page 6-188. Added the error message 2110-E on page A-25. Changes to the G06.27 Manual • • • • • Updated the TACL RUN command with the REPORT and jobrun-databasesubvol attributes under Running NETBATCH on page 3-10.
Changes to the G06.
Changes to the G06.
About This Manual This manual describes NetBatch, an HP NonStop software product that automates job scheduling, startup, and management on HP NonStop systems. The manual contains a product overview, software installation instructions, and planning, setup, and usage guidelines for NetBatch objects. The manual also contains descriptions of NetBatch commands and object attributes.
Organization About This Manual Section Description Section 6, Commands Describes and gives examples of the syntax, operation, and results of all BATCHCOM commands. Section 7, Attributes Describes and gives examples of the syntax, operation, and results of all attachment-set, class, executor, job, and scheduler attributes. Appendix A, Messages Lists NetBatch error, informational, and warning messages, and gives cause, effect, and recovery information for those messages.
Further Reading About This Manual Further Reading This manual contains references to: Manual Description Debug Manual Describes the Guardian debug facility on TNS and TNS/R systems DSM Template Services Manual Describes Distributed Systems Management (DSM) Template Services, which support the representation of SPI buffers in display text DSM/SCM User’s Guide Describes how to plan for and install a new software release or software product revision (SPR) using DSM/SCM.
Notation Conventions About This Manual Manual Description SPI Programming Manual Describes the Subsystem Programmatic Interface and tells how to use it in management applications and subsystems you write System Generation Manual Describes software installation and system generation TACL Programming Guide Presents examples of HP Tandem Advanced Command Language (TACL) macros and routines TACL Reference Manual Describes the syntax, operation, and results of all TACL commands, functions, built-in fu
General Syntax Notation About This Manual [ ] Brackets. Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list may be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: FC [ num ] [ -num ] [ text ] K [ X | D ] address { } Braces.
Notation for Messages About This Manual Item Spacing. Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: CALL STEPMOM ( process-id ) ; If there is no space between two items, spaces are not permitted. In these examples, there are no spaces permitted between the period and any other items: $process-name.#su-name Line Spacing.
Notation for Messages About This Manual Bold Text. Bold text in an example indicates user input entered at the terminal. For example: ENTER RUN CODE ?123 CODE RECEIVED: 123.00 The user must press the Return key after typing the input. Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned.
Change Bar Notation About This Manual % Percent Sign. A percent sign precedes a number that is not in decimal notation. The % notation precedes an octal number. The %B notation precedes a binary number. The %H notation precedes a hexadecimal number. For example: %005400 %B101111 %H2F P=%p-register E=%e-register Change Bar Notation Change bars are used to indicate substantive differences between this edition of the manual and the preceding edition.
1 NetBatch Introduction This section introduces the NetBatch product: Topic Page Product Overview 1-1 Core Components 1-4 Scheduler Functions 1-6 NetBatch High-PIN Capabilities 1-12 Product Overview NetBatch is an HP NonStop software product that lets your organization automate job scheduling, startup, and management on NonStop systems.
Executor Programs NetBatch Introduction Figure 1-1. A NetBatch Job NetBatch scheduler Executor program process Process Input file Process Process Process VST001.vsd Executor Programs A NetBatch job’s executor program can be any user-written or NonStop program. This flexibility in choosing an executor program has two main benefits: • • Programmers can select the most appropriate executor programs for jobs and not have to learn a special job control language.
ASSIGNs, DEFINEs, and PARAMs NetBatch Introduction ASSIGNs, DEFINEs, and PARAMs The NetBatch scheduler propagates ASSIGNs, DEFINEs, and PARAMs to executorprogram processes through user-defined entities called attachment sets. A single set can supply ASSIGNs, DEFINEs, and PARAMs to many jobs, thus simplifying job setup. Operator Interface The NetBatch operator interface (BATCHCOM) lets you inquire about and manipulate the scheduler, the scheduler’s executors and classes, and attachment sets and jobs.
Core Components NetBatch Introduction Core Components The NetBatch product has five core components: • • • • • A scheduler program (NETBATCH) A command interpreter (BATCHCOM) A calendar generation program (BATCHCAL) An executor program (NBEXEC) A TAL procedure (NB^JOB^SUBMIT) Figure 1-2 on page 1-5 shows the components in a sample NetBatch environment. NETBATCH NETBATCH is the program-file ID of the NetBatch scheduler. The scheduler is a process-pair server that stores job records in its database.
NB^JOB^SUBMIT NetBatch Introduction NB^JOB^SUBMIT NB^JOB^SUBMIT is a TAL procedure defined in the NetBatch library file BATCHLIB. The procedure enables programmatic submission and alteration of jobs from userwritten programs. For more information about NB^JOB^SUBMIT, see the NetBatch Management Programming Manual. Figure 1-2.
Scheduler Functions NetBatch Introduction Scheduler Functions The scheduler is a process-pair server whose functions are to: • • • • Store job records in its database Schedule and start jobs Track and control job execution Record job termination details This subsection expands this definition after describing how the scheduler assigns and controls the flow of jobs to CPUs. CPU Assignment The scheduler assigns jobs to CPUs by means of its classes and executors.
Job Storage NetBatch Introduction until the job finishes. (Stopping an executor prevents jobs from using it to access its CPU.) The number of started executors determines how many jobs can run together. For example, a scheduler with 10 started executors can run up to 10 jobs concurrently. To add executors to a scheduler and display and alter their attributes, use the BATCHCOM commands ADD EXECUTOR, INFO EXECUTOR, and ALTER EXECUTOR.
Job Scheduling and Startup NetBatch Introduction Attribute Function (continued) AFTER, AT, CALENDAR, EVERY, WAIT, LIMIT Schedule a job and specify a time limit HOLD, HOLDAFTER Specify a job’s hold characteristics IFFAILS, RESTART, STALL, STOPON-ABEND Control a job’s behavior on process failure TAPEDRIVES Specifies a job’s tape drives requirements WAITON Specifies a job’s dependencies ATTACHMENT-SET Specifies a job’s ASSIGNs, DEFINEs, and PARAMs DESCRIPTION Describes a job The scheduler let
Job Tracking, Control, and Termination NetBatch Introduction • • • Tape drives are available to the job (if the job has the TAPEDRIVES attribute). The job’s master jobs have released it (if the job has the WAITON attribute). The job has the attribute HOLD OFF. Figure 1-4 on page 1-10 illustrates and describes the algorithm used by the scheduler to select and start jobs. Attachment Sets An attachment set is a group of ASSIGNs, DEFINEs, and PARAMs you can link to jobs by the ATTACHMENT-SET attribute.
Job Tracking, Control, and Termination NetBatch Introduction Figure 1-4. Scheduling Algorithm 1 Begin No 2 Any jobs ready to run? 4 Executor selected? 3 Yes Select next available executor No No No 5 Job from 2 RUNNOW ? Yes 6 Create temporary executor Yes 7 State ON? Yes 8 CLASS * attribute? No No 11 Class selected? 10 Select next class Yes 9 Select job from 2 Yes No 12 INITIATION ON? Yes 13 Select highest pri. job No 14 Job selected? Yes 15 Start job End VST004a.
Job Tracking, Control, and Termination NetBatch Introduction Table 1-1. Scheduling Algorithm Description Item Description 1. Begin. These trigger events make the scheduler start the job selection and startup procedure: • • • • 2.
NetBatch High-PIN Capabilities NetBatch Introduction Table 1-1. Scheduling Algorithm Description Item Description 12. INITIATION ON? If the scheduler selects a class at item 10, it checks if the class’s INITIATION attribute is ON. If so, it goes to item 13. Otherwise, the scheduler returns to item 10. 13. Select highest priority job. 14. Job selected? The scheduler attempts selection of the highest priority job from the class selected at item 10 (not necessarily the job from item 2).
2 Software Installation This section describes how to install NetBatch: Topic Page Installing NetBatch Software—Overview 2-1 Installation Procedure 2-3 Migrating a Scheduler Database 2-7 Note. You need a good working knowledge of NonStop software installation and system generation functions. For information on these topics, see the DSM/SCM User’s Guide and the System Generation Manual. Installing NetBatch Software—Overview To install NetBatch software, the super ID (255,255): 1.
Installation Prerequisites Software Installation Table 2-2.
Installation Procedure Software Installation Table 2-3. NetBatch Installation Prerequisites (page 2 of 2) Prerequisite 9150 DDL data definition language D20 or later 9050 NonStop OS G02.00 or later 0295 ENFORM PLUS G02.00 or later Figure 2-1.
Step 2: Shut Down NETBATCH and Stop Its Processes Software Installation Step 2: Shut Down NETBATCH and Stop Its Processes 1. Shut down running NETBATCH schedulers, using the BATCHCOM command ABORT SCHEDULER or SHUTDOWN SCHEDULER. Note. Do not use the STOP command to stop a NETBATCH scheduler. STOP acts on the scheduler only and has no effect on processes of jobs the scheduler is controlling. 2. Stop running BATCHCAL, BATCHCOM, BATCHUTL, and NBEXEC processes, using the TACL STOP command.
Step 7: Perform Post-installation Tasks Software Installation Step 7: Perform Post-installation Tasks Perform any post-installation tasks listed in the softdoc’s “Post-Installation Instructions”. Tasks can include creating and binding the NBFLAGS procedure, specifying the library file for NetBatch programs, securing files, and licensing the NETBATCH program file.
Step 7: Perform Post-installation Tasks Software Installation 1. Make a backup copy of BATCHLIB. For example: > FUP DUP $DATA7.TEST.BATCHLIB, $NB.BACKUPS.BATCHLIB FILES DUPLICATED: 1 > 2. Create the NBFLAGS procedure. For example: > TAL; SUPPRESS > INT PROC NBFLAGS; BEGIN RETURN %B1111111111110111; END; > EOF! BINDER - OBJECT FILE BINDER ... Object File \MELBDEV.$DATA7.TEST.OBJECT.
Step 8: Restart Schedulers Software Installation Licensing the NETBATCH Program File The NETBATCH program file is the only file you must license before use (the program contains privileged code). To license the file, use the FUP LICENSE command. For example: > FUP LICENSE $SYSTEM.SYSTEM.NETBATCH Step 8: Restart Schedulers Restart the schedulers shut down in Step 2. This involves cold starting or warm starting the schedulers you shut down at the beginning of the installation procedure.
Step 3: Copy the Database Files to the Target Location Software Installation Step 3: Copy the Database Files to the Target Location Copy the database files to the target location by using the FUP DUP command with the SAVEALL option: > VOLUME $DATA7.SCHD > FILES \MELBDEV.$DATA7.SCHD ATTACH ATTACH0 BATCHCTL CHKQUE CHKQUE0 EXECUTO0 EXECUTOR JOB JOBCLAS0 JOBCLASS LOGAAA NBATTX NBATTX0 > FUP DUP ∗ , \MELRISK.$DATA.SCHD.∗ , SAVEALL WARNING − \MELRISK.$DATA.SCHD.
Step 5: Update Alternate Key File References Software Installation Step 5: Update Alternate Key File References Update the alternate key file references of these migrated files by using the FUP ALTER command: ATTACH, CHKQUE, EXECUTOR, JOBCLASS, and NBATTX.
Step 7: Verify and Alter Attributes Software Installation NetBatch Manual—522460-004 2- 10
3 Scheduler Planning, Configuration, and Management This section describes how to work with the scheduler: Topic Page Planning Schedulers 3-1 Starting Schedulers 3-9 Configuring Schedulers 3-23 Managing Schedulers 3-29 Planning Schedulers Planning your organization’s schedulers is a three-stage process that involves: Task 1. Compile Job Information 3-1 Task 2. Determine Scheduler Numbers and Attributes 3-2 Task 3. Establish Class and Executor Configurations 3-6 Task 1.
Scheduler Planning, Configuration, and Management Task 2. Determine Scheduler Numbers and Attributes Information required Function Tape drives Specifies the number of tape drives required by the job Output file Specifies the name of the job’s output file Duration Specifies how long the job takes to run Frequency Specifies how often the job runs Figure 3-1 records information about jobs in a sample three-node system. It is the basis of the examples in this subsection. Figure 3-1.
Scheduler Planning, Configuration, and Management Task 2. Determine Scheduler Numbers and Attributes General Rule As a rule, plan no more than one scheduler for each node where you want jobs placed under NetBatch control. A single scheduler on a node should be enough to satisfy users’ requirements on that node.
Scheduler Planning, Configuration, and Management Task 2. Determine Scheduler Numbers and Attributes The attributes’ values can be scheduler-assigned defaults, or values you specify during scheduler startup (by means of the ADD SCHEDULER command) or configuration (by means of the ALTER SCHEDULER command). For more information, see Section 7, Attributes. Table 3-1.
Scheduler Planning, Configuration, and Management Task 2. Determine Scheduler Numbers and Attributes Table 3-1.
Scheduler Planning, Configuration, and Management Task 3. Establish Class and Executor Configurations Task 3. Establish Class and Executor Configurations Determine the class and executor configurations of each scheduler. Establishing Class Configurations Classes function primarily as CPU resource managers. Through their INITIATION attributes, you can control the flow of jobs to executors and therefore to those executors’ CPUs. Thus, classes help you balance job workload across all CPUs in your system.
Scheduler Planning, Configuration, and Management Task 3. Establish Class and Executor Configurations Executor Numbers The number of executors you plan depends on the number of CPUs on the scheduler’s node and on your jobs’ CPU and I/O resource requirements. HP recommends four executors per CPU: • • • One executor for classes that group jobs by function or purpose. One executor for classes whose jobs are CPU-bound. Two executors for classes whose jobs are I/O-bound.
Scheduler Planning, Configuration, and Management Task 3. Establish Class and Executor Configurations Example Figure 3-3 shows an example of a table showing the classes and executors planned for a scheduler running on a four-CPU node. As well as showing the executors assigned to each CPU, the figure illustrates class distribution among those executors. For example, executors E1, E4, E8, and E12 have classes C1 through C4 assigned to them in different order.
Scheduler Planning, Configuration, and Management Starting Schedulers Starting Schedulers Topic Page Overview 3-9 Running NETBATCH 3-10 Cold Starting a Scheduler 3-15 Warm Starting a Scheduler 3-18 Warm-Start Events 3-21 Overview Scheduler startup is a task for NetBatch supervisors (users with execute access to the NETBATCH program file).
Scheduler Planning, Configuration, and Management Running NETBATCH Scheduler altered 26> BATCHCOM $WXYZ; START SCHEDULER Scheduler started For complete warm-start instructions, see Warm Starting a Scheduler on page 3-18.
Scheduler Planning, Configuration, and Management • Running NETBATCH For an implicit RUN command, enter the NETBATCH program file name only. If you enter a partially qualified file name, the TACL program searches for the file in the subvolumes specified by the TACL #PMSEARCHLIST variable. schd specifies the name of the scheduler process. The name can contain from one to four alphanumeric characters (preceded by the dollar sign), of which the first must be alphabetic.
Scheduler Planning, Configuration, and Management Running NETBATCH Note. BATCHCOM searches for a scheduler named $ZBAT when a RUN BATCHCOM command does not specify a scheduler. For this reason, consider using $ZBAT as a scheduler name.
Scheduler Planning, Configuration, and Management Running NETBATCH jobrun-database-subvol specifies the location of the JOBRUN database, dictionary, and compiled query files. Examples • To run NETBATCH, creating scheduler $ZBAT’s primary process in CPU 3, with the scheduler’s database $DATA7.ZBAT: NETBATCH /NAME $ZBAT, NOWAIT, CPU 3/ $DATA7.
Scheduler Planning, Configuration, and Management Running NETBATCH Table 3-2. High PIN Capabilities in NETBATCH Feature Implementation Comments Can have a high PIN creator? Yes None Can communicate with high PIN requests? Yes None Defaults to run at a high PIN? Yes A NETBATCH process runs at a high PIN by default when all these conditions exist: • • • • The operating system on the node where the process runs is a D-series system configured to handle high PIN processes.
Scheduler Planning, Configuration, and Management Cold Starting a Scheduler Cold Starting a Scheduler Step 1: Log On as a NetBatch Supervisor You must be a NetBatch supervisor to run NETBATCH and to use the ADD SCHEDULER and START SCHEDULER commands. Users who are not NetBatch supervisors cannot perform cold-start tasks. > LOGON 255,205, password > PPD $ZBAT (Process does not exist) > FILEINFO $NB.ZBAT.* No files match \MELBDEV.$NB.ZBAT.
Scheduler Planning, Configuration, and Management Cold Starting a Scheduler includes the ! parameter.) For a list of the files purged, see the description of the ! parameter on page 3-12. • • • Creates and opens the scheduler’s configuration file BATCHCTL in the database subvolume specified in the RUN NETBATCH command. The file contains default values for the scheduler’s attributes, as listed in Table 3-1 on page 3-4. Creates and opens the scheduler’s log file.
Scheduler Planning, Configuration, and Management LOGAAA O NBATTX NBATTX0 98> Cold Starting a Scheduler 847 847 847 924… 255,205 "NNNC" 50 0 … 255,255 "OOOO" 16 0 … 255,255 "OOOO" 16 100 16 16 The ADD SCHEDULER command creates and initializes some files in the scheduler’s database subvolume. For descriptions of the files, see ADD SCHEDULER Command on page 6-46.
Scheduler Planning, Configuration, and Management Warm Starting a Scheduler Warm Starting a Scheduler This subsection describes the steps in the warm-start procedure. For information on processing that occurs during a scheduler warm start, see Warm-Start Events on page 3-21. Step 1: Log On as a NetBatch Supervisor You must be a NetBatch supervisor to run NETBATCH and to use the START SCHEDULER command. Users who are not NetBatch supervisors cannot perform warm-start tasks.
Scheduler Planning, Configuration, and Management Warm Starting a Scheduler terminates at the break with a “file not found” error instead of continuing through subsequent files. > NETBATCH /NAME $ZBAT, NOWAIT, CPU 1, PRI 150/ $DATA7.ZBAT *WARNING* Scheduler log-file chaining lost: Error 11. Continuing … > PPD $ZBAT Name Primary Backup Ancestor $ZBAT 1,52 $Z161 > FILEINFO $DATA7.ZBAT.* $DATA7.
Scheduler Planning, Configuration, and Management • Warm Starting a Scheduler To specify another log file instead of accepting the default, add map DEFINE =_ZBAT_LOG_FILE to the TACL environment before running NETBATCH. For example: > ADD DEFINE =_ZBAT_LOG_FILE, CLASS MAP, FILE $ZTN0.#PTY6 > INFO DEFINE =_ZBAT_LOG_FILE Define Name =_ZBAT_LOG_FILE CLASS MAP FILE \MELBDEV.$ZTN0.#PTY6 > NETBATCH /NAME $ZBAT, NOWAIT/ $NB.ZBAT > BATCHCOM $ZBAT; STATUS SCHEDULER SCHEDULER STATUS Process : \MELBDEV.
Scheduler Planning, Configuration, and Management Warm-Start Events NBATTX O 847 0 18-Oct-94 13:57:38 255,255 … NBATTX0 O 847 0 18-Oct-94 13:57:38 255,255 … The START SCHEDULER command prepares the scheduler for use. The command creates the scheduler’s backup process (in the CPU specified by the scheduler’s BACKUPCPU attribute) and opens the database files. Warm-Start Events When a scheduler warm starts, these significant events occur: 1.
Scheduler Planning, Configuration, and Management Warm-Start Events 4. After stopping jobs, the scheduler reviews its executors and deletes those whose state was DELETE when the scheduler stopped. The scheduler then updates each executor’s state: State when scheduler stopped State after warm start ACTIVE ON or DOWN (depending on CPU availablity) DELETE NA (executor deleted) DOWN ON or DOWN (depending on CPU availablity) OFF OFF ON ON or DOWN (depending on CPU availablity) STOP OFF 5.
Scheduler Planning, Configuration, and Management Configuring Schedulers Configuring Schedulers Scheduler configuration is a task for a NetBatch supervisor to perform after a scheduler cold start. Configuration involves: • • • Specifying the scheduler’s attributes Adding the scheduler’s classes Adding and starting the scheduler’s executors Scheduler Configuration Commands This table lists the BATCHCOM commands to configure a scheduler.
Scheduler Planning, Configuration, and Management Scheduler Configuration Procedure Scheduler altered 2} Step 4: Add the Scheduler’s Attributes and Specify Their INITIATION Attributes Add the scheduler’s classes and specify their INITIATION attributes by using the ADD CLASS command. (Classes adopt the attribute INITIATION ON unless specified otherwise.
Scheduler Planning, Configuration, and Management Displaying Scheduler Configuration Displaying Scheduler Configuration You can display a scheduler’s configuration, its attributes, and the attributes of its classes and executors by using these commands. For information about the syntax, operation, and results of the commands, see Section 6, Commands and Managing Schedulers on page 3-29.
Scheduler Planning, Configuration, and Management Automating Scheduler Configuration default-executor-program: \MELBDEV.$SYSTEM.SYSTEM.TACL max-pri: 199 default-pri: 149 max-concurrent-jobs: 500,500 default-selpri: 3 default-maxprintlines: None default-maxprintpages: None tapedrives: 3 default-out: \MELBDEV.$S.
Scheduler Planning, Configuration, and Management Automating Scheduler Configuration Using EDIT to Create a Scheduler Configuration File Step 1: Create and Open a File for the Scheduler’s Configuration Commands Create and open a file for the scheduler’s configuration commands by using the EDIT program: 12> EDIT SCHDCONF ! CURRENT FILE IS $DATA7.SCHD.
Scheduler Planning, Configuration, and Management Automating Scheduler Configuration 1 ASSUME SCHEDULER 2 RESET 3 ALTER, BACKUPCPU 1,2 4 ALTER, AT-ALLOWED OFF 5 ALTER, SUBMIT-ALLOWED ON 6 ALTER, INITIATION ON 7 ALTER, DEFAULT-EXECUTOR-PROGRAM \MELBDEV.$SYSTEM.SYSTEM.
Scheduler Planning, Configuration, and Management Managing Schedulers Managing Schedulers This subsection provides instructions for various scheduler management tasks: Topic Page Determining Whether a Scheduler Is Running 3-29 Displaying Scheduler, Executor, and Class Status 3-29 Altering Executor and Class Attributes 3-33 Stopping and Restarting Executors 3-34 Deleting Executors and Classes 3-35 Dealing With Scheduler Log Files 3-38 Enabling and Disabling EMS Event-Message Generation 3-44
Scheduler Planning, Configuration, and Management • • Displaying Scheduler, Executor, and Class Status A count of the scheduler’s executors, classes, and jobs by state The number of active and suspended job processes, configured and in-use tape drives, and attachment sets For example: 1} STATUS SCHEDULER SCHEDULER STATUS Process : \MELBDEV.$NBAT Primary : 0,263 Backup : 1,264 Database: \MELBDEV.$NB.NBAT Logfile : \MELBDEV.$NB.NBAT.
Scheduler Planning, Configuration, and Management Displaying Scheduler, Executor, and Class Status Executor States This table lists and describes executor states. For more information on the states, see STATUS EXECUTOR Command on page 6-163. State Description ACTIVE The executor is in use by a job. DELETE The executor is in use by a job. When the job finishes, the scheduler deletes the executor. DOWN The executor is not available for use because its CPU is down.
Scheduler Planning, Configuration, and Management Displaying Scheduler, Executor, and Class Status when one of the scheduler’s processes stops or during scheduler startup).
Scheduler Planning, Configuration, and Management Altering Executor and Class Attributes Name Primary Backup Ancestor $ZBAT 3,269 0,268 $C8 > BATCHCOM $ZBAT; SHUTDOWN SCHEDULER Scheduler shutting down > NETBATCH /NAME $ZBAT, NOWAIT/ $DATA7.
Scheduler Planning, Configuration, and Management Stopping and Restarting Executors Figure 3-4. Example of ALTER EXECUTOR Command Executor and class configuration before ALTER EXECUTOR command: CPU 0 CPU 1 Executor and class configuration after command: ALTER EXECUTOR EX1, CLASS (CL1, CL2), CPU 1 CPU 0 Executor EX1 Class CL1 Job J1 Job J2 CPU 1 Executor EX1 Class CL2 Job J3 Job J4 Class CL1 Job J1 Job J2 Class CL2 Job J3 Job J4 VST006.
Scheduler Planning, Configuration, and Management Deleting Executors and Classes Stopping Executors The STOP EXECUTOR command stops an executor whose state is ACTIVE or ON.
Scheduler Planning, Configuration, and Management • • Deleting Executors and Classes DELETE EXECUTOR DELETE CLASS Deleting Executors The DELETE EXECUTOR command deletes an executor from a scheduler. For example: 4} DELETE EXECUTOR EXEC1 Executor EXEC1 deleted After deleting an executor, reassign classes that were unique to it to other executors. Otherwise, the scheduler never scans the classes for jobs.
Scheduler Planning, Configuration, and Management Deleting Executors and Classes Deleting Classes The DELETE CLASS command deletes a class from a scheduler. For example: 12} DELETE CLASS ENFORM-JOBS Class ENFORM-JOBS deleted The scheduler disallows deletion of a class assigned to an executor. To delete such a class, dissociate it from the executor by using the ALTER EXECUTOR command before the DELETE CLASS command. For example: 33} DELETE CLASS CL2 2104-E CLASS CL2 is in use by one or more executors.
Scheduler Planning, Configuration, and Management Dealing With Scheduler Log Files Dealing With Scheduler Log Files The scheduler records in a log file details of events that occur while it is running. You can use the log, for example, for troubleshooting purposes. The log can be a device, a process, or any type of unstructured disk file except an EDIT file. Figure 3-7 on page 3-38 shows a commented example of a scheduler log file.
Scheduler Planning, Configuration, and Management Dealing With Scheduler Log Files Creating and Opening a Scheduler Log File The scheduler opens its log file when you run the NETBATCH program during scheduler startup. For more information, see Warm Starting a Scheduler on page 3-18.
Scheduler Planning, Configuration, and Management Dealing With Scheduler Log Files You also can use the EDIT program to list a closed log file’s contents after putting the contents into an EDIT file. For example, this command creates file LOGTEMP, puts the contents of LOGADQ into that file, then lists LOGTEMP: > EDIT; GET LOGADQ PUT LOGTEMP; LIST ALL For information about the FUP COPY command, see the File Utility Program (FUP) Reference Manual.
Scheduler Planning, Configuration, and Management Dealing With Scheduler Log Files Record 2: For example, the SWITCHLOG event will be logged as Record 1: 06APR06 12:41:42 LOG SWITCHLOG \NODE1.$DSMSCM.S2345678.LOGAAA TO \NODE1.$DSMSCM.S2345678.LOGAAB Record 2: 06APR06 12:41:42 U_255,255 H_\NODE1.$ZTNT.#PT1RBGU Event Keywords Table 3-3. Scheduler Log File Keywords (page 1 of 3) Keyword Description Example A’VATE Suspended job reactivated by ACTIVATE JOB command.
Scheduler Planning, Configuration, and Management Dealing With Scheduler Log Files Table 3-3. Scheduler Log File Keywords (page 2 of 3) Keyword Description Example COLD Scheduler cold started. COLD Purge any existing scheduler database files CREATE Primary or backup scheduler process created. CREATE Scheduler Backup \MELBDEV.$SCHD CPU 2 U_255,255 H_\MELBDEV.$T4.#A DELETE Object deleted in response to user request. DELETE JOB XYZ J_1 U_255,255 H_\MELBDEV.$T4.
Scheduler Planning, Configuration, and Management Dealing With Scheduler Log Files Table 3-3. Scheduler Log File Keywords (page 3 of 3) Keyword Description Example STOP STOP system message received from process specified in event. STOP CC_6 by \MELBDEV.$SCHD:23826361 U_255,255 J_1 \MELBDEV.$X206:23826617 STOPT STOP system message text. STOPT Message text for J_2 \MELBDEV.$X284:25137081 SUSPND SUSPEND JOB command executed. SUSPND JOB XYZ J_1 U_255,255 H_\MELBDEV.$T4.
Scheduler Planning, Configuration, and Management Enabling and Disabling EMS Event-Message Generation Table 3-4. Scheduler Log File Logging Formats (page 2 of 2) Logging Format Description Example T_ cpu-time Supplies the CPU time taken by a job in hours, minutes, seconds, and microseconds. T_0:0:12:163 U_ group-ID, user-ID Identifies the user making the request. U_205,70 \ node.$: CPU: PIN: sequence-number Identifies an unnamed process. \MELBDEV.
Scheduler Planning, Configuration, and Management Stopping a Scheduler To disable event-message generation, use the ALTER SCHEDULER command to set the EMS attribute to OFF. For more information, see EMS Scheduler Attribute on page 7-54. Stopping a Scheduler NetBatch supervisors can stop (shut down) a scheduler by using either of these BATCHCOM commands: Command Function ABORT SCHEDULER Stops all executing and suspended processes associated with jobs, then stops the scheduler.
Scheduler Planning, Configuration, and Management Stopping a Scheduler 1. Establish the cause of the shutdown. Use the scheduler’s last log file to help. 2. Correct the cause of the shutdown as necessary. 3. Warm start the scheduler. See Warm Starting a Scheduler on page 3-18.
4 Job Planning, Submission, and Management This section describes how to work with NetBatch jobs: Topic Page Planning Jobs 4-1 Submitting Jobs 4-13 Managing Jobs 4-42 Planning Jobs This subsection outlines a job planning procedure that lets your organization take advantage of NetBatch job management facilities.
Planning Procedure Job Planning, Submission, and Management Table 4-1.
Planning Procedure Job Planning, Submission, and Management Figure 4-1. Sample Programs and Run Environments Diagram F Monthly executive report Monthly exec. report program C Application database Database update program G A Log processing program Calendar file Daily executive report Update report Restart file Daily transaction log E Daily exec.
Planning Procedure Job Planning, Submission, and Management Figure 4-2 shows the job names assigned to the programs from the previous figure and the dependencies between those programs. Figure 4-2. Sample Job Dependencies Diagram F Monthly exec. report program C Database update program Job name: TLOG-F Waits on: TLOG-C Releases: N.A. E Daily exec. report program Job name: TLOG-C Waits on: TLOG-A Releases: TLOG-E, TLOG-F A Log processing program Job name: TLOG-A Waits on: N.A.
Planning Procedure Job Planning, Submission, and Management attributes. (For a decision chart to help you determine the values of these attributes, see Controlling a Job’s Behavior on Process Failure on page 4-28.) For an example of a job-recovery strategy, consider the transaction log processing example from the previous steps. The recovery strategy for this application is to reduce operator intervention by partially automating job recovery and restart functions.
Planning Procedure Job Planning, Submission, and Management Step 5: Create Job Planning Table Create a table that lists the jobs identified at Step 3 and specifies their attributes. For information about job attributes, see Submitting a Job With the SUBMIT JOB Command on page 4-13. The table can help you when planning your organization’s schedulers (see Section 3, Scheduler Planning, Configuration, and Management) and submitting the jobs.
Creating a Job Input File Job Planning, Submission, and Management Creating a Job Input File A job’s input file contains the statements executed by the job’s executor program. (For example, if a TACL process is the executor program, the file contains TACL commands; if the COBOL compiler is the executor program, the file contains the program source code.) The syntax of the statements in the file must follow the syntax rules of the executor program.
Job Planning, Submission, and Management Using Completion Codes to Test Process Termination Status Table 4-3 lists and describes the standard completion codes used by NonStop system language compilers and other HP products. For more information about the codes, see the Guardian Procedure Calls Reference Manual. Table 4-3. Completion Codes Code Description -3 The process terminated itself but passed bad parameters to the ABEND, STOP, or PROCESS_DELETE_ system procedure.
Job Planning, Submission, and Management Using Completion Codes to Test Process Termination Status Figure 4-5. Sample #CASE and #IF Constructs for Completion Code Testing … [#CASE [:_COMPLETION:COMPLETIONCODE] |0| #OUTPUT text |1| #OUTPUT text |2| #OUTPUT text |OTHERWISE| #OUTPUT text ] [#IF [#COMPUTE :_COMPLETION:COMPLETIONCODE > 0] |THEN| non-zero-branch |ELSE| zero-branch ] VST119.vsd Figure 4-6 shows the input file of a job that compiles a program.
Identifying Processes of a Job Job Planning, Submission, and Management Identifying Processes of a Job When a scheduler starts a job with the attribute JOBID-ZERO OFF: 1. It tags the job’s executor-program process with a unique identifier called a GMOMJOBID. This identifier contains the scheduler’s process name (that is, the name of the job’s ancestor process, or GMOM) and the job’s number (JOBID); for example, $ZBAT.278. 2. The executor-program process propagates the GMOMJOBID to its child processes.
Identifying Processes of a Job Job Planning, Submission, and Management Pid: 1,78 ($Y) Primary GMOMJOBID: $ZBAT.661 For more information about the STATUS command, see the TACL Reference Manual. Dissociating a Process From a Job In some cases, you might want to prevent a process from receiving its creator’s GMOMJOBID so the process executes outside scheduler control. For example, you might want a NOWAIT Pathway process dissociated from the job that starts it.
Job Planning, Submission, and Management ZBAT:JOBINFO Dissociating a Job From the Scheduler To prevent the scheduler from assigning a GMOMJOBID to a job’s executor-program process, submit the job with the attribute JOBID-ZERO ON. This attribute dissociates the job completely from the scheduler.
Job Planning, Submission, and Management Submitting Jobs Submitting Jobs To submit jobs to a NetBatch scheduler, use: • • The BATCHCOM command SUBMIT JOB The NetBatch-Plus application You also can submit jobs programmatically from user-written programs.
Job Planning, Submission, and Management Submitting a Job With the SUBMIT JOB Command Examples • The SUBMIT JOB command in this example submits a job named DAILY-BACKUP. The job’s attributes nominate its run time, class, and executor program, its input and output files, and its tape drives requirements. The example also shows the command response, which contains the scheduler-assigned job number. 2} SUBMIT JOB DAILY-BACKUP, EVERY 1 DAYS, AFTER 18:00, CLASS OPERATIONS, EXECUTOR-PROGRAM BACKUP, IN $NB.
Job Planning, Submission, and Management Submitting a Job With the SUBMIT JOB Command Table 4-4. Job Attributes (page 1 of 4) Attribute Function Default Value AFTER Specifies the date and time after which a job becomes eligible for execution. The attribute also lets you change a nonexecuting job’s AT attribute to AFTER. No AFTER attribute. AT Specifies the date and time at which the scheduler is to create a temporary executor for and execute a job. No AT attribute.
Job Planning, Submission, and Management Submitting a Job With the SUBMIT JOB Command Table 4-4. Job Attributes (page 2 of 4) Attribute Function Default Value IFFAILS Determines whether the scheduler reschedules a recurrent job (a job that has the CALENDAR or EVERY attribute) that fails during execution. Works in combination with the job’s RESTART, STALL, and STOP-ON-ABEND attributes. No IFFAILS attribute. IN Specifies the name of a job’s input file. No IN attribute.
Job Planning, Submission, and Management Submitting a Job With the SUBMIT JOB Command Table 4-4. Job Attributes (page 3 of 4) Attribute Function Default Value PFS Specifies the size in bytes of a job’s executor-program process file segment (PFS). No PFS attribute. Executor program has PFS size specified in program. PRI Specifies the execution priority of a job’s executor-program process. DEFAULT-PRI scheduler attribute.
Job Planning, Submission, and Management Submitting a Job With the SUBMIT JOB Command Table 4-4. Job Attributes (page 4 of 4) Attribute Function Default Value SWAP Specifies the name of the swap file for the user data stack segment of a job’s executorprogram process. No SWAP attribute. Swap file created on volume specified by SWAP attribute of DEFINE =_DEFAULTS. If DEFINE does not have SWAP attribute, volume selected by operating system.
Job Planning, Submission, and Management Specifying a Job’s Class and Selection Priority highpin: On submit: 20OCT94 15:51:26 alter: 20OCT94 15:51:27 user: 255,205 next-runtime: 20OCT94 23:30:00 This command displays only specified attributes of job COBOL-COMPILE: 20} INFO JOB COBOL-COMPILE, IN, OUT, EXECUTOR-PROGRAM, PRI, SELPRI, CLASS JOB ATTRIBUTES for COBOL-COMPILE jobnumber: 6 in: \DEV.$DATA6.DEV.MYPROG out: \DEV.$S.#COBOL executor-program: \DEV.$SYSTEM.SYSTEM.
Specifying a Job’s Executor Program and the Program’s Run Options and Parameters Job Planning, Submission, and Management 483 Q 255,255 484 R 255,255 86} STATUS JOB *, SELPRI JOB JOBNAME USERID ---- ---------------- ------482 P 255,255 483 Q 255,255 87} STATUS JOB *, SELPRI JOB JOBNAME USERID ---- ---------------- ------482 P 255,255 88} STATUS JOB *, SELPRI 2117-I No JOB selected 4 7 READY EXECUTING DEFAULT DEFAULT SEL STATE CLASSNAME ---- ----------- --------1 READY DEFAULT 4 EXECUTING DEFAULT SEL S
Job Planning, Submission, and Management Specifying a Job’s Input File, Defaults, and PURGEIN-FILE Attribute > STATUS *, GMOMJOBID $SCHD.8 Process Pri … Program file Hometerm $Z227 0,42 180 … $SYSTEM.SYS00.
Job Planning, Submission, and Management Specifying a Job’s Output File, Maximum Print Lines or Maximum Print Pages, and Log File Specifying a Job’s Output File, Maximum Print Lines or Maximum Print Pages, and Log File The OUT attribute specifies a job’s output file, which collects data the job produces. If the file is a spooler collector process, the MAXPRINTLINES and MAXPRINTPAGES attributes specify the spooler job’s maximum print lines or maximum print pages.
Job Planning, Submission, and Management Scheduling a Job Scheduling a Job The attributes AFTER, AT, CALENDAR, EVERY, and WAIT are timing attributes that specify when a job runs and its run frequency. (AFTER, AT, and WAIT are mutually exclusive, as are CALENDAR and EVERY.) The LIMIT attribute specifies an execution time limit for the job. A job with the CALENDAR or EVERY attribute is a recurrent job because the scheduler automatically reschedules the job after it runs.
Job Planning, Submission, and Management Scheduling a Job at-allowed: Off 4} SUBMIT JOB M, AT 19:30 2056-E AT-ALLOWED is currently OFF; submit AFTER time 5} INFO JOB M 2099-E JOB does not exist • This example shows submission of a job with the AT attribute.
Job Planning, Submission, and Management Scheduling a Job Job ZBAT-0013 Jobnumber 13 submitted 19> BATCHCOM $ZBAT; INFO JOB 13, CALENDAR JOB ATTRIBUTES for ZBAT-0013 jobnumber: 13 calendar: \MELBDEV.$NB.MAN14.NOVDATES next-runtime: 01NOV2001 09:00:00 EVERY Attribute The EVERY attribute specifies a regular interval at which the scheduler automatically runs a job. Example This example shows the EVERY attribute specifying an eight-hour execution frequency for a job.
Job Planning, Submission, and Management Specifying a Job’s Hold Characteristics > BATCHCOM $ZBAT; SUBMIT JOB I, WAIT 0:30 Job I job number 715 submitted > BATCHCOM $ZBAT; INFO JOB I, WAIT; STATUS JOB I JOB ATTRIBUTES for I jobnumber: 715 after: 02APR93 16:37:20 next-runtime: 02APR93 16:37:20 JOB JOBNAME USERID LOG STATE CLASSNAME ---- ---------------- ------- ---- ----------- --------715 I 255,205 16:37:20 DEFAULT LIMIT Attribute The LIMIT attribute specifies an execution time limit for a job.
Job Planning, Submission, and Management Specifying a Job’s Hold Characteristics JOB JOBNAME USERID LOG STATE CLASSNAME ---- ---------------- ------- ---- ----------469 C 255,255 1:Hold DEFAULT 12} INFO JOB C, HOLD, HOLDAFTER JOB ATTRIBUTES for C jobnumber: 469 hold: On holdafter: On 13} ALTER JOB C, HOLD OFF Job C job number 469 altered 14} STATUS JOB C JOB JOBNAME USERID LOG STATE ---- ---------------- ------- ---- ----------469 C 255,255 212 EXECUTING 15} INFO JOB C, HOLD, HOLDAFTER JOB ATTRIBUTES for
Controlling a Job’s Behavior on Process Failure Job Planning, Submission, and Management Controlling a Job’s Behavior on Process Failure The IFFAILS, RESTART, STALL, and STOP-ON-ABEND attributes determine how the scheduler treats a job when a process of the job fails. Table 4-5 shows the effect on a job’s state of all combinations of the attributes. Table 4-5.
Controlling a Job’s Behavior on Process Failure Job Planning, Submission, and Management Determining a Job’s IFFAILS, RESTART, STALL, and STOPON-ABEND Attributes Figure 4-9 shows a decision chart that can help you determine the values of your jobs’ IFFAILS, RESTART, STALL, and STOP-ON-ABEND attributes. For more information on the attributes, see Section 7, Attributes. Figure 4-9.
Job Planning, Submission, and Management Specifying a Job’s Tape Drives Requirements Example This example shows the effect of the IFFAILS, RESTART, STALL, and STOP-ONABEND attributes on two recurrent jobs whose CPU fails. The jobs have the same RESTART, STALL, and STOP-ON-ABEND attributes, but different IFFAILS attributes. Job A has the IFFAILS OFF attribute, so the scheduler puts the job in the SPECIAL-6 state after failure.
Job Planning, Submission, and Management Specifying a Job’s Dependencies scheduler. Job O waits to run until job N finishes, because not enough drives are available until then. 10} STATUS SCHEDULER . . … TAPEDRIVES … … ------------- … … CONFIGURED 3 … … IN USE 0 … . . 11} SUBMIT JOB N, TAPEDRIVES 2 Job N job number 720 submitted 12} STATUS SCHEDULER . . … TAPEDRIVES … … ------------- … … CONFIGURED 3 … … IN USE 2 … . .
Job Planning, Submission, and Management Specifying a Job’s Dependencies jobnumber: 20 waiton: MASTER-JOB-1, Not Released MASTER-JOB-2, Not Released 14} STATUS JOB 20 JOB JOBNAME USERID LOG STATE CLASSNAME ---- ---------------- ------- ---- ----------- --------20 DEPENDENT-JOB 255,205 EVENT DEFAULT Releasing a Dependent Job A dependent job does not run until released by all its masters.
Job Planning, Submission, and Management Specifying a Job’s Dependencies error causes the scheduler to log an error or warning number in the master job’s executor-program output file when a release of a dependent job is unsuccessful. The NetBatch message corresponding to the number indicates the reason the release was unsuccessful. (For example, error 2099––“job does not exist”––would appear in the output file if job-name-range specified a nonexistent job.
Job Planning, Submission, and Management Specifying a Job’s ASSIGNs, DEFINEs, and PARAMs Examples • This example shows submission of a TACL master job that invokes the ZBAT:RELEASE macro to release a dependent job. The scheduler flags the dependent job as released by the master job after it executes the master.
Job Planning, Submission, and Management Specifying a Job’s ASSIGNs, DEFINEs, and PARAMs Example This example shows submission of a TACL job whose ATTACHMENT-SET attribute specifies the job’s ASSIGNs, DEFINEs, and PARAMs. The job writes its ASSIGNs, DEFINEs, and PARAMs to an output file to illustrate their propagation by the scheduler. > FUP COPY INFILE ASSIGN INFO DEFINE ** PARAM > BATCHCOM $SCHD; INFO ATTACHMENT-SET (SUPER.FPP)STANDARD, ASSIGN, DEFINE, PARAM ATTACHMENT-SET ATTRIBUTES for (SUPER.
Specifying a Job’s ASSIGNs, DEFINEs, and PARAMs Job Planning, Submission, and Management Table 4-6. Attachment-Set Attributes Attribute Function Default Value ASSIGN Specifies the name and attributes of an ASSIGN. No default. DEFINE Specifies the name and attributes of a DEFINE. DEFINE =_DEFAULTS specifying the node and volume set by the last SET ATTACHMENT-SET (DEFINE =_DEFAULTS, VOLUME …), SYSTEM, or VOLUME command.
Job Planning, Submission, and Management Specifying a Job’s ASSIGNs, DEFINEs, and PARAMs (FPP.MANAGER)ADDRESS (FPP.MANAGER)MAILOUT (FPP.MANAGER)SALES (SUPER.SUPER)Q3-BONUSES (SUPER.FPP)5 None (SUPER.SUPER)6 None Altering Attachment-Set Attributes The ALTER ATTACHMENT-SET command changes attachment-set attributes. In particular, the command lets you: • Add ASSIGNs, DEFINEs, and PARAMs to an attachment set. For example: 34} INFO ATTACHMENT-SET (FPP.
Job Planning, Submission, and Management • Specifying a Job’s ASSIGNs, DEFINEs, and PARAMs Alter SECURITY and TEMPORARY attributes; for example: 57} INFO ATTACHMENT-SET (FPP.MANAGER)SALES, SECURITY, TEMPORARY ATTACHMENT-SET ATTRIBUTES for (FPP.MANAGER)SALES security: "UUUU" temporary: Off 58} ALTER ATTACHMENT-SET (FPP.MANAGER)SALES, SECURITY "GOGO", TEMPORARY ON Attachment-set (FPP.MANAGER)SALES altered 59} INFO ATTACHMENT-SET (FPP.MANAGER)SALES, SECURITY, TEMPORARY ATTACHMENT-SET ATTRIBUTES for (FPP.
Job Planning, Submission, and Management Specifying a Job’s ASSIGNs, DEFINEs, and PARAMs ATTACHMENT-SET ATTRIBUTES for (SUPER.FPP)ADMIN security: "UUUU" temporary: Off attachments: DEFINE =_DEFAULTS, CLASS DEFAULTS, VOLUME $NB.SUPER 60} INFO ATTACHMENT-SET #CURRENT, DETAIL ATTACHMENT-SET ATTRIBUTES for (SUPER.FPP)ADMIN security: "UUUU" temporary: Off attachments: DEFINE =_DEFAULTS, CLASS DEFAULTS, VOLUME $NB.
Job Planning, Submission, and Management • Specifying a Job’s Description Create automatically an attachment set for a job when the job’s ATTACHMENTSET attribute specifies #CURRENT, and #CURRENT has a null value. The set has a scheduler-generated ID and these attributes: Attribute Value ASSIGN ASSIGN attributes from working-attributes set.
Job Planning, Submission, and Management Specifying a Job’s Description Example This example shows the ALTER JOB command adding a description to a job. The percent (%) characters force line breaks. 9} ALTER JOB PAYROLL, DESCRIPTION "--------- Payroll Run ---------% On failure: Check line #7% Restore EMP9% Rerun% See $SDOC.DOCS.
Managing Jobs Job Planning, Submission, and Management Managing Jobs This subsection describes various tasks for managing jobs: Topic Page Displaying Job Status 4-42 Altering Job Attributes 4-44 Overriding Job Dependencies, Timing Attributes, and Selection Priority 4-44 Suspending and Reactivating Job Processes 4-45 Stopping and Deleting Jobs 4-46 Dealing With Job Output 4-47 Displaying Job Status You can display the status of all jobs or specified jobs only by using the STATUS JOB command.
Job Planning, Submission, and Management Displaying Job Status Table 4-7. Job State (page 2 of 2) State Description READY The job is available for execution. RUNNEXT The job was the subject of a RUNNEXT JOB command and runs as soon as an executor associated with its class is available. RUNNOW The job was the subject of a RUNNOW JOB command or has the AT attribute. It is in this state momentarily until execution begins.
Altering Job Attributes Job Planning, Submission, and Management Altering Job Attributes The ALTER JOB command changes a job’s attributes. For example: 3} INFO JOB COBOL-COMPILE, OUT, PRI JOB ATTRIBUTES for COBOL-COMPILE jobnumber: 17 out: \MELBDEV.$S.#COBOL pri: 119 4} ALTER JOB 17, OUT $DATA7.PURGE.CMPL3, PRI 149 Job COBOL-COMPILE Jobnumber 17 altered 5} INFO JOB COBOL-COMPILE, OUT, PRI JOB ATTRIBUTES for COBOL-COMPILE jobnumber: 17 out: \MELBDEV.$DATA7.PURGE.
Job Planning, Submission, and Management Suspending and Reactivating Job Processes 49} STATUS JOB *, SELPRI JOB JOBNAME USERID SEL ---- ---------------- ------- ---758 A 255,205 7 759 B 255,205 6 760 C 255,205 1 50} STATUS JOB *, SELPRI JOB JOBNAME USERID SEL ---- ---------------- ------- ---759 B 255,205 6 760 C 255,205 1 STATE ----------EXECUTING READY RUNNEXT CLASSNAME --------DEFAULT DEFAULT DEFAULT STATE CLASSNAME ----------- --------READY DEFAULT EXECUTING DEFAULT RUNNOW JOB The RUNNOW JOB comma
Job Planning, Submission, and Management Stopping and Deleting Jobs 766 H 205,70 EXECUTING 29> STATUS *, GMOMJOBID $ZBAT.766 Process … $X466 1,51 … 1,52 … 30> BATCHCOM $ZBAT; SUSPEND JOB 766 Job H job number 766 suspended 31> BATCHCOM $ZBAT; STATUS JOB 766 JOB JOBNAME USERID LOG STATE ---- ---------------- ------- ---- ----------766 H 205,70 SUSPENDED 32> STATUS *, GMOMJOBID $ZBAT.766, DETAIL Pid: 1,51 ($X466) Primary Process States: … SUSPENDED GMOMJOBID: $ZBAT.
Job Planning, Submission, and Management Dealing With Job Output 43> BATCHCOM $ZBAT; STATUS JOB 767 JOB JOBNAME USERID LOG STATE CLASSNAME ---- ---------------- ------- ---- ----------- --------767 I 205,70 1:Hold DEFAULT 44> BATCHCOM $ZBAT; DELETE JOB 767 Job I job number 767 deleted 45> BATCHCOM $ZBAT; STATUS JOB 767 2099-E JOB does not exist Dealing With Job Output Job output is data produced by an executing job and written to the output file specified by the job’s OUT attribute.
Dealing With Job Output Job Planning, Submission, and Management Figure 4-11. Sample Job Log File 19MAR93 10:05:14 BEGIN JOB (SUPER.FPP)SPOOLER-CLEANUP E_EX1 L_1192 J_643 U_255,205 19MAR93 10:05:15 UPDATE JOB SPOOLER-CLEANUP J_643 19MAR93 10:05:15 LIST JOB SPOOLER-CLEANUP EXECUTING J_643 19MAR93 10:05:16 START EXECUTOR-PROGRAM U_255,205 J_643 P_TACL \MELBDEV.$Y373:35271353 19MAR93 10:05:34 START U_255,205 J_643 P_SPOOLCOM \MELBDEV.$:1:75:32058040 19MAR93 10:05:36 STOP CC_0 J_643 \MELBDEV.
Dealing With Job Output Job Planning, Submission, and Management Figure 4-12. Example of Executor-Program Output Banner, copyright notice, and process initialization messages of TACL executorprogram process TACL (T9205D10 - 08JUN92), Operating System D10, Release … COPYRIGHT TANDEM COMPUTERS INCORPORATED … CPU 1, process has no backup March 19, 1993 10:05:22 (Invoking $SYSTEM.SYSTEM.TACLLOCL) (Invoking $SYSTEM.NETBATCH.TACLCSTM) Current volume is $DATA7.
Job Planning, Submission, and Management NetBatch Manual—522460-004 4- 50 Dealing With Job Output
5 Run Calendar Generation and Display A run calendar is a disk file generated from user-supplied source data by the BATCHCAL program. It contains a series of dates and times called run times. You can schedule a job to run automatically at those times by using the CALENDAR attribute to assign the file to the job. For more information, see CALENDAR Job Attribute on page 7-25.
Running BATCHCAL Run Calendar Generation and Display 17> BATCHCAL /IN CALFRI95/ NEXT-DATE 1995-01-06 14:30:00 18> BATCHCOM $ZBAT; SUBMIT JOB FIRST-FRIDAY, CALENDAR CALFRI95 Job FIRST-FRIDAY Jobnumber 23 submitted 22> BATCHCOM $ZBAT; INFO JOB 23, AFTER, CALENDAR JOB ATTRIBUTES for FIRST-FRIDAY jobnumber: 23 calendar: \QA.$DATA7.CALFILES.
Running BATCHCAL Run Calendar Generation and Display program expands it by using the current default node, volume, and subvolume names. • For an implicit RUN command, enter the BATCHCAL program-file name only. If you enter a partially qualified file name, the TACL program searches for the file in the subvolumes specified by the TACL #PMSEARCHLIST variable. source-file is the name of an EDIT file (file code 101) containing source data for a BATCHCAL run calendar.
BATCHCAL’s High PIN Capabilities Run Calendar Generation and Display N[EXT-DATE] causes BATCHCAL to display the next run time after the beginning of the month specified by FROM-DATE. If you omit FROM-DATE, BATCHCAL displays the next run time after the current time. (The current time is the system date and time on the node where the BATCHCAL process runs.) S[HOW-DATES] causes BATCHCAL to display run times from the beginning of the month specified by FROM-DATE to the end of the month specified by TO-DATE.
Entering Source Data Run Calendar Generation and Display Table 5-1. High PIN Capabilities in BATCHCAL (page 2 of 2) Feature Implementation Comments Can run at a high PIN? Yes None Can recognize high PIN process IDs? NA None Defaults to run at a high PIN? Yes A BATCHCAL process runs at a high PIN by default when all these conditions exist: • • • • The operating system on the node where the process runs is a D-series system configured to handle high PIN processes.
Formatting Source Data Run Calendar Generation and Display • • The number of source data statements needed to generate the calendar. The minimum number is three—one naming the calendar file, one specifying the default start time, and one specifying a run time or range of run times. The likelihood that you will need to regenerate the calendar in the future (for example, when the calendar expires).
Formatting Source Data Run Calendar Generation and Display [ h] h:[ m] m[:[ s] s] [ h] h is a number in the range 0 through 23 specifying the hour of the day. [ m] m is a number in the range 0 through 59 specifying the minute of the hour. [ s] s is a number in the range 0 through 59 specifying seconds. The default is 0. run-time specifies when a job using the calendar can or cannot run. run-time must be the third noncomment line entered in the EDIT input file or interactively.
Formatting Source Data Run Calendar Generation and Display mmm is a character string specifying the month. The options are: JAN[UARY] APR[IL] JUL[Y] OCT[OBER] FEB[RUARY] MAY AUG[UST] NOV[EMBER] MAR[CH] JUN[E] SEP[TEMBER] DEC[EMBER] * specifies all months. day specifies the day in any of these forms: [ d] d is a number in the range 1 through 31 specifying the day of the month. ddd is a character string specifying the day.
Formatting Source Data Run Calendar Generation and Display [ + | - ] / option [ / option ]… [ time ] + adds the specified run times to the times so far recorded. deletes the specified run times from the times so far recorded. option specifies a run-time frequency. The options are: n specifies a day of the month where n is a number in the range 1 through 31. For example, /1 specifies the first day; /15 specifies the fifteenth day; /31 specifies the last day (not necessarily the thirty-first).
Formatting Source Data Run Calendar Generation and Display mth specifies the first of the month where mth is the first three characters of the month name. For example, /JAN specifies the first of January; /DEC specifies the first of December. You can combine this option with option n to specify a day other than the first of the month. For example, /JAN/18 specifies the eighteenth of January.
Formatting Source Data Run Calendar Generation and Display More examples of option combinations: /M/MON Mondays occurring on the last day of the month and, for a month that does not end on a Monday, the first Monday of these months: 1995-01-02, 1995-02-06, 1995-03-06, 1995-04-03, and 1995-0501 /10/FRI Fridays occurring on the tenth day of the month and, for a month in which no Friday occurs on the tenth day, the first Friday following the tenth day: 1995-01-13, 1995-02-10, 1995-03-10, 1995-04-14, and 1
Formatting Source Data Run Calendar Generation and Display == * The source data in this EDIT file will enable * == * BATCHCAL to generate a run calendar containing * == * run times for weekdays through 1995. * == * The calendar will include special run times for * == * June 30 and December 31 that override the weekday * == * run times where necessary. It also will exclude * == * run times on New Year's Day and Christmas Day. * == ***************************************************** $DATA7.CALFILES.
Using BATCHCAL Commands Run Calendar Generation and Display > BATCHCAL /IN ALLDAYS/ SHOW-DATES \MELBDEV.$DATA7.CALFILES.ALLDAYS 1995-11-01 06:45:00 1995-11-02 06:45:00 1995-11-03 06:45:00 1995-11-04 17:30:00 1995-11-05 17:30:00 . .
HELP Command Run Calendar Generation and Display HELP Command To display information about running the BATCHCAL program and about source data structure and format, use the HELP command.
Generating a Run Calendar During an Interactive BATCHCAL Session Run Calendar Generation and Display Code EOF Last Modification … SRC9303 101 310 22-Dec-92 11:27:24 … 64> Step 3: Generate the Calendar Run the BATCHCAL program, specifying the calendar’s source file as the program’s input file: 64> BATCHCAL /IN SRC9303/ CAL9303 == File ID of run calendar 18:15 == Default start time for jobs 1993 MARCH WEEKDAY == Run daily Mon-Fri at 18:15 1993 MARCH WEEKEND 09:00 == Run Sats and Suns at 09:00 - 1993 MARCH
Displaying Run Times Run Calendar Generation and Display Step 2: Create the Calendar Enter the calendar’s source data at the BATCHCAL prompts, then stop the BATCHCAL program to create the calendar: Note. The data structure and format must conform to the rules in Entering Source Data on page 5-5. 1}CAL9304 == File ID of run calendar 2}10:00 == Default start time for jobs 3}1993 APRIL ∗ == Run daily at 10:00 4}EXIT > FILEINFO $DATA7.
Displaying Run Times in List Form Run Calendar Generation and Display 1993-02-27 12:00:00 1993-02-28 12:00:00 • A run-times chart is a table of all run times for a given month. BATCHCAL displays run times in chart form when you omit the NEXT-DATE and SHOW-DATES program parameters from the RUN BATCHCAL command.
Displaying Run Times in List Form Run Calendar Generation and Display Table 5-2. Displaying Run Times in List Form (page 2 of 2) To display all run times after the current time … BATCHCAL / IN calendarfile /S[HOW-DATES] To display all run times after the beginning of a specified month … BATCHCAL / IN calendarfile / S[HOW-DATES] ; F[ROMDATE] [yy]yy mmm To display all run times in a specified range of months...
Displaying Run Times in Chart Form Run Calendar Generation and Display Displaying Run Times in Chart Form Table 5-3 on page 5-19 lists the procedures for displaying run times in chart form. The examples relate to the calendar generated by this source data: CALQ493 12:00 1993 JULY WEEKDAY 1993 JULY WEEKEND 06:45 1993 AUGUST WEEKDAY 17:45 1993 AUGUST WEEKEND 1993 SEPTEMBER WEEKDAY 22:30 1993 SEPTEMBER WEEKEND 03:15 The BATCHCAL program pauses indefinitely after each month when diplaying time in chart form.
Displaying Run Times in Chart Form Run Calendar Generation and Display Table 5-3. Displaying Run Times in Chart Form (page 2 of 3) To display all run times after the beginning of a specified month...
Displaying Run Times in Chart Form Run Calendar Generation and Display Table 5-3. Displaying Run Times in Chart Form (page 3 of 3) To display all run times in a specified range of months... BATCHCAL / IN calendarfile / F[ROM-DATE] [yy]yy mmm ; T[O-DATE] [yy]yy mmm To display all run times from the current time to the end of a specified month...
Reformatting an Old Calendar File Run Calendar Generation and Display Reformatting an Old Calendar File Versions of the BATCHCAL program from C22 through D21 cannot read calendar files created by earlier versions of the program. An attempt to read such a file fails with this message: Old calendar should be rebuilt or converted by RE-FORMAT To convert an old calendar file to the current format, use the RE-FORMAT program parameter in the RUN BATCHCAL command (see Table 5-4).
6 Commands This section describes how to use BATCHCOM commands: Topic Page Running BATCHCOM 6-1 BATCHCOM’s High PIN Capabilities 6-6 Command Reference Summary 6-11 Command Security 6-23 Command Descriptions 6-28 Running BATCHCOM Use the TACL RUN command to run the BATCHCOM program and start a BATCHCOM session. A session lasts until the program stops.
Considerations Commands subvolume-name specifies the subvolume containing the BATCHCOM program file. The default volume varies, depending on whether the RUN command is explicit or implicit. • • For an explicit RUN command, enter RUN followed by the BATCHCOM program-file name. If you enter a partially qualified file name, the TACL program expands it by using the current default node, volume, and subvolume names. For an implicit RUN command, enter the BATCHCOM program-file name only.
Considerations Commands You can manipulate the set’s contents by using the SET, SHOW, and RESET commands: ° ° ° • SET commands add attributes to or alter the values of attributes in the set. SHOW commands display attributes in the set. RESET commands remove attributes from the set except these defaults: Object Default Attributes ATTACHMENT-SET DEFINE =_DEFAULTS specifying the node and volume set by the last SET ATTACHMENT-SET (DEFINE =_DEFAULTS, VOLUME …), SYSTEM, or VOLUME command.
Considerations Commands subvolume. (This file contains the standard help text supplied with NetBatch software.) When BATCHIMU is not in the program-file subvolume, the help request fails, and BATCHCOM displays a message similar to this: 0011-E File or record does not exist, BATCHIMU Examples • The explicit RUN command in this example starts an interactive BATCHCOM session.
Considerations Commands STTUS JOB * STTUS JOB * ^-0290-E Invalid command • The implicit RUN command in this example causes BATCHCOM to execute the OPEN, SUBMIT JOB, and INFO JOB commands in the file BACKUP: > BATCHCOM /IN BACKUP/ BATCHCOM - T9190D30 … OPEN \MELBQAT.$SCHD NETBATCH SERVER - T9190C23 … Time: 26AUG94 10:29:26 SUBMIT JOB BACKUP, IN $A.OPS.BACKUP, OUT $S.#OPS, AFTER 17:30 Job BACKUP Jobnumber 7 submitted INFO JOB BACKUP JOB ATTRIBUTES for BACKUP jobnumber: 7 volume: $A.
BATCHCOM’s High PIN Capabilities Commands Physical file: $BIG1.OPS.BACKUP > INFO DEFINE ** Define Name =_DEFAULTS CLASS DEFAULTS VOLUME $A.NB > PARAM DEPT .OPERATIONS. SHIFT .DAY. HOURS .0900-1700. > WHO . Current volume: $A.NB . Userid: 133,2 Username: NB.USER Security: "AAAA" > BATCHCOM; SHOW ATTACHMENT-SET; SHOW CLASS; SHOW EXECUTOR; SHOW JOB; SHOW SCHEDULER ATTACHMENT-SET ATTRIBUTES attachments: DEFINE =_DEFAULTS, CLASS DEFAULTS, VOLUME $A.NB ASSIGN BACKUP-FILE, $BIG1.OPS.
Keywords Commands Table 6-1. High PIN Capabilities in BATCHCOM (page 2 of 2) Feature Implementation Comments Can run at a high PIN? Yes None Can recognize high PIN process IDs? Yes None Defaults to run at a high PIN? Yes A BATCHCOM process runs at a high PIN by default when all these conditions exist: • • • • The operating system on the node where the process runs is a D-series system configured to handle high PIN processes.
Keyword Types Commands Command Keywords A command keyword specifies a task BATCHCOM is to perform.
Keyword Abbreviations Commands Attribute Keywords An attribute keyword specifies a characteristic of an attachment set, class, executor, job, or scheduler.
Keyword Abbreviations Commands • • • • • You can abbreviate the object keywords ATTACHMENT-SET, CLASS, EXECUTOR, and SCHEDULER, but only when the preceding keyword is ASSUME. For example, you could abbreviate SCHEDULER to SC in the ASSUME SCHEDULER command (ASSU SC). In the STATUS SCHEDULER command, however, you must enter SCHEDULER in full (S SCHEDULER). You cannot abbreviate the object keyword JOB.
Keyword and Command Aliases Commands Keyword and Command Aliases Aliases exist for some BATCHCOM keywords and commands: Alias Command Comments == (double equals) COMMENT ADD SUBMIT ADD JOB and ADD-ALLOWED are acceptable variants of the SUBMIT JOB command and SUBMITALLOWED scheduler attribute. ADP (abbreviation of ASSIGNs, DEFINEs, PARAMs) ATTACHMENT-SET For example, you could enter the command SHOW ADP instead of SHOW ATTACHMENT-SET.
Attachment-Set Commands Commands Attachment-Set Commands • ADD ATTACHMENT-SET adds attachment sets to a scheduler: A[DD] [ ATTACHMENT-SET ] [ / OU[T] [ file-name ] / ] {( user-ID ) ] attachment-set-name |#CURRENT) } [ , attribute ]… attribute is one of: ( ASSI[GN] ASSIGN-name , ASSIGN-attributes ) ( DEFI[NE] DEFINE-name-1 , [ LIK[E] DEFINE-name-2 , ] [ CLASS DEFINE-class , ] [, DEFINE-attribute [ , DEFINE-attribute ]… ) ( PA[RAM] PARAM-name PARAM-value ) SEC[URITY] " security " TEM[PORARY] {OF[F]|ON) }
Class Commands Commands • RESET ATTACHMENT-SET removes all attachment-set attributes (except DEFINE =_DEFAULTS) from BATCHCOM’s working-attributes set: RESE[T] [ ATTACHMENT-SET ] [ attribute [ , attribute ]… ] For a description of attribute, see INFO ATTACHMENT-SET Command on page 6-99.
Executor Commands Commands • INFO CLASS lists the attributes of classes: I[NFO] [ CLASS ] [ / OU[T] [ file-name ] / ] class-ID [ , O[BEY]-[FORM] ] • RESET CLASS restores the default value of the INITIATION class attribute in BATCHCOM’s working-attributes set: RESE[T] [ CLASS ] • SET CLASS specifies the value of the INITIATION class attribute in BATCHCOM’s working-attributes set: SET [ CLASS ] attribute For a description of attribute, see ADD CLASS Command on page 6-40.
Job Commands Commands attribute is one of: CL[ASS] CP[U] • RESET EXECUTOR removes executor attributes from BATCHCOM’s workingattributes set: RESE[T] [ EXECUTOR ] [ attribute [ , attribute ] ] For a description of attribute, see INFO EXECUTOR Command on page 6-104. • SET EXECUTOR specifies executor attributes in BATCHCOM’s working-attributes set: SET [ EXECUTOR ] [ LIK[E] executor-name , ] attribute [ , attribute ] For a description of attribute, see ADD EXECUTOR Command on page 6-42.
Job Commands Commands { ( [ [NOT] job-ID ‚ ]… [NOT] filter [ ‚ [NOT] filter]… ) { , LIK[E] job-ID-2 [ ‚ attribute ]… } {, attribute [ ‚ attribute ]…} [ { IN } ] [‚ REM[OVE] { J[OB]-L[OG] } ] … [ { LIB } ] For a description of attribute, see SUBMIT JOB Command on page 6-183. For a description of filter, see STATUS JOB Command on page 6-165.
Job Commands Commands SA[VEABEND] SEL[PRI] STAL[L] STARTU[P] S[TOP]-[ON]-[ABEND] SWA[P] TA[PEDRIVES] V[OLUME] WAIT WAITO[N] For a description of filter, see SUSPEND JOB Command on page 6-190.
Job Commands Commands • SET JOB specifies job attributes in BATCHCOM’s working-attributes set: SET [ JOB ] [ LIK[E] job-ID , ] attribute [ , attribute ]… For a description of attribute, see SUBMIT JOB Command on page 6-183.
Job Commands Commands CA[LENDAR] [ file-name ] CL[ASS] class-name DES[CRIPTION] " [ string ] " EV[ERY] [ weeks WEEK[S] ] [ days D[AYS] ] [ hours [ : mins ] [HOURS] ] [ hours H[OURS] [ mins MIN[UTES] ] [ crontab-entry ] E[XECUTOR]-P[ROGRAM] file-name EXT[SWAP] { $volume |file-name } HIG[HPIN] { OF[F] | ON } HOLD { OF[F] | ON } HOLDA[FTER] { OF[F] | ON } IF[FAILS] { OF[F] | ON } IN [ file-name ] J[OB]-L[OG] [ log-file ] J[OBID]-Z[ERO] { OF[F] | ON } LIB [ file-name ] LIM[IT] hours [ : mins ] MAXPRINTL[INES]
Scheduler Commands Commands Scheduler Commands • ABORT SCHEDULER immediately stops all executing and suspended processes associated with jobs and shuts down the scheduler: AB[ORT] [ SCHEDULER ] [ / OU[T] [ file-name ] / ] • ADD SCHEDULER creates and initializes the scheduler’s database during a cold start: A[DD] [ SCHEDULER ] [ / OU[T] [ file-name ] / ] [ , attribute ]… attribute is one of: AT-A[LLOWED] { OF[F] | ON } B[ACKUPCPU] { cpu-number-1 [ ‚ cpu-number-2 ] |*} CAT[CHUP] { OF[F] | ON } D[EFAULT]
Scheduler Commands Commands attribute is one of: AT-A[LLOWED] B[ACKUPCPU] CAT[CHUP] D[EFAULT]-C[LASS] D[EFAULT]-E[XECUTOR]-[PROGRAM] D[EFAULT]-H[IGHPIN] D[EFAULT]-MAXPRINTL[INES] D[EFAULT]-MAXPRINTP[AGES] D[EFAULT]-O[UT] D[EFAULT]-P[RI] D[EFAULT]-SE[LPRI] D[EFAULT]-ST[ALL] D[EFAULT]-[STOP]-[ON]-[ABEND] EM[S] INI[TIATION] LO[CALNAMES] M[AX]-[CONCURRENT]-[JOBS] M[AX]-[PRI] S[UBMIT]-A[LLOWED] TA[PEDRIVES] • OPEN specifies the target scheduler for later commands: OP[EN] [ \node.
Other Commands Commands • START SCHEDULER makes available for use a scheduler you are cold starting or warm starting: START [ SCHEDULER ] [ / OU[T] [ file-name ] / ] • STATUS SCHEDULER displays information about a scheduler: S[TATUS] [ SCHEDULER ] [ / OU[T] [ file-name ] / ] • SWITCHCPU SCHEDULER makes a scheduler’s primary process run in the CPU of its backup process, and the backup process run in the CPU of its primary process: SWITCHC[PU] [ SCHEDULER ] [ / OU[T] [ file-name ] / ] • SWITCHLOG SCH
Command Security Commands • HISTORY displays a specified number of the most recent command lines in BATCHCOM’s history buffer: HIS[TORY] [ / OU[T] [ file-name ] / ] [ num ] • OBEY causes BATCHCOM to execute commands from a specified disk file: O[BEY] file-name • RUN runs a program during a BATCHCOM session: RUN program-file [ / OU[T] [ list-file ] / ] [ param-set ] • SYSTEM specifies the default node for a BATCHCOM session: SY[STEM] [ / OU[T] [ file-name ] / ] [ \node ] • VOLUME specifies the def
Command Security Commands Table 6-2. Command Security (page 1 of 4) Command NetBatch Supervisors Only? ABORT SCHEDULER Yes ACTIVATE JOB No Conditions Page 6-30 NetBatch supervisors can reactivate jobs belonging to any user. 6-32 Users who are not NetBatch supervisors can reactivate any job whose input file is a disk file to which they have write access. If the input file does not exist or is a device or process, only the owner and NetBatch supervisors can reactivate the job.
Command Security Commands Table 6-2. Command Security (page 2 of 4) Command NetBatch Supervisors Only? ASSUME JOB No 6-72 ASSUME SCHEDULER No 6-73 CHANGEUSER No 6-74 COMMENT No 6-76 DELETE ATTACHMENT-SET No Conditions To delete an attachment set, you must have purge access to the set. Page 6-77 To delete ASSIGNs, DEFINEs, and PARAMs from an attachment set, you must have write access to the set.
Command Security Commands Table 6-2. Command Security (page 3 of 4) Command NetBatch Supervisors Only? RELEASE-WAITON No Conditions Page NetBatch supervisors can release dependent jobs belonging to any user. 6-115 Users who are not NetBatch supervisors can release a dependent job whose input file is a disk file to which they have write access. If the input file does not exist or is a device or process, only the owner and NetBatch supervisors can release the job.
Command Security Commands Table 6-2. Command Security (page 4 of 4) Command NetBatch Supervisors Only? Conditions Page START SCHEDULER Yes 6-157 STATUS ATTACHMENT-SET No 6-160 STATUS EXECUTOR No 6-163 STATUS JOB No 6-165 STATUS SCHEDULER No 6-173 STATUS-HISTORY No STOP EXECUTOR Yes STOP JOB No You must have read access to a log file for BATCHCOM to display events from it. 6-175 6-178 NetBatch supervisors can stop jobs belonging to any user.
Command Descriptions Commands Command Descriptions This subsection contains descriptions and examples of the syntax, operation, and results of all BATCHCOM commands.
Wild-Card Characters Commands • • Submit, monitor, control, and maintain jobs: ACTIVATE JOB RUNNOW JOB ALTER JOB SET JOB ASSUME JOB SHOW JOB DELETE JOB STATUS JOB INFO JOB STATUS-HISTORY RELEASE-WAITON STOP JOB RESET JOB SUBMIT JOB RUNNEXT JOB SUSPEND JOB Set current defaults for a BATCHCOM session: SYSTEM • VOLUME Execute commands in a BATCHCOM input file: ALLOW ERRORS OBEY COMMENT • • Manipulate command lines: FC ! HISTORY ? Display help text, change the current user, and en
ABORT SCHEDULER Command Commands For example, *CD* matches strings containing CD (such as ABCDEF, XYZCD, and CD21, but not BC3D or DCA). * by itself matches all strings. ? matches a single character. For example, ABC?? matches five-character strings beginning with ABC (such as ABCDE and ABC12, but not ABCDEF). ABORT SCHEDULER Command To immediately stop all executing and suspended processes associated with jobs and to shut down the scheduler, use the ABORT SCHEDULER command.
ABORT SCHEDULER Command Commands 1. Run the scheduler program NETBATCH. 2. Create and initialize the scheduler’s database by using the ADD SCHEDULER command. 3. Start the scheduler by using the START SCHEDULER command. For more information about scheduler cold-start and warm-start procedures, see Section 3, Scheduler Planning, Configuration, and Management. • You can omit the object keyword SCHEDULER from the ABORT SCHEDULER command only when SCHEDULER is the current assumed object.
ACTIVATE JOB Command Commands FINISH JOB XYZ T_0:0:0:0 J_7 P_DELAY U_255,205 H_\M.$ZTN0.#PTY4 DELETE JOB XYZ J_7 U_255,205 H_\M.$ZTN0.#PTY4 DOSTOP Myself • To warm start a scheduler shut down by the ABORT SCHEDULER command: 14> PPD $ZBAT Name Primary Backup Ancestor $ZBAT 2,37 0,80 $C2 15> BATCHCOM $ZBAT; ABORT SCHEDULER Scheduler aborted 16> PPD $ZBAT (Process does not exist) 17> NETBATCH /NAME $ZBAT, NOWAIT/ $DATA7.
ACTIVATE JOB Command Commands filter specifies one of these job-selection criteria (see STATUS JOB Command on page 6-165): A[TTACHMENT]-S[ET]BBC[( AALVS1([ ( user-ID ) ] attachmentsetID,#CURRENT) ) CL[ASS] class-ID IN file-ID STATE state U[SER] user-ID WAITO[N] master-job Considerations • The ACTIVATE JOB command is available to all users, but: ° ° NetBatch supervisors can reactivate jobs belonging to any user.
ADD ATTACHMENT-SET Command Commands • You can omit the object keyword JOB from the ACTIVATE JOB command only when JOB is the current assumed object. For more information, see ASSUME JOB Command on page 6-72.
ADD ATTACHMENT-SET Command Commands file if the file does not exist. If you specify / OUT / (that is, omit file-name), BATCHCOM suppresses output. user-ID specifies the user ID of the attachment-set owner. (user-ID must be in groupname.user-name or group-ID,user-ID form.) The default is the ID of the current user. attachment-set-name is the name of an attachment set. The name can contain from 1 to 24 letters and numbers.
ADD ATTACHMENT-SET Command Commands Table 6-3. Attachment-Set Defaults (page 2 of 2) Attribute Default Value PARAM No PARAM attribute. SECURITY UUUU. TEMPORARY OFF for attachment sets added by ADD ATTACHMENT-SET commands that specify an ID of attachment-set-name. ON for attachment sets added by ADD ATTACHMENT-SET commands that specify an ID of #CURRENT. Figure 6-1 illustrates the attribute conditions described earlier. Figure 6-1.
ADD ATTACHMENT-SET Command Commands ATTACHMENT-SET commands. BATCHCOM displays an “undefined substitution” message when the variable has a null value: 6} CHANGEUSER NB.USER psswrd 7} RESET ATTACHMENT-SET 8} INFO ATTACHMENT-SET #CURRENT -^-0345E Undefined substitution 9} ADD ATTACHMENT-SET DAYLOG, … Attachment-set (NB.USER)DAYLOG added 10} INFO ATTACHMENT-SET #CURRENT ATTACHMENT-SET ATTRIBUTES for (NB.USER)DAYLOG . . 11} ADD ATTACHMENT-SET #CURRENT, … Attachment-set (NB.
ADD ATTACHMENT-SET Command Commands temporary: Off attachments: DEFINE =OUT, CLASS SPOOL, LOC \A.$S.#DEFAULT DEFINE =_DEFAULTS, CLASS DEFAULTS, VOLUME $A.NB ASSIGN ORDERS-LOG, $A.NB.ORDERS ASSIGN SALES-LOG, $A.NB.SALES PARAM DAY WEDNESDAY 4} ADD ATTACHMENT-SET MARKETING, & }} (ASSIGN STOCK-LOG, $A.NB.STOCK), & }} (DEFINE =OUT, LOC \A.$S.#MRKTNG), (PARAM DAY THURSDAY) Attachment-set (NB.USER)MARKETING added 5} INFO ATTACHMENT-SET MARKETING, DETAIL ATTACHMENT-SET ATTRIBUTES for (NB.
ADD ATTACHMENT-SET Command Commands ASSIGN TIMES-FILE, TIMES PARAM DAY 23 PARAM MONTH JUNE PARAM YEAR 1993 • This example shows the effect of the LIKE qualifier in an ADD ATTACHMENT-SET (DEFINE …) command: 28} ADD ATTACHMENT-SET (SUPER.NB)OUT, & }} (DEFINE =LOC1, CLASS SPOOL, BATCHNAME ACCOUNTS, COPIES 2, FORM INVOICES, HOLDAFTER ON, LOC \MELBDEV.$S.#DEFAULT, MAXPRINTLINES 132, OWNER "205,255", SELPRI 7), & }} (DEFINE =LOC2, LIKE =LOC1, LOC \MELBQAT.$S.
ADD CLASS Command Commands ADD CLASS Command Use the ADD CLASS command to add classes to a scheduler. A[DD] [ CLASS ] [ / OU[T] [ file-name ] / ] class-name [ , attribute ] file-name specifies a command output file. The file can be a device, a process, or a disk file. For a disk file, BATCHCOM appends output if the file exists, but creates an EDIT file if the file does not exist. If you specify / OUT / (that is, omit file-name), BATCHCOM suppresses output. class-name is the name of a class.
ADD CLASS Command Commands scheduler never scans the class for jobs. You cannot assign a class to an executor until you add the class to the scheduler. • • JOBCLASS is an alias of the object keyword CLASS. You can omit the object keyword CLASS from the ADD CLASS command only when CLASS is the current assumed object. For more information, see ASSUME CLASS Command on page 6-70.
ADD EXECUTOR Command Commands ADD EXECUTOR Command Use the ADD EXECUTOR command to add executors to a scheduler. A[DD] [ EXECUTOR ] [ / OU[T] [ file-name ] /] executor-name-1 [ , LIK[E] executor-name-2 ] [ , attribute ]… file-name specifies a command output file. The file can be a device, a process, or a disk file. For a disk file, BATCHCOM appends output if the file exists, but creates an EDIT file if the file does not exist. If you specify / OUT / (that is, omit file-name), BATCHCOM suppresses output.
ADD EXECUTOR Command Commands Table 6-4. Executor Defaults Attributes Default Values CLASS DEFAULT-CLASS scheduler attribute CPU No default Figure 6-3 illustrates some of the attribute conditions. Figure 6-3.
ADD EXECUTOR Command Commands To make the executor available for use by jobs: 36} START EXECUTOR ZBAT-EXEC-0 Executor ZBAT-EXEC-0 started • The ADD EXECUTOR command in this example adds an executor that adopts its CPU attribute from the working-attributes set. The executor’s CLASS attribute comes from the scheduler’s DEFAULT-CLASS attribute. The START EXECUTOR command makes the executor available for use by jobs.
ADD EXECUTOR Command Commands • This example shows the use of the ADD EXECUTOR command’s LIKE qualifier: 37} ADD EXECUTOR EXEC01, CPU 1, CLASS (CL1, CL2, CL3, CL4) Executor EXEC01 added 38} ADD EXECUTOR EXEC02, LIKE EXEC01, CPU 2 Executor EXEC02 added 39} INFO EXECUTOR * EXECUTOR ATTRIBUTES for EXEC01 cpu: 1 classes: CL1 CL2 CL3 CL4 EXECUTOR ATTRIBUTES for EXEC02 cpu: 2 classes: CL1 CL2 CL3 CL4 40} START EXECUTOR * Executor EXEC01 started Executor EXEC02 started • This example shows scheduler log-file
ADD SCHEDULER Command Commands ADD SCHEDULER Command Use the ADD SCHEDULER command in a scheduler cold start to create and initialize the scheduler’s database. Before using the command, run the scheduler program NETBATCH. Afterward, start the scheduler with the START SCHEDULER command. Caution. The ADD SCHEDULER command purges existing scheduler database files (except BATCHCTL and log files) before creating and initializing new files.
ADD SCHEDULER Command Commands Table 6-5. Scheduler Defaults Attribute Default Value AT-ALLOWED OFF BACKUPCPU CPU of scheduler’s primary process CATCHUP ON DEFAULT-CLASS DEFAULT DEFAULT-EXECUTOR-PROGRAM $SYSTEM.SYSTEM.TACL DEFAULT-HIGHPIN OFF DEFAULT-MAXPRINTLINES NONE DEFAULT-MAXPRINTPAGES NONE DEFAULT-OUT $S.
ADD SCHEDULER Command Commands Figure 6-4. Example of Attribute Defaulting-Scheduler RUN NETBATCH /NAME $ZBAT, NOWAIT, CPU 0/ $SYSTEM.ZBAT \DEV \QA + Scheduler defaults Working-attributes set AT-ALLOWED OFF BACKUPCPU 0 CATCHUP ON DEFAULT-CLASS DEFAULT DEFAULT-EXECUTOR-PROGRAM \PROD.$SYSTEM.SYSTEM.TACL DEFAULT-HIGHPIN OFF DEFAULT-MAXPRINTLINES NONE DEFAULT-MAXPRINTPAGES NONE DEFAULT-OUT \PROD.$S.
ADD SCHEDULER Command Commands Table 6-6. Files Created or Initialized by ADD SCHEDULER Command (page 2 of 2) File ID Created? Initialized? Purpose JOB Yes Yes Contains information about jobs and their attributes. JOBCLASS Yes Yes Contains information about classes and their attributes. JOBCLAS0 Yes Yes The JOBCLASS file’s alternate key file. NBATTX Yes Yes Contains information linking attachment sets to jobs. NBATTX0 Yes Yes The NBATTX file’s alternate key file.
ADD SCHEDULER Command Commands JOBCLAS0 847 12288 … JOBCLASS 847 12288 … LOGAAA 847 16104 … NBATTX 847 3072 … NBATTX0 847 3072 … $DATA7 SCHD 73> NETBATCH /NAME $SCHD, NOWAIT/ $DATA7.SCHD ! $DATA7 SCHD 74> FILEINFO $DATA7.SCHD Code EOF … BATCHCTL O 847 552 … LOGAAA 847 16500 … LOGAAB O 847 396 … $DATA7 SCHD 75> BATCHCOM $SCHD; ADD SCHEDULER Scheduler added $DATA7 SCHD 76> FILEINFO $DATA7.
ALLOW ERRORS Command Commands ALLOW ERRORS Command Use the ALLOW ERRORS command to specify the number of errors allowed during execution of commands contained in a BATCHCOM input file. BATCHCOM stops when the number of errors exceeds the specified limit. ALLO[W] num ER[RORS] num is an integer in the range 0 through 65535 specifying the number of errors allowed. Considerations • • • • The ALLOW ERRORS command is available to all users.
ALTER ATTACHMENT-SET Command Commands the BATCHCOM process to stop when a third error occurs. Note the completion code (2) when the process stops and the reported warnings (1) and errors (3). > BATCHCOM /IN INFILE/ $ZBAT ALLOW 2 ERRORS SUBMIT JOB A, IN A, OUT $S.#A, AT 20:30 2056-E AT-ALLOWED is currently OFF; submit AFTER time SUBMIT JOB B, IN B, OUT $S.#B, CLASS OPS 2105-E CLASS OPS does not exist SUBMIT JOB C, IN C, OUT $S.
ALTER ATTACHMENT-SET Command Commands attachment-set-name specifies an attachment-set name or a range of names when specified with the asterisk (*) and question mark (?) wild-card characters. attachment-set-number is a scheduler-generated number identifying an attachment set created by means of the #CURRENT variable. * specifies all attachment sets. #CURRENT is the attachment set specified by the #CURRENT variable.
ALTER ATTACHMENT-SET Command Commands 3} INFO ATTACHMENT-SET STANDARD, ASSIGN, DEFINE, PARAM ATTACHMENT-SET ATTRIBUTES for (SUPER.NB)STANDARD attachments: DEFINE =LOC, CLASS SPOOL, LOC \SYS1.$S DEFINE =_DEFAULTS, CLASS DEFAULTS, VOLUME $A.NB ASSIGN FILE-X, X ASSIGN FILE-Y, Y PARAM A 1 PARAM B 2 ° By resetting ASSIGNs and PARAMs. For example: 7} CHANGEUSER FPP.MANAGER psswrd 7} INFO ATTACHMENT-SET OPS, ASSIGN, PARAM ATTACHMENT-SET ATTRIBUTES for (FPP.MANAGER)OPS attachments: ASSIGN BCKPS-DLY, $A.NB.
ALTER ATTACHMENT-SET Command Commands 7} INFO ATTACHMENT-SET 23, SECURITY, TEMPORARY ATTACHMENT-SET ATTRIBUTES for (SUPER.SUPER)23 security: "GOGO" temporary: Off • • • • BATCHCOM supports all classes of DEFINE available in the TACL environment. The default DEFINE class is MAP. The LIKE qualifier is available for DEFINEs only. Use it in the ALTER ATTACHMENT-SET command to specify DEFINEs whose attributes match those of DEFINEs specified earlier in the command.
ALTER ATTACHMENT-SET Command Commands Examples • This example shows the ALTER ATTACHMENT-SET command altering a sort DEFINE by changing its attributes in the #CURRENT variable: > LOGON NB.USER, psswrd > INFO DEFINE =SORT, DETAIL Define Name =SORT CLASS SORT SCRATCH \MELBDEV.$TRASH.NB.PURGEME MODE AUTOMATIC PRI 149 CPUS ALL > BATCHCOM $ZBAT 1} SHOW ATTACHMENT-SET DEFINE =SORT ATTACHMENT-SET ATTRIBUTES attachments: DEFINE =SORT, CLASS SORT, SCRATCH \MELBDEV.$TRASH.NB.
ALTER ATTACHMENT-SET Command Commands • This example shows the ALTER ATTACHMENT-SET command changing the value of PARAM DATE in all attachment sets containing that PARAM. The command also adds PARAM TIME to those sets. 51} CHANGEUSER 255,255 psswrd 51} INFO ATTACHMENT-SET (*.*)DAY, PARAM DATE, PARAM TIME ATTACHMENT-SET ATTRIBUTES for (NB.USER)DAY attachments: PARAM DATE 22JUN93 ATTACHMENT-SET ATTRIBUTES for (NB.MANAGER)DAY attachments: PARAM DATE 22JUN93 ATTACHMENT-SET ATTRIBUTES for (SUPER.
ALTER CLASS Command Commands • This example shows the execution of ADD ATTACHMENT-SET and ALTER ATTACHMENT-SET commands and lists scheduler log file events relating to those commands: > LOGON 205,70, password > BATCHCOM $SCHD; ADD ADP (205,100) QA-1, SECURITY "NNNN", TEMPORARY OFF, (ASSIGN A, $A.NB.A), (DEFINE =_DEFAULTS, VOLUME $DATA7.SCHD), (PARAM TIME 5:00) Attachment-set (FPP.QA)QA-1 added > BATCHCOM $SCHD; ALTER ATTACHMENT-SET (205,100) QA-1, (PARAM DATE 21JUL93) Attachment-set (FPP.
ALTER EXECUTOR Command Commands • You can omit the object keyword CLASS from the ALTER CLASS command only when CLASS is the current assumed object. For more information, see ASSUME CLASS Command later in this section.
ALTER EXECUTOR Command Commands executor-name-2 is the name of an executor whose attributes you want executor executor-name-1 to match. attribute is one of these executor attributes (see Section 7, Attributes): CL[ASS] BBC{( AALVS1( class-name,( class-name [ , class-name ]…),*) ) CP[U] cpu-number attribute, when specified with LIKE, overrides executor-name-2 attributes of the same type. Considerations • • • • • • The ALTER EXECUTOR command is available to NetBatch supervisors only.
ALTER EXECUTOR Command Commands Examples • This example shows the ALTER EXECUTOR command altering the attributes of an executor. The command alters the CPU attribute to 0 and the CLASS attribute by dissociating class DEFAULT and reordering the remaining classes.
ALTER JOB Command Commands ALTER JOB Command Use the ALTER JOB command to change job attributes. ALT[ER] [ JOB ] [ / OU[T] [ file-name ] / ] { job-ID } { ( [ [NOT] job-ID ,]… [NOT] filter [ , [NOT] filter ]… ) } { , LIK[E] job-ID-2 [ , attribute ]… } { , attribute [ , attribute ]… } [ { IN } ] [ , REM[OVE] { J[OB]-L[OG] } ] … [ { LIB } ] file-name specifies a command output file. The file can be a device, a process, or a disk file.
ALTER JOB Command Commands attribute is one of these job attributes (see Section 7, Attributes): AF[TER] [ date ] [ time ] AT [ date ] [ time ] A[TTACHMENT]-S[ET] [ attachment-set | ( attachment-set [ ‚ attachment-set ]… )] CA[LENDAR] [ file-name ] CL[ASS] class-name DES[CRIPTION] " [ string ] " EV[ERY] [ ( weeks WEEK[S] days D[AYS] hours [ : mins ] [HOURS] hours H[OURS] [ mins MIN[UTES] ] crontab-entry) ] E[XECUTOR]-P[ROGRAM] file-name EXT[SWAP] { $volume-name | file-name } HIG[HPIN] {OF[F] | ON } HOLDBB
ALTER JOB Command Commands REMOVE removes the job’s IN attribute, JOB-LOG attribute, or the library file from the job’s executor program. IN removes the job’s IN attribute, which makes the scheduler become the job’s input file. If the job reads the file, it encounters file-system error 2 (operation not allowed). If the job writes the file, it writes to the scheduler’s log file.
ALTER JOB Command Commands ° If the job’s state is EXECUTING, OVER LIMIT, or SUSPENDED, the only attributes that can apply are DESCRIPTION, HOLDAFTER, IFFAILS, LIMIT, PURGE-IN-FILE, RESTART, SAVEABEND, STALL, and STOP-ON-ABEND. If the job is also recurrent, the updated description applies in full the next time the job runs. (A recurrent job has the CALENDAR or EVERY attribute.
ALTER JOB Command Commands attribute(s) might not affect current execution Job V job number 349 altered 36} ALTER JOB 353, SELPRI 1, PRI 119 2132-E Your user code does not give you access to Z 37} CHANGEUSER 255,205 password 37} ALTER JOB *, OUT $S.
ALTER SCHEDULER Command Commands ALTER SCHEDULER Command Use the ALTER SCHEDULER command to change scheduler attributes. ALT[ER] [ SCHEDULER ] [ / OU[T] [ file-name ] / ] , attribute [ , attribute ]… file-name specifies a command output file. The file can be a device, a process, or a disk file. For a disk file, BATCHCOM appends output if the file exists, but creates an EDIT file if the file does not exist. If you specify / OUT / (that is, omit file-name), BATCHCOM suppresses output.
ALTER SCHEDULER Command Commands Examples • This example shows the effect of an ALTER SCHEDULER command: 10} CHANGEUSER 255,255 password 10} INFO SCHEDULER, AT-ALLOWED, DEFAULT-PRI, DEFAULT-SELPRI, DEFAULT-OUT, DEFAULT-CLASS SCHEDULER ATTRIBUTES at-allowed: Off default-pri: 119 default-selpri: 2 default-out: \MELBDEV.$S.#ZBATJOB default-class: DEFAULT 11} ALTER SCHEDULER, AT-ALLOWED ON, DEFAULT-PRI 100, DEFAULTSELPRI 2, DEFAULT-OUT $S.
ASSUME ATTACHMENT-SET Command Commands ASSUME ATTACHMENT-SET Command Use the ASSUME ATTACHMENT-SET command to set the default object keyword for later commands to ATTACHMENT-SET. BATCHCOM substitutes this object keyword in all commands you enter that do not include an object keyword. ASSU[ME] A[TTACHMENT]-S[ET] Considerations • • • • • The ASSUME ATTACHMENT-SET command is available to all users.
ASSUME CLASS Command Commands ASSUME CLASS Command Use the ASSUME CLASS command to set the default object keyword for later commands to CLASS. BATCHCOM substitutes this object keyword in all commands you enter that do not include an object keyword. ASSU[ME] CL[ASS] Considerations • • • • • The ASSUME CLASS command is available to all users. Class commands you enter after the ASSUME CLASS command do not have to include the object keyword CLASS.
ASSUME EXECUTOR Command Commands ASSUME EXECUTOR Command Use the ASSUME EXECUTOR command to set the default object keyword for later commands to EXECUTOR. BATCHCOM substitutes this object keyword in all commands you enter that do not include an object keyword. ASSU[ME] EXE[CUTOR] Considerations • • • • The ASSUME EXECUTOR command is available to all users. Executor commands you enter after the ASSUME EXECUTOR command do not have to include the object keyword EXECUTOR.
ASSUME JOB Command Commands ASSUME JOB Command Use the ASSUME JOB command to set the default object keyword for later commands to JOB. BATCHCOM substitutes this object keyword in all commands you enter that do not include an object keyword. ASSU[ME] JOB Considerations • • • • The ASSUME JOB command is available to all users. Job commands you enter after the ASSUME JOB command do not have to include the object keyword JOB.
ASSUME SCHEDULER Command Commands ASSUME SCHEDULER Command Use the ASSUME SCHEDULER command to set the default object keyword for later commands to SCHEDULER. BATCHCOM substitutes this object keyword in all commands you enter that do not include an object keyword. ASSU[ME] SC[HEDULER] Considerations • • • • The ASSUME SCHEDULER command is available to all users. Scheduler commands you enter after the ASSUME SCHEDULER command do not have to include the object keyword SCHEDULER.
CHANGEUSER Command Commands CHANGEUSER Command Use the CHANGEUSER command to log on as a different user during a BATCHCOM session. The logon takes place on the system where the BATCHCOM process is running. CH[ANGEUSER] user-ID [ password ] user-ID is a user ID in either of these forms: group-name.user-name group-name is the name of the group to which the user belongs. user-name is the name of the user assigned to the group. An example of a user ID in group-name.user-name form is NB.USER.
CHANGEUSER Command Commands • If you specify an incorrect user ID or password, this message appears: 0300-E USER not found or incorrect password for LOGON BATCHCOM delays the return of its prompt for one minute if you enter an incorrect user ID or password three times in succession. • • BATCHCOM does not store the CHANGEUSER command in its history buffer. You can disable the CHANGEUSER command with the NBFLAGS procedure. For details, see on page 2-3.
COMMENT Command Commands COMMENT Command Use the COMMENT command at the beginning of a line in a BATCHCOM input file to cause BATCHCOM to ignore the line. COM[MENT] [ comment-text ] comment-text is any text, including braces and square brackets. Considerations • • • The COMMENT command is available to all users. You can enter the COMMENT command only at the beginning of a line in a BATCHCOM input file. Comment text finishes at the end of a line.
DELETE ATTACHMENT-SET Command Commands • This example shows the line continuation character used during an interactive session and the resulting double-braces prompts indicating the continued lines: 1} SUBMIT JOB FRIDAY, & }} IN $DATA7.NB.WEEKEND, & }} OUT \MELBDEV.$S.#FRIDAY, & }} EXECUTOR-PROGRAM $SYSTEM.SYSTEM.FUP, & }} AFTER 23:00, & }} WAITON THURSDAY Job FRIDAY job number 127 submitted DELETE ATTACHMENT-SET Command Use the DELETE ATTACHMENT-SET command to delete attachment sets from a scheduler.
DELETE ATTACHMENT-SET Command Commands attribute is one of these attachment-set attributes: ASSI[GN] [ ASSIGN-name ] DEFI[NE] [ DEFINE-name ] PA[RAM] [ PARAM-name ] attribute causes BATCHCOM to delete only the specified attribute from the attachment sets specified by attachment-set-ID. If you omit attribute and do not specify DETAIL, BATCHCOM deletes all attachment sets specified by attachment-set-ID.
Commands DELETE ATTACHMENT-SET Command Examples • This example shows the results of various DELETE ATTACHMENT-SET commands executed by different users: 42} CHANGEUSER SUPER.NB psswrd 42} INFO ATTACHMENT-SET A1, DETAIL ATTACHMENT-SET ATTRIBUTES for (SUPER.NB)A1 security: "GGGO" temporary: Off attachments: DEFINE =MAP, CLASS MAP, FILE \A.$D6.NB.MYFILE DEFINE =TAPE, CLASS TAPE, LABELS OMITTED, DEVICE \A.$TAPE DEFINE =_DEFAULTS, CLASS DEFAULTS, VOLUME $A.NB ASSIGN FILE-A, $NB.MYFILES.A ASSIGN FILE-B, $NB.
Commands DELETE ATTACHMENT-SET Command from attachment set SLS-WEDNESDAY-JOBS because the set’s name is outside the specified range. 25} CHANGEUSER NB.USER psswrd 25} INFO ATTACHMENT-SET SL?-*, ASSIGN ATTACHMENT-SET ATTRIBUTES for (NB.USER)SLS-FRIDAY-JOBS attachments: ASSIGN AFTERNOON, $A.NB.FRDYPM ASSIGN FRIDAY, $A.NB.FRDY ASSIGN MORNING, $A.NB.FRDYAM ASSIGN OUTPUT-FILE, $TRASH.PURGEME ATTACHMENT-SET ATTRIBUTES for (NB.USER)SLS-MONDAY-JOBS attachments: ASSIGN AFTERNOON, $A.NB.MNDYPM ASSIGN MONDAY, $A.NB.
DELETE CLASS Command Commands DELETE CLASS Command Use the DELETE CLASS command to delete classes from a scheduler. D[ELETE] [ CLASS ] [ / OU[T] [ file-name ] / ] class-name file-name specifies a command output file. The file can be a device, a process, or a disk file. For a disk file, BATCHCOM appends output if the file exists, but creates an EDIT file if the file does not exist. If you specify / OUT / (that is, omit file-name), BATCHCOM suppresses output. class-name is the name of a class.
DELETE EXECUTOR Command Commands cpu: 0 classes: DEFAULT STANDARD-CLASS EXECUTOR ATTRIBUTES for EX1 cpu: 1 classes: SPARE-PARTS-DEPT 11} DELETE CLASS SPARE-PARTS-DEPT 2104-E CLASS SPARE-PARTS-DEPT is in use by one or more executors. To delete the CLASS, you must remove it from the executors first. • This example shows events leading up to and including the deletion of class DEVELOPMENT. These events include dissociation of the class from the two executors to which it belongs and from a job.
DELETE EXECUTOR Command Commands executor-name is the name of an executor. Considerations • • • • The DELETE EXECUTOR command is available to NetBatch supervisors only. A job using an executor that is the subject of a DELETE EXECUTOR command finishes before the scheduler deletes the executor. The executor’s state pending deletion in this circumstance is DELETE. After deleting an executor, you must reassign classes that were unique to it to other executors.
DELETE JOB Command Commands • This example shows the deletion of an executor in use by a job. The scheduler allows the job to finish before deleting the executor. Note the change in executor state from ACTIVE to DELETE.
DELETE JOB Command Commands CL[ASS] class-ID IN file-ID STATE state U[SER] user-ID WAITO[N] master-job Considerations • The DELETE JOB command is available to all users, but these conditions apply: ° ° NetBatch supervisors can delete jobs belonging to any user. ° If you are not a NetBatch supervisor, a DELETE JOB command that specifies job-ID with wild-card characters deletes only your own jobs.
DISPLAY-SPI Command Commands 196 URGENT 255,8 RUN-NOW URGENT-JOBS 197 COMPILE 133,2 1412 SUSPENDED STANDARD-CLASS 198 Q3 205,70 1414 EXECUTING STANDARD-CLASS 2} DELETE JOB * 2132-E Your user code does not give you access to DEVELOPMENT 2132-E Your user code does not give you access to TOTALS 2132-E Your user code does not give you access to TEST 2132-E Your user code does not give you access to CLEANUP Job CAL-JOB-1 Jobnumber 188 deleted Job USERS Jobnumber 189 deleted 2132-E Your user code does not give
DISPLAY-SPI Command Commands -----------------------------------------------------------|_SPI_BUFFER_ { BEING_SENT_TO | RETURNED_FROM } _SCHEDULER_ | -----------------------------------------------------------Checksum: zspi-tkn-checksum Header Type: zspi-tkn-hdrtype Last error: zspi-tkn-lasterr Last error code: zspi-tkn-lasterrcode Last Position: zspi-tkn-lastposition Max Field Version: zspi-tkn-max-field-version Maxresp: zspi-tkn-maxresp Position: zspi-tkn-position Server version: zspi-tkn-server-version
DISPLAY-SPI Command Commands zspi-tkn-maxresp is the value of the SPI header token ZSPI-TKN-MAXRESP. The token contains a value indicating how many response records BATCHCOM accepts in a response message. zspi-tkn-position is the value of the SPI header token ZSPI-TKN-POSITION. The token contains the current-token pointer. zspi-tkn-server-version is the value of the SPI header token ZSPI-TKN-SERVER-VERSION.
DISPLAY-SPI Command Commands VAR indicates the token is a variable-length token. The size of the token’s value in bytes is given in size: token-value. size is the token size in bytes (when size appears in token-data-type: size) or the size of the token’s value in bytes (when size appears in size: token-value). size appears with token-data-type when the token is not a variable-length token. size appears with token-value when the token is a variable-length token. token-code is the token code.
DISPLAY-SPI Command Commands • If the value includes printable and unprintable characters, or is unprintable, the display format is: bytes: ? [ count x ] binary-value [ ? [ count x ] binary-value ]… [ printable-chars ]… bytes is the number of bytes in the value. count specifies the number of occurrences of binary-value. count appears only when binary-value occurs more than once. binary-value is the binary value of the character (not necessarily a space). printable-chars represents printable characters.
DISPLAY-SPI Command Commands Considerations • • The DISPLAY-SPI command is available to all users. The RUN NETBATCH command parameter DISPLAY-SPI is an alternative to the DISPLAY-SPI command. The parameter makes the scheduler write to its log file command and response buffers received from and sent to requesters such as BATCHCOM. The buffers appear in the log file in the same format as in BATCHCOM. For more information, see Running NETBATCH on page 3-10.
EXIT Command Commands END LIST Executor EXEC-01 deleted EXIT Command Use the EXIT command to end an interactive BATCHCOM session. The command stops the BATCHCOM process and returns you to the process from which you started the session. E[XIT] Considerations • • The EXIT command is available to all users. Creating an end-of-file (EOF) condition by pressing CTRL/Y has the same effect as the EXIT command.
FC Command Commands text is a character string identifying the latest line in the history buffer beginning with the string. Considerations • • The FC command is available to all users. If no line in the history buffer matches your specification, this message appears: 0541-I No such line • • Entering FC with no parameter retrieves the latest line from the history buffer (FC is the same as FC -1). The FC command displays the specified line with a period prompt (.) below it.
FC Command Commands 7} INFO JOB /OUT $S.#INFO/ * 8} SUBMIT JOB J3, IN INFILE3, AT 15:00 • This example shows retrieval, editing, and execution of the latest line in the buffer: 9} FC 9} SUBMIT JOB J3, 9}. 4// 4, WAITON 9} SUBMIT JOB J4, 9}. Job J4 job number 10} • IN INFILE3, AT 15:00 J3 IN INFILE4, WAITON J3 4 submitted This example shows retrieval, editing, and execution of command line 4 in the buffer: 9} FC 4 9} ADD CLASS DEFAULT, INITIATION OFF 9}.
HELP Command Commands 16}. 16}}CLASS STANDARD-CLASS, PRI 149, AFTER 17:30, HOLDAFTER ON 16}. DDDDDDDDDDDDDDIDEFAULT// FF 16}}CLASS DEFAULT, PRI 149, AFTER 17:30, HOLDAFTER OFF 16}. Job STOCK-LEVELS job number 5 altered HELP Command Use the HELP command to display information about objects, commands, and attributes and about other general NetBatch topics such as keyword abbreviation. H[ELP] [ / OU[T] [ file-name ] / ] [ topic | ALL ] file-name specifies a command output file.
HELP Command Commands DATE-TIME NUM SPECIAL DEFINE ? NUMBER STRING DEFINE DEFINE-class NUMCONC SUPERVISOR DEFINE-ATTRIBUTE NUMNOW TIME DEFINE-CLASS OBJECTS USER-ID DEFINE-NAME ON-OFF WAIT-FOR ALL causes BATCHCOM to display information about attachment sets, classes, executors, jobs, and schedulers, and to list the commands for manipulating them. Considerations • • • The HELP command is available to all users. Entering HELP without topic lists all topics for which HELP is available.
HELP Command Commands | P[ROTECTED] | | O[UTPUT] | R[EC] B[LOCK] All numeric values must be in the range 065535.
HISTORY Command Commands HISTORY Command Use the HISTORY command to display a specified number of the most recently executed command lines in BATCHCOM’s history buffer. HIS[TORY] [ / OU[T] [ file-name ] / ] [ num ] file-name specifies a command output file. The file can be a device, a process, or a disk file. For a disk file, BATCHCOM appends output if the file exists, but creates an EDIT file if the file does not exist. If you specify / OUT / (that is, omit file-name), BATCHCOM suppresses output.
INFO ATTACHMENT-SET Command Commands 12} ALTER JOB TODAY, PRI 165, SELPRI 7 13} • This example shows the HISTORY command displaying all commands except CHANGEUSER: 1} SUBMIT JOB X, AFTER 23:00 Job X job number 7 submitted 2} CHANGEUSER 255,205 password 2} ALTER SCHEDULER, AT-ALLOWED OFF Scheduler altered 3} CHANGEUSER 205,70 password 3} SUBMIT JOB Y, AFTER 23:15 Job Y job number 8 submitted 4} HISTORY 1} SUBMIT JOB X, AFTER 23:00 2} ALTER SCHEDULER, AT-ALLOWED OFF 3} SUBMIT JOB Y, AFTER 23:15 4} INFO A
INFO ATTACHMENT-SET Command Commands attachment-set-number is a scheduler-generated number identifying an attachment set created by means of the #CURRENT variable. * specifies all attachment sets. #CURRENT causes BATCHCOM to list attributes of the attachment set specified by the #CURRENT variable.
INFO ATTACHMENT-SET Command Commands The command appears in commented form if it specifies a numbered attachment set. For example: ==ADD (FPP.MANAGER)8 Considerations • • • • The INFO ATTACHMENT-SET command is available to all users. However, you must have read access to an attachment set for BATCHCOM to display more than the set’s SECURITY attribute. For example, NB.USER could list all attributes of set (SUPER.FPP)A secured “AGAG,” but only the SECURITY attribute of set (SUPER.FPP)B secured “GOGO.
INFO ATTACHMENT-SET Command Commands (SUPER.SUPER)MANAGERS-ONLY data ATTACHMENT-SET ATTRIBUTES for (SUPER.SUPER)SWING security: "AOOO" attachments: DEFINE =OUT, CLASS SPOOL, LOC \A.$S.#SWING PARAM SHIFT 0900-1700 • This example shows an INFO ATTACHMENT-SET command writing specified attachment-set attributes to an EDIT file: 6} ADD ATTACHMENT-SET (FPP.MANAGER)MNGR-ADPS, (ASSIGN BAPREWK, \MELBORN.$FPP.MSMNTHLY.BAPREWK), (PARAM REP-DATE .06-OCT94.), (PARAM MERGE-DATE .941006.
INFO CLASS Command Commands INFO CLASS Command Use the INFO CLASS command to list the attributes of classes. I[NFO] [ CLASS ] [ / OU[T] [ file-name ] / ] class-ID [ , O[BEY]-[FORM] ] file-name specifies a command output file. The file can be a device, a process, or a disk file. For a disk file, BATCHCOM appends output if the file exists, but creates an EDIT file if the file does not exist. If you specify / OUT / (that is, omit file-name), BATCHCOM suppresses output.
INFO EXECUTOR Command Commands initiation: On CLASS ATTRIBUTE for MIS initiation: Off CLASS ATTRIBUTE for SALES initiation: Off • This example shows the result of an INFO CLASS command that writes class details to an EDIT file: 24} INFO CLASS /OUT OPSINFO/ * 25} RUN FUP COPY OPSINFO CLASS ATTRIBUTE for DEFAULT initiation: On CLASS ATTRIBUTE for MIS initiation: Off CLASS ATTRIBUTE for SALES initiation: Off • This example shows the result of an INFO CLASS command that includes the OBEY-FORM qualifier.
INFO EXECUTOR Command Commands attribute causes BATCHCOM to list only the specified attribute. If you omit attribute, BATCHCOM lists all attributes. OBEY-FORM causes BATCHCOM to list attributes in ADD EXECUTOR command format. Considerations • • • The INFO EXECUTOR command is available to all users. The OBEY-FORM qualifier is available for all INFO commands. It enables the creation of BATCHCOM command files that you can use to set up a scheduler.
INFO JOB Command Commands cpu: 1 EXECUTOR ATTRIBUTES for RISC-2 cpu: 2 EXECUTOR ATTRIBUTES for RISC-3 cpu: 3 • This example shows the result of an INFO EXECUTOR command that includes the OBEY-FORM qualifier. In the example, BATCHCOM sends the command’s output to an EDIT file.
INFO JOB Command Commands STATE state U[SER] user-ID WAITO[N] master-job attribute is one of these job attributes: AF[TER] AT CA[LENDAR] CL[ASS] DES[CRIPTION] EV[ERY] E[XECUTOR] -[PROGRAM EXT[SWAP] HIG[HPIN] HOLD HOLDA[FTER] F[FAILS] IN J[OB]-L[OG] J[OBID]-Z[ERO] LIB LIM[IT] MAXPRINTL[INES] MAXPRINTP[AGES] ME[M] RUND SA[VEABEND] SEL[PRI] STAL[L] STARTU[P] S[TOP]-[ON]-[ABEND] SWA[P] NA[ME] OU[T] PF[S] PR[I] P[URGE]-[IN]-[FILE] REST[ART] TA[PEDRIVES] V[OLUME] WAIT WAITO[N] attribute causes BATCHCOM to
INFO JOB Command Commands The command appears in commented form if it specifies a numbered attachment set. For example: ==SET JOB ATTACHMENT-SET ((FPP.MANAGER)4) Considerations • • • The INFO JOB command is available to all users. The OBEY-FORM qualifier is available for all INFO commands. It enables the creation of BATCHCOM command files that you can use to set up a scheduler. For more information, see Section 3, Scheduler Planning, Configuration, and Management.
INFO JOB Command Commands • This example shows the result of an INFO JOB command that includes the OBEYFORM qualifier. In the example, BATCHCOM sends the command’s output to an EDIT file. 59} INFO JOB /OUT JOB29/ 29, EXECUTOR-PROGRAM, STARTUP, EVERY, OBEY-FORM 60} RUN FUP COPY JOB29 ASSUME JOB RESET SET EXECUTOR-PROGRAM \MELBDEV.$SYSTEM.SYSTEM.
INFO SCHEDULER Command Commands INFO SCHEDULER Command Use the INFO SCHEDULER command to list the attributes of schedulers. I[NFO] [ SCHEDULER ] [ / OU[T] [ file-name ] / ] [ , attribute ]… [ , O[BEY]-[FORM] ] file-name specifies a command output file. The file can be a device, a process, or a disk file. For a disk file, BATCHCOM appends output if the file exists, but creates an EDIT file if the file does not exist. If you specify / OUT / (that is, omit file-name), BATCHCOM suppresses output.
INFO SCHEDULER Command Commands • You can omit the object keyword SCHEDULER from the INFO SCHEDULER command only when SCHEDULER is the current assumed object. For more information, see ASSUME SCHEDULER Command on page 6-73. Examples • This example shows the result of an INFO SCHEDULER command: 65} INFO SCHEDULER SCHEDULER ATTRIBUTES backupcpu: 0 at-allowed: On submit-allowed: On initiation: On default-executor-program: \MELBDEV.$SYSTEM.SYSTEM.
OBEY Command Commands ALTER, ALTER, ALTER, ALTER, ALTER, ALTER, ALTER, ALTER, ALTER, ALTER, ALTER, ALTER, ALTER, ALTER, ALTER, DEFAULT-EXECUTOR-PROGRAM \MELBDEV.$SYSTEM.SYSTEM.TACL MAX-PRI 199 DEFAULT-PRI 120 MAX-CONCURRENT-JOBS 1,1 DEFAULT-SELPRI 3 DEFAULT-MAXPRINTLINES NONE DEFAULT-MAXPRINTPAGES NONE TAPEDRIVES 2 DEFAULT-OUT \MELBDEV.$S.
OPEN Command Commands A B C D E ADD SCHEDULER OBEY B START SCHEDULER OBEY C ADD CLASS … OBEY D ADD EXECUTOR … OBEY E START EXECUTOR … VST018.
OPEN Command Commands ° When you specify a scheduler in BATCHCOM’s TACL RUN command. For example, the first of these commands opens scheduler $SCHD. The second starts BATCHCOM but does not open a scheduler: > BATCHCOM $SCHD BATCHCOM - T9190D30 … NETBATCH SERVER - T9190D30 … Time: 06OCT94 11:47:24 1} 10> BATCHCOM BATCHCOM - T9190D30 … 1} ° When BATCHCOM executes the first scheduler-related command after a session begins and BATCHCOM’s TACL RUN command did not specify a scheduler.
RELEASE-WAITON Command Commands 2} OPEN \MELBQAT.$SCHD NETBATCH SERVER - T9190C23 … Time: 07OCT94 20:43:31 3} STATUS SCHEDULER SCHEDULER STATUS Process : \MELBQAT.$SCHD Primary : 1,43 Backup : 0,72 Database: $DATA7.SCHD Logfile : $DATA7.SCHD.LOGAAB Time : 07OCT94 20:43:31 . . RELEASE-WAITON Command Use the RELEASE-WAITON command to release dependent jobs from their masters, without running the masters.
REPORT JOB Command Commands UPDATE JOB X C_DEFAULT:3 J_24 U_255,255 H_\MELRISK.$ZTN0.
RESET ATTACHMENT-SET Command Commands HOLD-REPORT Job-Submit Jobs that are put on hold MISC-REPORT Job-Submit Jobs configured under a particular class, or satisfying the job-filter attribute PRED-REPORT Job-Submit Master jobs of jobs satisfying thejobfilter attribute SUCR-REPORT Job-Submit Dependent jobs of jobs satisfying the job-filter attribute TAPE-REPORT Job-Submit Jobs that require tapedrives to run ABEND-REPORT Job-Run Job RunJobs that abended LATE-REPORT Job-Run Job RunJobs not
RESET ATTACHMENT-SET Command Commands DEFINE, or PARAM, but omit ASSIGN-name, DEFINE-name, or PARAM-name, BATCHCOM removes all ASSIGNs, DEFINEs (except =_DEFAULTS), or PARAMs. Considerations • • • • The RESET ATTACHMENT-SET command is available to all users. The RESET ATTACHMENT-SET command, like the OPEN and SET ATTACHMENT-SET commands, sets the #CURRENT variable’s value to null. ADP (an abbreviation of ASSIGNs, DEFINEs, and PARAMs) is an alias of the object keyword ATTACHMENT-SET.
RESET CLASS Command Commands PARAM ADDR2 CUPERTINO PARAM ADDR3 CA_95014 • In this example, the RESET ATTACHMENT-SET command removes the TEMPORARY attribute from the working-attributes set and all ASSIGN attributes. The command also removes the DEFINE =TAPE but leaves all other DEFINEs, the PARAMs, and the SECURITY attribute. 33} SHOW ATTACHMENT-SET ATTACHMENT-SET ATTRIBUTES security: "AOAO" temporary: On attachments: DEFINE =SQLCAT, CLASS CATALOG, SUBVOL \MELBDEV.$SYSTEM.
RESET EXECUTOR Command Commands Example This example shows the RESET CLASS command restoring the default value of the INITIATION attribute in the working-attributes set: 6} SHOW CLASS CLASS ATTRIBUTE initiation: Off 7} RESET CLASS 8} SHOW CLASS CLASS ATTRIBUTE initiation: On RESET EXECUTOR Command Use the RESET EXECUTOR command to remove executor attributes from BATCHCOM’s working-attributes set.
RESET JOB Command Commands • To use the RESET EXECUTOR command to remove the CPU executor attribute from the working-attributes set: 1} SET EXECUTOR CLASS *, CPU 0 2} SHOW EXECUTOR EXECUTOR ATTRIBUTES cpu: 0 classes: * 3} RESET EXECUTOR CPU 4} SHOW EXECUTOR EXECUTOR ATTRIBUTES classes: * RESET JOB Command Use the RESET JOB command to remove job attributes from BATCHCOM’s workingattributes set.
RESET SCHEDULER Command Commands • You can omit the object keyword JOB from the RESET JOB command only when JOB is the current assumed object. For more information, see ASSUME JOB Command on page 6-72. Examples • This example shows the RESET JOB command removing the HOLD and AFTER job attributes from the working-attributes set: 6} SHOW JOB JOB ATTRIBUTES volume: \MELBDEV.$A.
RESET SCHEDULER Command Commands attribute is one of these scheduler attributes: AT-A[LLOWED] D[EFAULT]MAXPRINTP[AGES] INI[TIATION] B[ACKUPCPU] D[EFAULT]-O[UT] LO[CALNAMES] CAT[CHUP] D[EFAULT]-P[RI] M[AX]-[CONCURRENT][JOBS] D[EFAULT]-C[LASS] D[EFAULT]-SE[LPRI] M[AX]-[PRI] D[EFAULT]-E[XECUTOR][PROGRAM] D[EFAULT]-ST[ALL] S[UBMIT]-A[LLOWED] D[EFAULT]-H[IGHPIN] D[EFAULT]-[STOP][ON]-[ABEND] TA[PEDRIVES] D[EFAULT]MAXPRINTL[INES] EM[S] If you omit attribute, BATCHCOM removes all scheduler att
RUN Command Commands • This example shows the RESET SCHEDULER command removing all scheduler attributes from the working-attributes set: 3} SHOW SCHEDULER SCHEDULER ATTRIBUTES backupcpu: 1,2 at-allowed: On submit-allowed: On 4} RESET SCHEDULER 5} SHOW SCHEDULER SCHEDULER ATTRIBUTES RUN Command Use the RUN command to run a program during a BATCHCOM session. RUN program-file [ / OU[T] [ list-file ] / ] [ param-set ] program-file is the name of a program file.
RUNNEXT JOB Command Commands Example This example illustrates the use of the RUN command during a BATCHCOM session: 2} RUN EDIT; GET $QA.TESTS.FILES; LIST ALL TEXT EDITOR - T9601D20 - (01JUN93) CURRENT FILE IS $QA.TESTS.FILES 1 FILES /OUT \MELBDEV.$ZTN0.#PTY4/ $NB.T9190MAN *ADD 1 FILES /OUT \MELBDEV.$ZTN0.#PTY4/ $NB.T9190MAN 2 FILES /OUT \MELBDEV.$ZTN0.#PTY4/ $SYSTEM.
RUNNEXT JOB Command Commands IN file-ID STATE state U[SER] user-ID WAITO[N] master-job Considerations • • • • • • The RUNNEXT JOB command is available to NetBatch supervisors only. A job whose state is EVENT has the WAITON attribute and does not run until released by its masters. The RUNNEXT JOB command overrides the WAITON attribute and makes the job eligible to run, regardless of the completion states of its masters.
RUNNEXT JOB Command Commands JOB JOBNAME USERID LOG STATE CLASSNAME ---- ---------------- ------- ---- ----------- --------70 FIRST 255,255 670 EXECUTING DEFAULT 71 SECOND 255,255 READY DEFAULT 72 THIRD 255,255 RUNNEXT DEFAULT > FUP COPY LOGABR,,SHARE . . LIST JOB THIRD RUNNEXT J_72 U_255,255 H_\QA.$ZTN0.#PTY4 • This example shows two RUNNEXT JOB commands making jobs SELPRI-0 and SELPRI-1 run immediately after job SELPRI-7 finishes.
RUNNOW JOB Command Commands RUNNOW JOB Command Use the RUNNOW JOB command to make the scheduler run a job immediately. The command overrides job dependencies, timing attributes, and selection priority and makes the scheduler create a temporary executor for the job. RUNNO[W] [ JOB ] [ / OU[T] [ file-name ] / ] { job-ID } { ( [ [NOT] job-ID ,]… [NOT] filter [ , [NOT] filter ]… ) file-name specifies a command output file. The file can be a device, a process, or a disk file.
RUNNOW JOB Command Commands • • • • • • The scheduler creates temporary executors for all jobs with the AT attribute and for all jobs that are operated on by the RUNNOW JOB command. The scheduler deletes the executors when the jobs finish. A temporary executor has a scheduler-assigned name of the form __TEMP_EXEC_ job-number, where job-number is the number of the job using the executor; for example, __TEMP_EXEC_496.
SET ATTACHMENT-SET Command Commands JOB STATUS JOB JOBNAME USERID LOG STATE CLASSNAME ---- ---------------- ------- ---- ----------- --------82 ZBAT-0082 255,205 READY DEFAULT 56> BATCHCOM $ZBAT; RUNNOW JOB 82 Job ZBAT-0082 Jobnumber 82 runnow completed 57> BATCHCOM $ZBAT; STATUS JOB * JOB STATUS JOB JOBNAME USERID LOG STATE CLASSNAME ---- ---------------- ------- ---- ----------- --------82 ZBAT-0082 255,205 681 EXECUTING DEFAULT 58> BATCHCOM $ZBAT; STATUS EXECUTOR * EXECUTOR STATUS EXECUTOR CPU STATE JO
SET ATTACHMENT-SET Command Commands Considerations • • • • • • • • The SET ATTACHMENT-SET command is available to all users. You can list attachment-set attributes in the working-attributes set by using the SHOW ATTACHMENT-SET command. Two types of default attachment-set attributes are displayed in the workingattributes set: temporary and permanent. Temporary defaults are the ASSIGNs, DEFINEs, and PARAMs that BATCHCOM inherits from the TACL environment.
SET ATTACHMENT-SET Command Commands $A.NB ASSIGN ABC, $A.NB.ABC PARAM X 24 2} SET ATTACHMENT-SET (ASSIGN DEF, $A.NB.DEF), (DEFINE =GHI, CLASS MAP, FILE $A.NB.GHI), (PARAM Y 25), (ASSIGN ABC, $DATA7.NB.ABC); SHOW ATTACHMENT-SET ATTACHMENT-SET ATTRIBUTES attachments: DEFINE =GHI, CLASS MAP, FILE \DEV.$A.NB.GHI DEFINE =_DEFAULTS, CLASS DEFAULTS, VOLUME $A.NB ASSIGN ABC, $DATA7.NB.ABC ASSIGN DEF, $A.NB.
SET CLASS Command Commands 14} INFO ATTACHMENT-SET (SUPER.DRAT)2, DETAIL ATTACHMENT-SET ATTRIBUTES for (SUPER.DRAT)2 security: "AAAA" temporary: Off attachments: DEFINE =I, CLASS SPOOL, LOC \DEV.$I, OWNER "255,1" DEFINE =S, CLASS SPOOL, LOC \DEV.$S, OWNER "255,1" DEFINE =_DEFAULTS, CLASS DEFAULTS, VOLUME $A.NB ASSIGN ACCOUNT-REC, $D6.FIN.ACCNT PARAM SHIFT NIGHT SET CLASS Command Use the SET CLASS command to specify the value of the INITIATION class attribute in BATCHCOM’s working-attributes set.
SET EXECUTOR Command Commands Example This example shows the SET CLASS command setting the value of the INITIATION attribute in the working-attributes set. The class added after execution of the command adopts the attribute.
SET EXECUTOR Command Commands • • No default executor attributes are displayed in the working-attributes set. To remove attributes added to the set by the SET EXECUTOR command, use the RESET EXECUTOR command. You can omit the object keyword EXECUTOR from the SET EXECUTOR command only when EXECUTOR is the current assumed object. For more information, see ASSUME EXECUTOR Command on page 6-71.
SET JOB Command Commands SET JOB Command Use the SET JOB command to specify job attributes in BATCHCOM’s workingattributes set. Jobs submitted later by the SUBMIT JOB command adopt these attributes (which override job defaults) unless that command specifies otherwise. SET [ JOB ] [ LIK[E] job-ID , ] attribute [ , attribute ]… LIKE specifies that all attributes are to match those of job job-ID. job-ID specifies a job name or job number.
SET JOB Command Commands SEL[PRI] number STAL[L] { OF[F] | ON } STARTU[P] " param-set " S[TOP]-[ON]-[ABEND] { OF[F] | ON } SWA[P] {$volume-name | file-name } TA[PEDRIVES] number TERM $process-name V[OLUME] { \node. [ volume ] [ ‚ " [ \node. ] volume [ ‚ " security " [ \node. ] [ volume ] ‚ " security WAIT hours [ : mins ]| WAITO[N] [ job-name [ case ] ( job-name [ case ] [ , job-name [ security " ] ] " } case ] ]… ) ] Considerations • • • • • The SET JOB command is available to all users.
SET JOB Command Commands Examples • This example shows the SET JOB command specifying a series of job attributes in the working-attributes set. Note the effect of the RESET JOB command. 59} SHOW JOB JOB ATTRIBUTES volume: \DEV.$A.NB, "AAAO" in: \DEV.$A.NB.INFILE1 out: \DEV.$S.#TEMPOUT jobid-zero: Off user: 205,70 60} SET JOB VOLUME $DATA6.NBFILES, "NU-U", IN $DATA3.NBPBAT.OMSBATCH, OUT $S.#BPROC, EXECUTOR-PROGRAM NBEXEC, STARTUP "B-1, LI 2:00, XPRI 110"; SHOW JOB JOB ATTRIBUTES volume: \DEV.$DATA6.
SET JOB Command Commands out: \DEV.$S.#STATS executor-program: \DEV.$SYSTEM.SYSTEM.TACL jobid-zero: Off pri: 120 selpri: 6 maxprintlines: None maxprintpages: 100 class: DEFAULT stall: Off stop-on-abend: Off highpin: Off submit: 06OCT94 09:42:31 alter: 06OCT94 09:42:31 user: 133,2 next-runtime: 06OCT94 09:42:32 SCHEDULER ATTRIBUTES . default-executor-program: \DEV.$SYSTEM.SYSTEM.TACL . default-pri: 120 . default-selpri: 3 default-maxprintlines: None default-maxprintpages: None . default-out: \DEV.$S.
SET SCHEDULER Command Commands JOB JOB ATTRIBUTES volume: \DEV.$A.NB, "GOGO" in: \DEV.$A.NB.WKLYBKP out: \DEV.$S.#BACKUPS executor-program: \DEV.$SYSTEM.SYSTEM.BACKUP jobid-zero: Off pri: 149 selpri: 5 maxprintlines: None maxprintpages: None class: DEFAULT stall: Off stop-on-abend: Off every: 7 DAYS after: 06OCT94 18:00:00 highpin: Off user: 255,205 SET SCHEDULER Command Use the SET SCHEDULER command to specify scheduler attributes in BATCHCOM’s working-attributes set.
SET SCHEDULER Command Commands Considerations • • • • The SET SCHEDULER command is available to all users. However, you must be a NetBatch supervisor to use the ADD SCHEDULER command. To list scheduler attributes in the working-attributes set, use the SHOW SCHEDULER command. No default scheduler attributes are displayed in the working-attributes set. To remove attributes added to the set by the SET SCHEDULER command, use the RESET SCHEDULER command.
SHOW ATTACHMENT-SET Command Commands SHOW ATTACHMENT-SET Command Use the SHOW ATTACHMENT-SET command to list attachment-set attributes from BATCHCOM’s working-attributes set. SHO[W] [ ATTACHMENT-SET ] [ / OU[T] [ file-name ] / ] [ attribute [ , attribute ]… ] [ , O[BEY]-[FORM] ] [ O[BEY]-[FORM] ] file-name specifies a command output file. The file can be a device, a process, or a disk file. For a disk file, BATCHCOM appends output if the file exists, but creates an EDIT file if the file does not exist.
SHOW ATTACHMENT-SET Command Commands • The command SHOW ATTACHMENT-SET DEFINE =? displays the last DEFINE added to, altered in, or listed from the working-attributes set; for example: 5} SET ATTACHMENT-SET (DEFINE=BACKUP, CLASS TAPE, DEVICE $TAPE1, EXPIRATION 22OCT1994, OWNER "205,70", USE OPENFLAG, DENSITY 6250, LABELS ANSI) 6} SHOW ATTACHMENT-SET DEFINE =? ATTACHMENT-SET ATTRIBUTES attachments: DEFINE =_Work set, CLASS TAPE, LABELS ANSI, OWNER "205,70", EXPIRATION "22 OCT 1994", DENSITY 6250, USE OPENF
SHOW ATTACHMENT-SET Command Commands PARAM 2 DEF PARAM 3 GHI • This example shows the SHOW ATTACHMENT-SET command listing the attributes of a specified ASSIGN and PARAM from the working-attributes set: > BATCHCOM; SHOW ATTACHMENT-SET ASSIGN FILE-C, PARAM 3 ATTACHMENT-SET ATTRIBUTES attachments: ASSIGN FILE-C, $BIG2.FILES.
SHOW CLASS Command Commands SHOW CLASS Command Use the SHOW CLASS command to display the INITIATION class attribute from BATCHCOM’s working-attributes set. SHO[W] [ CLASS ] [ / OU[T] [file-name ] / ] [ O[BEY]-[FORM] ] file-name specifies a command output file. The file can be a device, a process, or a disk file. For a disk file, BATCHCOM appends output if the file exists, but creates an EDIT file if the file does not exist. If you specify / OUT / (that is, omit file-name), BATCHCOM suppresses output.
SHOW EXECUTOR Command Commands • This example shows the result of a SHOW CLASS command that includes the OBEY-FORM qualifier. In the example, BATCHCOM sends the command’s output to an EDIT file. 26> BATCHCOM; SHOW CLASS /OUT SHOWCL2/ OBEY-FORM 27> FUP COPY SHOWCL2 SET CLASS INITIATION ON SHOW EXECUTOR Command Use the SHOW EXECUTOR command to list executor attributes from BATCHCOM’s working-attributes set.
SHOW JOB Command Commands • You can omit the object keyword EXECUTOR from the SHOW EXECUTOR command only when EXECUTOR is the current assumed object. For more information, see ASSUME EXECUTOR Command on page 6-71.
SHOW JOB Command Commands attribute is one of these job attributes: AF[TER} IN REST[ART] AT J[OB]-L[OG] RUND A[TTACHMENT]-S[ET] J[OBID]-Z[ERO] SA[VEABEND] CA[LENDAR] LIB SEL[PRI] CL[ASS] LIM[IT] STAL[L] DES[CRIPTION] MAXPRINTL[INES] STARTU[P] EV[ERY] MAXPRINTP[AGES] S[TOP]-[ON]-[ABEND] E[XECUTOR]-P[ROGRAM] ME[M] SWA[P] EXT[SWAP] NA[ME] TA[PEDRIVES] HIG[HPIN] OU[T] V[OLUME] HOLD PF[S] WAIT HOLDA[FTER] PR[I] WAITO[N] IF[FAILS] P[URGE]-[IN]-[FILE] attribute causes BATCHC
SHOW JOB Command Commands • • The OBEY-FORM qualifier is available for all SHOW commands. It enables the creation of BATCHCOM command files that you can use to set up a workingattributes set. The SHOW JOB command displays the current user’s ID in group-ID,user-ID form. For example: 27} SHOW JOB JOB ATTRIBUTES volume: \MELBDEV.$A.NB, "NCNU" jobid-zero: Off user: 255,255 User is not a job attribute though BATCHCOM displays it as if it were.
SHOW SCHEDULER Command Commands class: ACCOUNTS-RPRTS attachment-set: LASER-PRINTER • This example shows the result of a SHOW JOB command that includes the OBEYFORM qualifier. In the example, BATCHCOM sends command output to an EDIT file. Note the commented CHANGEUSER command after the last SET command. 12} SHOW JOB JOB ATTRIBUTES volume: \DEV.$QAT2.HPLJ, "NNNN" out: \DEV.$S.#LP2 executor-program: \DEV.$SYSTEM.SYSTEM.COBOL85 jobid-zero: Off pri: 119 attachment-set: (SUPER.
SHOW SCHEDULER Command Commands D[EFAULT]-C[LASS] D[EFAULT]-SE[LPRI] M[AX]-[PRI] D[EFAULT]E[XECUTOR][PROGRAM] D[EFAULT]-ST[ALL] S[UBMIT]-A[LLOWED] D[EFAULT]H[IGHPIN] D[EFAULT]-[STOP][ON]-[ABEND] TA[PEDRIVES] D[EFAULT]MAXPRINTL[INES] EM[S] attribute causes BATCHCOM to list only the specified attribute. If you omit attribute, BATCHCOM lists all attributes. OBEY-FORM causes BATCHCOM to list attributes in SET SCHEDULER command format.
SHUTDOWN SCHEDULER Command Commands default-pri: 149 default-selpri: 4 tapedrives: 1 default-out: \MELBDEV.$S.#SCHD default-class: DEFAULT default-stop-on-abend: On • This example shows a SHOW SCHEDULER command writing specified scheduler attributes from the working-attributes set to an EDIT file: 24} SHOW SCHEDULER /OUT COBCOMP/ DEFAULT-EXECUTOR-PROGRAM, DEFAULT-OUT, DEFAULT-PRI 25} RUN FUP COPY COBCOMP SCHEDULER ATTRIBUTES default-executor-program: \DEV.$SYSTEM.SYSTEM.
SHUTDOWN SCHEDULER Command Commands Considerations • • • • • The SHUTDOWN SCHEDULER command is available to NetBatch supervisors only. SHUTDOWN SCHEDULER is one of two commands you can use to shut down a scheduler. The other command, ABORT SCHEDULER, does not allow executing and over-limit jobs to finish before shutdown. Like with SHUTDOWN SCHEDULER, it stops suspended jobs immediately. For more information, see ABORT SCHEDULER Command on page 6-30.
SHUTDOWN SCHEDULER Command Commands 38 ZBAT-0038 205,70 14:45:00 DEFAULT 97} SHUTDOWN SCHEDULER Scheduler shutting down 98} STATUS JOB * JOB JOBNAME USERID LOG STATE CLASSNAME ---- ---------------- ------- ---- ----------- -------------35 ZBAT-0035 205,70 644 EXECUTING DEFAULT 37 ZBAT-0037 205,70 READY DEFAULT 38 ZBAT-0038 205,70 14:45:00 DEFAULT 16} STATUS JOB * 0201-E Process gone or path down; operation failed, \QA.$ZBAT 0014-E Device does not exist, \QA.
START EXECUTOR Command Commands 29> PPD $SCHD Name Primary Backup Ancestor $SCHD 0,276 $C8 30> BATCHCOM $SCHD; START SCHEDULER Scheduler started 31> PPD $SCHD Name Primary Backup Ancestor $SCHD 0,276 2,275 $C8 32> BATCHCOM $SCHD; STATUS JOB * 2117-I No JOB selected START EXECUTOR Command Use the START EXECUTOR command to start executors whose state is OFF or STOP. The command makes the executors available for use by jobs and changes their states to ON.
START EXECUTOR Command Commands Examples • The START EXECUTOR command in this example starts an executor named A0: 42} STATUS EXECUTOR A0 EXECUTOR STATUS EXECUTOR CPU STATE JOB CLASS ------------------------ --- ------ ---- -------------------A0 0 OFF 43} START EXECUTOR A0 Executor A0 started 44} STATUS EXECUTOR A0 EXECUTOR STATUS EXECUTOR CPU STATE JOB CLASS ------------------------ --- ------ ---- -------------------A0 0 ON • The START EXECUTOR command in this example starts all OFF executors: 83} S
START SCHEDULER Command Commands START SCHEDULER Command Use the START SCHEDULER command to make available for use a scheduler you are cold starting or warm starting. For cold starts, use the command after running the scheduler program NETBATCH and executing the ADD SCHEDULER command. For warm starts, use the command immediately after running the scheduler program. START [ SCHEDULER ] [ / OU[T] [ file-name ] / ] file-name specifies a command output file.
START SCHEDULER Command Commands Examples • This example shows the cold start of a scheduler and the effect of the START SCHEDULER command in that process: $DATA7.TEST 55> NETBATCH /NAME $TEST, NOWAIT/ $DATA7.TEST ! $DATA7.TEST 56> PPD $TEST Name Primary Backup Ancestor $TEST 0,60 $Z743 $DATA7.TEST 57> FILEINFO Code EOF … Owner RWEP PExt SExt BATCHCTL O 847 552 … 255,255 "OOOO" 2 2 LOGAAA O 847 528 … 255,255 "NCNU" 50 100 $DATA7.TEST 58> BATCHCOM $TEST; ADD SCHEDULER Scheduler added $DATA7.
START SCHEDULER Command Commands • The log-file events resulting from the cold start of the scheduler in the previous example are: CREATE Scheduler Primary \MELBDEV.$TEST CPU 0 COLD Purge any existing scheduler database files OPEN U_255,255 P_BATCHCOM \MELBDEV.$:0:61:17122860 ADD SCHEDULER \MELBDEV.$:0:61:17122860 U_255,255 H_\MELBDEV.$ZTN0.#PTY6 CLOSE \MELBDEV.$:0:61:17122860 U_255,255 OPEN U_255,255 P_BATCHCOM \MELBDEV.$:0:61:17123116 START SCHEDULER \MELBDEV.$:0:61:17123116 U_255,255 H_\MELBDEV.$ZTN0.
STATUS ATTACHMENT-SET Command Commands STATUS ATTACHMENT-SET Command Use the STATUS ATTACHMENT-SET command to list attachment sets and the names and owners of jobs using those sets. S[TATUS] [ ATTACHMENT-SET ] [ / OU[T] [ file-name ] / ] { [ ( user-ID ) ] attachment-set-ID | #CURRENT file-name specifies a command output file. The file can be a device, a process, or a disk file. For a disk file, BATCHCOM appends output if the file exists, but creates an EDIT file if the file does not exist.
STATUS ATTACHMENT-SET Command Commands • • • ADP (an abbreviation of ASSIGNs, DEFINEs, and PARAMs) is an alias of the object keyword ATTACHMENT-SET. The STATUS ATTACHMENT-SET command displays attachment-set information in columnar format: Column Description ATTACHMENT SET Lists attachment-set names IN USE BY JOBS For each attachment set, lists the names and owners of jobs using the set. “None” appears if the set is not in use.
Commands • STATUS ATTACHMENT-SET Command The STATUS ATTACHMENT-SET command in this example lists attachment sets owned by NB.USER. The attachment-set-ID of M?2 restricts the listing to sets having three-character names beginning with M and ending with 2. 21} STATUS ATTACHMENT-SET (NB.USER)M?2 ATTACHMENT SET IN USE BY JOBS --------------------------------- --------------------------(NB.USER)MX2 None (NB.USER)MY2 None (NB.
STATUS EXECUTOR Command Commands 10} RESET ATTACHMENT-SET; STATUS ATTACHMENT-SET #CURRENT -^-0345E Undefined substitution STATUS EXECUTOR Command Use the STATUS EXECUTOR command to display executors’ names, CPUs, and states. If an executor is in use by a job, the command also displays the job’s number and its class name. S[TATUS] [ EXECUTOR ] [ / OU[T] [ file-name ] / ] executor-ID file-name specifies a command output file. The file can be a device, a process, or a disk file.
STATUS EXECUTOR Command Commands Table 6-7. Executor States State Description ACTIVE The executor is in use by a job. DELETE The executor is in use by a job. When the job finishes, the scheduler deletes the executor. An executor in the DELETE state can be: • • An executor that was the subject of a DELETE EXECUTOR command while in use by a job. A temporary executor. The scheduler creates temporary executors for all jobs with the AT attribute and all jobs operated on by the RUNNOW JOB command.
STATUS JOB Command Commands STATUS JOB Command Use the STATUS JOB command to display jobs’ numbers, names, owners, processing states, classes, SELPRI attributes, and log-file spooler-job numbers. The command also displays run statistics and information about executor-program processes. S[TATUS] [ JOB] [ / OU[T] [ file-name ] / ]{ job-ID } { ( [ [ NOT] job-ID ,] ... [NOT] filter [ , [NOT] filter ]...)} [SEL[PRI] ] [ DET[AIL] ] file-name specifies a command output file.
STATUS JOB Command Commands IN file-ID selects jobs that are using the specified input file or files. file-ID specifies an input-file name or a range of input-file names. To specify a range of input-file names, use the asterisk (*) and question mark (?) wild-card characters. STATUS JOB (IN \DEV.$DATA7.*.IN*) STATE state selects jobs that are in the specified state.
STATUS JOB Command Commands DETAIL causes BATCHCOM to display jobs’ run statistics and information about executorprogram processes. For details, see Figure 6-5 on page 6-168 and Figure 6-6 on page 6-169. Considerations • • • The STATUS JOB command is available to all users. The STATUS JOB display varies, depending on whether the command includes the DETAIL qualifier and whether jobs are executing, over limit, or suspended.
STATUS JOB Command Commands Prev 09SEP94 11:43:39 09SEP94 11:45:41 000:02:02 000:00:00 Next 09SEP94 11:48:38 - - List 09SEP94 11:45:42 - - Figure 6-5. Status JOB...
STATUS JOB Command Commands DELAY DL F $Z315 1,46 120 0:0:0 FORCED LOW , RUNNABLE Figure 6-6. JOB...
STATUS JOB Command Commands Table 6-8. Job States (page 2 of 4) State Description READY The job is available for execution. The scheduler selects it when an executor associated with the job’s class is available and no RUNNEXT or RUNNOW jobs are waiting. The job remains in the READY state if its class has the attribute INITIATION OFF or if the job was submitted when the scheduler has its attribute INITIATION OFF. This attribute prevents jobs belonging to the class from running.
STATUS JOB Command Commands Table 6-8. Job States (page 3 of 4) State Description n State Column Description 1 1:Hold The job is on hold for one of the first three reasons listed in the preceeding description of SPECIAL-n. 2 2:NB failed The job was running when an event other than the execution of an ABORT SCHEDULER or SHUTDOWN SCHEDULER command stopped its scheduler’s processes. Usually, this state results from execution of a TACL STOP command that specifies the job’s scheduler processes.
STATUS JOB Command Commands Table 6-8. Job States (page 4 of 4) State Description SUSPENDED The job was the subject of a SUSPEND JOB command. For more information, see SUSPEND JOB Command on page 6-190. To activate a suspended job, use the ACTIVATE JOB command. TAPE The job has the TAPEDRIVES attribute and requires more drives than are available. For more information, see TAPEDRIVES Job Attribute on page 7-109 and TAPEDRIVES Scheduler Attribute on page 7-110.
STATUS SCHEDULER Command Commands 322 323 324 325 326 327 328 329 330 331 332 333 • CAL-JOB-1 205,70 7:CAL error STANDARD-CLASS USERS 205,70 READY DEFAULT BACKUP 8,255 TAPE STANDARD-CLASS QUICK 8,1 RUN-NEXT DEFAULT ACCOUNTS 8,1 2115 5:Fail RsOn STANDARD-CLASS ADMIN 133,2 2117 6:Fail RsOffSTANDARD-CLASS CAL-JOB-2 205,70 8:CAL exprd STANDARD-CLASS STATISTICS 255,8 2119 2:NB failed STANDARD-CLASS URGENT 255,8 RUN-NOW URGENT-JOBS COMPILE 133,2 2122 SUSPENDED STANDARD-CLASS Q3 205,70 2123 EXECUTING STANDARD-
STATUS SCHEDULER Command Commands • • • The time displayed by the STATUS SCHEDULER command is the system date and time on the node where the scheduler process is running. The STATUS SCHEDULER command displays information about a scheduler’s executors, classes, jobs, job processes, attachment sets, and tape drives in columnar format. This table describes the contents of each column: Column Description EXECUTORS Lists the number of executors in each executor state.
STATUS-HISTORY Command Commands STATUS-HISTORY Command Use the STATUS-HISTORY command to list scheduler log-file events generated by a job. The command lists events from BEGIN (job initiation) through FINISH (job completion) for each run of the job. S[TATUS]-H[ISTORY] [ / OU[T] [ file-name ] / ] job-ID [ , N[B]-[LOG] log-file ] [ , RUN number ] [ , AF[TER] [ date ] [ time ] ] file-name specifies a command output file. The file can be a device, a process, or a disk file.
STATUS-HISTORY Command Commands time specifies the time from which BATCHCOM is to start searching for log-file events. You can enter the time in any of these forms. (For descriptions of the time forms, see AFTER Job Attribute on page 7-9.) [ h] h:[ m] m[:[ s] s]BBC[( AALVS1(A[M],P[M]) ) BBC[( AALVS1(MIDD[AY],NOO[N]) ) MIDN[IGHT] The start time of the current or most recent run applies if you omit time. Considerations • • • • The STATUS-HISTORY command is available to all users.
STATUS-HISTORY Command Commands • • The run number for a recurrent job (a job with the CALENDAR or EVERY attribute) increments by one each time the job runs. The run number for a nonrecurrent job is always one, no matter how many times the job runs. When STATUS-HISTORY command output goes to the current terminal, BATCHCOM displays the name of the log file being scanned on line 25. For example: Scanning : \MELRISK.$QA.ZBAT.
STOP EXECUTOR Command Commands STOP EXECUTOR Command Use the STOP EXECUTOR command to stop executors whose state is ACTIVE or ON. The command makes the executors unavailable for use by jobs and changes their state to OFF. STO[P] [ EXECUTOR ] [ / OU[T] [ file-name ] / ] executor-ID file-name specifies a command output file. The file can be a device, a process, or a disk file. For a disk file, BATCHCOM appends output if the file exists, but creates an EDIT file if the file does not exist.
STOP EXECUTOR Command Commands Executor RISC-3 stopped 88} STATUS EXECUTOR * EXECUTOR STATUS EXECUTOR CPU STATE JOB CLASS ------------------------ --- ------ ---- -------------------RISC-0 0 OFF RISC-1 1 OFF RISC-2 2 OFF RISC-3 3 OFF • This example lists the scheduler log file events recorded as a result of the previous STOP EXECUTOR * command: STOP EXECUTOR RISC-0 U_255,255 H_\MELBDEV.$ZTN0.#PTY4 UPDATE EXECUTOR RISC-0 S_OFF U_255,255 H_\MELBDEV.$ZTN0.#PTY4 STOP EXECUTOR RISC-1 U_255,255 H_\MELBDEV.
STOP JOB Command Commands STOP JOB Command Use the STOP JOB command to stop executing, over-limit, or suspended jobs. The command does not stop processes dissociated from a job by the TACL RUN command option JOBID or by the JOBID-ZERO job attribute. STO[P] [ JOB ] [ / OU[T] [ file-name ] / ] { job-ID } { ( [ [NOT] job-ID , ]… [NOT] filter [ , [NOT] filter ]… )} file-name specifies a command output file. The file can be a device, a process, or a disk file.
STOP JOB Command Commands To stop another user’s job if you have write access to its input file, specify the job’s full name or number in job-ID. • • • The STOP JOB command deletes nonrecurring jobs whose state is EXECUTING, OVER LIMIT, or SUSPENDED and whose attributes do not include HOLDAFTER ON. (A nonrecurring job does not have the CALENDAR or EVERY attribute.
STOP JOB Command Commands 225 CLEANUP 205,100 1645 3:NEWP.
SUBMIT JOB Command Commands > STATUS *, USER Process Pri PFR %WT Userid Program file Hometerm $C2 0,51 150 R 000 205,70 $SYS.SYS.TACL $TRM2.#A $Y 0,92 119 000 205,70 $SYS.SYS.DELAY $ZBAT $X 0,101 119 000 205,70 $SYS.SYS.DELAY $ZBAT $C2 B 2,22 150 001 205,70 $SYS.SYS.TACL $TRM2.#A SUBMIT JOB Command Use the SUBMIT JOB command to submit jobs to a scheduler. SUB[MIT] [ JOB ] [ / OU[T] [ file-name ] / ] [ job-name-1 ] [ , LIK[E] job-name-2 ] [ , attribute ]… file-name specifies a command output file.
SUBMIT JOB Command Commands CA[LENDAR] [ file-name ] CL[ASS] class-name DES[CRIPTION] " [ string ] " EV[ERY] [ weeks WEEK[S] ] [ days D[AYS] ] [ hours [ : mins ] [HOURS] ] [ hours H[OURS] [ mins MIN[UTES] ] ] [ crontab-entry ] E[XECUTOR]-P[ROGRAM] file-name EXT[SWAP] { $volume | file-name } HIG[HPIN] { OF[F] | ON } HOLD { OF[F] | ON } HOLDA[FTER] { OF[F] | ON } IF[FAILS] { OF[F] | ON } IN [ file-name ] J[OB]-L[OG] [ log-file ] J[OBID]-Z[ERO] { OF[F] | ON } LIB [ file-name ] LIM[IT] hours [ : mins ] MAXPRI
SUBMIT JOB Command Commands Table 6-9. Job Defaults (page 1 of 2) Attribute Default Value AFTER No AFTER attribute. AT No AT attribute. ATTACHMENT-SET No ATTACHMENT-SET attribute. CALENDAR No CALENDAR attribute. CLASS DEFAULT-CLASS scheduler attribute. DESCRIPTION No DESCRIPTION attribute. EVERY No EVERY attribute. EXECUTORPROGRAM DEFAULT-EXECUTOR-PROGRAM scheduler attribute. EXTSWAP No EXTSWAP attribute.
SUBMIT JOB Command Commands Table 6-9. Job Defaults (page 2 of 2) Attribute Default Value RUND No RUND attribute. SAVEABEND No SAVEABEND attribute. SELPRI DEFAULT-SELPRI scheduler attribute. STALL DEFAULT-STALL scheduler attribute. STARTUP No STARTUP attribute. STOP-ON-ABEND DEFAULT-STOP-ON-ABEND scheduler attribute. SWAP No SWAP attribute. Swap file created on volume specified by SWAP attribute of DEFINE=_DEFAULTS.
SUBMIT JOB Command Commands Considerations • • The SUBMIT JOB command is available to all users. When the scheduler accepts a submitted job, BATCHCOM displays a message that includes the scheduler-generated job number. For example: Job ZBAT-0088 Jobnumber 88 submitted You can use the job’s number instead of its name in commands that require you to specify a job. For example, to list the attributes of the job identified in the preceding message, enter INFO JOB ZBAT-0088 or INFO JOB 88.
SUBMIT JOB Command Commands • • ° Start of DST—clocks set ahead of local standard time (LST): Jobs due to run in the period lost run immediately after DST starts because their run times are then in the past. As a result, the jobs run earlier than expected by up to the amount of time lost. For example, DST starts at 0200 LST when clocks go forward one hour. A job submitted at 0130 LST with the attribute AT 02:30 runs at 0300 DST (that is, 30 minutes after submission instead of 60 minutes after).
SUBMIT JOB Command Commands jobid-zero: Off user: 133,2 23} SUBMIT JOB Job ZBAT-0089 Jobnumber 89 submitted 24} INFO JOB 89 JOB ATTRIBUTES for ZBAT-0089 jobnumber: 89 volume: \MELBDEV.$A.NB, "NCNU" out: \MELBDEV.$S.#BATCH executor-program: \MELBDEV.$SYSTEM.SYSTEM.
SUSPEND JOB Command Commands BEGIN JOB (FPP.USER)ZBAT-0092:1 E_E1 L_689 J_92 P_DELAY \MELBDEV.$Z714:17394989 U_205,70 UPDATE EXECUTOR E1 S_ACTIVE LIST JOB ZBAT-0092 EXECUTING J_92 START EXECUTOR-PROGRAM U_205,70 J_92 P_DELAY \MELBDEV.$Z714:17394989 STOP CC_0 EXECUTOR-PROGRAM J_92 \MELBDEV.$Z714:17394989 UPDATE EXECUTOR E1 S_ON FINISH JOB ZBAT-0092 T_0:0:0:12 J_92 P_DELAY DELETE JOB ZBAT-0092 J_92 SUSPEND JOB Command Use the SUSPEND JOB command to suspend executing processes associated with jobs.
SUSPEND JOB Command Commands Considerations • The SUSPEND JOB command is available to all users, but these conditions apply: ° ° NetBatch supervisors can suspend jobs belonging to any user. Users who are not NetBatch supervisors can suspend any job whose input file is a disk file to which they have write access. If the input file does not exist or is a device or process, only the owner and NetBatch supervisors can suspend the job.
SWITCHCPU SCHEDULER Command Commands Example This example shows SUBMIT JOB, SUSPEND JOB, and ACTIVATE JOB commands submitting, suspending, and reactivating a job and the resulting scheduler log-file events: > BATCHCOM $ZBAT; SUBMIT JOB, EXECUTOR-PROGRAM DELAY, STARTUP "4 MINS" Job ZBAT-0098 Jobnumber 98 submitted > BATCHCOM $ZBAT; SUSPEND JOB 98 Job ZBAT-0098 Jobnumber 98 suspended > BATCHCOM $ZBAT; ACTIVATE JOB 98 Job ZBAT-0098 Jobnumber 98 activated > FUP COPY LOGABO,,SHARE . .
SWITCHLOG SCHEDULER Command Commands Considerations • • • The SWITCHCPU SCHEDULER command is available to NetBatch supervisors only. The SWITCHCPU SCHEDULER command switches scheduler processes only between the current primary and backup CPUs. You cannot use the BACKUPCPU attribute with the command to specify a different backup CPU. You can omit the object keyword SCHEDULER from the SWITCHCPU SCHEDULER command only when SCHEDULER is the current assumed object.
SWITCHLOG SCHEDULER Command Commands log-file is the name of a scheduler log file. The file can be a device, a process, or any type of unstructured disk file except an EDIT file. If you specify a disk file, these conditions apply: • • If the file exists and is not an EDIT file, the scheduler opens it and appends events. If the file is an EDIT file, the command fails. If the file does not exist or if you omit log-file, the scheduler creates a file (file code 847) named svol.LOGxxx.
SYSTEM Command Commands Scheduler 3} STATUS SCHEDULER Process : Database: Logfile : . • logfile switched SCHEDULER STATUS \MELBDEV.$TEST Primary : 0,60 Backup : 1,41 \MELBDEV.$DATA7.TEST \MELBDEV.$DATA7.TEST.LOGAAB . These examples list the scheduler log file events that record the results of the previous SWITCHLOG SCHEDULER command: ° Last event in log file $NB.LOGS.TESTLOG: LOG \MELBDEV.$NB.LOGS.TESTLOG TO \MELBDEV.$DATA7.TEST.LOGAAB ° First two events in log file $DATA7.TEST.
VOLUME Command Commands file if the file does not exist. If you specify / OUT / (that is, omit file-name), BATCHCOM suppresses output. node is a node name. The default is the node where the process that creates the BATCHCOM process is running. Considerations • • The SYSTEM command is available to all users. Entering SYSTEM by itself resets the default node to the node current at the start of the session. Example This example shows the effect of two SYSTEM commands.
VOLUME Command Commands volume is one of: $volume-name.subvolume-name are volume and subvolume names. $volume-name is a volume name. subvolume-name is a subvolume name. If you specify subvolume-name but omit $volumename, BATCHCOM resets the default volume to the volume from the current TACL environment. security is a four-character string specifying Guardian security for read, write, execute, and purge (RWEP) file access.
! Command Commands command changes the current default node, volume, and subvolume. For example: 1} VOLUME VOLUME $SYSTEM.NETBATCH, "NNNC" 2} SHOW ATTACHMENT-SET DEFINE =_DEFAULTS ATTACHMENT-SET ATTRIBUTES attachments: DEFINE =_DEFAULTS, CLASS DEFAULTS, VOLUME $SYSTEM.NETBATCH 3} VOLUME \MELBQAT.$QAT2.ISPFILES VOLUME \MELBQAT.$QAT2.ISPFILES, "NNNC" 4} SHOW ATTACHMENT-SET DEFINE =_DEFAULTS ATTACHMENT-SET ATTRIBUTES attachments: DEFINE =_DEFAULTS, CLASS DEFAULTS, VOLUME \MELBQAT.$QAT2.
! Command Commands num is a positive integer identifying a line in the history buffer. - num is a negative integer identifying a line in the history buffer relative to the current line. text is a character string identifying the latest line in the history buffer beginning with the string. Considerations • • The ! command is available to all users.
? Command Commands • To execute the fourth command line preceding the current command line: 7} ! -4 7} SWITCHCPU SCHEDULER Scheduler CPUs switched 8} • To execute the latest command line that begins with ST: 7} ! ST 7} STATUS SCHEDULER SCHEDULER STATUS Process : \MELBDEV.$SCHD Primary : 1,67 Backup : 3,38 Database: \MELBDEV.$DATA7.SCHD Logfile : \MELBDEV.$DATA7.SCHD.LOGAAE Time : 06OCT94 12:42:19 . .
? Command Commands • BATCHCOM stores all commands in its history buffer except CHANGEUSER, COMMENT, and HISTORY. Examples These examples of the ? command relate to these commands in the history buffer: 3} 4} 5} 6} 7} 8} 9} • STATUS SCHEDULER ASSUME JOB SUBMIT TRIAL-BAL, IN TB, OUT $S, WAITON (MISC-DR, MISC-CR) SUBMIT MISC-DR, IN MSCDR, OUT $S, WAITON MISC-CR SUBMIT MISC-CR, IN MSCCR, OUT $S, HOLD ON ALTER SCHEDULER, DEFAULT-OUT $S.
? Command Commands NetBatch Manual—522460-004 6 -202
7 Attributes This section describes the syntax, operation, and results of all attachment-set, class, execurot, job, and scheduler attributes: Topic Page Attribute Reference Summary 7-1 Attribute Descriptions 7-8 For information on abbreviating attribute keywords and a list of keyword aliases, see Keywords on page 6-7. Attribute Reference Summary This subsection is a quick-reference guide to the syntax of attachment-set, class, executor, job, and scheduler attributes.
Executor Attributes Attributes Executor Attributes • CLASS specifies an executor’s classes: CL[ASS] { class-name | ( class-name [ ‚ class-name ]… ) | *) } • CPU assigns an executor to a CPU: CP[U] cpu-number Job Attributes • AFTER specifies the date and time after which a job becomes eligible for execution. The attribute also enables you to change a nonexecuting job’s AT attribute to AFTER.
Job Attributes Attributes • EXECUTOR-PROGRAM specifies the program file of the program the scheduler starts as the initial process of a job: E[XECUTOR]-P[ROGRAM] file-name • EXTSWAP specifies the name of the swap file for the default extended data segment of a job’s executor-program process: EXT[SWAP] { $volume-name | file-name } • HIGHPIN determines whether a job’s executor-program process runs at a low PIN or at a high PIN (available only in D20 or later versions of the NetBatch product): HIG[HPIN]
Job Attributes Attributes • MAXPRINTPAGES specifies the maximum number of print pages for a job’s spooler output file: MAXPRINTP[AGES] { number | NON[E] } • MEM specifies the minimum number of 2048-byte memory pages allotted to a job’s executor-program process for user data: ME[M] number • NAME specifies a name for a job’s executor-program process: NA[ME] $process-name • OUT specifies the output file to which the scheduler writes data produced by an executing job: OU[T] [ file-name ] • PFS specif
Job Attributes Attributes • STALL determines whether the scheduler puts in the SPECIAL-9 state a failed job it would otherwise reschedule or delete. The attribute works in combination with the job’s IFFAILS, RESTART, and STOP-ON-ABEND attributes.
Scheduler Attributes Attributes Scheduler Attributes • AT-ALLOWED determines whether users without execute access to the NETBATCH program file (that is, users who are not NetBatch supervisors) can submit jobs with the AT attribute: AT-A[LLOWED] { OF[F] | ON } • BACKUPCPU specifies the preferred CPUs for a scheduler’s backup process: B[ACKUPCPU] { cpu-number-1 [ ‚ cpu-number-2 ] | * } • CATCHUP determines whether jobs with the EVERY attribute accumulate run backlogs: CAT[CHUP] { OF[F] | ON } • DEFA
Scheduler Attributes Attributes • DEFAULT-SELPRI specifies the selection priority of a job submitted without the SELPRI attribute: D[EFAULT]-SE[LPRI] number • DEFAULT-STALL specifies the STALL attribute of a job submitted without that attribute: D[EFAULT]-ST[ALL] { OF[F] | ON } • DEFAULT-STOP-ON-ABEND specifies the STOP-ON-ABEND attribute of a job submitted without that attribute: D[EFAULT]-[STOP]-[ON]-[ABEND] { OF[F] | ON } • EMS enables or disables event-message generation while the scheduler is
Attribute Descriptions Attributes Attribute Descriptions This subsection contains descriptions and examples of the syntax, operation, and results of all attributes, in alphabetical order by object type: • Attachment-set attributes: ASSIGN • DEFINE PARAM SECURITY TEMPORARY Class attribute: INITIATION • Executor attributes: CLASS • • CPU Job attributes: AFTER IN RESTART AT JOB-ZERO RUND ATTACHMENT-SET JOBID-ZERO SAVEABEND CALENDAR LIB SELPRI CLASS LIMIT STALL DESCRIPTION MAXPRI
AFTER Job Attribute Attributes AFTER Job Attribute The AFTER job attribute specifies the date and time after which a job becomes eligible for execution. The attribute also lets you change a nonexecuting job’s AT attribute to AFTER. AF[TER] [ date ] [ time ] date is the date on which the job becomes eligible for execution.
AFTER Job Attribute Attributes as the sum plus 100. For example, in 1993, BATCHCOM interprets 05 as the year 2005, 67 as 2067, and 94 as 1994. day is a day of the week. day causes BATCHCOM to generate an AFTER date of the next day whose name matches day. The options are: MON[DAY] WED[NESDAY] FRI[DAY] TUE[SDAY] THU[RSDAY] SAT[URDAY] SUN[DAY] [ d] d mmm and mmm [ d] d refer to the current year. To use one of these date forms and specify time, time must appear before date, not after.
AFTER Job Attribute Attributes MIDN[IGHT] specifies the middle of the night (specifically, 12 o’clock at night). The time 00:00:00 applies if you omit time. Considerations • The scheduler treats a job submitted without the AFTER, AT, or WAIT attributes like a job with the attribute WAIT 0:0. Such a job is eligible to run immediately on submission unless delayed by another attribute such as HOLD or TAPEDRIVES. • The AFTER, AT, and WAIT job attributes are mutually exclusive.
ASSIGN Attachment-Set Attribute Attributes Example This example shows the AFTER attribute of a job specifying the time after which the job becomes eligible for execution: 25} SUBMIT JOB YEAR-END, AFTER 31DEC94 MIDDAY Job YEAR-END Jobnumber 23 submitted 26} STATUS JOB YEAR-END JOB STATUS JOB JOBNAME USERID LOG STATE CLASSNAME ---- ---------------- ------- ---- ----------- --------23 YEAR-END 255,255 31DEC94 DEFAULT 27} INFO JOB YEAR-END, AFTER JOB ATTRIBUTES for YEAR-END jobnumber: 23 after: 31DEC94 12:00:
ASSIGN Attachment-Set Attribute Attributes ASSIGN-attributes specifies ASSIGN attributes in this form. For descriptions of the options for each syntax item, see the description of the ASSIGN command in theTACL Reference Manual. logical-unit , actual-file-name [ , create-open-spec ]… logical-unit is the name to use as a substitute for the actual file name, specified in one of these forms: [ logical-file program-unit.logical-file *.
ASSIGN Attachment-Set Attribute Attributes Job Y job number 270 submitted > FUP COPY OUTFILE TACL (T9205Dxx - DDMMMYY), Operating System Dxx . . ASSIGN DAILY-LOG Physical file: $DATA7.LOGS.DAYLOG FILE-A Physical file: $NB.NEWFILE.A Primary extent: 100 Secondary extent: 200 File code: 789 Exclusion: EXCLUSIVE Access: INPUT Record: 1024 Block: 4096 • This example shows various attachment-set commands adding, altering, and displaying an attachment set’s ASSIGN attributes.
AT Job Attribute Attributes attachments: ASSIGN ASSIGN ACCNTS-JRNL, PROTECTED, I-O, EXT 905, REC 512, BLOCK ASSIGN ACCNTS-PYBL, ACCNTS-GLDGR, $A.ACCOUNTS.GLDGR $A.ACCOUNTS.JRNL, (256,512), CODE 2048 $DATA7.ADMIN.PYBL AT Job Attribute The AT job attribute specifies the date and time at which the scheduler is to execute a job. The attribute makes the scheduler create a temporary executor for the job. AT [ date ] [ time ] date is the date on which the scheduler executes the job.
AT Job Attribute Attributes • Users without execute access to the NETBATCH program file (that is, users who are not NetBatch supervisors) cannot submit jobs with the AT attribute when the scheduler’s AT-ALLOWED attribute is set to OFF (the default value). For more information, see AT-ALLOWED Scheduler Attribute on page 7-18. • The scheduler creates temporary executors for all jobs with the AT attribute and for all jobs that are operated on by the RUNNOW JOB command.
AT Job Attribute Attributes • To change a nonexecuting job’s AT attribute to \AFTER, use the ALTER JOB command to specify AFTER without date and time. (Omitting date and time leaves intact the original date and time.
AT-ALLOWED Scheduler Attribute Attributes AT-ALLOWED Scheduler Attribute The AT-ALLOWED scheduler attribute determines whether users without execute access to the NETBATCH program file (that is, users who are not NetBatch supervisors) can submit jobs with the AT attribute. (Jobs with the AT attribute create temporary executors that can overload your system. Preventing nonprivileged users from using the attribute helps you prevent system overload.
ATTACHMENT-SET Job Attribute Attributes ATTACHMENT-SET Job Attribute The ATTACHMENT-SET job attribute assigns up to three attachment sets to a job. You also can use the attribute to dissociate attachment sets from a job. A[TTACHMENT]-S[ET] [ attachment-set ( attachment-set [ attachment-set ]… ) ] attachment-set specifies an attachment set in one of these forms: [ ( user-ID ) ] attachment-set-ID user-ID specifies the user ID of the attachment-set owner. (user-ID must be in group-name.
ATTACHMENT-SET Job Attribute Attributes Considerations • You must have execute access to the attachment set you want to assign to a job. For example, NB.USER can assign set (SUPER.SUPER)ADP2 to a job if the set’s security is “OAAA” but not if the security is “OAGA.” • A job can have up to three attachment sets. The order in which you specify the sets is the order in which the scheduler supplies them to the job.
ATTACHMENT-SET Job Attribute Attributes Attachment-set commands that do not affect the #CURRENT variable are ASSUME, DELETE, INFO, SHOW, and STATUS. • ADP (an abbreviation of ASSIGNs, DEFINEs, and PARAMs) is an alias of the attribute keyword ATTACHMENT-SET. Examples • This example shows the ATTACHMENT-SET attribute assigning, changing, and dissociating a job’s attachment set: 37} SUBMIT JOB COMPILE-JOB, IN BUILD, OUT =OUT, HOLD ON, ATTACHMENT-SET (NB.
ATTACHMENT-SET Job Attribute Attributes null value (shown by the “undefined substitution” message). The set’s attributes come from the working-attributes set. 67} CHANGEUSER SUPER.FPP psswrd 67} SHOW ATTACHMENT-SET ATTACHMENT-SET ATTRIBUTES security: "NNNN" temporary: Off attachments: DEFINE =_DEFAULTS, CLASS DEFAULTS, VOLUME $A.B ASSIGN P, Q PARAM X Y 68} INFO ATTACHMENT-SET #CURRENT, DETAIL -^-0345E Undefined substitution 69} SUBMIT JOB TEST, HOLD ON, ATTACHMENT-SET #CURRENT Attachment-set (SUPER.
BACKUPCPU Scheduler Attribute Attributes ATTACHMENT-SET ATTRIBUTES attachments: DEFINE =OUT, CLASS SPOOL, LOC \MELBQAT.$S DEFINE =_DEFAULTS, CLASS DEFAULTS, VOLUME $SYSTEM.NETBATCH ASSIGN A, $DATA7.NB.A ASSIGN B, $BIG1.USERS.B PARAM DAY THURSDAY PARAM DATE 18NOV93 2} INFO ATTACHMENT-SET #CURRENT, DETAIL -^-0345E Undefined substitution 3} SUBMIT JOB X, HOLD ON, ATTACHMENT-SET #CURRENT Attachment-set (SUPER.
BACKUPCPU Scheduler Attribute Attributes * specifies any available CPU on the scheduler’s node. The scheduler selects the CPU at random. Considerations • • The default value of the BACKUPCPU attribute when cold starting a scheduler is the number of the CPU of the scheduler’s primary process. When cpu-number-1 or cpu-number-2 specifies a nonexistent CPU, the command fails with a message advising the allowable CPU number range for the node.
CALENDAR Job Attribute Attributes Name Primary Backup Ancestor $ZBAT 0,51 2,58 $X849 • This example shows that the BACKUPCPU attribute has no effect on the result of a SWITCHCPU SCHEDULER command: > BATCHCOM $ZBAT; INFO SCHEDULER, BACKUPCPU SCHEDULER ATTRIBUTES backupcpu: 1,3 > PPD $ZBAT Name Primary Backup Ancestor $ZBAT 0,51 2,58 $X849 > BATCHCOM $ZBAT; SWITCHCPU SCHEDULER Scheduler CPUs switched > PPD $ZBAT Name Primary Backup Ancestor $ZBAT 2,58 0,51 $X849 CALENDAR Job Attribute The CALENDAR job at
CALENDAR Job Attribute Attributes • The scheduler accepts a job whose CALENDAR attribute specifies a nonexistent calendar file, but puts the job in the SPECIAL-7 state. For example: 5} SUBMIT JOB X, CALENDAR NOFILE Job X job number 331 submitted 0531-W Error 11 opening CALENDAR file. 6} STATUS JOB X JOB JOBNAME USERID LOG STATE CLASSNAME ---- ---------------- ------- ---- ----------- --------331 X 205,70 7:CAL error DEFAULT Error 11 in message 0531-W is the file-system error “file not found.
CALENDAR Job Attribute Attributes ° ° • • A job can have one of the attributes, but not both. CALENDAR overrides EVERY when assigned to a job whose attributes include EVERY, and EVERY overrides CALENDAR when assigned to a job whose attributes include CALENDAR.
CATCHUP Scheduler Attribute Attributes CATCHUP Scheduler Attribute The CATCHUP scheduler attribute determines whether jobs with the EVERY attribute accumulate run backlogs. Run backlogs can accumulate when the jobs are on hold or suspended for longer than the EVERY interval or run for longer than the interval. CAT[CHUP] { OF[F] | ON } OFF prevents job run backlogs from accumulating.
CATCHUP Scheduler Attribute Attributes • This example shows how a recurrent suspended job functions when reactivated and CATCHUP is set to ON. The job runs continuously until it clears the run backlog it accumulated while suspended, then it runs at the specified interval.
CLASS Executor Attribute Attributes Job CATCHUP-NO Jobnumber 2 activated 8} STATUS JOB 2 JOB JOBNAME USERID LOG STATE CLASSNAME ---- ---------------- ------- ---- ----------- --------2 CATCHUP-NO 255,255 4393 15:48:48 DEFAULT 9} STATUS-HISTORY 2, NB-LOG $DATA7.ZBAT.LOGAAI 16SEP94 15:42:51 BEGIN JOB (SUPER.
CLASS Executor Attribute Attributes • The order in which you assign classes to an executor determines the order in which the scheduler scans them for jobs. For example, assigning classes B and A to an executor (in that order) makes the scheduler scan class B before it scans class A. Jobs in class B therefore run before jobs in class A. • • You can assign a class to more than one executor.
CLASS Job Attribute Attributes • This example shows an executor adopting its CLASS attribute from the DEFAULTCLASS scheduler attribute: 56} INFO SCHEDULER, DEFAULT-CLASS SCHEDULER ATTRIBUTES default-class: STANDARD 57} SHOW EXECUTOR EXECUTOR ATTRIBUTES 58} ADD EXECUTOR CPU-0, CPU 0 Executor CPU-0 added 59} INFO EXECUTOR CPU-0 EXECUTOR ATTRIBUTES for CPU-0 cpu: 0 classes: STANDARD CLASS Job Attribute The CLASS job attribute specifies the class to which a job belongs.
CLASS Job Attribute Attributes • JOBCLASS is an alias of the attribute keyword CLASS. Example This example shows a job adopting its CLASS attribute from the scheduler’s DEFAULT-CLASS attribute. The class has the attribute INITIATION OFF, which prevents the job from running, as does the executor whose state is OFF. The example shows the correction of both these conditions, which enables the job to run.
CPU Executor Attribute Attributes CPU Executor Attribute The CPU executor attribute assigns an executor to a CPU. This assignment lets the scheduler execute in the CPU the initial processes (the executor programs) of jobs in the executor’s classes. CP[U] cpu-number cpu-number is the number of a CPU configured for the scheduler’s node. If you specify a nonexistent CPU, BATCHCOM displays a message advising the allowable CPU number range for the node.
CPU Executor Attribute Attributes on page 7-64, RESTART Job Attribute on page 7-95, STALL Job Attribute on page 7-102, and STOP-ON-ABEND Job Attribute on page 7-105. Examples • This example shows the CPUs of a job’s processes. The job’s TACL executorprogram process $X228 runs in CPU 0 (specified by the CPU attribute of the job’s executor). FUP processes $X and $Y created by the TACL process run in the CPU specified by their RUN commands. FUP process $Z runs in the CPU of the TACL process.
DEFAULT-CLASS Scheduler Attribute Attributes 10} INFO EXECUTOR DEV-1, CPU 2087-E EXECUTOR DEV-1 does not exist 11} ADD EXECUTOR DEV-1, CLASS *, CPU 4 2074-E CPU must be 0 to 3 12} ADD EXECUTOR DEV-1, CLASS *, CPU 3 Executor DEV-1 added 13} OPEN \MELBQAT.
DEFAULT-CLASS Scheduler Attribute Attributes > BATCHCOM $ZBAT; START SCHEDULER Scheduler started > BATCHCOM $ZBAT; INFO SCHEDULER, DEFAULT-CLASS SCHEDULER ATTRIBUTES default-class: DEFAULT > BATCHCOM $ZBAT; INFO CLASS DEFAULT 2105-E CLASS DEFAULT does not exist > BATCHCOM $ZBAT; ADD CLASS DEFAULT, INITIATION OFF Class DEFAULT added > BATCHCOM $ZBAT; INFO CLASS DEFAULT CLASS ATTRIBUTE for DEFAULT initiation: Off • This example shows a job adopting its CLASS attribute from the scheduler’s DEFAULT-CLASS at
DEFAULT-EXECUTOR-PROGRAM Scheduler Attribute Attributes • This example shows an ADD EXECUTOR command specifying an executor’s CLASS attribute, thus overriding the scheduler’s DEFAULT-CLASS attribute: 35} INFO SCHEDULER, DEFAULT-CLASS SCHEDULER ATTRIBUTES default-class: BUILDS 36} ADD EXECUTOR DEVELOPMENT, CPU 2, CLASS COMPILES Executor DEVELOPMENT added 37} INFO EXECUTOR DEVELOPMENT, CLASS EXECUTOR ATTRIBUTES for DEVELOPMENT classes: COMPILES DEFAULT-EXECUTOR-PROGRAM Scheduler Attribute The DEFAULT-EXEC
DEFAULT-HIGHPIN Scheduler Attribute Attributes Job BC job number 322 submitted 13} INFO JOB BC, EXECUTOR-PROGRAM JOB ATTRIBUTES for BC jobnumber: 322 executor-program: $QAT2.T9190D20.BATCHCOM DEFAULT-HIGHPIN Scheduler Attribute The DEFAULT-HIGHPIN scheduler attribute (available in D20 or later versions of the NetBatch product) specifies the HIGHPIN attribute of a job submitted without that attribute. For more information, see HIGHPIN Job Attribute on page 7-61.
DEFAULT-MAXPRINTLINES Scheduler Attribute Attributes DEFAULT-MAXPRINTLINES Scheduler Attribute The DEFAULT-MAXPRINTLINES scheduler attribute specifies the maximum number of output-file print lines of a job submitted without the MAXPRINTLINES attribute. For more information, see MAXPRINTLINES Job Attribute on page 7-82. D[EFAULT]-MAXPRINTL[INES] { number | NON[E] number is a number in the range 120 through 65534 specifying the maximum number of print lines. NONE specifies no maximum.
DEFAULT-MAXPRINTPAGES Scheduler Attribute Attributes scheduler’s DEFAULT-MAXPRINTLINES and DEFAULT-MAXPRINTPAGES attributes: 11} INFO SCHEDULER, DEFAULT-MAXPRINTLINES, DEFAULTMAXPRINTPAGES SCHEDULER ATTRIBUTES default-maxprintlines: 600 default-maxprintpages: None 12} SUBMIT JOB MPL-2, MAXPRINTLINES NONE, MAXPRINTPAGES 10 Job MPL-2 job number 273 submitted 13} INFO JOB MPL-2, MAXPRINTLINES, MAXPRINTPAGES JOB ATTRIBUTES for MPL-2 jobnumber: 273 maxprintlines: None maxprintpages: 10 DEFAULT-MAXPRINTPAGES S
DEFAULT-OUT Scheduler Attribute Attributes Examples • This example shows a job adopting its MAXPRINTLINES and MAXPRINTPAGES attributes from the scheduler’s DEFAULT-MAXPRINTLINES and DEFAULTMAXPRINTPAGES attributes: 15} INFO SCHEDULER, DEFAULT-MAXPRINTLINES, DEFAULTMAXPRINTPAGES SCHEDULER ATTRIBUTES default-maxprintlines: 1200 default-maxprintpages: None 16} SUBMIT JOB MPP-1 Job MPP-1 job number 274 submitted 17} INFO JOB MPP-1, MAXPRINTLINES, MAXPRINTPAGES JOB ATTRIBUTES for MPP-1 jobnumber: 274 maxprin
DEFAULT-PRI Scheduler Attribute Attributes Examples • This example shows a job adopting its OUT attribute from the scheduler’s DEFAULT-OUT attribute: 9} INFO SCHEDULER, DEFAULT-OUT SCHEDULER ATTRIBUTES default-out: \MELBDEV.$S.#BATCH 10} SUBMIT JOB DO1 Job DO1 Jobnumber 1 submitted 11} INFO JOB DO1, OUT JOB ATTRIBUTES for DO1 jobnumber: 1 out: \MELBDEV.$S.
DEFAULT-SELPRI Scheduler Attribute Attributes default-pri: 120 4} SUBMIT JOB PRI-1 Job PRI-1 job number 276 submitted 5} INFO JOB PRI-1, PRI JOB ATTRIBUTES for PRI-1 jobnumber: 276 pri: 120 • This example shows a SUBMIT JOB command specifying a job’s PRI attribute, thus overriding the scheduler’s DEFAULT-PRI attribute: 11} INFO SCHEDULER, DEFAULT-PRI SCHEDULER ATTRIBUTES default-pri: 99 12} SUBMIT JOB PRI-2, PRI 149 Job PRI-2 job number 278 submitted 13} INFO JOB PRI-2, PRI JOB ATTRIBUTES for PRI-2 jobn
DEFAULT-STALL Scheduler Attribute Attributes • This example shows SUBMIT JOB command specifying a job’s SELPRI attribute, thus overriding the scheduler’s DEFAULT-SELPRI attribute: 17} INFO SCHEDULER, DEFAULT-SELPRI SCHEDULER ATTRIBUTES default-selpri: 5 18} SUBMIT JOB B, HOLD ON, SELPRI 4 Job B job number 316 submitted 19} INFO JOB B, SELPRI JOB ATTRIBUTES for B jobnumber: 316 selpri: 4 DEFAULT-STALL Scheduler Attribute The DEFAULT-STALL scheduler attribute specifies the STALL attribute of a job submitt
DEFAULT-STOP-ON-ABEND Scheduler Attribute Attributes DEFAULT-STOP-ON-ABEND Scheduler Attribute The DEFAULT-STOP-ON-ABEND scheduler attribute specifies the STOP-ON-ABEND attribute of a job submitted without that attribute. For more information, see STOP-ONABEND Job Attribute on page 7-105. D[EFAULT]-[STOP]-[ON]-[ABEND] { OF[F] | ON } Consideration A scheduler adopts the attribute DEFAULT-STOP-ON-ABEND OFF by default when cold started.
DEFINE Attachment-Set Attribute Attributes DEFINE Attachment-Set Attribute The DEFINE attachment-set attribute specifies the name and attributes of a DEFINE. (A DEFINE is a named set of attributes and associated values.) The scheduler passes the DEFINE to the executor-program process of a job using the attachment set when the job starts. ( DEFI[NE] DEFINE-name-1 , [ LIK[E] DEFINE-name-2 , ] [ CLASS DEFINE-class , ] DEFINE-attribute [ , DEFINE-attribute ]… ) DEFINE-name-1 is the name of a DEFINE.
DEFINE Attachment-Set Attribute Attributes Table 7-1. DEFINE Types (Classes) Type Description CATALOG Specifies the location of a SQL/MP catalog. You can enter the logical name of the catalog DEFINE instead of a catalog name in, for example, CATALOG clauses in NonStop SQL/MP data definition language (DDL) statements. DEFAULTS Holds the standard default values of a process such as the default volume. MAP Redirects or substitutes a file.
DEFINE Attachment-Set Attribute Attributes Table 7-2.
DEFINE Attachment-Set Attribute Attributes Table 7-2. DEFINE Attributes (page 3 of 3) Type Attributes SPOOL BATCHNAME batch-name COPIES num FORM form-name HOLD { OFF | ON } HOLDAFTER { OFF | ON } LOC [ \node. ] $collector [ .#group-name [ .dest ] ] MAXPRINTLINES num MAXPRINTPAGES num OWNER { group-name.
DEFINE Attachment-Set Attribute Attributes Consideration For more information on DEFINEs, see the TACL Reference Manual and the TACL Programming Guide. Examples • This example shows the scheduler passing DEFINEs from a job’s attachment set to the job’s TACL executor-program process: > LOGON NB.USER, psswrd > FUP COPY INFILE INFO DEFINE **, DETAIL > BATCHCOM $ZBAT; ADD ATTACHMENT-SET D, (DEFINE =_DEFAULTS, CLASS DEFAULTS, VOLUME $A.
DESCRIPTION Job Attribute Attributes ATTACHMENT-SET ATTRIBUTES attachments: DEFINE =TAPE1, CLASS TAPE, VOLUME "30 ", LABELS ANSI, FILEID BACKUPS, DEVICE \MELBDEV.$TAPE DEFINE =_DEFAULTS, CLASS DEFAULTS, VOLUME $DATA7.DEVBAKUP 2} SET ATTACHMENT-SET (DEFINE =TAPE2, LIKE =TAPE1, MOUNTMSG "DAILY BACKUPS ONLY", DEVICE \MELBQAT.$TAPE) 3} ADD ATTACHMENT-SET BKUPS, (DEFINE =TAPE3, LIKE =TAPE2, DEVICE \MELBORN.$TAPE) Attachment-set (FPP.
DESCRIPTION Job Attribute Attributes • BATCHCOM breaks lines when their length exceeds 70 characters. To force a line break, enter a percent (%) character where you want the break to occur. Characters preceded by a backslash (\) are treated as literal characters.
EMS Scheduler Attribute Attributes EMS Scheduler Attribute The EMS scheduler attribute enables or disables event-message generation while the scheduler is running. For information about NetBatch event messages, see the NetBatch Management Programming Manual. EM[S] { ER[RORS] OF[F] ON) ERRORS enables generation of all scheduler event messages except 102 (ZBAT-EVT-JOBSTART) and 202 (ZBAT-EVT-JOB-NORMAL-STOP). OFF disables generation of all scheduler event messages.
EVERY Job Attribute Attributes EVERY Job Attribute The EVERY job attribute specifies that job execution occur at regular, specified intervals. EV[ERY] [ weeks WEEK[S] days D[AYS] hours [ : mins ] [HOURS] hours H[OURS] [ mins MIN[UTES] ] crontab-entry ] weeks is an integer in the range 1 through 52 specifying the interval in seven-day weeks. days is an integer in the range 1 through 365 specifying the interval in days. hours is an integer in the range 0 through 168 specifying the interval in hours.
EVERY Job Attribute Attributes Each crontab-entry field can contain: • • • • A number in the specified range Two numbers separated by a dash to indicate an inclusive range A list of numbers separated by commas, which selects all numbers in the list An asterisk (*), meaning all legal values The specification of days can be made by two fields ( day-of-month and dayof-week). If you specify both as a list of elements, both are adhered to.
EVERY Job Attribute Attributes • • For information about how the scheduler treats a recurrent job that fails, see IFFAILS Job Attribute on page 7-64, RESTART Job Attribute on page 7-95, STALL Job Attribute on page 7-102, STOP-ON-ABEND Job Attribute on page 7-105. For information about recurrent jobs that are also dependent jobs, see WAITON Job Attribute on page 7-119. Examples • This example shows the submission of a job whose EVERY attribute specifies execution at five-minute intervals.
EXECUTOR-PROGRAM Job Attribute Attributes minutes: 0 hours: 12 days: 14 months: 2 weekday: * EXECUTOR-PROGRAM Job Attribute The EXECUTOR-PROGRAM job attribute specifies the program file of the program the scheduler starts as the initial process of a job. E[XECUTOR]-P[ROGRAM] file-name file-name is the name of a program file. BATCHCOM expands a partially qualified executor-program file name by using the defaults specified in the last VOLUME command.
EXECUTOR-PROGRAM Job Attribute Attributes Example This example shows execution of a TACL job that starts three FUP processes. (The job inherits its EXECUTOR-PROGRAM attribute from the scheduler.) The example also shows the home terminals of the job’s processes. The TACL executor-program process $Y561 uses the scheduler process $ZBAT as its home terminal. FUP processes $EP1 and $EP2 created by the TACL process use the home terminals specified by their RUN commands.
EXTSWAP Job Attribute Attributes EXTSWAP Job Attribute The EXTSWAP job attribute specifies the name of the swap file for the default extended data segment of a job’s executor-program process. The file provides space for memory swaps of the default extended data segment during process execution. EXT[SWAP]BBC{( AALVS1($volume-name, file-name) ) volume-name is the name of the volume where the executor-program process is to create a temporary swap file.
HIGHPIN Job Attribute Attributes jobnumber: 5 extswap: \MELBDEV.$TRASH.ZBAT.EXTSWAP > STATUS *, GMOMJOBID $ZBAT.5, DETAIL . . Current Extended Swap File Name: $TRASH.ZBAT.EXTSWAP . . GMOMJOBID: $ZBAT.5 HIGHPIN Job Attribute The HIGHPIN job attribute determines whether a job’s executor-program process runs at a low PIN or at a high PIN. The attribute is available only in D20 or later versions of the NetBatch product.
HOLD Job Attribute Attributes Example This example shows the HIGHPIN job attribute making the scheduler run a job’s executor-program process at a high PIN (PIN 267): > BATCHCOM $ZBAT; SUBMIT JOB FILES, IN FILES, EXECUTORPROGRAM TACL, HIGHPIN ON Job FILES job number 399 submitted > STATUS *, GMOMJOBID $ZBAT.399 Process … Program file Hometerm $Z0279 1,267 … $SYSTEM.SYS00.TACL $ZBAT HOLD Job Attribute The HOLD job attribute determines whether a job is available for execution.
HOLDAFTER Job Attribute Attributes ° A job on hold whose attributes include CALENDAR does not accumulate a run backlog while held. When you change the job’s HOLD attribute to OFF, the job runs again at the next future CALENDAR time. For more information about run backlogs, see ACTIVATE JOB Command on page 6-32. • To make a job in the SPECIAL-1 state eligible for execution, alter its HOLD attribute from ON to OFF.
IFFAILS Job Attribute Attributes • The scheduler treats a job submitted without the HOLDAFTER attribute like a job with the attribute HOLDAFTER OFF. • The scheduler puts a recurring job with the HOLDAFTER ON attribute in the • To make a job in the SPECIAL-1 state eligible for execution, alter its HOLD SPECIAL-1 state, not the TIME state, after execution finishes. (A recurring job has the CALENDAR or EVERY attribute.) attribute from ON to OFF.
IFFAILS Job Attribute Attributes • The cause of the failure (for example, the job’s executor-program process abends) For more information, see Table 4-5, Job States on Process Failure, on page 4-28, RESTART Job Attribute on page 7-95, STALL Job Attribute on page 7-102, and STOPON-ABEND Job Attribute on page 7-105. ON causes the scheduler to reschedule the job if it fails and is recurrent, depending on the values of the job’s RESTART, STALL, and STOP-ON-ABEND attributes.
IN Job Attribute Attributes $Z585 … $SYSTEM.SYS00.TACL $ZBAT > STATUS *, GMOMJOBID $ZBAT.433 Process … Program file Hometerm … $SYSTEM.SYS00.DELAY $ZBAT $Z586 … $SYSTEM.SYS00.TACL $ZBAT > STOP $Z585 > STOP $Z586 > BATCHCOM $ZBAT; STATUS JOB * JOB STATUS JOB JOBNAME USERID LOG STATE CLASSNAME ---- ---------------- ------- ---- ----------- --------432 X 205,70 399 6:Fail RsOffDEFAULT 433 Y 205,70 401 06NOV93 DEFAULT IN Job Attribute The IN job attribute specifies the name of a job’s input file.
IN Job Attribute Attributes • Specifying an input file to which other users have write access causes the scheduler to generate this warning message: 0512-W Other users can WRITE or PURGE the IN file; resecure if required Users with write access to your job input file can alter any job attribute or delete a job using the file. Using the input file as a medium, these users also can assume your level of security.
INITIATION Class Attribute Attributes INITIATION Class Attribute The INITIATION class attribute specifies whether jobs from the class are available for execution by the scheduler. INI[TIATION] { OF[F] | ON } OFF specifies jobs from the class are unavailable for execution. ON specifies jobs from the class are available for execution. Consideration The scheduler assigns the attribute INITIATION ON to a class added without the INITIATION attribute.
INITIATION Scheduler Attribute Attributes 23} STATUS JOB * JOB JOBNAME USERID LOG STATE CLASSNAME ---- ------------------------ ------- ---- ----------- ----390 JOB-A 255,205 READY DEFAULT 391 JOB-B 255,205 READY DEFAULT 24} ALTER CLASS DEFAULT, INITIATION ON Class DEFAULT altered 25} STATUS JOB * JOB JOBNAME USERID LOG STATE CLASSNAME ---- ------------------------ ------- ---- ----------- ----390 JOB-A 255,205 141 EXECUTING DEFAULT 391 JOB-B 255,205 142 EXECUTING DEFAULT 26} STATUS EXECUTOR * EXECUTOR CP
JOB-LOG Job Attribute Attributes Example This example shows the effect of the INITIATION scheduler attribute. When set to OFF, the attribute disables job startup. When set to ON, the attribute enables job startup.
JOB-LOG Job Attribute Attributes For a job with the ATTACHMENT-SET attribute, log-file can specify a DEFINE from the attachment set. Considerations • The scheduler creates a spooler-job log file for a job without the JOB-LOG attribute if the job’s OUT attribute specifies a spooler collector process. The scheduler does not create a log file if the OUT attribute specifies a device, a disk file, or a nonspooler collector process.
JOB-LOG Job Attribute Attributes job-log: 8} RUN PERUSE PERUSE - T9101D20 - (01JUN93) SYSTEM \MELBDEV SPOOLER SUPERVISOR IS \MELBDEV.$SPLS JOB BATCH STATE PAGES COPIES PRI HOLD LOCATION … . . 80 48 READY 2 1 4 #RUN1 … 81 48 READY 1 1 4 #RUN1 … 82 49 READY 1 1 4 #RUN2 … . . • This example shows two similar jobs that send their output to a spooler. The first job does not have the JOB-LOG attribute, so the spooler batches together the job’s log file and executor-program output file.
JOBID-ZERO Job Attribute Attributes JOBID-ZERO Job Attribute The JOBID-ZERO job attribute determines whether the scheduler assigns a GMOMJOBID to a job’s executor-program process. The job executes under the scheduler’s control if assigned a GMOMJOBID and outside that control if not. J[OBID]-Z[ERO] { OF[F] | ON } OFF makes the scheduler assign a GMOMJOBID to the job’s executor-program process. As a result, the job executes under the scheduler’s control.
LIB Job Attribute Attributes Myterm: $ZBAT . . GMOMJOBID: $ZBAT.1 > BATCHCOM $ZBAT; SUBMIT JOB NO-GMOMJOBID, EXECUTOR-PROGRAM DELAY, STARTUP "1 MINS", NAME $NO, JOBID-ZERO ON, TERM \MELBDEV.$ZTN0.#PTY6 Job NO-GMOMJOBID Jobnumber 2 submitted > STATUS $NO, DETAIL . . Myterm: $ZTN0.#PTY6 . . GMOMJOBID: LIB Job Attribute The LIB job attribute specifies the name of the user library file for a job’s executor program. LIB [ file-name ] file-name specifies the name of the user library file.
LIMIT Job Attribute Attributes RUN command has the same effect.) For more information, see ALTER JOB Command on page 6-62. • The scheduler places the value of the LIB attribute in the library-file parameter of the PROCESS_CREATE_ procedure. For more information about the procedure, see the Guardian Procedure Calls Reference Manual. Example This example shows the LIB attribute specifying the library file for a user-written program: > BATCHCOM $ZBAT; SUBMIT JOB SCHDCOLD, EXECUTOR-PROGRAM $TRASH.OBJS.
LIMIT Job Attribute Attributes • A scheduler with EMS event-message generation enabled generates event message 204 (ZBAT-EVT-JOB-OVER-LIMIT) when a job exceeds its execution time limit. For message details, see the NetBatch Management Programming Manual. Example This example shows the submission and execution of a job with the LIMIT attribute. The example shows the job’s state change when the specified limit expires and the log-file events that record the job’s execution history.
LOCALNAMES Scheduler Attribute Attributes LOCALNAMES Scheduler Attribute The LOCALNAMES scheduler attribute makes the scheduler treat jobs submitted from licensed requesters on specified nodes as local jobs, not as remote jobs. (An example of such a requester is NetBatch-Plus.) The remotely submitted jobs gain, through the scheduler, the same access privileges on the scheduler’s node as locally submitted jobs.
LOCALNAMES Scheduler Attribute Attributes • If the command does not include the remote-node parameter, the scheduler starts without the LOCALNAMES attribute; for example: > NETBATCH /NAME $ZBAT, NOWAIT/ $DATA7.ZBAT ! > BATCHCOM $ZBAT; INFO SCHEDULER, LOCALNAMES SCHEDULER ATTRIBUTES • • A scheduler without the LOCALNAMES attribute treats remotely submitted jobs as remote jobs subject to normal NonStop system remote-access restrictions.
MAX-CONCURRENT-JOBS Scheduler Attribute Attributes ---- ---------------- ------- ---- ----------- --------4 ZBAT-0004 255,255 122 3:NEWP. err DEFAULT • This example shows the same command sequence as that in the previous example, but the job starts successfully because the scheduler has the LOCALNAMES attribute: > FILEINFO \REMOTE.$TRASH.OBJECTS.BATCHCOM \REMOTE.$TRASH.OBJECTS Code … Owner RWEP … BATCHCOM 100L … 255,255 "A-A-" … > FILEINFO \LOCAL.$DATA7.PURGE.* \LOCAL.$DATA7.
MAX-CONCURRENT-JOBS Scheduler Attribute Attributes temporary executors for jobs with the AT attribute and for jobs affected by the RUNNOW JOB command. For more information, see AT Job Attribute on page 7-15 and RUNNOW JOB Command on page 6-128.) Considerations • • A scheduler adopts the attribute MAX-CONCURRENT-JOBS 500,500 by default when cold started.
MAX-PRI Scheduler Attribute Attributes MAX-PRI Scheduler Attribute The MAX-PRI scheduler attribute specifies an upper execution-priority limit for executor-program processes and processes they create. The attribute overrides the PRI job attribute, thereby enabling you to prevent processes from executing at a priority higher than appropriate for your system. M[AX]-[PRI] number number is a number in the range 1 through 199 (1 is lowest) specifying the executionpriority limit.
MAXPRINTLINES Job Attribute Attributes . Program … Pid … Pri … TACL … $TEST … 199 … DELAY … $D3 … 100 … DELAY … $D2 … 100 … DELAY … $D1 … 100 … MAXPRINTLINES Job Attribute The MAXPRINTLINES job attribute specifies the maximum number of print lines for a job output file. The attribute is, in effect, a spooler-job attribute, so it only applies if the output file is a spooler collector process.
MAXPRINTPAGES Job Attribute Attributes value for one of MAXPRINTPAGES and MAXPRINTLINES, and NONE for the other. • For information on spooler jobs, see the manual for the spooler product you are using. Example This example shows the submission of a job whose output file is a spooler location. The example shows the sources of the job’s MAXPRINTLINES and MAXPRINTPAGES attributes and the effect the attributes have on the output file.
MAXPRINTPAGES Job Attribute Attributes NONE specifies no maximum. Considerations • • • • • • • A job submitted without the MAXPRINTPAGES attribute adopts the DEFAULTMAXPRINTPAGES scheduler attribute. To display the value of this attribute, use the INFO SCHEDULER command. The scheduler passes the MAXPRINTLINES attribute to a job’s executor-program process as a spool DEFINE named =_ZBAT_OUT if the job’s OUT attribute specifies a spooler collector process.
MEM Job Attribute Attributes MAXPRINTPAGES JOB ATTRIBUTES for PAGES jobnumber: 257 maxprintlines: None maxprintpages: 50 > BATCHCOM $ZBAT; STATUS JOB PAGES JOB STATUS JOB JOBNAME USERID LOG STATE CLASSNAME ---- ---------------- ------- ---- ----------- --------257 PAGES 205,70 11 EXECUTING DEFAULT > SPOOLCOM )JOB 11, STATUS DETAIL JOB: 11 STATE: READY LOCATION: #PAGES . .
NAME Job Attribute Attributes NAME Job Attribute The NAME job attribute specifies a name for a job’s executor-program process. NA[ME] $process-name process-name specifies a unique name for the executor-program process. The name can contain from one to five alphanumeric characters. The first character must be alphabetic. For network access and for processes that use the C-series OPEN procedure instead of the D-series FILE_OPEN_ procedure, the name cannot contain more than four characters.
OUT Job Attribute Attributes OUT Job Attribute The OUT job attribute specifies the output file to which the scheduler writes data produced by an executing job. This data can include the job’s log file, executorprogram output, and output from processes started by the executor program. OU[T] [ file-name ] file-name is the name of an output file. The file can be a device, a process, or a disk file. If you omit file-name, the scheduler passes spaces as the output file name.
OUT Job Attribute Attributes Spooler jobs 100 and 101 are the log file and executor-program output file respectively. Spooler jobs 102 and 103 are the output files of the job’s two FUP processes. > FUP COPY FUPS FUP FILES $NB.* FUP FILES $DATA6.* > BATCHCOM $ZBAT; SUBMIT JOB A, IN FUPS, OUT $S.
PARAM Attachment-Set Attribute Attributes • The FUP process in this example fails because it tries to open the same disk output file as that of the executor program. This failure does not occur if output from the FUP and executor-program processes goes to the same spooler location. > FUP COPY FUPIN FUP FILES * > BATCHCOM $ZBAT; SUBMIT JOB Y, IN FUPIN, OUT FUPOUT Job Y job number 346 submitted 112> FUP COPY FUPOUT TACL (T9205Dxx - DDMMMYY), Operating System Dxx . .
PARAM Attachment-Set Attribute Attributes Consideration For more information on PARAMs, see the TACL Reference Manual and the TACL Programming Guide. Examples • This example shows the scheduler passing PARAMs from a job’s attachment set to the job’s TACL executor-program process: > LOGON NB.USER, psswrd > FUP COPY INFILE PARAM > BATCHCOM $ZBAT; ADD ATTACHMENT-SET A, (PARAM LOC 148), (PARAM DEPT 7326), (PARAM EMPNUM 19197) Attachment-set (NB.
PFS Job Attribute Attributes PARAM YEAR 1993 5} ALTER ATTACHMENT-SET TODAY, (PARAM DAY 22) Attachment-set (NB.USER)TODAY altered 6} DELETE ATTACHMENT-SET TODAY, PARAM DATE Attachment-set (NB.USER)TODAY altered 7} INFO ATTACHMENT-SET TODAY, PARAM * attachments: PARAM PERIOD-BEGIN 01SEP93 PARAM PERIOD-END 30SEP93 PARAM PERIOD-ID 9 PARAM DAY 22 PARAM MONTH SEPTEMBER PARAM YEAR 1993 PFS Job Attribute The PFS job attribute specifies the size in bytes of a job’s executor-program process file segment (PFS).
PRI Job Attribute Attributes PRI Job Attribute The PRI job attribute specifies the execution priority of a job’s executor-program process. PR[I] number number is a number in the range 1 through 199 (1 is lowest) specifying the execution priority of a job’s executor-program process. Considerations • • • A job submitted without the PRI attribute adopts the DEFAULT-PRI scheduler attribute. To display the value of this attribute, use the INFO SCHEDULER command.
PURGE-IN-FILE Job Attribute Attributes not include the PRI run option. For more information, see the TACL Reference Manual.
PURGE-IN-FILE Job Attribute Attributes • BATCHCOM displays this message if you specify the PURGE-IN-FILE ON attribute for a job whose input file denies you purge access: 0530-W You have no PURGE access to IN file Examples • This example shows the effect of the PURGE-IN-FILE ON attribute: > FILEINFO $DATA7.TRASH Code … Last Modification Owner RWEP … INFILE 101 … 3-Oct-94 11:04:30 205,70 "AAAO" … > LOGON 205,70, psswrd > BATCHCOM $ZBAT; SUBMIT JOB, IN $DATA7.TRASH.
RESTART Job Attribute Attributes > FILEINFO No files match \MELBDEV.$NB.TEMP.* • This example shows a job’s input-file security preventing the scheduler from purging the file on deletion of the job: > FILEINFO $BIG1.
RESTART Job Attribute Attributes ON causes the scheduler to restart the job if it stops with completion code 7 (restart request sent to the scheduler) or terminates because of CPU failure. (This action depends on the values of the job’s IFFAILS, STALL, and STOP-ON-ABEND attributes.) For more information, see Figure 4-9 on page 4-29. Considerations • • • • The scheduler treats a job submitted without the RESTART attribute like a job with the attribute RESTART OFF.
RUND Job Attribute Attributes > DIVER /CPU 3/ PROCESSOR FAILURE: 3 > BATCHCOM $ZBAT; STATUS JOB * JOB STATUS JOB JOBNAME USERID LOG STATE CLASSNAME ---- ---------------- ------- ---- ----------- --------438 X 255,255 85 READY DEFAULT 439 Y 255,255 87 10NOV93 DEFAULT RUND Job Attribute The RUND job attribute specifies whether a job’s executor program enters the Guardian debug facility Debug or the Inspect interactive symbolic debugger when the program runs.
SAVEABEND Job Attribute Attributes 4 RUND-JOB 205,70 EXECUTING DEFAULT > PAUSE INSPECT - Symbolic Debugger - T9673D30 - (31OCT94) System … (C)1983 Tandem (C)2004 Hewlett Packard Development Company, L.P. INSPECT 247,01,00039 $Y225 #BATCHCOM.#11595(SBATCOM) + %1I -$Y225- SAVEABEND Job Attribute The SAVEABEND job attribute specifies whether a job’s executor-program process is to create a save file if the process traps or abends.
SECURITY Attachment-Set Attribute Attributes \MELBDEV.$Y290:16288557 15SEP94 14:45:42 OPEN U_255,255 P_DMON \MELBDEV.$DM01:9611309 15SEP94 14:45:42 MSG Save file \MELBDEV.$DATA7.OBJFILES.ZZSA2285 created for process 1,51 ($Y290) P_DMON \MELBDEV.$DM01:9611309 15SEP94 14:45:42 CLOSE \MELBDEV.$DM01:9611309 U_255,255 15SEP94 14:45:42 ABEND CC_5 EXECUTOR-PROGRAM J_11 \MELBDEV.$Y290:16288557 . . SECURITY Attachment-Set Attribute The SECURITY attachment-set attribute controls user access to an attachment set.
SECURITY Attachment-Set Attribute Attributes Table 7-3.
SELPRI Job Attribute Attributes security: "GOGO" temporary: Off 0535-I Your user code does not give you access to (SUPER.FPP)MNGRS data SELPRI Job Attribute The SELPRI job attribute specifies the selection priority of a job in its class. SEL[PRI] number number is a number in the range 0 through 7 (0 is lowest) specifying the selection priority.
STALL Job Attribute Attributes Job D-SELPRI-6 job number 815 submitted 8} INFO JOB 814, SELPRI JOB ATTRIBUTES for C-SELPRI-DEFAULT jobnumber: 814 selpri: 3 9} ALTER CLASS DEFAULT, INITIATION ON Class DEFAULT altered 10} STATUS JOB *, SELPRI JOB JOBNAME USERID SEL STATE CLASSNAME ---- ------------------ ------- ---- ----------812 A-SELPRI-6 255,205 6 READY DEFAULT 813 B-SELPRI-7 255,205 7 EXECUTING DEFAULT 814 C-SELPRI-DEFAULT 255,205 3 READY DEFAULT 815 D-SELPRI-6 255,205 6 READY DEFAULT 11} STATUS JOB *,
STALL Job Attribute Attributes ON causes the scheduler to put the job in the SPECIAL-9 state if the job fails and either of these conditions exists. (This action depends on the values of the job’s IFFAILS, RESTART, and STOP-ON-ABEND attributes.) • • The job is recurrent, and the scheduler would otherwise reschedule it. The job is nonrecurrent, and the scheduler would otherwise delete it. Considerations • • A job submitted without the STALL attribute adopts the DEFAULT-STALL scheduler attribute.
STARTUP Job Attribute Attributes > STOP $Z076 > BATCHCOM $ZBAT; STATUS JOB * JOB STATUS JOB JOBNAME USERID LOG STATE CLASSNAME ---- ---------------- ------- ---- ----------- --------380 X 205,70 30 14OCT93 DEFAULT 381 Y 205,70 32 9:STALL DEFAULT STARTUP Job Attribute The STARTUP job attribute specifies one or more program parameters the scheduler sends a job’s executor-program process in the startup message. STARTU[P] " param-set " param-set is a string of 1 through 961 characters.
STOP-ON-ABEND Job Attribute Attributes jobnumber: 501 startup: LABEL XYZ, PURGE, LIMIT 3:00 STOP-ON-ABEND Job Attribute The STOP-ON-ABEND job attribute determines whether the scheduler stops a job and all its processes if any process of the job terminates because of CPU failure; abends with any completion code; or stops with completion code -3, -2, -1, 2, 3, 4, 5, or 6. The attribute works in combination with the job’s IFFAILS, RESTART, and STALL attributes.
STOP-ON-ABEND Job Attribute Attributes • • Do not use STOP-ON-ABEND for NBEXEC jobs. NBEXEC always terminates on an untrapped error condition. For help when setting the IFFAILS, RESTART, STALL, and STOP-ON-ABEND attributes, see Figure 4-9 on page 4-29. Example This example shows the effect of the STOP-ON-ABEND attribute on two recurrent jobs whose child processes stop because of CPU failure. The jobs have the same IFFAILS, RESTART, and STALL attributes, but different STOP-ON-ABEND attributes.
SUBMIT-ALLOWED Scheduler Attribute Attributes SUBMIT-ALLOWED Scheduler Attribute The SUBMIT-ALLOWED scheduler attribute allows or disallows job submission by permitting or preventing use of the SUBMIT JOB command. S[UBMIT]-A[LLOWED] { OF[F] | ON } OFF disallows job submission by preventing use of the SUBMIT JOB command.
SWAP Job Attribute Attributes attribute affects only the SUBMIT JOB command and not other scheduler operations.
TAPEDRIVES Job Attribute Attributes • The scheduler places the value of the SWAP attribute in the swap-file parameter of the PROCESS_CREATE_ procedure. For more information on the procedure, see the Guardian Procedure Calls Reference Manual. Example This example shows the SWAP attribute specifying the swap file for a job’s TACL executor-program process: > BATCHCOM $ZBAT; SUBMIT JOB SWAP-JOB, EXECUTOR-PROGRAM TACL, IN \MELRISK.$QA.FILES.INFILE, SWAP $TRASH.ZBAT.
TAPEDRIVES Scheduler Attribute Attributes • • • Increase the number of drives specified by the TAPEDRIVES scheduler attribute Reduce the number of drives required by the job For more information on the scheduler’s internal tape drives counter, see TAPEDRIVES Scheduler Attribute on page 7-110. Example This example shows the submission of two jobs, each of which requires tape drives. The scheduler puts job 396 into the TAPE state because insufficient drives are available.
TAPEDRIVES Scheduler Attribute Attributes • The scheduler calculates the number of tape drives available for use by using its TAPEDRIVES attribute to initialize an internal counter. When you submit a job, the scheduler compares the number of drives required by the job with the counter. The scheduler’s treatment of the job (assuming no other factors are delaying job execution) depends on whether the number is: ° Less than or equal to the counter.
TEMPORARY Attachment-Set Attribute Attributes ACTIVE 0 SPECIAL 0 STOP 0 TIME 0 DOWN 0 EVENT 0 TAPE DRIVES … DELETE 0 SUSPENDED 0 ------------- … RUN NEXT 0 CONFIGURED 3 … RUN NOW 0 IN USE 0 TAPE 0 26> BATCHCOM $ZBAT; SUBMIT JOB BACKUP, TAPEDRIVES 2 Job BACKUP job number 1 submitted 27> BATCHCOM $ZBAT; STATUS SCHEDULER SCHEDULER STATUS Process : \MELBDEV.$ZBAT Primary : 1,37 Backup : 3,27 Database: $DATA7.ZBAT Logfile : $DATA7.ZBAT.
TEMPORARY Attachment-Set Attribute Attributes Consideration The scheduler assigns a default TEMPORARY attribute to an attachment set added by a command that does not specify that attribute. The value of the default attribute depends on whether the set has a user-specified or scheduler-generated (through #CURRENT) identifier. Possible values are: • TEMPORARY OFFfor sets added with user-specified identifiers (that is, named attachment sets). For example: 17} ADD ATTACHMENT-SET (FPP.
TERM Job Attribute Attributes 387 A 133,2 132 1:Hold DEFAULT 16} STATUS ATTACHMENT-SET 34 ATTACHMENT SET IN USE BY JOBS --------------------------------- -------------(NB.USER)34 (NB.USER)A 17} DELETE JOB 387 Job A job number 387 deleted 18} STATUS ATTACHMENT-SET 34 ATTACHMENT SET IN USE BY JOBS --------------------------------- -------------(NB.USER)34 None 19} EXIT > BATCHCOM $ZBAT; STATUS ATTACHMENT-SET 34 2172-E (NB.
TERM Job Attribute Attributes Considerations • • A job submitted without the TERM attribute uses the scheduler as its home terminal. A job with the RUND ON attribute must also have the TERM attribute specifying a home terminal for Debug or Inspect output. Without the TERM attribute, the job fails during startup and goes into the SPECIAL-4 state. • Processes of a job with the JOBID-ZERO ON attribute cannot access the scheduler as a home terminal.
VOLUME Job Attribute Attributes VOLUME Job Attribute The VOLUME job attribute specifies the default node, volume, and subvolume for unqualified file references in a job’s input file. You also can use the attribute to specify the default security for disk files created by the job. V[OLUME] { \node. [ volume ] [ ‚ " security " ] [ \node. ] volume [ ‚ " security " ] [ \node. ] [ volume ] ‚ " security ") } node is a node name. volume is one of: $volume-name.subvolume-name are volume and subvolume names.
VOLUME Job Attribute Attributes Considerations • • The default VOLUME attribute values are the node, volume, subvolume, and security defaults set by the last SET JOB VOLUME command. If there was no such command, the default values are the defaults current when the BATCHCOM session began. The VOLUME job attribute always overrides the VOLUME attribute of defaults DEFINE =_DEFAULTS in a job’s attachment set.
WAIT Job Attribute Attributes WAIT Job Attribute The WAIT job attribute delays execution of a job for a specified period from the current time. (The current time is the system date and time on the node where the job’s scheduler is running.) WAIT hours [ : mins ] hours is a number in the range 0 through 168 specifying the number of hours delay (168 hours equals 7 days). mins is a number in the range 0 through 59 specifying the number of minutes delay.
WAITON Job Attribute Attributes Examples • This example shows the WAIT attribute delaying execution of a job by 10 minutes: > TIME September 10, 1993 10:30:40 > BATCHCOM $ZBAT; SUBMIT JOB A, WAIT 0:10 Job A job number 226 submitted > BATCHCOM $ZBAT; INFO JOB A, AFTER JOB ATTRIBUTES for A jobnumber: 226 after: 10SEP93 10:40:48 next-runtime: 10SEP93 10:40:48 • This example shows the WAIT attribute overriding a job’s AFTER attribute: > TIME September 10, 1993 10:35:10 > BATCHCOM $ZBAT; SUBMIT JOB B, AFTE
WAITON Job Attribute Attributes WAITON without job-name in a SET JOB command makes BATCHCOM remove the WAITON attribute from the working-attributes set. case is one of: REL[EASE] makes the dependent job wait for its master to release it with the ZBAT:RELEASE macro, the NBEXEC command $RELEASE, or the NetBatch programmatic command RELEASE JOB. (For information about the RELEASE JOB command, see the NetBatch Management Programming Manual.
WAITON Job Attribute Attributes ° Execute an explicit or implicit $RELEASE commandif the master job’s executor program is an NBEXEC process. NBEXEC automatically executes an implicit $RELEASE * command if the job runs without errors. ° ° Execute the NetBatch programmatic command RELEASE JOB. Terminate normally (if the dependent has the attribute WAITON master-job STOP or WAITON master-job STOP-ABEND) or abnormally (WAITON master-job STOP-ABEND).
WAITON Job Attribute Attributes ° • If the master runs less frequently than the dependent, the dependent runs only when released by the master. As a result, the dependent runs at the same frequency as its master even though its execution interval specifies otherwise. Use of RUNNOW command on a dependent job, in order to run the dependent job without running the master job, is not recommended.
WAITON Job Attribute Attributes • This example shows an ALTER JOB command changing the master jobs specified by a dependent job’s WAITON attribute: 70} INFO JOB DEPENDENT-JOB, WAITON JOB ATTRIBUTES for DEPENDENT-JOB jobnumber: 19 waiton: MASTER-JOB-1, Not Released MASTER-JOB-2, Not Released 71} ALTER JOB DEPENDENT-JOB, WAITON & }} (MASTER-JOB-3, MASTER-JOB-4, MASTER-JOB-5) Job DEPENDENT-JOB Jobnumber 19 altered 72} INFO JOB DEPENDENT-JOB, WAITON JOB ATTRIBUTES for DEPENDENT-JOB jobnumber: 19 waiton: MAST
WAITON Job Attribute Attributes NetBatch Manual—522460-004 7 -124
A Messages This appendix describes the three types of NetBatch messages and provides detailed information on NetBatch messages in the range 512 through 2237: Topic Page Message Types A-2 Message Descriptions A-3 The appendix does not contain information about these messages: Message Numbers Message type For cause, effect, and recovery information, see: -14— -1 Subsystem Programmatic Interface (SPI) errors Descriptions of SPI errors in the Guardian Procedure Errors and Messages Manual 1—2555 F
Message Types Messages Message Types There are three types of NetBatch messages: error, informational, and warning. Error Messages Error messages (prefix nnnn-E) indicate NetBatch software did not perform the requested function and give a reason.
Message Descriptions Messages Message Descriptions This subsection contains cause, effect, and recovery information for NetBatch messages with numbers in the range 512 through 2237. 0512-W Other users can WRITE or PURGE the IN file; resecure if required Cause. The IN job attribute specified an input file to which other users have write orpurge access. Effect. The command executed successfully. However, users with write access to the input file can alter any attribute of or delete the job using the file.
Message Descriptions Messages 0515-W ALTER CLASS expects INITIATION ON or OFF Cause. The ALTER CLASS command omitted the INITIATION attribute completely or specified INITIATION without a value. The command must specify the INITIATION attribute in full. Effect. The command failed. Recovery. Retry the command, specifying the attribute INITIATION OFF or INITIATION ON. 0516-W Executor executor-name has already started Cause.
Message Descriptions Messages 0518-W Job has already been released Cause. The dependent job received a second or subsequent release from its master or a job with the same name as its master. Effect. None. Recovery. Not applicable unless the names of the jobs receiving the releases conflict. In that case, make sure the jobs in the master-dependent relationship have names that no other jobs use at any time. 0522-W File file-name cannot be referenced over network Cause.
Message Descriptions Messages 0525-W Executor executor-name not started; CPU cpu-number is not available Cause. The START EXECUTOR command specified an executor whose CPU is unavailable. Effect. None. Recovery. Retry the command when the CPU is available or after altering the executor’s CPU attribute to specify an available CPU. 0526-W Executor executor-name has stopped, or will stop or be deleted when current job finishes Cause.
Message Descriptions Messages 0528-W You have no WRITE access to OUT file or OUT file does not exist Cause. The OUT job attribute specified a nonexistent output file or an output file to which you have no write access. Effect. The command executed successfully, but the job abends when it runs if its executor program is incapable of creating or writing to the output file. Recovery. Create the output file or ask the file’s owner to resecure it for write access before the job runs.
Message Descriptions Messages 0531-W Error file-system-error-number opening CALENDAR file. Cause. The CALENDAR job attribute specified a calendar file the scheduler could not open because of a file-system error. Effect. The command executed successfully. The scheduler put the job in the SPECIAL-7 state, however, thus preventing the job from running. Recovery. To resolve the SPECIAL-7 state and make the job ready to run: 1. Correct the condition indicated by error file-system-error-number.
Message Descriptions Messages 0535-I Your user code does not give you access to ( user-ID) attachment-set-ID data Cause. The command specified an attachment set to which you have no access. Effect. None. Recovery. Not applicable. 0536-I =_DEFAULTS cannot be deleted Cause. The DELETE ATTACHMENT-SET command specified the defaults DEFINE=_DEFAULTS. You cannot delete this DEFINE. Effect. None. Recovery. Not applicable. 0537-W ( user-ID) attachment-set-ID does not exist Cause.
Message Descriptions Messages 0541-I No such line Cause. The FC, !, or ? command specified a nonexistent line in BATCHCOM’s history buffer. Effect. None. Recovery. Retry the command after checking for the correct line in the history buffer by using the HISTORY command. 0542-W DEFINE names beginning with =_ZBAT reserved for Tandem use Cause. An attachment-set command specified a DEFINE whose name began with =_ZBAT. HP reserves DEFINE names beginning with =_ZBAT for its own use. Effect.
Message Descriptions Messages 0544-W SWAP, EXTSWAP, LIB, EXECUTOR-PROGRAM must be on same system Cause. The job’s EXTSWAP, LIB, or SWAP attribute specified a file on a different node from that of the job’s executor program. The attributes must specify files on the same node as the executor program. Effect. The command failed. Recovery. Retry the command, specifying extended swap, swap, and library files on the same node as the executor program.
Message Descriptions Messages 0548-W AT/AFTER specifies a time in the past. Cause. A job was submitted or altered to run at or after a time in the past. Effect. The job runs. Recovery. Not applicable. 0549-I process-handles-count Process handles omitted Cause. In response to a STATUS command, the process-handle-count process handles started by a NetBatch job could not be accommodated in the Reply buffer due to resource limitations. Effect. None.
Message Descriptions Messages 2050-E In AFTER date: YEAR must be in the range 1993 to 2525 Cause. The AFTER job attribute’s date option specified a year value outside the allowable range 1993 through 2525. Effect. The command failed. Recovery. Retry the command, specifying a year value in the range 1993 through 2525. 2051-E In AFTER date: MONTH must be in the range 1 to 12 Cause. The AFTER job attribute’s date option specified a month value outside the allowable range 1 through 12. Effect.
Message Descriptions Messages 2054-E In AFTER time: MINUTE must be in the range 0 to 59 Cause. The AFTER job attribute’s time option specified a minute value outside the allowable range 0 through 59. Effect. The command failed. Recovery. Retry the command, specifying a minute value in the range 0 through 59. 2055-E Scheduler is already started; command ignored. Cause. The START SCHEDULER command operated on a started scheduler. Effect. None. Recovery. Not applicable.
Message Descriptions Messages 2058-E In AT date: YEAR must be in the range 1993 to 2525 Cause. The AT job attribute’s date option specified a year value outside the allowable range 1993-2525. Effect. The command failed. Recovery. Retry the command, specifying a year value in the range 1993 through 2525. 2059-E In AT date: MONTH must be in the range 1 to 12 Cause. The AT job attribute’s date option specified a month value outside the allowable range 1 through 12. Effect. The command failed. Recovery.
Message Descriptions Messages 2062-E In AT time: MINUTE must be in the range 0 to 59 Cause. The AT job attribute’s time option specified a minute value outside the allowable range 0 through 59. Effect. The command failed. Recovery. Retry the command, specifying a minute value in the range 0 through 59. 2063-E BACKUPCPU out of range 0 to 15, or * for any CPU Cause. The BACKUPCPU scheduler attribute specified a nonexistent CPU on the scheduler’s node. Effect. The command failed. Cause.
Message Descriptions Messages 2068-E CALENDAR file is not a valid calendar file; it must be created by BATCHCAL Cause. The CALENDAR job attribute specified a file that was not generated by BATCHCAL. Effect. The command failed. Recovery. Retry the command, specifying a file generated by BATCHCAL. 2069-E Use ADD SCHEDULER to create and initialize the database Cause. The file JOB was missing from the scheduler’s database during a warm start of the scheduler. Effect. The warm start failed. Recovery.
Message Descriptions Messages 2073-E Invalid SPI CONTEXT token, command terminated Cause. A requester sent an invalid context token. Effect. The command failed. Recovery. Modify the requester to send a valid context token. 2074-E CPU must be cpu-number to cpu-number Cause. The CPU executor attribute specified a nonexistent CPU on the scheduler’s node. Effect. The command failed. Recovery.
Message Descriptions Messages 2077-E Job is executing or suspended; DELETE command ignored. Cause. The DELETE JOB command specified an executing, over-limit, or suspended job (state EXECUTING, OVER LIMIT, or SUSPENDED). The command only operates on jobs whose states are EVENT, READY, RUNNEXT, RUNNOW, SPECIAL-n, TAPE, or TIME. Effect. The command failed. Recovery. Use the STOP JOB command to stop the job.
Message Descriptions Messages 2080-E You cannot specify both CALENDAR and EVERY attributes for a job Cause. The command specified two or more of the CALENDAR attribute, the EVERY attribute, and ZBAT-MAP-DEF-CRONTAB. CALENDAR, EVERY, and ZBAT-MAP-DEFCRONTAB are mutually exclusive. Effect. The command failed. Recovery. Retry the command, specifying only one of CALENDAR, EVERY, and ZBAT-MAP-DEF-CRONTAB. 2082-E EXECUTOR-PROGRAM file-name is not a valid file name Cause.
Message Descriptions Messages 2087-E EXECUTOR executor-name does not exist Cause. The executor command specified a nonexistent executor. Effect. The command failed. Recovery. Retry the command, specifying an existing executor. 2088-E The EXECUTOR file is full Cause. The scheduler attempted to add an executor to its database in response to an ADD EXECUTOR command. The attempt failed because the EXECUTOR file that records executor details was full. Effect. The command failed. Recovery.
Message Descriptions Messages 2092-E IFFAILS invalid value Cause. A requester specified an invalid value for a job’s IFFAILS attribute. Effect. The command failed. Recovery. Modify the requester to specify an IFFAILS value of -1 (true) or 0 (false). 2093-E IN file file-name is an invalid file name Cause. A requester specified an invalid file name for the IN job attribute. Effect. The command failed. Recovery. Modify the requester to specify a valid file name. 2095-E INITIATION invalid value Cause.
Message Descriptions Messages 2098-E Either the JOB or CHKQUE file is full Cause. The scheduler attempted to add a job to its database in response to a SUBMIT JOB command. The attempt failed because either the JOB or CHKQUE file that records job details was full.
Message Descriptions Messages 2103-E The CLASS file is full Cause. The scheduler attempted to add a class to its database in response to an ADD CLASS command. The attempt failed because the JOBCLASS file that records class details was full. Effect. The command failed. Recovery. Retry the command after your system administrator increases the maximum extents of the JOBCLASS file by using the FUP ALTER command. (The default maximum extents for the file is 100.
Message Descriptions Messages 2107-E Job job-name already exists Cause. The SUBMIT JOB command specified the name of an existing job. Effect. The command failed. Recovery. Retry the command, specifying a unique job name. 2108-E You must specify a job name Cause. The command did not specify the name of a job (a required syntax item). Effect. The command failed. Recovery. Retry the command, specifying a job name. 2110-E Job number must be in the range 1 to 32767 inclusive Cause.
Message Descriptions Messages 2118-E MAXPRINTLINES is out of range 120 to 65534 Cause. The MAXPRINTLINES job attribute specified a maximum number of print lines outside the allowable range 120 through 65534. Effect. The command failed. Recovery. Retry the command, specifying a MAXPRINTLINES value in the range 120 through 65534. 2119-E MAXPRINTPAGES is out of range 2 to 65534 Cause. The MAXPRINTPAGES job attribute specified a maximum number of print pages outside the allowable range 2 through 65534.
Message Descriptions Messages 2122-E You must specify a CLASS Cause. The command omitted the CLASS attribute. Effect. The command failed. Recovery. Retry the command, specifying the CLASS attribute. 2123-E Only one CONTEXT token is allowed per command Cause. A requester sent two or more context tokens in a command where the scheduler expected only one. Effect. The command failed. Recovery. Modify the requester to send one context token. 2124-E Only one MAP token is allowed per command Cause.
Message Descriptions Messages Effect. The command failed. Recovery. Report the error to your HP representative. 2127-E You must specify either the job name or the job number Cause. The job command did not specify the job on which it was to operate. Effect. The command failed. Recovery. Retry the command, specifying a job name or number. 2128-E SUBMIT-ALLOWED is OFF; the scheduler is not accepting job submissions Cause. The scheduler has the attribute SUBMIT-ALLOWED OFF. Effect. The command failed.
Message Descriptions Messages 2132-E Your user code does not give you access to { ( user-ID) attachment-set-ID | job-name } Cause. The command specified an attachment set or job to which you have no access. Effect. The command failed. Recovery. Not applicable. 2133-E The scheduler is being SHUTDOWN; command ignored. Cause. The command operated on a scheduler that was shutting down. Effect. The command failed. Recovery. Not applicable. 2136-E OUT file file-name is not a valid file name Cause.
Message Descriptions Messages 2139-E RESTART invalid value Cause. A requester specified an invalid value for a job’s RESTART attribute. Effect. The command failed. Recovery. Modify the requester to specify a RESTART value of -1 (true) or 0 (false). 2140-E STOP-ON-ABEND invalid value Cause. A requester specified an invalid value for a job’s STOP-ON-ABEND attribute. Effect. The command failed. Recovery. Modify the requester to specify a STOP-ON-ABEND value of -1 (true) or 0 (false).
Message Descriptions Messages 2143-E Scheduler cannot write to Edit-format log file, file-name Cause. The SWITCHLOG SCHEDULER command specified an EDIT file as the scheduler’s log file. EDIT files cannot be log files. Effect. The command failed. Recovery. Retry the command, specifying one of these as the log file: a device; a process; or any type of unstructured disk file except an EDIT file; or a nonexistent disk file. 2144-E SELPRI must be in range 0 to 7 Cause.
Message Descriptions Messages 2147-E SUBMIT-ALLOWED invalid value Cause. A requester specified an invalid value for the SUBMIT-ALLOWED attribute. Effect. The command failed. Recovery. Modify the requester to specify a SUBMIT-ALLOWED value of -1 (true) or 0 (false). 2148-E Job is not executing; SUSPEND command ignored. Cause. The SUSPEND JOB command specified a job that was not executing or over limit. The command only operates on executing and over-limit jobs (states EXECUTING and OVER LIMIT). Effect.
Message Descriptions Messages 2151-E Object object-keyword is invalid Cause. The object-keyword object is not a NETBATCH object. NETBATCH objects are ATTACHMENT-SET, CLASS, EXECUTOR, JOB, and SCHEDULER. Effect. The command failed. Recovery. Retry the command, specifying an allowable NETBATCH object. 2153-E Invalid token token-code in SPI buffer Cause. A requester sent a token not recognized by the scheduler. Effect. The command failed. Recovery. Modify the requester to send the correct token.
Message Descriptions Messages 2157-E RELEASE failed on one or more dependent jobs matching the specification Cause. The master job did not release all its dependent jobs because the job range specified by the ZBAT:RELEASE macro in the master’s input file excluded some of those jobs. Effect. The master released only some of its dependents. Recovery. Ask the master job’s owner to check and, where appropriate, to change the job range specified by the ZBAT:RELEASE macro.
Message Descriptions Messages 2161-E The specified job is not waiting on any jobs Cause. The ZBAT:RELEASE macro invoked by the master job sent a release to a nondependent job (a job without the WAITON attribute). Effect. None. Recovery.
Message Descriptions Messages 2167-E Cannot switch CPU without a backup process Cause. The scheduler attempted to switch CPUs in response to a SWITCHCPU SCHEDULER command. The attempt failed because the scheduler was running without a backup in the only available CPU on its node. Effect. The command failed. Recovery. The scheduler automatically creates its backup when another CPU becomes available. 2168-E Error file-system-error-number trying to switch to log file file-name Cause.
Message Descriptions Messages 2170-E CONVERTTIMESTAMP Error CONVERTTIMESTAMP-procedure-error-number; check daylight savings time (DST) table Cause. The AFTER or AT job attribute specified a run time in a daylight-saving time (DST) transition period, resulting in a CONVERTTIMESTAMP procedure error. Effect. The command failed. Recovery. Retry the command, specifying a run time outside the DST transition period. (Your system administrator will tell you when the period occurs.
Message Descriptions Messages 2173-E ( user-ID) attachment-set-ID is referenced by one or more jobs Cause. The DELETE ATTACHMENT-SET command specified an attachment set in use by one or more jobs. Effect. The command failed. Recovery. Retry the command after using the ALTER JOB, ATTACHMENT-SET command to dissociate the attachment set from the jobs using it. You can list the jobs using the set with the STATUS ATTACHMENT-SET command.
Message Descriptions Messages 2177-E ( user-ID) attachment-set-ID storage overflow Cause. An internal storage overflow momentarily prevented the scheduler from updating the attachment-set record. Effect. The command failed. Recovery. Retry the command. 2178-E Attachment set was updated during multiple replies to this command. Retry the command Cause. The attachment-set command referred to a set the scheduler was updating in response to another command. Effect. The command failed. Recovery.
Message Descriptions Messages 2189-E Error file-system-error-number, File: file-name Cause. A file-system error on file file-name prevented command execution. Effect. The command failed. Recovery. Retry the command after correcting the condition indicated for file file-name by error file-system-error-number. For information on the cause of the error, see the descriptions of file-system errors in the Guardian Procedure Errors and Messages Manual. 2190-E Invalid NetBatch ID attachment-set-name Cause.
Message Descriptions Messages 2192-E SPI Error SPI-error-number, invalid SPI request Cause. A requester sent an invalid SPI request to the scheduler. Effect. The command failed. Recovery. Determine the cause of the error by checking the documentation for SPI procedures SSGET and SSGETTKN in the SPI Programming Manual. Modify the requester if the error comes from the requester. Report the error to your HP representative if it comes from the scheduler.
Message Descriptions Messages 2195-E Cannot ACTIVATE job-ID Cause. One of these file-system errors occurred when the scheduler tried to reactivate job job-ID in response to an ACTIVATE JOB command: File-system error number Description 11 Process does not exist 48 Security violation 201 Unable to communicate with the process’s CPU Effect. The command failed. Recovery.
Message Descriptions Messages 2198-E Wild-card names are not supported for this command Cause. The RUNNEXT JOB or RUNNOW JOB command used wild-card characters to specify a range of job names. These commands do not support wild-card character searching in your version of the NetBatch product. Effect. The command failed. Recovery. Retry the command, specifying the full name or number of a single job. 2199-E Greater than 3 attachment sets specified for job Cause.
Message Descriptions Messages 2202-E AT inv val Cause. The ZAT-FLAG field of ZBAT-MAP-DEF-JOB specified an invalid value for the job’s AT flag. Effect. The command failed. Recovery. Retry the command, setting the ZAT-FLAG field to a valid Boolean value (for example, ZSPI-VAL-TRUE or ZSPI-VAL-FALSE). 2203-E You must specify an EXECUTOR Cause. The executor command omitted ZBAT-TKN-SEL-EXECUTORNAME (a required token) or specified ZBAT-TKN-SEL-EXECUTORNAME without a valid value. Effect. The command failed.
Message Descriptions Messages 2206-E ( user-ID) attachment-set-ID ASSIGN-name error Cause. The attachment-set command specified an invalid ASSIGN name. Effect. The command failed. Recovery. Retry the command, specifying a valid ASSIGN name. 2207-E ( user-ID) attachment-set-ID DEFINE-details error DEFINEerror-number Cause. The attachment-set command generated a DEFINE error. Effect. The command failed. Recovery. Retry the command after correcting the condition indicated by DEFINEerror-number.
Message Descriptions Messages 2210-E In AFTER time: SECOND must be in the range 0 to 59 Cause. The AFTER job attribute’s time option specified a seconds value outside the allowable range 0 through 59. Effect. The command failed. Recovery. Retry the command, specifying a seconds value in the range 0 through 59. 2211-E In AFTER time: MILLISECS must be in the range 0 to 999 Cause. The AFTER job attribute’s time option specified a milliseconds value outside the allowable range 0 through 999. Effect.
Message Descriptions Messages 2214-E Invalid WAITON name job-name Cause. The command specified an invalid master-job name. Effect. The command failed. Recovery. Retry the command, specifying a valid name of a master job. 2215-E Invalid executor name executor-name Cause. The command specified an invalid executor name. Effect. The command failed. Recovery. Retry the command, specifying a valid executor name. For information on the form of an executor name, see ADD EXECUTOR Command on page 6-42.
Message Descriptions Messages 2218-E Crontab inv val Cause. One or more of the EVERY attribute’s crontab-entry fields specified an invalid value. Effect. The command failed. Recovery. Retry the command, specifying valid values for all crontab-entry fields. For more information, see EVERY Job Attribute on page 7-55. 2219-E PURGE-IN-FILE inv val Cause. The ZPURGE-IN-FILE field of ZBAT-MAP-DEF-JOB specified an invalid value for the job’s PURGE-IN-FILE attribute. Effect. The command failed. Recovery.
Message Descriptions Messages 2222-E SAVEABEND inv val Cause. The ZSAVEABEND field of ZBAT-MAP-DEF-JOB specified an invalid value for the job’s SAVEABEND attribute. Effect. The command failed. Recovery. Retry the command, setting the ZSAVEABEND field to a valid Boolean value (for example, ZSPI-VAL-TRUE or ZSPI-VAL-FALSE). 2223-E RUND inv val Cause. The ZRUND field of ZBAT-MAP-DEF-JOB specified an invalid value for the job’s RUND attribute. Effect. The command failed. Recovery.
Message Descriptions Messages 2226-E LIMIT must be in range hours-range to minutes-range Cause. The ZTIME-LIMIT field of ZBAT-MAP-DEF-JOB specified a time limit outside the allowable range hours-range to minutes-range. Effect. The command failed. Recovery. Retry the command, specifying a time limit in the range hours-range to minutes-range. 2227-E DESCRIPTION too long Cause. The size of ZBAT-TKN-DESCRIPTION exceeded 1000 bytes. Effect. The command failed. Recovery.
Message Descriptions Messages 2230-E MAXPRI must be from 1 to 199 Cause. The MAX-PRI scheduler attribute specified a maximum priority outside the allowable range 1 through 199. Effect. The command failed. Recovery. Retry the command, specifying a MAX-PRI value in the range 1 through 199. 2231-E MAXCONCURRENT must be from 0 to 500 Cause. The MAX-CONCURRENT-JOBS scheduler attribute specified a concurrentjobs limit outside the allowable range 0 through 500. Effect. The command failed. Recovery.
Message Descriptions Messages 2234-E EMS inv val Cause. The ZEMS field of ZBAT-MAP-DEF-SCHEDULER specified an invalid value for the scheduler’s EMS attribute. Effect. The command failed. Recovery. Retry the command, setting the ZEMS field to a valid ZBAT-DDL-EMS value. 2235-E PFS range 131072-1048576 Cause. The PFS job attribute specified a nonzero process-file-segment size outside the allowable range 131,072 through 1,048,576 bytes. Effect. The command failed. Recovery.
B NBEXEC This appendix describes NBEXEC, the NetBatch executor program: Topic Page Introducing NBEXEC B-1 Command and Variable Reference Summary B-3 NBEXEC Syntax Summary B-5 Note. For detailed information on the NBEXEC program, print the TFORM disk file NBEXDOC in the NetBatch installation subvolume. NBEXDOC describes NBEXEC’s features and functions, and describes and gives examples of the syntax, operation, and results of NBEXEC commands and variables.
Log Files NBEXEC Log Files Each NBEXEC process logs to its OUT file details of the interaction between the process, the control file, and controlled processes. Each OUT file has three parts: • • • A timestamped header that lists the job’s defaults and execution environment A timestamped list of the commands executed and their responses Termination lines that record the completion status of the job For a sample NBEXEC log file, see the example in High PIN Capabilities.
Command and Variable Reference Summary NBEXEC PROGRAM NBEXEC, IN $NB.INFILES.ZBATWARM, OUT [#MYTERM], STARTUP "ID D940920, LIMIT 00:10" Job ZBAT-WARM-START Jobnumber 1 submitted > PAUSE NBEXEC T9190D30 - (31OCT94^01JUN94) - 20 Sep 1994 09:06:12 (C)1986 Tandem (C)2004 Hewlett Packard Development Company, L.P. JOB ID: D940920 SYSTEM SUPERVISOR: \MELBDEV.$SCHD JOB NUMBER: 1 NBEXEC PROCESS NAME: \MELBDEV.$X630 HOME TERMINAL: Self CURRENT VOLUME: \MELBDEV.$NB.INFILES USERID: 255,255 USERNAME: SUPER.
NBEXEC-Defined Variables NBEXEC • • • :ACTIVATE :DELETE DEFINE :PURGE :SUSPEND :ADD DEFINE :FILES :RENAME :SYSTEM :ASSIGN :LOGON :RUN :TIME :COMMENT :OBEY :SET DEFINE :VOLUME :CLEAR :PARAM :STATUS :WHO :CREATE :PPD :STOP ! (exclamation point) indicates a nonexecutable comment. * (asterisk) indicates data that NBEXEC passes to a process it starts. . (period) indicates a label.
NBEXEC Syntax Summary NBEXEC NBEXEC Syntax Summary This subsection provides a quick reference to NBEXEC command and variable syntax. The table includes the syntax of the TACL RUN command that runs the NBEXEC program. Command to Run NBEXEC [ RUN ] [ \node. ] [ volume.
Control-file ($) Commands NBEXEC S[YNTAX] causes NBEXEC to validate the syntax of, but not execute, statements in filename.
Command-Interpreter (:) Commands NBEXEC • $PAGE determines whether NBEXEC issues a new page on receiving an OPEN or CLOSE system message from a process it started: $PAGE { OFF ON } • $RELEASE causes NBEXEC to release one or more dependent NetBatch jobs: $RELEASE [ [ \node.
Command-Interpreter (:) Commands NBEXEC For a description of logical-unit, see the description of the CLEAR command in the TACL Reference Manual. • :COMMENT causes NBEXEC to ignore the rest of the command line. (As an alternative to :COMMENT, use an exclamation point.
Command-Interpreter (:) Commands NBEXEC • :RUN runs a program: :[ RUN ] program-file-name [ /run-option [ ,run-option ]… / ] [ param-set ] run-option is a TACL RUN command option. For a list and descriptions of the options, see the RUN[D] command description in the TACL Reference Manual. param-set specifies program parameters for program-file-name.
Other Commands NBEXEC Other Commands • ! (exclamation point) causes NBEXEC to ignore the rest of the command line. (As an alternative to !, use :COMMENT.) ! [ comment-text ] • * (asterisk) is the identifier of data that NBEXEC passes to a process it starts: * data • . (period) is the identifier of a label marking the start of a section in a control file: .
NBEXEC-Defined String Variables NBEXEC • #BPID contains the NBEXEC process name: #BPID • #CC contains the text representation of the completion code supplied in the last stop message received by NBEXEC from a waited process: #CC • #HOME contains the name of the home terminal of the NBEXEC process: #HOME • #JOBID contains the number of the current NBEXEC job: #JOBID • #NEXTBLOCK contains the number of bytes in each block of records in the file: #NEXTBLOCK • #NEXTCODE contains the file code: #NEX
NBEXEC-Defined String Variables NBEXEC • #PID contains the ID of the process started by the last :RUN command: #PID • #TI contains the text representation of the termination information supplied in the last stop message received by NBEXEC from a waited process: #TI • #TIME contains the current time plus or minus a specified number of minutes: #TIME [ { + - } minutes ] • #TODAY contains the current date plus or minus a specified number of days: #TODAY [ { + - } days ] NetBatch Manual—522460-004 B -
C National Language Support This appendix explains how to change BATCHCOM keywords and messages to suit your operational environment. To change the keywords and messages, use BATCHUTL, the NetBatch national-language-support program. Changing BATCHCOM Keywords and Messages Step 1: Log On as the Super ID Log on as the super ID (255,255): > LOGON SUPER.SUPER, password Consideration Logging on as the super ID lets you avoid security violations when completing the procedure.
National Language Support Step 4: Change Keywords and Messages in EDIT Source File BATCHLIB-file specifies the BATCHLIB file from which you want to extract keywords and messages. EDIT-file specifies the name of the EDIT file BATCHUTL creates for the keywords and messages it extracts from BATCHLIB-file. n is a number in the range 0 through 6 identifying the keyword and message source. You use this number in the RUN BATCHUTL command at Step 5 when converting EDIT-file to a TAL source file.
Step 4: Change Keywords and Messages in EDIT Source File National Language Support message^literal is a valid TAL literal. message^literal is for HP internal use only. number is a message number. number is for HP internal use only. severity-indicator is a message-severity indicator with a value of 0 (informational message), 1 (warning message), or 2 (error message). The default is 2. severityindicator is for HP internal use only. message-text is user-modifiable text.
Step 4: Change Keywords and Messages in EDIT Source File National Language Support • A line-break character in message-text makes BATCHCOM wrap text to the next line after the character. Message Displays BATCHCOM displays messages in the form: message-number - severity-character message-text message-number is the message number. severity-character is the message-severity character as specified by message 0. message-text is the message text.
National Language Support Step 4: Change Keywords and Messages in EDIT Source File Vocabulary The EDIT-file section beginning with =VOCAB contains a NetBatch vocabulary. For example: =VOCAB ABORTED T^001 . . Editing Keywords, Days, Months, Times, and the Vocabulary You can edit the names associated with various tokens in the EDIT file and include aliases for keywords. These considerations apply: • • • • • • • • • • A name must have a unique token number T^ number; for example, T^010.
Step 5: Convert EDIT Source File to TAL Source File National Language Support Step 5: Convert EDIT Source File to TAL Source File Run BATCHUTL with the COMPILE-SYMBOLS parameter to convert the EDIT file to a TAL source file: > BATCHUTL /IN EDITSRC, OUT TALSRC/ COMPILE-SYMBOLS 1 Considerations Run the BATCHUTL program to convert the modified EDIT file to a TAL source file: [ RUN ] BATCHUTL / IN EDIT-file , OUT TAL-source-file / C[OMPILE-SYMBOLS] [ n ] EDIT-file specifies the name of the EDIT file created
National Language Support Step 8: Assign Updated BATCHLIB File to BATCHCOM Considerations You can bind up to seven such objects into BATCHLIB (each object specifying a set of keywords and messages identified by the BATCHUTL run parameter n).
National Language Support Step 9: Add DEFINE =_ZBAT_NLS to the TACL Environment DEFINE =_ZBAT_NLS to the TACL environment by using this ADD DEFINE command: ADD DEFINE =_ZBAT_NLS, CLASS MAP, FILE L n.[ date-format ] n is the number identifying the keyword and message set you want to use. You specified this number for the set at Steps 3 and 5. date-format specifies your preferred date format for command input and output.
Glossary access privileges. Screen and function usage rights assigned by the system administrator to NetBatch-Plus users on a series of three linked screens: Security Supervise, Screen Security, and Utility Security. ad hoc job. A job selected from a list of job names displayed on the Ad Hoc Job Selection screen. You can submit the selected job for execution from either the Ad Hoc Job Selection screen or Job Definition screen.
catalog DEFINEs Glossary catalog DEFINEs. See DEFINE. category. See calendar category and selection category. class. A logical entity in a NetBatch scheduler. Classes control the flow of jobs to executors and therefore to those executors’ CPUs. You can use classes to group jobs according to their demand for system resources. For example, you could group CPU-bound jobs such as program compilations into one class, I/O-bound jobs such as reports into another class, and so on.
dependency Glossary • Tape DEFINEs pass information to the tape process during labeled-tape operations. Tape DEFINE attributes specify parameters such as the tape device name and the record format. dependency. A relationship between two jobs that prevents one of the jobs (the dependent job) from executing before the other job (the master job) releases it. dependent job. A job with the WAITON attribute. Dependent jobs do not execute until released by all the jobs specified by the attribute. EBCDIC.
job attachment Glossary • • Resource requirements such as the number of tape drives the job needs Run information such as timing details, hold flags, and the action to be taken in the event of job failure You can record job descriptions in the NetBatch-Plus database. You can then select jobs from this database at any time and submit them for execution by a NetBatch scheduler. job attachment. An ASSIGN, PARAM, or DEFINE used by a job. You define job attachments on the Job Attachments screens.
one-off job Glossary one-off job. A job submitted from within the NetBatch-Plus application to a NetBatch scheduler and whose details are not recorded in the NetBatch-Plus database. You can create and submit one-off jobs by using the Job Info screen or Ad Hoc Job Selection screen. PARAM. A parameter supplying a user-defined value to a process requesting that value at creation time. Prev Page key. The key you press on your keyboard to display the previous 24 lines of help text.
selection date Glossary selection date. A date used by the bulk submit program to select a job from the NetBatch-Plus database. session. The period of time from when you start and sign on to the NetBatch-Plus application to when you sign off. spool DEFINEs. See DEFINE. Software Product Revision The generic term for a distributed software product object. An SPR is distributed in the form of a Product Version Update (PVU) within a Product Version.SPRs have access, delivery, and sequence attributes.
Index A Abbreviations, of keywords 6-9 ABORT SCHEDULER command description 6-30 synopsis and syntax summary 6-20 ACTIVATE JOB command description 6-32 synopsis and syntax summary 6-15 ACTIVE executor state CPU failure, effect of 7-34 description 3-31, 6-164 scheduler warm start, effect of 3-22 STOP EXECUTOR command, effect of 6-178 ADD ATTACHMENT-SET command description 6-34 synopsis and syntax summary 6-12 ADD CLASS command description 6-40 synopsis and syntax summary 6-13 ADD EXECUTOR command description
A Index ASSUME JOB command description 6-72 synopsis and syntax summary 6-16 ASSUME SCHEDULER command description 6-73 synopsis and syntax summary 6-20 Asterisk (*) wild-card character See Wild-card characters AT job attribute description 7-15 synopsis and syntax summary 7-2 ATTACH scheduler database file 6-48 ATTACH0 scheduler database file 6-48 Attachment set adding 1-9, 4-35, 6-34 altering description 1-9, 4-37, 6-52 See also Attachment set, deleting attribute default values 6-35 attribute descriptions
A Index Attribute descriptions (continued) DEFAULT-HIGHPIN 7-39 DEFAULT-MAXPRINTLINES 7-40 DEFAULT-MAXPRINTPAGES 7-41 DEFAULT-OUT 7-42 DEFAULT-PRI 7-43 DEFAULT-SELPRI 7-44 DEFAULT-STALL 7-45 DEFAULT-STOP-ON-ABEND 7-46 DEFINE 7-47 DESCRIPTION 7-52 EMS 7-54 EVERY 7-55 EXECUTOR-PROGRAM 7-58 EXTSWAP 7-60 HIGHPIN 7-61 HOLD 7-62 HOLDAFTER 7-63 IFFAILS 7-64 IN 7-66 INITIATION (class) 7-68 INITIATION (scheduler) 7-69 JOBID-ZERO 7-73 JOB-LOG 7-70 LIMIT 7-75 LOCALNAMES 7-77 MAXPRINTLINES 7-82 MAXPRINTPAGES 7-83 MAX
B Index A, N, G, C, O, U, - (security codes) descriptions for SECURITY attribute 7-99 for VOLUME attribute 7-116 for VOLUME command 6-197 B BACKUPCPU scheduler attribute description 7-23 synopsis and syntax summary 7-6 BATCHCAL command descriptions 5-13 definition 1-4 high PIN capabilities 1-12, 5-4 BATCHCOM attributes descriptions 7-8 synopses and syntax summaries 7-1 changing keywords and messages C-1 commands descriptions 6-28 security of 6-23 synopses and syntax summaries 6-11 completion codes return
C Index Class (continued) command descriptions ADD CLASS 6-40 ALTER CLASS 6-58 ASSUME CLASS 6-70 DELETE CLASS 6-81 INFO CLASS 6-103 RESET CLASS 6-119 SET CLASS 6-133 SHOW CLASS 6-145 configuration 3-6 definition 3-6 deleting 1-6, 3-37, 6-81 displaying 3-31, 6-103, 6-145 CLASS executor attribute description 7-30 synopsis and syntax summary 7-2 CLASS job attribute description 7-32 synopsis and syntax summary 7-2 CLASS keyword, alias of JOBCLASS 6-11 Command descriptions ABORT SCHEDULER 6-30 ACTIVATE JOB 6-3
D Index Command descriptions (continued) SHOW ATTACHMENT-SET 6-142 SHOW CLASS 6-145 SHOW EXECUTOR 6-146 SHOW JOB 6-147 SHOW SCHEDULER 6-150 SHUTDOWN SCHEDULER 6-152 START EXECUTOR 6-155 START SCHEDULER 6-157 STATUS ATTACHMENT-SET 6-160 STATUS EXECUTOR 6-163 STATUS JOB 6-165 STATUS SCHEDULER 6-173 STATUS-HISTORY 6-175 STOP EXECUTOR 6-178 STOP JOB 6-180 SUBMIT JOB 6-183 SUSPEND JOB 6-190 SWITCHCPU SCHEDULER 6-192 SWITCHLOG SCHEDULER 6-193 SYSTEM 6-195 VOLUME 6-196 ! (exclamation point) 6-198 == (double equa
D Index DEFAULT-STALL scheduler attribute description 7-45 synopsis and syntax summary 7-7 DEFAULT-STOP-ON-ABEND scheduler attribute description 7-46 synopsis and syntax summary 7-7 DEFINE attributes 7-48 catalog DEFINE attributes 7-48 definition 7-48 default class 7-47 defaults DEFINE attributes 7-48 definition 7-48 definition 7-47 map DEFINE attributes 7-48 definition 7-48 search DEFINE attributes 7-48 definition 7-48 sort DEFINE attributes 7-49 definition 7-48 spool DEFINE attributes 7-50 definition 7-
E Index E EMS parameter, in RUN NETBATCH command 3-12, 3-44, 7-54 EMS scheduler attribute description 7-54 synopsis and syntax summary 7-7 End-of-file condition See CTRL/Y 6-92 EOF See CTRL/Y Equals, double (==) See == (double equals) Error 11, on scheduler warm start 6-177 Error 12, on scheduler warm start 3-21 Error 201, on scheduler warm start 3-21 Error messages A-1 EVENT job state, description 4-42, 6-169 Event-message generation, enabling and disabling 3-12, 3-44, 7-54 EVERY job attribute descriptio
G Index G GMOM definition 1-9 See also GMOMJOBID GMOMJOBID definition 1-9, 4-10 displaying 4-10 dissociating a job from the scheduler 4-12 dissociating a process from a job 4-11 process identification, tracking, and control, use in 1-9, 4-10 See also JOBID-ZERO job attribute specifying TERM, IN, OUT, and NOWAIT for a dissociated process 4-12 Guidelines, planning See Planning guidelines H HELP command in BATCHCAL 5-14 in BATCHCOM description 6-95 help text file 6-3 synopsis and syntax summary 6-22 High PI
J Index INFO EXECUTOR command description 6-104 synopsis and syntax summary 6-14 INFO JOB command description 6-106 synopsis and syntax summary 6-16 INFO SCHEDULER command description 6-110 synopsis and syntax summary 6-20 Information Message Management Utilities (IMMU), definition 6-3 INITIATION class attribute description 7-68 synopsis and syntax summary 7-1 INITIATION scheduler attribute description 7-69 synopsis and syntax summary 7-7 Input file defaults, specifying 4-21 definition 4-7 purging 4-21 sp
K Index command descriptions (continued) SET JOB 6-136 SHOW JOB 6-147 STATUS JOB 6-165 STATUS-EXECUTING 6-11, 6-166, 6-172 STATUS-HISTORY 6-175 STATUS-READY 6-11, 6-166, 6-172 STATUS-USER 6-11, 6-166, 6-172 STOP JOB 6-180 SUBMIT JOB 6-183 SUSPEND JOB 6-190 Job control language 1-2 JOB scheduler database file description 6-49 renamed to JOBSAVED 3-21, 3-25 JOBCLAS0 scheduler database file 6-49 JOBCLASS scheduler database file 6-49 JOBCLASS, alias of CLASS 6-11 JOBID-ZERO job attribute description 7-73 syno
M Index Low PIN definition 7-61 running executor-program processes at 7-61 See also High PIN M Macros ZBAT JOBINFO 4-12 ZBAT RELEASE 4-32, 7-120 Management job 4-42 scheduler 3-29 MAXPRINTLINES job attribute description 7-82 synopsis and syntax summary 7-3 MAXPRINTPAGES job attribute description 7-83 synopsis and syntax summary 7-4 MAX-CONCURRENT-JOBS scheduler attribute description 7-79 synopsis and syntax summary 7-7 MAX-PRI scheduler attribute description 7-81 synopsis and syntax summary 7-7 MEM job a
O Index Nested OBEY commands definition 6-112 maximum number 6-112 NetBatch product ASSIGN, DEFINE, and PARAM propagation 1-3 command interpreter 1-4 CPU assignment 1-2 EMS interface 1-3 files restoring to distribution subvolume 2-1 updating installation subvolumes 2-1 national-language support C-1 programmatic job submission and alteration 1-3 softdoc 2-2 spooler support 1-3 supervisor, definition 6-23 NETBATCH program core component of NetBatch product 1-4 default log file size 3-20, 3-39, 6-194 definit
P Index executor state (continued) STOP EXECUTOR command, effect of 6-178 OFF executor state scheduler warm start, effect of 3-22 ON class state, description 6-103 executor state CPU failure, effect of 7-34 description 3-31, 6-164 scheduler warm start, effect of 3-22 START EXECUTOR command, effect of 6-155 STOP EXECUTOR command, effect of 6-178 ON executor state scheduler warm start, effect of 3-22 Online help See HELP command OPEN command description 6-113 synopsis and syntax summary 6-21 Openers (schedu
Q Index PFS job attribute (continued) synopsis and syntax summary 7-4 use in commands SET JOB 6-136 PIN definition 6-6 See also High PIN or Low PIN Planning guidelines job 3-1, 4-1 scheduler 3-1 PMSEARCHLIST variable, function when running BATCHCAL 5-3 when running NETBATCH 3-11 PRI job attribute description 7-92 synopsis and syntax summary 7-4 Processes high PIN capabilities of BATCHCAL 1-12, 5-4 BATCHCOM 1-12, 6-6 executor program 7-61 NBEXEC 1-12, B-2 NETBATCH 1-12, 3-13 Prompts }} (double braces) in C
S Index RUNNEXT job state, description 4-43, 6-170 RUNNOW JOB command description 6-128 synopsis and syntax summary 6-17 RUNNOW job state, description 4-43, 6-170 S SAVEABEND job attribute description 7-98 synopsis and syntax summary 7-4 Scheduler adding 3-9, 6-46 algorithm (scheduling), description 1-11 altering 3-31, 6-67 attachment set See Attachment set attribute default values 6-47 attribute descriptions AT-ALLOWED 7-18 BACKUPCPU 7-23 CATCHUP 7-28 DEFAULT-CLASS 7-36 DEFAULT-EXECUTORPROGRAM 7-38 DEFA
S Index SHOW ATTACHMENT-SET command description 6-142 synopsis and syntax summary 6-13 SHOW CLASS command description 6-145 synopsis and syntax summary 6-14 SHOW EXECUTOR command description 6-146 synopsis and syntax summary 6-15 SHOW JOB command description 6-147 synopsis and syntax summary 6-18 SHOW SCHEDULER command description 6-150 synopsis and syntax summary 6-21 SHUTDOWN SCHEDULER command description 6-152 synopsis and syntax summary 6-21 SPECIAL-n job state description 4-43, 6-170 SPI (Subsystem P
T Index SYSTEM command description 6-195 synopsis and syntax summary 6-23 T TAPE job state, description 4-43, 6-172 TAPEDRIVES job attribute description 7-109 synopsis and syntax summary 7-5 TAPEDRIVES scheduler attribute description 7-110 synopsis and syntax summary 7-7 TEMPORARY attachment-set attribute description 7-112 synopsis and syntax summary 7-1 Temporary executor See Executor, temporary TEMP_EXEC_... See __TEMP_EXEC_...
Special Characters Index Special Characters ! (exclamation point) command description 6-198 synopsis and syntax summary 6-23 $RELEASE command, releases dependent jobs 4-33 & (ampersand), line continuation character 6-76 ? (question mark) command description 6-200 synopsis and syntax summary 6-23 wild-card character See Wild-card characters __TEMP_EXEC_...
Special Characters Index NetBatch Manual—522460-004 Index -20
