This example is based on a lab from DAT2330 Winter 2000. It is provided here as another example for Spring 2001. =================================== DAT2330 Winter 2000 - MVS JCL Lab 1 =================================== -IAN! idallen@ncf.ca from an example by Harold Smith If any information that is required is missing, make a guess as to what it might be, and put a note in the comments at the top of the JCL indicating how you would find out what it ought to be if this info was missing 'on the job'. Code all JCL for the following job, which will process bank charges, and print statements. Use your own name as programmer name, and account number MVSLAB1. All tapes in our installation are in group called SYSSQ, disks in group SYSDA. Suppress output of messages regarding allocation, etc. Arrange that only your own JCL and JES statements are printed, and when printed they should be held for viewing by TSO. The job should be run as the bottom priority in its queue, when it is finally run; but, for this exercise, code the job to be checked for JCL errors, but not run. First, the charge data (instream) should be copied to a tape, using IDCAMS. Put ANSI labels on the tape. Use tape #454655, and the largest block size suitable for this format of tape. Keep this tape and catalog it after last use. Also hold the printout from this step in the spool queue for verification via TSO. Next, the customer accounts must be updated and statements printed. The program to do this is still at the testing stage, so you will need to compile, link edit, and test the COBOL source program from the input stream. A procedure to do this is available, called COBCLG2. The source program is read by compiler from DDname SYSIN in proc step name COMPIL. The program will be executed in the proc step named TST. It will read the charge data tape records from DDname CUSTINP, and use them to update a catalogued disk master file with dataset name CUSTMSTR, accessed using DDname UPDCUST. Statements will be printed via DDname STMOUTP, and these should be directed to the laser printer. The program being tested will also produce a new tape file of about 2,000 records, on tape #135245 which should be kept in the catalog after last use. It is created using the following COBOL code: SELECT DISK-FILE ASSIGN TO CHRGOUTP. FD DISK-FILE RECORD CONTAINS 90 CHARACTERS BLOCK CONTAINS 0 RECORDS ORGANIZATION IS SEQUENTIAL. After the test, use program IDCAMS to print the new tape file created in the previous step. Do *not* hold the status and error message printout from this step; send it to the printer. Job scheduler classes for this lab should be as follows: CLASS A - no tapes, no special forms - maximum 500 prt lines, 10 mins run time CLASS F - no tapes, no special forms - maximum 5000 prt lines, 1 hour run time CLASS G - 1 tape, special forms allowed - maximum 500 prt lines, 10 mins run time CLASS H - 2 tapes, no special forms - maximum 5000 prt lines, 1 hour run time CLASS I - 2 tapes, special forms allowed - no prt line maximum, no run time limit JES printer spooling classes for this lab should be as follows: CLASS A - no special forms, maximum 500 print lines CLASS D - no special forms, maximum 5000 print lines CLASS E - special forms allowed, no print line maximum CLASS P - all output for laser printer (only) CLASS T - hold output for viewing via TSO