Re: z/OS SYSLOG observation / thought
The ASID is available at the point just before the message is sent to the console. Our SyzMPF/z product gets the messages before they go to hardcopy (you can have SyzMPF/z keep them from getting there if you want), and one of the fields that I have access to (and we allow you to use in the scripts that are automatically processed for the messages) is the ASID of the issuer. It would not be that difficult to just update the outgoing message and pop in the ASID, especially if it was destined for a specific spot in the message. The only messages that wouldn't get the ASID would be those that are issued on behalf of something else, so they would get the ASID of the actual issuer of the message. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: z/OS SYSLOG observation / thought
We don't have that product. And we basically have no money for any new product. But we do have CA-OPS/MVS. Maybe I can pervert it to do that. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Brian Westerman Sent: Wednesday, October 19, 2011 2:38 AM To: IBM-MAIN@bama.ua.edu Subject: Re: z/OS SYSLOG observation / thought The ASID is available at the point just before the message is sent to the console. Our SyzMPF/z product gets the messages before they go to hardcopy (you can have SyzMPF/z keep them from getting there if you want), and one of the fields that I have access to (and we allow you to use in the scripts that are automatically processed for the messages) is the ASID of the issuer. It would not be that difficult to just update the outgoing message and pop in the ASID, especially if it was destined for a specific spot in the message. The only messages that wouldn't get the ASID would be those that are issued on behalf of something else, so they would get the ASID of the actual issuer of the message. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: z/OS SYSLOG observation / thought
John, Yeah, I have been there, what about MPF..I know that was the original point in z/OS where Netview got its messages. Scott J Ford Software Engineer http://www.identityforge.com From: McKown, John john.mck...@healthmarkets.com To: IBM-MAIN@bama.ua.edu Sent: Wednesday, October 19, 2011 8:20 AM Subject: Re: z/OS SYSLOG observation / thought We don't have that product. And we basically have no money for any new product. But we do have CA-OPS/MVS. Maybe I can pervert it to do that. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Brian Westerman Sent: Wednesday, October 19, 2011 2:38 AM To: IBM-MAIN@bama.ua.edu Subject: Re: z/OS SYSLOG observation / thought The ASID is available at the point just before the message is sent to the console. Our SyzMPF/z product gets the messages before they go to hardcopy (you can have SyzMPF/z keep them from getting there if you want), and one of the fields that I have access to (and we allow you to use in the scripts that are automatically processed for the messages) is the ASID of the issuer. It would not be that difficult to just update the outgoing message and pop in the ASID, especially if it was destined for a specific spot in the message. The only messages that wouldn't get the ASID would be those that are issued on behalf of something else, so they would get the ASID of the actual issuer of the message. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: z/OS SYSLOG observation / thought
Yes, I could do that, I suppose. I'm a bit lazy. Also, my manager dislikes non-vendor stuff because who's going to support it if you leave? Which is now hilarious to me. Why? Because we are now running unsupported software and we're having problems with it. Since we don't have source code, being a vendor product, we can't fix it at all. So in one case I'm converting about 2000 VSAM datasets. The product runs well on 1.10, but fails on 1.12, so 1.12 conversion is delayed. In another case, a Windows product is producing graphs and they are wrong. We have nobody here who knows the product and no support. Why is it in z/OS Tech Services domain? I don't know. Our response to the users of the graphs: Too bad. We don't know the product. We can't get support or training because it's not in the budget. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets® 9151 Boulevard 26 . N. Richland Hills . TX 76010 (817) 255-3225 phone . john.mck...@healthmarkets.com . www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets® is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company®, Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Scott Ford Sent: Wednesday, October 19, 2011 8:25 AM To: IBM-MAIN@bama.ua.edu Subject: Re: z/OS SYSLOG observation / thought John, Yeah, I have been there, what about MPF..I know that was the original point in z/OS where Netview got its messages. Scott J Ford Software Engineer http://www.identityforge.com From: McKown, John john.mck...@healthmarkets.com To: IBM-MAIN@bama.ua.edu Sent: Wednesday, October 19, 2011 8:20 AM Subject: Re: z/OS SYSLOG observation / thought We don't have that product. And we basically have no money for any new product. But we do have CA-OPS/MVS. Maybe I can pervert it to do that. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Brian Westerman Sent: Wednesday, October 19, 2011 2:38 AM To: IBM-MAIN@bama.ua.edu Subject: Re: z/OS SYSLOG observation / thought The ASID is available at the point just before the message is sent to the console. Our SyzMPF/z product gets the messages before they go to hardcopy (you can have SyzMPF/z keep them from getting there if you want), and one of the fields that I have access to (and we allow you to use in the scripts that are automatically processed for the messages) is the ASID of the issuer. It would not be that difficult to just update the outgoing message and pop in the ASID, especially if it was destined for a specific spot in the message. The only messages that wouldn't get the ASID would be those that are issued on behalf of something else, so they would get the ASID of the actual issuer of the message. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
z/OS SYSLOG observation / thought
Columns 41 through 48 in the z/OS SYSLOG (formatted with a 4 digit year in columns 21-27) have various information in them. For many messages, it is the JES assigned number such as JOB12345. For a commands and command responses it appears to the be console name or for a MLWTO response the continuation number. For an S line it is blank because that means the line is a continuation of the above output line (N or S). But, for WTOs issued by started tasks which are running under the MSTR subsystem, it is blank instead of having the JES jobid (N lines, that is). So there's no way to know which task issued the message. I guess that most of the time, this doesn't really matter. But I was thinking, perhaps poorly, that where the JES jobid would be, wouldn't it be useful to have the ASID of the address space? Perhaps formatted as ASID where is the hex value of the ASID? I am wondering if one of the WTO exits could be used to implement this. I guess that I'll look and see. John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: z/OS SYSLOG observation / thought
On 18 October 2011 13:29, McKown, John john.mck...@healthmarkets.com wrote: Columns 41 through 48 in the z/OS SYSLOG (formatted with a 4 digit year in columns 21-27) have various information in them. For many messages, it is the JES assigned number such as JOB12345. For a commands and command responses it appears to the be console name or for a MLWTO response the continuation number. For an S line it is blank because that means the line is a continuation of the above output line (N or S). But, for WTOs issued by started tasks which are running under the MSTR subsystem, it is blank instead of having the JES jobid (N lines, that is). So there's no way to know which task issued the message. I guess that most of the time, this doesn't really matter. But I was thinking, perhaps poorly, that where the JES jobid would be, wouldn't it be useful to have the ASID of the address space? Perhaps formatted as ASID where is the hex value of the ASID? I am wondering if one of the WTO exits could be used to implement this. I guess that I'll look and see. Some years ago I looked at putting the UNIX PID in there. It's very easy to retrieve and insert; the problem lies in where to squeeze it in in a way that won't break other programs that know what log lines contain, and that makes it unambiguous what the new field means. Had IBM not used large PIDs (or rather, not encoded two items in each PID), it would've been easy. Tony H. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: z/OS SYSLOG observation / thought
John: I think, if my old cobwebby gray matter serves me here, we did that with the Message automation table in Netview.. Each message was tagged , so we knew who issued it. But they also came through the NetVSSI, which might have tagged them prior to hand off to the message table. BTW also on commands from SDSF nothing is there , he is my 1.10 test system (also have 1.11 and 1.12) NC000 ADCD 11291 16:08:00.75 SFORD 0290 D A,L MR000 ADCD 11291 16:08:00.76 SFORD 0090 IEE114I 16.08.00 2011.2 LR 618 0090 JOBS M/S TS USE LR 618 0090 2 00012 1 DR 618 0090 LLA LLA LLA DR 618 0090 VLF VLF VLF DR 618 0090 DLF DLF DLF DR 618 0090 INETD4 STEP1 OMVS DR 618 0090 SDSF SDSF SDSF DR 618 0090 TN3270 TN3270 TN32 DR 618 0090 PORTMAP PORTMAP PMAP ER 618 0090 SFORD IN Scott J Ford Software Engineer http://www.identityforge.com From: McKown, John john.mck...@healthmarkets.com To: IBM-MAIN@bama.ua.edu Sent: Tuesday, October 18, 2011 1:29 PM Subject: z/OS SYSLOG observation / thought Columns 41 through 48 in the z/OS SYSLOG (formatted with a 4 digit year in columns 21-27) have various information in them. For many messages, it is the JES assigned number such as JOB12345. For a commands and command responses it appears to the be console name or for a MLWTO response the continuation number. For an S line it is blank because that means the line is a continuation of the above output line (N or S). But, for WTOs issued by started tasks which are running under the MSTR subsystem, it is blank instead of having the JES jobid (N lines, that is). So there's no way to know which task issued the message. I guess that most of the time, this doesn't really matter. But I was thinking, perhaps poorly, that where the JES jobid would be, wouldn't it be useful to have the ASID of the address space? Perhaps formatted as ASID where is the hex value of the ASID? I am wondering if one of the WTO exits could be used to implement this. I guess that I'll look and see. John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
