OPC(Operations Planning & Control) Tool:

OPC/ESA
OPC/ESA is a key step towards unattended operations.
OPC/ESA expands the scope for automation of data processing operations. It
automates, monitors, and controls the flow of batch work. It plans and automatically
schedules the batch work load on a daily and long-term basis.
Increased automation improves utilization of resources and gives more control over
assets and better management of batch processing.
The job tracking function automates batch processing by controlling the execution of
jobs in accordance with priorities, required resources, available resources and
dependencies. This promotes optimum use of resources, improves systems availability,
and reduces the number of complex and repetitive operator tasks.
OPC/ESA long-term planning function enables you to maximize utilization of system
resources. You can produce long-range plans that accurately display the future
workload and its impact on the data processing environment.
OPC/ESA gives detailed real-time information about the processing of the workload.
Type O in the command line to select OPC/ESA

OPC Pannel

Long-Term Plan :
The long-term plan is a high-level schedule of processing activities for the forthcoming
weeks and months.
The long-term plan lists, by day, the instances of applications to be run during the plan
period. (In OPC/ESA each instance of an application is called an occurrence.) It shows when
they are to be run and the dependencies among different applications.
The long-term planning function plans production runs of applications and enables to
examine and analyze the expected future work load.
Current Plan :
The current plan is an online working copy of the daily plan. It contains essential
information about individual operations, current status information that is updated online.
This status is used by job tracking to submit the operations for processing.
Automatic Job Submission:
The job tracking function automates batch processing by controlling the submission of
jobs in accordance with the:

Dependencies among operations and applications

Job priorities
Specified time for execution of certain jobs
Availability of resources required for execution.

It promotes the optimum use of resources, improves systems availability, and reduces the
number of complex and repetitive operator tasks.
Activities:

Find out how many jobs are there in the application

Add an application
Create ETT application
Create run cycles for an application
Check operator instructions for a Job
Schedule an application
View whether an application is running or not
View JCL
Restart a job
Force complete a job
Set maximum allowable return code for a job

1.Find out how many jobs are there in the application :

Type 1 in the command line to select the Data Base

Type 4 in command line to select Application Description

Type 1 to List the applications

Enter the name of the application to be listed

Select the application by typing the row command S

T: Shows the type of application:

A = Application.
G = Group definition.

S: Shows the application status:

A = Active. The application can be selected for processing.
P = Pending. The application CANNOT be selected for processing.

To see the Jobs in the application type op or oper in the command line

2.Add an application:
Type 4 in command line to select the Application description

Select Create application description by typing 2 in the command line

Type in the application ID and give the command op to proceed.

Give the work station, operation number, duration, job names and internal dependencies
To set external predecessor select the first job by giving the row command s

Select the option 1 to set the predecessors

Give the Application ID, job name and work station & operation number assigned for that
job to which dependency should be made.

3. Create ETT application:

Event Trigger Tracking (ETT)

For a job to be tracked, usually it is define as an operation in an application in the

OPC/ESA databases and it must be scheduled, included in the current plan.

Using ETT, it is possible to track 'unplannable' jobs, jobs whose runtimes cannot be
determined in advance, and which, therefore, cannot be planned and then scheduled. ETT
dynamically adds these jobs to the current plan at the time of a triggering event.

The triggering event occurs,

when a non-OPC/ESA job matches an ETT specification or
when the availability status of a special resource is changed to 'yes' by a user
action.

Give 2 in the command line to select the Modify option

Type a new Trigger name which is to be created and then press Enter

Give the Row command I to insert a new row and give the Trigger name, ID of the
application to which that trigger should be associated and Event types etc (This screenshot is
for browsing ETT thats why there is no option for row command)

E T:

Shows the type of Trigger event which adds the associated

application to Current plan

J - A job reader event is the triggering event.

R - A special resource availability event is the triggering event.

J R: Shows job-name replace, which is only valid with event type J.

Indicates if the job name of the first operation in the associated
application should be replaced.
Y - The name of the first operation is replaced by the job name of the
triggering job.
N - The application is added unchanged.

D R: Shows the dependency resolution, which indicates if external dependencies

should be resolved automatically when occurrences are added to the Current Plan.
Y - External dependencies will be resolved.
N - External dependencies will NOT be resolved.
P - Only external predecessors will be resolved.

A S: Availability status switch indicator. Only valid if the event type is R .

Indicates if ETT should add an occurrence only if there is a true availability status
switch for a special resource from status available=no to available=yes, or if ETT should add
an occurrence each time the availability status is set to available=yes (regardless of the
previous status of the special resource). For event type J this field must have the value N or

blank. Y means that ETT adds an occurrence only when there is a true availability status
switch from status available=no to available=yes. N means that ETT adds an occurrence each
time the availability status is set to available=yes.
4.Create run cycles for an application :
Select the list by giving the option 3

Give the application name and press Enter

Modify the application by giving the row command M

Give the line command run to create a run cycle of this application

Give the name for the period or rule input, deadline time and all other options, to setup a rule
give row command S otherwise give a valid period name

Type:

Shows the run-cycle type for the application

R - Rule-based run cycle. Identifies days when

the application is to be run.
E - Exclusion rule-based run cycle. Identifies
days when the application is NOT to be run.
N - Offset-based normal run cycle. Identifies
days when the application is to be run.
X - Offset-based negative run cycle. Identifies
days when the application is NOT to be run.
F(ree) day rule: Shows how the run cycle handles free days defined in the calendar.
E - Free days excluded. Only count work days when the run cycle is defined using a
numeric offset. For example, if you define offset 10 in a monthly noncyclic period, or the 10th
day of the month in a rule, and you specify E occurrences are generated on the 10th work day
of the month as opposed to the 10th day.
If an occurrence is generated on a free day it can be handled as follows:
1 - Moved to the closest work day before the free day.
2 - Moved to the closest work day after the free day.
3 - Run on the free day.
This is the option to create the rule based run cycles. After selecting the Frequency, day
and Cycle give the command Gendays to view the calendar showing the run days

