Watch for event function was created in V5R3 as part of some trace
commands (STRTRC, TRCINT, TRCCNN, TRCTCPAPP, STRCMNTRC). The purpose then
was to automatically stop the traces when the watched for event occurred.
The design then was to create a single job "listening" for those events and
also taking care of the WCHTIMO and TRCPGMITV parameters. This job would
also call the user exit program (TRCPGM parameter) and end the trace. You
can see more info about the watch for trace event capability at:
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/rzaku/rzakuadvtrc.htm
In V5R4 watch for event function was enhanced. STRWCH, ENDWCH and WRKWCH
commands, and QSCSWCH and QSCEWCH APIs were created. This new watch
functionality has a notification capability (instead of the auto-stop
capability). The one to one relationship between a watch session and a job
was kept. You can read more at:
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/rzahb/rzahb_eventfunction.htm
Service Monitor was born in V5R4 too. And Service Monitor uses watches
under the covers. Service Monitor starts a watch session for every policy
defined by IBM developers and support representatives.
By the way, I forgot to mention in my previous post that Service Monitor
also ends and restarts all the watch sessions when an updated policy file
is downloaded from IBM. This can occur when Service Agent connects to IBM
or when a Service Monitor PTF is applied.
¡Saludos! / Regards!
Sergio Toscano Lomeli
midrange-l-reques
t@xxxxxxxxxxxx
Sent by: To
midrange-l-bounce midrange-l@xxxxxxxxxxxx
s@xxxxxxxxxxxx cc
Subject
30/07/2007 08:18 MIDRANGE-L Digest, Vol 6, Issue
1476
Please respond to
midrange-l@midran
ge.com
Send MIDRANGE-L mailing list submissions to
midrange-l@xxxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.midrange.com/mailman/listinfo/midrange-l
or, via email, send a message with subject or body 'help' to
midrange-l-request@xxxxxxxxxxxx
You can reach the person managing the list at
midrange-l-owner@xxxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of MIDRANGE-L digest..."
*** NOTE: When replying to this digest message, PLEASE remove all text
unrelated to your reply and change the subject line so it is meaningful.
Today's Topics:
1. SQL Gurus Wanted (Jon Paris)
2. AW: SQL Gurus Wanted (BirgittaHauser)
3. RE: SQL Gurus Wanted (Joe Pluta)
4. 3479 + Symbol LS3070 wireless scanner - Replacement needed
(Don Cavaiani)
5. Re: SRVMON Jobs - New Twist? (ChadB@xxxxxxxxxxxxxxxxxxxx)
6. View Contents Of Tape (Ryan Hunt)
7. Re: View Contents Of Tape (Ryan Hunt)
----------------------------------------------------------------------
message: 1
date: Mon, 30 Jul 2007 00:43:17 -0400
from: "Jon Paris" <Jon.Paris@xxxxxxxxxxxxxx>
subject: SQL Gurus Wanted
Can any of the SQL gurus out there suggest the magic incantation's) that
will achieve the following.
Tables A and B have a number of common columns.
If the keys in A and B match, update columns in A with the values from B.
If there is a row in B that does not exist in A, then insert a new row
based
on B.
It is late on Sunday (actually early Monday) and my brain has seized.
Jon Paris
Partner400
www.Partner400.com
------------------------------
message: 2
date: Mon, 30 Jul 2007 07:13:10 +0200
from: "BirgittaHauser" <Hauser@xxxxxxxxxxxxxxx>
subject: AW: SQL Gurus Wanted
Hi Jon,
1. Update from an other table:
UPDATE TableA a
SET (a.Field1,
a.Field2, ... ,
a.FieldN) = (SELECT b.Field1, b.Field2, ... , FieldN
FROM TableB b
WHERE a.Key1 = b.Key1
and a.Key2 = b.Key2)
WHERE EXISTS (SELECT 1 FROM TableB c
WHERE a.Key1 = c.Key2
a.Key1 = c.Key2)
2. Insert from an other table
Insert into TableB
(Field1, Field2, ... , FieldN)
Select Field1, Field2, ... , FieldN
from TableA a exception join TableB b
on a.Key1 = b.Key1
and a.Key2 = b.Key2
These SQL statements are not checked, because I currently have no access to
an iSeries.
Mit freundlichen Gr??en / Best regards
Birgitta Hauser
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
-----Urspr?ngliche Nachricht-----
Von: midrange-l-bounces+hauser=sss-software.de@xxxxxxxxxxxx
[mailto:midrange-l-bounces+hauser=sss-software.de@xxxxxxxxxxxx] Im Auftrag
von Jon Paris
Gesendet: Monday, July 30, 2007 06:43
An: midrange-l@xxxxxxxxxxxx
Betreff: SQL Gurus Wanted
Can any of the SQL gurus out there suggest the magic incantation's) that
will achieve the following.
Tables A and B have a number of common columns.
If the keys in A and B match, update columns in A with the values from B.
If there is a row in B that does not exist in A, then insert a new row
based
on B.
It is late on Sunday (actually early Monday) and my brain has seized.
Jon Paris
Partner400
www.Partner400.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
------------------------------
message: 3
date: Mon, 30 Jul 2007 00:31:28 -0500
from: "Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
subject: RE: SQL Gurus Wanted
From: Jon Paris
Can any of the SQL gurus out there suggest the magic incantation's) that
will achieve the following.
Tables A and B have a number of common columns.
If the keys in A and B match, update columns in A with the values from B.
If there is a row in B that does not exist in A, then insert a new row
based
on B.
It is late on Sunday (actually early Monday) and my brain has seized.
Yeah, it's called RPG <grin>.
Seriously, you may not like the answer, although it works:
update A set (data1, data2) =
(select data1, data2 from B
where A.key1 = B.key1 and A.key2 = B.key2)
where exists
(select data1, data2 from B
where joe1.key1 = joe2.key1 and joe2.key2 = joe1.key2)
Note the duplication of the key clause, once to select the record to update
and once to only update those records that have matches. If you didn't do
that, you'd get NULLs in the data values for records without matches.
Also note that this will end messily if more than one record in B matches a
record in A.
Insertion is a little different:
insert into A
(select B.* from B exception join A
on A.key1 = B.key1 and A.key2 = B.key2)
This works when the tables have exactly the same layout. The "B.*" would
have to be a specific list of fields if the tables didn't match exactly.
Enjoy.
Joe
P.S. Really, though, this is almost a picture-perfect matching record
program in RPG!
------------------------------
message: 4
date: Mon, 30 Jul 2007 05:58:30 -0500
from: "Don Cavaiani" <dcavaiani@xxxxxxxxxxxxx>
subject: 3479 + Symbol LS3070 wireless scanner - Replacement needed
We have had this cost effective wireless scanning method in process for
years.
Now - the scanner has failed, and we need to look for a replacement
"system". The old way was cost effective and VERY SIMPLE.
Anyone know what we can look to get as a replacement?
Don F. Cavaiani
IT Manager
Amerequip Corp.
920-894-7063
"Only one who devotes himself to a cause with his whole strength and soul
can be a true master. For this reason mastery demands all of a person."
Albert Einstein
------------------------------
message: 5
date: Mon, 30 Jul 2007 08:55:10 -0400
from: ChadB@xxxxxxxxxxxxxxxxxxxx
subject: Re: SRVMON Jobs - New Twist?
OK, thanks Sergio! It's good to see the IBMers chime in once in a while!
Out of curiousity, do you know why they built this functionality so that it
starts 70+ jobs? It's something i've had to explain at least 3 times
already to people that have noticed the jobs and associated messages on the
system... my response was that "It's normal... it's for the new software
error logging", but i'm sure the answer was bought 100%...
Sergio Toscano
Lomeli/Mexico/IBM
<stlomeli@xxxxxxx To
.com> midrange-l@xxxxxxxxxxxx
Sent by: cc
midrange-l-bounce
s@xxxxxxxxxxxx Subject
Re: SRVMON Jobs - New Twist?
07/27/2007 06:46
PM
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
Reason code 8 is a normal reason code when a watch session is ending. This
is not a problem and none of the PTFs posted before will fix it. Even when
you did not use ENDWCH, Service Monitor did. Service Monitor ends all of
those watch sessions every time it is ended.
Service Monitor can be restarted because of the following reasons:
1. Changing the QSFWERRLOG value from *LOG to *NOLOG and back to *LOG (this
starts the QSYSWRK/QSRVMON job - which starts the QUSRWRK/SRVMONxxxx jobs)
2. IPLing the system or restarting QSYSWKR and QUSRWRK subsystems - when
the subsystem comes up, the QSRVMON jobs will start - which starts the
SRVMONxxxx jobs
ChadB@wheeling-ni
sshin.com
Sent by: To
midrange-l-bounce Midrange Systems Technical
s@xxxxxxxxxxxx Discussion
<midrange-l@xxxxxxxxxxxx>
cc
27/07/2007 09:03
Subject
Re: SRVMON Jobs - New Twist?
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
That sounds like one of the inventory or service director jobs sending
something off to IBM to me.
It seems that the batch of SRVMON messages on our boxes have kicked off
only once or twice in the week we've been at V5R4. Did you just recently
upgrade?
Jerry Adams
<jerry@bwwholesal
e.com> To
Sent by: Midrange Systems Technical
midrange-l-bounce Discussion
s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx>
cc
07/27/2007 09:53 Subject
AM Re: SRVMON Jobs - New Twist?
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
Chad,
Thanks. Looking forward to hearing your results. In the meantime I'll
go ahead and download the PTF's in preparation.
I check QSYSOPR messages every morning on both of our machines, but this
is the first time I have seen these messages. These were on our
production box; haven't seen anything of this nature on our backup box.
I did notice this one issued about 20 minutes later:
Message ID . . . . . . :
TCP2617
Date sent . . . . . . : 07/27/07 Time sent . . . . . . :
05:32:26
Message . . . . : TCP/IP connection to remote system 207.25.252.200
closed,
reason code
2.
Cause . . . . . : The TCP/IP connection to remote system
207.25.252.200 has
been closed. The connection was closed for reason code 2. Full
connection
details for the closed connection
include:
- local IP address is
12.65.66.10
- local port is
59292
- remote IP address is
207.25.252.200
- remote port is
443
I don't think there's a connection, but that's just a WAG. I can
actually hit the 207.25.252.200 address (an IBM HTTP Server site), but
not the 12.65.66.10 address. The HTTP server on our system, for what
it's worth, is stopped.
* Jerry C. Adams
*IBM System i Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
615.995.7024
fax
615.995.1201
email
jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>
ChadB@xxxxxxxxxxxxxxxxxxxx wrote:
Jerry - in looking closer at my jobs I saw the same thing and found these
3
V5R4 PTFs that seemed like a match for the reason code '08' :
SI26806
SI26745
SI26817
SI24998 (coreq of one of the 3)
SI23663 (coreq of one of the 3)
I put them on our dev box yesterday (they were all immediate PTFs) and
will
see if they resolve the messages. It sounds like the high number of jobs
is normal, but I think the messages we've got will probably get resolved
with these PTFs.
Jerry Adams
<jerry@bwwholesal
e.com>
To
Sent by: Midrange-L
midrange-l-bounce <midrange-l@xxxxxxxxxxxx>
s@xxxxxxxxxxxx
cc
Subject
07/27/2007 08:02 SRVMON Jobs - New Twist?
AM
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
There's been a little bit of a discussion here about the SRVMONxx jobs.
I, too, have 78 of these running but, after the discussion and
investigation, decided they were OK. But this morning, when I checked
QSYSOPR's messages something strange popped out:
Message ID . . . . . . :
CPI3999
Date sent . . . . . . : 07/27/07 Time sent . . . . . . :
05:03:58
Message . . . . : Watch session SRVMON0000 issued by
223998/QUSER/QZRCSRVS
at 07/23/07 11:31:43 has been ended. Reason code:
X'08'
Cause . . . . . : Watch session SRVMON0000 issued by
223998/QUSER/QZRCSRVS
and associated with QSCSWCH has been ended. Reason code: X'08'. The
possible
reason codes
follow:
08 - End Watch (ENDWCH) command or End Watch (QSCEWCH) API was
issued.
The above is just a sample of 78 such messages sent between 05:03:58 and
05:05:15.
Now the other side of the coin is that the jobs are running again. The
start times range from 05:05:20 and 05:05:34.
I know that I didn't issue the ENDWCH command. Any clues?
--
* Jerry C. Adams
*IBM System i Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
615.995.7024
fax
615.995.1201
email
jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
midrange.com
