Re: DB2 - DSNL message not showing in syslog

2021-10-18 Thread Steve Horein
You've checked MPF?
If using NetView for your base automation, MRT (Message Revision Table) can
change MPF settings.
https://www.ibm.com/docs/en/z-netview/6.3.0?topic=npaf-message-revision-table

I always liked this diagram to keep me on track:
https://docplayer.net/docs-images/64/51620684/images/22-0.jpg


On Mon, Oct 18, 2021 at 11:18 AM J Ellis <
020d5fbe36e0-dmarc-requ...@listserv.ua.edu> wrote:

> I have been asked by the AO folks and DB2 why messages issued in their
> data sharing environment only show up in the STC log of the DB**MSTR.
> the command and output are below, for all the non-sharing DB2's this
> message goes into syslog.
> we have done diligence looking for routing codes / AO rules, etc and not
> finding anything.
> we have looked in the DB2 message manuals, again with no luck.
> this may be and probably is, something we have missed in relation to data
> sharing environments, just not finding it.
>
> Command = #dbc4dis ddf
>
> SYSC:
> RESPONSE=SYSC
>  DSNL080I  #DBC4 DSNLTDDF DISPLAY DDF REPORT FOLLOWS:
>  DSNL081I STATUS=STARTD
>  DSNL082I LOCATION   LUNAMEGENERICLU
>  DSNL083I DB2CGRPLIBNET.DBC4   -NONE
>  DSNL084I TCPPORT=5446  SECPORT=5448  RESPORT=33007 IPNAME=-NONE
>  DSNL085I IPADDR=::xx.xx.xx.xx
>  DSNL086I SQLDOMAIN=db2c.xx.com
>  DSNL086I RESYNC DOMAIN=dbc4.xx..com
>  DSNL087I ALIAS  PORT  SECPORT STATUS
>  DSNL088I DB2C   5002  0   STARTD
>  DSNL089I MEMBER IPADDR=::xx.xx.xx.xx
>  DSNL105I CURRENT DDF OPTIONS ARE:
>  DSNL106I PKGREL = COMMIT
>  DSNL106I SESSIDLE = 001440
>  DSNL099I DSNLTDDF DISPLAY DDF REPORT COMPLETE
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


DB2 - DSNL message not showing in syslog

2021-10-18 Thread J Ellis
I have been asked by the AO folks and DB2 why messages issued in their data 
sharing environment only show up in the STC log of the DB**MSTR.
the command and output are below, for all the non-sharing DB2's this message 
goes into syslog.
we have done diligence looking for routing codes / AO rules, etc and not 
finding anything.
we have looked in the DB2 message manuals, again with no luck.
this may be and probably is, something we have missed in relation to data 
sharing environments, just not finding it.

Command = #dbc4dis ddf

SYSC: 
RESPONSE=SYSC  
 DSNL080I  #DBC4 DSNLTDDF DISPLAY DDF REPORT FOLLOWS:  
 DSNL081I STATUS=STARTD
 DSNL082I LOCATION   LUNAMEGENERICLU   
 DSNL083I DB2CGRPLIBNET.DBC4   -NONE   
 DSNL084I TCPPORT=5446  SECPORT=5448  RESPORT=33007 IPNAME=-NONE   
 DSNL085I IPADDR=::xx.xx.xx.xx
 DSNL086I SQLDOMAIN=db2c.xx.com  
 DSNL086I RESYNC DOMAIN=dbc4.xx..com  
 DSNL087I ALIAS  PORT  SECPORT STATUS  
 DSNL088I DB2C   5002  0   STARTD  
 DSNL089I MEMBER IPADDR=::xx.xx.xx.xx
 DSNL105I CURRENT DDF OPTIONS ARE: 
 DSNL106I PKGREL = COMMIT  
 DSNL106I SESSIDLE = 001440
 DSNL099I DSNLTDDF DISPLAY DDF REPORT COMPLETE

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN