McKown, John
2011-10-18 17:31:35 UTC
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 ASIDhhhh where hhhh 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 *
***@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 ***@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
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 ASIDhhhh where hhhh 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 *
***@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 ***@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html