HP OpenVMS Installation *No Longer Supported*
Installation of the ActiveBatch Execution Agent for HP OpenVMS is performed using the VMSINSTAL procedure. No LMF PAK is required since all licensing is performed on the Job Scheduler machine. The saveset name is ABATOVMS0110.A. If you’ve received this file from a web site or via FTP you will need to issue the following VMS command to restore the file’s attributes:
$ SET FILE/ATTRIB=(ORG:SEQ,RFM:FIX,LRL=32256) ABATOVMS0120.A
Then you can invoke @SYS$UPDATE:VMSINSTAL to install the product. Product name is ABATOVMS0120.
Prior to starting the Execution Agent you must first start one of the following TCP/IP stacks: HP TCP/IP services, Process Software MultiNet or TCPware. The ActiveBatch Execution Agent for HP OpenVMS requires access to TCP/IP services. By default, port 3655 is used. You must have connectivity to this machine from the Job Scheduler machine(s).
The file ABATOVMS_PRODUCT:AbatEmgr.Conf is a standard ASCII file that contains various parameters that can affect the Execution Agent’s run-time characteristics. The only parameter you may change is CPUSpeed. This parameter is used by generic queues to help determine workload balancing.
To notify the Execution Agent of a real-time change in configuration parameters, use the following command:
$ ABATCOMMAND :== $ABATOVMS_PRODUCT:ABATCOMMAND.EXE
$ ABATCOMMAND PARAMCHANGE <port>
Where “port” is a non-standard Execution Agent port number. For the standard port, this parameter can be omitted.
Note: For Archive/Unarchive Jobs Library Job Steps you must define the logical ABAT_ZIP to contain the device/directory pointing to a ZIP.EXE/UNZIP.EXE image. The logical must be system-wide.
HP OpenVMS Startup and Shutdown
To start the Execution Agent, invoke @SYS$STARTUP:ABATOVMS_STARTUP. You will normally place this file into your site-specific startup procedure after the TCP/IP software has been started.
One way to kill the process is (excluding quotes when the commands are run):
-
Run "show system" and look for ABATEMGR
-
Run "stop/id=<id_from_step1>"
HP OpenVMS Batch Job Environment and Considerations
Note: See VMSBatchQueue parameter below introduced in V8 SP3 provides a better alternative than the use of ABATSETBATCH.
The Batch job is started as a detached process. Two types of batch file extensions are supported: .COM and .EXE. All file specifications entered must adhere to VMS specifications. This means you can also specify logical names or any other constructions that would be supported on a VMS system. The ActiveBatch environment variables are created as job-wide logical names. All batch jobs are executed under the user security context as specified in the Job Execution tab. Please note, by default, that the OpenVMS lexical F$MODE will return “INTERACTIVE” and not “BATCH” (unless you invoke ABATSETBATCH to change mode to a BATCH job) during the execution of SYLOGIN.COM and LOGIN.COM since this process is not running under the VMS Batch Symbiont.
To use the ActiveBatch run-time utilities we recommend you create the following symbol as part of your LOGIN or SYLOGIN procedure:
$ ABATCHKPT :== $ABATOVMS_PRODUCT:ABATCHKPT.EXE
$ ABATSET :== $ABATOVMS_PRODUCT:ABATSET.EXE
$ ABATDATESUB :== $ABATOVMS_PRODUCT:ABATDATESUB.EXE
$ ABATSETBATCH :== $ABATOVMS_PRODUCT:ABATSETBATCH.EXE
By default (unless VMSBatchQueue is specified), ABATSETBATCH is executed to allow the use of VMS F$MODE and SET OUTPUT_RATE. A side-effect of this is that VMS Accounting will not produce Process accounting records (Image accounting is still available). If you decide that you don’t want to execute ABATSETBATCH by default, you can disable this feature through the Configuration File or on a job-by-job basis by enabling the variable ABAT_SETBATCH and selecting “export as environment variable”.