CA Workload Automation Agent for Micro Focus

Transcription

1 CA Workload Automation Agent for Micro Focus Implementation Guide r11.3.4

2 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 , , and (c)(1) - (2) and DFARS Section (b)(3), as applicable, or their successors. Copyright 2014 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

3 CA Technologies Product References This document references the following CA Technologies products: CA Process Automation CA Workload Automation AE CA Workload Automation Agent for Application Services (CA WA Agent for Application Services) CA Workload Automation Agent for Databases (CA WA Agent for Databases) CA Workload Automation Agent for i5/os (CA WA Agent for i5/os) CA Workload Automation Agent for Informatica (CA WA Agent for Informatica) CA Workload Automation Agent for Linux (CA WA Agent for Linux) CA Workload Automation Agent for Micro Focus (CA WA Agent for Micro Focus) CA Workload Automation Agent for Microsoft SQL Server (CA WA Agent for Microsoft SQL Server) CA Workload Automation Agent for Oracle E-Business Suite (CA WA Agent for Oracle E-Business Suite) CA Workload Automation Agent for PeopleSoft (CA WA Agent for PeopleSoft) CA Workload Automation Agent for Remote Execution (CA WA Agent for Remote Execution) CA Workload Automation Agent for SAP (CA WA Agent for SAP) CA Workload Automation Agent for UNIX (CA WA Agent for UNIX) CA Workload Automation Agent for Web Services (CA WA Agent for Web Services) CA Workload Automation Agent for Windows (CA WA Agent for Windows) CA Workload Automation CA 7 Edition CA Workload Automation DE CA Workload Automation Desktop Client (CA WA Desktop Client) CA Workload Automation ESP Edition CA Workload Control Center

4 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 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 techpubs@ca.com. To provide feedback about CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at

5 Contents Chapter 1: Introduction 7 Intended Audience... 7 Agents and Agent Plug-ins... 7 CA WA Agent for Micro Focus... 8 Job Types Supported by CA WA Agent for Micro Focus... 8 Chapter 2: Implementation Checklist 9 How to Install and Configure CA WA Agent for Micro Focus... 9 Deciding Whether to Create an Alias Chapter 3: Installing the Agent Plug-in 11 Controlling the Agent Plug-in Install CA WA Agent for Micro Focus on Windows Load the event_manager Exit Routine on Windows Install CA WA Agent for Micro Focus on UNIX Verify Micro Focus Loaded the event_manager Exit Routine How to Remove the Agent Plug-in Disable CA WA Agent for Micro Focus Remove the Agent Plug-in from the Scheduling Manager Chapter 4: Your Scheduling Manager and the Agent Plug-in 19 Configuring the Scheduling Manager to Work with the Agent Plug-in Running a Verification Test Chapter 5: Configuring the Agent Plug-in 21 How to Configure Agent Parameters Configure Agent Parameters on the Agent Configure Agent Parameters on the Scheduling Manager CA WA Agent for Micro Focus Parameters in the agentparm.txt File How to Set Up an Alias for the Agent Plug-in Create an Alias for the Agent Plug-in Configuring an Alias on the Scheduling Manager Configure Local Security for Micro Focus Jobs Configure How Often Job State Messages are Purged Processing Success and Failure Criteria Contents 5

6 Change the CMPC Offset Values Chapter 6: Related Documentation 29 CA Workload Automation AE Documentation CA Workload Automation DE Documentation CA Workload Automation ESP Edition Documentation Index 31 6 Implementation Guide

7 Chapter 1: Introduction This section contains the following topics: Intended Audience (see page 7) Agents and Agent Plug-ins (see page 7) CA WA Agent for Micro Focus (see page 8) Job Types Supported by CA WA Agent for Micro Focus (see page 8) Intended Audience This document is for system administrators who are responsible for upgrading, installing, and configuring agents. You require knowledge of the operating system where the agent is installed and any third-party products or software technology that the agent uses. Notes: The term Windows refers to any Microsoft Windows operating system supported by the agent. The UNIX instructions in this document also apply to Linux systems unless otherwise noted. Agents and Agent Plug-ins Agents are the key integration components of CA Technologies workload automation products. Agents let you automate, monitor, and manage workload on all major platforms, applications, and databases. To run workload on a particular system, you install an agent on that system. If your workload must run on a UNIX computer, for example, you can install and configure the CA WA Agent for UNIX. The agent can run UNIX scripts, execute UNIX commands, transfer files using FTP, monitor file activity on the agent computer, and perform many other tasks. You can extend the functionality of the agent by installing one or more agent plug-ins in the agent installation directory. If you have a relational database such as Oracle, you can install a database agent plug-in to query and monitor the database. Other agent plug-ins are also available. For more information about agent plug-ins, see the Implementation Guide for the appropriate agent plug-in. Note: The agent plug-ins are only available for UNIX, Linux, and Windows operating environments. Chapter 1: Introduction 7

