Skip to main content

Posts

Showing posts from 2015

Restarting a abended job in CA7

To restart the job, type xQ command to get into the CA7 Queue Maintenance. Tab down to the job you want to restart, type an 'F' beside it, and hit the Enter key. You will get into restart panel. Options for restarting the job: Resubmit for production: Resubmits the job with no changes.  Force complete: Indicates whether to flag the job as normally completed. If force complete is selected, the previous abnormal status of the job is ignored, and normal job completion processing is performed instead of a restart. CA-11 restart/rerun :Complete the following fields for a CA-11 restart/rerun: Pseudo(Optional) Indicates whether this job uses the CA WA Restart Option pseudo processing feature. Usage(Optional) Indicates an optional CA WA Restart Option usage code, the character to use in the restart/rerun. For values, see the CA WA Restart Option documentation. This option is honored only when CA WA Restart Option is in use and CA Workload Automation CA 7 Ed

Job abend restart process guidelines

    When any job abends, the first thing we need to do is identify the reason for the failure of the job.Once the reason is found then you need to see whether any data correction/data deletion to be done.Some times you may have to do program change to correct the failure. Once after correcting the problematic data or issue one has to decide from where the job need to restart. Options for restarting jobs. Restart from the same abended step Restart form any earlier step Restart form top Bypass the abended step and continue from next step Mark the job as completed. 1.If there is no dependency with earlier steps then the abended job can be restarted from the same step. 2.If any temporary data sets are used in the abended step,then we will have to find from where they are getting created in the job.If that file is created two steps earlier then you may have to restart the job from that step where the temporary data set is getting created. We should refer

TSO and ISPF

TSO : It stands for Time Sharing Option .  It provides command-line-interface to zOS. It fulfills the similar purpose to Unix login session. Time sharing means many persons can access the operating system concurrently.  TSO commands can be embedded in REXX execs or CLIST, which run interactively or in batch. It provides a text editor, batch job support and debuggers. It provides facility to submit job and store datasets via computer's operating system TSO Login Screen  ISPF : It stands for Interactive System Productivity Facility . It is frequently used to manipulate z/OS datasets. It provides terminal interface with a set of panels. ISPF Sceen ISPF FUNCTION KEYS PF 1 = Help PF 2 = Split the session PF 3 = End PF 4 = Return PF 5 = Rfind (repeat last find) PF 6 = Rchange (repeat lst change) PF 7 = Move Backward PF 8 = Move forward PF 9 = Switch between screens during a split session; goes with PF 2 PF 10 = Move left PF 11 = Move rig

Overview

Mainframe is a high performance computer which supports multiple user at same time. It is used for large scale computing. It is highly reliable and secured. It is used by big organizations like banks, financial institution, retail sector, travel industry, military agencies etc  Application support is an essential process for any application to make sure The application is running fine on day to day basis. Help business when ever they require any information related to the application. To make sure the application is up and running as soon as possible when ever any abnormalities happen. Mainframe Application Support team may perform  Batch Execution Batch Scheduling Batch Optimization Batch Standard Consulting Production deployment Test component deployment Mid range Transition Process Automation   CA7 cleanup