Job Management Manager OpenVMS Installation

Examples of New Installations › Job Management Manager OpenVMS Installation

Job Management Manager OpenVMS Installation

The following example shows the log file from a sample installation of the manager.

$ run $3$lda1:[000000]setup_alpha
UnZipSFX 5.20 of 30 April 1996, by Info-ZIP (Zip-Bugs@wkuvx1.wku.edu).
UnZipSFX is distributed by CA, Inc., and has been modified to spawn a subprocess
that installs either a product or a product patch kit. The original
distributors of UnZipSFX cannot and do not support CA's modified version.
Please see the Acknowledgements section of the CA OpenVMS product documentation
for more information.
inflating: ca$setup.com
inflating: installhelp.hlp
inflating: cajm_product.key
inflating: cajm$readme.txt
Setup location: $3$LDA1:[000000]

CA Job Management for OpenVMS

-----------------------------

PRODUCT

1 Job Management Manager Install
2 Job Management Agent Install

I CA NSM/CCS Integration Help
P Product Readme
H Install Help
E Exit

Please Enter the Number of the Product you wish to
install >>>> 1
%DCL-S-SPAWNED, process SYSTEM_52491 spawned
%DCL-S-ATTACHED, terminal now attached to process SYSTEM_52491
UnZipSFX 5.20 of 30 April 1996, by Info-ZIP (Zip-Bugs@wkuvx1.wku.edu).
UnZipSFX is distributed by CA, Inc., and has been modified to spawn a subprocess
that installs either a product or a product patch kit. The original
distributors of UnZipSFX cannot and do not support CA's modified version.
Please see the Acknowledgements section of the CA OpenVMS product documentation
for more information.
inflating: ca$setup.ini
inflating: ca$setup.com
inflating: unzip_alpha.exe
inflating: unzip_ia64.exe
Platform type : ALPHA
OS version : V7.3
Setup location: $3$LDA1:[000000.ENU.OPENVMS.JOBMANAGER]
Product Kit : $3$LDA1:[000000.ENU.OPENVMS.JOBMANAGER]UJMMGR_UNI_0000_yymmdd_V031.ZIP;1
* Enter the device and directory to unzip the save-sets, 110000 blocks of temp space needed [sys$common:[CA$SETUP]]:
UNZIP location: SYS$SYSROOT:[SYSMGR]UNZIP_ALPHA.EXE;1
Unzipping installation media ... Please be patient ...

OpenVMS AXP Software Product Installation Procedure V7.3-2

It is 23-NOV-2011 at 10:40.

Enter a question mark (?) at any time for help.

%VMSINSTAL-W-ACTIVE, The following processes are still active:
TCPIP$FTP_1
* Do you want to continue anyway [NO]? y
* Are you satisfied with the backup of your system disk [YES]?

The following products will be processed:

UJMMGR_UNI_0000_yymmdd_V V3.1

Beginning installation of UJMMGR_UNI_0000_yymmdd_V V3.1 at 10:40

%VMSINSTAL-I-RESTORE, Restoring product save set A ...
%VMSINSTAL-I-RESTORE, Restoring product save set Y ...

* DO YOU ACCEPT THE TERMS AND CONDITIONS OF THIS AGREEMENT AS SET FORTH IN THE LICENSE AGREEMENT (YES (Y) / NO (N) / VIEW (V)) [N]:
y

%VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[CAI$REGISTRY].

* Do you want to run the IVP after the installation (Product Startup Required) [YES]?

The product will be started and the IVP will run automatically at the end of this install.

* Do you want to purge files replaced by this installation [YES]?

The DECwindows/MOTIF components of this software are optional

* Do you want to install the DECwindows/MOTIF components [YES]?

This product needs a TCP/IP network stack installed and
started on this node. You can use TCPWARE, MULTINET or
HP TCP/IP Services.

The TCP/IP stack TCP/IP Services is up and running...

Support for remote agent command execution is an available option.

* Do you want support for remote Agent command execution [YES]?

The installation procedure will prompt you for pathnames to two distinct
areas: cluster-common files area and node-specific files area.
When prompted, enter the full pathname of selected root directories,
including device names.

o Cluster Common files area
Contains data files and scripts which are shared by all cluster nodes.
It must be on a cluster-common non-DFS device.
Default value SYS$COMMON:[NSCHED] is intended for homogeneous clusters
and stand-alone nodes. It will NOT work for clusters that have different
system disks for different nodes.
Directories [DATA] and [COM] will be created under the path you specify.
Logical names NSCHED$DATA and NSCHED$COM will be associated accordingly.

