Daniel,
Do a Q status and check out MAXSESSIONS and MAXSCHEDSESSIONS
Use the SET MAXSCHEDSESSIONS command to regulate the number of sessions
that the server can use for processing scheduled work. This command
specifies the
maximum number of scheduled sessions as a percentage of the total number
of server
sessions available.
Hope this helps.
Regards,
Eric P. Gruber
RISCmanagement, Inc.
ADSM Certified Instructor/Consultant
-----Original Message-----
From: Daniel Casey [mailto:jistdc1 AT MAIL.JBHUNT DOT COM]
Sent: Thursday, March 04, 1999 12:47 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: adsm client on unix
ADSM Server MVS 3.1.2.0
ADSM Client UNIX (os/390 Unix System Servies) 2.1.01
Anyone have any idea why on my UNIX client, the backups
fail if I start the dsmc schedule BEFORE the server has
me scheduled, but if I start the schedule AFTER the
server's
scheduled time, it works?
So, let's say that the server is scheduled to backup my
UNIX client at 09:00. What I would normally do is start
the
schedule on the client at 08:45 or 08:55...then, when
09:00
rolls around, the ADSM server says he cannot contact the
UNIX client.
But, if I kill that schedule process and start another
one,
let's say at 09:05, it works. The backup starts without
a
hitch.
03/03/1999 09:25:03 Querying server for next scheduled
event.
03/03/1999 09:25:03 Next operation scheduled:
03/03/1999 09:25:03
-------------------------------------------------------
03/03/1999 09:25:03 Schedule Name: TEST
03/03/1999 09:25:03 Schedule Name: TEST
03/03/1999 09:25:03 Action: Incremental
03/03/1999 09:25:03 Objects:
03/03/1999 09:25:03 Options:
03/03/1999 09:25:03 Server Window Start: 09:23:00 on
03/03/1999
03/03/1999 09:25:03
-------------------------------------------------------
So, from this you can tell that the dsmc schedule
So, from this you can tell that the dsmc schedule
process started
AFTER the Server was scheduled to start the backup.
Is this normal? The dsm.sys file is set to PROMPTED.
Thanks,
Daniel
|