z13 and z14 system hardware, I/O and storage technologies, memory and task management, virtualization and cloud computing, hands-on SDSF system information, JCL, Putty and USS

In Windows, one can review the Window's System Properties under the Control Panel to determine processor and other information. For example, my laptop provides the following system information concerning the processor type, processor speed and the amount of installed RAM.

Summer 2018

One can use the Windows command WMIC to display the processor serial number used to uniquely identity your processor and is used for auditing and licensing purposes.

The processor serial number and type of computer is often used to automatically name your computer in Windows.

Windows Management Instrumentation (WMI) is the infrastructure for management data and operations on Windows-based operating systems. WMIC extends WMI for operation from several command-line interfaces and through batch scripts. For more information concerning the WMIC command interface consult the following links

The Linux commands lscpu, /proc/cpuinfo and lstopo (hwloc) can report detailed information about the cpu cores/processing units.

For example, the most frequently used Linux command to display system information about the processor is cat /proc/cpuinfo . The Linux cat command displays the content of a file. The Linux /proc subdirectory is a virtual directory, which contains information about the system hardware and functionality. The Linux /proc subdirectory does not really exist. During the Linux boot process this virtual directory is created. The system information stored in RAM contains many of the same information that you can find in the Windows Device Manager. The following is a partial example of the information of display by cat /proc/cpuinfo

Virtual files such as / proc/interrupts, /proc/meminfo, /proc/mounts, and /proc/partitions provide an up-to-the-moment glimpse of the system's hardware. Others, like the /proc/filesystems file and the /proc/sys/ directory provide system configuration information and interfaces.

Summer 2018

1. Use the Snipping Tool to document the CPU information below =

2. From the CPU information listed above, what is the serial number of z/OS CPU that you are using? Your answer is

3. From the CPU information listed above, what is the model number of your z System mainframe? Your answer is

In a previous discussion on virtual memory and memory pages, you had learned that when the real memory (frames) is full, excess pages of a program or subsystem are temporarily stored as auxiliary storage or as a slot. The role of the virtual memory is to serve as table that determines the current location of the page, i.e., in real memory or on disk. The maximum amount of virtual memory available is dependent on the amount of disk storage dedicated to slots.

In the real world it is important to determine the amount of auxiliary storage allocated to support slots.

The name of the paging file in Windows is a hidden file named PAGEFILE.SYS . One can 1) determine amount of storage space that slots are currently using PAGEFILE.SYS, or 2) change the amount of disk space allocated to PAGEFILE.SYS, or 3) change the location of PAGEFILE.SYS. Since the demonstration Window's computer has only one disk, the Drive C: is greyed out. Other options are prevented by Windows security settings. [Having too little space allocated to the paging file will cause Windows to be unable to execute more programs even though you have enough disk space.]

The Linux swapon command will display the location and amount of page file space used to store slots

The Linux free command will display the both the real (mem) and swap space. If a large percentage of the swap space is used, then one of two actions may be warranted: you may want to either add an additional swap disk to increase the available swap space, or you may want to add additional physical memory to the system.

4A In reference to virtual memory operating systems, what is a Frame? Your answer is

4B. In reference to virtual memory operating systems, what is a Page? Your answer is

4C. In reference to virtual memory operating systems, what is a Slot? Your answer is

5. How does one display Windows Page file information? Your answer is

6. How does one display Linux Memory and page file information? Your answer is

To display the data set names that space that z/OS is currently using slots for slots are displayed. Navigate to SDSF by typing the =SD command and press right-ctrl to execute. On the SDSF command line type /D ASM and press right-ctrl to execute.

7. Use the Snipping Tool to document your page data set names and utilization information below =

Windows permits one to increase the size of PAGEFILE.SYS. This approach may lead to disk fragmentation and slow disk performance to page files. Linux creates a storage volume or partition, and hence is more difficult to change, but does avoid this disk fragmentation problem.

On the other hand z/OS permits the system programmer to allocate a paging data set on any volume of any size. Allocation is designed to use contiguous tracks and cylinders and therefore avoid disk fragmentation. Once a new page data set has been allocated it simply be activated (added) by the system program command /pa page=xx.yy.zz , where the name of the new page data set is xx.yy.zz

Basic SDSF Commands - http://mainframewizard.com/content/basic-sdsf-commands

The SDSF OWNER will filter list of JCL the z System Userid who submitted the JCL Job. For example, if you type OWNER RMUI001 on the SDSF Command Input prompt, SDSF will only display JCL Jobs which were submitted by UserID RMUI001.

The SDSF PREFIX is the Job Name of the JCL JOB statement. Normally the PREFIX Filter would be PREFIX * As a result the following would be displayed.

The filter OWNER RMUI001 and PREFIX * would instruct SDSF to display any job name that was submitted by userid RMUI001.

The SDSF DA command will display all active users. Before we execute that command we will need to set up SDSF Filters

Step 1. On the SDSF command line type OWNER * and press right-ctrl to execute. The asterisk will display any job submitted by any owners, or userids.

Step 2 On the SDSF command line type PREFIX RMU* and press right-ctrl to execute. This is change the filter to display all owners that start with a userid of RMU

After Steps 1 and 2 your filter line should appear as

Step 3 On the SDSF command line type DA and press right-ctrl to execute. The SDSF DA command will display all active users. You should see your userid highlighted in black.

8A. Use the Snipping Tool to document the list of active users on the system at the time when you executed the DA command below =

8A.When using SDSF what is purpose of the PREFIX command and filter? Your answer is

8B.When using SDSF what is purpose of the OWNER command and filter? Your answer is

8C.List the SDSF OWNER and PREFIX commands that will display all JCL JOBs for userid BOB's submitted that includes a Job Name that starts ASSGN1. Your answer is

8D.List the SDSF OWNER and PREFIX commands that will display all JCL JOBs for any userid that includes 711 in the Job Name. Your answer is

Error messages appear in the upper right hand corner of the panel. In this case

You should see displayed information similar to the following. The SDSF DA command displays Active Users. When this example was captured using the prefix RMU*, only two TSO RMU* users were active

When you logon to any multiuser operating system, the operating system must start a program that allocates address space, and then runs a user interface within that address space. TSO will then interact with the user.

If 30 users are active, then 30 copies of TSO sessions (address spaces) are allocated. Multiple user interfaces are not as important in your Windows or MAC OS computer, since there is only one current active user.

Similar to z/OS Linux is a multiuser operating system and does permit multiple users. Every time you logon to Linux, either by using a command line interface or menu user interface like TSO/ISPF, or a graphical user interface, a multiuser operating system must allocate space for each individual logon user.

Do not confuse multiple user operating systems with multitasking. Each logon user who logons to a multiuser operating system, must allocate separate address space, and then each user can executed multitasks. The iPhone iOS is single-user and single tasking. Android is single-user, but may perfrom multitasking. But, z/OS, UNIX and Linux are multiuser and multitasking. The previous SDSF DA command provides evidence that are two current RMU* users which are identified by a JOBID of TSU06784 and TSU06785.

In z/OS, every "executing or executed" program is called a JOB. A JOB contains JCL commands which are used to start a program. When you logon to ANY operating system, the operating system must execute a logon program.

