× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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/



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.