IBM Support

II12021: READ FIRST: SYSLOGD HOWTO TCPIPINFO

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • ****************************************************************
    *                                                              *
    *   Information in this APAR is no longer being updated.       *
    *   Please use the following URL for the most current          *
    *   information:                                               *
    *                                                              *
      http://www.ibm.com/support/docview.wss?rs=852&uid=swg21316946
    *                                                              *
    ****************************************************************
                            SYSLOGD HOWTO
    
    In addition to the information provided below, here are some
    publications, including RED BOOKS, which cover SYSLOGD topics.
    
      Website for Red books:    http://www.redbooks.ibm.com
      Website for various pubs in OS/390 Bookshelves:
         http://publib.boulder.ibm.com:80/cgi-bin/bookmgr/SEARCH?
    
    Red Book Accessing OS/390 OE MVS from the Internet SG24-4721
    (p.137 contains example how to periodically cleanout logs
     without stopping syslogd)
    
    Red Book: OS/390 eNetwork Communications Server V2R5 TCP/IP
            Implementation Guide Volume 2: OpenEdition Applications,
            SG24-5229-01
    (Covers using AUTOLOG for SYSLOGD.  Contains sample procedure
     that specifies the config file name to be used)
                *              *             *
    Red book:  OS/390 eNetwork Communications Server V2R7 TCP/IP
               Implementation Guide Volume 2: UNIX Applications,
               SG24-5228-01
    Red Book:  IBM Communications Server for OS/390 V2R10 TCP/IP
               Implementation Guide: Volume 2: UNIX Applications,
               SG24-5228-02
    --------------------------------------------------------
    Bookshelf: OS/390 V2R8.0 SecureWay Communications
           Server Unlicensed BookShelf
    
    Title: OS/390 V2R8.0 SecureWay CS IP Configuration
    Document Number: SC31-8513-03
    Book Path: /home/publib/epubs/book/f1af7020.boo
               *                *                *
    Bookshelf: OS/390 V2R10.0 IBM COMMUNICATIONS
           Server Unlicensed BookShelf
    
    Title: OS/390 V2R10.0 IBM CS IP Configuration Guide
    Document Number: SC31-8725-00
    Book Path: /home/publib/epubs/book/f1af7030.boo
                   and
    Title: OS/390 V2R10.0 IBM CS IP Configuration Reference
    Document Number: SC31-8726-00
    Book Path: /home/publib/epubs/book/f1af4000.boo
               *               *                  *
    -------------------------------
    Setup requirements for syslogd:
    -------------------------------
    
    1) Ensure that your BPXPRMxx parmlib member contains a
       definition for AF_UNIX filesystem.
    
       The following is a sample definition from the OE Planning
       Guide.
    
          ...
          FILESYSTYPE TYPE(UDS) ENTRYPOINT(BPXTUINT)
          NETWORK DOMAINNAME(AF_UNIX)
                  DOMAINNUMBER(1)
                  MAXSOCKETS(64)
                  TYPE(UDS)
          ...
       An IPL is required to pick up this change to BPXPRMxx.
    2) Ensure /dev/console and /dev/log are properly defined.
       issue 'ls -l /dev/console' from the OMVS shell
       Output should be:
       c-w--w--w-   1 IBMUSER  SYS1  9,  0 Jul  2 17:18 /dev/console
       If the /dev/console file is missing, issue:
         /usr/sbin/mknod /dev/console c 9 0
       If the file permissions are incorrect, issue:
         /bin/chmod 222 /dev/console
    
       issuing 'ls -l /dev/log' from OMVS shell should show:
       c-w--w--w-   1 IBMUSER  SYS1     6,  0 Jul  2 17:18 /dev/log
       If the /dev/log file is missing, issue:
         /usr/sbin/mknod /dev/log c 6 0
       If the file permissions are incorrect, issue:
         /bin/chmod 222 /dev/log
    
       For more info see OE Planning Guide (SC28-1890-01, pages
       206-209), OE MVS Command Reference (SC28-1892-01), and
       OS/390 UNIX System Services Planning (SC28-1890-06).
    
     Note: if /dev/console is defined as a regular hfs file, syslog
           messages go to this file when syslogd is not active.
    
    3) Create the syslog daemon configuration file with permissions
       600
    
       The following example will log all messages in
       /tmp/syslog.log and also log all daemon messages in
       /tmp/daemon.trace
    
    /etc/syslog.conf
    # if you change this file, you tell syslogd to reprocess it with
    #  kill -s SIGHUP pid
    # syslogd's pid can be found in /etc/syslogd.pid
    #
    # log all messages to file /tmp/syslogd.log
    *.*         /tmp/syslogd.log
    #
    # log daemon messages to file /tmp/daemon.trace
    #  FTPD uses the daemon facility.  Specifying 'debug' will get
    #  FTP trace entries recorded when FTP's trace is active
    daemon.debug /tmp/daemon.trace
    
    4) Create empty syslog output file(s) with permissions 666
       (/tmp/syslogd.log and /tmp/daemon.trace in our example).
    
        Eg.  touch /tmp/daemon.trace
             chmod 666 /tmp/daemon.trace
    NOTE:  If syslogd is configured to dynamically
           generate files, then these files are
           created with permissions of 600.  Only
           the Superuser can read these files.  This
           is a standard UNIX security measure to prevent
           ordinary users from reading sensative information
           in the logs files
    
    5) Assign port 514 to syslogd in the tcpip profile and/or
       /etc/services as a UDP service.
       See IP Configuration (appendix) for more information.
    
    
    -----------------
    To start syslogd:
    -----------------
    SYSLOGD should be started before TCP/IP to capture all messages
    To run syslogd as a started task:
    
    a) create SYSLOGD PROC to start up the syslog daemon
        USER.PROCLIB(SYSLOGD)
         //SYSLOGD PROC
         //*********************************************************
         //SYSLOGD EXEC PGM=SYSLOGD,REGION=30M,TIME=NOLIMIT,
         //      PARM='POSIX(ON) ALL31(ON)/ '
         //SYSPRINT DD SYSOUT=*
         //SYSIN    DD DUMMY
         //SYSERR   DD SYSOUT=*
         //SYSOUT   DD SYSOUT=*
         //CEEDUMP  DD SYSOUT=*
    
    b) Setup the RACF entries for SYSLOGD
    
        ADDUSER SYSLOGD OMVS(UID(0) HOME('/') PROGRAM('/bin/sh'))
        RDEFINE STARTED SYSLOGD.* STDATA( USER(SYSLOGD))
    
    
     Alternatively, you can start syslog daemon from the OE shell.
        It must be started from a superuser.
    
        Example:
       # TOP OF /etc/rc FILE
       # Start the SYSLOGD daemon
       #Lines starting with a hash (#) are comments
       # THIS MUST BE THE FIRST TASK STARTED (1st in /etc/rc)
       export _BPX_JOBNAME='SYSLOGD'
       export _CEE_RUNOPTS='ALL31(ON)'
       /usr/sbin/syslogd -f /etc/syslog.conf &
    
    
    
        /d a,l   ==> shows SYSLOGD
        /c SYSLOGD  will work
    
    
    Note: You cannot successfully start syslogd from a userid that
          is not a superuser.  You will get error messages on the
          operator's console, and not in the OE shell.Any subsequent
          messages sent to syslog will appear on the operator's
          console.
    
    
                       ----------------------
                       FTP MSG/TRACE SYMPTOMS
                       ----------------------
    
    Symptom                  Possible Cause
    -------                  --------------
    all msgs to console      syslogd not active
                               note: /dev/console must be defined
                                     as char special file with
                                     major=9
    E-msgs to console        syslogd active but no /etc/syslog.conf
                              file
    no FTP msgs in           syslogd not active & /dev/console not
     /tmp/daemon.trace        defined
      or on                      or
      operator's console     syslogd active but no daemon.x
                              statements in /etc/syslog.conf
                                or
                            syslogd active, daemon.x stmts exist but
                              specified output file (eg.
                              /tmp/daemon.trace) does not exist
                              or did not exist when syslogd
                              was started.
                         1) ensure /tmp/daemon.trace exists
                         2) Issue 'kill -1 <syslog_pid>'
                             to refresh syslogd configuration
                             (syslog_pid is in /etc/syslog.pid).
                             Msgs/trace from ftpd & servers
                             already started will appear in
                             /tmp/daemon.trace from this point on.
                             or
                             cancel and restart syslogd.
    -----------------------
    
    What appears on the operator's console if you start syslogd from
    the OE shell of a userid that is not a superuser:
    
    ICH408I USER(USER32  ) GROUP(SYS1    ) NAME(TSO USERID USER32  )
      /dev/log CL(FSOBJ   ) FID(01E2D4E2E5D3F100100B000000000003)
      INSUFFICIENT AUTHORITY TO UNLINK
      ACCESS INTENT(-W-)  ACCESS ALLOWED(GROUP R-X)
    IOS000I 050F,D2,WRI,47,0200,,04460003,CATLOG,CATALOG , 830
    80020000114643000000008B3900000521005728BD3C000000004CE000044603
    IEC331I 028-002(000C0010),USER326 ,STEP1   ,IOEA,IGG0CLEG
    IEC332I CLX0,CLF0,CLAT,CLEH,ALTR,CLKH,PUPD
    IEC333I P016(000),03,SYSENV.MASTCAT,SYS1.TCPPARMS
    ICH408I USER(USER32  ) GROUP(SYS1    ) NAME(TSO USERID USER32  )
     /dev/console CL(FSOBJ   ) FID(01E2D4E2E5D3F100100B0005D46E0000)
     INSUFFICIENT AUTHORITY TO OPEN
     ACCESS INTENT(-W-)  ACCESS ALLOWED(GROUP R--)
    ICH408I USER(USER32  ) GROUP(SYS1    ) NAME(TSO USERID USER32  )
     /dev/log CL(FSOBJ   ) FID(01E2D4E2E5D3F100100B000000000003)
     INSUFFICIENT AUTHORITY TO UNLINK
     ACCESS INTENT(-W-)  ACCESS ALLOWED(GROUP R-X)
    .
    NOTE: For z/OS Commserver hints and tips go to:
    http://www.ibm.com/software/network/commserver/support/
    
    ----------------------------------------------------------------
    
      - To the customer: if you have suggestions to improve this
        informational APAR, please submit a problem record to
           TCPIP level 2 using component ID 5655HAL00.
    
                     WE APPRECIATE YOUR SUGGESTIONS.
    ----------------------------------------------------------------
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

  • information purposes only
    

APAR Information

  • APAR number

    II12021

  • Reported component name

    PA LIB INFO ITE

  • Reported component ID

    INFOPALIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1999-08-22

  • Closed date

    1999-12-09

  • Last modified date

    2009-08-24

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG32M","label":"APARs - VSE\/ESA environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]

Document Information

Modified date:
24 August 2009