The first line of a JCL program MUST be the JOB card, e.g., //RMUI001 JOB 1,CLASS=TSU. When you logon, e.g., LOGON RMUI001, to the z/OS session, it executes a logon JOB. To review the syntax JCL (that was discussed in this assignment), columns 3 to 10 may contain a job name.

While one can submit jobs with the same, z/OS and JES must uniquely identify each job and a unique JobID or Job Number. Notice the values displayed under the JobID column, e.g., TSU06784 and TSU06785. TSO sessions use a JobID that are a combination of the TSO Job class and a unique number, e.g., Class TSU + Job Number 06784. Therefore, the SDSF command DA looks for TSU jobs, or Jobs that have been started and are active. UNIX and Linux functions in a similar way, except they will use the terminology of a "process id".

8E. Assume that SDSF displays a JobID of TSU06784. What does TSU mean? Your answer is

Notice the security implications of logon sessions. Since I know the list of active logon users who have been authenticated and have assigned privileges and permissions, can a hacker hijack the multiuser session? This type of security attack is called "Session Hijacking". Yes, it is possible. This course does not address this security topic. However, one can see if one understands the multiuser process they can better appreciate a potential security vulnerability and the necessary requirements to protect this this type of threat. By taking over another user's session one may enjoy evaluated permissions of the vulnerable user or session.

At the end of our TSO Logon process, a CLIST program named VENDOR.CLIST was executed to start the ISPF menus. CLIST (Command List) (pronounced "C-List") is a procedural programming language for TSO in MVS systems. It is similar to the Windows Batch file. Unlike batch files, CLIST also supports conditional and looping (iteration) statements. CLIST can be used to provide TSO dialog screens, e.g., your password screen, or ISPF Menus.

The previous SDSF DA (Active Users) command provides different information than the SDSF STATUS or ST commands. When the SDSF ST command was executed, the following was displayed. Comparing the following displayed results Job STATUS report will confirm that the displayed information is similar but different than the SFS DA command.

Earlier we had altered the SDSF filters by typing OWNER and right-ctrl to execute, and the PREFIX RMU* and right-ctrl key. The function of SDSF STATUS command is to display status of all jobs that are currently executing or have finished execution. The previous report only displays Job ID that begin with TSU, or TSO sections. In this discussion, batch COBOL program job submissions were ignored.

A review indicates that two jobs had a job status EXECUTION. The EXECUTION JOB Status indicates that that the job was still running, and in this case the TSO session was active . Therefore, the SDSF command DA looks for TSU-prefixed jobs that are executing.

Normally, when a JOB has a status of PRINT, the job submission has been completed. JES printing is the last phase of JOB executing. Sometimes, a JOB may display EXECUTION, when it is actually finished. Unlike Window operating systems the status displays are not automatically updated without user intervention. As a result, you can update the SDSF Job Status display by pressing right-ctrl.

Notice users (owners) RMU0119 and RMU0174 and their TSU Job status is PRINT, or not active. TSU jobs will automatically erase the JES TSU job status when the user properly logoffs. Users (owners) RMU0119 and RMU0174 were so busy to get to "happy hour" they did not logoff properly.

Normally, when a student's COBOL program is compiled, linked and executed the job lasts for less than a second. Therefore, a student's COBOL program job submission rarely is in the EXECUTION status for longer than a few seconds. This situation occurs when a student codes and executes any program that results in an infinite loop .

Students also code and execute VB.NET, Java and other program languages that create an infinite loop on Windows and Linux operating systems. But, these beginning programs are not COBOL batch programs without a user interface. In Windows or Linux, one can press the CTRL-C or CTRL-Break keys. Using SDSF one may purge a job that has a program that is stuck in an infinite loop.

Under the NP column, type P (to purge) and press right-ctrl to execute a job if it is executing in an infinite loop. For security reasons either the Owner of a Job or an instructor can purge a Job.

8F. A JCL Job list a Job Status of PRINT. What does the PRINT Job Status mean? Your answer is

8G. A JCL Job list a Job Status of EXECUTION. What does the EXECUTION Job Status mean? Your answer is

8H. List two examples of JCL Jobs that have a Job Status of EXECUTION. Your answer is

8I. When a Window's Program is executing in an infinite loop (will not stop) one can try to make the executing program stop by using either the Task Manager or press a CTRL-Break Keys. How does on stop a z/OS JCL Job executing in an infinite loop? Your answer is

Let's review the Jobs for all Owner Prefixes that start with RMU*.

Review the column labeled Prty (priority) column. An operating system uses priority values to determine which job or program should be allocated the most processing time. Any job or process which has a higher priority compare to others should have better throughput or response time.

A special operating system program called a z/OS Dispatcher is responsible for using the priority value to determine the amount of processor time to be allocated to the job or process. The dispatcher priority values for JobID TSU06784 and TSU06785 have is 15, while the other jobs have a dispatcher priority of 1. This makes sense. Since TSO jobs will require better response time to process user-entered keystrokes than batch jobs with no user interface. It makes sense to make the users happy by assign a higher Job priority.

How is the dispatcher priority set? Each job is assigned a JOB class. Each JOB class is assigned an initial priority value, which may be changed either manually by the system programmer, or automatically by the WorkLoad manager (WLM). In the case of the TSU job class, the default initial priority is set at value 15. This makes sense since TSO requires better response time than batch jobs since it must interact with users.

Every operating system has a system that assigns dispatcher priorities to manage throughput and response time for various applications or processes. In a desktop version of Windows, one can review the Base Priority values using the Task Manger and set the column display to show the Base Priority column. The displayed priority values are not numeric. Notice that most Windows Desktop processes are set to a Normal Priority, except the dwm.exe, Windows Desktop Manger is set to a High Priority. This also makes sense since the Windows desktop must interact with users like TSO.

The Linux Priority value represents the initial priority. The Linux nice value is added or subtracted from the initial priority. The combination of priority and nice value of a process in Linux makes it dynamic: In addition, the longer a process runs, the lower its priority will be. The priority is taken into account when there are more processes running than CPU cores available: Highest priority wins. But, when a process loses its priority over time, other processes will take over the CPU priority at some point.

The Linux nice and renice commands may be used toadd/remove some "points" from priority. A process which has a higher nice value will get lesser CPU time. Root can also set a negative nice value - the process gets more CPU time. In modern desktops there is plenty CPU time available - they are fast these days. The bottom line is Windows and Linux servers has the same problem as z/OS.

In Linux you may display processes and priority information with the ps command

The -l (lowercase L) flag of the ps command displays the nice values and current priority values of the specified processes. The command is ps -lu user1 is executed below. For example, you can display the priorities of all of the processes owned by a given user with the following:

The Linux CMD column displays the name of the program that is being executed. Ksh is the name of the Linux command line user interface like TSO. Just as we display to separate processes for the two Ksh users session, this is very similar to JobIDs TSU06784 and TSU06785. All modern operating systems were based on IBM mainframe operating systems, and therefore, they often perform the same requirements using different names and procedures.

Now it is time for you to do some work. In the SDSF STATUS panel 1) Type PREFIX * on the SDSF command line and press right-ctrl to execute. This filter change will display all userIDs. 2) Type OWNER * on the SDSF command line and press right-ctrl to execute. This filter change will display all useriIDs. There will be hundreds of JOB status records displayed.

9. What is the function of a Job or Process Priority? Your answer is

10. Use the Snipping Tool to document the a sample of job statuses below =

The SDSF Status Filter Line will limit the jobs to be displayed by JOB name. The JOB Name appears in the JCL JOB statement which is the first line of JCL. In the following example the JOBNAME is JPL.

The PREFIX filter will limit number of Jobnames displayed. A job name is with the JCL JOB statement. You may change the SDSF filter PREFIX, by entering PREFIX on the COMMAND INPUT Line. DO NOT USE THE EQUAL SIGN to separate the keyword PREFIX from the operand.

PREFIX=* means to display all JOBNAMEs.

PREFIX=JPL will ONLY display Jobnames of JPL.

PREFIX=JPL* will display ANY Jobname beginning with JPL and ends with any number of characters.

Similar to Windows and Linux the asterisk (*) is a wildcard character used to represent ANY zero or many characters, including the period.

Similar to Windows and Linux the question mark (?) is a wildcard character used to represent single character. Therefore, JPL???, which ends with three question marks wildcards, requires exactly three characters, not zero characters , not any one character , or not and two characters, rather exactly three characters.

Since z/OS wildcard characters were introduced in 1955 in TSO, one may assume that IBM introduced the concept of wildcard characters decades before MS-DOS, Windows, UNIX or Linux.

The OWNER filter will limit the number of Owner submissions displayed. The Job OWNER is the userid who submitted the job. The JCL code is not required to list the owner of the job, but JES and z/OS does keep track of the owner who was responsible for the job. You may change the SDSF filter OWNER by entering OWNER on the COMMAND INPUT Line. DO NOT USE THE EQUAL SIGN to separate the keyword OWNER from the operand.

OWNER=* means to display all jobs submitted by any owner.

OWNER=RMUI001 means to display all jobs submitted ONLY by owner RMUI001

OWNER=RMU* means to display all jobs submitted by ANY owner jobs whose owner begins with RMU and ends with any number of characters.

10.1 When viewing job submissions in SDSF, what is the purpose of a PREFIX filter? Answer = >

10.2 When viewing job submissions in SDSF, what is the purpose of an OWNER filter? Answer = >

10.3 Given the following SDSF Job Status Filter

When viewing job submissions in SDSF, which JOB will be displayed? (Hint: Think of AND) Answer = >

When our z/OS system goes down for maintenance and then rebooted, the DB2 database manager is not automatically started. One method to determine if the DB2 is running is to use the Find command in SDSF. All DB2 jobs (processes) begin with DBAG, which means DB - DB2, version A (The letter A represents the number 11 in hexadecimal, and G - general z/OS DB2. Type F DBAG and press right ctrl to execute. The Find command only finds the first occurrence of DBAG (which will work in our example if you have OWNER=* and PREFIX=*).

or you can change the Prefix to DBAG*. Ensure the owner filter is set to *.

11. Use the Snipping Tool to document the list of job statuses that starts with the string of DBAG below =

If you do not see a DBAG JOB names displayed, then 1) ensure that your PREFIX filter is properly set, or 2) ensure that your OWNER filter is properly set. If your SDSF filters are properly set contact your instructor. Perhaps DBAG, or DB2, is not running.

11.1 List the job names of DBAG of DB2 jobs that are currently executing? Answer = >

11.2 List the owner of the DBAG, or DB2 jobs? Answer = >

11.3 A student cannot see any of DBAG, or DB2 jobs listed. The student's SDSF Filter appears as the follows:

What is the problem of the previous SDSF Job filter? Answer = >

11.4 A student does see the DBAG, or DB2 jobs listed. After completing this assignment the student can no longer see their SDSF jobs after submit their JCL jobs/ SDSF Filter appears as the follows:

What is the problem of the previous SDSF Job filter? Answer = >

12. What is the dispatcher priority value for DBAG? Answer = >

13. In your informed opinion (read the previous discussion one more time), do you believe the dispatcher priority value for DBAG is appropriate? Please explain in detail. Yes of No is not an answer. Answer = >

Notice the JOBID of DBAG, it is prefixed with the STC job number (class), rather the TSU job number(class) used by TSO sessions. A job class is a named collection of job processing parameters, such as dispatcher priority, default initiator, and other parameters execution.

z/OS provides 38 predefined JOB Classes. The MOST popular z System job classes are TSU and STC job classes. The TSU Job class was introduced earlier since this is the default job class used to start time sharing sessions when users logon. The STC (Start Task Control) is the default Job class that is most often used to start z subsystems such as DB2, CICS, WebSphere, RACF, and many others. If the system programmer does not believe that the z/OS predefined job classes are appropriate for their z System installation that may customize their own job class parameters.

ALL operating systems use predefined parameters similar to a JOB class to start a program. Windows hides the details of these start up parameters from the user. In this course, it is important to be aware that Job classes and Start Up parameters exist and will be important to performance of your System z, Windows or Linux server.

When our z/OS system goes down for maintenance and then rebooted, the CICS subsystem will not be automatically started. One method to determine if the CICS is running is use the Find command in SDSF.

However the Find command works by searching from the cursor position downwards. Since we had previously typed and executed F DBAG, we need to move the cursor to the TOP of the job status list. Type TOP and press right ctrl to execute.

Now type F CICS and press right-ctrl to execute. The Find command only finds the first occurrence of CICS (which will work in our example).

Or you can the Prefix to CICS*.

You will see jobs display as CICSTS42, which means CICS Transaction Server Version 4.2. The current CICS version is 5.5 and version 6.0 is being tested by z System customer as of 2017

15. Use the Snipping Tool to document the list of all job statuses that starts with the string of CICS below =

If you do not see any CICS JOB names displayed, then 1) ensure that your PREFIX filter is properly set, or 2) ensure that your OWNER filter is properly set. If your SDSF filters are properly set contact your instructor. Perhaps CICS is not running.

16. Why does the job status value for CICS is listed as EXECUTION? Answer = >

17. What is the dispatcher priority value for CICSTS42? Answer = >

18. After reviewing the previous discussion one more time, do you believe the dispatcher priority value for CICSTS42 s appropriate? Please explain in detail. Yes of No is not an answer. Answer = >

Using the F command in ISPF or SDSF is very useful, but you must remember the rules of the FIND command. 1) It only searches downwards. Use the TOP command between multiple searches. 2) It only finds the first occurrence of the string to be searches. Press the F5 to repeat the Find command.

Now type PREFIX DBAG* and press right ctrl to execute. (Do not forget the wildcard character the trailing asterisk. Who invented operating system wildcard characters? I forgot.)

The Find command only finds the first occurrence of DBAG. The PREFIX filter display all Jobs that have a prefix of DBAG

19. Use the Snipping Tool document the list of all job statuses with the prefix of DBAG below =

