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

CPFB94A was sent on 07/26/05  00:03:37
Job 310207/QSYS/QYPSPFRCOL ended on 07/26/05 at 00:03:39; 

It seems that collector did end as was requested by QYPSENDC API.
Only it took it longer than the timeout tolerated by API.
One possibility is that if this was a relatively slow system and a lot of 
jobs were being ended at the same time (in preparation for backup), it 
simply took too much time for the collector to end.

You cannot control the timeout used by API, but you can repeat the API 
until it ends without exception. If you are on V5R3, you can use CL 
command ENDPFRCOL FRCCOLEND(*YES).
It's more aggressive and it will make sure that collector job is gone.
It will also take care of another issue - QYPSENDC API ends system 
collection only.
If there was non-system collection, initiated e.g. by Management Central 
system monitors, the collector will stay active. This is probably not what 
you want.

    Alexei Pytel




rob@xxxxxxxxx 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
07/26/2005 01:22 PM
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.






V5R3.

wrkjob QYPSPFRCOL
Job //QYPSPFRCOL not found.

DSPLOG PERIOD((*AVAIL *BEGIN)) JOB(QYPSPFRCOL)
Job 925706/QSYS/QYPSPFRCOL ended on 07/25/05 at 00:04:01; 
Job 310207/QSYS/QYPSPFRCOL started on 07/25/05 at 04:30:22
Job 310207/QSYS/QYPSPFRCOL ended on 07/26/05 at 00:03:39; 
Job 328060/QSYS/QYPSPFRCOL started on 07/26/05 at 04:30:08
Job 328060/QSYS/QYPSPFRCOL ended on 07/26/05 at 08:01:56; 

Rob Berendt