× 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: Re: CPF1001
  • From: "Neil Palmer"<neilp@xxxxxxxxxxx>
  • Date: Wed, 4 Oct 2000 01:24:42 -0400

It was V3R1. 
Our nightly backup ends QINTER. 
After upgrading to V3R1 when it went to restart (STRSBS QINTER) we would 
occasionally get CPF1001.
PTF SF32088 fixed it.  The problem was that some V3R1 tapes had a bug.  If 
you had  TWO job classes named QBATCH (one in QGPL & one in QSYS), one of 
them incorrectly had a DFTWAIT time of 1 second instead of 120 seconds 
after installing V3R1.
Several other commands could also result in CPF1001 - especially on the 
"slower" systems.

Anyway - find what Class your job is using.  Check the default wait time 
for that class.
If it's around 30 seconds or less, try increasing to 120.

If you were running the power down from the Operations Assistant (QEZ.... 
programs), and you're on V4R4, 
see if you have PTF  SF57600.  (If your cum package are current you should 
have, it was on C0049440).



Neil Palmer         DPS Data Processing Services Canada Ltd.
                                             AS/400~~~~~
Markham,  Ontario,   Canada    ___________          ___  ~ 
Phone: (905) 474-4890  x303   |OOOOOOOOOO| ________  o|__||= 
Cell.: (416) 565-1682  x303   |__________|_|______|_|______) 
Fax:   (905) 474-4898          oo      oo   oo  oo   OOOo=o\ 
mailto:NeilP@DPSlink.com    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
http://www.DPSlink.com        AS/400e  The Ultimate Business Machine





Chuck Lewis <clewis@iquest.net>
Sent by: owner-midrange-l@midrange.com
2000/10/03 13:15
Please respond to MIDRANGE-L

 
        To:     MIDRANGE-L@midrange.com
        cc: 
        Subject:        Re: CPF1001

Dan,

I forget what version of OS/400 you are running on, but way back in the 
V3R1 days,
I THINK it was after upgrading to it or MAYBE after our move to RISC and 
V4R1, we
had problems. In one of our shutdown CL's we were killing everything with 
*IMMED
and Rochester said to but some times on there. It was something do to with 
a time
out before the request could complete or something. Sorry for being SO 
vague here,
but this was 3 or 4 years ago and at my last job.

Do you have SupportLine ?

Chuck

D.BALE@handleman.com wrote:

+---



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

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.