The command will ask you to display all jobs who are owned, or started by a user ID. Either use OWNER information from the SDSF status (other than your own), or select any other USERID that your own from the userid list displayed in the Blackboard Assignment folder. Your instructor may also decide to provide a specific owner to be displayed.

Now type OWNER XXXXXXX where XXXXX is another userid and press right ctrl to execute. Do not used you userid.

20. Use the Snipping Tool document the list of all job statuses of some other owner or userid other than your userid below =

Step 1. Type /$DA,X and press right-ctrl to execute. This command will display all executing programs, similar to the Windows Task Manager and the Linux ps command.

Step 2. SDSF has limited capabilities to display detailed system information with many records. Type ULOG and press right-ctrl to execute.

Unlike SDSF, ULOG will permit you to use the function keys to move to the next page or to the bottom (F8), move to the previous page (F7),shift to the right (F11), or shift to the left (F10).

21. Use the Snipping Tool to document all executing programs below =

Step 3. Use the Find command to find your TSO section. Type F XXXXXXX where XXXXXX is your useID. If necessary press F5 to repeat the find until you see your TSO session with the job class of TSU

22. Use the Snipping Tool to document your TSO session below =

Important distinction! The SDSF command DA command displays all active users. The /$DA,X displays all active system jobs.

ULOG - Display all Active Jobs

Step 1. Type /$DA,X and press right- ctrl to execute.

Step 2. SDSF has limited capabilities to display detailed system information with many records. If the number of active users is too long type ULOG and press right ctrl to execute.

Unlike SDSF, ULOG will permit you use the function to move to the next page or to the bottom (F8), move to the previous page or top (F7), shift to the right (F11), or shift to the left (F10).

23. Use the Snipping Tool to document the active users below =

Type OFF and press right- ctrl to execute.

I am confused?

It seems that some commands begin with a forward slash (/), other commands may begin with a forward slash and dollar sign (/$) and some commands have no command prefix, or does not begin with anything. The difference between command prefixes is which z/OS subsystem is responsible to execute the command. Consider the flowing table

1. A user is executing the WMIC and SYSINFO commands. What type of system information is provided by these commands? Which operating system support the WMIC and SYSINFO commands? Answer:

2. A user is executing the lscpu or cat /proc/cpuinfo commands. Which operating system will use this command? Answer:

3. Which SFSF command is used to display z System CPU information? Answer:

Chapter 4: TSO/E, ISPF, and UNIX: Interactive facilities of TSO: Introduction to the Mainframe: z/OS basics

· Acronym for Interactive System Productivity Facility

· ISPF is a menu-driven interface for user interaction with z/OS system. The ISPF environment is executed from native TSO.

· ISPF provides utilities, an editor and ISPF applications to the user. To the extent permitted by various security controls an ISPF user has full access to most z/OS system functions.

· To access ISPF under TSO, the user enters a command from the READY prompt to display the ISPF Primary Option Menu.

· You can access online help from any of the ISPF panels (press the PF1 key)

· ISPF includes a text editor and browser, and functions for locating files and performing other utility functions.

After logging on to TSO, users typically access the ISPF Primary Options menu. In fact, many use ISPF exclusively for performing work on z/OS. ISPF is a full panel application navigated by keyboard. ISPF includes a text editor and browser, and functions for locating and listing files and performing other utility functions. ISPF menus list the functions that are most frequently needed by online users.

ISPF has a “tree structure.” Some UNIX users call this menu structure a “captive” interface. The Primary Option menu is at the top of the tree. This panel can be customized with additional options by the local system programmer. Therefore, it varies in features and content from site to site.

General structure of ISPF panels

Option zero (0) allows you to change ISPF settings. For example, the command line for your ISPF session might appear at the bottom of the display, while your instructor’s ISPF command line might appear at the top. This is a personal preference, but traditional usage places it at the top of the panel. If you want your command line to appear at the top of the panel, do the following:

1. Go to the ISPF primary option menu.

2. Select option 0 to display the Settings menu

3. In the list of Options, remove the “/” on the line that says “Command line at bottom.” Use the Tab or New line key to move the cursor.

· Function Key

· Enter Right Ctrl (right side)

· Exit, end, or return PF3

· Help PF1

· PA1 or Attention Alt-Ins or Esc

· PA2 Alt-Home

· Cursor movement Tab or Enter

· Clear Pause

· Repeat Last Find Command PF5

· Repeat Last Change PF6

· Page up PF7

· Page down PF8

· Scroll left PF10

· Scroll right PF11

· Reset locked keyboard Left Ctrl (left side)

Step 1. Enter = 3.4 and press right-ctrl to navigate to the Data Set List Utility Panel. Your TSO logon account should be listed at the Dsname Level parameter. If not, edit the DSNAME Level parameter to list your UserID. Check that the Volume Serial entry is left blank. Press the right-CTRL key to continue.

DO NOT enter the example of RMUI001

Step 2. Type E (for edit) under the command column. Move the cursor to the right of RMUXXXX.JCL and append a member name. This example appended the member name (PACKY). A member name must be surrounded by parentheses. You are required to use YOUR name as a member name. A member name must be severn (7) characters or less.

When you edit a member name that does not exist, z/OS will automatically create a new blank member. Then you will move to the edit panel. If you type 'E" to edit a member that does exist, the member will be opened for editing. If you just type E with a member name, the next panel will display all members in the data set.

Now enter your name as a new member name and press the right-CTRL key to continue.

Step 3. By default an Edit Entry Panel may be displayed on SOME z System servers to warn you that you are trying to create a new PDS member. Your z System server may not display this warning. Ignore the following instructions.

You may type a space to replace the forward slash before Warn on First Data Change, but this is not recommended. Type right-ctrl to continue.

Step 4. A blank new PDS member will appear in the ISPF Edit Panel. Notice that the upper left-corner displays the ISPF panel name EDIT.

You are required to complete the following steps and then document you final version of your ISPF EDIT practice document.

Move the cursor (preferably using the arrow keys) and type the following lines, e.g., "This is Line 1, This is Line 2, This is Line 3 and This is Line 4."

When editing a data set or data asset member, you often use line commands to work with the contents of the data set. For example:

· To edit the contents of a data set, move the cursor to the area of the record to be changed and type over the existing text.

· To insert a new line, use the ISPF Edit Line command

· To find and change text, you can enter commands on the editor command line.

· To insert, copy, delete, or move text, place these commands directly on the line numbers where the action should occur.

·

Warnings! Gotchas!

· You cannot enter ISPF line commands if the Insert keys are on

· You cannot execute any other command if there are any pending line commands. Type the Primary command RESET to cancel any pending commands.

· You may not be able to execute any ISPF Line commands if there is an incorrect Primary command entered on the Command Line. You must manually erase any incorrect Primary commands.

Step 10. Inserting a single line (I) Insert Line Command

Type I on any line number that you want to insert a line after. Press the right-ctrl key to execute.

[Before]

[After]

Type RESET to hide any line messages. Type RENUM to re-number all lines.

Step11. Inserting Multiple Lines at the beginning of the editor (I5)

Type I followed by the number of lines that you want to insert, e.g., I5. Lines will be inserted AFTER the line the command was written. Press the right-ctrl key to execute.

