|
Any detailed messages before this messages? What was MSGLEVEL and MSGSEV
when you did this test?
John
On Sun, Oct 29, 2017 at 4:48 PM, Bradley Stone <bvstone@xxxxxxxxx> wrote:
My V7R3 system, now that I started monitoring for messages, gave me this:the
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
previously listed messages in the job log and the Service Agent audit logGateway.
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
not
2 -- An attempt to connect with IBM to send a Heartbeat Status was
setup!
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
No confusing or obscure setup instructions, directory entries, SMTPusers,
aliases or host tables. All you need is TCPIP, a connection to theinternet
and you're done!list
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.