RE: IPGCFP4/@CPISYS -- SYSTEM21

I thought of that too but our job numbers had actually rolled over, there
were so many of them...
I think you're safe to remove all but the current days records...
That limits the SQL delete statement selection criteria to:
delete from IPGCFP4/@CPISYS
where @Zdate <> 102300  AND
      @Zdate <>   1023  AND
      @Zdate <>   1001023

That should cover all permutations of todays date...





"Grinstead, Scott" <SAGrinstead@Rockyboots.com> on 10/23/2000 10:32:00 AM

Please respond to JBAUSERS-L@midrange.com
                                                              
                                                              
                                                              
  To:          "'JBAUSERS-L@midrange.com'"                    
               <JBAUSERS-L@midrange.com>                      
                                                              
  cc:          (bcc: Jeff Klipa/Harvard)                      
                                                              
                                                              
                                                              
  Subject      RE: IPGCFP4/@CPISYS                            
  :                                                           
                                                              






Could you use the Job Number field (@ZJOBN) for the selection criteria for
the archive?  That would eliminate the possibility of a bad date range, or
better phrased an impossible date range.
Scott Grinstead
-----Original Message-----
From: Jeff_Klipa/Harvard@harvardind.com
[mailto:Jeff_Klipa/Harvard@harvardind.com]
Sent: Monday, October 23, 2000 9:44 AM
To: JBAUSERS-L@midrange.com
Subject: RE: IPGCFP4/@CPISYS
Good observation Art...!!!  Wow...  Ours is also set to *NOMAX...
I have just detected three distinct methods of date storage in this file...
See the following example...
    Date    Time  Program
                  Name
 1001005   83430  MP240
 1001006  101057  MP240
  102000  171455  MJ500
  102000  210108  @CPIPGMJ
  102100    1227  @CPIPGMJ
    1023   11304  DB287
    1023   73139  DB270
Last friday when I cleared the file I left only two (2) records in the
file...  Today there are twenty-two (22) records...
Again - I do not know what this file is used for but I suspect that
clearing old records will not cause any harm...




"Heffner, Art" <AHeffne@PTS-TOOLS.COM> on 10/23/2000 08:53:28 AM
Please respond to JBAUSERS-L@midrange.com


  To:          "'JBAUSERS-L@midrange.com'"
               <JBAUSERS-L@midrange.com>
  cc:          (bcc: Jeff Klipa/Harvard)


  Subject      RE: IPGCFP4/@CPISYS
  :






When I looked at our file it is *NOMAX and contains 138,000 records going
back to August of 1996.  Since we installed JBA in May of 1999,  I must
assume the older records were a gift from our JBA setup people.  I also
noticed that records output by program MR235 or CPIPGAO have the date in
MMDDYY sequence and other programs put the date out in YYMMDD sequence (no
century).  This will make it a joy to purge!
Art Heffner - Production Tool Supply
          -----Original Message-----
          From:     Prill, Steve [mailto:sprill@rexairinc.com]
          Sent:     Friday, October 20, 2000 3:17 PM
          To:  'jbausers-l@midrange.com'
          Subject:  IPGCFP4/@CPISYS
          We received a file full error on the above file when
attempting to submit
          MRP.  Although it only contains 10,000+ records, they date
back to 1996.  It
          appears that the file is used to retrieve the current job
number in various
          programs in MR, IN, AO, and PD applications.  I believe its
roots go back to
          the IPG (Interactive Program Generator) programs that JBA
used to write
          several years ago.
          Does System 21 have a method of removing old records from
this file?  Or can
          I simply delete some of the old records and re-org the file?
          I hesitate to change the physical file to max. records  =
*NOMAX and let the
          file grow if the old data is not needed.
          Thank you,
          Steve --
          +---
          | This is the JBA Software Users Mailing List!
          | To submit a new message send your mail to
JBAUSERS-L@midrange.com.
          | To subscribe to this list send email to
JBAUSERS-L-SUB@midrange.com.
          | To unsubscribe from this list send email to
JBAUSERS-L-UNSUB@midrange.com.
          | Questions should be directed to the list owner:
doug333@aol.com.
          +---
+---
| This is the JBA Software Users Mailing List!
| To submit a new message send your mail to JBAUSERS-L@midrange.com.
| To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com.
| To unsubscribe from this list send email to
JBAUSERS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: doug333@aol.com.
+---


+---
| This is the JBA Software Users Mailing List!
| To submit a new message send your mail to JBAUSERS-L@midrange.com.
| To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com.
| To unsubscribe from this list send email to
JBAUSERS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: doug333@aol.com.
+---
+---
| This is the JBA Software Users Mailing List!
| To submit a new message send your mail to JBAUSERS-L@midrange.com.
| To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com.
| To unsubscribe from this list send email to
JBAUSERS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: doug333@aol.com.
+---



+---
| This is the JBA Software Users Mailing List!
| To submit a new message send your mail to JBAUSERS-L@midrange.com.
| To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com.
| To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: doug333@aol.com.
+---