CPIEF12 Service Agent was unable to send a message to user -- MIDRANGE-L

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

Subject: CPIEF12 Service Agent was unable to send a message to user
From: Kevin Monceaux <Kevin@xxxxxxxxxxxxxx>
Date: Mon, 17 Oct 2022 08:38:30 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

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?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: CPIEF12 Service Agent was unable to send a message to user , Rob Berendt

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.