8 CA WA Agent for Micro Focus Example: Workload with Different Types of Jobs The following workload contains z/os jobs, a UNIX job, an SAP job, and a Windows job, running on different computers, in different locations, and at different times: CA WA Agent for Micro Focus CA WA Agent for Micro Focus provides an interface to the Micro Focus Enterprise Server. Job Types Supported by CA WA Agent for Micro Focus With the CA WA Agent for Micro Focus, you can define and run the following job: Micro Focus Lets you run mainframe JCL and COBOL programs in a UNIX or Windows environment. 8 Implementation Guide

9 Chapter 2: Implementation Checklist This section contains the following topics: How to Install and Configure CA WA Agent for Micro Focus (see page 9) Deciding Whether to Create an Alias (see page 10) How to Install and Configure CA WA Agent for Micro Focus CA WA Agent for Micro Focus is an agent plug-in that installs into the CA WA Agent for UNIX, Linux, or Windows installation directory. Note: Before you install the agent plug-in, install and configure the agent. To install and configure the agent plug-in, follow these steps: 1. Review the system requirements in the CA Workload Automation Agent for Micro Focus Release Notes. 2. Decide whether to create an alias (see page 10). 3. Install the agent plug-in: On Windows (see page 11) On UNIX (see page 13) 4. (Windows only) Load the event_manager exit routine (see page 13). 5. Verify Micro Focus loaded the event_manager exit routine (see page 16). 6. Configure local security for Micro Focus jobs (see page 24). 7. Configure the scheduling manager to work with the agent plug-in (see page 19). 8. (Optional) Run a verification test (see page 20). Chapter 2: Implementation Checklist 9

10 Deciding Whether to Create an Alias Deciding Whether to Create an Alias You install an agent plug-in into the agent installation directory to extend the core functionality of the agent. By default, the agent plug-in operates under the same agent name that is assigned to the agent. An alias lets you create a unique agent name for an agent plug-in, which is useful for controlling agent security or for setting up clustered environments. The installation program generates the alias by adding a suffix to the agent name. Note: If you are installing the agent plug-in to work with CA Workload Automation DE, you must set up an alias. Setting up an alias for use with other scheduling managers is optional. Suppose you have installed an agent named AGT10 on a Windows computer. Users who have access to that agent through their security permissions specify AGT10 as the agent name in their job definitions. Now suppose that you install an agent plug-in into the installation directory for AGT10. You can create an alias for the agent plug-in, for example, AGT10_MF. You can then restrict access to that alias to only those users that run Micro Focus workload. Those specific users then must specify AGT10_MF as the agent name in their job definitions. Each agent plug-in has a default alias that you can enable during installation. For example, the agent plug-in for CA WA Agent for Micro Focus has the default alias agentname_mf. You can enable or change the default alias name after installation. To work, you must also configure the alias on the scheduling manager. Note: To configure agent aliasing for clustered environments, see the CA Workload Automation Agent for UNIX, Linux, or Windows Implementation Guide. 10 Implementation Guide