Days highlighted is the day on which the job runs according to the rule specified

5.Check operator instructions for a Job

Select the application description by giving the command 4

Give the application name

Select the application by giving the row command S

Give the command op or oper

Select the job to by giving the row command s

Select the operator instruction by giving the option 7

6.Schedule an application

Select the Modify current plan by giving the option 5

Select the Add new occurrence by giving the option 1

Give the application which has to be scheduled and press enter

Give the input arrival date and time (i.e. date and time at which the job should start) and
also the deadline date and time. Then give the line command op or oper

If we want the job should be submitted automatically when the input arrival date n time is
reached, give the Opt S as Y otherwise give N and if we want the job to start only when the

input arrival date and time is reached give Opt T as Y, if T is set N then job will stat to run
immediately after coming out of the MCP

Operation ws : Specify the name of a workstation, 1-4 alphanumeric

characters, the first alphabetic or national.

Operation no. : Specify the operation number. Valid values are 1-255.

Operation text

Jobname
: Specify the name of the job, 1-8 alphanumeric characters, the
first alphabetic or national.

PS

Duration: Specify the approximate time needed to complete the operation at the
workstation, in the HH.MM format.

Opt S:

Opt T: Specify if the job is time dependent or if it is submitted as soon as possible.

Y = Yes. Do not start the job before the input arrival time is

: Specify a description of the operation, up to 24 characters.

: Specify the number of parallel servers

Specify if the operation should be submitted automatically.

Y = Yes. Submit the operation.
N = No. Do NOT submit the operation.

reached.
N = NO. Start the job as soon as predecessors are

Ext S/P: Shows if the operation has external dependencies, successors S and
predecessors P.

Res S: Shows if special resources are required:

Y = Yes. Special resources are required.
N = No. Special resources are NOT required.

Res R1: Specify the required number of workstation

R2: Resource 1 and 2. Valid values are 0-99.

Status New: Specify a new status code for the operation.

Optional.
C - Complete.
I - Interrupted.
R - Ready for processing.
S - Started.

Status
A
C
D
E
I
R
S
U
W
*

Cu:
-

Shows the current status of the operation:

Ready, no predecessors were defined.
Complete.
Deleted.
Operation ended in error.
Interrupted operation.
Ready for processing, predecessors complete.
Started.
Undecided. The status is not known.
Waiting for a predecessor to complete.
Ready, at least one predecessor was
defined at a non-reporting workstation.

7.View whether an application is running or not

Select MCP by giving the option 5

Give the application name or job name

Check whether the Status field S if its c job completed, if s job submitted, if w job is
waiting and if E ended in error. Give row command B to see the jobs in that nest

Status of each job can be checked. To see more details of the job select the job by giving the
row command S

More information can be viewed by selecting appropriate options

8. View JCL
JCL can be Viewed or edited only in the Current Plan. Select List by giving the
Option 2

Give the application name or job name and then press Enter

Give the row command m to open the application in the modify mode or b to browse

Give the line command op or oper

Give the row command J to view the JCL of that particular job

If it is opened in browse mode we can see the JCL or if in modify mode we can make
Changes to JCL

Restart a job :
Force complete a job :

Give e in the status field to list application which ended in error

Give the row command m to open the application in modify mode

Row cmd:

this group will

group will be

be erased.

Specify one of the following commands:

B - Browse the occurrence.
C - Complete the occurrence.
CG - Complete the occurrence group. All occurrences belonging to
be completed.
D - Delete the occurrence.
DG - Delete the occurrence group. All occurrences belonging to this
deleted.
M - Modify the occurrence.
R - Rerun the occurrence.
RG - Remove from the occurrence group. The group definition id. will

W - Set the occurrence to waiting.

S: Shows the occurrence status:
C = Complete. All operations are complete.
E = Ended-in-error. One or more failed operations.
S = Started. One or more started operations.
U = Undecided. The status is not known.
W = Waiting. No operation has started.

P:

Shows the priority, where 1 = low, 2-7 = medium, 8 = high, and 9 = urgent

G:

Add func:
Blank
A
D
E
P

Shows whether occurrence is a member of a group.

Y = Occurrence is a member of an
occurrence group.
N = Occurrence is not a member of
an occurrence group.
Shows which function added the occurrence:
Daily planning batch program
Automatic recovery (AR)
Dialog (MCP dialog)
Event-triggered tracking (ETT)
Program interface (PIF)

Give the line command op

Give the Status New as r to restart the job or c to force complete the job

11. Set maximum allowable return code for a job

This is option 1.4.3 (i.e. Database AD List) give the job name or the application
name

If job name is entered, it will list all the applications which contain that job
So select the required application give the row command M

Give the line command op

Select the application for which the highest allowable return code to be set by giving
The row command S

Select the option 4 i.e. Automatic Options

Give the return code in the field Highest returncode

NFTP RAP TABLE SETUP

To create the RAP Entry the following information needed from the remote
end.
Remote System, Remote Userid, File name

Give 9.F at ISPF main panel to go to NFTP panel

Give R to goto RAP entry panel

Option 1 to view all the existing entries & 2 to create new RAP entry

Give Remote Userid, server name and dataset name. Pds containing jobs and successful &
unsuccessfull job names are from our end. Once giving all the above info come out from this
panel and it will be save and throws a message Permit update successful.