Contest ID in the instructions:
  All references to Z##### are examples.
  Substitute your assigned ID in all cases.

The challenge objective is familiarity with TSO, Time Sharing Option.

• TN3270 LOGON results in a session with TSO.
• TSO is a command line interface, CLI, without full screen support.
• Password is required on the TSO LOGON screen.
• The contest system is customized to automatically start ISPF, a panel driven interface with full screen support. Therefore, you do not see the TSO Ready prompt during LOGON process.
• The TSO logon screen was customized with LOGOFF in the Command field.
   LOGOFF in the Command field bypasses the TSO Ready prompt.

Observe
Command ===> logoff
in the TSO/E LOGON display.

The result is execution of TSO logoff upon termination of ISPF session.

Tab to logoff and use space bar to remove logoff, then enter to proceed to ISPF Primary Option Menu.

From ISPF Primary Option Menu, enter x to terminate the ISPF session.

The following display may or may not appear.

If the following screen appears, then enter 2 to Delete data set without printing.

The Log Data Set contains activity from session which is no longer needed.

1. Enter time command to verify READY prompt environment
2. Submit a JCL job entering submit 'zos.public.jcl(part2)'
3. Enter a in response to ENTER JOBNAME CHARACTER(S) -
     press enter a few times until MAXCC=0000 is displayed
4. Allocate your P2.OUTPUT partitioned data set member name #01 assigning a file name SYSUT2
5. Allocate ZOS.MTM2018.PUBLIC.PDS.DATA partitioned data set member name COUNTRY
     assigning a file name SYSUT1
6. Allocate DUMMY to system input
     assigning a file name SYSIN
7. Enter IEBGENER to execute the system generate utility
    where program IEBGENER reads from file name SYSUT1 and writes the content to file name SYSUT2
8. Enter logon z##### to re-logon to the TSO/ISPF environment
     where z##### must be substituted with your personal ID

The previous action to LOGON from the READY prompt restarted the TSO session.

After typing your password, tab to Command ===> input field and enter logoff in the command field of the TSO/E LOGON panel to save time exiting from the TSO/ISPF session in the future.

Familiarity with ISPF is needed to complete challenge #02.

ISPF is used frequently throughout the contest to complete challenges.

A short video is available to explain ISPF.

Click on the following URL, then select Lecture 7 video which is less than 8 minutes.
z/OS Introduction
 Note: If "Start Chat" appears, decline. Chat is for clients considering a purchase.

1. Enter your ID in the Dsname Level field on the ISPF Data Set List Utility (3.4) panel.
    All data set names that begin with your ID are displayed.
2. Enter print on the command line once the data set names beginning with your ID are displayed.
    Physical screen printed appears in the upper right corner.
