3) I need to create a run...
            A) I can use RDz (Eclipse) and access the Eclipse debugger
                 I will not be able to do this in production
            B) I can create a Unix Shell script and execute it
            C) I can write JCL to submit the job
                 This is what production expects
                 
  
  to use 3.B above, I need to create a new file in USS on the MF
  and write Unix Shell commands, I MUST make this shell script exectuable
  or it will not run (See JCLPlay3)
  
#!/bin/sh  

#
#  This is an example Unix Shell script to run a Java Application
#
#    Please note this script must be "executabe" or the JCL will fail
#    It can be made executable via RDz (right click this script in the 
#    Remote Systems view and select Permissions) or via OMVS with the Unix 
#    command: chmod u+x runExample.sh
#

export CLASSPATH=/u/user900/JCLPlay3.jar:/u/jearl/jars/*
export JAVA_HOME=/usr/lpp/java/J8.0_64
export PATH=/usr/lpp/java/J8.0_64/bin

commandLineArg1="/u/jearl/data/POP.csv"
commandLineArg2="//'USER900.TRAINING.RESULTS'"

fileForSTDOUT="JCLPlay3.out"
fileForSTDERR="JCLPlay3.err"

# Shell scripts allow long lines, so I can avoid the cutoff JCL imposes
#     > is the redirection for STDOUT (System.out.print)
#    2> is the redirection for STDERR (System.err.print, and stack traces)
java org.example.play.JCLPlay3 $commandLineArg1 $commandLineArg2 > $fileForSTDOUT 2> $fileForSTDERR