[Before]

[After]

Step 12. Copying a Single Line (C line command)

Type C on the line to be copied. Type A (for after) or B (for before) the line that you want to copy the line to. It really does not matter which order you type the C or A. Line commands will only be executed after you press the right-CTRL key.

[Before]

[After]

Step 13. Repeating Lines (R line command)

Type R on the line to be repeated. If your follow the R command by a number, e.g., R5, then the line will be repeated 5 times. Line commands will only be executed after you press the right-CTRL key.

[Before]

COBOL has many commands that are similar. For example, COBOL has a command like this:

MOVE THIS TO THAT .

Some programmers repeat this command 10 times and simply type over the THIS and THAT phrases for the data that want to code.

Step 14. Moving a Block of Lines (MM..MM, A)

Most line commands provide for a block option. Surround the lines to be moved with a beginning MM and an ending MM command. The lines between and including the MM marked lines will be moved. Type A (for after) or B (for before) to where you will like to move the lines. The type of blocking technique can be used for the Copy lines, Delete Lines, and many other line commands.

[Before]

[After]

Step 15. Copying a Block of Lines (CC..CC, A)

[Before]

[After]

1. It is required to display your data set name which lists your user catalog. Use the Snipping Tool to document your ISPF screen below =

Type each of the following ISPF primary commands, to be entered on the Command line, and press right-ctrl to execute. It is recommended to follow the order of the commands as provided

2. The previous requirement made some changes. It is required to display your data set name which lists your user catalog. Use a Snipping Tool to document your ISPF changed edit panel below =

Step 16. Deleting a Block of Lines (DD..DD). Execute these ISPF Line commands.

[Before]

[After]

Delete any remaining line and use the RESET command to this content and panel view.

Step 17. Displaying Columns. Execute these ISPF Line commands.

COBOL is a column sensitive application programming language. Cobol syntax may be only coded between columns 8 and 71. Some COBOL statements must begin between columns 8 and11. Other COBOL statements may begin between columns 12 and 71. A COBOL comment is typing an asterisk in column 7.

Therefore, it should not be surprising why many COBOL programmers prefer displaying the column line. Type COLS in the primary command line and press right-Ctrl

[Before]

{After]

Step 18. Shift columns to right ( )) ..)) 7 ) Execute these ISPF Line commands.

Even with the column line many COBOL programmers will still make errors and will type the syntax in the wrong column. Fortunately, there is a column move command. You may type a single parenthesis to move a single line to a new column position, or double parentheses to move a block on lines.

In this example, type )) in the beginning of the block, and ))7 at the end of the block. The number"7" indicates to move 7 columns from the current position. ")" means to move to right, and "(" means move to the left.

[Before]

[After]

Step 19. Split Screen (F2)

To view and edit two data members/sets in ISPF, one can split the screen. Before pressing the F2 function key, position the cursor in the middle of the panel. This is where ISPF will split the screen at the cursor position. This allows you to have two or more concurrent ISPF screens.

Create split screens by pressing PF2. This creates a second screen beginning at the current cursor position. To create “full” screens, position your cursor at the very top or very bottom of the display and press PF2.

Toggle between split screens using PF9 (‘SWAP’). Exit any spilt screen by pressing F3.

Before continuing with this spilt screen example, review the previous display. Four lines are used to display the list of function keys, e.g., F1 Help, etc. at the bottom of the panel. Many programmers prefer to remove these lines to increase the number of visible lines available for editing.

To remove the Function key display line type the primary command PFSHOW OFF and press the right-Ctrl key. Notice that PFSHOW is one word followed by a space

To re-display the Function Key display line type the primary command PFSHOW ON and press the right-Ctrl key

Step 20. Changing the Scroll Value. Execute these ISPF Line commands.

The Scroll Value determines how many lines are scrolled very time you press the F7 key to scroll-down (forward) through any ISPF panel and you press F8 key to scroll-up (Backwards) through any ISPF panel. The scroll value is set to PAGE by default and can be used to scroll through ISPF EDIT document or any log file.

You can the scroll value to either HALF or CSR. The HALF potion will scroll in half-page increments. Many prefer the CSR increment which will scroll anywhere you position the cursor. The change the scroll value or increment simply move the cursor and overtype the value. For example:

Step 21. Using the Primary Commands: LOCATE (L) or FIND (F) [You can use the abbreviation]

LOCATE will move to a specific ISPF Line number. It will LOCATE a line number. L 150

Always start the LOCATE command with a TOP command, e.g., TOP;L 150

FIND will move to a specific line number based on a string. For example F PROCEDURE

This example will move to the first line that contains the word PROCEDURE. You can press the F5 function key to repeat the last FIND command to find the next string.

Always start the FIND command with a TOP command, e.g., TOP;F PROCEDURE

FIND will move to a specific line number based on a phrase which will contain embedded spaces by enclosing the phrase with single quotes. For example F 'LETS GO STEELERS'

CHANGE will a word or phrase to a different word or phrase. For example C PERFROM PERFORM

This is my most popular coding error. I always incorrectly misspell the PERFORM command in COBOL.

You can press the F6 function key to repeat the CHANGE command to change the next word or you can change all of the words by appending ALL. For example C PERFROM PERFORM ALL

CHANGE will change a phrase which will contain embedded spaces by enclosing the phrase with single quotes. For example C 'LETS GO STEELERS' 'LETS GO PENGUINS'

(Of course I am biased.)

You can also delete a word or phrase using CHANGE command by using two single quotes – a null string. For example C 'LETS GO STEELERS' ''" ALL

Always start the CHANGE command with a TOP command, e.g., TOP;C PERFROM PERFORM

ISPF Tips for Cobol Programmers - http://billpriceweb.com/ispf.html

12. It is required to display your data set name which lists your user catalog. Use the Snipping Tool to document your ISPF scroll value which is set to CSR below and to document any recent ranges that you have made. =

11. How do you execute two or more ISPF commands, e.g., SUB;=SD;ST?

Using the Job Control Language and the System Display and Search Facility - Chapter 6 - "Introduction to the New Mainframe: z/OS Basics"

IBM Paul Newton's discussion and demonstration of the functions of JCL, the JCL JOB, EXEC, and DD statements, and the relationship of a program file name to JCL DDNAME

Utility programs are pre-written programs, widely used in mainframes by system programmers and application developers to achieve day-to-day requirements, organizing and maintaining data.

The following example will sort a PDS member named RMUXXXXX.JCL(AREACODE). This dataset lists the first-three digits on the postal area codes followed by the state or country that uses those first-three digits. The JCL will EXEC the SORT program. The SORT program is an older utility program and has been replaced by the DFSORT program. The DFSORT program provides more options to exclude, include, MERGE, and copy datasets. The syntax between SORT and DFSORT is similar by, but DFSORT is more powerful. At the time of this writing DFSORT is not available on our system.

Step 1. On the ISPF command input type =3.4, press the right-ctrl key. Move the cursor to the RMUXXXX.JCL partitioned dataset. When the RMUXXXX.JCL displays a list of members type "E" under the command column to edit this PDS member. Press the right-ctrl key. (You may also use "B" for browse.)

