assistance needed on OPCA ETT.

aprocon · New User Joined: 26 Oct 2010 Posts: 41 Location: chennai

Hi all

I have some files that are being FTP'ed from unix to mainframes almost thru out the day. I would like to process these files based on their availability. hence i have chosen OPCA ETT. My process with the files is going to be the same( unloading, loading, etc.). but my file names differ in the last qualifier. I do not know how many files i am going to receive a day. Just wondering will my job process trigger if i give * as the last qualifier in the name of the triggering event.

Any suggestion other than ETT is also appreciated..

Thanks in advance for all your suggestions.

PeterHolland · Posted: Tue Oct 26, 2010 1:32 pm

You can specify the triggering-event name generically by using the
generic search characters * (asterisk) or % (percent). If there is more
than one match for generic filters, the most specific match is selected.

See :

TWS Managing the Workload SC32-1263-00

Arun Raj · Posted: Tue Oct 26, 2010 1:34 pm

Hello,

Welcome to the forums.

I doubt if it's possible to give multiple datasets as ETT triggers. You may give a single dataset as ETT trigger and list out the rest of datasets as "special resources" in OPC if you want to wait for all the files.

Anyways it all depends on how you want to trigger your process, whether ANY one of the files is available or ALL the files are available.

aprocon · New User Joined: 26 Oct 2010 Posts: 41 Location: chennai

Thanks Peter and Arun..

I need to start my job as and when the file is available in the mainframes. so here is my requirement like. my job "x" should trigger when file A.B.1 is available, again x should trigger when file A.B.2 is available and it should work until all the files A.B.N are received.

Thanks

PeterHolland · Posted: Tue Oct 26, 2010 5:38 pm

*sigh*

What didnt you understand about the answer i gave in response to
your question on using a generic dataset name as triggering dataset.
Its all in the manuals and else ask your TWS support.

aprocon · New User Joined: 26 Oct 2010 Posts: 41 Location: chennai

Hi Peter,

I looked at the document and was little confused. I thought it was just for J- type.. Will try and let you know..

Thanks for your response..

aprocon · New User Joined: 26 Oct 2010 Posts: 41 Location: chennai

Peter,
It works if the dataset is already exisitng but not when I try FTP ing. I am not able to figure out the reason. I skimmed through the forums to figure out if anyone have had similar issues, I saw the below instructions from Rajesh and followed them, but still unlucky.

1. Triggering event and job submitted application, and other parameter
should be defined in ETT pannel shown in my first post.

2. Triggering event should be present in EQQDLIST and EQQDLIST in
member of OPC job lib. ( I was missed out this thing. )

3 EQQDLIST is created by using EQLSJCLR JCL ( It is supplied by IBM while installing OPC,change the JCL according to your needs ).

could you please help me through?

PeterHolland · Posted: Wed Oct 27, 2010 2:59 pm

Did you follow the instructions in chapter Chapter 20 Event Triggered Tracking in manual :
TWS Planning and Scheduling the Workload SH19-4546-01

Ramya G · New User Joined: 01 Jul 2009 Posts: 6 Location: India

Hi,

My problem is the same too. If I FTP the dataset, the job is not triggered. but it works fine when I do a COPY of the dataset. Is their any other way to achieve this? I followed the instructions in the manual.

Thanks

aprocon · New User Joined: 26 Oct 2010 Posts: 41 Location: chennai

Peter,

yes, I did follow the instructions in the manual.

PeterHolland · Posted: Wed Oct 27, 2010 4:48 pm

For now im at a loss, cause here :

ibmmainframes.com/about47408.html

it worked.

dick scherrer · Posted: Wed Oct 27, 2010 7:41 pm

Hello,

Is the FTP actually creating the dataset or simply over-writing an existing dataset?

PeterHolland · Posted: Wed Oct 27, 2010 9:11 pm

dick scherrer · Posted: Wed Oct 27, 2010 9:25 pm

Hi Peter,

PeterHolland · Posted: Wed Oct 27, 2010 9:32 pm

Dick,

data set triggering is depending of the closing of a dataset. FTP'ing a
dataset to a mainframe is in my opinion receiving it and then after that
closing it. TWS (OPC) exits have to take care of that. I dont know the
environment te TS is working with, so as i suggested to read the manuals
and act like suggested in those manuals, another way to solve this problem is to ask TWS support (if existing)

dick scherrer · Posted: Thu Oct 28, 2010 3:53 am

Hi Peter,