------------------------ Exercise #5 for DAT2330 due March 23 ------------------------ -Ian! D. Allen - idallen@idallen.ca Remember - knowing how to find out an answer is more important than memorizing the answer. Learn to fish! RTFM! (Read The Fine Manual) Global weight: 2% of your total mark this term Due date: 11h00 (11am) Tuesday, March 23, 2004. The deliverables for this exercise are to be submitted online on the Course Linux Server using the "datsubmit" method described in the exercise description, below. No paper; no email; no FTP. Late-submission date: I will accept without penalty exercises that are submitted late but before 14h30 (2:30pm) on Friday, March 26. After that late-submission date, the exercise is worth zero marks; but, it must still be completed and submitted successfully to earn credit in the course. This exercise is due on or before 11h00 (11am) Tuesday, March 23, 2004 JCL Notes Location: You can find copies of the JCL Notes under this directory on the Course Linux Server: ~idallen/public_html/teaching/dat2330/04w/jclnotes/ And under here on ACADUNIX: ~alleni/public_html/teaching/dat2330/04w/jclnotes/ OS/390 Reference: See the week10notes.txt file for the IBM Manual URLs. The HTML Manual has section numbers. The PDF manual does not. Readings in "IBM MVS JCL User's Guide": 1.0 Introduction 1.1 Chapter 1. Introduction - Job Control Statements 1.1.1 JCL Statements Only these three: JOB, EXEC, DD 1.2 Chapter 2. Introduction - Job Control Language (JCL) 1.2.1 Understanding JCL 1.2.1.1 "Chez MVS" 1.2.1.2 How This Relates to JCL 1.2.1.3 Job Control Statements 1.2.1.4 Required Control Statements 1.2.2 Exercise: Creating and Entering a Job - since you do not have an MVS system on which to practice, some of the information in this Exercise section is "skim only" - the screen shots look best in the PDF file, not in HTML 1.2.2.1 Before You Begin 1.2.2.2 Step 1. Allocate a Data Set to Contain Your JCL 1.2.2.3 Step 2. Edit the JCL Data Set and Add the Necessary JCL 1.2.2.4 Step 3. Submit the JCL to the System as a Job 1.2.2.5 Step 4. View and Understand the Output from the Job 1.2.2.6 Step 5. Make Changes to Your JCL 1.2.2.7 Step 6. View and Understand Your Final Output 1.3 Chapter 3. Job Control Tasks 1.3.1 Entering Jobs 1.3.2 Processing Jobs 1.3.3 Requesting Resources 1.3.4 Task Charts - Omit the Tasks Charts themselves; read only the text of this page. - Note well the two minimum required statements. 2.0 Tasks for Entering Jobs 2.1 Chapter 4. Entering Jobs - Identification 2.1.1 Identification of Job 2.1.2 Identification of Step 2.1.5 Identification of Account 2.1.6 Identification of Programmer 2.2 Chapter 5. Entering Jobs - Execution 2.2.1 Execution of Program - Omit material on temporary libraries 2.2.2 Execution of Procedure - Omit material on in-stream procedures 2.4.3 Communication from JCL to Programmer Readings in "IBM MVS JCL Reference": 1.1 JCL Statements: Only these three: JOB, EXEC, DD 3.0 Chapter 3. Format of Statements 3.1 JCL Statement Fields: All syntax descriptions. In Figure 3-1, only: Comment, DD, Delimiter, EXEC, JOB, Null 3.4 Continuing Statements 3.4.1 Continuing JCL Statements 3.4.1.1 Continuing the Parameter Field 3.4.2 Examples of Continued Statements - Examples 1 and 2 only 4.0 Chapter 4. Syntax of Parameters 4.1 Notation Used to Show Syntax 4.2 Character Sets 4.3 Syntax Notes Exercises: 1) Time yourself on how long it takes you to do this next exercise. (Your JCL Final Exam, during exam week, is about 50 lines of JCL that you must type in using the VIM editor. Speed and accuracy will be important.) Using VIM, enter the 15 lines of JCL given in file accuracy_test.png (under JCL Notes) into a file named "accuracy_test.txt". Do not copy the file from other students; type it in yourself. This exercise is to help you know how accurate you think you are in typing precise JCL. Many students are unaware of the typing errors they make when copying JCL exactly. This exercise will help you become aware of your own inaccuracies. The JCL must be entered exactly, including counting *spaces*, *punctuation*, and CAPITAL LETTERS! No blank lines are allowed. All the lines start in column 1. Every space and comma is important. No tab characters are allowed. Be *exact*! The correct file will contain 518 characters and a "sum" of 39659. 2) Copy and read the file "expljcl.txt" (under JCL Notes). Follow the directions contained in the file. Name your annotated answer file "explained.txt". 3) Using the JCL Reference Manual, identify all the syntax error in the JCL file "badjcl.txt" (under the JCL Notes button on the course home page). (In addition to syntax errors, there is one incorrectly spelled parameter and another incorrectly spelled parameter value.) Copy the badjcl.txt file and correct the JCL errors. Name your corrected JCL file "goodjcl.txt". Deliverables: Use the "datsubmit" command to submit your three files to me as Exercise #5 on the Linux Course Server: $ datsubmit 5 accuracy_test.txt explained.txt goodjcl.txt Marking: The intent of this exericise is to have you *think* about the JCL topics covered this week. I will not correct the mistakes in the exercise homework you submit; since, I will be doing that in class next week. Bring a copy of your submission to class and correct your own mistakes. You receive marks for your exercise if it is an original, reasonable effort at solving the exercise problem, even if it contains some errors. Exercises that are not original (including copies of posted solutions) will be treated as plagiarism. (See the course home page regarding plagiarism.) Handed-in JCL homework is marked for rough quantity, not quality; you earn marks for doing the homework even if it may have minor errors. We correct all homework carefully in class each week - that is where you learn to find the errors in your own JCL.