Solutions to Module 3: Batch Processing

Check Your Answers

	Is Your Answer ... ?	If Not, Start With
1.	b,c	Lesson 1
2.	`SCHED, WAIT, INTRO, EXEC, SUSP`	Lesson 1
3.	jobfence session limit input priority job limit	Lesson 1
4.	`!JOB JOBx,USERx/UPASSx.&!ACCTx/APASSx;INPRI=8;OUTCLASS=LP,1!PRINT MYFILE1;OUT=*LP!EOJ`	Lesson 2
5.	`STREAM JOBFILE` `STREAM JOBFILE;AT=23:00` `STREAM JOBFILE;DAY=MON;` `AT=8:00` `STREAM JOBFILE;DAY=WED;AT=22:00`	Lesson 3
6.	`BREAKJOB, ALTJOB, RESUMEJOB, STREAM, ABORTJOB`	Lesson 4
7.	`CREATE, READY, ACTIVE, OPEN, PRINT, DEFER, SPSAVE, PROBLM, DELPND, XFER` In `PRINT` state, file is printing. `READY` means that the spool file is ready for printing. `CREATE` means that the spool file is being created as output.	Lesson 4
8.	`LISTSPF, SPOOLF, PRINT`	Lesson 4

Lesson 1 Introducing Jobs

Q 3-1

	Characteristic	Jobs	Session
a.	interactive processing.		`X`
b.	synonymous with batch processing.	`X`
c.	does not require constant supervision.	`X`
d.	submits a single command at a time.		`X`
e.	can be scheduled to run at specified time.	`X`
f.	most time/resource efficient.	`X`
g.	Executes with STREAM command.	`X`

Q 3-2

Only J32 is executing.

Q 3-3

Job J35 is being submitted.

Q 3-4

J30 is awaiting execution.

Q 3-5

(b) Only JOBB executes since its input priority is above the jobfence.

Q 3-6

The job will be listed as WAIT.

Q 3-7

J35 was streamed at 5:45 A.M.

Q 3-8

J35 was submitted from the PROJECT account by the STATS user.

(Note: It is possible for a user other than STATS, working in an account other than PROJECT, to submit this job.)

Q 3-9

Currently, a maximum of 11 jobs and 20 sessions can be run on this system.

Q 3-10

Since only two jobs are executing, nine more jobs could be submitted for execution.

Q 3-11

No jobs have been suspended.

Q 3-12

Job #J34 will run at 10:00 P.M.

Q 3-13

SHOWJOB command parameters

list job summary information: SHOWJOB STATUS
list jobs which have been scheduled: SHOWJOB SCHED
list information on all jobs: SHOWJOB JOB=@J
list information on Job 105: SHOWJOB #J105
list status of all jobs that you might have submitted from your account: SHOWJOB JOB=USERx.ACCTx

Exercise 3-1: Lesson 1 Review

1.: TRUE
2.: FALSE
3.: TRUE
4.: TRUE
5.: FALSE

************* End of Exercise 3-1 ***********

Lesson 2 Examining a Job File

Q 3-14

JOB Command Parameter	Required	Optional
User Name	`X`
Account Name	`X`
Group Name		`X`
Job Name		`X`
Time		`X`
`INPRI`		`X`
`RESTART`		`X`
`OUTCLASS`		`X`
`SPSAVE`		`X`

Q 3-15

MYJOB1 is the job name; ACCTx is the account name; USERx is the user name; CLASS is the group name.

Q 3-16

No. The group password should be inserted in the !JOB command in order for MYJOB1 to run.

   !JOB MYJOB1,USERx/UPASSX...CLASS/LASER..

Q 3-17

If the system crashes and you do not have the RESTART parameter in your !JOB command, your job will not continue processing when the system is restarted, even if the operator uses the RECOVERY option.

Q 3-18

Q 3-19

The job listing from MYJOB1 is scheduled to be printed on the line printer (LP). The outclass priority is 1 (which means the job listing will not print).

Q 3-20

MYJOB1 IS DONE!! prints on USERx's screen when MYJOB1 completes processing.

Q 3-21

This line accesses the editor.

Q 3-22

This line texts in MYFILE1 so that it can be listed with the L ALL, OFFLINE command.

Q 3-23

The print priority of the output is 1. The line printer (LP) is scheduled to print the output; however, the output does not print until the priority, currently 1, has a value above the outfence.

Exercise 3-2: Lesson 2 Review