3. Enter =x to terminate ISPF.
    Observe Specify Disposition of List Data Set panel appears.
    Observe List Data Set (Z#####.SPF#.LIST) Disposition:
    Take note of the SPF# where # will be an assigned number between 1 and 9
4. Enter 4 in the Process Option field.
    A data set name beginning with your ID and ending with SPF#.LIST was created and kept
    where # is a number from 1 to 9.
5. Logon to TSO ISPF environment.
6. Enter dslist 'z#####' - remember to substitute your ID for z#####.
    Command dslist 'z#####' is an alternative method to display the Data Set List Utility panel
    and all data sets beginning with 'z#####' appear.
7. Enter co in the command column to the left of data set name ending with SPF#.LIST
    Copy Entry Panel is displayed.
8. Type p2.output in the Name field just below To Other Data Set Name, then tab to NEW member name field and enter #02 .
    A message stating Data set attributes are inconsistent appears.
    Ignore the message and enter to perform copy action.

Familiarity with ISPF Editor is needed to complete challenge #03.

ISPF Editor is used frequently throughout the contest to complete challenges.

A short video is available to explain ISPF.

Click on the following URL, then select Lecture 8 video which is less than 8 minutes.
z/OS Introduction

Note: If "Start Chat" appears, decline.
Chat is for clients considering a purchase of additional IBM Z technology features.

While in ISPF Edit session, enter help or press function key 1, F1, to display online ISPF Editor tutorial help.

The contest instruction web site has an ISPF Editor Command Summary under the References drop down.
ISPF Editor Command Summary

1. Edit data set name ending with SPF#.LIST where # can be 1 to 9.
    Observe text of the screen print from previous challenge.
2. Enter primary command reset to suppress the ==MSG> lines at the top.
3. Enter primary command cols to display a column ruler.
4. Enter primary command right 29 to shift the text right by 29 columns -
     the line text begins with column 30 in the display.
5. Enter primary command left 29 placing column 1 back in the far left of the display.
6. Enter line command d10 over top of line 000001 - (overtype 00001 with d10).
    d10 deletes 10 lines.
7. Enter line command d99 over top of the line number where the text "******** End of Data Set list" appears.
    d99 deletes 99 lines which is more than all the remaining lines in the data set.
8. Type line command ((29 over top of line 000001, then
    tab to last line number and type (( over top of the last line number, then
    enter to execute the line commands where -
    ((29 to (( shifts the range of lines 29 columns to the left.
    The shift left line operation removed text in column 1 to 29 which was mostly spaces.

If the format is not correct, then enter ISPF primary command cancel and start over.

If the format is correct, type primary command replace p2.output(#03)
and c99 over top of line 000001, then enter to copy all lines to member #03 in data set p2.output .

NOTE: A truncation message appears. Truncation is ok. Enter to proceed.

Member #03 created message appears in the upper right area of the display.

The above created member #03 in data set name P2.OUTPUT
where #03 contains an edited screen print of data set names beginning with your ID.

F3 (function key 3) to save and exit from the ISPF editor session.

In challenge #04 you submitted JCL for execution and viewed the output.

In challenge #05 you will learn the basics of JCL.

Purpose of JCL:

• Tell the system what program to execute
• Tell the system about the program inputs and outputs

z/OS Application Program Execution

• A program reads, writes, and updates file names.
• A program has internally coded file names.
• A program is without any information about the physical data sources.

JCL Syntax

• // starting in column 1
• JCL is UPPERCASE
    Only exception is lowercase in quotes for unix file names, unix parameters, etc.
• The 2 most important JCL operations are:
    EXEC
     - used to tell system what program to execute
    DD
     - used to identify program inputs and outputs

What is a JCL ddname?

• A ddname is on a DD operation where DD is JCL syntax for Data Definition
• The program requests access to inputs and outputs using filenames
• A program filename needs a ddname where the filename = ddname
• DD parameters describe the input/output data source to be accessed by the program

What is a JCL step?

• Each EXEC operation starts a new step
• A step includes an EXEC operation followed by DD operations
• A stepname is coded immediately after // on the EXEC operation
• A subsequent EXEC operation is the end of the previous step and start of a new step

Description of a few DD parameters describing the data input/output resources

• DSN=value - where value is a data set name
• PATH=value - where value is a unix filename
• DISP=value - where value is data set name or unix filename disposition, such as NEW, OLD, SHR, CATLG
•   *   - an asterisk(*) where what follows the DD * is in-stream data or control statements the program would recognize

----------------------------------------------------------------------------------------------
The program determines JCL the ddname.
----------------------------------------------------------------------------------------------

If a program file name does not have an associated JCL ddname, then the program execution will fail reporting no ddname found for the program file name.

JCL DD Operation Summary

• Begins with //
• DDNAME immediately after // on the same line
    where DDNAME must match the program coded internal file name
• DD is after the DDNAME on the JCL line
• Parameters used to describe input/output physical resource is after DD on the JCL line
    More about DD parameters later

Below describes the screen shots requiring action by you to complete the challenge

1. Submit JCL to execute a system program utility, SORT.
2. Review JCL JOBNAME output to identify DDNAME spelling expected by SORT.
3. Edit, modify, and submit JCL to verify successful execution.
4. Edit, modify, and submit JCL to write data output based upon specfic sort criteria
     where SORT program writes output to P2.OUTPUT(#05).

Enter dslist command from ISPF as follows to display Data Sets Matching Z#####.JCL
  Reminder - substitute your ID for Z#####

In the command column enter 'e' to the left of the partitioned data set name Z#####.JCL as displayed below.

A partioned data set has member names.

Enter 's' to left of member name CH05JCL.

ISPF EDIT is now able to modify member name CH05JCL in the partitioned data set Z#####.JCL.

Enter ISPF commands as displayed below to remove ==MSG> lines and hilite JCL reserved words.

Take note of line 000005 with '//DDNAME DD' syntax.

Big Hint: EXEC PGM=SORT does not expect a file name with spelling of 'DDNAME' in the SORT program.

Line 000005 DD DSN=&SYSUID..P2.OUTPUT(#05),DISP=SHR are the correct parameters describing SORT program physical resource for the sorted output.

The objective is to determine the correct DDNAME spelling.

Enter commands as seen below to submit JCL to execute the SORT program, then jump to SDSF status display.

A message that JOB SORT05 submitted is displayed.

A unique JOB number is assigned. In the example, the unique number is JOB00691.

Your unique JOB number will be different.

A message that JOB SORT05 ended with MAXCC=0016 is displayed.

The commands =sd ; st previously entered will display the SDSF STATUS panel.

Enter ' ? ' to the left of JOBNAME SORT05 with the unique JOB number from above to display sections of the JOB output.

JESMSGLG, JESJCL, and JESYSMSG are DDNAMEs generated by the system.

Program SORT expected DDNAME SYSOUT and wrote execution information in SYSOUT.

Enter ' s ' to the left of DDNAME SYSOUT to select what program SORT wrote about the execution.

The messages that begin with ICE are messages written by program SORT.

The ICE message that ends with ' A ' indicates an action is required for a successful execution.

Program SORT was looking for a specific DDNAME and wrote NOT FOUND.
  The SORT required DDNAME is on the same message line.

The JCL needs modification based upon the SORT message.

Last, use dslist command to jump to Z#####.JCL partitioned data set name.

Edit Z#####.JCL

Select member name CH05JCL

Given the hints, correct the JCL to allow SORT program to write the sorted output to data set name Z#####.P2.OUTPUT member name #05

NOTE: System variable &SYSUID. in JCL is automatically substituted with your ID.

Correct JCL, submit, and view the new SORT05 JOBNAME output for success.

In challenge #05 you were introduced to JCL.

You learned about the relationship between a program file name and the DDNAME.

Bottom line
A program file name must be spelled the same as the DDNAME for the system to locate the physical inputs and outputs.

In challenge #06 you are introduced to JCL DD operation parameters which are used to
describe the program inputs and outputs.

Many JCL DD parameters exist which can appear confusing. However, learning the most common parameters is pretty easy.

Most common JCL DD parameters include:

• DSNAME=
   Data Set Name of the physical resource, typically DSN= abbreviation is coded
     z/OS has several Data Set Name types and DSN= handles all Data Set Name types
     More about the different Data Set Name types later in the contest
• DISP=
   DISPOSITION of the DSNAME physical resource
     DISP=SHR -- resource exists and program will share access with others
     DISP=NEW -- resource is created for program output
     DISP=OLD -- resource exists and program wants exclusive access
• PATH=
   Unix file name path of the physical resource
     Enclosed in quote marks - reason:
     Unix file names and file path are case sensitive where JCL is normally UPPERCASE
• PATHOPTS=
    Access file options and Status file options
     More about the PATHOPTS= Access and Status file options later
• *  (asterisk)
    What follows the asterisk ' * ' is data - NOT JCL
     The data in the JCL stream will be understood by the program
     The program is looking for the DDNAME to read followed by the data lines
     The data lines are read until the next JCL statement is found
• SYSOUT=*
    Write the data to the system JES spool data set
     The JES spool data set is what SDSF is viewing - which you have already done.

You will have several SORT05 JOBNAMEs with unique JOB numbers.

From SDSF status panel, entering ' p ' to the left of any SORT05 JOBNAME will purge unwanted output.

Challenge #06 uses the same JCL you used in challenge #05.

Enter dslist command from ISPF as follows to display Data Sets Matching Z#####.JCL
  Reminder - substitute your ID for Z#####

In the command column enter 'e' to the left of the partitioned data set name Z#####.JCL as displayed below.

A partioned data set has member names.

Enter 's' to left of member name CH05JCL.

ISPF EDIT is now able to modify member name CH05JCL in partitioned data set Z#####.JCL.

Enter ISPF commands as displayed below to remove ==MSG> lines and hilite JCL reserved words.

If you successfully completed challenge #05, then JCL has a modification on line 000005 .

Line 000007 is data read by SORT program.

Program SORT is looking for SYSIN DDNAME to provide sort control instructions.

The control statement instructs the program to sort the data from SORTIN starting
in column 1 for a length of 5 using character CH format and ascending A order.

Helpful Trick:
Enter bd over top of line number 000004 or 000005 to browse the data in the data set name member.

F3 will return you back to the ISPF edit session.

1. While browsing 'bd' SORTIN data, enter cols to view column numbers
     Locate column number of last name, then F3 to return to SORT05 edit session
2. Modify SORTOUT member name from #05 to #06
     IMPORTANT: If not done, then you will replace the valid challenge #05 answer
       Rerun of challenge #05 would be necessary to correct #05
3. Modify sort control statement using column number of last name
     Sort length, character format, and order can remain the same
   
4. Submit the JCL with the modified sort control statement and review the output

You practiced what you learned in the previous challenge,
"how to submit JCL and view the JCL JOBNAME output"

Some operating systems process data as a stream of bytes or characters where a "new line" of data requires a "carriage return" character or "line feed" character embedded in the stream of characters.

z/OS manages data differently.

z/OS data is processed with an assigned record length.

z/OS "new line" occurs as the result of the assigned record length resulting in significant implications on how datasets are created, how programs process data, and contributes to why z/OS memory management is superior to other operating systems.

Master the Mainframe contest objective is knowledge and experience with details of z/OS.

z/OS system technicians customize z/OS and DevOps environment to handle data set creation.

Application developers are typically unaware of details related to data set creation.
Application developers use documented procedures hiding the details required for data set creation.

DevOps tooling allows the application developers to maintain, test, and develop new business applications without the need to have any detailed knowledge about the operating system environment.

Common ways z/OS data sets are created include:

• Using JCL DD parameters
• Using ISPF panels
• Using TSO ALLOCATE command
• Using system utility programs
• Using system routines and automation

z/OS needs more than a data set name to create a data set such as:

• Record length
• Record format
   Fixed length records or Variable length records
   Blocksize - number of records in a block
• Data Set Organization
   Sequential - a collection of records
   Partitioned - a collection of members where the members contain records
   VSAM - Virtual Storage Access Method
     flexibility to organize records in four unique types
     designed for high speed and high volume access to data

Syntax involved in creating a data set includes:

• LRECL - logical record length
• RECFM - record format
• BLKSIZE - block size
• DSORG - data set organization
• SPACE - disk storage size limits
    primary extent value
     - all data sets have 1 primary extent
    secondary extent value
     - numerous secondary extents are automatically created after the primary extent
       is full
• UNIT and optionally VOL=SER=
    device type and disk volume label
• LIKE - uses attributes of a like data set name for creating new data set

Description of actions in the screen shots below to complete challenge:

1. Edit Z#####.JCL member name CH07JCL
2. Modify member name CH07JCL to create a data set name Z#####.CLIENTS with the following attributes:
     data set organization - physical sequential (PS)
     logical record length - 170
     record format - fixed block (FB)
     blocksize - 8500
     unit - SYSDA
     space in unit of tracks - TRK
     primary extent size - 1
     secondary extent size - 1
   
3. Submit JCL
4. View JCL JOBNAME for successful completion

Enter dslist jcl to list data set names the begin with your ID followed by JCL

Edit your JCL partitioned data set name

Select ' s ' member name CH07JCL

Observe the following in the JCL below

1. JCL JOB has 3 EXEC statements
• Each EXEC is called a JCL JOB step.
2. Line 000003 is JCL stepname STEP1
• Executes system utility IDCAMS to delete the data set name if the data set name exists
• JCL feature SYMBOLS=CNVTSYS enables to system to resolve variables in the data following DD *
• IDCAMS utility documentation describes DDNAMEs the program is expecting and purpose
3. Line 000009 is JCL stepname STEP2
• Executes system utility SORT to copy data into newly created data set name Z#####.CLIENTS
• Lines 000012 to 000014 results in a single DD operation as a result of the comma's at the end of each line
• Line 000012 DISP=(NEW,CATLG) instructs the system to create a new data set name
• Line 000013 and 000014 includes DD parameters describing the attributes of the new data sets name
• SORT utility documentation describes DDNAMEs the SORT program is expecting and purpose
4. Line 000020 is JCL stepname STEP3
• Executes system utility IKJEFT01 to list data set attributes of the newly created data set name
• IKJEFT01 utility documentation describes DDNAMEs the program is expecting and purpose
5. Line 00018 is a JCL condition saying execute next JCL step only if the previous step is completed successfully
6. Line 00025 terminates the JCL condition statement on line 00018.

Enter sub ; =sd ; st to submit the JCL and jump to SDSF status panel

System message about JOB CH07JCL SUBMITTED is displayed

System message about CH07JCL ENDED with a JCL ERROR is displayed

Result of previous =sd ; st is a jump to SDSF status panel

Select ' s ' CH07JCL print output

JOB NOT RUN - JCL ERROR is in the output

Page forward entering forward command or press F8.

JCL statement 8 is the DD operation which continues on the 2 lines that follow.

When JCL errors occur, STMT NO. MESSAGE information is always at the end of the output.

STMT NO. 8 is flagged as a problem statement.

Below is a shift to the right in the output showing DSORG SUBPARAMETER OF THE DCB on line 8

JCL DD parameter DCB=(...) is used to code data set attributes as shown

Enter dslist jcl to jump to the data set list panel

Edit the JCL partitioned data set again

Select memeber name CH07JCL

1. Edit Z#####.JCL member name CH07JCL
     The @ symbols need to be replaced with the following data set name attributes
2. Modify member name CH07JCL to create a data set name Z#####.CLIENTS with the following attributes:
     data set organization - physical sequential (PS)
     logical record length - 170
     record format - fixed block (FB)
     blocksize - 8500
     unit - SYSDA
     space in unit of tracks - TRK
     primary extent size - 1
     secondary extent size - 1
     primary extent - 1
   
3. Submit JCL
4. Jump to SDSF and view JCL JOBNAME output for successful completion

View JCL JOBNAME DDNAMEs for successful completion

If errors persist, then edit, modify, and submit Z#####.JCL member name CH07JCL until successful completion

If SYSTSPRT DDNAME has the newly created data set name attributes,
then use XDC to print SYSTSPRT DDNAME content

Write the SYSTSPRT output into Z#####.P2.OUTPUT data set name
as member name #07

Reminder - Replace Z##### with your ID

ISPF editor has capabilities to explore hexadecimal, EBCDIC, and ASCII

1. Edit Z#####.PDS.DATA member name MIX
     - Only lines 000001 and 000003 are readable
2. Enter ISPF edit primary command source ascii
     - Only lines 000002, 000004, 000005, and 000006 are readable
3. Enter ISPF edit primary command reset
     - Again, only lines 000001 and 000003 are readable
4. Enter ISPF edit line command cols on line 000001
5. Enter ISPF edit primary command hex on
     - Hexadecimal values for each character are visible directly below the character
     - Line 000001 - column 1 is an EBCDIC uppercase T
      - Below T on line 000001 is E and below E is 3
      - EBCDIC uppercase T is hexadecimal x'E3' where x means hexadecimal
6. Enter ISPF edit primary command source ascii
     Line 000002 - column 1 is an ASCII uppercase T
     Below T on line 000002 is 5 and below the 5 is a 4
     ASCII uppercase T is hexadecimal x'54' where x means hexadecimal

1. The word binary is misspelled on line 000004 and 000005.
   Correct the spelling.
     - Correction can be accomplished any 1 of 3 ways
     1) Overtype the hexadecimal value with correct value for the misspelled letter
     2) While in source ascii mode, overtype the incorrect letter with the correct letter
     3) Primary command change can correct each occurrence of the misspelled word
2. Decode "packed decimal" value on line 000007 located in columns 1-3
     What is "packed decimal"?
     1) See table at the bottom of Reference - Character Encoding Summary
     2) Internet research of "packed decimal" format
   
3. Enter the decoded "packed decimal" value in EBCDIC format in the line 000008 text area columns 1-5 and the sign character (+ or -) in column 6

• Overtype line 000001 with c8 to copy 8 lines
• Enter primary command replace p2.output(#08)

You will allocate 7 unique z/OS data set types

Edit and submit JCL JOB with the following modifications:

1. Modify DD operation DSORG parameter to allocate a sequential data set
2. Modify DD operation DSORG parameter to allocate a partitioned data set
3. Modify DD operation DSORG and DSNTYPE parameter to allocate a partitioned data set extended
4. Modify IDCAMS utility program DEFINE CLUSTER control statement to allocate a VSAM KSDS cluster
5. Modify IDCAMS utility program DEFINE CLUSTER control statement to allocate a VSAM ESDS cluster
6. Modify IDCAMS utility program DEFINE CLUSTER control statement to allocate a VSAM RRDS cluster
7. Modify IDCAMS utility program DEFINE CLUSTER control statement to allocate a VSAM LDS cluster

• z/OS disk storage space is allocated in 'extents'
    - An extent is a contiguous area on disk with an absolute starting and ending location
    - z/OS data sets have 1 primary extent
    - When the primary extent is full, then a secondary extent is automatically allocated
    - The number of secondary extents depends upon the type of data set
    - The size of a primary extent and subsequent secondary extents are determined by a SPACE attribute
  

  See References drop down Data Set Allocation and Disk Storage Summary

• z/OS stores data in a variety of organization types categorized as NON-VSAM and VSAM
  NON-VSAM includes
    1) Sequential
    2) PDS, Partitioned Data Set
    3) PDS/E, Partitioned Data Set/Extended
  VSAM includes
    1) KSDS, Key Sequences Data Set
    2) ESDS, Entry Sequenced Data Set
    3) RRDS, Relative Record Data Set
    4) LDS, Linear Data Set
• Unix file systems
    - Unix filesystem is a stream of bytes
    - Physical VSAM LDS formatted for Unix filesystem stream of byte processing
• Databases
    DB2 is a relational database
    DB2 data is stored in a VSAM LDS, formatted, and managed by DB2
    IMS Hierarchical DB uses special access method data sources which are excluded from the contest
• Data Set attribute syntax includes:
    LRECL, Record Length
    DSORG, Data Set Organization
      - PS Physical Sequential
      - PO Partitioned Organization
      - VS VSAM
    RECFM, Record Format
      - F Fixed Length Records
      - FB Fixed Length Blocked Records
      - V Variable Length Records
      - VB Variable Length Blocked Records
      - U Undefined Length Records
  

VSAM Tutorial
VSAM Tutorial - Defining a Cluster
DSORG
DSNTYPE

NOTE: All occurrences of &SYSUID. are automatically replaced by your ID when submitted.

Change all occurrences of the @ symbols with appropriate parameters to accomplish the following:

• &SYSUID..CH9.SEQ created as a sequential data set type
• &SYSUID..CH9.PDS created as a partitioned data set type
• &SYSUID..CH9.PDSE created as a partitioned data set extended type
• &SYSUID..CH9.KSDS created as a VSAM Key Sequenced Data Set type
• &SYSUID..CH9.ESDS created as a VSAM Entry Sequenced Data Set type
• &SYSUID..CH9.RRDS created as a VSAM Relative Record Data Set type
• &SYSUID..CH9.LDS created as a VSAM Linear Data Set type

Submit JCL member name CH09JCL and view the output for successful execution.

If unsuccessful, then correct and submit again.

View CH09JCL output DDNAMEs

Use XDC to print content of DDNAME SYSTSPRT StepName RESULT to P2.OUTPUT member name #09 as follows:

Edit, modify, and submit JCL JOB executing system utility program IDCAMS to copy the same input data
into 6 unique data source types:

• Sequential
• PDS
• PDS/E
• VSAM/KSDS
• VSAM/ESDS
• VSAM/RRDS

The input data source is data you modified in a previous challenge, Z#####.PDS.DATA member name MIX.

It is not a matter of how to copy data, it is a matter what facility you want to use to copy data.

• ISPF panels are available to interactively copy data.
• ISPF DSLIST column command is available to interactively copy data.
• Unix services command ' cp ' is available to interactively copy data.
• Many z/OS utility programs are available to copy data.
    z/OS utility programs can be executed interactively or using JCL.
    Part 1 challenge used a z/OS utility program to copy data interactively from TSO Ready prompt.
• Writing a program in any language to copy data from a file name to a target file name,
  then execute program using JCL where DD statements are used to identify the from and to data sources.

VSAM Tutorial
IDCAMS command

NOTE: All occurrences of &SYSUID. are automatically replaced by your ID when submitted.

Modify JCL as follows:

• Change @@@@@ on line 000013 to an IDCAMS control statement command used to reproduce data
• Enter ISPF edit line command, ' r5 ', to replicate line 000013 5 times creating a total of 6 lines with the IDCAMS control statement command used to reproduce data
• Change each occurrence of OUTFILE(@@@@) to the respective JCL DDNAME found on lines 6 to 11

Submit JCL member name CH10JCL and view the output for successful execution.

If unsuccessful, then
  1) tso submit jcl(ch09jcl) to recreate empty data set names
  2) Correct JCL, submit, and view output

