Investigation: AutoForecast not working V12.3.0

[Pete Wirfs]

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
------------------------------

[Thomas Brodrecht]

Hello, Pete,
after the upgrade from V12.0.7 to V12.3 the AUTOFORECAST also does not finish.
We haven't been able to find a cause yet.
However, if we create a forecast for a single scheduler from the perspective of process assembly, we always get the status "ENDED_TIMEOUT start time exceeded" for the contained objects. In reality at least some of these objects should start at a certain time, while others should be skipped due to calendar conditions.
In this case, the FORECASTS states should also be treated with caution!
And yes, some of these forecasts do not come to an end too.
We have created Tickest for both cases, but have not received a usable answer yet.

Regards
Thomas

[Frantisek Elias]

Hi all, we have 2 confirmed bugs with forecast in awaV12.3.0hf2 from Automic support:

{Case#20078659} ## Forecast is not working properly for schedule object - timezone is ignored

Response Update: Hi Frantisek,

I was able to reproduce this issue. It has been sent to Engineering to be patche up.

{Case#20078672} ## Forecast is not working for object with mx runtime defined (frozen in preparing) has been updated
I was able to reproduce this issue. It has been sent to Engineering to be patche up.

Best Regards,

[Pete Wirfs]

Thank you for confirming it is not just us.  My support call has not yet gotten a response.  I suspect that the forecast function is so bad off, that support is probably sitting back and waiting for engineering to go through it and report the finding and correction of some of these issues.

In the mean time, I'm educating my staff on how to fly blind during maintenance cycles;
1. Go ahead and shut down AE systems for maintenance when necessary.
2. After AE system restart, review all schedule monitors to see exactly what was missed, and take appropriate action.

We are doing a maintenance cycle this Sunday morning to apply patches to our PROD AE Windows server OS, and we'll see how it goes.

------------------------------
Pete
------------------------------

[Thomas Brodrecht]

Good news on the topic "Forecast".
We have received the following information from Broadcom Support.
--snip--
This issue is already reported by many other customer and it has been already investigated by R&D team.
Issue description: Forecast not completing as per expectation and it doesn't not end from preparing state.
This issue is fixed in the upcoming release, that is 12.3.2
Which will be available for download from Feb 24th 2020.
Please upgrade to the fixed version to resolve the issue.
--snap

[Bethel Ademowore]

Great news - thanks!

[Pete Wirfs]

Just yesterday I was re-creating the Forecast problems with WP traces turned on as per American support.  I will inform them that 12.3.2 is supposed to have repaired this.  I'll ask if they can get an advanced copy of the 12.3.2 documentation.

------------------------------
Pete
------------------------------

[Bethel Ademowore]

This is good to know. Tried executing my first Recalculation in 12.3.0 today and it got stuck on preparing, then caused the AWI to stop responding for all users. I had to delete the forecast I'd tried running (for one agent over a 5 hour period) through the thick client, and restart the JWPs and JCP. I hope they never get rid of the thick client or we will be dead in the water.

[Jared Kessans]

We had major issues with the forecast in v9 and v10, but v12.0 has been pretty decent for the most part other than some strange occurrences.  Currently with the v12.0, we have two schedules that fault within the forecast.  

Have you looked at the last message that is generated on those that are stuck in preparing status?

With the two faults that we encountered, one I just found was due to the use of an invalid calendar object.  The other is due to the use an agent group in a file transfer for the source and a variable listed in the destination.  The second forecast issue is probably a bug since the variable was really just a single host, but I haven't taken the time to open a ticket on it.

[Ron Gates]

i have 12.3.2.hf1 and it still hangs when doing an AutoForecast...
Is there a specific hotfix version that resolved this issue?

[Markus Embacher]

Please check if in your system there is an object having the same name as an agent. If yes, please rename the object.

[Kenneth Hutchins]

I was able to get AutoForecast to work.

I tested the forecast option on every Job Plan in my environment. (Luckily we only have a 100 JPs, not ideal for those who have 100s or 1000s of Job Plans). 

The Job Plans which did not generate an Forecast, I had to export and Import them back in using keep in folder and replace the existing options. 

------------------------------
DevOps Engineer
ULLICO
------------------------------

[Alain Moisy]

For those who wants to do this test + export/import on all their JobPlan / Workflowa small solution :

1 - Define an SQL variable that returns all the JobPlan aka Worflow names from the client. (OH_Name = *,  OH_OType = 'JOBP', OH_Client = client number and OH_DeleteFlag = 0 to get only the current version of the object)
2 - For each object found, run the FORECAST_OBJECT command
3 - For each object in error in the FORECAST_OBJECT command, like indicated by Kenneth, run the EXPORT followed by the IMPORT command.

All this using a PREP_PROCESS_VAR command to automate the process.

Just check the value of SCR_LOOPCHK_TIME in the UC_SYSTEMS_SETTINGS to avoid long waiting time if you have a lot of JobPlan / Workflow.

Regards.
Alain

[Pete Wirfs]

I have written a home-grown forecasting tool.  It only forecasts events that are scheduled via JSCH objects. I'm interested in sharing it with someone else for testing purposes as I've exhausted all of the things I can test here.  It's pretty simple in its moving parts; you provide a date parameter to a script that queries the database and writes the forecast results for one calendar day into a CSV.  

Any takers?  Send me a private message with your email and I'll send you a copy.

EDIT:  I now have three volunteers.  I will work with them on 
EDIT:  validating the tool, and post results back here.

EDIT2: Testers have already revealed several improvements to me. 
EDIT2: For instance I had hard-coded several references to our local CALE object.
EDIT2: And problems with different default date formats.
EDIT2: Improvements are being made....!  (Thank you testers!)

EDIT3: At least one tester has claimed success after uncovering several
EDIT3: defects that are now repaired.  I'm also maintaining a list
EDIT3: of site-mods that must be applied.
EDIT3: If you would like to try it as well, send me a private message with a target email for me to send the code to!

------------------------------
Pete Wirfs
SAIF Corporation
Salem Oregon USA
------------------------------

[Pete Wirfs]

For those of you that I've shared my code with, I've uncovered a defect in my forecast script.

The defect is with the case statement that is intended to filter out unwanted objects from the forecast report.  It was only working properly for those objects that needed calendar hits.  I had to make a modification so that it would also filter out objects that want NO calendar hits.
This:

: switch &Task#
: case 'TASK1'
: case 'TASK2'
: set &SkipMe# = "YES"

Needs to be changed to this;

: switch &Task#
: case 'TASK1'
: case 'TASK2'
: if &CalRule# = 3
: set &SkipMe# = "NO"
: else
: set &SkipMe# = "YES"
: endif

------------------------------
Pete Wirfs
SAIF Corporation
Salem Oregon USA
------------------------------

[Pete Wirfs]

The forecast script I wrote fails to forecast the iterations that can occur from a scheduled EVNT.TIME.* object.   I hope to work on this omission as time permits.

------------------------------
Pete Wirfs
SAIF Corporation
Salem Oregon USA
------------------------------

[Prakash Subramanian]

Hi Pete,
Facing forecast report creation issue after upgrading from 12.2.2 HF3 into 12.3.4 HF1 version. For us EVNT schedule is working fine. But other regular JOBPs not generating any fore cast. In face we have calendar for all JOBPs in JSCH. We see some java exception and created ticket with automic support. Waiting for their response. 

Did you create new script to generate the fore cast report? If so, can you please share the full script? I see above only partial script. Appreciate your help.

Thanks,
Prakash S

[Pete Wirfs]

@Prakash Subramanian  Private-message me with your email address to receive a copy and a list of mods you must apply.

The capabilities of this script solution are limited. It was designed to only forecast JSCH tasks and it does not forecast tasks that repeat themselves. ​

------------------------------
Pete Wirfs
SAIF Corporation
Salem Oregon USA
------------------------------

[Christoph Rekers]

Hi @Pete Wirfs

I 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
----------------------------------------------------------------
------------------------------

[Christoph Rekers]

Hi @Pete Wirfs,

I 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. with EVNTs 

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
----------------------------------------------------------------
------------------------------

[Christoph Rekers]

Hi @Pete Wirfs ​

I found that with V12.3.6 HF the AUTO_FORCAST seem's to be fixed  -as far as my testing went...

I created a Master-JOBP with one Sub-JOBP. The latter contains 3 Jobs. One is bend to a calendar ("Christmas"), one is set to inactive (General=>Properties). The V12.3.5-Forcast doesn't recognise that the inactive task is set to inactive (which is obviously wrong). The Master-JOBP is executed daily at 6pm by a JSCH.

Furthermore I created a second JSCH, which executes the Master-JOBP at 1pm. However the Master-JOBP is set to inactive within the JSCH. The Forecast says, the Master-JOBP will run today...WTF?

Well, with V12.3.6 (Windows with Postgres) it works well, inactive Workflow tasks are recognised as such! WOW, after all....However, the Childs of the inactive Master-JOBP aren't displayed as inactive, they just don't get a start and end time.

I ran an AUTO_FORECAST() with the help of a SCRI, PREP_PROCESS_VAR'ed a VARA.SQLI and wrote the output to a text file, which I afterwards pulled back (PREP_PROCESS(agent,xxxCMD,filter,"CMD=type/cat my.file", LOGIN). Here's the result (only JOBS are displayed)



Hope this helps

Cheers
Christoph 



V12.3.5 (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 (at least not obviously wrong)

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,,

------------------------------
----------------------------------------------------------------
Automic AE Consultant and Trainer since 2000
----------------------------------------------------------------
------------------------------

[Christoph Rekers]

Hi @Pete Wirfs ​

I found that with V12.3.6 HF the AUTO_FORCAST seem's to be fixed  -as far as my testing went...

I created a Master-JOBP with one Sub-JOBP. The latter contains 3 Jobs. One is bend to a calendar ("Christmas"), one is set to inactive (General=>Properties). The V12.3.5-Forcast doesn't recognise that the inactive task is set to inactive (which is obviously wrong). The Master-JOBP is executed daily at 6pm by a JSCH.

Furthermore I created a second JSCH, which executes the Master-JOBP at 1pm. However the Master-JOBP is set to inactive within the JSCH. The Forecast says, the Master-JOBP will run today...WTF?

Well, with V12.3.6 (Windows with Postgres) it works well, inactive Workflow tasks are recognised as such! WOW, after all....However, the Childs of the inactive Master-JOBP aren't displayed as inactive, they just don't get a start and end time.

I ran an AUTO_FORECAST() with the help of a SCRI, PREP_PROCESS_VAR'ed a VARA.SQLI and wrote the output to a text file, which I afterwards pulled back (PREP_PROCESS(agent,xxxCMD,filter,"CMD=type/cat my.file", LOGIN). Here's the result (only JOBS are displayed)



Hope this helps

Cheers
Christoph 



V12.3.5 (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 (at least not obviously wrong)

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,,

------------------------------
----------------------------------------------------------------
Automic AE Consultant and Trainer since 2000
----------------------------------------------------------------
------------------------------

[Christoph Rekers]

test

------------------------------
----------------------------------------------------------------
Automic AE Consultant and Trainer since 2000
----------------------------------------------------------------
------------------------------