|
John Here are a couple of suggestions: 1. Create a data area or file to hold the "Application Date" {in CCYYMMDD format}. That way it does not mater what the system date is. Just write a program to increment it once a day. 2. Have you clearing program check the "Application Date" data area for Jan 31, ie. substr("Application Date" 5 4). 3. You may want to copy the file to a backup file for possible additional reporting. We use a data area in my shop & it is great for a testing environment. We can test any day, month or year end long before it happens without having to change the system or job date. Our nightly process actually does end-of-day processing, changes the "Application Date" & then does beginning-of-day processing. Vincent Forbes CIBC Toronto, Ontario > I have a file that I append data to each month throughout the year via > query. Come January 31 when we run our first closeout of the year, this file > has to be cleared so that we can start all over again. I usually just CLRPFM > I am trying to automate this process but keep in mind, when we run the > month-end on Jan 1 for the year-end, this file must not get cleared. It is > entirely possible this process won't run on Jan 31, it could spill over to > Feb 1 depending on the length of the closeout. Any ideas keeping within a CL > or something simple would be greatly appreciated. > > > > John A Candidi
As an Amazon Associate we earn from qualifying purchases.
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.