Re: Hearbeat Status?

It doesn't work, I downloaded the latest CUM last night and 2 more PTFs
this morning for OSS since the latest CUM broke that. :)

I did look at the server jobs that were running and sending the error and
did find that they didn't have proper authority to QSYSOPR message queue.
Not sure if that's related at all.


Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #5 <https://www.bvstools.com/mailtool.html>: Easy setup!
No confusing or obscure setup instructions, directory entries, SMTP users,
aliases or host tables. All you need is TCPIP, a connection to the internet
and you're done!

On Mon, Oct 30, 2017 at 1:45 PM, Rob Berendt <rob@xxxxxxxxx> wrote:

BTW, that last step, SNDPTFORD SF98730, was simply to download the PTF
cover letter, not the whole cume. Just to test that SNDPTFORD works.


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: Bradley Stone <bvstone@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 10/30/2017 01:01 PM
Subject: Re: Hearbeat Status?
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



On Mon, Oct 30, 2017 at 10:19 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

I'm curious to know what exact command you were running to test. Let me
explain why I am asking...

The initial message I didn't do anything to make it appear.

To test, I did exactly what is in the text of the error:

To test the
connection manually, on a command line type GO SERVICE and press enter.
Select option 17, Verify Service Agent connection.

This system came loaded with V7R2 and was immediately updated to V7R3 the
day I got it.

Reading further is optional...

I did.. this test you gave seemed to work (see below if interested). It's
possible since I just did the latest CUM last night maybe now it's fixed.

Downtime service verification steps:

Step one:
GO SERVICE
1. Change Service Agent attributes
Make sure that Enable is set to *YES. If already *YES, then F12 back to
Electronic Service Agent menu. If not, change it to *YES and enter
through the defaults.
Did you have to change it to *YES? ____________

No, it was set to *YES on my system.

10. Work with jobs
You should have at least the following 5 jobs:
Job User Type -----Status----- Function
QS9HDWMON QSRVAGT BATCH ACTIVE PGM-QS9HDWMON
QS9PALMON QSRVAGT BATCH ACTIVE PGM-QS9PALMON
QS9PRBMON QSRVAGT BATCH ACTIVE PGM-QS9PRBMON
QS9PRBSND QSRVAGT BATCH ACTIVE PGM-QS9PRBSND
QS9SFWMON QSRVAGT BATCH ACTIVE PGM-QS9SFWMON
If not, take “8. End jobs” to ensure that all are down. Then “9. Start
jobs”. When complete then another “10. Work with jobs”.

Yes, those jobs are running.

Step two: (Do not do anymore!)
VFYSRVCFG SERVICE(*ECS)
When complete page down through the messages at the bottom. Hopefully

you

have:
Verify processing completed successfully.
If not, take a note here.
A few times lately I’ve had this run for over 5 minutes. If so, start
another session and telnet here or something. Find the original job you
were running this from. WRKUSRJOB QSECOFR *ACTIVE is one good

technique.

Check the joblog. If you are seeing a lot of bad pointer messages then
Sys-Req out of the first job, sign off, and sign back on to start a new
job and try it again.

Step three:
SNDSRVRQS ACTION(*TEST)

I got:

Message ID . . . . . . : CPZ8C02 Severity . . . . . . . : 00
Message type . . . . . : Completion
Date sent . . . . . . : 10/30/17 Time sent . . . . . . : 10:54:46

Message . . . . : Test request complete.
Cause . . . . . : The test of the communications connections between
this
system and the remote service system was successful.

If it works Rob “may” get a call from IBM to his extension. His

extension

also rings on one phone in the Kendallville computer room. Sometimes

the

local CE just emails Rob.
On 2016-09-14 Rob Berendt had an issue with GDI with SNDSRVRQS and
SNDPTFORD. He followed the steps in Corrective Action SYS16000013. If
you get an error, and upon further examination of the joblog you notice
“Point-to-point profile QVPN01IBM1 in use.” then it would behoove you to
peruse that corrective action.
Write down time _____________

Step four:
DSPPTF
Write down what you have for “Release of base option” _____________
If you wrote down V7R3M0 then
SNDPTFORD PTFID((SF98730))
Otherwise
SNDPTFORD PTFID((SF98720))
Enter defaults on first screen, 1=Send now on second screen.
WRKPRB
Top one should have a description of ‘Preventive service planning
information request‘
5=Display details
F9=Display PTFs
PTF ID Requested PTF Save File
SF987#0 Yes No
8=Display cover letter
and it should have a somewhat recent date in "the information in this
document was last updated : ".

I installed the latest CUM last night.

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: Bradley Stone <bvstone@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 10/29/2017 05:48 PM
Subject: Hearbeat Status?
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



My V7R3 system, now that I started monitoring for messages, gave me

this:

Text:
Service Agent connection verification failed.

Second Level Text:
&N Cause . . . . . : An attempt was made to connect to IBM to test
connectivity. The test was not successful. &N Recovery . . . : See

the

previously listed messages in the job log and the Service Agent audit

log

for additional information on the cause of the error. To test the
connection manually, on a command line type GO SERVICE and press enter.
Select option 17, Verify Service Agent connection.

So, following the instructions I used the Verify option and got this:

Message ID . . . . . . : CPIEF85

Date sent . . . . . . : 10/29/17 Time sent . . . . . . :
15:42:28


Message . . . . : Verify operation not successful.



Cause . . . . . : An attempt to verify the service information
connection
configuration was not successful because of reason code 2.

Recovery . . . : Reason codes and their meaning:

1 -- An error occurred while attempting to connect to the IBM

Gateway.

2 -- An attempt to connect with IBM to send a Heartbeat Status was

not

successful.

3 -- An attempt to connect with IBM to send a Heartbeat Service

Information was not successful.

See any previously listed messages and the Electronic Service Agent
audit
log for additional information. Fix any errors, then try the request
again.
If the problem continues to occur, contact your local IBM Service


Is this a big deal?


Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #5 <https://www.bvstools.com/mailtool.html>: Easy

setup!

No confusing or obscure setup instructions, directory entries, SMTP

users,

aliases or host tables. All you need is TCPIP, a connection to the
internet
and you're done!
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD



--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD



--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD