ca workload automation agent for hp integrity nonstop workload... · 2014-12-05 · ca technologies...

Release Notes Release 11.3.1, Second Edition

CA Workload Automation Agent for HP Integrity NonStop

This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation is proprietary information of CA and may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA.

If you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy.

The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.

The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice.

The manufacturer of this Documentation is CA.

Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.

Copyright © 2013 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

CA Technologies Product References

This document references the following CA Technologies products:

■ CA Network and Systems Management (CA NSM)

■ CA Universal Job Management Agent (CA UJMA)

■ CA Workload Automation Agent for HP Integrity NonStop (CA WA Agent for HP Integrity NonStop), formerly Tandem NSK

■ CA Workload Automation AE

■ CA Workload Automation ESP Edition

■ CA Workload Automation CA 7 Edition

■ CA Workload Control Center (CA WCC)

■ CA Service Desk Manager (CA SDM)

Contact CA Technologies

Contact CA Support

For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following resources:

■ Online and telephone contact information for technical assistance and customer services

■ Information about user communities and forums

■ Product and documentation downloads

■ CA Support policies and guidelines

■ Other helpful resources appropriate for your product

Providing Feedback About Product Documentation

If you have comments or questions about CA Technologies product documentation, you can send a message to [email protected].

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.

http://www.ca.com/support

mailto:[email protected]

http://www.ca.com/docs

http://www.ca.com/docs

Contents 5

Contents

Chapter 1: Agent Functionality 7

CA WA Agent for HP Integrity NonStop ....................................................................................................................... 7

Chapter 2: New Features 9

ASSIGN, PARAM, and DEFINE Command Options for HP Integrity NonStop ............................................................... 9

File Monitoring ............................................................................................................................................................. 9

Logging and Tracing .................................................................................................................................................... 10

Spool Files Retrieval ................................................................................................................................................... 10

Standard Streams ....................................................................................................................................................... 10

Chapter 3: Known Issues 11

Agent Responds if Ending Double Quotes are Missing .............................................................................................. 11

Agent Sends Syntax Error When an Invalid Keyword is Entered After a Valid Keyword ............................................ 11

Agent Truncates PARAM Messages ........................................................................................................................... 11

ASSIGN Logical Filenames Limited to 31 Characters .................................................................................................. 11

Customized TCP/IP Related DEFINEs are Removed When the Agent Starts .............................................................. 12

Chapter 4: Supported Systems and Requirements 13

System Requirements ................................................................................................................................................ 13

Hardware Requirements ..................................................................................................................................... 13

Software Requirements ...................................................................................................................................... 13

Supported Platforms and Scheduling Managers ........................................................................................................ 13

Chapter 5: Related Documentation 15

Agent Documentation ................................................................................................................................................ 15

CA Workload Automation AE Documentation ........................................................................................................... 15

CA Workload Automation ESP Edition Documentation ............................................................................................. 16

CA Workload Automation CA 7 Edition Documentation ............................................................................................ 16

Appendix A: Using the Agent to Schedule Jobs 17

Migrating from CA UJMA on CA Workload Automation AE ....................................................................................... 17

ASSIGN ........................................................................................................................................................................ 18

PARAM ....................................................................................................................................................................... 21

DEFINE ........................................................................................................................................................................ 23

6 Release Notes

Multiple Commands ................................................................................................................................................... 27

Chapter 1: Agent Functionality 7

Chapter 1: Agent Functionality

This section contains the following topics:

CA WA Agent for HP Integrity NonStop (see page 7)

CA WA Agent for HP Integrity NonStop

CA WA Agent for HP Integrity NonStop runs on the HP Integrity NonStop operating system, enabling the scheduling manager to submit and run workload on that platform.

The CA WA Agent for HP Integrity NonStop lets a user perform tasks such as the following:

■ Execute commands or scripts

■ Pass environment variables to the commands or scripts

■ Retrieve spool files

■ Verify the current job status of a given job

■ Monitor files

Chapter 2: New Features 9

Chapter 2: New Features


ASSIGN, PARAM, and DEFINE Command Options for HP Integrity NonStop (see page 9) File Monitoring (see page 9) Logging and Tracing (see page 10) Spool Files Retrieval (see page 10) Standard Streams (see page 10)

ASSIGN, PARAM, and DEFINE Command Options for HP Integrity NonStop