o Machine architecture specific files area
Contains executables and other files which are specific to the hardware
architecture and/or OpenVMS version of the node.
A single set of executables can be shared for nodes with the same
architecture and OpenVMS version, to save disk space. For other cases
be sure to specify a directory that is specific to the local node.
The default value SYS$COMMON:[NSCHED] is a valid choice for stand-alone
nodes and clustered nodes with a shared system disk.
Directory [EXE] will be created under the path you specify.
Logical name NSCHED$EXE will be associated with this directory.

o Disk space required
Initial cluster-common NSCHED$ area requires a total of 5,000 blocks of
disk space. Node architecture specific area requires about 25,000 blocks.
If this installation is an upgrade from a previous version, additional
disk space (equal to the current total size of NSCHED$ directory) will be
required to backup your current files.
If you do not have sufficient space, abort the installation by pressing
CTRL-Y at this time.

* Enter the full pathname for CA Job Management - (cluster) common files [SYS$COMMON:[NSCHED]]:

Selected pathname: SYS$COMMON:[NSCHED]

* Is that correct [Y]?

* Enter the full pathname for CA Job Management - node specific files [SYS$COMMON:[NSCHED]]:

Selected pathname: SYS$COMMON:[NSCHED]

* Is that correct [Y]?
%VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[NSCHED].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[NSCHED].
%CREATE-I-EXISTS, SYS$COMMON:[NSCHED] already exists
%VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[NSCHED.DATA].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[NSCHED.COM].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[NSCHED.EXE].

** NOTE **

If you are installing on a cluster that has mixed versions,
mixed architectures, or uses different IP stacks in the cluster,
you MUST install on SYS$SPECIFIC. Otherwise, you may use the
default of SYS$COMMON.

* Enter the full pathname for the CA Common Services root directory [SYS$COMMON:[UNIVMS]]:

Selected pathname: SYS$COMMON:[UNIVMS]

* Is that correct [Y]?
%VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[UNIVMS].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory CAPOLY$BIN.
%VMSINSTAL-I-SYSDIR, This product creates system disk directory CAPOLY$LOCAL_BIN.
%VMSINSTAL-I-SYSDIR, This product creates system disk directory CAPOLY$TMP.
%VMSINSTAL-I-SYSDIR, This product creates system disk directory CAPOLY$DATA.
%VMSINSTAL-I-SYSDIR, This product creates system disk directory CAPOLY$LOGS.
COMMON install complete
%VMSINSTAL-I-RESTORE, Restoring product save set X ...
%VMSINSTAL-I-RESTORE, Restoring product save set R ...

The installation will now check the for the presence of an
OpenVMS account CAUNIVMS. This account is needed to support
the remote commands from the CA NSM management station.

The installation did not find the CAUNIVMS account.
It will prompt you for the UIC information to create the account.
You will need to have a unique UIC value.

* Enter a new UIC (include brackets) [[713,63]]:
%VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named CAUNIVMS.
%UAF-I-ADDMSG, user record successfully added
%UAF-I-RDBADDMSGU, identifier CAUNIVMS value [000713,000063] added to rights database
%UAF-I-RDBADDMSGU, identifier NSM value [000713,177777] added to rights database
* Do you want to activate the CA Common Services Integration Components [YES]? y
%UJMMGR_UNI_0000_yymmdd_V-I-EXISTS, Directory VMI$SPECIFIC:[UNIVMS.BIN] already exists.

CA NSM/CCS for OpenVMS - product startup selection
--------------------------------------------------

1 CA Job Management ................................. YES
2 CA Job Management Agent ........................... NO
3 CA Universal Job Management Agent ................. NO
4 CA NSM Jobflow Support ............................ YES
5 CA Job Management NSM/CCS Integration ............. YES
6 CA Console Management ............................. NO
7 CA System Watchdog ................................ NO
8 CA System Watchdog NSM/CCS Integration ............ NO
9 CA Performance Management Agent ................... NO
10 CA NSM Performance Trend Cube ..................... NO
11 CA Common Services OpenVMS Gateway ................ YES

* Are you satisfied with the product selection Y/[N] ? y

To complete integration with a CA NSM/CCS Management Station,
its IP address or node name is required.

* Node Name or IP Address ? win2K3a
%UJMMGR_UNI_0000_yymmdd_V-I-TRAPDST, The CA NSM/CCS Management station is set to "win2K3a"
%UJMMGR_UNI_0000_yymmdd_V-I-CREPRM, Created the file SYS$MANAGER:CAPOLY$SYSTARTUP.COM
%UJMMGR_UNI_0000_yymmdd_V-I-SETPRM, You can modify the selection later, using: SYS$MANAGER:CAPOLY$SET_STARTUP_PARAMS.COM

All questions regarding this installation have been asked.
The installation will run for approximately 2 to 5 minutes