Step 2. Enter the reset;cols command on the Command line (Do not use embedded spaces). The ISPF primary command will not execute until you press the right-ctrl key.

Document the data contained in this PDS member named RMUXXXX.JCL(AREACODE) below =

Hint: you should see the phone area code associated with each state.

List the column number where the state or country abbreviation begins. Answer = >

Step 3. Press F3 to exit the ISPF editor. Then press F3 to exit the ISPF member list.

Step 4. Creating a new PDS member is probably the most routine task that a system or application programmer will do. In this example, we will create a new RMUXXXX.JCL member in the 3.4 DSLIST panel. Enter an E (Edit) under the Command column. Move the cursor to end of the PDS name and append a new member name, e.g., (MYSORT). Then press the right-ctrl key (ENTER) to execute.

You may get the "Warn of First Data Change" dialog box. Press the right-ctrl key to continue.

Step 5. Type RESET on the ISPF command line and press the right-ctrl. In order to complete the new member process one MUST enter a few lines and either SAVE or F3 Exit and Save. Z/OS will not save an empty member.

JCL for Sorting Data Sets Directly - http://pic.dhe.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ibm.zos.r12.iceg200%2Fcontras.htm

SORT TUTORIAL - http://www.mainframetutorials.com/drona/programming/languages/jcl/jcl.sort11111.html

LINE 3 describes the DDNAME SYSOUT. What is the purpose of the SORT utility SYSOUT DDNAME? Answer = >

LINE 3 also lists SYSOUT=*. What is the purpose of the SYSOUT=*? Answer = >

Likewise, we must create DD statements for SYSOUT, SORTOUT. SORTIN, and SYSIN.

LINE 4 describes the DDNAME SORTOUT. What is the purpose of the SORT utility SORTOUT DDNAME? Answer = >

LINE 5 describes the DDNAME SORTIN. What is the purpose of the SORT utility SORTIN DDNAME? Answer = >

LINE 5 also lists DSN=&SYSUID..JCL(AREACODE). What is the purpose of this DSN parameter? Answer = >

LINE 6 describes the DDNAME SYSIN. What is the purpose of the SORT utility SYSIN DDNAME?

Answer = >

LINE 6 contains the following operator DD * Follow the DD operator by the name of a dataset or predefined system substitution name of a data set name. DD * means that the content will be an "instream" data content or program parameters. In simpler terms, the DDNAME SYSIN requires directions on how to sort. Instead of putting these directions in a separate data set, place the SORT directions inside the JCL member. Look at Line 7 that follows.

LINE 7 does NOT begin will a double slash. Hence, this is instream data content for the execution of the program. In this example, use SYSIN DD * to provide directions on which columns and how to sort.

The content of LINE 7 is SORT FIELDS=(1,3,CH,A)

Sorting Data Sets - http://pic.dhe.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ibm.zos.r12.iceg200%2Fcontras.htm

After reviewing the following SORT utility input parameters on LINE 7, explain the purpose of "1,3," sub-parameters in the following SORT FIELDS=(1,3,CH,A) Answer = >

After reviewing the following SORT utility input parameters on LINE 7, explain the purpose of sub-parameter "CH" in the following SORT FIELDS=(1,3,CH,A)? Answer = >

After reviewing following SORT utility input parameters on LINE 7, explain the purpose of sub-parameter "A" in the following SORT FIELDS=(1,3,CH,A)? Answer = >

Step 6. On the ISPF command line type SUB;=SD;ST and press ctrl-enter to execute this JCL code.

Step 7. If you have written the correct JCL code and a MAXCC=0000 code is displayed, you should be directed to SDSF. Find the job output with your JOBNAME. Enter a "?" under the NP column to open the SDSF job dataset and list the members (or results) from the job submission. In the following example, the JOBNAME was PL1127. Select your JOBNAME.

Step 8. I hope that you had answered the previous question concerning the purpose of the DDName SYSOUT. To view your sorted output type S under the NP column and press the right-ctrl key.

Step 9. Using a snipping tool document the first 10 lines of DDName SORTOUT for the MYSORT Step, which contains your sorted data below =

Which data was sorted, e.g., the first-three digits of the area code or the state/country name? Why? Answer = >

Step 10. Press F3 several times to exit SDSF and enter =3.4 to re-open your RMUXXXXX.JCL(MYSORT) JCL member. Change Line 7 to the following:

Step 11. On the ISPF command line type SUB;=SD;ST and press ctrl-enter to execute. This will re-submit your JCL job with the new changes.

Step 12. If you have written the correct code and received a MAXCC=0000 code, you should be directed to SDSF. Find the job output with your JOBNAME. Be careful to select the correct job output. Since we had previously submitted two jobs with the same JOB NAME, e.g., PL1127, how will we know which was the most recent job submitted? Select the PL1127 or other JOBNAME with the highest JOBID. Enter a "?" under the NP column and press right-ctrl to open the SDSF job dataset and list the members (or results) from the job submission.

Enter S to select the DDName SORTOUT for Step MYSORT and press right-ctrl to execute.

Step 12. Document the first 10 lines of DDName SORTOUT for the MYSORT Step, which contains your sorted data below =

The data was sorted by which columns? Was the sort order by the first-three digits of the area code or the state/country name? Why? Answer = >

Step 13. Create and code a new PDS member using JCL(MRCREM) and the IEBGENER utility.

This next example will require you to create a new PDS member named MYPROCI, which will mean "My JCL Procedure Instream." A JCL Procedure is simply a set of JCL statements that we want to reuse. For example, few of us are qualified to write prefect JCL to compile, link and execute a COBOL program. Therefore, it is typical that someone codes a PROC or procedure and then others will reuse the PROC. Not only does this save time and complexity, others with less JCL experience can re-use the JCL PROC.

The objective of this step is to convert the JCL SORT statements list in Step 10 to a JCL PROC. In this step, we will first use JCL to create a new member and use the IEBGENER utility.

Create a new PDS member is named MYCRMEM, or My Create PDS member, using the 3.4 DSLIST panel. Enter an E (Edit) under the Command column. Move the cursor to end of the PDS name and append a new member name, e.g., (MYCCRMEM). Then press the right-ctrl key to execute.

You may get the "Warn of First Data Change" dialog box. Press the right-ctrl key to ignore and continue.

Type RESET on the ISPF command line and press the right-ctrl to execute. In order to complete the new member process one MUST enter a few lines and either SAVE or F3 Exit and Save. Z/OS will not save an empty member.

LINE 3 describes the DDNAME SYSIN. What is the purpose of the IEBGENER? Answer = >

LINE 3 also lists DD DUMMY. What is the purpose of the parameter named DUMMY data set name? Answer = >

Step 16. Navigate to your JOB. Document the output for your DDname SYSPRINT for STEP 1 below =

The MYCRMEM JCL was designed to introduce the IEBGENER utility to copy instream data to a new PDS member. The "in-stream" text that was copied into that new member MYPROCI was just a sample. Your MYPROCI should look similar to the result below. In the next step we will 1) copy the MYSORT JCL utility into the MYPROCI JCL, and 2) modify the JCL code to introduce the concept of an Instream JCL Procedure

