|
View previous topic :: View next topic
|
| Author |
Message |
me00266
New User
Joined: 29 May 2007
Posts: 2
Location: Portugal
|
|
|
|
Hello all, maybe someone can help me with the following issue:
I'm testing the use of the ETT file triggering in order to put an application in the current plan whe a file is created; I've followed the manual instructions and first I've tested by creating the file thru TSO and it works fine;
By submiting thru the IBM util IEBGENER when it creates the file, it also works;
Finally, when creating the file thru the util IEFBR14, it does not trigger the application on the current PLAN.
Does anyone has an idea of the reason why ?
thank you in advance |
|
| Back to top |
|
 |
Nic Clouston
Global Moderator
Joined: 10 May 2007
Posts: 2454
Location: Hampshire, UK
|
|
|
|
| Probably because IEFBR14 does not access the dataset (it's not a file) so the relevant SMF records are not created. |
|
| Back to top |
|
|
steve-myers
Active Member
Joined: 30 Nov 2013
Posts: 917
Location: The Universe
|
|
|
|
At one level I agree with Mr. Clouston. I have no idea what SMF records TWS looks for. I think - mind you I do not have any expertise on this area - that an IEFBR14 step like this will create SMF data acceptable to TWS.
| Code: |
//... EXEC PGM=IEFBR14
//... DD DISP=(,CATLG),...,DSN=... |
I think cataloging the data set is a requirement. I do not think defining a tape data set using JCL like this will work; only defining a disk data set will work.
If TWS also wants to see type 15 records as Mr. Clouston thinks, then you will have to write a dummy IEBGENER like this, or an equivalent.
| Code: |
//... EXEC PGM=IEBGENER
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DUMMY
//SYSUT2 DD DISP=(,CATLG),...,DSN=...
//SYSIN DD DUMMY |
You will have to code appropriate DCB parameters on the SYSUT1 and SYSUT2 DD statements. If that doesn't work, then you will have to contact TWS support for additional guidance. |
|
| Back to top |
|
|
Apoorva
New User
Joined: 28 Jan 2020
Posts: 49
Location: India
|
|
|
|
| me00266 wrote: |
Hello all, maybe someone can help me with the following issue:
I'm testing the use of the ETT file triggering in order to put an application in the current plan whe a file is created; I've followed the manual instructions and first I've tested by creating the file thru TSO and it works fine;
By submiting thru the IBM util IEBGENER when it creates the file, it also works;
Finally, when creating the file thru the util IEFBR14, it does not trigger the application on the current PLAN.
Does anyone has an idea of the reason why ?
thank you in advance |
publib.boulder.ibm.com/tividd/td/TWS/SC32-1263-00/en_US/HTML/EQQR1MST93.htm
ETT looks for SMF records created by CLOSE action. Since IEFBR14 doesn't perform OPEN/CLOSE action against the allocated dataset, the trigger doesn't work. |
|
| Back to top |
|
|
me00266
New User
Joined: 29 May 2007
Posts: 2
Location: Portugal
|
|
|
|
| Apoorva wrote: |
| me00266 wrote: |
Hello all, maybe someone can help me with the following issue:
I'm testing the use of the ETT file triggering in order to put an application in the current plan whe a file is created; I've followed the manual instructions and first I've tested by creating the file thru TSO and it works fine;
By submiting thru the IBM util IEBGENER when it creates the file, it also works;
Finally, when creating the file thru the util IEFBR14, it does not trigger the application on the current PLAN.
Does anyone has an idea of the reason why ?
thank you in advance |
publib.boulder.ibm.com/tividd/td/TWS/SC32-1263-00/en_US/HTML/EQQR1MST93.htm
ETT looks for SMF records created by CLOSE action. Since IEFBR14 doesn't perform OPEN/CLOSE action against the allocated dataset, the trigger doesn't work. |
Yeah, you're right ! IEFBR14 does not create an OPEN/CLOSE action against SMF
Many thanks ! |
|
| Back to top |
|
|
|
|
