|
Update from IBM SME.--
I am responding to answer the questions you have regarding Management
Central (MGTC). You asked:
Q1-Why is STRTCPSVR *MGTC still an option at 7.2 and beyond if it's
not supported?
A1-The *MGTC TCP/IP server is still supported, however, majority of
people use it for the functions within the Management Central section
of System i Navigator. It is System i Navigator, which is provided by
IBM i Access for Windows (Client Access) that is out of support as of
April 30, 2019. Thus, we can no longer provide support for any
function within System i Navigator related to MGTC. Do you use the
server for anything outside of System i Navigator? From previous
updates, you stated that you do not use it, thus the recommendation to
end the QYPSJSVR job and change it so it does not autostart when TCP/IP is started.
Also, IBM i Access for Windows is not supported on Windows 10. Since
Windows 7 is or will soon be out of support, you will need to consider
using IBM i Access Client Solutions or a different emulation package.
Q2-Why does STRTCPSVR *MGTC still fire off a job which runs at 7.2 and
beyond if it's not supported?
A2-See A1
Q3-Why does this QYPSJSVR job keep spawning so many QSQSRVR jobs?
A3-ODBC/JDBC functions may also use the QYPSJSVR job, though again,
those functions are provided by IBM i Access for Windows, which is out
of support as of April 30. This doesn't mean that they won't still
work, it just means IBM i Global Support Center will no longer provide
support if there are errors. You'll need to move to use the same
functions with IBM i Access Client Solutions, which does NOT use MGTC or QYPSJSVR job.
Q4-Why does even the 7.4 Knowledge Center refer so often to MGTC?
A4-I don't know, I have not reviewed the 7.4 Knowledge Center but
suspect the items were just migrated from 7.3 and have not been
cleaned up. I don't know if development will clean it up either as
some may be using the QYPSJSVR job outside of System i Navigator.
Q5-Where is the announcement letter or MTU that says that "Management
Central" is now "deprecated" and no longer supported?
A5-There isn't a separate announcement for Management Central. Again,
majority use the MGTC options through System i Navigator, which is
what is out of support. From the IBM i Access for Windows website:
https://www-01.ibm.com/support/docview.wss?uid=isg3T1026807
*
Effective April 30, 2019, IBM(r) will withdraw support for 5770-XE1
IBM i Access for Windows(tm) 7.1. IBM i Access for Windows 7.1. was
delivered with IBM i 7.3, 7.2, and 7.1. Extended support will not be available.
Refer to:
https://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_c
a/8/897/ENUS918-058/index.html
http://www-01.ibm.com/support/docview.wss?uid=nas8N1022047
Replacement product is IBM i Access Client Solutions (5733-XJ1). Refer
to IBM i Access Client Solutions for more information.
*
Since you do not use MGTC or the QYPSJSVR job, our recommendation is
to end the server and set it not to autostart. Then look into the
functions and abilities provided by IBM i Access Client Solutions
(ACS), such as Navigator for i, or IBM i Access for Web (product 5770XH2).
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On
Behalf Of Rob Berendt
Sent: Tuesday, May 21, 2019 12:46 PM
To: Midrange Systems Technical Discussion
Subject: Management Central Was: New IPL timing issiue since applying
latest V7R3 CUME and TR6
I'm open to enlightenment but I thought Management Central was a
gatherer and System i Navigator (part of the deprecated IBM i Client
Access for
Windows) was a client to use it.
I do see this:
https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_72/rzahg/rzah
g2aaih.htm
However I have a few questions.
1-Why is STRTCPSVR *MGTC still an option at 7.2 and beyond if it's not
supported?
2-Why does STRTCPSVR *MGTC still fire off a job which runs at 7.2 and
beyond if it's not supported?
3-Why does this QYPSJSVR job keep spawning so many QSQSRVR jobs?
4-Why does even the 7.4 Knowledge Center refer so often to MGTC?
5-Are we positive that it doesn't still collect data used by other
tools to analyze?
I'm not sure on many of these.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Steinmetz, Paul via MIDRANGE-L
Sent: Tuesday, May 21, 2019 12:02 PM
To: 'Midrange Systems Technical Discussion'
<midrange-l@xxxxxxxxxxxxxxxxxx
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: RE: New IPL timing issiue since applying latest V7R3 CUME and
TR6
IBM is now suggesting that I should no longer be using Management
Central, since it is part of System I Navigator, which is no longer supported.
The QYPSJSVR job, which threw the error and is a Management Central
job, should actually not be started/running.
I'm curious what others are doing with Management Central?
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On
Behalf Of Steinmetz, Paul via MIDRANGE-L
Sent: Friday, May 17, 2019 9:22 AM
To: 'Midrange Systems Technical Discussion'
Cc: Steinmetz, Paul
Subject: RE: New IPL timing issiue since applying latest V7R3 CUME and
TR6
We have EIM configured, so a little out of the norm.
Be curious if any other users experience the same issue.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On
Behalf Of Rob Berendt
Sent: Friday, May 17, 2019 9:19 AM
To: Midrange Systems Technical Discussion
Subject: RE: New IPL timing issiue since applying latest V7R3 CUME and
TR6
Were you doing something outside the norm? Since you're sharing this
is there a possibility that all may be affected or just those using an
outside the norm configuration?
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Steinmetz, Paul via MIDRANGE-L
Sent: Friday, May 17, 2019 9:06 AM
To: 'Midrange Systems Technical Discussion'
<midrange-l@xxxxxxxxxxxxxxxxxx
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: New IPL timing issiue since applying latest V7R3 CUME and TR6
Since applying latest V7R3 CUME and TR6, (R&D LPAR), a new timing
issue is occurring on IPL.
I received CPI93B2 from Management Central job QYPSJSVR Software
problem data for QSYEIMSYS has been logged
Symptom string . . . . . . . . . : 5770 SP/QSYEIMSYS MOD/EIMHANDLE RC110
Opened PMR with IBM.
Turns out QUSRDIR job (IBM Tivoli Directory Server instance) is now
starting after QYPSJSVR.
QUSRDIR needs to be started before QYPSJSVR.
Currently, I have QYPSJSVR set to start with TCP/IP.
Probably need to change this.
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@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
--
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
--
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.
midrange.com
