0% found this document useful (0 votes)
30 views12 pages

TWS Notes

The document outlines procedures for managing failed jobs in an application, including removing dependencies, releasing special resources, and force completing jobs. Users can modify job settings through specific commands in the system interface to manage job execution and scheduling. Additionally, it provides instructions for adding or deleting dates in RUN periods for job cycles.

Uploaded by

SaKetGupTa
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
30 views12 pages

TWS Notes

The document outlines procedures for managing failed jobs in an application, including removing dependencies, releasing special resources, and force completing jobs. Users can modify job settings through specific commands in the system interface to manage job execution and scheduling. Additionally, it provides instructions for adding or deleting dates in RUN periods for job cycles.

Uploaded by

SaKetGupTa
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 12

7) Restarting failed application without its dependencies / Removing

dependencies:

Whenever user doen’t want to trigger the dependent application of failed job we have to
remove it’s dependencies.

 Go to option 5.2 Specify job name.

 In row command type M –(Modify)

 Type OPER at command line.

 Type S.1 at row command of last DUMMY job.


 Type D to delete all the successor applications.
8) Releasing Special Resources of failed jobs:

Request may come to release special resource of failed job in order to trigger another job
which is using the same resource.

 Go to option 5.2 Specify job name.

 In row command type M –(Modify)

 Type OPER at command line.


 Type S.2 at row command of failed job.

 Type D to delete special resource.


9) Force completing failed job

 Go to OPC error list option 5.4

 Type C in row command of failed job to force complete job.


 It will ask confirmation. Type Y to confirm.

9.2) Go to option 5.2 Specify job name.


 In row command type M –(Modify)

 Type OPER at command line.


 Type C in second last column of failed job.Press F3 twice to come out. Occurrence will get
modify.

10) Force completing whole application

This is one way. 10.1) Type CMP in option 5.4(error list).

This is another way 10.2) Go to option 5.2 Specify job name.


 Type C in row command.
11) Adding /Deleting dates in RUN Periods:

User provides RUN Period name and asks to add or delete the specific dates.

 Go to 1.3.2 (Database-Period-Create)

It will list all the dates of that RUN cycle on which it is supposed to run.

 Type M at row command of run perid name

(e.g. M PPAZMTH1)
 For adding new dates type I at row command to insert new rows. Specify the new
Dates

 For deleting new dates type D at row command to delete specified dates.

You might also like