I hope I understand your question correctly... To run more than one dsmcad command, you need multiple option files which point to separate stanzas in the dsm.sys file. with dsmc sched you could specify -servername, but this is not accepted by dsmcad, just -optfile. BTW if you give dsmcad an option that it doesn't understand or an options file that doesn't exist, it still starts using defaults. I'd prefer it didn't, but that's just me.
HTH Steve Harris AIX and TSM Admin Queensland Health Brisbane Australia >>> [EMAIL PROTECTED] 31/10/2002 10:21:15 >>> Is it possible to run both a B-A client and a TDP client on the same machine both listening on port 1501? Can I have the dsmcad process listening for 2 different schedules (an incremental backup and a command execution) and start the "TSM Client Schedulers" at different times? -- Joshua S. Bassi IBM Certified - AIX 4/5L, SAN, Shark Tivoli Certified Consultant - ADSM/TSM eServer Systems Expert -pSeries HACMP AIX, HACMP, Storage, TSM Consultant Cell (831) 595-3962 [EMAIL PROTECTED] -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU] On Behalf Of Jin Bae Chi Sent: Wednesday, October 30, 2002 9:21 AM To: [EMAIL PROTECTED] Subject: Re: Automating RMAN Backup Through TSM When using the TSM scheduler to automate the TDP Oracle backups, the differences in how these two clients work must be taken into account. - The scheduler runs as root and would need passwordaccess generate. - The TDP Oracle backup runs as an Oracle user and need passwordaccess prompt. In this one dsm.sys file, there will normally be more than one ServerName stanza when using the TDP Oracle on the same machine. One ServerName stanza for the filesystem backups and another ServerName stanza for the TDP Oracle backups (which need passwordaccess prompt). To assist with setting up the TSM Scheduler for the TDP Oracle node, you would need to create a third ServerName stanza in this dsm.sys file. In general, the dsm.sys file would be similar to the following: servername TSMbackup COMMMETHOD tcpip TCPServeraddress xxx.xxx.xxx.xxx TCPPORT 1500 NODENAME Client PASSWORDACCESS generate servername TSMOracle COMMMETHOD tcpip TCPServeraddress xxx.xxx.xxx.xxx TCPPORT 1500 PASSWORDACCESS prompt servername TDPSched COMMMETHOD tcpip TCPServeraddress xxx.xxx.xxx.xxx TCPPORT 1500 NODENAME TDPNode PASSWORDACCESS generate You would have three dsm.opt files. One for the Backup/Archive client that would normally be located in the /opt/tivoli/tsm/client/ba/bin directory. Based on the dsm.sys example above, this would contain the line: servername TSMbackup There would be a second dsm.opt file (which could have a different filename, such as dsmoracle.opt) for the TDP for Oracle. Based on the dsm.sys example this user option file for the Oracle client would contain the line: servername TSMOracle and would have passwordaccess prompt. There would be a third dsm.opt file (which could have a different filename, such as dsmsched.opt) for the TDP for Oracle scheduler. Based on the dsm.sys example this user option file for the Oracle client would contain the line: servername TDPSched and would have passwordaccess generate and have the NodeName for the TDP Oracle client specified. Environment variables would need to be utilized with the Oracle backup to point to the user option file. This would be specified in the TDPO_OPTFILE with the DSMI_ORC_CONFIG variable. For example: DSMI_ORC_CONFIG /opt/tivol/tsm/client/oracle/bin/dsmoracle.opt When starting the TSM Scheduler for the TDP Oracle backups, you will need to use the -SErvername parameter and specify which stanza should be used. Based on the example dsm.sys the scheduler command would be such as: dsmc sched -SE=TDPSched Neil Rasmussen Software Development TDP for Oracle [EMAIL PROTECTED] ********************************************************************** This e-mail, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost if you receive it and you are not the intended recipient(s), or if it is transmitted/ received in error. Any unauthorised use, alteration, disclosure, distribution or review of this e-mail is prohibited. It may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this e-mail in error, you are asked to immediately notify the sender by telephone or by return e-mail. You should also delete this e-mail message and destroy any hard copies produced. **********************************************************************