The new ASSIGN, PARAM, and DEFINE command options for HP Integrity NonStop are used to pass specific values to scripts, programs, and commands that the agent executes on behalf of the CA Workload Automation scheduling managers. The ability to pass these command parameters enhances the agent’s capability to reference and use system resources within the HP Integrity NonStop environment.

The implementation of the ASSIGN, PARAM, and DEFINE command options varies depending on the scheduling manager.

Note: For more information about using these command options, see the documentation for your scheduling manager.

File Monitoring

You can now define a File Monitoring job to monitor file activity for HP Integrity NonStop systems. The File Monitoring job can monitor when a file is created or updated.

Notes:

■ The CA WA Agent for HP Integrity NonStop does not support event-level triggers and wildcards in file triggers.

■ For more information about monitoring file activity, see the documentation for your scheduling manager.

Logging and Tracing

10 Release Notes

Logging and Tracing

Logging has been added to the agent to provide information about scheduled jobs. Logs must be cleared periodically to maintain disk space availability. The agent supports log file maintenance through an automatic log file rollover.

Function-level logging is stored in the EMS disk files. All errors and warnings are logged in the log file’s EMS log systems.

You can record the function-level traces of process when communication between the agent and scheduling manager has failed. The agent logs all incoming and outgoing messages in separate disk files and supports the per-process disk file tracing.

Note: For more information about logging and tracing, see the Implementation Guide.

Spool Files Retrieval

The agent generates spool files to store workload data. Spool file retrieval extracts spool file contents for a particular job from an agent whenever requested by a scheduling manager.

Notes:

■ For more information about spool file retrieval, see the Implementation Guide.

■ You must set the WLA-PASSW-REQUIRED environment variable to N when working with CA Workload Automation AE for spool file retrieval to work properly.

Standard Streams

Standard streams are pre-connected input and output channels between an application and its environment that exchange data when the application is running.

Note: For more information about standard streams, see the Implementation Guide.

Chapter 3: Known Issues 11

Chapter 3: Known Issues

The chapter details the known issues in CA Workload Automation Agent for HP Integrity NonStop r11.3.1.


Agent Responds if Ending Double Quotes are Missing (see page 11) Agent Sends Syntax Error When an Invalid Keyword is Entered After a Valid Keyword (see page 11) Agent Truncates PARAM Messages (see page 11) ASSIGN Logical Filenames Limited to 31 Characters (see page 11) Customized TCP/IP Related DEFINEs are Removed When the Agent Starts (see page 12)

Agent Responds if Ending Double Quotes are Missing

A series of error messages are displayed when the agent responds to specific combinations of the invalid AFM messages if ending double quotes are missing.

Agent Sends Syntax Error When an Invalid Keyword is Entered After a Valid Keyword

When an invalid keyword is entered after a valid keyword in an AFM message, the agent does not ignore the message and sends a syntax error.

Agent Truncates PARAM Messages

The agent truncates the PARAM messages in a job which consists of duplicate param_name entries.

ASSIGN Logical Filenames Limited to 31 Characters

The limits of the ASSIGN logical filename is 32 characters on the HP Integrity Nonstop system. But, the agent limits the length to 31 characters. If you send a job with a 32 characters ASSIGN logical filename, the following message is displayed:

ASSIGN logical file name is too long.

Customized TCP/IP Related DEFINEs are Removed When the Agent Starts

12 Release Notes

Customized TCP/IP Related DEFINEs are Removed When the Agent Starts

When you run the agent startup script using non-default values, a few TCP/IP-related DEFINEs may be removed. For example, if you have a TCPIP^PROCESS^NAME defined in $SYSTEM.SYSTEM.TACLLOCL. When you start the agent, the TCPIP^PROCESS^NAME DEFINE is removed.

The impact is:

■ The TACL session that starts the agent is not able to run the network-related command or program if the command or program expects customized DEFINEs. As a workaround, close the current TACL session and log in again.

■ If a command or program that runs inside an agent job expects customized DEFINEs, the job fails. For example, if you run a ping command in the job, the ping job fails with Guardian error 14, “Name does not resolve to supplied parameters", or another network-related error. As a workaround, create a TACL macro to wrap the command or program in and run it.

The DEFINEs involved are:

■ TCPIP^HOST^FILE

■ TCPIP^PROCESS^NAME

■ TCPIP^SERVICE^FILE

■ TCPIP^RESOLVER^NAME

Chapter 4: Supported Systems and Requirements 13

Chapter 4: Supported Systems and Requirements


System Requirements (see page 13) Supported Platforms and Scheduling Managers (see page 13)