Step 17. Copy your SORT JCL code into your RMUXXXX.JCL(MYPROCI) member. You can copy the content of one PDS member by using one of three methods.

This method may be clumsy at times. While we start by entering a C on the Option line, one will not be able to use the fill-in-the-blanks format FROM ISPF LIBRARY. It is required to must specify the source member name. This utility assumes that the source is always in the format of HLQ.DDD.DDD(MMMMM). We will not use this PDS member copy member method in this example.

SYSUT1 in Line 5 was changed from our previous example from DD * - designed to instream data to DD DISP=SHR,DSN=&SYSUID..JCL(MYSORT). This method is a little clumsy also. We will not use this PDS member copy member method in this example.

This method is normally the easiest to use for copy JCL or application code. It will be demonstrated in the next requirement.

The JCL Procedures are set of statements inside a JCL grouped together to perform a particular function. Usually, the fixed part of the JCL is coded in a procedure. The varying part of the Job is coded within the JCL.

You can use a procedure to achieve parallel execution of a program using multiple input files. A JCL can be created for each input file, and a single procedure can be called simultaneously by passing the input file name as a symbolic parameter https://www.tutorialspoint.com/jcl/jcl_procedures.htm

Use the ISPF EDIT Primary Command. In STEP 16, you were instructed to open the RMUXXXX.JCL(MYPROCI) data set member. Type either A or B on a line (for either After or Before) to indicate where the copied line code should be placed.

Type the member name to be copied. [This example only pertains to copy a 'from' member to a 'to' member in the same PDS dataset.] Press the right-ctrl key to execute the COPY.

The result should look similar to the following.