View CH10JCL output DDNAMEs

Use XDC to print content of DDNAME SYSTSPRT StepName RESULT to P2.OUTPUT member name #10 as follows:

JCL is rarely written from scratch.

JCL is commonly copied, then modified to accomplish a task.

In this challenge an ISPF edit session is used to copy in JCL from a different member name,
then modified to accomplish a task as instructed.

Common ways z/OS data sets are deleted include:

• Using JCL DD parameter DISP=(OLD,DELETE) for NON-VSAM
• Using ISPF panels
• Using TSO delete command
• Using system utility programs such as IDCAMS

1. Edit Z#####.JCL
2. On the command line enter s ch11jcl to select and create a new member name, CH11JCL
     CH11JCL is empty
3. Enter ISPF editor primary command copy ch09jcl
     CH11JCL member name now includes a copy of CH09JCL
4. Modify JCL to delete data sets
   
   • Change JCL jobname from CH09JCL to CH11JCL
   • Delete JCL and control statements involved with creating the data sets
   • What should remain is 2 JCL step names, DELETE and RESULT
       Note: Modified JCL will keep the comment lines and the IF/ENDIF lines
5. Submit modified JCL to delete the 7 data sets
     Max-RC code of 0004 is expected and normal
6. Check CH11JCL output, specifically StepName RESULT and DDNAME SYSTSPRT, for successful deletion of 7 data sets
   
   • 3 ' NOT IN CATALOG ' messages for the NON-VSAM data sets
   • 4 ' LOCATE ERROR ' messages for the VSAM data sets

