You have to run several parallell job streams.  The easiest way to do that,
is to change your backup schedule from INCREMENTAL to COMMAND, and insert
the name of a "parent" backup script as OBJECT, e.g.
/opt/IBMDSMba5/adsm_backup

That script has to start several "child" backup scripts (in background),
doing the real backup.  It's a good idea to let the parent script wait for
the child scripts to complete before returning control to the scheduler.
(This will give the scheduler an idea of wether the backup is running or
not.)

Each child scripts has to set and export environement variable DSM_CONFIG
to its own dsm.opt file, e.g. /opt/IBMDSMba5/dsm.opt_1 .  Afterwords it
runs dsmc:

dsmc incr > /<Your backup log directory>/backup_log_1 2>&1

The clue is that you have to split your total number of filesystems across
the different dsm.opt files, each file containing a set of DOMAIN records
to assign a filesystem to a specific job stream.

WARNING:  This has to be maintained manually, and filesystems NOT defined
on any DOMAIN record, will NEVER be backed up!

Bjorn Harald Sandvik
Statoil

To:       ADSM-L @ VM.MARIST.EDU
cc:        (bcc: Bjørn Harald Sandvik)
From:     evanloon @ KLM.NL @ INTERNET
Date:     03.11.97 19:13:47
Subject:  Processor usage Sun client



Content-type: text/plain; charset=us-ascii


Hi ADSM-ers!
When my Sun client is backing up I see that it is only using two processors
while there are 6 processors available. The remaining 4 are just doing
nothing.
Is there any way to control this?
Thanks in advance for any reply!
Kindest regards,
Eric van Loon