Re: Hearbeat Status? -- MIDRANGE-L

But to what/whom and using what method? I can connect to IBM just find for
PTFs.

Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #21 <https://www.bvstools.com/mailtool.html>: Superior
Product Support - BVSTools has proven over the past 20+ years and working
with thousands of customers all over the world and many different SMTP
servers to have superior support for our products. We feel functionality is
important, but just as important is making sure that emails and phone calls
for support are answered as quickly as possible. During working hours
you'll often get a response in less than 30 minutes.

On Sun, Oct 29, 2017 at 8:22 PM, John McKee <jmmckee3@xxxxxxxxx> wrote:

Communication problem... Makes me wonder what a communication trace might
reveal. Been many years since I have seen one, but it showed more than
ever made it to a job log.

John McKee

On Sun, Oct 29, 2017 at 6:59 PM, Bradley Stone <bvstone@xxxxxxxxx> wrote:

Nope, nothing before it that I could tell that mean anything.

I keep getting it now and then. I'll look again but I really don't see
anything in the job log. It looks like a communications problem, but for
what and where I have no idea. I just did the latest CUM for V7R3

without

any issues (besides node not working any more.. lol)

Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #3 <https://www.bvstools.com/mailtool.html>: No 400

byte

or less message limit as with SNDDST or SNDSMTPEMM.

On Sun, Oct 29, 2017 at 6:32 PM, John McKee <jmmckee3@xxxxxxxxx> wrote:

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:

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