Okay, I've dumped the SMF26 records from this development system, to be called
X2. From looking at these four SMF26 fields that Barry referred to, some of the
records have system X1 listed in all four fields, even though the SID field
says X2. Since we use zOSEM here I wonder if behind the
Mark Reganwrote:
Okay, I've dumped the SMF26 records from this development system, to be called
X2. From looking at these four SMF26 fields that Barry referred to, some of
the records have system X1 listed in all four fields, even though the SID
field says X2. Since we use zOSEM here I wonder
The SID (SYSTEM ID) of the TYPE 26 RECORD is the system on which the job PURGED,
and in a JES2 MAS, whichever system happened to have the checkpoint record
(I think that is what it is called) will write the purge record.
A very common experience, to find the purge record on a system different
We have a JES2Plex/JES2MAS that has three LPARS in it, two prod and one dev.
Later this year the development LPAR will be moving to a different sysplex that
only supports development work. What I want to find out is if anyone submits
jobs from this dev LPAR, but either codes a Class that is
SMF Type 30's are cut on the machine where the job actually runs. There is a
userid and class that that might let you infer where it was submitted from.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Mark Regan
Sent:
TYPE26 records contain four SYSTEM fields,
SYSREAD $EBCDIC4. /*SMF26RID*/
SYSCVRT $EBCDIC4. /*SMF26CID*/
SYSEXEC $EBCDIC4. /*SMF26XID*/
SYSOUTP $EBCDIC4. /*SMF26OID*/
And Job Class
SMF26WJC $EBCDIC8. /*JOB*CLASS*/
But only Throughput Manager
SMF will not help you here...
The key here is the scope of the JES MAS. As long as there is a separate MAS,
SYSAFF will not work. SMF will not help you here...
You *might* consider a single sysplex and the use of WLM Scheduling
environments to control the location of job execution.
There are
Actually what we are trying to do is find out what current jobs are being
submitted from the dev LPAR that get executed on the prod LPAR and vice versa.
We know that once we move this dev LPAR to a different sysplex and JES2MAS, our
users will no be longer be able to do this any longer and will
In the absence of help from SMF, I suggest a scan of SYSLOG. HASP100 shows
the system where a job was submitted. HASP373 shows where the job
executed. Should not be too hard to write a Rexx to get the info you need.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team
As Barry stated, look at the SMF Type26
-
-teD
-
Original Message
From: Mark Regan
Sent: Wednesday, June 25, 2014 21:49
To: IBM-MAIN@LISTSERV.UA.EDU
Reply To: IBM Mainframe Discussion List
Subject: Re: SMF record that records a job being submitted from one system but
executing on a different
10 matches
Mail list logo