Thanks John.

I spend an hour or so to make sure my old eyes are not cheating me ;-) strange 
that I have'nt found it myself as I googled for it...



ITschak

בתאריך 27 בספט 2016 15:00,‏ "John McKown" <[email protected]> כתב:
> Damn, I hate it when I do this. I then found:
> 
> http://www-01.ibm.com/support/docview.wss?uid=isg1PI47467
> 
> 
>    -
> 
>    ****************************************************************
>    * USERS AFFECTED:                                              *
>    * All users of the IBM Communications Server for z/OS Version  *
>    * 2 Release 1 IP: syslog daemon                                *
>    ****************************************************************
>    * PROBLEM DESCRIPTION:                                         *
>    * The syslog daemon configuration file name in the EZBSYSLOGD  *
>    * name/token pair is truncated by 1 character                  *
>    ****************************************************************
>    * RECOMMENDATION:                                              *
>    * Apply the PTF                                                *
>    ****************************************************************
>    During initialization, the syslog daemon creates a name/token
>    pair named EZBSYSLOGD.  The information saved in the name/token
>    pair contains the configuration file name.  The last character
>    of the name was overlaid with 1-byte of x'00'.
> 
> 
> Problem conclusion
> 
>    -
> 
>    The syslog daemon has been corrected to save the entire
>    configuration file name in the EZBSYSLOGD name/token pair.
> 
> 
> 
> On Tue, Sep 27, 2016 at 6:57 AM, John McKown <[email protected]>
> wrote:
> 
> > On Tue, Sep 27, 2016 at 3:34 AM, Itschak Mugzach <
> > [email protected]> wrote:
> >
> >> I am looking at the name/token pair of syslogd and the file name (hfs) is
> >> missing the last character. The value of the last character is binary
> >> zero.
> >>
> >> Is this a known issue?
> >>
> >> *| **Itschak Mugzach | Director | SecuriTeam Software | *
> >>
> >>
> > ​I'm not sure, but could this be the "normal" 0x00 that terminates a C
> > language "string"? I'm looking at:
> > https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/
> > com.ibm.zos.v2r1.halx001/syslogdntpairecsasm.htm
> > At offset 56, the associated length says: "1025 (max 1024 + 1)" which
> > makes me think that the 0x00 is correct. Unless, of course, you have really
> > verified that the file name on disk is one character longer than the file
> > name in this field. In which case, my apologies for intruding. I'm on z/OS
> > 1.12, and so can't easily test this.​
> >
> >
> > --
> > Heisenberg may have been here.
> >
> > Unicode: http://xkcd.com/1726/
> >
> > Maranatha! <><
> > John McKown
> >
> 
> 
> 
> --
> Heisenberg may have been here.
> 
> Unicode: http://xkcd.com/1726/
> 
> Maranatha! <><
> John McKown
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to