!JOB MYJOB2, USERx/UPASSX.ACCTx/APASSX
SHOWJOB STATUS (to verify jobfence)
!JOB MYJOB2...;INPRI=10 (or 1 greater than the jobfence);...
!JOB MYJOB2,....ACCTx/APASSX,CLASS ;INPRI=10;RESTART;....
!JOB MYJOB2.....;OUTCLASS=LP,1
The line following !EDITOR should read T MYFILE2.CLASS
Add a line after EXIT: !TELL USERx.ACCTx MYJOB2 IS COMPLETE!!

The modified MYJOB2 file should now look like the following:

   !JOB MYJOB2,USERx/UPASSX.ACCTx/APASSX,CLASS;&

   !INPRI=10;RESTART;OUTCLASS=LP,1

   !COMMENT MYJOB2 PRINTS MYFILE2

   !CONTINUE

   !EDITOR

   T MYFILE2.CLASS

   L ALL, OFFLINE

   EXIT

   !TELL USERx.ACCTx MYJOB2 IS COMPLETE!!

   !EOJ<\esc>

*********** End of Exercise 3-2 **********

Lesson 3 Creating and Streaming a Job File

Q 3-24

The state of the job is EXEC.

Depending on how your terminal is set up, the state of your session may be EXEC QUIET. This means that no messages can be sent to your terminal screen.

Q 3-25

The job state is SCHED. This means that the job is scheduled to run at a later time.

Q 3-26

You should match the descriptions and command as follows:

	Command		Description
1.	`STREAM JOBFILE`	d.	Job runs immediately.
2.	`STREAM JOBFILE` `;AT=8:00`	c.	Job will run today, at 8:00 A.M.
3.	`STREAM JOBFILE` `;AT=20:00`	g.	Job will run today, at 8:00 P.M.
4.	`STREAM JOBFILE` `;IN=,+8`	f.	Job will run today, 8 hours from now.
5.	`STREAM JOBFILE;` `IN=+1,+8`	h.	Job will run tomorrow, 8 hours from now.
6.	`STREAM JOBFILE;` `DATE=08/09/89;` `AT=20:00`	b.	Job will run on August 9 at 8:00 P.M.
7.	`STREAM JOBFILE` `;DAY=MONDAY` `;AT=22:00`	a.	Job will run on Monday, at 10:00 P.M.
8.	`STREAM JOBFILE;` `DATE=08/09/89`	e.	Job will run on August 9, at the same time you execute the `STREAM` command today.

Q 3-27

The job will execute on the day specified, at the time that matches the time when the job was submitted.

Q 3-28

When you do a SHOWJOB #Jxxx, you should see this message after the job has been aborted:

   NO SUCH JOB(S)



   JOBFENCE=x;JLIMIT=y;SLIMIT=z

Q 3-29

The job is supposed to run at midnight. Even though the job has not yet run, use the ABORTJOB command. It works on scheduled jobs, as well as executing jobs.

Q 3-30

The status of the job is SUSP.

Q 3-31

The status of the job is now EXEC.

Q 3-32

The job is in WAIT state.

Q 3-33

The job is in EXEC state.

Lesson 4 Monitoring Job Progress

Q 3-34

There is one file associated with JOB1:

$STDLIST




	NOTE: If you do a `LISTSPF` at just the right moment, a spool file called `EDTLIST` may appear in the display. `EDTLIST` is a transitory spool file associated with the editor.

Q 3-35

The priority of the $STDLIST spool file is 1. This should be below the outfence, which is generally 7.

Q 3-36

When the spool file is no longer active the spool file "disappears" from the LISTSPF display.

Exercise 3-4 Aborting a Job and Using PRINT

2.

If you use PRINT and attempt to access the job listing spool file before the job has completed, you will be unable to look at the file because it is not Ready.

You can use PRINT to examine the spool file while it is still in the CREATE state.

3a.

If you did not alter the priority, the file, with any errors, would print on the line printer.

3c.

Yes, you can now access and view the job listing.

3d.

The following message appears at the end of the job listing.

4.

The state of the spool file (now that the job has been aborted) is Ready.

   *** JOB ABORTED BY SYSTEM MANAGEMENT ***

5.

Display remaining spool files and purge them.

   LISTSPF @;SELEQ=[OWNER=USERx.ACCTx]

Abort any job that still as a $STDIN spool file. Use ABORTJOB.

   SPOOLF (!!filenumber, filenumber, ...!!)SELEQ=[OWNER=USERx.ACCTx];DELETE

Purge those spool files.

   >EXIT

*********End of Exercise 3-4 *************

Solutions to Module 3: Batch Processing

Technical documentation

» Table of Contents

» Glossary

» Index