| CA |
3.0 System Requirements
3.1 OpenVMS Requirements
3.1.1 Manager
3.1.2 Agent
3.2 TCP/IP Stack Requirements
4.0 Installation Considerations
4.1 Natively Mount CD on OpenVMS
4.2 Access ISO Disk Image with OpenVMS Logical Disk Facility
4.2.1 Launch the Installation
5.0 General Considerations for the Manager
5.1 Above Average Workloads
5.2 Installing in a Cluster
5.3 Installing When DECnet is Not Running
5.4 Version Number
6.0 CA Common Services
6.1 Windows Considerations
6.2 CA Common Services for OpenVMS Versions
7.0 Known Issues
7.1 SHOW_SCHEDULED_RUNS Command Processes Slowly
7.2 Communications Failure with Multiple Cluster Nodes
7.3 Batch Job Failure with No Batch Access
7.4 Memory Intensive Commands: SHOW DEPENDENCIES and SCRIPT JOB
7.5 Modifying a Job Running in BATCH Mode
7.6 $ SCHEDULE SET LOGGING JOB_EVENT, ABNORMAL_EVENT - _$ /SERVER=MYNODE"myname mypassword"
7.7 Motif Support
7.8 Remote Executor (Agent)
7.9 Callable Interface (API)
7.10 Remote Support
7.11 Retry Function
7.12 Special Days
7.13 Fiscal Calendar Expressions
7.14 Next Scheduled Run Time for Jobs in Fiscal Leap Year
7.15 DCL Interface
7.16 Shutdown Does Not Always Shut Down
7.17 Late Install Prompt Upon Upgrade
7.18 Agent Deinstall Does Not Remove Itself
7.19 Documentation Issues
7.19.1 Administrator Guide
7.19.2 Installation Guide
7.19.3 SDK Guide
9.0 Logical Name Definitions
9.1 Motif GUI
9.2 SCHEDULE STOP
10.0 Third-Party Software Agreement
10.1 Info-ZIP Acknowledgements
10.2 Tomcat Acknowledgements
10.3 Sun JRE Acknowledgements
11.0 Documentation
11.1 Release Numbers on Documentation
This README contains important information about Unicenter Job Management for OpenVMS r3 SP1 that might not be included in the Installation Guide.
Note: The term Windows refers to any Microsoft Windows operating system supported by CA.
CA Job Management for OpenVMS r3 SP1 supports the following operating systems:
This release does not support the following operating systems:
The following requirements must be met or exceeded for CA Job Management for OpenVMS to install and run correctly:
The following list contains the OpenVMS versions and the corresponding TCP/IP stack versions:
For systems running HP TCP/IP Services, at a minimum the following HP ECO level is recommended:
For systems running TCPware v5.7-2 or v5.8, the following Process Software ECO is required:
For systems running TCPware v5.9, the following Process Software ECOs are required:
For systems running MultiNet v5.1, the following Process Software ECOs are required:
For systems running MultiNet v5.2, the following Process Software ECOs are required:
For systems running MultiNet v5.3, the following Process Software ECOs are required:
Installation procedures for this release of CA Job Management for OpenVMS are in the CA Job Management for OpenVMS Installation Guide.
Note: For more information, see the CA Job Management for OpenVMS Installation Guide.
Before installing CA Job Management for OpenVMS (or any of its components), be sure to review the following sections carefully to determine if there are additional installation and/or configuration steps you need to follow for this release.
Use the following commands to natively mount the CD, after replacing duxx with your own drive information:
mount duxx: /over=id
Note: where duxx: is the CD-ROM drive.
OpenVMS provides a mechanism to mount an ISO image of a CA OpenVMS product CD/DVD directly, through the LD driver. While the LD driver is native on OpenVMS Alpha 7.3-2 and newer, and on OpenVMS I64 8.2-1 and newer, it is not directly available on OpenVMS v6.2. It may however be obtained from the latest HP freeware CD for OpenVMS. LD v6.3, part of the OpenVMS Freeware V5.0 distribution, is the minimum version that supports OpenVMS VAX and Alpha v6.2.
Notes:
To access the ISO disk Image
Search for the text “load_ldcld:”. The line immediately following the occurrence of this text should be “$ set command sys$input”. Starting with the line immediately after the line that reads "$ set command sys$input", cut all lines of text up to but not including the line that reads "$ RETURN 1" into a file named LD.CLD; this will be approximately 245 lines of text.
The first few and last few lines of the selected text should look as follows:
!+++ ! ! Facility: ! ! Command Definition File for the LD Utility. ! ! Abstract: ! ! This file defines the following commands; . . . DEFINE SYNTAX PARAM_ALL PARAMETER P1,LABEL=COMMAND,PROMPT="Command", VALUE(REQUIRED,TYPE=LD_OPTIONS) PARAMETER P2,LABEL=DEVICE,VALUE(TYPE=$DEVICE) !<end-of-file>
$ if f$file_attributes("sys$system:ld$utility.exe","known")
Insert the following lines of DCL immediately before that line:
$ if f$file_attributes("sys$message:ld$msg.exe","known")
$ then
$ install replace sys$message:ld$msg.exe
$ else
$ install create sys$message:ld$msg.exe
$ endif
Close the file and terminate your editing session.
$ SET COMMAND LD
For OpenVMS Alpha 8.2 and newer, execute the following:
$ SET COMMAND SYS$UPDATE:LD.CLD
The above commands should be executed whenever you login.
$ @SYS$STARTUP:LD$STARTUP.COM
$ LD CONNECT disk:[dir-path]filename.ISO
The system responds with the device name of the logical disk device that the .ISO file was connected to. You will need this device name for the following step.
$ MOUNT/MEDIA=CD/OVER=ID logical-disk-device-from-step-6
$ DISMOUNT LD-device-name $ LD DISCONNECT LD-device-name
You can do this after you complete each installation and before repeating steps 6 and 7 for other ISO product disk images, or after you have completed all installations. If you do this after all installations, repeat these commands once for each ISO product disk image that was connected and mounted.
Sample log file
This log shows the connection, mounting, and start of the installation for the CA Console Management r3.1 for OpenVMS Alpha on a system running OpenVMS Alpha 8.3.
Steps 1 through 5 have already been performed.
$ LD CONNECT $1$DKA100:[000000]CACM_31_VMSAXP.ISO %LD-I-UNIT, Allocated device is $1$LDA6: $ MOUNT/OVER=ID/MEDIA=CD/NOASSIST $1$LDA6: %MOUNT-I-WRITELOCK, volume is write locked %MOUNT-I-CDROM_ISO, CACM_31_VMSAXP: (1 of 1) , mounted on _$1$LDA6: (USXXXX) $ RUN $1$LDA6:[000000]SETUP_ALPHA.EXE UnZipSFX 5.20 of 30 April 1996, by Info-ZIP (Zip-Bugs@wkuvx1.wku.edu). inflating: ca$setup.com inflating: installhelp.hlp inflating: cacm$readme.txt inflating: cacm_product.key inflating: unzip_alpha.exe inflating: unzip_ia64.exe Setup location: $1$LDA6:[000000] CA Console Management for OpenVMS Copyright (c) 2004,2010 CA. All rights reserved. --------------------------------- PRODUCT 1 Console Manager 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 >>>>
Using the SYSTEM account, run the installation procedure on the OpenVMS system by typing the following command:
$ run device:[000000]setup_alpha.exe
$ run device:[000000]setup_ia64.exe
These commands launch an installation menu where you can install the components
This section contains general information you should know before using CA Job Management for OpenVMS:
CA Job Management for OpenVMS is a performance sensitive application. For above average workloads, ensure that the Job Management systems are configured to handle the expected workload.
If you are installing r3 SP1 on a server in a cluster, you must do the following in order for the product to work correctly:
During the installation, an important message is displayed regarding proxy authorization for CA Job Management users. When you are installing on a system that is not running DECnet, you can ignore the final paragraph in this message, which describes adding a user account for the DECnet network object. The text to ignore is:
Note:
Installing the product without DECnet installed or running will preclude access to any remote job management command such as:
SCHEDULE CREATE <command> /SERVER=…
SCHEDULE SHOW <option> /SERVER=…
SCHEDULE MODIFY <job> /SERVER=…
It will also prevent setting up remote dependencies with such commands as:
SCHEDULE CREATE <command> /SYNCHRONIZATION=<hostname>::<job>
SCHEDULE MODIFY <job> /SYNCHRONIZATION=<hostname>::<job>
These remote job management abilities may be restored later by reinstalling the product while DECnet is running.
CA has changed their product version scheme. The official version of this release of CA Job Management for OpenVMS is r3 SP1. This version is the same as V3.0-1006.
The CA NSM Integration component name has been changed from Unicenter for OpenVMS to CA Common Services Integration for OpenVMS (CCS Integration for OpenVMS).
If you are using CA NSM on Windows, you must be aware of the following situations:
The version number for CA Common Services for OpenVMS Integration is independent of the product version. The CA Common Services for OpenVMS Integration version used in this release is r3.2 on OpenVMS I64 v8.2 and above and on OpenVMS Alpha v7.3-2 and above. Installations on OpenVMS VAX (all versions) and OpenVMS Alpha v6.2 still use the CCS for OpenVMS Integration version 2.4.
For more information on this component, see the CA Common Services for OpenVMS Integration Guide.
The SHOW_SCHEDULED_RUNS command reads the history file and the database to find the jobs and their dependencies. This command runs slowly if any of the following conditions are true:
For better performance, use the following command to write the output from the SHOW_SCHEDULED_RUNS command to an output file instead of your terminal:
$SCHED SHOW SCHEDULED_RUNS/OUTPUT=filename
A communications failure occurs between one CA Job Management for OpenVMS installation and a second CA Job Management for OpenVMS installation when you install the second installation on a cluster where you have not installed CA Job Management for OpenVMS on all of that cluster’s nodes. This communication failure occurs in the following situations:
To work around this failure, add the following lines to SYLOGIN.COM or SYSTARTUP.COM on the cluster:
$ @SYS$STARTUP:UJM$MANAGER$STARTUP LOGICAL_NAMES $ DEFINE/SYSTEM/EXEC NSCHED$ NSCHED$DATA,NSCHED$COM,NSCHED$EXE
To let a node that does not have CA Job Management for OpenVMS installed and running receive job completion messages, run AUTHORIZE and add the following proxies:
$ RUN AUTHORIZE UAF> ADD/PROXY <job_dependency_node>::SYSTEM SYSTEM/DEF
This authorization lets jobs on nodes with CA Job Management for OpenVMS running in the same cluster run when their dependencies are satisfied.
When a user runs a job specifying /MODE=BATCH and /USER=another_user, another_user has no batch access, and the batch job fails. The job is submitted successfully, but fails when it tries to run. Because SCHEDULER$SHELL.COM never executes, failure notification is not sent. This problem occurs when a new installation of CA Job Management for OpenVMS purges SCHEDULER$SHELL.COM while batch mode jobs are queued.
The SCHEDULE SHOW DEPENDENCIES and SCHEDULE SCRIPT JOB commands are memory intensive. Depending on the size of the job stream being identified and the quotas of the process making the attempt, these commands may not work correctly or may cause the interface to crash. To work around this problem, increase the required quotas for the process.
When you modify a job that is running in BATCH mode at the same time that job is executing, an error may occur when NSCHED processes the job completion. This error occurs if the modification of the job occurs in the period of time between when the batch job completes execution and when NSCHED processes the batch job completion. Though this time period is small, conditions occur during this time period, such as a job with a postfunction that modifies itself.
When this error occurs, the JOB SLOT count is not decremented. This count tells NSCHED how many job slots are currently in use. If this count is not decremented properly, NSCHED thinks that the job slots are still in use. Each time this error occurs, CA Job Management for OpenVMS loses the use of one job slot. Eventually, all job slots will be exhausted, and CA Job Management for OpenVMS cannot execute any jobs.
If you run jobs and they fall into "job slot wait" status, your system may suffer from loss of job slots. This condition should only occur on systems that use the BATCH execution mode. Use the SCHEDULE CHECK command to recover lost job slots.
This command returns the error message SYSTEM-F-IVBUFLEN and fails to perform the intended operation.
"Cannot load all successor jobs. Display limit of 100 dep_post jobs exceeded."
The load will complete, however, all the successor jobs for the job will not be displayed.
"Cannot load all ghost dependency jobs. Display limit of 1000 ghost jobs exceeded."
The load will complete; however, all the unselected local dependency jobs will not be displayed.
"Cannot load all remote jobs. Display limit of 1000 remote jobs exceeded."
The load will complete; however all the unselected remote jobs will not be displayed.
Under unknown conditions, the Remote Executor (Agent) and the Server cannot get each other’s names by IP address using DNS. You can work around this problem by defining the Remote Executor’s name in the Server TCPIP local database and vice versa.
TCPIP> SET HOST <NAME> /ADDRESS=<IP ADDRESS>
The job count produced by the SCHED SHOW STAT /REMOTE_NODE=nodename command can be inaccurate. The conditions for this problem are unknown.
SYS$MANAGER: SYS$ERROR
Fiscal calendar expressions can contain up to 14 characters. Anything beyond 14 characters is lost.
If you need to specify a fiscal calendar expression with more than 14 characters, you can eliminate all spaces within the expression except the space before the time. For example, you want to specify the following fiscal expression, which contains 15 characters:
F M W5 D4 10:34
By eliminating any unnecessary spaces, you have the following valid fiscal calendar expression:
FMW5D4 10:34
CA Job Management for OpenVMS does not calculate correctly the next scheduled run time for jobs using a fiscal scheduling interval when the fiscal base date is in a (calendar) leap year. For example, using a base date of 26-DEC-1996 produces incorrect next scheduled run time values using a fiscal date expression.
node"user_name"::job_number=owner
SCHED SET LOGGING ALL/SERVER=node
SCHED SET MAX_JOBS nnn/SERVER=node
SCHED SET PRIORITY nnn/SERVER=node
SCHED CHECK/SERVER=node
The shutdown procedure UJM$MANAGER$SHUTDOWN.COM (or CAPOLY$SHUTDOWN.COM) completes; however the main process, NSCHED, is still running. This can occur if you have many jobs terminating at the same time, if you have a job or jobs with /INTERVAL=0 and a very short job run time (e.g. exit 1), or if NSCHED is busy processing a simple command that operates on thousands of jobs (e.g. SCHED HOLD *=*). Zero interval jobs in a dependency tree will make this problem worse -- it will take longer for the NSCHED process to shut down.
The system logical name NSCHED$TERMINATION_RATIO helps to work around this problem. By default, the value is 5. This means 5 job terminations are accepted for every non-job-termination message (e.g. MODIFY, HOLD, ABORT, STOP). Setting this value to 2 or 3 will allow the STOP command to reach the head of the message list sooner.
When you upgrade from an earlier version of Unicenter Job Management or ScheduleIT, the installation script might prompt you to backup existing executables and/or locate a database to use. This prompting takes place after the message has been displayed that no further prompts would be issued.
When you uninstall the Job Management Agent on VAX and on Alpha 6.2, the uninstall file UNIJM$AGENT$DEINSTALL.COM is not removed. If you run this script again, you might see warning messages as target of GOTO not found. To avoid this issue, manually delete the file SYS$UPDATE:UNIJM$AGENT$DEINSTALL.COM when you complete the uninstallation.
The following example shows how a Special Day Class is defined in the DCL interface:
SCHEDULE> CREATE MY-CLASS /SD_CLASS -
_SCHEDULE> /DATES=(1-JAN-2000,25-DEC-1999,26-NOV-1999)
The Class name (MY-CLASS) should NOT contain a dash character (-).
A job can have a restart parameter set while it is running, so if it fails during execution, the restart parameter can be passed back when it restarts. If this is defined as TRUE, this behavior is maintained. If defined as FALSE, the restart parameter will not be cleared when the job completes.
Default: TRUE.
A job can have a restart parameter set while it is running, so if it fails during execution, the restart parameter can be passed back when it restarts. If this is defined as TRUE, the restart parameter will be cleared when the job completes and the job will start from the beginning the next time it runs. If defined as FALSE the restart parameter will not be cleared when the job completes, thus the next time the job runs it will continue from the saved restart parameter.
Default: TRUE.
Note: On a standalone system, the prompt still refers to a cluster common directory. You may choose to install the common and specific files to the same directory. However, we recommend choosing a directory that is part of SYS$COMMON, which makes it easier to add this system to a cluster in the future.
Note: On a standalone system, the prompt still refers to a cluster common directory. You may choose to install the common and specific files to the same directory. However, we recommend choosing a directory that is part of SYS$COMMON, which makes it easier to add this system to a cluster in the future.
Directories [DATA] and [COM] will be created under the path you specify. All data and common files are moved to these directories. Logical names NSCHED$DATA and NSCHED$COM will be associated accordingly.
Note: Directory [EXE] will be created under the path you specify. All the executable files will be moved to this [EXE] directory. Logical name NSCHED$EXE will be associated with this directory.
The installation is checking the account quotas required for the product startup. If at least one quota is below the required value, the installation lists current quotas and asks if you want to continue. If you choose to continue anyway, the product will NOT start after the installation and IVP will NOT run.
If the installation is an upgrade from a previous version of the product, the existing job database VSS.DAT must be upgraded to support the new features in V3.0. Ensure you have the proper VSS.DAT file in NSCHED$ directory before the installation.
The installation searches for the existing database in the NSCHED$ and NSCHED$DATA paths and determine whether or not the file must be upgraded / moved to another directory.
If the installation cannot find the VSS.DAT file, it prompts you to create a new one during product startup. You can redefine NSCHED$ logical name or copy the desired file to the NSCHED$ directory at that time and retry the search.
If the installation finds multiple VSS.DAT files in different directories, it lets you choose which one should be used.
If the installation finds the VSS.DAT file and determines that it must be moved to NSCHED$DATA, it asks for your confirmation.
Note:
Important! After the database upgrade, you must not copy another VSS.DAT file from a previous version to the NSCHED$DATA directory. Trying to use JM Manager 3.0 with an older VSS.DAT results in the product failing to work properly.
If the installation is not a first time install on the
node, it will determine whether or not it should backup the
existing files.
The installation might create two savesets:
NSCHED$:OLD_UJM_DATABASE.BCK (with NSCHED$:*.DAT;* files) NSCHED$:OLD_UJM_EXECUTABLES.BCK (with NSCHED$:*.EXE;*,*.OLB;*, *.UID;*,*.COM;*,*.HLB;*,*.CLD;* files.)
The installation will also delete all files from their original location.
In addition, place the Unicenter Job Management Agent startup command after the line that invokes the TCP/IP services startup command procedure.
For example:
$ @SYS$STARTUP:UCX$STARTUP.COM . . . $ @SYS$STARTUP:UNIJM$AGENT$SHUTDOWN.COM
The file name in the line above
$ @SYS$STARTUP:UNIJM$AGENT$SHUTDOWN.COM
should be changed to
$ @SYS$STARTUP:UNIJM$AGENT$STARTUP.COM
The item_list argument specifies in what format the date information is sent. The item_list argument is the address of an ITEM_BLOCK that says what format the input date is in, and describes the buffer containing the input date. Only one ITEM_BLOCK is passed in for this call.
The following is a description of item codes used in the ITEM_BLOCK:
| Item Code | Meaning |
|---|---|
| VSS$K_ASCII_INPUT | Specifies the input date is in ASCII format.The calling program must allocate and set up a buffer containing a null-terminated ASCII string representation of a date specification. The size and address of this buffer must be passed in the ITEM_BLOCK. |
| VSS$K_BINARY_INPUT | Specifies the input date is in binary format. The calling program must allocate and set up a buffer containing a binary number representation of a date specification. The size and address of this buffer must be passed in the ITEM_BLOCK. |
The item_list argument is the address of an ITEM_BLOCK structure that says what format the input date is in, describes the buffer containing the input date and specifies a buffer for the return code. Only one ITEM_BLOCK is passed in for this call.
The following is a description of item codes used in the ITEM_BLOCK:
| Item Code | Meaning |
|---|---|
| VSS$K_ASCII_INPUT | Specifies the input date is in ASCII format. |
| VSS$K_BINARY_INPUT | Specifies the input date is in binary format. |
The following is a description of Buffer Length and Buffer Address used in the ITEM_BLOCK:
| Item Code | Meaning |
|---|---|
| VSS$K_ASCII_INPUT | The calling program must allocate and set up a buffer containing an ASCII Date Specifier Data Structure. "Buffer Address" is the address of a buffer containing an ASCII Date Specifier Data Structure. "Buffer Length" is not used. |
| VSS$K_BINARY_INPUT | The calling program must allocate and set up a buffer containing a binary representation of a date specification. Buffer Address is the address of a time quadword containing the binary date. "Buffer Length" is not used. |
The following is a description of "Return Length Address" used in the ITEM_BLOCK:
Return Length Address (write only) is an address of a longword to receive the function result:
| Return Value | Meaning |
|---|---|
| NSCHED$_SUCCESS | Successful completion |
| NSCHED$_INVARG | Invalid argument address in ITEM_BLOCK |
You can find the complete list of published bug fixes for this product at CA Support Online: https://support.ca.com
The following fixes and behavioral changes are included in this release. Where applicable, the published PTF number is specified before the description of the fix:
| PTF Number | Fix Description |
|---|---|
| QI63440 | The command SCHED SHOW HISTORY <job> returns incomplete data when issued from an account without WORLD privilege and <job> belongs to another user and is running as the command is issued. |
| QI80429 | CA Common Services for OpenVMS Integration Guide Appendix A states: By default, CASEND will send the message to nodes defined by the logical name CAPOLY$TRAP_DEST. The proper logical name is CAPOLY$TRAP_DST |
| QI84858 | CA Licensing update from OpenVMS |
| QO58169 | Hardware model GS1280 not rated |
| QO58726 | Multiple installation problems |
| QO58727 | Hardware rating exceeds 32767 |
| QO63434 | Modify job command is looping |
| QO64587 | Hardware model DS20 500 | 1838 | 800 not rated |
| QO64592 | Sends mail with wrong subject |
| QO66794 | Full product cumulative patch, Alpha 8.2 |
| QO67671 | Errors connecting to server with V2.* |
| QO69494 | Job stay in Job Slot Wait when slots are available in the cluster, Alpha 6.2 and 7.* |
| QO73198 | Incremental fix, Alpha 8.2 |
| QO73199 | Job stay in Job Slot Wait when slots are available in the cluster, Alpha 8.* |
| QO74748 | VSS$CHECK_BITMASK_DATE() fails, Alpha |
| QO75091 | Full Alpha 8.2 kit, with install fails with newer CA Licensing, Alpha 8.2 |
| QO77832 | Install fails with newer CA Licensing, Integrity |
| QO79809 | Batch job fails with doo_command:--- Can't clear event flag: 9, Alpha 6.2 and 7.* |
| QO80425 | Hardware model AlphaStation DS10 617 MHz Model 1963 and AlphaServer 4100 5/466 4MB Model 1595 not rated |
| QO80426 | NSCHED hangs in HIB, simple program wakes it, Alpha 7.3-2 |
| QO80427 | Quoted Load Balance Group name creates a duplicate |
| QO81203 | Reduce lib$wait() argumernt to improve performance |
| QO81583 | Cube files directory name is created in lower-case |
| QO85953 | Batch job fails with doo_command:--- Can't clear event flag: 9, Alpha 8.2 |
| QO86279 | Improve performance of job data access, Alpha |
| QO87410 | Cumulative fixes ported from Alpha, Integrity |
| QO89039 | No username sent in SNMP trap, Integrity |
| QO89382 | Run /noreschedule error with wrong job or username, Integrity |
| QO92842 | SCHEDULE MODIFY /PROMPT locks job and incremental fix, Alpha 6.2 and 7.* |
| QO95523 | Incremental fix with duplicate vermont_creamery and stall function, Alpha 6.2 and 7.* |
| QO99138 | WVUniVMS process fails in PPEecifde.dll |
| QO99159 | Incremental fix with copy job /SERVER does not write SD restrictions and ViewInfo fields, Integrity |
| RI04405 | The NSCHED process crashes with various errors. |
| RO00448 | Batch job in NotRunning state after completion, with all Alpha 6.2 and 7.* cumulative fixes, Alpha 8.* |
| RO20255 | SCHEDULE command -F- status creates DUMP, Alpha 8.* |
| RO20256 | SCHEDULE command -F- status creates DUMP, Integrity |
| RO20257 | Hardware model BL860c and BL870c Blade servers not rated |
| RO02348 | Hardware model ES80, GS1280, rx8640, rx7640 not rated, with compatibility with DAT on I64, Alpha 6.2 and 7.* |
| RO02349 | Hardware model Rate ES80, GS1280, rx8640, rx7640 not rated, with compatibility with DAT on I64, Alpha 8.* |
| RO03529 | SCHEDULE SHOW LOAD shows up to 100% for multiprocessor CPU, Integrity |
| RO04630 | SCHEDULE STOP command stops the NSCHED process without asking for user confirmation, Alpha 8.3 |
| RO06794 | Open log files in Motif, Alpha 6.2 and 7.* |
| RO06795 | Open log files in Motif, Alpha 8.* |
| RO06796 | Open log files in Motif, Integrity |
| RO07034 | CAPOLY$SCHEVENT fails with for jobs with long names |
| RO07035 | Cumulative fixes, VAX |
| RO13106 | Job won’t run at scheduled time, Alpha 6.2 and 7.* |
| VSS$MODIFY_REMOTE_LBAL: ERROR RECEIVING OUTPUT PARAMETERS. | |
| Wrong calculation of next_run_time in leap year with fiscal interval, Alpha 6.2 and 7.* | |
| Remote sync time not returned but status is OK, Alpha 6.2 and 7.* | |
| CA Licensing update, VAX and Alpha 6.2 and 7.* | |
| SCHEDULE command -F- status creates DUMP | |
| Hardware model BL860c and BL870c Blade servers not rated | |
| Excessive messages, "LBAL GROUP NOT FOUND" | |
| Agent version is incorrect, SCHEDULE SHOW STATUS /REMOTE=<Agent node> displays V2.4.2 instead of V3.0 |
This section describes the new logical names that are added to solve end-user problems.
To view a job log file in the Job Management Motif GUI while the job is running, the Motif GUI creates a temporary file in job user's SYS$LOGIN directory. The file name is the original job log file name plus _SCHED$JOU. After a short delay needed for the viewer to load the file (default is 10 seconds), this file gets deleted. A longer delay might be required on slow systems or if the log file is large and the viewer has not enough time to load it.
To increase the delay, define the following logical name:
$ define /system SCHED$VIEWER_DELAY <delay in seconds>
Note: During this delay, the process hibernates and other Job Management Motif GUI windows are frozen.
The SCHEDULE STOP command now uses new qualifier /[NO]CONFIRM. The default is /NOCONFIRM. The default can be overridden by the following logical name definition:
$ define/system/executive NSCHED$CONFIRM_STOP "TRUE"
When this logical is defined, the default is /CONFIRM. On SCHED STOP /CONFIRM, you must confirm the command:
Do you really want to stop UJM processes? [No]
This product includes UnZip 5.2, which is distributed in accordance with the following terms:
This is version 2005-Feb-10 of the Info-ZIP copyright and license. The definitive version of this document should be available at
ftp://ftp.info-zip.org/pub/infozip/license.html indefinitely.
Copyright (c) 1990-2005 Info-ZIP. All rights reserved.
For the purposes of this copyright and license, "Info-ZIP" is defined as the following set of individuals:
Mark Adler, John Bush, Karl Davis, Harald Denker, Jean-Michel Dubois, Jean-loup Gailly, Hunter Goatley, Ed Gordon, Ian Gorman, Chris Herborth, Dirk Haase, Greg Hartwig, Robert Heath, Jonathan Hudson, Paul Kienitz, David Kirschbaum, Johnny Lee, Onno van der Linden, Igor Mandrichenko, Steve P. Miller, Sergio Monesi, Keith Owens, George Petrov, Greg Roelofs, Kai Uwe Rommel, Steve Salisbury, Dave Smith, Steven M. Schweda, Christian Spieler, Cosmin Truta, Antoine Verheijen, Paul von Behren, Rich Wales, Mike White
This software is provided "as is," without warranty of any kind, express or implied. In no event shall Info-ZIP or its contributors be held liable for any direct, indirect, incidental, special or consequential damages arising out of the use of or inability to use this software.
Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:
UnZipSFX is a self-extracting unzip tool, which CA OpenVMS uses to package installation kits and fixes that we provide to our customers. CA has modified the UnZipSFX source code in order to call a patch install script once the self-extracting file is unpackaged.
Copyright (c) 1990-2005 Info-ZIP. All rights reserved.
See the accompanying file LICENSE, version 2000-Apr-09 or later (the contents of which are also included in unzip.h) for terms of use. If, for some reason, all these files are missing, the Info-ZIP license also may be found at: ftp://ftp.info-zip.org/pub/infozip/license.html
This product includes Apache Tomcat 5.5.23 which is distributed in accordance with the following license agreement:
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
END OF TERMS AND CONDITIONS
This product is distributed with Sun JRE 1.5.0_11 (Sun JRE). The Sun JRE is distributed in accordance with the Sun Microsystems, Inc. (Sun) Binary Code License Agreement set forth below. As noted in Section G of the Supplemental License Terms of this license, Sun has provided additional copyright notices and license terms that may be applicable to portions of the Sun JRE in the THIRDPARTYLICENSEREADME.txt file that accompanies the Sun JRE.
License Text
Sun Microsystems, Inc. Binary Code License Agreement for the JAVA 2 PLATFORM STANDARD EDITION DEVELOPMENT KIT 5.0
SUN MICROSYSTEMS, INC. ("SUN") IS WILLING TO LICENSE THE SOFTWARE IDENTIFIED BELOW TO YOU ONLY UPON THE CONDITION THAT YOU ACCEPT ALL OF THE TERMS CONTAINED IN THIS BINARY CODE LICENSE AGREEMENT AND SUPPLEMENTAL LICENSE TERMS (COLLECTIVELY "AGREEMENT"). PLEASE READ THE AGREEMENT CAREFULLY. BY DOWNLOADING OR INSTALLING THIS SOFTWARE, YOU ACCEPT THE TERMS OF THE AGREEMENT. INDICATE ACCEPTANCE BY SELECTING THE "ACCEPT" BUTTON AT THE BOTTOM OF THE AGREEMENT. IF YOU ARE NOT WILLING TO BE BOUND BY ALL THE TERMS, SELECT THE "DECLINE" BUTTON AT THE BOTTOM OF THE AGREEMENT AND THE DOWNLOAD OR INSTALL PROCESS WILL NOT CONTINUE.
1.DEFINITIONS. "Software" means the identified above in binary form, any other machine readable materials (including, but not limited to, libraries, source files, header files, and data files), any updates or error corrections provided by Sun, and any user manuals, programming guides and other documentation provided to you by Sun under this Agreement. "Programs" mean Java applets and applications intended to run on the Java 2 Platform Standard Edition (J2SE platform) platform on Java-enabled general purpose desktop computers and servers.
2.LICENSE TO USE. Subject to the terms and conditions of this Agreement, including, but not limited to the Java Technology Restrictions of the Supplemental License Terms, Sun grants you a non-exclusive, non-transferable, limited license without license fees to reproduce and use internally Software complete and unmodified for the sole purpose of running Programs. Additional licenses for developers and/or publishers are granted in the
3.RESTRICTIONS. Software is confidential and copyrighted. Title to Software and all associated intellectual property rights is retained by Sun and/or its licensors. Unless enforcement is prohibited by applicable law, you may not modify, decompile, or reverse engineer Software. You acknowledge that Licensed Software is not designed or intended for use in the design, construction, operation or maintenance of any nuclear facility. Sun Microsystems, Inc. disclaims any express or implied warranty of fitness for such uses. No right, title or interest in or to any trademark, service mark, logo or trade name of Sun or its licensors is granted under this Agreement. Additional restrictions for developers and/or publishers licenses are set forth in the Supplemental License Terms.
4.LIMITED WARRANTY. Sun warrants to you that for a period of ninety (90) days from the date of purchase, as evidenced by a copy of the receipt, the media on which Software is furnished (if any) will be free of defects in materials and workmanship under normal use. Except for the foregoing, Software is provided "AS IS". Your exclusive remedy and Sun's entire liability under this limited warranty will be at Sun's option to replace Software media or refund the fee paid for Software. Any implied warranties on the Software are limited to 90 days. Some states do not allow limitations on duration of an implied warranty, so the above may not apply to you. This limited warranty gives you specific legal rights. You may have others, which vary from state to state.
5.DISCLAIMER OF WARRANTY. UNLESS SPECIFIED IN THIS GREEMENT, ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT THESE DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
6.LIMITATION OF LIABILITY. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF OR RELATED TO THE USE OF OR INABILITY TO USE SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. In no event will Sun's liability to you, whether in contract, tort (including negligence), or otherwise, exceed the amount paid by you for Software under this Agreement. The foregoing limitations will apply even if the above stated warranty fails of its essential purpose. Some states do not allow the exclusion of incidental or consequential damages, so some of the terms above may not be applicable to you.
7.TERMINATION. This Agreement is effective until terminated. You may terminate this Agreement at any time by destroying all copies of Software. This Agreement will terminate immediately without notice from Sun if you fail to comply with any provision of this Agreement. Either party may terminate this Agreement immediately should any Software become, or in either party's opinion be likely to become, the subject of a claim of infringement of any intellectual property right. Upon Termination, you must destroy all copies of Software.
8.EXPORT REGULATIONS. All Software and technical data delivered under this Agreement are subject to US export control laws and may be subject to export or import regulations in other countries. You agree to comply strictly with all such laws and regulations and acknowledge that you have the responsibility to obtain such licenses to export, re-export, or import as may be required after delivery to you.
9.TRADEMARKS AND LOGOS. You acknowledge and agree as between you and Sun that Sun owns the SUN, SOLARIS, JAVA, JINI, FORTE, and iPLANET trademarks and all SUN, SOLARIS, JAVA, JINI, FORTE, and iPLANET-related trademarks, service marks, logos and other brand designations ("Sun Marks"), and you agree to comply with the Sun Trademark and Logo Usage Requirements currently located at http://www.sun.com/policies/trademarks. Any use you make of the Sun Marks inures to Sun's benefit.
10.U.S. GOVERNMENT RESTRICTED RIGHTS. If Software is being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), then the Government's rights in Software and accompanying documentation will be only as set forth in this Agreement; this is in accordance with 48 CFR 227.7201 through 227.7202-4 (for Department of Defense (DOD) acquisitions) and with 48 CFR 2.101 and 12.212 (for non-DOD acquisitions).
11.GOVERNING LAW. Any action related to this Agreement will be governed by California law and controlling U.S. federal law. No choice of law rules of any jurisdiction will apply.
12.SEVERABILITY. If any provision of this Agreement is held to be unenforceable, this Agreement will remain in effect with the provision omitted, unless omission would frustrate the intent of the parties, in which case this Agreement will immediately terminate.
13.INTEGRATION. This Agreement is the entire agreement between you and Sun relating to its subject matter. It supersedes all prior or contemporaneous oral or written communications, proposals, representations and warranties and prevails over any conflicting or additional terms of any quote, order, acknowledgment, or other communication between the parties relating to its subject matter during the term of this Agreement. No modification of this Agreement will be binding, unless in writing and signed by an authorized representative of each party.
SUPPLEMENTAL LICENSE TERMS
These Supplemental License Terms add to or modify the terms of the Binary Code License Agreement. Capitalized terms not defined in these Supplemental Terms shall have the same meanings ascribed to them in the Binary Code License Agreement . These Supplemental Terms shall supersede any inconsistent or conflicting terms in the Binary Code License Agreement, or in any license contained within the Software.
A.Software Internal Use and Development License Grant. Subject to the terms and conditions of this Agreement and restrictions and exceptions set forth in the Software "README" file, including, but not limited to the Java Technology Restrictions of these Supplemental Terms, Sun grants you a non-exclusive, non-transferable, limited license without fees to reproduce internally and use internally the Software complete and unmodified for the purpose of designing, developing, and testing your Programs.
B.License to Distribute Software. Subject to the terms and conditions of this Agreement and restrictions and exceptions set forth in the Software README file, including, but not limited to the Java Technology Restrictions of these Supplemental Terms, Sun grants you a non-exclusive, non-transferable, limited license without fees to reproduce and distribute the Software, provided that (i) you distribute the Software complete and unmodified and only bundled as part of, and for the sole purpose of running, your Programs, (ii) the Programs add significant and primary functionality to the Software, (iii) you do not distribute additional software intended to replace any component(s) of the Software, (iv) you do not remove or alter any proprietary legends or notices contained in the Software, (v) you only distribute the Software subject to a license agreement that protects Sun's interests consistent with the terms contained in this Agreement, and (vi) you agree to defend and indemnify Sun and its licensors from and against any damages, costs, liabilities, settlement amounts and/or expenses (including attorneys' fees) incurred in connection with any claim, lawsuit or action by any third party that arises or results from the use or distribution of any and all Programs and/or Software.
C.License to Distribute Redistributables. Subject to the terms and conditions of this Agreement and restrictions and exceptions set forth in the Software README file, including but not limited to the Java Technology Restrictions of these Supplemental Terms, Sun grants you a non-exclusive, non-transferable, limited license without fees to reproduce and distribute those files specifically identified as redistributable in the Software "README" file ("Redistributables") provided that: (i) you distribute the Redistributables complete and unmodified, and only bundled as part of Programs, (ii) the Programs add significant and primary functionality to the Redistributables, (iii) you do not distribute additional software intended to supersede any component(s) of the Redistributables (unless otherwise specified in the applicable README file), (iv) you do not remove or alter any proprietary legends or notices contained in or on the Redistributables, (v) you only distribute the Redistributables pursuant to a license agreement that protects Sun's interests consistent with the terms contained in the Agreement, (vi) you agree to defend and indemnify Sun and its licensors from and against any damages, costs, liabilities, settlement amounts and/or expenses (including attorneys' fees) incurred in connection with any claim, lawsuit or action by any third party that arises or results from the use or distribution of any and all Programs and/or Software.
D.Java Technology Restrictions. You may not create, modify, or change the behavior of, or authorize your licensees to create, modify, or change the behavior of, classes, interfaces, or subpackages that are in any way identified as "java", "javax", "sun" or similar convention as specified by Sun in any naming convention designation.
E.Distribution by Publishers. This section pertains to your distribution of the Software with your printed book or magazine (as those terms are commonly used in the industry) relating to Java technology ("Publication"). Subject to and conditioned upon your compliance with the restrictions and obligations contained in the Agreement, in addition to the license granted in Paragraph 1 above, Sun hereby grants to you a non-exclusive, nontransferable limited right to reproduce complete and unmodified copies of the Software on electronic media (the "Media") for the sole purpose of inclusion and distribution with your Publication(s), subject to the following terms: (i) You may not distribute the Software on a stand-alone basis; it must be distributed with your Publication(s); (ii) You are responsible for downloading the Software from the applicable Sun web site; (iii) You must refer to the Software as JavaTM 2 Platform Standard Edition Development Kit 5.0; (iv) The Software must be reproduced in its entirety and without any modification whatsoever (including, without limitation, the Binary Code License and Supplemental License Terms accompanying the Software and proprietary rights notices contained in the Software); (v) The Media label shall include the following information: Copyright 2004, Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Sun, Sun Microsystems, the Sun logo, Solaris, Java, the Java Coffee Cup logo, J2SE , and all trademarks and logos based on Java are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. This information must be placed on the Media label in such a manner as to only apply to the Sun Software; (vi) You must clearly identify the Software as Sun's product on the Media holder or Media label, and you may not state or imply that Sun is responsible for any third-party software contained on the Media; (vii) You may not include any third party software on the Media which is intended to be a replacement or substitute for the Software; (viii) You shall indemnify Sun for all damages arising from your failure to comply with the requirements of this Agreement. In addition, you shall defend, at your expense, any and all claims brought against Sun by third parties, and shall pay all damages awarded by a court of competent jurisdiction, or such settlement amount negotiated by you, arising out of or in connection with your use, reproduction or distribution of the Software and/or the Publication. Your obligation to provide indemnification under this section shall arise provided that Sun: (i) provides you prompt notice of the claim; (ii) gives you sole control of the defense and settlement of the claim; (iii) provides you, at your expense, with all available information, assistance and authority to defend; and (iv) has not compromised or settled such claim without your prior written consent; and (ix) You shall provide Sun with a written notice for each Publication; such notice shall include the following information: (1) title of Publication, (2) author(s), (3) date of Publication, and (4) ISBN or ISSN numbers. Such notice shall be sent to Sun Microsystems, Inc., 4150 Network Circle, M/S USCA12-110, Santa Clara, California 95054, U.S.A , Attention: Contracts Administration.
F.Source Code. Software may contain source code that, unless expressly licensed for other purposes, is provided solely for reference purposes pursuant to the terms of this Agreement. Source code may not be redistributed unless expressly provided for in this Agreement.
G. Third Party Code. Additional copyright notices and license terms applicable to portions of the Software are set forth in the THIRDPARTYLICENSEREADME.txt file. In addition to any terms and conditions of any third party opensource/freeware license identified in the THIRDPARTYLICENSEREADME.txt file, the disclaimer of warranty and limitation of liability provisions in paragraphs 5 and 6 of the Binary Code License Agreement shall apply to all Software in this distribution.
For inquiries please contact: Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. (LFI#141623/Form ID#011801)
The current guides for this product are available at: http://ca.com/support
The release number on the title page of a document might not correspond to the current product release number; however, all documentation delivered with the product, regardless of release number on the title page, does support your use of the current product release. The release number changes only when a significant portion of a document changes to support a new or updated product release. If no substantive changes are made to a document, the release number does not change. For example, a document for r2.4 can still be valid for r2.4 SP3 or even r3.1. Documentation bookshelves always reflect the current product release number.
Occasionally, we must update documentation outside of a new or updated release. To indicate a minor change to the documentation that does not invalidate it for any releases that it supports, we update the edition number on the cover page. First editions do not have an edition number.
Contact CA Support
For your convenience, CA Technologies provides one site where you can access the information you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following:
Provide Feedback
If you have comments or questions about CA Technologies product documentation, you can send a message to techpubs@ca.com.
If you would like to provide feedback about CA Technologies product documentation, complete our short customer survey, which is available on the CA Support website at http://ca.com/docs.
Copyright © 2010 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.