Yes, any job that isn't required to be an interactive job can (and possibly should) be a batch job.
Generally, a program that doesn't open a display file (and doesn't call any other program that opens a display file) can be submitted for batch processing. Some commands require interactive screens and are marked for interactive use; programs can't successfully execute those commands in batch.
Is the question about the meaning of "batch job"? Is it about the uses or purpose of batch?
The use of the word "transferred" puts an odd twist to the question. It implies that a job is an interactive and that it is unknown if it can be "transferred" to batch. Generally, an interactive job can't be transferred to batch because interactive jobs have display devices associated with them, and "batch" subsystems usually don't have workstation entries.
Depending on what you want, anything can be made into a batch job, you just need to be able to write up a script for it. Once that is done and tested and shows no ill effects, then you should be able to run it on the network.
One good example is removing a folder that Adobe leaves when it upgrades itself and when you do a vulnerability scan, it comes up dirty. You find the folder, you know the path, you are SURE that deleting the folder will not cause any problems, write the script and then run it on the network. We do it all the time. It is the best way to clean up a lot of lose files that are causing such problems when scanning.
Hope this helps and good luck