DAT2330 - Harold Smith Class - Tue Feb  2, 2000

Today: review homework - "MVS JCL Example 1 Homework"

- begin with a flow diagram (not required on job or exam)
  - use it if you find it helpful; as messy as you please
- most examples are cobol compiles
  - that's the most likely thing you will be doing on the job
- use the given COBCLG proc 
  - called up from sys1.proclib when job submitted to JES
  - we may have to go fishing to find the name
  - ask, or list the contents of sys1.proclib!
- we must add the JCL for the things not specified in the PROC
- CLG is compile, link, and GO
- remember to qualify the DDnames with the matching step names in the proc
- if you can't find out the internal proc step names
  - ask someone
  - make something up and watch for the error messages
- dotted box (proc) means dotted DDnames!
- you must use the DDnames given

- why doesn't the link step have DDnames?
  - all taken care of in the PROC

- DDnames are associated with the programs, not with the dataset
  - you can't usually use the same DDname for different programs
  - DDname must match the program

- use a fixed-width font for JCL coding
  - suggest Courier size 11 or 12 (if using a word processor)

- You can bring one side of one letter page cheat sheet for tests
  - it must be your own
  - similar sheets are discarded

- refer to JCL checklist (Basics) slide
- positional parameters precede keyword parameters
- billing is often done even if it's your own computer
  - shop tracks which team uses more/less CPU
- UPPER CASE ONLY
- blanks start comments
- picking a class
  - not a random choice
  - different for each shop
  - you can't experiment with this one - must be told
  - typically, low-alpha classes are better service, less resources
  - submitting a job in the wrong class will cause job failure
  - confusing letter sounds; use: Able, Baker, Charie, Dog, Easy, Fox

//coboltst   job  4444,'your name',class=d
//clgstep    exec proc=cobclg

- check flow diagram to count DD statements
- what is the output of the COB step
  - what does a compiler produce?
  - should I put a DD statement for this output?
    - no, that's handled by the PROC
- ordering of DD statements for MVS?
  - order of steps for PROC must be in PROC order
  - COB before link before GO
  - order within the steps doesn't matter to MVS
    - matters to instructors who want instream data LAST

//cob.sysin   DD *
...cobol program goes here (see p.76)...
...this is fed to the cobol compiler...
/*

- sysout classes are different from job classes
- pick the sysout class that matches the output and the requirements

//go.translog DD sysout=b

- "MOD" would be used to extend the length of a sequential dataset
- "OLD" is used to update a dataset in place
- disp=(xxx,keep) would have the dataset deallocated

//go.master   DD dsn=paymast,disp=(old,pass)

- don't leave the tape mounted unnecessarily
- specifications say to delete the tape
- this abbreviated JCL only works because dataset is catalogued
  - catalogue has vol, ser, space, etc.

//go.tranin   DD dsn=testtran,disp=(old,delete)

//verify      exec pgm=viewdata

- we are asked to hold the output for TSO; choose D

//prt         DD sysout=d
//datatin     DD dsn=paymast,disp=(old,keep)
//

Look at course outline to see what we do next; read ahead.
Next class: MVS JCL Example 2 (and attached homework)