Hi
@Pete WirfsI installed V12.3.6 (Windows with Postgres, OneInstaller) and found out, that the Forecast delivers better results than it did in V12.3.5. Here's my setup:
Master-JOBP with one Sub-JOBP. The latter contains 3 JOBS, where the first is linked with a CALE ("Christmas") and the second is set to inactive. The third has no special settings. The Master-JOBP is called by a JSCH every day at 6pm. A second JSCH calls the same Master-JOBP at 1pm every day, but is set to inactive in the JSCH definition (not the monitor). I generated a forecast using FORECAST() within a SCRI. The SCRI also calls a VARA.SQLI, which returns the forecast results. In V12.3.5 (and V12.3.4) objects set to inactive are not determined correctly, in fact they are determend as "yes, they'll be started!" This seem's to be fixed in V12.3.6. I didn't do any further testing e.g. EVNT
V12.3.5 (Linux with Oracle)WRONG!
2021-07-12 11:53:34 - U00020824 Because of the entered forecast filters ('AUTOFORECAST', '', ''), 1 of 1 forecasts have been deleted.
2021-07-12 11:53:34 - U00020408 0000000000000000
2021-07-12 11:53:35 - U00020408 0000000000000000
2021-07-12 11:53:35 - U00020237 The object variable '&SQL#' in object: 'SCRI.STARTE_AUTOPROGNOSE', line: '00011' (RunID: '0001102051') has been created with the value 'SELECT fe_name,fe_otype, fe_status,fe_starttime,fe_endtime,fe_ert FROM fe where fe_otype = 'JOBS' ORDER BY fe_starttime' by using the command :PSET.
2021-07-12 11:53:35 - U00020206 Variable '&SQL#' was stored with value 'SELECT fe_name,fe_otype, fe_status,fe_starttime,fe_endtime,fe_ert FROM fe where fe_otype = 'JOBS' ORDER BY fe_starttime'.
2021-07-12 11:53:36 - U02000218 Text file (RunID '1102051') completed successfully. File: '/tmp/forcast_2021.07.12_11:53:34.txt'.
2021-07-12 11:53:36 - U00007000 'EVENT.UNIXCMD' activated with RunID '0001107206'.
2021-07-12 11:53:36 - U00020408 Alle Objekte mit Status anders als 1900 sind heute inaktiv!
2021-07-12 11:53:36 - U00020408 Objekt-Name , Typ , => Status-Code , Startzeit , Endezeit , ERT
2021-07-12 11:53:36 - U00020408 JOBS.UNIX.JSCH.TEST.AAA.001,JOBS, => 1900 ,2021-07-12 13:00:00.000,2021-07-12 14:00:00.000,3600,,
2021-07-12 11:53:36 - U00020408 JOBS.UNIX.JSCH.TEST.BBB.001,JOBS, => 1920 ,2021-07-12 14:00:00.000,2021-07-12 14:00:00.000,10,,
2021-07-12 11:53:36 - U00020408 JOBS.UNIX.JSCH.TEST.AAA.002,JOBS, => 1900 ,2021-07-12 14:00:00.000,2021-07-12 14:00:10.000,10,,
2021-07-12 11:53:36 - U00020408 JOBS.UNIX.JSCH.TEST.BBB.002,JOBS, => 1900 ,2021-07-12 14:00:00.000,2021-07-12 14:00:10.000,10,,
2021-07-12 11:53:36 - U00020408 JOBS.UNIX.JSCH.TEST.BBB.003,JOBS, => 1900 ,2021-07-12 14:00:10.000,2021-07-12 14:00:20.000,10,,
2021-07-12 11:53:36 - U00020408 JOBS.UNIX.JSCH.TEST.AAA.003,JOBS, => 1900 ,2021-07-12 14:00:10.000,2021-07-12 14:00:20.000,10,,
2021-07-12 11:53:36 - U00020408 JOBS.UNIX.JSCH.TEST.AAA.001,JOBS, => 1900 ,2021-07-12 18:00:00.000,2021-07-12 19:00:00.000,3600,,
2021-07-12 11:53:36 - U00020408 JOBS.UNIX.JSCH.TEST.BBB.001,JOBS, => 1920 ,2021-07-12 19:00:00.000,2021-07-12 19:00:00.000,10,,
2021-07-12 11:53:36 - U00020408 JOBS.UNIX.JSCH.TEST.AAA.002,JOBS, => 1900 ,2021-07-12 19:00:00.000,2021-07-12 19:00:10.000,10,,
2021-07-12 11:53:36 - U00020408 JOBS.UNIX.JSCH.TEST.BBB.002,JOBS, => 1900 ,2021-07-12 19:00:00.000,2021-07-12 19:00:10.000,10,,
2021-07-12 11:53:36 - U00020408 JOBS.UNIX.JSCH.TEST.BBB.003,JOBS, => 1900 ,2021-07-12 19:00:10.000,2021-07-12 19:00:20.000,10,,
2021-07-12 11:53:36 - U00020408 JOBS.UNIX.JSCH.TEST.AAA.003,JOBS, => 1900 ,2021-07-12 19:00:10.000,2021-07-12 19:00:20.000,10,,
V12.3.6 (Windows with Postgres)
no obvious error
2021-07-12 11:52:40 - U00020824 Because of the entered forecast filters ('AUTOFORECAST', '', ''), 1 of 1 forecasts have been deleted.
2021-07-12 11:52:40 - U00020408 0000000000000000
2021-07-12 11:52:41 - U00020408 0000000000000000
2021-07-12 11:52:41 - U00020237 The object variable '&SQL#' in object: 'SCRI.STARTE_AUTOPROGNOSE', line: '00011' (RunID: '0001027016') has been created with the value 'SELECT fe_name,fe_otype, fe_status,fe_starttime,fe_endtime,fe_ert FROM fe where fe_otype = 'JOBS' ORDER BY fe_starttime' by using the command :PSET.
2021-07-12 11:52:41 - U00020206 Variable '&SQL#' was stored with value 'SELECT fe_name,fe_otype, fe_status,fe_starttime,fe_endtime,fe_ert FROM fe where fe_otype = 'JOBS' ORDER BY fe_starttime'.
2021-07-12 11:52:41 - U02000218 Text file (RunID '1027016') completed successfully. File: 'c:\temp\forcast_2021.07.12_115240.txt'.
2021-07-12 11:52:41 - U00007000 'EVENT.WINCMD' activated with RunID '0001026012'.
2021-07-12 11:52:43 - U00020408 Alle Objekte mit Status anders als 1900 und ohne Start-/Endezeit sind heute inaktiv!
2021-07-12 11:52:43 - U00020408 Objekt-Name , Typ , => Status-Code ,Startzeit , Endezeit , ERT
2021-07-12 11:52:43 - U00020408 JOBS.WIN.JSCH.TEST.AAA.001,JOBS, => 1900 ,2021-07-12 18:00:00,2021-07-12 19:00:00,3600,,
2021-07-12 11:52:43 - U00020408 JOBS.WIN.JSCH.TEST.AAA.002,JOBS, => 1900 ,2021-07-12 19:00:00,2021-07-12 19:00:01,1,,
2021-07-12 11:52:43 - U00020408 JOBS.WIN.JSCH.TEST.BBB.003,JOBS, => 1900 ,2021-07-12 19:00:00,2021-07-12 19:00:01,1,,
2021-07-12 11:52:43 - U00020408 JOBS.WIN.JSCH.TEST.BBB.002,JOBS, => 1921 ,2021-07-12 19:00:00,2021-07-12 19:00:00,1,,
2021-07-12 11:52:43 - U00020408 JOBS.WIN.JSCH.TEST.BBB.001,JOBS, => 1920 ,2021-07-12 19:00:00,2021-07-12 19:00:00,1,,
2021-07-12 11:52:43 - U00020408 JOBS.WIN.JSCH.TEST.AAA.003,JOBS, => 1900 ,2021-07-12 19:00:01,2021-07-12 19:00:02,1,,
2021-07-12 11:52:43 - U00020408 JOBS.WIN.JSCH.TEST.AAA.003,JOBS, => 1900 ,,,1,,
2021-07-12 11:52:43 - U00020408 JOBS.WIN.JSCH.TEST.AAA.002,JOBS, => 1900 ,,,1,,
2021-07-12 11:52:43 - U00020408 JOBS.WIN.JSCH.TEST.BBB.003,JOBS, => 1900 ,,,1,,
2021-07-12 11:52:43 - U00020408 JOBS.WIN.JSCH.TEST.BBB.002,JOBS, => 1900 ,,,1,,
2021-07-12 11:52:43 - U00020408 JOBS.WIN.JSCH.TEST.BBB.001,JOBS, => 1900 ,,,1,,
2021-07-12 11:52:43 - U00020408 JOBS.WIN.JSCH.TEST.AAA.001,JOBS, => 1900 ,,,3600,,
Cheers
Christoph
------------------------------
----------------------------------------------------------------
Automic AE Consultant and Trainer since 2000
----------------------------------------------------------------
------------------------------
Original Message:
Sent: 11-13-2019 12:08 PM
From: Pete Wirfs
Subject: Investigation: AutoForecast not working V12.3.0
I've seen others here state that they could no longer use AutoForecast, so I know I'm in good company. Under V11 we could never trust the script function to complete, so we were recalculating manually. Now that we are on V12, it seems that even doing a manual recalculation will not complete either. It generates some results but they are incomplete, which misleads my operations staff. (I've informed them to NOT TRUST IT at this time.)
So I stripped one of our schedule objects down to 3 tasks that can't AutoForecast. When I strip it down to 2, it can AutoForecast. So I'm doing some deep analysis to try to figure out what about that one task is blocking the process. I've also got support working on re-creating this problem today as I've been exporting all of the related objects to them.
Seriously hoping to get to the bottom of this... Without a healthy AutoForecast, any impromptu maintenance windows will be flying blind.
SYMPTOM:
Under "Forecasts", the AUTOFORECAST entry hangs up in "Preparing" state and never completes. It must be manually deleted before another attempt is allowed.
------------------------------
Pete
------------------------------