> Subject: > > IEAMBDLG and SYSLOGD > > Sent by: > > IBM Mainframe Discussion List <[email protected]> > > Why does IEAMBDLG skip OPERLOG entries created by USS? > > SYS1.SAMPLIB(IEAMDBLG) > - - - - - - - - - - - - - - - - - - 487 Line(s) notDisplayed > 046010 * $L2=DCRA990 HBB7730 050525 PDKX: Skip MDB if MDB has > been sent * > 046020 * from USS * > - - - - - - - - - - - - - - - - - - - 56 Line(s) notDisplayed > 050300 * NOTG (a) Add support for USS Msg Integration to write @L2A* > * Messages to operlog. @L2A* > - - - - - - - - - - - - - - - - - - 774 Line(s) notDisplayed > 124310 TM MDBCMSC2,MDBCOPON Has MDB been sent from USS? @L2A > 124311 BO COPYLOOP skip MDB if it is @L2A > - - - - - - - - - - - - - - - - - - 1411 Line(s) notDisplayed > > We are sending selected SYSLOGD records to /dev/operlog and SDSF > displays the records just fine. However, IEAMDBLG does not copy > them. I commented the two instructions and the records are copied > fine. Is there some form of USS records that may cause a problem?
I don't know. The programmer (PDKX) identified by the change activity flagging is no longer in the IBM internal directory. It might be this person: http://www.linkedin.com/pub/akash-desai/5/681/683 Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