If SYSTSPRT DDNAME output proves the data sets were deleted,
then use XDC to print SYSTSPRT DDNAME content to P2.OUTPUT member name #11

Many techniques are available to copy data between z/OS data sets and Unix file names.

The challenge uses JCL to execute Unix shell commands and execute a standard z/OS system utility to copy data from a partitioned data set member name to a Unix file name.

Common ways to copy data between Unix file names and z/OS data sets:

• Using JCL to execute standard utilities
• Using Unix shell cp command
• Using TSO ocopy, oput, oget, oputx, and ogetx commands
• Using ISPF panels
• Using ISPF editor

1. Edit Z#####.JCL member name CH12JCL
   Modify JCL to copy data to a Unix file name, then execute Unix word count command,
   ' wc ' proving data was successfully copied
   
   • Change line 000013 where SYSUT2 is output of the data copy
   • Change line 000017 where STDOUT is output of the word count command
     proving data was successfully copied into Unix file name
2. Submit modified JCL to copy data and verify successful copy
3. Check output for successful copy

NOTE: The first time running CH12JCL, the DELETE step finish with a return code of 256 as a result of attempting to remove filename mix when mix filename does not exist. Return code 256 is the expected return code. All is ok.

z/OS is both flexible and open as a result of a tightly integrated Unix Systems Services component in the z/OS Base Control Program.