System Requirements

Hardware Requirements

To run the CA WA Agent for HP Integrity NonStop on your HP Integrity NonStop server, the following must be available:

■ Support for G-Series, H-Series, and J-Series (Itanium) systems.

■ At least 90 MB of free disk space for the agent installation.

■ A LAN controller capable of supporting TCP/IP.

Software Requirements

To run CA WA Agent for HP Integrity NonStop on an HP Integrity NonStop server, the NonStop Kernel Version G06.29.02, H06.15, J06.13.0, or later software must be running and correctly configured.

Note: To see if any patches are required for specific releases of the NonStop system, check the Support matrix at https://support.ca.com/irj/portal/anonymous/phpsupcontent?contentID=%7bD0483718-32D2-4505-9088-8671471C9EED%7d.

Supported Platforms and Scheduling Managers

For current information regarding platform and scheduling manager support, see the CA Workload Automation Support web page at http://ca.com/support.

https://support.ca.com/irj/portal/anonymous/phpsupcontent?contentID=%7bD0483718-32D2-4505-9088-8671471C9EED%7d

https://support.ca.com/irj/portal/anonymous/phpsupcontent?contentID=%7bD0483718-32D2-4505-9088-8671471C9EED%7d



Chapter 5: Related Documentation 15

Chapter 5: Related Documentation

Documentation for the agent and scheduling managers is available in PDF format at http://ca.com/support.

Note: To view PDF files, you must download and install the Adobe Reader from the Adobe website if it is not already installed on your computer.


Agent Documentation (see page 15) CA Workload Automation AE Documentation (see page 15) CA Workload Automation ESP Edition Documentation (see page 16) CA Workload Automation CA 7 Edition Documentation (see page 16)

Agent Documentation

To install, configure, and maintain the agent, see the CA Workload Automation Agent for HP Integrity NonStop Implementation Guide.

CA Workload Automation AE Documentation

To work with the agent and CA Workload Automation AE, see the following documentation:

Task Documentation

Configure the scheduling manager to work with the agent

CA Workload Automation AE UNIX Implementation Guide

CA Workload Automation AE Windows Implementation Guide


CA Workload Automation ESP Edition Documentation

16 Release Notes

CA Workload Automation ESP Edition Documentation

To work with the agent and CA Workload Automation ESP Edition, see the following documentation:

Task Documentation

Configure the agent to work with the scheduling manager

CA Workload Automation ESP Edition Installation and Configuration Guide

CA Workload Automation CA 7 Edition Documentation

To work with the agent and CA Workload Automation CA 7 Edition, see the following documentation:

Task Documentation

Configure the scheduling manager to work with the agent

CA Integrated Agent Services Implementation Guide

CA Workload Automation CA 7 Edition Systems Programming Guide


Appendix A: Using the Agent to Schedule Jobs

There are different ways of defining jobs depending on your scheduling manager. For example, on CA Workload Automation AE, you can create a command job to run an HP Integrity NonStop TACL program, program, or script. Some scheduling managers, such as CA Workload Automation ESP Edition and CA Workload Automation CA 7 Edition, have implemented the new functionality through a native job type. For information specific to your scheduling manager, see the scheduling manager's documentation.

If your scheduling manager lets you define native jobs that accept a command, such as command jobs in CA Workload Automation AE, you can use keywords within the command parameter. Alternatively, for all scheduling managers, the HP Integrity NonStop environment lets you use runtime environment variables to schedule workload. The information in this section applies to defining a generic job or to scheduling workload at runtime; however, the examples show how to define CA Workload Automation AE command jobs only.

There are three new HP Integrity NonStop keywords available with this release of the agent: ASSIGN, PARAM, and DEFINE.

Migrating from CA UJMA on CA Workload Automation AE

If you are migrating from the CA Universal Job Management Agent (CA UJMA) on CA Workload Automation AE, update your job definitions as follows:

If there are spaces between the command and arguments, enclose the first word in double quotes and the rest of the string in single quotes.

For example, the following command must be updated because of the space between the first word (fup) and the rest of the string:

command: "fup dup $vol.subvol.file1, $vol.subvol1.file2,purge"

To update this command in the job definition, enclose "fup" in double quotes and the rest of the string in single quotes as follows:

command: "fup" 'dup $vol.subvol.file1, $vol.subvol1.file2,purge'

ASSIGN

18 Release Notes

ASSIGN

