Difference between revisions of "Information Systems:IBM i Periodic Administrative Tasks"
Jump to navigation
Jump to search
m |
|||
| (31 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | * [[Periodic-Month|Month]] |
||
| − | =Month= |
||
| + | * [[Periodic-Calendar Year|Calendar Year]] |
||
| + | * [[Periodic-Fiscal Year|Fiscal Year]] |
||
| + | * [[Periodic-Monitor|Monitor]] |
||
| + | * [[Periodic-Housekeeping|Housekeeping]] |
||
| + | * [[Periodic-Purge|Purge]] |
||
| + | [[Category: IBM i]] |
||
| − | =Calendar Year= |
||
| + | [[Category: I.T. Periodic Tasks]] |
||
| − | |||
| − | ==Set up Courier Schedule for the Year== |
||
| − | |||
| − | From the warehouse manager, get the list of days that the warehouse will not be open. Enter these days into file ATLDATEP. Program PLZIU511 (PLZ -- build shipment file for Atlas) will not run if the current date is in this file. |
||
| − | |||
| − | whse menu / configuration / stat holidays no pickups |
||
| − | |||
| − | ==Change Atlas Transmission Times When Friday is a Statutory Holiday== |
||
| − | |||
| − | Atlas does a late pickup on Fridays, to take to their depot, and distribute to the drivers on Saturday morning (for Saturday delivery). If the warehouse is closed on Friday, this late pickup will have to be done on Thursday. Which means we will have to do a late transmission as well. |
||
| − | |||
| − | We cannot change the transmission schedule ahead of time, so put reminders in your calendar. |
||
| − | |||
| − | Key in the command WRKJOBSCDE and press enter. |
||
| − | |||
| − | Work with Job Schedule Entries BART |
||
| − | 10/14/15 16:53:30 |
||
| − | |||
| − | Type options, press Enter. |
||
| − | 2=Change 3=Hold 4=Remove 5=Display details 6=Release |
||
| − | 8=Work with last submission 10=Submit immediately |
||
| − | |||
| − | Next |
||
| − | -----Schedule------ Recovery Submit |
||
| − | Opt Job Status Date Time Frequency Action Date |
||
| − | _ ATLAS01 SCD USER DEF 06:15:00 *WEEKLY *NOSBM 10/15/15 |
||
| − | _ ATLAS02 SCD USER DEF 13:15:00 *WEEKLY *NOSBM 10/15/15 |
||
| − | _ ATLAS03 SCD USER DEF 13:35:00 *WEEKLY *NOSBM 10/15/15 |
||
| − | 2 ATLAS04 SCD *FRI 19:15:00 *WEEKLY *NOSBM 10/16/15 |
||
| − | _ DHLINV SCD USER DEF 22:00:00 *WEEKLY *NOSBM 10/14/15 |
||
| − | _ ECUREGULAR SCD *THU 21:30:00 *WEEKLY *NOSBM 10/15/15 |
||
| − | _ EDI_PO SCD *ALL 07:00:00 *WEEKLY *SBMRLS 10/15/15 |
||
| − | More... |
||
| − | Parameters or command |
||
| − | ===> |
||
| − | F3=Exit F4=Prompt F5=Refresh F6=Add F9=Retrieve |
||
| − | F11=Display job queue data F12=Cancel F17=Top F18=Bottom |
||
| − | |||
| − | Use option 2 to change job ATLAS04. |
||
| − | |||
| − | Change Job Schedule Entry (CHGJOBSCDE) |
||
| − | |||
| − | Type choices, press Enter. |
||
| − | |||
| − | Job name . . . . . . . . . . . . > ATLAS04 Name |
||
| − | Entry number . . . . . . . . . . > 309408 000001-999999, *ONLY |
||
| − | Command to run . . . . . . . . . CALL PGM(PLCIU511) PARM('AM') |
||
| − | |||
| − | Frequency . . . . . . . . . . . *WEEKLY *SAME, *ONCE, *WEEKLY... |
||
| − | Schedule date . . . . . . . . . *NONE Date, *SAME, *CURRENT... |
||
| − | Schedule day . . . . . . . . . . *FRI *SAME, *NONE, *ALL, *MON... |
||
| − | + for more values |
||
| − | Schedule time . . . . . . . . . '19:15:00' Time, *SAME, *CURRENT |
||
| − | |||
| − | F3=Exit F4=Prompt F5=Refresh F10=Additional parameters F12=Cancel |
||
| − | F13=How to use this display F24=More keys |
||
| − | |||
| − | Change the schedule day from *FRI to *THU, and press enter. Don't forget the change this back for the following week. |
||
| − | |||
| − | ==Copy of Warehouse Balance File== |
||
| − | |||
| − | When program EOMASW runs on January first for December, it creates a copy of SROSRO, and names it SROSROyyyy where yyyy is the calendar year just ending. It also builds the logical file SRBSROyyyy. This allows us to run reports for the auditors. |
||
| − | |||
| − | Confirm that this has been done. |
||
| − | |||
| − | ==Check ECU (Electronic Catalogue Update) Calendar== |
||
| − | |||
| − | Every Thursday, a scheduled job builds item files to send to the POS vendors. |
||
| − | |||
| − | Unity / Start uniPharm Extensions / VA Company / UWD Extensions / ECU Catalog Update / Show Calendar |
||
| − | |||
| − | Change 'Display Order' to DATED - date descending. |
||
| − | |||
| − | 10/15/15 09:54:01 uniPHARM -- PRODUCTION ECRIQ010/LISTCTL |
||
| − | ECU RUNNING ECU - Show Calendar Master File PRODUCTION 1.00 |
||
| − | Display Order Field Test Values |
||
| − | DATED DATE DESCENDING |
||
| − | Date Range Week Status AND |
||
| − | ST 00 00 00 00 AND |
||
| − | Period |
||
| − | RH=Run History WK |
||
| − | MA=Main TR=Transmissions BA=Base File CH=Changes PR=Promo |
||
| − | |||
| − | Reference Week St Start/End Dates SCHED DATE PRICE DATE ADDED DATE |
||
| − | APR08 2022 1580 NP APR 9 22 APR 15 22 APR 08 22 APR 08 22 NOV 07 14 |
||
| − | APR01 2022 1579 NP APR 2 22 APR 8 22 APR 01 22 APR 01 22 NOV 07 14 |
||
| − | MAR25 2022 1578 NP MAR 26 22 APR 1 22 MAR 25 22 MAR 25 22 NOV 07 14 |
||
| − | MAR18 2022 1577 NP MAR 19 22 MAR 25 22 MAR 18 22 MAR 18 22 NOV 07 14 |
||
| − | MAR11 2022 1576 NP MAR 12 22 MAR 18 22 MAR 11 22 MAR 11 22 NOV 07 14 |
||
| − | MAR04 2022 1575 NP MAR 5 22 MAR 11 22 MAR 04 22 MAR 04 22 NOV 07 14 |
||
| − | FEB25 2022 1574 NP FEB 26 22 MAR 4 22 FEB 25 22 FEB 25 22 NOV 07 14 |
||
| − | FEB18 2022 1573 NP FEB 19 22 FEB 25 22 FEB 18 22 FEB 18 22 NOV 07 14 |
||
| − | FEB11 2022 1572 NP FEB 12 22 FEB 18 22 FEB 11 22 FEB 11 22 NOV 07 14 |
||
| − | FEB04 2022 1571 NP FEB 5 22 FEB 11 22 FEB 04 22 FEB 04 22 NOV 07 14 + |
||
| − | F21=Scrn Reset |
||
| − | F3=Exit F5=Refresh . F12=Previous F24=Scrn Save |
||
| − | |||
| − | Make sure the latest date on this file will cover the following year. If not, add more. |
||
| − | |||
| − | Key in GENECUCAL and press F4 to prompt. Start with the week AFTER the last one on the file. |
||
| − | |||
| − | GENERATE ECUCALP FILE (GENECUCAL) |
||
| − | |||
| − | Type choices, press Enter. |
||
| − | |||
| − | STARTING WEEK # . . . . . . . . 1581 Number |
||
| − | # OF WEEKS TO GENERATE . . . . . 300 Number |
||
| − | SCHEDULE DATE - CE . . . . . . . 20 Number |
||
| − | SCHEDULE DATE - YR . . . . . . . 22 Number |
||
| − | SCHEDULE DATE - MO . . . . . . . 04 Number |
||
| − | SCHEDULE DATE - DY . . . . . . . 22 Number |
||
| − | |||
| − | =Fiscal Year= |
||
| − | |||
| − | ==Correct Last Day of February== |
||
| − | |||
| − | ASW does not handle leap year when setting period end dates - it simply adds one to the year. This means that February 29th is not in any fiscal period, and the system does not know how to deal with it. |
||
| − | |||
| − | At the beginning of a leap year, we must manually change February 28 to 29. Then, the year following, we must change it back. |
||
| − | |||
| − | The G/L Control File can only be changed by a user profile connected to the group profile ASW4ADM. An ASW administrator can change tables that affect the way ASW functions. They can also update an out of balance journal that would put the G/L out of balance - so use it with care!. |
||
| − | |||
| − | Sign on as user FINADMIN with our favorite password. |
||
| − | |||
| − | Key ASW and press enter. |
||
| − | |||
| − | Key GO GLSET and press enter. |
||
| − | |||
| − | Select option 2 Work with G/L control file, and correct the last day in February. |
||
| − | |||
| − | *VA/480B* G/L control file maintenance 10/15/15 09:16:16 GDMD0911 |
||
| − | ------------------------------------------------------------------------------- |
||
| − | Period name End date |
||
| − | Actual year/period.. 1609 FEBRUARY 022815 |
||
| − | MARCH 033115 |
||
| − | Last closed period.. 1607 APRIL 043015 |
||
| − | First stored period. 0812 MAY 053115 |
||
| − | JUNE 063015 |
||
| − | JULY 073115 |
||
| − | AUGUST 083115 |
||
| − | SEPTEMBER 093015 |
||
| − | OCTOBER 103115 |
||
| − | NOVEMBER 113015 |
||
| − | No of normal periods 12 DECEMBER 123115 |
||
| − | Total no of periods. 13 JANUARY 013116 |
||
| − | YEAR END 043016 |
||
| − | |||
| − | ==Make Sure Opening Balances for Analyser have been Built Correctly== |
||
| − | |||
| − | Go into G/L transaction inquiry, and look at a balance sheet account, for example 130000. Look at the balance for the last period of the previous year, and the first period of current year. If they don't look right, check file ANOBOB with query. |
||
| − | |||
| − | Specify File Selections |
||
| − | |||
| − | Type choices, press Enter. Press F9 to specify an additional |
||
| − | file selection. |
||
| − | |||
| − | File . . . . . . . . . ANOSTK Name, F4 for list |
||
| − | Library . . . . . . UP1480BFVA Name, *LIBL, F4 for list |
||
| − | Member . . . . . . . . *FIRST Name, *FIRST, F4 for list |
||
| − | Format . . . . . . . . ANSTK Name, *FIRST, F4 for list |
||
| − | File ID . . . . . . . T01 A-Z99, *ID |
||
| − | |||
| − | File . . . . . . . . . ANOBOB Name, F4 for list |
||
| − | Library . . . . . . UP1480BFVA Name, *LIBL, F4 for list |
||
| − | Member . . . . . . . . *FIRST Name, *FIRST, F4 for list |
||
| − | Format . . . . . . . . ANBOB Name, *FIRST, F4 for list |
||
| − | File ID . . . . . . . T02 A-Z99, *ID |
||
| − | |||
| − | Specify Type of Join |
||
| − | |||
| − | Type choice, press Enter. |
||
| − | |||
| − | Type of join . . . . . . . . 1 1=Matched records |
||
| − | 2=Matched records with primary file |
||
| − | 3=Unmatched records with primary file |
||
| − | |||
| − | Specify How to Join Files |
||
| − | |||
| − | Type comparisons to show how file selections are related, press Enter. |
||
| − | Tests: EQ, NE, LE, GE, LT, GT |
||
| − | |||
| − | Field Test Field |
||
| − | KESUTA EQ BOSUTA |
||
| − | KEREFK EQ BOREFK |
||
| − | |||
| − | Select and Sequence Fields |
||
| − | |||
| − | Type sequence number (0-9999) for the names of up to 500 fields to |
||
| − | appear in the report, press Enter. |
||
| − | |||
| − | Seq Field Text Len Dec |
||
| − | 10 T01.KESUTA Base or summary level code 3 |
||
| − | 20 T01.KEMK01 Mapped statistics key 01 35 |
||
| − | 30 T02.BOSUTA Base or summary level code 3 |
||
| − | 40 T02.BOYEAR Year 4 0 |
||
| − | 50 T02.BOBATP Balance type 3 |
||
| − | 60 T02.BOREFK Reference key between STK > BAL/BKX/BOB/BU 13 0 |
||
| − | 70 T02.BODAOB Debit opening balance value 21 4 |
||
| − | 80 T02.BOCAOB Credit opening balance value 21 4 |
||
| − | |||
| − | Select Records |
||
| − | |||
| − | Type comparisons, press Enter. Specify OR to start each new group. |
||
| − | Tests: EQ, NE, LE, GE, LT, GT, RANGE, LIST, LIKE, IS, ISNOT... |
||
| − | |||
| − | AND/OR Field Test Value (Field, Number, 'Characters', or ...) |
||
| − | KEMK01 EQ '130000' |
||
| − | AND BOYEAR EQ 2015 |
||
| − | |||
| − | Press F5 to run this query. |
||
| − | |||
| − | Lvl Key Lvl Year Bal Ref Debit opening Credit opening |
||
| − | cod 01 cod tpe key balance value balance value |
||
| − | |||
| − | 008 130000 008 2015 301 150 1,230,233,934.2600 1,219,240,254.9400- |
||
| − | 013 130000 013 2015 301 264 1,230,233,934.2600 1,219,240,254.9400- |
||
| − | 004 130000 004 2015 301 152 1,230,233,934.2600 1,219,240,254.9400- |
||
| − | 003 130000 003 2015 301 219 1,230,233,934.2600 1,219,240,254.9400- |
||
| − | 005 130000 005 2015 301 128 1,230,233,934.2600 1,219,240,254.9400- |
||
| − | 007 130000 007 2015 301 170 1,230,233,934.2600 1,219,240,254.9400- |
||
| − | 014 130000 014 2015 301 264 1,230,233,934.2600 1,219,240,254.9400- |
||
| − | 009 130000 009 2015 301 264 1,230,233,934.2600 1,219,240,254.9400- |
||
| − | 002 130000 002 2015 301 264 1,230,233,934.2600 1,219,240,254.9400- |
||
| − | A11 130000 A11 2015 301 415 1,230,233,934.2600 1,219,240,254.9400- |
||
| − | A12 130000 A12 2015 303 18 1,230,233,934.2600 1,219,240,254.9400- |
||
| − | 006 130000 006 2015 301 192 1,230,233,934.2600 1,219,240,254.9400- |
||
| − | 001 130000 001 2015 301 264 1,230,233,934.2600 1,219,240,254.9400- |
||
| − | |||
| − | The different summary levels should all agree. (the base levels A11 and A12 will probably be correct). If they don't, sign on as FINADMIN and go to menu STCSLM. Do menu option 3 for each level that does not have the correct opening balances. You have to redo the most complex levels first; as the program will try to use a different summary level as the base. The most complex summary level will have to use the base levels to recalculate. For example, in this sequence. 1, 2, 3, 4, 5, 9, 6, 7, 8, 13, 14. See the section on ASW Analyser for an explanation of what these are. |
||
| − | |||
| − | * Note that you cannot rebuild these summaries while there is activity on the system. Current transactions will update Analyser dynamically, then be included a second time in the rebuild. It is also possible to use the same reference key number twice. I have been doing this on Saturdays. |
||
| − | |||
| − | =Monitor= |
||
| − | |||
| − | ==Invoice Numbers - Estimated to Wrap in 2018== |
||
| − | |||
| − | We started in 2005 with an invoice number of 1000001, and credit note number of 3000001. On June 5, 2009 invoice numbers passed 3000000 and duplicated the credit note numbers. ASW was fine, as it accesses files by invoice number / type (1-invoice, 2-credit note) / year. The extensions were not. We quickly changed them to use the same key structure - after changing the next invoice number (in the number series table) to 5000001. |
||
| − | |||
| − | When the invoice number reaches 8999999 it will go back to 1000001. I don't think anything will happen - but keep an eye on it just in case. |
||
| − | |||
| − | ==Pick List Numbers - estimated to Wrap in 201?== |
||