Hi Shravan,
Automic v12.2 is out of support since 2022-06-30. You should already have upgraded to a supported version.
Nevertheless you could start the objects using periodic execution.
regards,
Peter
------------------------------
Automic Certified Professional/Expert & Broadcom Knight
For AUTOMIC trainings please check
https://www.qskills.de/qs/workshops/automic/------------------------------
Original Message:
Sent: Mar 20, 2023 03:15 AM
From: Shravan shetty
Subject: Jobs in schedules(JSCH) not executing
Hi Community,
we have schedule where jobs are not executing and also after period turnaround time a new execution of JSCH is also not starting and it will stuck in the previous execution.
we found below in the reports -
U00011086 Schedule 'JSCH.JDE' (RunID '0017923157') starting ...
2023-03-17 21:56:49 - U00011088 Task 'JOBP.E1_A100AUTOPICK' does not start because the scheduled start time lies before the start time of 'JSCH.JDE'.
2023-03-17 21:56:49 - U00011088 Task 'EVNT.E1_A100ORDERRPT' does not start because the scheduled start time lies before the start time of 'JSCH.JDE'.
2023-03-17 21:56:49 - U00011088 Task 'EVNT.E1.A120.WMSSALES.2' does not start because the scheduled start time lies before the start time of 'JSCH.JDE'.
We have version 12.2.1 Automic. We are aware that, As per Broadcom, it is a bug in this version.
Upgradation may delay a month or two. So, Is there any workaround we can do to run these JSCH for now?
Regards,
ShravanShetty