With Spring Boot 3, there is no need for @EnableBatchProcessing. If you add it, the auto-configuration of Spring Batch (including the automatic launching of jobs at startup) will back off.

This is mentioned in the migration guide of Spring Boot 3.

EDIT: Not able to reproduce the issue. Things are working as expected with Spring Batch 5 and Spring Boot 3.

$>curl https://start.spring.io/starter.zip -d dependencies=h2,batch -d type=maven-project -o my-batch-job.zip
$>unzip my-batch-job.zip
$> # Paste AbacusJobConfiguration and MyTasklet code in the demo package + add imports
$>./mvnw package
$>./mvnw spring-boot:run

This prints:

  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/
 :: Spring Boot ::                (v3.0.2)

2023-01-31T07:48:24.206+01:00  INFO 91983 --- [           main] com.example.demo.DemoApplicationTests    : Starting DemoApplicationTests using Java 17.0.4 with PID 91983 (started by mbenhassine in /tmp/so75287102)
2023-01-31T07:48:24.207+01:00  INFO 91983 --- [           main] com.example.demo.DemoApplicationTests    : No active profile set, falling back to 1 default profile: "default"
2023-01-31T07:48:24.625+01:00  INFO 91983 --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Starting...
2023-01-31T07:48:24.779+01:00  INFO 91983 --- [           main] com.zaxxer.hikari.pool.HikariPool        : HikariPool-1 - Added connection conn0: url=jdbc:h2:mem:0b237f7c-fec8-446f-b2ac-086801ddb7fd user=SA
2023-01-31T07:48:24.780+01:00  INFO 91983 --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Start completed.
2023-01-31T07:48:24.858+01:00  INFO 91983 --- [           main] c.example.demo.AbacusJobConfiguration    : Building tasklet
2023-01-31T07:48:24.860+01:00  INFO 91983 --- [           main] c.example.demo.AbacusJobConfiguration    : Building step
2023-01-31T07:48:24.957+01:00  INFO 91983 --- [           main] com.example.demo.DemoApplicationTests    : Started DemoApplicationTests in 0.91 seconds (process running for 1.585)
2023-01-31T07:48:24.958+01:00  INFO 91983 --- [           main] o.s.b.a.b.JobLauncherApplicationRunner   : Running default command line with: []
2023-01-31T07:48:24.990+01:00  INFO 91983 --- [           main] o.s.b.c.l.support.SimpleJobLauncher      : Job: [SimpleJob: [name=myJob]] launched with the following parameters: [{'run.id':'{value=1, type=class java.lang.Long, identifying=true}'}]
2023-01-31T07:48:25.009+01:00  INFO 91983 --- [           main] o.s.batch.core.job.SimpleStepHandler     : Executing step: [myTasklet]
Running MyTasklet
2023-01-31T07:48:25.017+01:00  INFO 91983 --- [           main] o.s.batch.core.step.AbstractStep         : Step: [myTasklet] executed in 8ms
2023-01-31T07:48:25.025+01:00  INFO 91983 --- [           main] o.s.b.c.l.support.SimpleJobLauncher      : Job: [SimpleJob: [name=myJob]] completed with the following parameters: [{'run.id':'{value=1, type=class java.lang.Long, identifying=true}'}] and the following status: [COMPLETED] in 23ms
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.556 s - in com.example.demo.DemoApplicationTests
2023-01-31T07:48:25.312+01:00  INFO 91983 --- [ionShutdownHook] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Shutdown initiated...
2023-01-31T07:48:25.315+01:00  INFO 91983 --- [ionShutdownHook] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Shutdown completed.

The JobRepository has always been mandatory in Spring Batch. What has changed between v4 and v5 is that the Map-based implementation (that was used by default when there is no datasource defined) was removed.

Therefore, you either have to define a datasource (could be an embedded one) and use the JDBC-based JobRepository, or provide a custom JobRepository implementation according to your needs.