11 Chapter 3: Installing the Agent Plug-in This section contains the following topics: Controlling the Agent Plug-in (see page 11) Install CA WA Agent for Micro Focus on Windows (see page 11) Install CA WA Agent for Micro Focus on UNIX (see page 13) Verify Micro Focus Loaded the event_manager Exit Routine (see page 16) How to Remove the Agent Plug-in (see page 16) Controlling the Agent Plug-in You control the agent plug-in using the agent where the plug-in is installed. Depending on your operating system, you have several options for starting or stopping the agent. On UNIX, issue a command to run a start or stop script. On Windows, start or stop the agent as a Windows service. Note: For more information about starting and stopping the agent, see the CA Workload Automation Agent for UNIX, Linux, or Windows Implementation Guide. Install CA WA Agent for Micro Focus on Windows You install the agent plug-in on Windows using an interactive program that prompts you for the required information. Follow these steps: 1. Copy the microfocus_win.pak file into the agent installation directory. You can copy this file from the product DVD or you can download a zip file that contains the file from the CA Support Online website ( 2. Change to the agent installation directory. For example, type the following command: cd C:\Program Files\CA\WA Agent R Stop the agent using the following command: cybagent -s 4. Stop the Micro Focus server. Chapter 3: Installing the Agent Plug-in 11

12 Install CA WA Agent for Micro Focus on Windows 5. Start the installation program using the following command: PluginInstaller.exe microfocus_win.pak "install_dir" install_dir Specifies the agent installation directory. For example, type the following command: PluginInstaller.exe microfocus_win.pak. 6. Enter the path to the BIN directory of Micro Focus Enterprise Server, for example: C:\Program Files\Micro Focus\Studio 5.0\Base\BIN 7. Decide whether to create an alias as follows: Y N Enables the default alias. Disables the default alias. Default: Y Note: The default alias for the Micro Focus Agent plug-in is agentname_mf. The installation program displays a message and closes automatically upon a successful installation. You are now ready to load the event_manager exit routine (see page 13). Note: The agent installation program backs up all modified and replaced files. The backup files are compressed into a file that is named backup_timestamp.zip, located in the backups subdirectory of the agent installation directory. You can use Winzip or other similar utilities to open the backup file. A backup copy of the agentparm.txt file is stored in the zip file. 12 Implementation Guide

13 Install CA WA Agent for Micro Focus on UNIX Load the event_manager Exit Routine on Windows You configure a Micro Focus Enterprise Server environment variable to load the event_manager exit routine that passes Micro Focus event information to the agent. Follow these steps: 1. Open the System Properties dialog on your Windows computer. For example, click Start, Control Panel, System. 2. Click the Advanced tab. 3. Click Environment Variables. 4. Click New to create a system environment variable. 5. Enter the following information: Variable name ES_EMP_EXIT_1 Variable value event_manager 6. Restart the Windows computer. 7. Start the agent using the following command: cybagent -a 8. Start the Micro Focus server. Install CA WA Agent for Micro Focus on UNIX You install the agent plug-in on UNIX using an interactive program that prompts you for the required information. Follow these steps: 1. Copy the CA WA Agent for Micro Focus plug-in file for your system into the agent installation directory. For example, on 64-bit Linux, the plug-in file name is microfocus_linux_x86_64.pak. You can copy this file from the product DVD or you can download a zip file that contains the file from the CA Support Online website ( 2. Change to the agent installation directory. For example, type the following command: cd opt/ca/wa_agent_r11_3 Chapter 3: Installing the Agent Plug-in 13

14 Install CA WA Agent for Micro Focus on UNIX 3. Stop the agent using the following command:./cybagent -s 4. Stop all Micro Focus servers that are running under the Micro Focus Directory Server. 5. Stop the Micro Focus Directory Server (mfds) process. 6. (AIX only) Run the following command as root to remove unused modules from memory: slibclean 7. Start the installation program using the following command:./plugininstaller plugin_file install_dir plugin_file Specifies the name of the plug-in file. For example, on 64-bit Linux, the plug-in file name is microfocus_linux_x86_64.pak. install_dir Specifies the agent installation directory. 8. Enter the path to the bin directory on the Micro Focus Enterprise Server, for example: /opt/microfocus/enterpriseserver/bin 9. Enter the path to the lib directory on the Micro Focus Enterprise Server, for example: /opt/microfocus/enterpriseserver/lib 10. Decide whether to create an alias as follows: Y N Enables the default alias. Disables the default alias. Default: Y Note: The default alias for the Micro Focus Agent plug-in is agentname_mf. The installation program displays a message and closes automatically upon a successful installation. 14 Implementation Guide

15 Install CA WA Agent for Micro Focus on UNIX 11. Set the Micro Focus environment, for example:. /opt/microfocus/enterprisedeveloper/bin/cobsetenv This script sets the COBDIR, LD_LIBRARY_PATH, and other Micro Focus environment variables. 12. (Linux 64-bit only) Add lib64 to the LD_LIBRARY_PATH environment variable: export LD_LIBRARY_PATH=/usr/lib64:$LD_LIBRARY_PATH 13. Set the ES_EMP_EXIT_1 environment variable: export ES_EMP_EXIT_1=event_manager 14. Start the agent using the following command:./cybagent & 15. Start the Micro Focus Directory Server (mfds) process. 16. Start all Micro Focus servers that are running under the Micro Focus Directory Server. Note: The agent installation program backs up all modified and replaced files. The backup files are compressed into a file that is named backup_timestamp.zip, located in the backups subdirectory of the agent installation directory. You can use Winzip or other similar utilities to open the backup file. A backup copy of the agentparm.txt file is stored in the zip file. Chapter 3: Installing the Agent Plug-in 15

16 Verify Micro Focus Loaded the event_manager Exit Routine Verify Micro Focus Loaded the event_manager Exit Routine You verify that Micro Focus loaded the event_manager exit routine using Enterprise Server Administration. Follow these steps: 1. Start Enterprise Server Administration. 2. Locate the row for your Micro Focus Server and click Details in the Current status column. The details page for the server appears. 3. Click the Control tab. 4. Click ES Monitor and Control. The Server Information page appears. 5. Press Display located in the Diagnostics section on the left side of the page. The log activity for the server appears in a browser. 6. Search the log text for event_manager. The following text indicates Micro Focus loaded the event_manager exit routine successfully: Event Manager exit enabled (event_manager) How to Remove the Agent Plug-in You can remove an agent plug-in when you no longer require it. To remove the agent plug-in, follow these steps: 1. Disable the agent plug-in (see page 16). 2. (Optional) Remove the agent plug-in from the scheduling manager (see page 18). Disable CA WA Agent for Micro Focus Use this procedure when you want to remove CA WA Agent for Micro Focus from your system. Follow these steps: 1. Verify that all workload is complete. 2. Stop the agent. 16 Implementation Guide

17 How to Remove the Agent Plug-in 3. Stop Micro Focus Enterprise Server if you want to remove the event_manager shared library. 4. Open the agentparm.txt file that is located in the agent installation directory. 5. Comment out the plugins.start_internal_n parameter if you created an alias during the agent plug-in installation. Renumber any subsequent plugins.start_internal_n parameters. Note: Renumber all other agent plug-ins that are assigned a greater number than the agent plug-in you are uninstalling. 6. Comment out the communication.alias parameter if you created an alias during the agent plug-in installation. Note: Renumber any subsequent communication.alias_n parameters. 7. Comment out the microfocus.commandpath parameter. 8. Save and close the agentparm.txt file. 9. Remove the microfocus.jar file from the JARs subdirectory of the agent installation directory. 10. (AIX only) Run slibclean from the command line to remove unused modules from memory. 11. Remove the following files from the Micro Focus directory: event_manager.* init.txt or cyb_init.txt 12. (Windows only) Remove the ES_EMP_EXIT_1 variable from your system. 13. Start the agent. Example: Renumber the plugins.start_internal_n Parameter Suppose that you have the following agent plug-ins set in the agentparm.txt file: plugins.start_internal_1=runner plugins.start_internal_2=sap plugins.start_internal_3=ftp plugins.start_internal_4=microfocus To disable the agent plug-in for CA WA Agent for Micro Focus, you would modify the agentparm.txt file as follows: plugins.start_internal_1=runner plugins.start_internal_2=sap plugins.start_internal_2=ftp #plugins.start_internal_3=microfocus Chapter 3: Installing the Agent Plug-in 17

18 How to Remove the Agent Plug-in Example: Renumber the communication.alias_n Parameter Suppose that you have two alias agent plug-ins. The agentparm.txt file has the following parameters: communication.alias_1=agentname_sap communication.alias_2=agentname_mf To disable the agent plug-in for CA WA Agent for Micro Focus, modify the agentparm.txt file as follows: communication.alias_1=agentname_sap #communication.alias_1=agentname_mf More information: Load the event_manager Exit Routine on Windows (see page 13) Remove the Agent Plug-in from the Scheduling Manager In addition to disabling the agent plug-in, you can remove it from the configuration on the scheduling manager. Note: For detailed instructions to remove the agent from the scheduling manager, see the documentation for your scheduling manager. 18 Implementation Guide

19 Chapter 4: Your Scheduling Manager and the Agent Plug-in This section contains the following topics: Configuring the Scheduling Manager to Work with the Agent Plug-in (see page 19) Running a Verification Test (see page 20) Configuring the Scheduling Manager to Work with the Agent Plug-in If you have defined the following items for the agent plug-in, configure the items on the scheduling manager: An alias A user For detailed configuration instructions, see the documentation for your scheduling manager. Chapter 4: Your Scheduling Manager and the Agent Plug-in 19

20 Running a Verification Test Running a Verification Test For your verification test, you define and run a Micro Focus job. To define the job, you require the following information: Agent name Specifies the name of your agent or the alias for the CA WA Agent for Micro Focus if you created an alias. JCL name JCL type Specifies the path to and name of a JCL file to run. Specifies whether to pass the JCL by content or by reference to the server. Micro Focus server address type Specifies whether the address is a server name or the IP address and port of the Micro Focus server. Micro Focus server address Specifies the server name or the IP address and port of the Micro Focus server. For more information about defining a Micro Focus job, see the documentation for your scheduling manager. 20 Implementation Guide

21 Chapter 5: Configuring the Agent Plug-in This section contains the following topics: How to Configure Agent Parameters (see page 21) CA WA Agent for Micro Focus Parameters in the agentparm.txt File (see page 22) How to Set Up an Alias for the Agent Plug-in (see page 23) Configure Local Security for Micro Focus Jobs (see page 24) Configure How Often Job State Messages are Purged (see page 25) Processing Success and Failure Criteria (see page 26) How to Configure Agent Parameters You configure agent parameters by editing the agentparm.txt file, which is located in the agent installation directory. When you install the agent, the installation program adds frequently configured agent parameters to the file. Other agent parameters exist, which you must manually add to the agentparm.txt file to configure the agent. For any configuration changes to take effect, always stop and restart the agent. For some agent parameters, such as the agent name and communication parameters, also configure the parameters on the scheduling manager. To configure agent parameters, do the following steps: 1. Configure agent parameters on the agent (see page 21). 2. Configure agent parameters on the scheduling manager (see page 22). Configure Agent Parameters on the Agent Configure agent parameters on CA WA Agent for UNIX, Linux, or Windows using the following procedure. Follow these steps: 1. Change to the agent installation directory. 2. Stop the agent using one of the following commands: On UNIX:./cybAgent -s On Windows: cybagent -s Chapter 5: Configuring the Agent Plug-in 21

22 CA WA Agent for Micro Focus Parameters in the agentparm.txt File 3. Open the agentparm.txt file that is located in the agent installation directory. 4. Make the required changes to the agent parameters. 5. Save and close the agentparm.txt file. 6. Start the agent using one of the following commands: On UNIX:./cybAgent & On Windows: cybagent -a Configure Agent Parameters on the Scheduling Manager When you change an agent parameter in the agentparm.txt file that is also defined on the scheduling manager, such as the agent name, configure the agent parameter on the scheduling manager. Note: For detailed instructions to configure agent parameters on the scheduling manager, see the documentation for your scheduling manager. CA WA Agent for Micro Focus Parameters in the agentparm.txt File You can configure the following parameters in the agentparm.txt file. The file is located in the agent installation directory. You can open the agentparm.txt file in any standard text editor. communication.alias_n Defines the alias name for the agent. The n suffix increments sequentially for each alias agent. Note: To enable an alias on the agent, verify that the comment character (#) is removed from the parameter line. Default: agentname_mf mf.checkforoutdatedafms Indicates whether to enable the cleanup process to purge job state messages. By default, the cleanup process purges messages that are older than five hours ( milliseconds). You can configure the cleanup threshold by setting the microfocus.cleanup parameter in the agentparm.txt file. Default: true 22 Implementation Guide

23 How to Set Up an Alias for the Agent Plug-in MF_EXITCODE_Base Defines the starting CMPC offset value that the agent uses to convert string-based completion codes that Micro Focus returns. Default: Note: Setting MF_EXITCODE_Base=0 overrides the completion code conversion the agent uses and returns the completion codes as is from Micro Focus. MF_EXITCODE_Step Defines the increment between completion type CMPC offset values. Default: microfocus.cleanup Specifies the cleanup threshold in milliseconds. The cleanup process purges job state messages that are older than the specified value. Default: (5 hours) microfocus.commandpath Defines the path to the event_manager.dll. This value corresponds to the path, set during the agent plug-in installation, to the BIN directory of the Micro Focus Enterprise Server. How to Set Up an Alias for the Agent Plug-in During the agent plug-in installation, you are prompted to create a default alias, which you can change after installation. If you enable an alias on the agent plug-in, also configure the alias on the scheduling manager. To set up an alias for the agent plug-in, follow these steps: 1. Create an alias for the agent plug-in (see page 24). 2. Configure the alias on the scheduling manager (see page 24). Chapter 5: Configuring the Agent Plug-in 23

24 Configure Local Security for Micro Focus Jobs Create an Alias for the Agent Plug-in An alias lets you create a unique agent name for an agent plug-in. Each agent plug-in has a default alias, which you can enable or change. To create an alias for the agent, configure the following parameter on the agent: communication.alias_n Defines the alias name for the agent. The n suffix increments sequentially for each alias agent. Note: To enable an alias on the agent, verify that the comment character (#) is removed from the parameter line. Configuring an Alias on the Scheduling Manager When you create an alias for an agent plug-in, also configure the alias on the scheduling manager. Define the alias on the scheduling manager with the same address, port number, and encryption key as the agent where the agent plug-in is installed. Note: For detailed instructions to configure an alias on the scheduling manager, see the documentation for your scheduling manager. Configure Local Security for Micro Focus Jobs If local security is enabled on the agent, add a security rule to the security.txt file so that Micro Focus jobs can run on the agent computer. Follow these steps: 1. Open the agentparm.txt file that is located in the agent installation directory. 2. Review the security.level parameter setting. If security.level is set to on, local security is enabled. Continue with Step 3 to configure local security. If security.level is set to off, local security is disabled. No changes are required. Close the agentparm.txt file. 3. Open the security.txt file that is located in the agent installation directory. 24 Implementation Guide

25 Configure How Often Job State Messages are Purged 4. Add the following security rule. x a * * install_dir\cybmfcommand install_dir Specifies the agent installation directory. Note: This rule lets any scheduling manager user submit Micro Focus jobs that run under any agent user ID. 5. Save and close the file. 6. Refresh the security.txt file using the following command: cybagent -r The local security is configured to allow Micro Focus jobs to run. Configure How Often Job State Messages are Purged In earlier releases, records in the agent job state database are not cleared after jobs (submitted outside of the agent) complete in Micro Focus. If the Micro Focus job ID range is recycled, agent-submitted jobs can reuse job IDs of cached status updates from the previous cycle. To prevent invalid job status information being sent to the scheduling manager, a cleanup process is enabled on the agent to purge job state messages. To configure how often job state messages are purged, configure the following parameters on the agent: mf.checkforoutdatedafms Indicates whether to enable the cleanup process to purge job state messages. By default, the cleanup process purges messages that are older than five hours ( milliseconds). You can configure the cleanup threshold by setting the microfocus.cleanup parameter in the agentparm.txt file. Default: true microfocus.cleanup Specifies the cleanup threshold in milliseconds. The cleanup process purges job state messages that are older than the specified value. Default: (5 hours) More information: CA WA Agent for Micro Focus Parameters in the agentparm.txt File (see page 22) Chapter 5: Configuring the Agent Plug-in 25

26 Processing Success and Failure Criteria Processing Success and Failure Criteria Some completion codes (CMPC) the agent plug-in returns contain a character prefix to determine the completion type and distinguish the code from normal completion. For example, a Micro Focus job that ends with a JES error returns CON03, indicating a job concluded error. You specify success and failure criteria in the job definition using exit codes. The exit codes are compared against the actual CMPC returned by a Micro Focus job. To evaluate job success and failure criteria, string-based CMPC values must be converted to numbers. The conversion procedure the agent uses adds a CMPC offset based on the type of completion. For example, to treat the completion code CON03 as success, specify as a successful exit. The value results from combining the CMPC offset for job concluded errors ( ) listed in the following table with the last two digits of the CON03 completion code. System abend completion codes (prefixed by S) are hexadecimal. The agent only looks at the actual completion code, not the appended reason code after the '-' character. For example, to treat the completion code S as success, specify as a successful exit code. The value results from combining the CMPC offset for system abends ( ) with the hexadecimal value of 806 (2054). Normal completion return codes have no prefix and thus no offset is added. The following table lists the default CMPC offset values the agent uses to convert Micro Focus job completion codes. Note: You can configure the agent to change these CMPC offset values. Completion Type Completion Code (CMPC) Prefix CMPC Offset Normal User abend U System abend S RU error RU Unknown error UN RTS error RTS Job concluded error CON SEP termination SEP Implementation Guide

27 Processing Success and Failure Criteria More information: Change the CMPC Offset Values (see page 27) Change the CMPC Offset Values The completion code (CMPC) offset values the agent uses are set using the following algorithm: CMPC Offset = Base + Step By default, the agent is set to a Base value of and a Step value of You can you configure the agent to change the default CMPC offset values by changing the Base, the Step, or both values. To change the CMPC offset values, configure the following parameters on the agent: MF_EXITCODE_Base Defines the starting CMPC offset value that the agent uses to convert string-based completion codes that Micro Focus returns. Default: Note: Setting MF_EXITCODE_Base=0 overrides the completion code conversion the agent uses and returns the completion codes as is from Micro Focus. MF_EXITCODE_Step Defines the increment between completion type CMPC offset values. Default: Example: Changing the CMPC Offset Increment Suppose that you want to increase the increment between the completion codes the agent uses from to You can add the following parameter to the agentparm.txt file: MF_EXITCODE_Step= The agent then uses the following CMPC offset values: Completion Type Completion Code (CMPC) Prefix CMPC Offset Normal Chapter 5: Configuring the Agent Plug-in 27

28 Processing Success and Failure Criteria Completion Type Completion Code (CMPC) Prefix CMPC Offset User abend U System abend S RU error RU Unknown error UN RTS error RTS Job concluded error CON SEP termination SEP More information: How to Configure Agent Parameters (see page 21) 28 Implementation Guide

29 Chapter 6: Related Documentation Documentation for the agent and scheduling managers is available in HTML and PDF format at Note: To view PDF files, download and install the Adobe Reader from the Adobe website if it is not already installed on your computer. This section contains the following topics: CA Workload Automation AE Documentation (see page 29) CA Workload Automation DE Documentation (see page 30) CA Workload Automation ESP Edition Documentation (see page 30) CA Workload Automation AE Documentation To work with the agent and CA Workload Automation AE, see the following documentation: Task Configure the scheduling manager to work with the agent Define, monitor, and control jobs Documentation CA Workload Automation AE UNIX Implementation Guide CA Workload Automation AE Windows Implementation Guide CA Workload Automation AE Reference Guide CA Workload Automation AE User Guide CA Workload Control Center Workload Scheduling Guide Chapter 6: Related Documentation 29

30 CA Workload Automation DE Documentation CA Workload Automation DE Documentation To work with the agent and CA Workload Automation DE, see the following documentation: Task Configure the scheduling manager to work with the agent Define jobs Monitor and control jobs Documentation CA Workload Automation DE Admin Perspective Help CA Workload Automation DE Define Perspective Help CA Workload Automation DE Monitor Perspective Help Note: The online help is available in HTML and PDF formats. CA Workload Automation ESP Edition Documentation To work with the agent and CA Workload Automation ESP Edition, see the following documentation: Task Configure the agent to work with the scheduling manager Define jobs Monitor and control jobs Documentation CA Workload Automation ESP Edition Installation and Configuration Guide CA Workload Automation Agent for UNIX, Linux, or Windows User Guide CA Workload Automation ESP Edition Command Reference Guide CA Workload Automation Agent for UNIX, Linux, or Windows User Guide CA Workload Automation ESP Edition Operator's Guide 30 Implementation Guide

31 Index A agent plug-in configuring 21 controlling 11 description 7 function 8 uninstall process 16 alias setup process 23 C configuration process, agent plug-in 21 D documentation, scheduling manager 29 I installation removing the plug-in 16 verification test 20 N name, agent plug-in 24 S scheduling manager configuration for the agent plug-in 19 configuring agent parameters 22 configuring an alias 24 documentation 29 starting and stopping, agent plug-in 11 V verification test, agent plug-in installation 20 W workload example, different jobs 7 Index 31