%VMSINSTAL-I-RESTORE, Restoring product save set Z ...
%VMSINSTAL-I-SYSDIR, This product creates system directory [CA_LIC].
%VMSINSTAL-I-SYSDIR, This product creates system specific directory [CA_LIC].

Installing CA Message Service (CAM/CAFT)
%VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[UNIVMS.LOGS.ALPBOX.CAM].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[UNIVMS.LOGS.ALPBOX.CAM.LOGS].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[UNIVMS.LOGS.ALPBOX.CAM.QLOCAL].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[UNIVMS.LOGS.ALPBOXCAM.QREMOTE].
%VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[UNIVMS.LOGS.ALPBOX.CAM.FTLOGS].
%VMSINSTAL-I-RESTORE, Restoring product save set B ...

Linking CA Job Management Manager images...
Linking NSCHED.EXE ...
Linking SCHED_DECNET...
Linking INTERFACE...
Linking RETRY...
Linking MANAGER...
Linking SHELL_INTERFACE...
Linking SUMMARIZE_LOG...
Linking DOO_COMMAND...
Linking DB_UTILITY...
Linking VSS_REPORTS...
Linking SCHED$LISTENER...
Linking SCHED$GET_BEST_NODE...
Linking MOTIF...
Linking Config Utility...
Linking CPU Utility...
Linking Convert Utility...

Providing files...
Providing DCL interface, utilities, and HELP...
Providing Wide Area Network capabilities...
Providing Remote Executor capabilities for Agent...
Providing DECWindows Interface...
Providing Callable Application Programming Interface (API)...

Providing Startup, Shutdown, Installation Verification
and Deinstallation procedures ...

Restoring the links saveset...

%VMSINSTAL-I-RESTORE, Restoring product save set T ...

Installing links...

To have CA Common Services started when rebooting, add
"@SYS$STARTUP:CAPOLY$STARTUP" to the system startup file,
either SYS$MANAGER:SYSTARTUP_V5.COM for VMS V5 or
SYSTARTUP_VMS.COM for OpenVMS V6 and OpenVMS V7, and add
"@SYS$STARTUP:CAPOLY$SHUTDOWN" to the system shutdown file,
SYS$MANAGER:SYSHUTDWN.COM.

The TCP/IP stack TCP/IP Services is up and running...

%UJMMGR_UNI_0000_yymmdd_V-I-BUILDING, Linking CAPOLY$TNGD ...
%UJMMGR_UNI_0000_yymmdd_V-I-BUILDING, Linking CAPOLY$TRAP ...
%UJMMGR_UNI_0000_yymmdd_V-I-BUILDING, Linking CAPOLY$CASEND ...
%UJMMGR_UNI_0000_yymmdd_V-I-BUILDING, Linking CAPOLY$FORCEX ...

You may run the CA Common Services integration Installation
Verification Procedure at any time by typing the command:

$ @SYS$TEST:TNG$LINKS$IVP.COM

%UJMMGR_UNI_0000_yymmdd_V-I-BUILDING, Linking CAPOLY$SCHEVENT...
%UJMMGR_UNI_0000_yymmdd_V-I-BUILDING, Linking CAPOLY$SCHD...

--------------------------------------------------------------------------
Product Management Command Files
--------------------------------------------------------------------------
Startup: $ @SYS$STARTUP:UJM$MANAGER$STARTUP.COM
Shutdown: $ @SYS$STARTUP:UJM$MANAGER$SHUTDOWN.COM
IVP: $ @SYS$TEST:UJM$MANAGER$IVP.COM
Deinstall: $ @SYS$UPDATE:UJM$MANAGER$DEINSTALL.COM
--------------------------------------------------------------------------

--------------------------------------------------------------------------
Common Component Command Files
--------------------------------------------------------------------------
Startup: $ @SYS$STARTUP:CAPOLY$STARTUP
Shutdown: $ @SYS$STARTUP:CAPOLY$SHUTDOWN
Reconfig Common Startup: $ @SYS$MANAGER:CAPOLY$SET_STARTUP_PARAMS
List Installed Products: $ @SYS$STARTUP:CAREGISTRY$LISTPRODUCTS [FULL]
--------------------------------------------------------------------------

Note: A call to the product startup procedure or common
startup procedure should be inserted manually in
SYS$STARTUP:SYSTARTUP_VMS.COM in order to start
the product automatically at system boot time.
Similarly, a call to the product or common
shutdown procedure should be inserted in the system
shutdown procedure, SYS$MANAGER:SYSHUTDWN.COM

%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

DECwindows interface installation has completed successfully.

The DECwindows interface may be accessed by type the command:

$ schedule/interface=decwindows