HP Integrity NonStop applications running on the HP Integrity NonStop platform use ASSIGN messages to assign logical file names to actual files. Optionally, ASSIGN messages can also specify the characteristics of such files. In CA Workload Automation AE, the envvars attribute is used to specify ASSIGN commands.

ASSIGN messages are sent to the agent through the scheduling manager.

This variable has the following syntax:

command: “filename”

envvars:ASN1=”asn_spec”

...

envvars:ASNn=”asn_spec”

filename

Specifies an object to run.

ASN

Indicates an ASSIGN message as follows:

logical_unit;actual_filename;PEXT=primary_extent_spec;SEXT=secondary_extent_s

pec;EXL=exclusion_spec;ACC=access_spec;CODE=file_code;REC=rec_size;BLOCK=bloc

k_size

logical_unit

Specifies the name to which a file name or file attributes are assigned.

Limits: Up to 32 characters; not case-sensitive; valid characters are alphanumeric, hyphen (-), or circumflex (^)

actual_filename

Specifies the name of the actual physical file in the following format:

$volume.subvolume.filename

Limits: Actual physical name consists of three fields of no more than 8 characters each, separated by a period

create_open_spec

Specifies a Create or Open Specification that sets certain file attributes.

ASSIGN


Notes:

■ You can define a maximum of 63 ASSIGN messages in a single job.

■ The entire value of one ASSIGN message can be up to 160 characters.

■ ASSIGN messages should be enclosed in double-quotation marks. If an ASSIGN message is defined with the envvars attribute, it is not completely enclosed in double quotes, for example, Env (ASN="LOGFILE; $c35.tcsobj.phyfile") or when defined as a separate keyword, ASN ("LOGFILE;$c35.tcsobj.phyfile").

The following table lists the optional fields of the Create or Open Specification types with descriptions and examples:

Keyword Create or Open Specification Type Description Example

PEXT primary_extent_spec Size of the primary file extent to be allocated to the file. It is an integer between 1 and 65535.

PEXT=1024

SEXT secondary_extent_spec Size of the secondary file extent to be allocated to the file. It is an integer between 1 and 65535.

SEXT=512

EXL exclusion_spec Specifies how processes access a file, as follows: EXCLUSIVE—Specifies that processes can access the file while the program has the file open. SHARED—Specifies that processes can read and write to the file while the program has the file open. PROTECTED—Specifies that processes can read, but not write to the file while the program has the file open.

EXL=EXCLUSIVE

EXL=SHARED

EXL=PROTECTED

ACC access_spec Specifies the access mode of the file operations that can be performed, as follows: I-O—Specifies that processes can read the file and write to it. INPUT—Specifies that processes can only write to the file. OUTPUT—Specifies that processes can only read the file.

ACC=I-O

ACC=INPUT

ACC=OUTPUT

CODE code File code. The maximum file code is 22222.

CODE=file-code

CODE=101

ASSIGN

20 Release Notes

REC rec Size of the record. It is an integer between 1 and 65535.

REC=record-size

REC=300

BLOCK block Size of data blocks used by the logical unit. It is an integer between 1 and 65535.

BLOCK=block-size

BLOCK=4096

Example: ASSIGN for Primary Extent Specification

This example defines a CA Workload Automation AE command job that executes a TACL command on the server1 HP Integrity NonStop server. The envvars attribute is used to specify ASSIGN commands. The job passes some specific variable values using the HP Integrity NonStop environment variables option ASSIGN.

insert_job: nsk14

job_type: CMD

command: "$VOLUME1.NSKOBJS.GETASGN"

envvars:

ASN1="LGFILE;$VOLUME1.NSKOBJS.PHFILE;PEXT=1024;CODE=101;BLOCK=500;REC=80"

machine: server1

owner: agent.oper@server1

ASN is a keyword to recognize ASSIGN messages. $VOLUME1.NSKOBJS.GETASGN is the sample test program to be scheduled, LGFILE is the logical file name, $VOLUME1.NSKOBJS.PHFILE is the physical file name, PEXT=1024 is the primary space extent specification, CODE=101 is the file type, BLOCK=500 is the block size, and REC=80 is the record size.

Example: ASSIGN for Primary Extent Specification and Secondary Extent Specification

This example defines a CA Workload Automation AE command job that executes a TACL command on the server1 HP Integrity NonStop server. The envvars attribute is used to specify ASSIGN commands. The job passes some specific variable values using the HP NonStop environment variables option ASSIGN.

insert_job: nsk13

job_type: CMD