The challenge involves using JCL to execute Unix shell commands, reviewing the output, and then editing a Unix file created by a Unix shell command processing.

Description of JCL JOB CH13JCL

• PGM=BPXBATCH provides a Unix environment for shell command processing or program execution
• STDPARM is the DDNAME BPXBATCH uses to read input
• sh is the first control statement requesting BPXBATCH to start a Unix shell
    Alternatively, pgm can be coded to execute a Unix program instead of a Unix shell commands
• The semicolon ' ; ' at the end of each line means the next line is new input to sh Unix shell
• Line 17 executes Unix calendar cal command and writes ' > ' output to Unix file name sept1752
    Unix cal command writes calendar information
• Line 23 executes Unix ls -al command and writes output to Unix standard output STDOUT DDNAME
    Unix ls -al command writes a list of file names
• Line 29 executes Unix uname -a command and writes output to Unix standard output STDOUT DDNAME
    Unix uname -a command writes the Unix name
• Line 35 executes Unix manual page man command
    Unix man command writes information from the Unix manual pages
    -- Unix manual page information about copy cp command is written to STDOUT
    -- The written output is passed as input to a pipe which the vertical bar ' | '
    -- Output of the pipe is input to Unix grep command
    -- grep // will output only lines containing ' // '
    -- // syntax can be used in Unix System Services cp command to reference data set names
    -- The resulting lines from man cp show syntax examples of copying data between Unix file names
      and data set names