This method can be also used to copy member between two different PDSs. Assume that your instructor wants you to copy the same JCL into your PDS member from RMU.JCL(MYSORT). The ISPF Edit command would be the following. [Notice the single quotes. Surrounding a dataset member with single quotes means that the source member will be found in a different dataset. DO NOT PERFORM THIS EXAMPLE.

Step 18. Edit and enter the following MYPROCI code.

When the procedure is coded within the same JCL member, it is called an Instream Procedure. It should start with a PROC statement and end with a PEND statement.

The previous JCL code includes an in-stream PROC (JCL Procedure) declared Lines 4 to 9. An in-stream PROC begins with a PROC or PROCEDURE statement which defines the PROC name, e.g., the MYPROC DDNAME. When a COBOL compile-link-go JCL was demonstrated in a previous assignment, the IGYWCLG JCL Procedure was used (EXEC IGYWCLG). If we would have written the IGYWCLGPROC, the code would be similar to Line 4, e.g., //IGYWCLG PROC instead of our example //MYPROC PROC.

A PROCEDURE can be executed one of two ways: External PROCs (two separate JCL members or one JCL member - an in-stream PROC. An in-stream PROC must be declared BEFORE the PROC is used in Line 12. An in-stream PROC must end with the PEND statement. A catalogue PROC will be demonstrated next. The PEND statement will be optional since the PROC will be declared in separate PDS member than the JCL member that calls or invokes it.

Carefully review Lines 8, 12 and 14. Any JCL identifier that begins with an ampersand, i.e., &, is a substitution variable. In a previous assignment the substation variable &SYSUID coded on Line 1 was discussed. When the JCL is execute, z/OS will substitute the USERID of the person who submitted the job. In Line 8 the substitution variable &SORTDSN is declared. When the PROC is executed in Lines 12 and 14, the substitution variable SORTDSN must be defined before a call to the PROC named MYPROC. In this example, the &SYSUID..JCL(AREACODE) will be substituted or use in &SORTDSN. Therefore, the MYRPOC Procedure requires the calling JCL to provide the name of the data set to be sorted.

By using substitution variables, the same JCL PROC can be re-used by any calling JCL. Just provide the name of the data set to be sorted and MYRPOC will sort it

MYPROC is executed twice . Once in //STEP1 (Line12), which will sort by the first three characters, and then in //STEP2, which will sort by characters 6 thru 10.

Step 19. On the ISPF command line type SUB;=SD;ST and press ctrl-enter.

Step 20. If you have written the correct code and received a MAXCC=0000 code, you should be directed to SDSF. Find the job output with your JOBNAME. Be careful to select the correct job output. Since we had previously submitted two jobs with the same JOB NAME, e.g., PL1129, how will can one determine which was the most recent job submitted? The answer is the PL1129 JOBNAME with the highest JOBID. Enter a "?" under the NP column to open the SDSF job dataset and list the members (or results) from the job submission. Your JOB should appear similar to the following

Notice that there are two DDNames for SORTOUT listed, i.e., once for Step1 and a second for Step 2. The reason for this is MYSORT PROC is called twice.

Navigate to your JOB. Document the first 10 lines of your DDname SORTOUT for STEP 1 below =

Navigate to your JOB. Document the first 10 lines of your DDname SORTOUT for STEP 2 below =

When the procedure is separated out from the JCL and coded in a different data store, it is called a Cataloged Procedure. A PROC statement is not mandatory to be coded in a cataloged procedure.

Step 21. Creating a catalog procedure (PROC) (Page 366 of text book). In this example, we will separate MYPROCI (our in-stream PROC) into two separate members, which will be named MYPROCC and MYPCALL. By separating the PROC into a separate PDS member any JCL code may use the PROC.

Create a new member named MYPROCC. The appended "C" stands for cataloged and previously appended "I" means an in-stream procedure.

You may get the "Warn of First Data Change" dialog box. Press the right-ctrl key to ignore and continue.

Type RESET on the ISPF command line and press the right-ctrl. In order to complete the new member process one MUST enter a few lines and either SAVE or F3 Exit and Save. Z/OS will not save an empty member.

Type either A or B one a line (for either After or Before) to indicate where the copied code should be placed.

Type the member name to be copied. [This example only pertains to copy a 'from' member to a 'to' member in the same PDS dataset.] Press the right-ctrl key to execute the COPY.

Step 22. Edit and enter the following JCL code to create a cataloged procedure (PROC).

First, notice that a catalog PROC contains NO JOB statement. The reason for no JOB statement is that a cataloged PROCEDURE will not be submitted for a JOB. Rather, it will be called by another JOB, i.e., MYPCALL JCL, which we will code in the next step.

Second, to distinguish the cataloged PROC from other PROCs we will code it with a unique DDname, e.g., MYPROCC. While PROC DDNames are not required to be unique there may some confusion when there duplicate PROC DDnames within the same JCL library or PDS data set.

Third, the PEND statement is optional within a catalog PROC since the code ends automatically at the end of the JCL code.

Document your MPPOCC Catalog Procedure below =

Step 23. Create a JCL member that will call the catalog procedure (PROC), i.e., MYPCALL. Create a new member named MYPCALL.

You may get the "Warn of First Data Change" dialog box. Press the right-ctrl key to ignore this and continue.

Type RESET on the ISPF command line and press the right-ctrl. In order to complete the new member process one MUST enter a few lines and either SAVE or F3 Exit and Save. z/OS will not save an empty PDS member.

Type either A or B one a line (for either After or Before) to indicate where the copied code should be placed.

Type the member name to be copied. [This example only pertains to copy a 'from' member to a 'to' member in the same PDS dataset.] Press the right-ctrl key to execute the COPY.

Navigate to your most recent JOB submission. Document the first 10 lines of your DDname SORTOUT for STEP 1 below =

Document the first 10 lines of your DDname SORTOUT for STEP 2 below =

Step 27. JCL PROC Overrides (Page 255 text book). The advantage of using a PROC is that a developer can re-use JCL Procedure code previously developed and slightly modify its execution. This will same time and hide the complexity of the JCL. The disadvantage of using a PROC is that it might not do exactly what you want it to do. This is frequently the case when a user wants to redirect the output to a different location or replace a procedure step.

Create a JCL member that will illustrate a PROC override, i.e., MYPROCO. Create a new member named MYPROCO.

You may get the "Warn of First Data Change" dialog box. Press the right-ctrl key to ignore and continue.

Type RESET on the ISPF command line and press the right-ctrl. In order to complete the new member process one MUST enter a few lines and either SAVE or F3 Exit and Save. Z/OS will not save an empty member.

Type either A or B one a line (for either After or Before) to indicate where the copied code should be placed.

Type the member name to be copied. [This example only pertains to copy a 'from' member to a 'to' member in the same PDS dataset. ] Press the right-ctrl key to execute the COPY.

Step 28. Edit and enter the following JCL code to OVERRIDE the DDName SORTOUT. The second job step STEP2 was omitted.

The JOBname in Line 1 was changed to MYPROCO to make it easier to find in SDSF. This is not required.

The original PROC statement for the DDName SORTOUT (Line7) was //SORTOUT DD SYSOUT=*

Where does keyword SYSOUT=* direct its output to? Answer = >

The override is coded on Line 13. It starts out with MYSORT.SORTOUT, or STEPNAME.DDNAME. Remember the STEP Name is found with an EXEC statement. Review Line 5. The DDname is found on a DD statement. Review line 7.

The override will simply redirect the output form SYSOUT=* to DSN=&SYSUID..JCL(ASSIGN5) - a member name. The output will NOT be directed to SDSF, but rather be overridden and directed to a PDS member name,

Step 29. Submit your MYPROCO JCL. On the ISPF command line type SUB and press ctrl-enter to execute.

If you have written the correct code and received a MAXCC=0000 code, there is no reason to go to SDSF since the output was redirected to your JCL PDS file. Navigate to your RMUXXXX.JCL(ASSIGN5) PDS member . Document the data set name and the first 10 lines of this member below =

What are the differencesbetween a substitution variable, e.g., &SORTDSN, and a PROC override? Substitution variables represent the REQUIRED data input to the PROC or JCL in order to execute. Without the values stored in a substitution variable the PROC or JCL cannot execute. Substitution variables provide flexibility to execute the PROC or JCL under various conditions or values.

On the other hand, a PROC override is NOT required, or optional. A PROC override permits the calling JCL to replace existing PROC JCL code. While both substitution variables and PROC overrides provide flexibility when designing JCL code, PROCs overrides replace while substitution variables customized.

1. What is a cataloged procedure? Answer = >

2. What is the advantage of a cataloged procedure? Answer = >

3. What is an in-stream procedure? Answer = >

4. What doesn't a cataloged procedure contain a JOB statement? Answer = >

1. What is UNIX Shell? Answer = >

2. What is function of the Unix Shell prompt? Answer = >

3. What is a UNIX or Linux Shell Script? Answer = >

4. List at least three reasons why the integration of UNIX and z/OS a powerful combination? Answer = >

5. What is function of Telnet? Answer = >

6. What is the function of FTP? Answer = >

7. What is the function of SSH? Answer = >

Chapter 4: TSO/E, ISPF, and UNIX: Interactive facilities of TSO: Introduction to the Mainframe: z/OS basics

8. Check either the Yes or No columns in the following table concerning the integration the integration of USS and z/OS

9. What are the functions of the z/OS OMVS command shell processor? Answer = >

UNIX users normally have a variety of UNIX text editors. The most historic and popular UNIX editor is called vi. IBM provides a more familiar text editor for z/OS users called oedit (lower-case please)

Type oedit rmuxxxxmyfile, where xxxx is your z/OS userid, and press the right-ctrl to execute.

The following z/OS text editor should appear. Type and execute the RESET command to clear any message lines.

There are two important features to notice.

1. We were not required to allocate our UNIX file before we could edit the file. In z/OS you are required to allocate a data set before use.

2. The file system rules UNIX files are different that z/OS. There is no user catalog, but there is a subdirectory based on your z/OS userID. z/OS does not use subdirectories to organize data sets , rather, it uses partitioned data sets, VTOCs and catalogs. In some features USS is very similar to Windows, Linux, and other modern operating systems. But, you will not see this file displayed in ISPF Data set view (3.4)

Using ISPF enter your name on the first line, your email address on the second line, and some of your words of wisdom on the third line. When finished press F3 to exit and save.

Use oedit to create two more UNIX files with a filename that starts with your z/OS userID. The rules for naming UNIX and LINUX files are provided. Each file should contain any five lines of text you want.

· All file names are case sensitive. So filename vivek.txt Vivek.txt VIVEK.txt all are three different files.

· Spaces are permitted, excepted when escaped.

· You can use upper and lowercase letters, numbers, "." (dot), and "_" (underscore) symbols.

· You can use other special characters such as blank space, but they are hard to use and it is better to avoid them.

· In short, filenames may contain any character except / (root directory), which is reserved as the separator between files and directories in a pathname. You cannot use the null character.

· No need to use . (dot) in a filename. Sometimes a dot improves readability of filenames. And you can use dot based filename extension to identify the type or content of the file. For example: .sh = Shell file, or .tar.gz = Compressed archive

· Most modern Linux and UNIX limit filename to 255 characters (255 bytes). However, some older version of UNIX system limits filenames to 14 characters only.

· A filename must be unique inside its directory. For example, inside /home/vivek directory you cannot create a demo.txt file and demo.txt directory name. However, other directory may have files with the same names. For example, you can create demo.txt directory in /tmp.

· Linux / UNIX: Reserved Characters And Words Avoid using the following characters from appearing in file names: / > < | : &

· Please note that Linux and UNIX allows white spaces, <, >, |, \, :, (, ), &, ;, as well as wildcards such as ? and *, to be quoted or escaped using \ symbol.

Use the OMVS obrowse command to view your first file. Normally, UNIX users use the cat command to display the contents of a file. This will be illustrated next.

13. Use the Snipping Tool to document the results of your OMVS obrowse command below =

Press F3 to exit and return to OVS.

Use the cat command to display the contents of a file.

14. Use the Snipping Tool to document the results of your UNIX cat command below =

15. What are the differences between the OMVS obrowse command and the UNIX cat command? Answer = >

17. Explain the function of the following UNIX commands using the following table.

Type exit and exit the OMVS UNIX command shell

In the ISPF press F3 to exit ISPF.

End of Assignment 2 Hands-on

Page 90 | 90