Skip to main content

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



Comments

Popular posts from this blog

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

Control M: Zoom Screen

This section breaks down the various fields you see within a job using the Zoom command.    Many of the fields within the zoom     screen can be altered.   There a few (they will show a different color) that cannot.   To make any changes, a job must be in a HELD     state before zooming, then when in the zoom screen make the changes and type SAVE at the command line.   Remember to FREE     the job when you are satisfied with your change.   Type CANCEL instead of SAVE if you don’t want your changes to be saved. MEMNAME – schedule member name, should be same as jobname. MEMLIB – denotes where CTM will scan for jcl, standard is GENERAL, which will default to the                     predefined concatenation.   An entry of DUMMY indicates a dummy job, or one that will not execute jcl.   These                    are used as schedule placeholders.   OWNER – owner id of job. TASKTYPE – JOB – batch job, STC – started task, GRP – group entry, CYC – cyclical job o

Control M : Commands entered against a job or task

  ? (WHY) Displays what a job is waiting on.    This shows only what a job is currently waiting on at that          time.    It will not show conditions that have already been met, and, certain requirements may change.   ex – you may check a job and it is waiting on a certain job/in-condition one minute.   you check 5 minutes          later and the in/condition may have been met, but it now is waiting on an INIT.       Also, within this screen, you can add an IN-CONDITION.   USE CAUTION when doing this.   It should     only be used when you are ABSOLUTELY SURE that you want to add this condition as it will add it for     any job on the schedule looking for it- and any other job looking for it on that day. L   (log) Displays IOA log entries for that job.   H (hold) Puts job in held status.   A job held will not change states until it is freed.   For example, if a job         is executing is held, even though the job ends, Control M will not change it’s sta