Ruth,

It is possible that the WTO operation in the exit is failing - maybe due to a 
overlay in the exit working storage or some other "bad parameter list" error. I 
would check any code in the exit that varies with userid/jobname values and 
also check the bounds of any other variables around the WTO parmlist in the 
working storage.

It would help if you posted the source code as some bright spark on here might 
see something that you missed.



Rob Scott
Rocket Software, Inc
275 Grove Street
Newton, MA 02466
617-614-2305
[EMAIL PROTECTED]


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of 
O'Connor, Ruth
Sent: 18 January 2008 15:45
To: IBM-MAIN@BAMA.UA.EDU
Subject: IEFACTRT exit

Hello

We have an intermittent problem with IEFACTRT and are wondering if anyone else 
has ever seen this phenomenon. We're running z/OS 1.7 with Top Secret 9.0 but 
the problem goes back at least several years and software levels.

Like many shops, we use the exit to write WTO messages at the end of each batch 
job step. Every once in a while a user reports that the messages are no longer 
being written for his batch jobs, even though the messages were being produced 
for that user the previous day (or previous
hour) and the messages are still being produced for other users' jobs.
The messages don't come back for that user's batch jobs until the next time we 
IPL the LPAR.

We have never been able to figure out what causes this problem. The type 30, 
subtype 4, smf records are still being cut for the jobs without the messages. I 
have looked through the exit code without finding anything useful. We're 
wondering if something prevents the IEFACTRT exit from being called for certain 
users.

This week the problem has been reported in our applications development LPAR. 
For at least 3 userids (or ACIDs in Top Secret terminology) the messages 
stopped appearing early Monday morning. There is nothing in logrec at that time 
and I don't see anything strange in syslog, either.

A search of the archives turned up one thread about a similar problem at a DR 
site but there didn't appear to be any resolution.

Thanks in advance for any suggestions.

Ruth O'Connor
Senior Systems Software Specialist
Boston University

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at 
http://bama.ua.edu/archives/ibm-main.html

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to