× 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.



Thanks Rob. That is exactly it. I recall doing that a few years back but couldn't quite
remember the steps. Like most things, I'll usually dig until I find the answer. This was
no different. I had to pop in and out of a few IBM sites to locate those steps.


Very Respectfully,
Michael Mayer
IBM i on Power System Admin.
IT Operations.
The Florida Bar
651 E. Jefferson St
Tallahassee, Florida 32399-2300
mmayer@xxxxxxxxxxxxxx
https://www.floridabar.org
Office: 850.561.5761
Cell: 518.641.8906
IBM i Reference blog page: http://ibmireference.blogspot.com/



3. RE: CPIEF12 Service Agent was unable to send a message to
user (Rob Berendt)

----------------------------------------------------------------------

message: 3
date: Mon, 17 Oct 2022 20:27:09 +0000
from: Rob Berendt <rob@xxxxxxxxx>
subject: RE: CPIEF12 Service Agent was unable to send a message to
user

This is starting to sound familiar...
I think there was one upgrade issue we had where it was recommended to delete and rebuild the service configuration. Steps involved included

Rebuild of service configuration:
DLTSRVCFG DLTCMNCFG(*YES)

WRKTCPPTP and delete (4=Remove) any remaining profiles that begin with the letter 'Q'

WRKLIND LIND(Q*) and delete (4=Delete) any remaining lines that have the type of *PPP and begin with the letter 'Q'. Also delete QESLINE and QTILINE which are type *SDLC

RMVLNK OBJLNK('/qibm/userdata/os400/universalconnection/*')
You may get a message that not everything was deleted. You may have to empty the contents of some subdirectories within it to delete it. Then try again.

The CRTSRVCFG cannot be run in restricted state. Put a note on the after IPL instructions to do this.
CRTSRVCFG ROLE(*PRIMARY) CNNTYPE(*DIRECT) CNTRYID(US) STATE(IN)
Write down time. __________________
End of Rebuild of service configuration:

I now do this as part of every upgrade.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Mayer, Michael via MIDRANGE-L
Sent: Monday, October 17, 2022 3:30 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Cc: Mayer, Michael <MMayer@xxxxxxxxxxxxxx>
Subject: CPIEF12 Service Agent was unable to send a message to user

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.


I've seen this before and had to locate the CPIEF12 error. It took a bit but in the end I had to reconfigure the Service Agent. It was a several step process as I recall but relatively easy.

Perhaps a place to start:
https://www.ibm.com/docs/en/i/7.3?topic=agent-activating-electronic-service


Very Respectfully,
Michael Mayer
IBM i on Power System Admin.
IT Operations.
The Florida Bar
651 E. Jefferson St
Tallahassee, Florida 32399-2300
mmayer@xxxxxxxxxxxxxx
https://www.floridabar.org
Office: 850.561.5761
Cell: 518.641.8906
IBM i Reference blog page: http://ibmireference.blogspot.com/


3. CPIEF12 Service Agent was unable to send a message to user
(Kevin Monceaux)
4. RE: CPIEF12 Service Agent was unable to send a message to
user (Rob Berendt)


----------------------------------------------------------------------


message: 3
date: Mon, 17 Oct 2022 08:38:30 -0500
from: Kevin Monceaux <Kevin@xxxxxxxxxxxxxx>
subject: CPIEF12 Service Agent was unable to send a message to user

Where I work we have one LPAR getting daily CPIEF12 messages like:

Service Agent was unable to send a message to user ???????/ .
Service Agent was unable to send a message to user ???/?%? ??.
Service Agent was unable to send a message to user ???/??????.

from job QSJSENDER. Data area QSRVAGT/QS9USERS is set to a blank list, all EBCDIC x'40's, as it is on other LPARs where QSJSENDER jobs are running successfully without getting CPIEF12 messages. Does anyone know what might be causing this?


--

Kevin
http://www.RawFedDogs.net
http://www.WacoAgilityGroup.org
Bruceville, TX

What's the definition of a legacy system? One that works!
Errare humanum est, ignoscere caninum.


------------------------------

message: 4
date: Mon, 17 Oct 2022 14:00:30 +0000
from: Rob Berendt <rob@xxxxxxxxx>
subject: RE: CPIEF12 Service Agent was unable to send a message to
user

Try prompting CHGSRVAGTA and actually change a user name and see if that makes a difference.

I checked out
select data_area_value, HEX(data_area_value) from
table(qsys2.data_area_info(DATA_AREA_LIBRARY => 'QSRVAGT',
DATA_AREA_NAME => 'QS9USERS'));

And x'40' blanks are used as the filler.

A casual glance didn't seem to care about CCSID.

A search for that error message had only 3 hits. One was some site which felt a need to list all IBM error messages themselves. The other two were
1 - 7.3 upgrade instructions admonishing you to put on PTF's after the upgrade but didn't mention that message specifically.
2 - An IBM site listing 'recommended ptfs' including service agent but not that specific error message.
Weird. Does even google say if you can't find the specific message then get current on PTF's and try again?

See the "select topics" below:
https://www.ibm.com/support/pages/ibm-i-support-recommended-fixes

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com


________________________________
Please note: Florida has very broad public records laws. Many written communications to or from The Florida Bar regarding Bar business may be considered public records, which must be made available to anyone upon request. Your e-mail communications may therefore be subject to public disclosure.
--
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@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com


------------------------------

Subject: Digest Footer

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) digest 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@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com


------------------------------

End of MIDRANGE-L Digest, Vol 21, Issue 1249
********************************************

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.