|
HP OpenVMS Systemsask the wizard |
|
The Question is: VMS Version: All HSCPAD (SET HOST/DUP...) in batch? Why do the %%%PAD programs demand that their SYS$INPUT point to a terminal class device? We have a VERY large shop here where in order to solve the problems associated with shadow copies, we've chosen to let the HSJ50's do mirror copies instead - they're *TONS* faster, the impact on cluster-wide I/O is very low and the entire load is local to the controller pair. However, the best we've been able to get is the unsupported freeware program HSDSA. This program is unsupported, no source code is available, it's not written very well (doesn't understand EOF on its SYS$INPUT stream), it inserts superfluous blank lines in the data coming back from the HSJs and does not allow for easy determination of whether a command succeeded or not. How do we tell Compaq that we need something that we can use in an OpenVMS batch job, preferably a command like: $ DUP/NODE=HSJ001/TASK=CLI/OUTPUT=outfile hsj_command_string ...which sets $STATUS as appropriate to the completion code of the command on the HSJ? Please don't suggest SWCC (Storage Works Command Console). Remember - we're an OpenVMS shop. We need to command the HSJs from within an OpenVMS batch job in a lights-out, unattended operation (that means no operator assistance, no GUIs). Thanx in advance for any help you can offer. David J. Dachtera Advocate Health Care The Answer is :
Please be aware of the ALPDUP01_062 ECO kit.
The following kludge (or similar) may be of interest:
$ SPAWN/WAIT/NOLOG/OUTPUT=OPA0: -
SET HOST/DUP/SERVER=MSCP$DUP/TASK='task'/NOLOG 'Node'
Pseudo-terminals could also be used, rather than OPA0:.
The OpenVMS Wizard will check for an updated version of the HSDSA_SCRIPT
for inclusion on the OpenVMS Freeware, and will pass this request along
to OpenVMS Product Management.
|