MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » December 2013

Re: Service Director



fixed

Thank you!

John McKee


On Wed, Dec 4, 2013 at 2:27 PM, Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>wrote:

Document Number: 397926833
____________________________________________________________
Functional Area: Electronic Service Agent
SubFunctional Area: General
SubSubFunctional Area: General
____________________________________________________________
Product: OS/400 BASE (5722SS100)
Release: V5R3M0

Classification: Public Use

Keywords: SERVICE
____________________________________________________________
Document Title:V5R3M0 Service Agent Jobs
Document Description:
The following are descriptions of V5R3M0 Service Agent Jobs:

QS9PALMON - This job periodically monitors the product activity log for
errors. The start hour and analysis interval are set in GO SERVICE Option
1. PAL analysis will run 10 minutes after the hour. For example, 00 means
the start hour is at midnight, and the PAL analysis interval is 4 so it
will run at 00:10, 4:10, 8:10, 12:10, and 16:10 daily.

QS9PRBMON - This job analyzes problem log entries as they enter the
problem log (WRKPRB), and reports problems to the service provider when
necessary.

QS9AUTOPTF - This job uses ECS to order an informational APAR that
contains a list of PTFs deemed critical by IBM Service. After this list has
been downloaded, the system or logical partition is checked to determine if
the PTFs on the informational APAR list are on the system or not. If there
are PTFs that are on the list that are not on the system, a secondary PTF
order is created and sent to the service provider for those PTFs only. The
job runs weekly, but currently it only downloads the informational APAR
list every other week. For the weeks when the informational APAR list is
not downloaded, the job will simply end normally and take no action.

QS9AUTOTST - This job periodically sends a test problem to the service
provider using ECS. It runs weekly and when its interval is met, the job
will send the test problem. For the weeks when sending the test problem is
not done, the job will simply end normally and take no action.

Note: This does not use HTTP connectivity, due to the type of transaction
it only uses VPN connectivity.

QS9SACOL - This is a service information collection/transmission job. It
runs daily to collect and send the service information to IBM. If the
settings in GO SERVICE Option 1 for the Send time element of the Service
information parameter is set to *COLLECT, then QS9SACOL will do both the
collect and send. If the send time is not *COLLECT, then QS9SACOL will only
collect the service information and not send.

QS9SASND - This is a service information transmission job. It runs daily
to send the service information to IBM only if the send time is different
than *COLLECT, which is immediately after the collection time based on the
settings in GO SERVICE Option 1. If the settings in GO SERVICE Option 1 for
the Send time element of the Service information parameter is set to
*COLLECT, then this job is not needed and it will not exist. If the send
time is not *COLLECT, then QS9SASND will be scheduled and only send the
service information.

QSJHEARTBT - This job does a verification transaction to IBM to test the
service information connection configuration. The default is 7 days;
however, it can be changed in GO SERVICE Option 1 - Connection Verification
Timer. It can be changed from 1 through 21 days.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, December 04, 2013 3:18 PM
To: Midrange Systems Technical Discussion
Subject: Re: Service Director

Ease up on the person. Too much and then it's like 3 fingers pointing at
you for each pointing at someone else (look at your hand while pointing).

You could look at the date applied. It probably matches some IPL. There's
nothing wrong with permanently applying ptfs after some time. It's
actually a good thing. It saves space. And, reduces all those PTF backup
files from being left over after a release upgrade. There's nothing that I
know of in the OS to automatically permanently apply PTFs.
The only caveat to not permanently apply are 'test' ptf's, and, certain
domino hotfixes.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: John McKee <jmmckee@xxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 12/04/2013 02:36 PM
Subject: Re: Service Director
Sent by: midrange-l-bounces@xxxxxxxxxxxx



I am going to assume that the QS9AUTOPTF job was always there. Still
leaves me wondering, though - there were hundreds of temp applied PTFs
. All are now perm.

Is there some magic PTF from IBM that would have been applied that would
have set all to perm, and then deleted itself?

I'm trying to understand what may have happened. The antisocial person
might have decided, for whatever reason, to perm apply PTFs. Or, could
have been something with the automatic process.

To your knowledge, is there any automated PTF process that would PERM
apply
all TEMP applied PTFs after some period? I do not see any such parameter
in CHGSRVAGTA to effect that.

John McKee


On Wed, Dec 4, 2013 at 1:16 PM, <rob@xxxxxxxxx> wrote:

That could be...


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: John McKee <jmmckee@xxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 12/04/2013 02:00 PM
Subject: Re: Service Director
Sent by: midrange-l-bounces@xxxxxxxxxxxx



That is exactly what GO SERVICE shows.

Thus, my original question as far as what >might< have happened. I have
no
idea if the anti-social person (just how antisocial can somebody be to
their own boss and STILL have a job) got a bill for service director and
cancelled it, or if he jst got into a snit. Why the library is gone,
but
the scheduled job remains.


Oh wait - this just hit me. Maybe at an earlier release - v4r5 or
earlier,
service director was an added thing, like TCP/IP was back in the v2
days,
and later it was put into the OS and thus the job schedule entry is
vestigal from ancient days. Does that make sense?

John McKee


On Wed, Dec 4, 2013 at 12:49 PM, <rob@xxxxxxxxx> wrote:

Try a couple of things.
GO SERVICE
1. Change Service Agent attributes
F9=All parameters
Page down to
Auto PTF:
Enable . . . . . . . . . . . . *NO
Schedule day . . . . . . . . . *SUN
Download PTFs . . . . . . . . *YES


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: John McKee <jmmckee@xxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxx>
Date: 12/04/2013 01:40 PM
Subject: Service Director
Sent by: midrange-l-bounces@xxxxxxxxxxxx



there is job scheduler entry on our system (v5r4m0) named AUTOPTF.

It is set to run on Mondays at 01:00:00.

The command is CALL PGM(SVCDRCTR/AUTOPTF).

That library does not exist, and, therefore the job submission fails.

The person who formerly tended to things, has never communicated to
others,
even to our mutual boss what he did or why.

Can anybody tell me if Service Director was abandoned and while the
library
was removed the scheduled job just slipped through?

Or, is that a separate maintenance thing, with the same result that it
was
removed but job scheduler entry remained?

I am not eager to remove things without a good reason. This doesn't
cause
harm, but appears to be useless. I can't get any answers here.

John McKee
--
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.


--
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.


--
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.


--
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.


--
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.


--
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.

--
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.







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact