Give the correct answer using userid kc$03$b$29$JCL and SDSF $(5$ Marks$)$

Background: In Assignment $1,$ you ran a simple REXX program from the ISPF Command Shell $(=6).$ Now we are qoing to run another REXX program, only this time in batch. In z$/$OS$,$ you have two different ways to do work interactively in the foreground or non$-$interactively in the background $($aka "batch processing"$).$ Allof your work in Assignment $1$ was considered foreground work. You can do a lot of stuft in the foreground, but when a program takes a lot of time to process, you can't do anything else with your interactive session while it's running. The solution is to submit long$-$running programs to process in the background, then you can continue to work interartively and z$/$OS will let you know when your long$-$running program has completed.

In the mainframe world, a "iob" is a collection of different proqrams that work together and runs in the background. In order to cause work to run in batch $($that is to submit a job$),$ you need to instruct z$/$OS through JCL $($Job Control Language$).$ You submit your JCL to JES $($Job Entry Subsystem$)$ and the system allocates the necessary resources for your job, then executes the work when the resources are available. Understanding JCL is a very important skill to have, so you'll be seeing more of it throughout the rest of Assianment $2.$

Most systems and applications proarammers will find a piece of existing JCL code that does something very close to what they want to do$,$ and then make a few little chanqes to it so that it fits their needs. You're going to do the same thing in this challenge.

Your challenge: Submit JCL to execute a REXX exec as a batch job.

First, edit member RUNREXX in KCO$3$##$.$ASSIGN$2.$JCL$.$ This member contains a job that is very close to what you need. Inside that member, edit the job name so that it ends with the last three hexadecimal digits of your user ID$.$ For example, change it to REXXD$11$ if your ID is KC$03$D$11.($REXX## is the jobname. The jobname is the very first thing in the JCL job, and it identifies the job to the system.$)$ From here on out, whenever you see three # signs in a row, you can assume that vou need to replace them with the last three hexadecimal digits of your user ID$.$

Pn the command line, enter SUB $($short for submit$).$

This will send your JCL$,$ which you can also call your job, to JES for processing. JES manages all jobs submitted to the zOOS system. JES will put your job on a queue $($called an "initiator"$),$ which helps decide when to submit your job for exerution, and helps allocate some resources needed for the iob. When your job runs, JES manages output from your job $($and all other iobs that are submitted$)$ in a special set of data sets called the "spool". Press Enter to see the results of your submission. See the text MAXCC $=0$ inside the system generated message? That means that your iob$-$ran with a return code of $0,$ which is qood news. Press Enter again to dismiss the message and return to your job.

To check the status of your job, enter the following on the command line:

tso status REXX###

which should tell you that your job is on the output queue.

To display the output produced when your job ran we use the Spool Display and Search Facility $($SDSF$).$

To get to SDSF on the Marist system, enter SD from the ISPF Primary Option Menu or $=$SD from any ISPF command line. From the SDSF Primary

OWNER KCO$3$H##

This filters the output so that you only see your own jobs. Then enter the following SDSF command:

ST

SI$,$ or STATUS, will display the status of all tasks owned by OWNER KC$03$###$.$

Note: If you've already set the PREFIX option to KC$03$###$\text{'}$ for the labs just reset it by entering prefix without any parameters $($i$.$e$.$ PREFIX$).$

View vour output, along with some system qenerated output, by entering a $?$ to the left your iobname. The jobname specified in your JCL job was REXX##$.$ Enter $S($select$)$ to the left of each piece to see output of your iob.

F$3$ will exit each piece of the output and a second F$3$ will return to the panel that lists the entire REXX### job in the JES output queue.

Enter an $S$ to the left of REXX###$.$

What you'll see now is all your output in one place. Entering $?$ to the left of the jobname separates the output into logical sections $($these sections are called DDNAMES$).$ Entering $S$ to the left of the jobname will display all the logical sections concatenated as a continuous stream of output. To view all, of the output, you'll need to use F$7$ and F$8$ to scroll up and down, and F$10$ and F$11$ to scroll left and right.

At the bottom of the output $($in the OUTDD section$),$ you'll see a list of all users who are currently logged into the Marist system.

After viewing the output of your iob, you need to write out all of the output to a member of vour ASSIGN$2.$ WORK data set called RUNREXX.

To do this, press F$3$ to return to the status queue, thes navi