A new thread, called "What subsystem ate my message?" opened up and I
posted the following:
After setting the SLIP trap, on the first go round I
didn't restrict GTF to only collecting SLIP entries (so I had lots of SVC's
etc.).
On the second go round, I had to clean up the directory in IPCS before I could
look at the trace (same dataset name, different allocation). Here is the
important part from IBM:
This SLIP trap generates two entries per one called subsystem: before
and after the call. Since a subsystem has ONE possibility to suppress a
essage - via 00000004 or 0000000C in the SSOBRETN field in the SSOB
control block - it is what you have to check in all even records;
specifically, you will be interested to check the following line in
even records
001D E2E2D6C2 001C0009 7E873990 00000000 ! SSOB....=g...... !
========
If you find one or more subsystems with 4 or C in the SSOBRETN field,
then you can identify them by using the SSIB which follows SSOB.
The real culprit (in my case), was CA-Opera (the operations automation
package). It seems I was missing some PTFs. I have since applied all of the
outstanding fixes to CA-Opera, and all works well now.
Thanks for all of the help.
----------------------------------------------------------------------
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
