|
Hello,
Let me answer some of my own questions.. I've tried some things at the
customer site, and this is what was discovered :
>>- Can you install Scheduler Agent on a system that allready was running
>> Scheduler Server ?
>> * will it delete the 'old' server images, or
>> * is it advised to use another directory for installation
You can install Scheduler Agent on a system along-side Scheduler
server. They can be active at the same time, and can make use of
the same license.... (probably not allowed to both use one
DECSCHEDULER license, but it works..
Scheduler installs all its stuff in SYS$SYSTEM/SYS$STARTUP etc.,
not in NSCHED$..
>>- If we 'misuse' a scheduler server to act as an agent,
>> * will it need TCP/IP for communication, or can it still use
>> DECnet ?
>> * will the 'server-acting-as-an-agent' have the functionality
>> that a real agent misses, like pre- and post-processing ?
A server CANNOT act as an agent ! At least, i don't get it working.
With 'agent' i mean running a job from a server on a remote system,
where the job is administered on the server, and there is no job
info on the node where the command/job is run.
If i create a job on a server to execute on a remote system, i
specify "<user>@<remote-node>. When i run the job i get the
following message :
Running job 100 on remote node BVGAXP...
545285006: final error on connect to socket 3
545285006: send failed
SEND_REMOTE_RUN failed, status : 211192530
%NSCHED-E-EXEBADRECV, failed to receive confirmation from executor node
Remote Node=<BVGAXP> Remote User=<DEC_BEHEER>
So, is it true that a server cannot be an agent at the same time ?
Regards,
Paul.
|
| Paul,
My response is preceeded by// below.
Raminder Bhatia
------------------------------------------------------------------------------------------------------------------
Hi,
I have some questions regarding POLYCENTER Scheduler V2.1B on OpenVMS,
whan used as Server and/or Agent.
Customer situation :
- lots of stand-alone OpenVMS systems, with Scheduler server installed
- most of them still use older versions, like V2.1A or V2.0A
- they have NAS licenses for all systems, so they can and will use UCX
The customer uses Scheduler now as servers, and synchronise jobs by
using remote dependencies. They want to move to a situation where one
OpenVMS Cluster (VAX) will be the Scheduler server, and all the others
are able to act as agents..
Since they allready have scheduler installed, and are in the posession
of Scheduler server licenses, we have some questions regarding the move
from server-servers to server-agents.
Questions:
- Can you install Scheduler Agent on a system that allready was running
Scheduler Server ?
//YES. THE AGENT LICENSE IS PART OF THE SERVER LICENSE AS LONG AS IT IS ON THE
//SAME SYSTEM.
* will it delete the 'old' server images, or
//NO.
* is it advised to use another directory for installation
//NOT NECESSARY. THE AGENT GETS INSTALLED UNDER A DIFFERENT DIRECTORY.
- If we 'misuse' a scheduler server to act as an agent,
* will it need TCP/IP for communication, or can it still use
DECnet ?
//COMMUNICATION BETWEEN A SERVER AND AN AGENT IS THROUGH TCP/IP (UCX).
* will the 'server-acting-as-an-agent' have the functionality
that a real agent misses, like pre- and post-processing ?
//THE AGENTS DO NOT HAVE PRE OR POST PROCESSING FUNCTIONS. MY
//SUGGESTION IS THAT SINCE YOU ALREADY HAVE SERVER LICENSES, WHY NOT
//USE THOSE TO PERFORM PRE AND POST FUNCTIONS.
- Can someone inform me what the latest version of the Scheduler Agent
for Digital UNIX is, which can be used with Scheduler Server for OpenVMS
V2.1B-9 ?
//IT IS V2.1B-1.
Regards,
Raminder Bhatia
|