NIM TELINV.INI file was corrupted.
Backup and running.
When ever you exit the NIM PC application, the TELINV.INI file is updated.
Somehow, it got updated with some garbage.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Nelson
Sent: Thursday, April 06, 2017 9:30 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: NIM 830 won't conect to our Production I - TELINV.EXEhasstopped working
Sounds like a good opportunity to expand their knowledge base. :-)
Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Thursday, April 06, 2017 8:24 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: NIM 830 won't conect to our Production I - TELINV.EXEhasstopped working
Already done.
They have never seen this error.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Nelson
Sent: Thursday, April 06, 2017 9:17 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: NIM 830 won't conect to our Production I - TELINV.EXE hasstopped working
What does your vendor say? I would start with them.
Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Thursday, April 06, 2017 7:47 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: NIM 830 won't conect to our Production I - TELINV.EXE hasstopped working
Which IBM I subsystems/server jobs would be used by YOBSYTCPDP - CA Plex TCPIP Dispatcher?
Paul
-----Original Message-----
From: Steinmetz, Paul
Sent: Wednesday, April 05, 2017 9:35 PM
To: 'Midrange Systems Technical Discussion'
Subject: NIM 830 won't conect to our Production I - TELINV.EXE has stopped working
On our Production LPAR - NIM 830 won't connect to our Production I - TELINV.EXE has stopped working.
This error is on the Windows server.
No errors anywhere on the I.
Problem started late Monday, 4/3.
The NIM 830 PC software runs on a Windows server.
It connects to the I via a listener program.
YOBSYTCPDP *PGM NMLSTNRPNC CLE CA Plex TCPIP Dispatcher
R&D LPAR is fine.
R&D NIM server connects fine.
NIM server is not the issue.
Recreated the same error from the R&D NIM server trying to connect to Production I.
Restored Production env to R&D LPAR, connects fine, this eliminated both application programs and data.
I'm thinking it is something on the I, outside of both applications.
Last resort is an emergency IPL, waiting for that approval.
Any thoughts from the group.
Any service programs, etc that might need recycling.
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx
http://www.pencor.com/
--
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.
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:
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.
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:
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.
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:
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.
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.