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



what releaae are you running it on?
When I do it on my system, I only get two messages - create and then 
delete DTAQ.
Anyway, CPFB94A is issued if collector does not reply within a timeout 
period.
To find out why it does not reply, look at QYPSPFRCOL job.
What was its status and what it had in the joblog.

    Alexei Pytel




rob@xxxxxxxxx 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
07/26/2005 11:43 AM
Please respond to
Midrange Systems Technical Discussion


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
Re: CPFB94A-Collector communications error.  Reason code 02.






CALL PGM(QYPSENDC) PARM('*PFR         '   X'00000000')
CPC2206-Ownership of object QPFR000950 in QTEMP type *USRSPC changed.
CPC2206-Ownership of object Q117730950 in QUSRSYS type *DTAQ changed.
CPC9801-Object Q117730950 type *DTAQ created in library QUSRSYS.
CPC2191-Object Q117730950 in QUSRSYS type *DTAQ deleted.

- one minute time lapse -

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 


Rob Berendt

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.