CPFB94A-Collector communications error. Reason code 02. -- 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.

V5R3.  Been running fine for a long time now.  However, now when my backup 
program does
/*  Shut down pm/400 jobs for backup of QUSRSYS. */
             HLDJOBQ QSYS/Q1PSCHQ
             MONMSG  CPF3425 /* Job queue already held */
             CALL PGM(QYPSENDC) PARM('*PFR         '   X'00000000')
I am getting a series of messages about user spaces and data queues 
followed by:
CPFB94A-Collector communications error.  Reason code 02.
SEV  DATE      TIME             FROM PGM     LIBRARY     INST
40   07/26/05  00:03:37.207040  QYPSCOLL     QSYS        *STMT

TO PGM      LIBRARY     INST
BKPCTL3CC   GDISYS      0249

>From module . . . . . . . . :   QYPSENDCOL 
>From procedure  . . . . . . :   QypsEndCollector
Statement . . . . . . . . . :   106 

02 - The QYPSPFRCOL collector job did not respond to the request.

Granted, I could put a MONMSG on the CALL.  And I may have to do so 
because the backup has aborted two consecutive days because of this. 
However, has anyone else noticed this.

The only recent change I can think of is the person who normally starts up 
a bunch of Management Central monitors is out on vacation this week.  No 
recent ptf activity.

Rob Berendt

This mailing list archive is Copyright 1997-2025 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.