1. View or Edit JCL(CH13JCL)
     Observe output Unix calendar cal command will be written to a Unix file name
2. Submit JCL
3. Review CH13JCL output for successful completion
4. Enter tso omvs on any ISPF command line
     You are now in Unix System Services Shell prompt in your home directory
5. Enter oedit sept1752 from the Unix shell prompt
     Observe 11 days are missing
6. On line 8 starting in column 1, enter the year in which the "Gregorian" calendar was first introduced
     The year can found in Explanation for the 11 missing days
7. Type ISPF editor primary command replace p2.output(#13) and c99 on line 000001, then enter to copy all lines to member #13 in data set p2.output.   Result should be output written to P2.OUTPUT(#13)
     ISPF line command c99 copies 99 lines which copies all the lines because number of lines is less than 99

NOTE: Ignore message "Data set attributes are inconsistent. Truncation may result.."
Enter to proceed past message

F3 to exit oedit session

exit to terminate unix shell session

enter to return to ISPF session

The challenge demonstrates how to select rows and columns from a DB2 table,
then you will be instructed to select rows and columns from a different DB2 table.

1. All previous statements in Z#####.PDS.DATA(SQL) need to be comment statements
2. Same as previous interactive SQL executions, write the output to sql.out
3. Insert a forth statement to return the following:
   
   • select all rows and all columns from table emp owned by ibmuser

1. Edit Z#####.SQL.OUT
2. Enter the following ISPF editor commands:
   
   • Type primary command rep p2.output(#14)
   • Overtype line 000001 with with line command c99, then enter

A correct number is required to complete the challenge.

The correct number is the sum of 8 numbers from 4 separate data sources.
The 4 data sources include:

1. Sequential Data Set Name
2. Partitioned Data Set Member Name
3. Unix File Name
4. DB2 Table

Each number may be in 1 of 3 formats:

1. EBCDIC
2. ASCII
3. Packed Decimal

Each non-EBCDIC number must be converted to an EBCDIC numeric value where the sum of the EBCDIC numeric values is the single number required to complete the challenge.

You will be given the name of the data sources, specific record numbers, beginning and ending column numbers within the specific record to find the number. You will NOT be given the data format such as EBCDIC, ASCII, or Packed Decimal. You will need to view the hexadecimal representation to determine when value is either ASCII or Packed Decimal.

You are prepared to complete the challenge based upon what you learned in previous Part 2 challenges.

What you learned in previous Part 2 challenge:

• Edit, View, or Browse sequential data set names
• Edit, View, or Browse partitioned data set member names
• Edit, View, or Browse unix file names
    Use Data Set List Utility panel (3.4), then enter /z/z##### ....substituting your ID for z#####
    Enter 'e', 'v', or 'b' to the left of any file to edit, view, or browse the data
• Use ISPF primary and line commands to
    - display column ruler
    - display hexadecimal values
    - move forward, backward, right, and left in data set
• Interpret a packed decimal format
    - packed decimal number can be positive or negative
    - a negative packed decimal number requires a subtraction operation when summing the numbers
• Use DB2 for z/OS SQL interactively to 'select' data from a DB2 table

tso submit 'zos.public.jcl(p2final)'

Sum the 8 numbers found in the specified record and column positions from the following data sources:

• Data Set Name Z#####.HUNT1
    #1 Record 14 Column 35 to 38
    #2 Record 18 Column 78 to 80
• Data Set Name Z#####.HUNT2 Member Name FRED
    #3 Record 7 Column 1 to 3
    #4 Record 9 Column 47 to 49
• Unix File Name /z/z#####/dennis
    #5 Record 6 Column 42 to 45
    #6 Record 11 Column 31 to 33
• DB2 Table IBMUSER.EMP
    #7 Column PHONENO where lastname is YAMAMOTO
    #8 Column BONUS where lastname is YAMAMOTO

Take the following steps to record your answer for scoring:

1. Edit Z#####.JCL member name P2DONE
2. Modify 0000 value located on the last line to the sum of the 8 numbers
3. Submit JCL with the modified value