All good questions. I guess you could end it and see what happens.
-----Original Message-----
From: Rob Berendt [mailto:rob@xxxxxxxxx]
Sent: Tuesday, May 21, 2019 11:46 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
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/rzahg2aaih.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
midrange.com
