|
Start with these:
https://www-01.ibm.com/support/docview.wss?uid=nas8N1010756
https://archive.midrange.com/midrange-l/201612/msg01012.html
How to Delete and Recreate your ECS Configuration
http://www-01.ibm.com/support/docview.wss?uid=nas8N1020782
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
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Art
Tostaine, Jr.
Sent: Monday, July 8, 2019 3:57 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: ECS Phone Home SNDSRVRQS *TEST fails
CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.
After reading the other Phone home thread, I tried to test ours.
This system is on V7R3 but might be late on PTF's.
Object QESE844025 type *DTAQ created in library QGPL.
Cannot connect to IBM service system.
Object QESE844025 in QGPL type *DTAQ deleted.
Error occurred while processing request.
This message says to look at previous messages but there are none.
Message ID . . . . . . : CPF8C2A Severity . . . . . . . : 40
Message type . . . . . : Diagnostic
Date sent . . . . . . : 07/08/19 Time sent . . . . . . :
15:39:24
Message . . . . : Cannot connect to IBM service system.
Cause . . . . . : An error occurred while attempting to establish
communications with the IBM service system.
Recovery . . . : See the previously listed messages in the job log to
determine the cause of the error. Correct the error and try the request
again. If the problem continues, contact your service representative.
Verifying the connection from SERVICE #17
Message ID . . . . . . : CPIEF85
Date sent . . . . . . : 07/08/19 Time sent . . . . . . :
15:58:22
Message . . . . : Verify operation not successful.
Cause . . . . . : An attempt to verify the service information connection
configuration was not successful because of reason code 1.
Recovery . . . : Reason codes and their meaning:
1 -- An error occurred while attempting to connect to the IBM Gateway.
--
Art Tostaine
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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: https://amazon.midrange.com
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.