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)
 
 NC0000000 ADCD     11291 16:08:00.75 SFORD    00000290  D A,L
 MR0000000 ADCD     11291 16:08:00.76 SFORD    00000090  IEE114I 16.08.00 2011.2
 LR                                        618 00000090   JOBS     M/S    TS USE
 LR                                        618 00000090  00002    00012    00001
 DR                                        618 00000090   LLA      LLA      LLA
 DR                                        618 00000090   VLF      VLF      VLF
 DR                                        618 00000090   DLF      DLF      DLF
 DR                                        618 00000090   INETD4   STEP1    OMVS
 DR                                        618 00000090   SDSF     SDSF     SDSF
 DR                                        618 00000090   TN3270   TN3270   TN32
 DR                                        618 00000090   PORTMAP  PORTMAP  PMAP
 ER                                        618 00000090  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 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 *
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

Reply via email to