command: "$VOLUME1.NSKOBJS.GETASGN"

envvars: ASN1="ABC;$VOLUME1.NSKOBJS.OABC"

envvars: ASN2="XYZ;$VOLUME1.NSKOBJS.GETPMSG;PEXT=4096;SEXT=200"

machine: server1


ASN is a keyword to recognize ASSIGN messages. $VOLUME1.NSKOBJS.GETASGN is the sample test program to be scheduled, ABC and XYZ are the logical file names, $VOLUME1.NSKOBJS.OABC and $VOLUME1.NSKOBJS.GETPMSG are the physical file names, PEXT=4096 is the primary space extent specification, and SEXT=200 is the secondary extent specification.

PARAM


PARAM

PARAM messages are used to create a parameter and give it a value. These messages are sent through the scheduling manager. In CA Workload Automation AE, the envvars attribute is used to specify the PARAM commands.

This message has the following syntax:


envvars:PRM1=”prm_spec”

...

envvars:PRMn=”prm_spec”

filename


PRM

Indicates a PARAM message as follows:

param_name=param_value

param_name

Specifies a user-defined parameter name. You cannot use duplicate param_name entries in the same job for the PARAM message.

Limits: Up to 32 characters; not case-sensitive; valid characters are alphanumeric, hyphen (-), or circumflex (^)

param_value

Specifies the value assigned to param_name.

Limits: The param_value can be up to 255 characters and must start with letters.

Notes:

■ You can define a maximum of 65535 PARAM messages in a single job.

■ The entire value of one PARAM message can be up to 287 characters.

■ A sum of number of PARAM and the combined length of all PARAM should be less than 511 characters.

■ PARAM messages should be enclosed in double-quotation marks.

PARAM

22 Release Notes

Example: PARAM with One Parameter Name and Value

This example defines a CA Workload Automation AE command job that executes a TACL command on the server1 HP Integrity NonStop server. The envvars attribute is used to specify the PARAM commands. The job passes some specific variable values using the HP Integrity NonStop environment variable option PARAM. You can create a parameter and give it a value.

insert_job: nsk11

job_type: CMD

command: "$VOLUME1.NSKOBJS.GETPMSG"

envvars: PRM1="VISH=320"

machine: server1


PRM is a keyword to recognize PARAM messages. $VOLUME1.NSKOBJS.GETPMSG is the sample test program to be scheduled, VISH is the parameter name and the value assigned to it is 320.

Example: PARAM with Two Parameter Names and Values

This example defines a CA Workload Automation AE command job that executes a TACL command on the server1 HP Integrity NonStop server. The envvars attribute is used to specify the PARAM commands. The job passes some specific variable values using the HP Integrity NonStop environment variables option PARAM. You can create a parameter and give it a value.

insert_job: nsk10

job_type: CMD

command: "$VOLUME1.NSKOBJS.GETPMSG"

envvars: PRM1="ABC=100"

envvars: PRM2="XYZ=800"

machine: server1


PRM is a keyword to recognize PARAM messages. $VOLUME1.NSKOBJS.GETPMSG is the sample test program to be scheduled, ABC and XYZ are the parameter names and the values assigned to them are 100 and 800 respectively.

Example: A Command Statement

This example defines a TACL routine ($DATA2.MONTHLY.PURGJOB1) that purges files that reside at a specific location and are greater than 30 days old. The location and number of days are sent to the agent.

command:"$DATA2.MONTHLY.PURGJOB1"

envvars: PRM1="PURGELOC=$DATA1.NSKDATA"

envvars: PRM2="AGE=30"

DEFINE


DEFINE

DEFINE messages are file-system elements that pass information to a process. For example, DEFINE can be used to pass attributes to a process to provide:

■ An alternate name for accessing a file.

■ A list of subvolumes to search for a file name.

■ A simple way to set up attributes for labeled-tape processing.

■ A simple means of passing attributes to the spooler subsystem.

DEFINE messages are stored within the program file segment (PFS) of the creating process. The programmatic approach stores DEFINE in the context of the creating process and affects the environment of the creating process. DEFINE can be passed to other processes when creating new processes.

DEFINE allow attributes to be grouped and named. These attributes can then be passed to a process or retrieved by specifying the name of the DEFINE. DEFINE removes the need to set up attributes each time a given process is invoked. Specifically, several classes of DEFINE each pass attributes to a specific process or class of processes.

Examples of DEFINE classes are:

■ CLASS MAP DEFINE

