OSPool jobs are scheduled by HTCondor, not Slurm. You describe a job in a plain-text submit file - what to run, what to bring back, and how much CPU, memory and disk it needs - and submit it with condor_submit from your /home directory, the only directory you may submit from. See [Overview: Submit Jobs to the OSPool using HTCondor].
There are no queues or partitions to choose between. HTCondor matchmaking sends each job to whichever contributed machine satisfies what it asked for, so you select hardware by stating requirements in the submit file - request_cpus, request_memory, request_disk - not by naming a partition. Jobs are single-node, and a bigger request matches fewer machines and waits longer. Most of the capacity is opportunistic: the site that owns a machine can interrupt your job at any time and HTCondor requeues it to start again from the beginning, so work that cannot tolerate a restart must checkpoint.
There is no per-queue wall clock either. Each job declares a +JobDurationCategory instead - Medium, expected under 10 hours and held after 20, or Long, expected under 20 and held after 40 - and Medium applies if you set nothing. An overrun job is held, not killed, so you can resubmit it as Long. See [OSPool Job Duration Categories].
Two more traps. Keep no more than 10,000 jobs in the queue at once unless you add max_idle to the submit file. And bring your software with you, in a container or as a portable binary: the machines your jobs land on belong to other sites and are not yours to install on. OSPool access does not consume an ACCESS allocation by default. Coming from Slurm, start with [OSPool Convert your workflow from Slurm to HTCondor].