You may want to edit the startup file UJM$MANAGER$STARTUP.COM
to change the default value for Max_jobs, or to enable load balancing...
Users who are currently logged on must log off and then back on again
to gain access to the CA Job Management Manager
command line interface.
IMPORTANT

For each CA Job Management Manager user on this node
set up a proxy to self, using AUTHORIZE as follows:

$ RUN AUTHORIZE
UAF> ADD/PROXY <local-node>::<local-user> <local-user>/DEFAULT

An additional proxy is needed to support job execution synchronization.
This proxy must exist in AUTHORIZE on the DEPENDENT JOB NODE. If both
CA Job Management Managers are started
under the SYSTEM account, then add:

UAF> add/proxy <predecessor-job-node>::SYSTEM SYSTEM/DEFAULT

Finally, add the account for the network object: first determine an UIC
which is either in the same group as the default DECNET account, or in
a group by itself. Then, run AUTHORIZE as follows:

UAF> ADD SCHED_DECNET/FLAGS=DISUSER/UIC=<uic-spec>
UAF> EXIT
Please refer to the CA Job Management Installation Guide for more details.
%RUN-S-PROC_ID, identification of created process is 21A0042F
%RUN-S-PROC_ID, identification of created process is 21A00430

Node 0 Session Control Application SCHED_DECNET
at 2011-11-23-10:53:22.578-07:00Iinf

Node 0 Session Control Application SCHED_DECNET
at 2011-11-23-10:53:22.693-07:00Iinf

Characteristics

Addresses =
{
name = SCHED_DECNET
}
Client = <Default value>
Incoming Alias = True
Incoming Proxy = True
Outgoing Alias = True
Outgoing Proxy = True
Node Synonym = True
Image Name = SYS$SYSTEM:SCHED_DECNET.COM
User Name = "SCHED$DECNET"
Incoming OSI TSEL = <Default value>
CCS OpenVMS Gateway Daemon Shutdown Complete

CA NSM/CCS for OpenVMS - product startup selection
--------------------------------------------------

The CA NSM/CCS Management station is set to
"win2K3a"

Note: You may change the list of products to be started on this node, using:
@SYS$MANAGER:CAPOLY$SET_STARTUP_PARAMS.COM
prior to launching this startup procedure...

CA NSM/CCS for OpenVMS - product startup selection
--------------------------------------------------

The CA NSM/CCS Management station is set to
"win2K3a"

Starting CAM Server...
%RUN-S-PROC_ID, identification of created process is 21A00432
Starting CAFT Server...
%RUN-S-PROC_ID, identification of created process is 21A00433
Starting OpenVMS TNG Gateway Daemon...
%RUN-S-PROC_ID, identification of created process is 21A00434
Job Management Manager already running...
Starting Job Management Jobflow Daemon...
%RUN-S-PROC_ID, identification of created process is 21A00435
Starting CAPOLY$SCHEVENT...
%RUN-S-PROC_ID, identification of created process is 21A00436

Beginning the CA Job Management Manager for OpenVMS Installation Verification Procedure.

%NSCHED-I-RQSTSUCCSS, Job 1 - Created
Job Management job #1 (Name: IVP_JOB) Started on node ALPBOX
Job Management Job #1 (Name: IVP_JOB) Completed on node ALPBOX
%NSCHED-I-FLAGSET, Job IVP_JOB - DELETE Requested

CA Job Management Manager for OpenVMS has been successfully installed.

Starting TNG$LINKS$IVP

Sending IVP Request to node: win2K3a
wait 5 seconds
Checking node: win2K3a
................... Responded OK

All CA NSM/CCS Management stations responded!

CA NSM/CCS Integration IVP completed successfully!

Installation of UJMMGR_UNI_0000_yymmdd_V V3.1 completed at 10:55

Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY

Creating installation data file: VMI$ROOT:[SYSUPD]UJMMGR_UNI_0000_yymmdd_V031.VMI_DATA

VMSINSTAL procedure done at 10:56

%DELETE-I-FILDEL, SYS$COMMON:[000000]CA$SETUP.DIR;1 deleted (16 blocks)
%DELETE-I-FILDEL, SYS$SYSROOT:[SYSMGR]CA$SETUP.INI;1 deleted (160 blocks)
%DELETE-I-FILDEL, SYS$SYSROOT:[SYSMGR]CA$SETUP.COM;1 deleted (160 blocks)
%DCL-S-RETURNED, control returned to process SYSTEM_48483
CA Job Management for OpenVMS

-----------------------------

PRODUCT

1 Job Management Manager Install
2 Job Management Agent Install

I CA NSM/CCS Integration Help
P Product Readme
H Install Help
E Exit

Please Enter the Number of the Product you wish to
install >>>>

Tell Technical Publications how we can improve this information