■ CLASS SEARCH DEFINE

■ CLASS TAPE DEFINE

■ CLASS DEFAULTS DEFINE

The following is the syntax of the DEFINE variable:


envvars:DEF1=”def_spec”

...

envvars:DEFn=”def_spec”

DEFINE

24 Release Notes

filename


job_attributes

Specifies the job attributes.

DEF

Indicates a DEFINE message as follows:

define_name;define_attribute_name=define_attribute_value

define_name

Specifies the user-defined name.

Limits: Up to 2-24 characters; case-sensitive; valid characters are alphanumeric, hyphen (-), underscore (_), or circumflex (^)

Note: The first character of define_name must be a letter.

define_attribute_name

Specifies the attribute name of the DEFINE keyword.

define_attribute_value

Specifies the attribute value of the DEFINE keyword.

Limits: case-sensitive; valid characters are alphanumeric, hyphen (-), underscore (_), or circumflex (^)

Notes:

■ You can define a maximum of 65535 ASSIGN messages in a single job.

■ The entire value of one DEFINE message can be up to 4094 characters

■ A sum of number of DEFINEs and combined length of all DEFINEs should be less than 4095 characters.

■ DEFINE messages should be enclosed in double-quotation marks

The following table describes the possible attribute names and values for the DEFINE classes and attributes:

Class Name Attribute Name Attribute Value

CLASS MAP

CLASS MAP

FILE file-name

CLASS SEARCH

CLASS SEARCH

RELSUBVOLn subvolume-name

SUBVOLn subvolume-name

DEFINE



CLASS SORT

CLASS SORT

BLOCK size

CPU cpu-number

CPUS cpu-number,cpu-number..|ALL }

MODE - AUTOMATIC

- MINSPACE

- MINTIME

NOTCPUS cpu-number,cpu-number...

PRI priority

PROGRAM file-name

SCRATCH file-name

SEGMENT size

SUBSORTS DEFINE-name, DEFINE-name...

SWAP file-name

CLASS TAPE

CLASS TAPE

BLOCKLEN block-length

DENSITY - 800

- 1600

- 6250

RETENTION days

SYSTEM \node-name

TAPEMODE - STARTSTOP

- STREAM

USE - IN

- OUT

- EXTEND

- OPENFLAG

VERSION num

VOLUME vol-id | SCRATCH

DEVICE device-name

REELS volumes

EBCDIC { IN | OUT | ON | OFF }

DEFINE

26 Release Notes


EXPIRATION date

FILEID file-name

FILESECT volume-order

FILESEQ file-order

GEN gen-num

LABELS - ANSI

- IBM

- OMITTED

- BYPASS

- BACKUP

- IBMBACKUP

MOUNTMSG " text"

OWNER owner-id

RECFORM - F

- U

RECLEN record-length

Example: Job Definition Using DEFINE Environment Variable

This example defines a CA Workload Automation AE command job that executes a TACL command on the server1 HP Integrity NonStop server. The envvars attribute is used to specify DEFINE commands. The job passes some specific variable values using the HP Integrity NonStop environment variables option DEFINE.

insert_job: nsk15

job_type: CMD

command: "$VOLUME1.NSKOBJS.GETDEF"

envvars: DEF1="DABC;CLASS=MAP;FILE="$VOLUME1.NSKOBJS.GETDEF"

machine: server1


DEF is a keyword to recognize DEFINE messages. $VOLUME1.NSKOBJS.GETDEF is the sample test program to be scheduled and DABC is the DEFINE name.

Multiple Commands


Multiple Commands

You can also code multiple ASSIGN, PARAM, or DEFINE commands in a job. The following is the syntax for multiple variables:


envvars: ASN1=”asn_spec”

envvars: PRM1=”prm_spec”

envvars: DEF1=”def_spec”

Example: A Command Statement Using the ASSIGN and PARAM Keywords

This example defines a program ($DATA1.SERVOBJ.ROUTER) that communicates with a running process named $VOLUME1.NSKOBJS.GETPMSG. The ASSIGN keyword is used to pass information to the running process to create a log file named LOG1.

command: "$DATA1.SERVOBJ.ROUTER"

envvars: ASN1="SNAME;$VOLUME1.NSKOBJS.GETPMSG;PEXT=100;SEXT=500"

envvars: PRM1="LNAME=$DATA2.LOGS.LOG1"

ca workload automation agent for hp integrity nonstop workload... · 2014-12-05 · ca technologies...

Documents