CA 2.4.1 Unicenter AutoSys Job Management Connect Option Installation and Administration Guide

Unicenter



AutoSys



Job

Management Connect Option

Installation and Administration Guide

2.4.1

MAN04165418E

This documentation and related computer software program (hereinafter referred to as the “Documentation”) is for the end user’s informational purposes only and is subject to change or withdrawal by Computer Associates

International, Inc. (“CA”) at any time.

This documentation may not be copied, transferred, reproduced, disclosed or duplicated, in whole or in part, without the prior written consent of CA. This documentation is proprietary information of CA and protected by the copyright laws of the United States and international treaties.

Notwithstanding the foregoing, licensed users may print a reasonable number of copies of this documentation for their own internal use, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the confidentiality provisions of the license for the software are permitted to have access to such copies.

This right to print copies is limited to the period during which the license for the product remains in full force and effect. Should the license terminate for any reason, it shall be the user’s responsibility to return to CA the reproduced copies or to certify to CA that same have been 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 the end user or any third party for any loss or damage, direct or indirect, from the use of this documentation, including without limitation, lost profits, business interruption, goodwill, or lost data, even if CA is expressly advised of such loss or damage.

The use of any product referenced in this documentation and this documentation is governed by the end user’s applicable license agreement.

The manufacturer of this documentation is Computer Associates International, Inc.

Provided with “Restricted Rights” as set forth in 48 C.F.R. Section 12.212, 48 C.F.R. Sections 52.227-19(c)(1) and (2) or

DFARS Section 252.227-7013(c)(1)(ii) or applicable successor provisions.



2003 Computer Associates International, Inc.

All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Contents

Chapter 1: Welcome to Unicenter AutoSys Connect Option

Features and Enhancements

..................................................................

1-2

Hardware and Software Requirements

.........................................................

1-4

Minimum Requirements

..................................................................

1-4

Operating System Requirements

..........................................................

1-5

CSA Space Requirements

.................................................................

1-5

LNKLST Concatenation

..................................................................

1-5

Dispatching Priority

......................................................................

1-5

Technical Support

...........................................................................

1-6

Chapter 2: Mainframe Installation

Installing Without SMP/E

....................................................................

2-1

Verifying the Installation

.....................................................................

2-4

Upgrade Unicenter AutoSys Connect 2.3 or 2.4 to Unicenter AutoSys Connect 2.4.1

................

2-5

Upgrade Approach #1

....................................................................

2-5

Upgrade Approach #2

....................................................................

2-6

Contents iii

Chapter 3: Using Unicenter AutoSys Connect Option

Startup Options

..............................................................................

3-1

ATCOPTS

...................................................................................

3-2

DEBUG

..................................................................................

3-3

FILTER

..................................................................................

3-6

Suppressing ATC0705I Message

...........................................................

3-7

Manual Job Restarts and Force Job Completions (CA-7 only)

.................................

3-8

Activating Send Retry (SRETRY)

...........................................................

3-9

XCCODE

...............................................................................

3-10

Obtaining Environment Status

................................................................

3-14

Displaying Remote Nodes

................................................................

3-16

Displaying PRIMARYCCISYSID

..........................................................

3-17

Modifying Remote Node Statuses

.........................................................

3-18

Displaying Dependencies

................................................................

3-20

Refreshing External Dependencies

........................................................

3-21

Deleting Dependencies

...................................................................

3-22

Viewing Queued Sends

..................................................................

3-23

Removing Queued Sends

.................................................................

3-23

Displaying XCCODE Entries

.............................................................

3-24

ASPING

................................................................................

3-24

Remote Machine Validation

..............................................................

3-25

Direct Job Submit

...........................................................................

3-26

iv Installation and Administrator Guide

Chapter 4: Operation

Message Processing

..........................................................................

4-1

Message Types

..............................................................................

4-2

STARTJOB

..............................................................................

4-2

ADD AGENT

............................................................................

4-5

ADD DEPENDENCY

....................................................................

4-5

PING

...................................................................................

4-6

XCCODE Processing

.........................................................................

4-7

Unicenter AutoSys Connect Startup

........................................................

4-7

XCCODE Process Flow

...................................................................

4-8

Unicenter AutoSys Connect and Unicenter AutoSys Failover

...................................

4-10

Unicenter AutoSys Connect Failover Support Process Flow

.................................

4-11

Appendix A: Operator Commands

Commands

..................................................................................

A-1

Appendix B: Troubleshooting

Message Codes

..............................................................................

B-1

Contents v

Appendix C: Initiating Jobs on a Mainframe

Configure CCI

..............................................................................

C-2

Start or Restart CCI

..........................................................................

C-2

Enable Cross-Platform Scheduling Support

....................................................

C-3

Install Client License Key for the Mainframe

...................................................

C-3

Define the Machine

..........................................................................

C-4

Submit Command Jobs to the Mainframe

......................................................

C-5

Syntax

..................................................................................

C-5

Define Command Jobs to Run on the Mainframe

...........................................

C-6

Define a Job that Depends on a Job Scheduled on the Mainframe

.............................

C-7

Working with Mainframe Scheduling Packages

................................................

C-8

CA-7

...................................................................................

C-8

CA-Scheduler

...........................................................................

C-9

CA-Jobtrac

.............................................................................

C-10

OPC

...................................................................................

C-10

ESP

...................................................................................

C-11

Control-M

.............................................................................

C-12

Zeke

..................................................................................

C-12

vi Installation and Administrator Guide

Chapter

1

Welcome to Unicenter AutoSys

Connect Option

Welcome to Unicenter AutoSys Connect Option. This product provides cross-platform-scheduling capabilities to mainframe users by enabling them to schedule jobs into a mainframe-based scheduling system.

Unicenter AutoSys on UNIX and Windows, as the manager, initiates a job that will start a job defined in a mainframe-based scheduling system through the

Unicenter AutoSys Connect Option. Through use of the Unicenter Common

Services, it tracks the mainframe-based job and reports its status back to

Unicenter AutoSys on the distributed platform.

This product was developed using the foundation provided by Unicenter

Common Services on UNIX and Windows, as well as on other distributed platforms. Unicenter AutoSys Connect Option is a stand-alone product that can be installed on any OS/390 system that needs to interface with both Unicenter

AutoSys on the distributed platform and any of the supported mainframe-based scheduling systems (Unicenter CA-7 Scheduling, Unicenter CA-7 Scheduler,

Unicenter CA-Jobtrac Scheduling). In addition, this product can integrate

Unicenter AutoSys with existing third-party mainframe scheduling systems. For an up-to-date list of non-CA scheduling systems, contact Computer Associates

Technical Support.

Welcome to Unicenter AutoSys Connect Option 1–1


Features and Enhancements

This latest version of the product offers the following features and enhancements:

■

Provide support for Unicenter AutoSys High Availability. This support enables Unicenter AutoSys Connect to dispatch event statuses to the

Unicenter AutoSys Shadow Event Processor in the event of a failover from the Primary Event Processor.

■

■

Activate OPC filtering support. Was not available in Unicenter AutoSys

Connect 2.4. Only the OPC batch interface was active. Filtering allows

Unicenter AutoSys Connect to discard jobs it receives from the OS/390

Unicenter Event Notification Facility interface if they are not currently active in OPC.

Update FILTER (OPC) control option. Added OPC subsystem name keyword to FILTER option which is now required when Unicenter AutoSys

Connect initializes with the OPC PIF (program interface facility) interface.

■

■

Provide batch interface support for the Zeke scheduling system. New batch interface jcl member ATCJZEK added.

New operator command PSYSID. Allows the PRIMARYCCISYSID of a

Unicenter AutoSys installation to be displayed.

■

■

■

■

New operator command DELDEP. Allows orphaned dependencies to be deleted from the Unicenter AutoSys Connect dependency array without having to shutdown Unicenter AutoSys Connect.

New operator command AGTMOD. Allows the status of a remote node registered with Unicenter AutoSys Connect to be modified. The state of a remote node can be modified to anyone of the valid supported statuses (“A”

ACTIVE, “I” INACTIVE, “U” UNKNOWN). The remote node can also be marked as deleted using a status of “D” DELETED.

Update operator command AGTLIST. Allows individual remote node and id to be specified. An extended report is provided for the remote node detailing number of ping requests processed, number of active external dependencies, number of processed startjob requests, number of queued sends, and the last job successfully processed from the remote node.

Update operator command DEPLIST. Allows individual remote node and id to be specified. The DEPLIST command allows an operator to display dependencies (masked or not) for just the specified remote node.

1–2 Installation and Administrator Guide


■

■

■

■

■

Add new control option “OPT” to the STATUS operator command. Allows the operator to display the current status of control options set through the

EXEC PGM= PARM statement or through the ACTOPTS parmlib member.

New ATCOPT control option NO_ATC0705I_MSG. Controls whether or not event-processing messages will be issued to the operator console.

Enhanced XCCODE debug messages. Assists support with XCCODE problem determination.

Support for JES2 Z2 mode (large job numbers JOB00001 to J0000001) for z/OS releases 1.2 and up.

Includes all Unicenter AutoSys Connect 2.4 product maintenance to date.



Hardware and Software Requirements

The hardware required to install and operate Unicenter AutoSys Connect Option will vary depending on whether you are installing all components on a single machine or across multiple servers. Consequently, it is not possible to make a definitive statement of your hardware requirements.

This section provides the following information:

■

Minimum requirements

■

Operating system requirements

■

CSA space requirements

■ concatenation

■ priority

Minimum Requirements

The minimum hardware and software requirements for the target system

(mainframe), based on practical experience to date, are:

■

Platform—OS/390

■

Hardware—No specific requirements

■

Software:

– TCP/IP (IBM or Interlink)

■

CA90s Services Genlevel 9712 or higher, or Unicenter OS/390

Framework Common Services

CAIRIM

CAICCI

CAIENF

Note: As a minimum requirement, Unicenter AutoSys 3.5.1 needs to be installed on the distributed platform.



Operating System Requirements

This product runs as a started task. It adds one active task to the system. The maximum number of tasks is specified by the MAXUSER parameter of

IEASYSxx PARMLIB member. If the system runs near the maximum number of tasks, you may need to increase this value.

If Unicenter AutoSys Connect is being used to interface with OPC and the

FILTER=OPC option is specified at startup, the Unicenter AutoSys Connect load library must be placed in the APF authorization list. Use of the FILTER=OPC option requires APF authorization.

CSA Space Requirements

Unicenter AutoSys Connect Option does not explicitly allocate CSA storage for its operations. However, a small amount of CSA space is used for system calls.

The product utilizes private storage for its tables, arrays, and program storage.

The region size on the started procedure JCL (job control language) may need to be increased if storage demands are exceeded.

LNKLST Concatenation

Unicenter AutoSys Connect Option does not require a LNKLST location to operate. Although LNKLST can be used if your installation standards require it, it is not necessary since these modules are not used by any other applications.

Additionally, using STEPLIB in the started procedure JCL will reduce the number of modules to search through in the LNKLST.

Dispatching Priority

We recommend that dispatching priority be set above batch processing and equal to noncritical online systems.


Technical Support

Technical Support

For further technical assistance with this product, please contact Computer

Associates Technical Support at http://esupport.ca.com/ for a complete list of locations and phone numbers. Computer Associates Technical Support is available 24 hours a day, seven days a week.


Chapter

2

Mainframe Installation

This chapter provides step-by-step procedures to install the product on the mainframe.

Installing Without SMP/E

To install without SMP/E do the following:

1. Assign data set names for the product libraries.

Identify a prefix for the libraries. The installation JCL is set up so that you need only decide on a data set name prefix. During installation, you will create an install library, a JCL library, and a load library (LINKLIB).

2. Unload install JCL.

Customize and submit the following JCL to restore the install library from the distribution tape.

PGM=IEBCOPY

//SYSPRINT DD SYSOUT=*

//SYSIN DD DUMMY

//SYSUT2 DD DSN=UATC24.install,

// SPACE=(TRK,(15,15,30)),

// UNIT=SYSDA,VOL=SER=dasd-volume,DISP=(NEW,CATLG,DELETE)

//SYSUT1 DD DSN=UATC24.INSTALL,

// UNIT=tape-unit,VOL=(,RETAIN,SER=tape-volume),

// LABEL=(1,SL,EXPDT=02000),DISP=OLD

3. Unload the remaining libraries.

Customize and submit install library member X01RST to restore the other libraries.

4. Catalog the procedure.

Customize and submit install library member X02PROCC to add the

CAUATCON procedure to your installation procedure library.

Mainframe Installation 2–1


5. Create and customize batch scheduler JCL.

The product uses a batch interface for scheduling jobs through all mainframe schedulers. For each supported scheduler there is a member in

{install}.PARMLIB. The syntax of the member names for the scheduler JCL is:

ATCJ xxx where xxx specifies the three-byte scheduler identifier.

Each ATCJ xxx member contains sample JCL that must be customized. For more information on the appropriate scheduler for batch interface JCL see the

Unicenter AutoSys Job Management for UNIX User Guide. For a list of valid scheduler identifiers see the appendix “Initiating Jobs on a

Mainframe,” in this guide.

6. Update the CAIENF database.

SAMPJCL member XO3ENFJ defines events to CAIENF and makes them active. CAIENF must be shut down to run the job. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero.


SYSID

PROTOCOL


7. Update the CAICCI startup options.

Prior to starting the option, which utilizes the Common Communications

Interface (CCI), you must add the SYSID and PROTOCOL command statements to the CCIPARM member (created during the OS/390

Framework installation). The addition of the SYSID and PROTOCOL command is necessary to allow CCI (running on the mainframe) to communicate with its counterpart on the distributed platform. For example:

SYSID

(MVSNODE)

PROTOCOL

(TCPIPGW,7000,01,MVSNODE) where:

Is a one to eight character identifier that is unique throughout the CAICCI network.

Is used to specify the communications protocol supported by this local host node and its associated network parameters to access remote CAICCI nodes.

For more details on the individual operands of the PROTOCOL statement, see the OS/390 Framework Documentation.

You must ensure that you have executed installation member W010LINK contained within your OS/390 Framework installation sample JCL library.

This link JCL member creates the CCI Gateway load module required for cross-platform communication.

8. Start the OS/390 Unicenter ENF started task using the OS/390 command

START ENF

.

9. Start the Unicenter AutoSys Connect started task using the OS/390 command

START CAUATCON

.

Ensure that you are executing ATCMAIN. The product runs as a started task in the OS/390 system; therefore, it must be started after each IPL. The started task procedure is placed into a PROCLIB during system installation. The product initializes for processing and stays active until the started task is terminated.

10. Unload the online documentation. This step is optional and can be skipped.

Customize and submit install library member X04UAPDF to unload the online documentation.


Verifying the Installation

Note: The Unicenter AutoSys Connect Option PDF documentation has been optimized for use with Adobe Acrobat Reader 5.0, including the ability to open PDF files in Netscape Communicator 4.x or Internet Explorer 5.x on windows. If you do not have Adobe Acrobat Reader installed, or have an earlier version of Adobe Acrobat Reader and experience any problems opening Unicenter AutoSys Connect Option Documentation go to www.adobe.com to download the recent version.

Verifying the Installation

Perform the following steps to verify the previous installation:

1. Verify the Communications Interface.

The first task is to initialize the Common Communications Interface

(CAICCI). Message ATC0204I appears in the job log when the product initializes the CAICCI interface. Message ATC0204I appears in the job log to indicate the CAICCI identifier to which the product has connected.

2. Verify the Event Notification Facility Processing Interface.

The second task is to initialize itself with the ENF (CAIENF). Message

ATC0603I appears in the job log when the product has initialized itself with the CAIENF interface.

Messages ATC0863I and ATC0865I appear in the job log when the initialization tasks have been completed and processing is ready to begin.



Upgrade Unicenter AutoSys Connect 2.3 or 2.4 to Unicenter

AutoSys Connect 2.4.1

This section has been prepared to assist those existing Unicenter AutoSys

Connect 2.3 or 2.4 users in upgrading their current installation to Unicenter

AutoSys Connect 2.4.1. This section can be used to obtain the sample jcl needed to unload the Unicenter AutoSys Connect installation tape dataset, and so forth.

Being as the Unicenter AutoSys Connect 2.4.1 install is fairly short in length two approaches can be used to upgrade.

1. Upgrade in place.

2. Perform a fresh (new) installation. That is, create Unicenter AutoSys Connect

2.4.1 unique libraries and merge in any Unicenter AutoSys Connect parmlib updates from 2.3 or 2.4.

No changes or updates are required to the Unicenter Common Services

(ENF – Event Notification Facility) and CCI – Common Communications

Interface. Those steps, which refer to execution of sample installation members, or modifications, which are specifically required for the Unicenter Common

Services, can be ignored.

Use the instructions following, depending on which approach you choose, to upgrade to Unicenter AutoSys Connect 2.4.1.

Upgrade Approach #1

1. Shut down your existing Unicenter AutoSys Connect 2.3 or 2.4 installation.

2. Back up your existing Unicenter AutoSys Connect 2.3 or 2.4 installation

(install, loadlib and parmlib datasets). It is important to perform a back up procedure, as the Unicenter AutoSys Connect 2.3 or 2.4 parmlib will be required in later steps.

3. Unload the Unicenter AutoSys Connect 2.4.1 install dataset

UATC24.INSTALL from the installation tape.

4. Tailor installation member X01RST so the Unicenter AutoSys Connect 2.4.1 tape datasets will overlay your Unicenter AutoSys Connect 2.3 or 2.4 installation datasets. Submit this installation member for execution.



5. Locate installation member X02PROC. This member will create the new

Unicenter AutoSys Connect started task procedure CAUATCON. It is important this step be executed as the Unicenter AutoSys Connect started task procedure differs slightly from Unicenter AutoSys Connect 2.3 and must be used to the start the Unicenter AutoSys Connect 2.4.1 product.

Tailor accordingly and submit this installation member for execution. If you are upgrading from Unicenter AutoSys Connect 2.4 there were no changes to the started task procedure. Your Unicenter AutoSys Connect 2.4 started task procedure can be used in place of the 2.4.1 procedure.

6. Using the Unicenter AutoSys Connect 2.3 or 2.4 parmlib backup, merge all

Unicenter AutoSys Connect 2.3 parmlib changes to their Unicenter AutoSys

Connect 2.4 equivalent, for example, batch interface jcl, XCCODE, and so forth.

7. With Unicenter AutoSys Connect 2.4.1, input control options no longer need to be specified on the EXEC PGM= statement. These control options can be moved to the ATCOPTS member in the Unicenter AutoSys Connect parmlib dataset and will be read at Unicenter AutoSys Connect 2.4.1 startup.

8. You are now ready to use the Unicenter AutoSys Connect 2.4.1 product.

Upgrade Approach #2

1. Shut down your existing Unicenter AutoSys Connect 2.3 or 2.4 installation.

2. Install Unicenter AutoSys Connect 2.4.1 as a new installation.

3. Using the Unicenter AutoSys Connect 2.3 or 2.4 parmlib, merge all Unicenter

AutoSys Connect 2.3 or 2.4 parmlib changes to their Unicenter AutoSys

Connect 2.4.1 equivalent, for example, batch interface jcl, XCCODE, and so forth.

4. You are now ready to use the Unicenter AutoSys Connect 2.4.1 product.

Note: You cannot have both installations of Unicenter AutoSys Connect running at the same time. However, you can start up and shut down one installation and then start the other without having to take any additional steps to do so. This note applies to users who chose upgrade approach #2 only.


Chapter

3

Using Unicenter AutoSys Connect

Option

This chapter discusses the use of various options and settings associated with this product.

Startup Options

This section discusses how to enable various job-specific functions by setting startup options. Enable these options after completion of the installation. The following options are discussed:

■

■

ATCOPTS

DEBUG

■

■

■

■

DMSG

FILTER

NO_ATC7051_MSG

PURGE_FAILED_JOBDEP

■

SRETRY

■

XCCODE

Using Unicenter AutoSys Connect Option 3–1

ATCOPTS

ATCOPTS

This section discusses how to enable various job-specific functions by setting startup options in the ATCOPTS member located the Unicenter AutoSys Connect

Option parmlib dataset. The ATCOPTS member allows startup options to be specified through a dataset as opposed to modification of the started task JCL

(EXEC PGM=ATCMAIN, PARM=).

You must enable these options after completion of the installation, through

ATCOPTS:

■

DEBUG

■

DMSG

■

FILTER

■

■

NO_ATC7051_MSG

■

PURGE_FAILED_JOBDEP

SRETRY

■

XCCODE

The following is a sample ATCOPTS member:

* UNICENTER AUTOSYS CONNECT

* STARTUP OPTIONS

FILTER=(OPC, <OPC subsystem name>)

DEBUG=(0)

DMSG(LOG)

NO_ATC7051_MSG(Y)

SRETRY(Y)

XCCODE

Comment records can be coded in ATCOPTS by placing an asterisk in card column 1. If an asterisk is not present, the input record will be processed as an input control option.


ATCOPTS

DEBUG

The following sections discuss specifying the DEBUG level and controlling

DEBUG output.

Specifying DEBUG Level

Note: This option should be used only under the direction of Computer

Associates Technical Support personnel. For more information see the topic

Technical Support in the chapter “Welcome to Unicenter AutoSys Connect

Option,” in this guide.

The DEBUG level can be set from the system operator console, EXEC PGM= statement or the ACTOPTS parmlib member. If you modify the DEBUG level from the system operator console, EXEC PGM= statement or the ACTOPTS parmlib member, you can use either of the following:

DEBUG( n

) or:

DEBUG=

The example following shows how to specify the option through the EXEC

PGM= statement.

//CONNECT EXEC PGM=ATCMAIN,PARM='DEBUG= n

' where n is a number from 0 to 9. The default DEBUG level is 0.

For a description of the DEBUG levels, see the following table. For a complete list of message codes, see the appendix “Troubleshooting,” in this guide.

DEBUG Level Messages

0 (Default) All Informational, Error, and Warning messages.

1

2

3

Unused.

Processing console command messages. Includes messages from all prior levels.

Agent-related messages. Includes messages from all prior levels.


ATCOPTS

8

9

DEBUG Level Messages

4 Dependency request and application-related messages.

Includes messages from all prior levels.

5

6

7

CCI notification and job initiation-related messages. Includes messages from all prior levels.

Event occurrence messages. Includes messages from all prior levels.

Job processing-related messages. Includes messages from all prior levels.



The DEBUG level can also be changed from the operator console with the following command:

/F{connect_started_task},DEBUG= n or:

/F{connect_started_task},DEBUG( n

) where n is a number from 0 to 9.


ATCOPTS

Controlling DEBUG Output

If you have enabled the DEBUG option, you can control where DEBUG messages are directed. To control where messages are directed, specify the DMSG control option. The DEBUG option can be specified in the ATCOPTS input options parmlib member or can be issued as an operator command.

The DMSG control option has the following sub options:

WTO—Directs all DEBUG output to the system operator console.

SYSLOG—Directs all DEBUG output to the system log.

LOG—Directs all DEBUG output to the ATCOUT DD statement specified in the Unicenter AutoSys Connect 2.4.1 started task job control.

If you have enabled the Unicenter AutoSys Connect DEBUG option and have not specified the DMSG control option, messages by default are directed to the system operator console.

If the DMSG(LOG) option is specified, the ATCOUT dataset is closed when any of the following occur:

■

Unicenter AutoSys Connect Option is shut down.

■

DEBUG messages are redirected from the ATCOUT dataset to the system console or the system log.

■

The DEBUG control option is reset to “0.”


ATCOPTS

FILTER

If you are using OPC or ESP as your mainframe scheduler and want Unicenter

AutoSys Connect Option to monitor these jobs exclusively, you must enable this function through the FILTER option.

Enabling this option ensures that jobs submitted outside of the scheduling application are ignored and not erroneously reported back to Unicenter AutoSys.

Activating OPC Filter

To activate OPC filtering specify the FILTER OPC control option. Filtering allows Unicenter AutoSys Connect to discard jobs it receives from the OS/390

Unicenter ENF interface if they are not currently active in OPC. This control option can be specified in the ACTOPTS input control option file or the EXEC

PGM= PARM statement. We recommend the option be added to the ACTOPTS control option file.

Specify the control option as follows in ACTOPTS:

FILTER(OPC,<opc_subsystem_name>)

Specify the control option on the EXEC PGM= PARM statement as follows:

//CONNECT EXEC PGM=ATCMAIN, //PARM=’FILTER=(OPC,<opc_subsystem_name>)

Note: The activation of the OPC filtering interface does not require the Unicenter

AutoSys Connect load library run APF authorized as previously stated in the

Unicenter AutoSys Connect 2.4 documentation. This is no longer a requirement and can be ignored.


ATCOPTS

Activiating ESP Filter

To activate ESP filtering specify the FILTER ESP control option. Filtering allows

Unicenter AutoSys Connect to discard jobs it receives from the OS/390

Unicenter ENF interface if they are not currently active in ESP. This control option can be specified in the ACTOPTS input control option file or the EXEC

PGM= PARM statement. We recommend the option be added to the ACTOPTS control option file.


FILTER(ESP)

Specify the control option on the EXEC PGM= PARM statement as follows:

//CONNECT EXEC PGM=ATCMAIN,PARM=’FILTER=ESP’

Suppressing ATC0705I Message

To suppress event processing messages, which by default are written to the operator console as part of normal job processing messages, specify the

NO_ATC0705I_MSG control option in member ATCOPTS.


NO_ATC0705I_MSG(Y|N)

Note: If this message is suppressed through the control option and the

DEBUGLEVEL specified is greater than “5”, the ATC0705I messages will be written to either the operator console, syslog or ATCOUT log dataset depending on the value of the DMSG control option.


ATCOPTS

Manual Job Restarts and Force Job Completions (CA-7 only)

Unicenter AutoSys Connect provides support for manual job restarts and force job completions from within the Unicenter CA-7 mainframe scheduling system.

The job being restarted or forced complete must have been originally started through use of Unicenter AutoSys Connect. This support is provided through control option PURGE_FAILED_JOBDEP. When activating this control option to retain failed job dependencies, Unicenter AutoSys Connect can detect and match up ENF events that occurred as a result of manually restarting a job. The corresponding event statuses will be dispatched to the remote Unicenter

AutoSys node.

Unicenter AutoSys Connect can also detect when jobs are manually forced complete through interrogation of the Unicenter CA-7 job completion event passed to it by ENF. The corresponding Unicenter CA-7 job completion event is converted to a JOBTERM event and dispatched to the remote Unicenter AutoSys node.

Note: To support force job completions, the Unicenter CA-7 data control module, CAL2DCM0, must be installed and activated within the ENF database.

This enables Unicenter AutoSys Connect to listen for the Unicenter CA-7 job completion event.


PURGE_FAILED_JOBDEP(Y|N,< scheduler_name

>)

When setting this control option to a value of ‘Y ‘, the scheduler_name is not required.

The default for this control option is Y. After a job is processed resulting in a

JOBFAIL event being dispatched to the remote node, the job dependency is deleted from memory. No further processing will occur with this job dependency.

At the present time this support has only been provided for the Unicenter CA-7 mainframe scheduling system. If a scheduler name other than Unicenter CA-7 is specified it will result in an error message during control option processing.


ATCOPTS

Activating Send Retry (SRETRY)

Note: The SRETRY option can be specified only through the ATCOPTS parmlib member during Unicenter AutoSys Connect Option startup.

Through use of the SRETRY control option, Unicenter AutoSys Connect Option will queue failed sends to a remote machine. When a failed send occurs, the product writes several messages to the system operator console detailing the specific job being processed, and the communications error encountered.

When the remote machine reestablishes communication with Unicenter AutoSys

Connect Option, Unicenter AutoSys Connect Option will resend all queued send buffers.

The operator command syntax is as follows:

SRETRY( option

) where option is defined by either:

Y—Activate send retry functionality.

N—Disable send retry functionality.

Note: The default value of SRETRY is ‘N’.

Unicenter AutoSys Connect queues failed send buffers in memory waiting for the remote machine to reestablish communication. For each queued buffer,

Unicenter AutoSys Connect Option requires 1KB of subpool 0 private storage.

The region size on the started procedure JCL may need to be increased if storage demands are exceeded. We recommend the region size of the Unicenter AutoSys

Connect Option started task be increased from 1MB (default) to 4MB if the

SRETRY control is to be activated.


ATCOPTS

XCCODE

Unicenter AutoSys Connect Option monitors jobs running on the mainframe by scheduling work into a batch scheduler’s interface and routing the job return code back to the Unicenter AutoSys machine. Based on the return code Unicenter

AutoSys receives, AutoSys then determines whether the job is marked SUCCESS or FAILURE.

To enable the option to intervene or override the job return code, you must set up the XCCODE member. This allows the user to manage the job’s success or failure from the mainframe.

For more information on the XCCODE process flow, see the section XCCODE

Process Flow in the chapter “Operation,” in this guide.

Setting Up the XCCODE Member

To enable the product to report a specified job as failed, you must specify the

JOB or JOBSTEP parameters in the XCCODE option.


JOB

jobname

operator

value

ATCOPTS

The syntax of the JOB parameter is:

JOB jobname RC operator value where:

Specifies the name of the job. To create a comment line, enter an asterisk (*).

Any line with an asterisk in this space is ignored in processing.

Specifies the comparison operator for the return code:

EQ – Equal

NE – Not equal

LT – Less than

LE – Less than or equal

GT – Greater than

GE – Greater than or equal

Specifies the value (0 to 4095) to compare to the return code.

Conditions specified in the JOB parameter are compared with the final return code of a specified job. If the conditions are met, the job is reported to have failed. For example:

JOB JOBA RC GT 8

If rc > 8 FAILURE (means condition is met)

If rc <= 8 SUCCESS


ATCOPTS

JOBSTEP

jobname

stepname

operator

value

The syntax of the JOBSTEP parameter is:

JOB jobname STEP stepname RC operator value where:

Specifies the name of the job. To create a comment line, enter an asterisk (*).

Any line with an asterisk in this space is ignored in processing.

Specifies the name of the step

.

Specifies the comparison operator for the return code:

EQ – Equal

NE – Not equal

LT – Less than

LE – Less than or equal

GT – Greater than

GE – Greater than or equal

Specifies the value (0 to 4095) to compare to the return code.

A job/step combination may match more than one line. The most specific line is considered a match, and the other lines are ignored. The sequence of the lines has no effect on the results, so they can be entered in any order. For example, all of the following lines match job PPR235 step CKEOJ. The second line is the most specific because it matches only one job/step combination. The second line is considered a match.

JOB PPR235 STEP * RC GT 0

JOB PPR235 STEP CKEOJ RC GT 12

JOB * STEP OKEOJ RC GT 0

JOB * STEP * RC GT 0

After locating the matching line, the option tests for the condition RC operator value. If the condition is true, the job is treated as JOBFAIL.

If no matching line is found, the condition code is compared to the value of the

JOB parameter. If the condition code is greater than the JOB parameter value, the job is treated as JOBFAIL. If the member contains a line with JOB * STEP *, that line matches any job/step combination not matched by any other line, and the

JOB option is never used.


ATCOPTS

Examples

Example 1:

Example 2:

Example 3:

PPR235 is JOBFAIL if step EOMTBLD completes with Return Code (RC) higher than 4.

JOB PPR235 STEP EOMTBLD RC GT 4

ZO5EMPQ is JOBFAIL if any step completes with RC higher than 4.

JOB ZO5EMPQ STEP * RC GT 4

PRKA0140 is JOBFAIL if step S022 completes with RC higher than 0 or if step

S040 completes with RC 24 or if any other step completes with RC higher than 4.

JOB PRKA0140 STEP S022 RC GT 0

JOB PRKA0140 STEP S040 RC EQ 24

JOB PRKA0140 STEP * RC GT 4

Activating the XCCODE Member

To enable the XCCODE parmlib member for use, you must specify either the

XCCODE control option in the ATCOPTS parmlib member or specify the

XCCODE keyword in the PARM field on the PGM= statement of the started task

JCL.

For use with the ATCOPTS:

*

*

* STARTUP OPTIONS

*

FILTER(OPC,<opc subsystem name>)

DEBUG(0)

DMSG(LOG)

NO_ATC7051_MSG(Y)

SRETRY(Y)

XCCODE

For use with the EXEC PGM= statement:

//CONNECT EXEC PGM=ATCMAIN,PARM='XCCODE'



Obtaining Environment Status

Status of the Unicenter AutoSys Connect Option environment can be obtained through the STATUS operator command. The STATUS operator command will output the following information:

VERSION (VER)—Displays current version information.

DEBUG (DBG)—Displays current DEBUG value and where DEBUG messages are directed.

DEPENDENCY (DEP)—Displays total number of dependencies including a breakdown by the type of dependency.

CCI (CCI)—Displays the status of the Unicenter AutoSys Connect CCI interface along with RECEIVE, SEND, QUEUED SEND and ERROR communication counts.

ENF (ENF)—Displays the status of the Unicenter AutoSys Connect ENF interface along with processed event counts.

REQUESTS (REQ)—Displays remote request totals for add dependencies, delete dependencies, start job, refresh and ping requests.

OPERATOR COMMANDS (OPR)—Displays a total number of operator commands issued.

OPTIONS (OPT)—Displays the current status of options specified through the EXEC PGM= PARM statement or through the ACTOPTS parmlib member.

XCCODE (XCD)—Displays the status of XCCODE and the total number of

XCCODE entries.



Individual statuses can be obtained by using the control verb in parentheses previously shown. For example, to obtain status of the Unicenter AutoSys

Connect CCI interface, issue the following operator command:

F CAUATCON,STATUS(CCI)

Output of the STATUS(CCI) command is:


ATC0257I - PROCESSING COMMAND STATUS(CCI)

ATC0514I - OS/390 UNICENTER CCI SERVICES ARE ACTIVE

ATC0203I - LOCAL CCI SYSID=A50SENF

ATC0206I - LOCAL APPLICATION NAME=AUTOSYS-CONNECT

ATC1116I - REMOTE APPLICATIONS USING AUTOSYS CONNECT

ATC1113I - ID NODE STATUS APPLICATION NAME

ATC1114I - 1 usilsudt A ATSBTRK Job track

ATC1114I - 2 adora A ATSSY2 Job track

ATC1114I - 1 usiljdt2 A ATSBTRK Job track

ATC1114I - 1 adora A ATSBTRK Job track

ATC0870I - SEND RETRY LOGIC IS ACTIVE

ATC0517I - CCI STATUS

ATC0518I - RECEIVES (654) ERRORS (0)

ATC0519I - SENDS (333) ERRORS (0)

ATC0530I - QUEUED SENDS (0)

ATC0255I - COMMAND COMPLETE



Displaying Remote Nodes

Remote nodes registered with Unicenter AutoSys Connect can be displayed through the AGTLIST operator command. The id, node name, status and the nodes application name is displayed.

node

id


F CAUATCON,AGTLIST

Output messages are directed to the operator console providing a status of the command.

F CAUATCON,AGTLIST

ATC0254I - RECEIVED OPERATOR COMMAND

ATC0257I - PROCESSING COMMAND AGTLIST





ATC1114I - 1 usiljdt1 A ACEBTRK Job track




An individual report per agent can be obtained by specifying the remote node and id of the remote node. This individual report will contain information on the number of ping requests processed on behalf of this remote node, number of external dependencies currently active for this remote node, the number of processed startjob requests, the number of queued sends currently active for this remote node and finally the last job processed successfully for this remote node.


F CAUATCON,AGTLIST (< node >,< id >) where:

Is the remote node currently registered with Unicenter AutoSys Connect.

Is the unique identifier assigned by Unicenter AutoSys Connect when the remote node is registered.

The id of a remote node can be determined through execution of the AGTLIST or the STATUS(CCI) operator command. If the id is not specified it defaults to a value of “1.” If you wish to input the application name of the agent node, specify “0” as the id and Unicenter AutoSys Connect will prompt at the operator console for the 20- id character node application name of the agent node.




F CAUATCON,AGTLIST(usiljdt2,1)


ATC0257I - PROCESSING COMMAND AGTLIST(USILJDT2,1)



ATC0275I - PRIMARYCCISYSID=usiljdt1 FOR NODE=usiljdt2 APPL=ACEBTRK Job track

ID=1

ATC0531I - PING REQUESTS (8)

ATC0532I - EXTERNAL DEPENDENCIES (0)

ATC0533I - STARTJOB REQUESTS (71)


ATC0535I - LAST JOB PROCESSED: A79JOB JOB06164 0000 2002113104747


Displaying PRIMARYCCISYSID

Through use of the PSYSID operator command the PRIMARYCCISYSID

(Primary Event Processor node) of a Unicenter AutoSys distributed based installation can be displayed. This node name is specifically used during queued send lookup after a new agent has made contact with Unicenter AutoSys

Connect. In the simplest terms, it allows Unicenter AutoSys Connect to dispatch queued send buffers originally targeted for a Primary Event Processor installation to be dispatched to a Shadow Event Processor installation.

node

id


F CAUATCON,PSYSID(< node

>,< id

>)


Is the unique identifier assigned by Unicenter AutoSys Connect when the remote node registered.

The id of a remote node can be determined through execution of the AGTLIST or the STATUS(CCI) operator command. If the id is not specified it defaults to a value of “1”. If you wish to input the application name of the agent node, specify “0” as the id and Unicenter AutoSys Connect will prompt at the operator console for the 20- id character node application name of the agent node.




F CAUATCON,PSYSID(USILJDT2,1)


ATC0257I - PROCESSING COMMAND PSYSID(USILJDT2,1)


ID=1


In the example previously shown, which refers to nodes on the distributed platform, node “usiljdt1” represents the Unicenter AutoSys Primary Event

Processor and node “usiljdt2” represents the Unicenter AutoSys Shadow Event

Processor. In the event of a Unicenter AutoSys failover, any statuses destined to be sent to the primary node “usiljdt1,” would now be sent to the shadow node

“usiljdt2.”

Modifying Remote Node Statuses

Should the need arise to manually alter the current status of a registered remote node with Unicenter AutoSys Connect, the AGTMOD operator command can be used. A valid list of remote nodes and their respective statuses can be obtained through the use of the AGTLIST operator command.

status


F CAUATCON,AGTMOD(< status

>,< node

>,< id

>) where:

Is a valid remote status. Valid status values are:

node

id

“A” ACTIVE

“I” INACTIVE

“U” UNKNOWN

“D” DELETED





The id of a remote node can be determined through execution of the AGTLIST or the STATUS(CCI) operator command. If the id is not specified it defaults to a value of “1”. If you wish to input the application name of the agent node, specify “0” as the id and Unicenter AutoSys Connect will prompt at the operator console for the 20- id character node application name of the agent node.








ID=1







F CAUATCON,AGTMOD(i,usiljdt1,1)


ATC0257I - PROCESSING COMMAND AGTMOD(i,USILJDT1,1)


ATC1114I - 1 usiljdt1 I ACEBTRK Job track


In the case where the DELETE status is specified, Unicenter AutoSys Connect will modify the remote node and application name (changes first character of node and application to a pound sign “#”) in memory. The physical storage entry for the node is not deleted and remains in the current remote node array as a reference for future use. Should this remote node contact Unicenter AutoSys

Connect again in the future a new remote node array entry will be created.







ID=1







F CAUATCON,AGTMOD(d,usiljdt1,1)


ATC0257I - PROCESSING COMMAND AGTMOD(d,USILJDT1,1)


ATC1114I - 1 #siljdt1 D #CEBTRK Job track




Displaying Dependencies

Startjob and external dependencies can be displayed by using the DEPLIST operator command. The dependency name, job number, node, application name, event name, and type are displayed.

mask

node id

Dependency names can be masked allowing the list to be qualified to a specific set of dependencies for a given node or multiple nodes.


F CAUATCON,DEPLIST(< mask

>,< node

>,< id

>) where:

Is the fully qualified dependency or masked dependency name to be listed.



The id of a remote node can be determined through execution of the AGTLIST or the STATUS(CCI) operator command. If the id is not specified it defaults to a value of “1”. If the agent node for the dependency being deleted does not exist in the Unicenter AutoSys Connect agent array, specify “0” as the id and

Unicenter AutoSys Connect will prompt at the operator console for the 20character node application name of the dependency.

Note: The mask, node and id parameters are optional parameters. These parameters allow the DEPLIST operator command to allow for the list to be further qualified.




F CAUATCON,DEPLIST


ATC0257I - PROCESSING COMMAND DEPLIST

ATC1110I - JOBNAME JOBNUM NODE APPLICATION TYPE EVENT

ATC1111I - A14JOB -------- usiljdt1 SQLBTRK Job Track AD --------

ATC1111I - A15JOB JOB08757 usiljdt1 SQLBTRK Job Track SJ JOBINIT

ATC1111I - A16JOB JOB08758 usiljdt2 ORABTRK Job Track SJ JOBTERM


F CAUATCON,DEPLIST(*,usiljdt2,1)


ATC0257I - PROCESSING COMMAND DEPLIST

ATC1110I - JOBNAME JOBNUM NODE APPLICATION TYPE EVENT

ATC1111I - A16JOB JOB08758 usiljdt2 ORABTRK Job Track SJ JOBTERM


Refreshing External Dependencies

External dependencies from a remote machine can be refreshed through use of the REFRESH XDEP command.

node

id


REFRESH(XDEP, node

, id

) where:

Is the remote machine currently registered with the product.

Is the identifier assigned by the product when the remote machine registered.

The ID of a remote machine can be determined through execution of the

AGTLIST or the STATUS(CCI) operator command. If the ID is not specified, it defaults to a value of “1.”


F CAUATCON,REFRESH(XDEP,USILSUDT,1)


ATC0257I - PROCESSING COMMAND REFRESH(XDEP,USILSUDT,1)

ATC0270I - REFRESH XDEP REQUEST SUCCESSFULLY SENT TO NODE=USILSUDT




Deleting Dependencies

Through use of the DELDEP operator command orphan dependencies can be removed from the Unicenter AutoSys Connect dependency array. This alleviates the need to recycle Unicenter AutoSys Connect to remove the orphan dependencies.

name


F CAUATCON,DELDEP(< name

>,< type

>,< node

>,< id

>) where:

Is the name of the dependency to be deleted.

Valid dependency names can be derived from the DEPLIST operator command.

The dependency name can be masked.

type

Is the dependency type of the dependency to be deleted.

Valid types are “AD,” “SJ,” “**” or “*.” The “**” type indicates a batch interface

(ATCJxxx) dependency. The “*” indicates the delete will occur for all dependency types for a given node.

node id



The id of a remote node can be determined through execution of the AGTLIST or the STATUS(CCI) operator command. If the id is not specified it defaults to a value of “1”. If the agent node for the dependency being deleted does not exist in the Unicenter AutoSys Connect agent array, specify “0” as the id and

Unicenter AutoSys Connect will prompt at the operator console for the 20character node application name of the dependency.


F CAUATCON,DELDEP(A*,AD,USILJDT1,1)


ATC0257I - PROCESSING COMMAND DELDEP(A*,AD,USILJDT1,1)

ATC0243I - **DELETED** DEPNAME=A14JOB TYPE=AD NODE=USILJDT1

APPL=SQLBTRK Job track

ATC0248I - TOTAL DEPENDENCIES DELETED (1)




Viewing Queued Sends

When the SRETRY control option is activated and sends have been successfully queued in memory, they can be viewed by issuing the QSDLIST operator command.


F CAUATCON,QSDLIST

The following is a sample output of the command:

F CAUATCON,QSDLIST

ATC0257I – PROCESSING COMMAND QSDLIST

ATC1122I – EVENT JOBNAME JOBNUM NODE APPLICATION

ATC1123I – JOBINIT DOUGT007 JOB06548 usilsudt ATSBTRK Job Track

ATC1123I - JOBTERM DOUGT007 JOB06548 usilsudt ATSBTRK Job Track

ATC1124I - TOTAL QUEUED SEND ENTRIES (2)


Removing Queued Sends

If for any reason you wish to remove queue sends for a specific remote machine, this can be accomplished through the QSDFREE operator command. The remote machine for which queued sends are to be removed must have successfully registered with Unicenter AutoSys Connect at some point earlier.

node

id

The format of the QSDFREE command follows:

QSDFREE( node

, id

) where:


Is the identifier assigned when the remote machine is registered.




F CAUATCON,QSDFREE (USILSUDT,1)

ATC0257I - PROCESSING COMMAND QSDFREE

ATC1138I - QUEUED SEND BUFFERS RELEASED FOR NODE=USILSUDT ID=1




Displaying XCCODE Entries

XCCODE entries defined through use of the XCCODE parmlib member can be displayed using the XCDLIST operator command. The ID, machine name, status, and the machines application name are displayed.


F CAUATCON,XCDLIST


F CAUATCON,XCDLIST


ATC0257I - PROCESSING COMMAND XCDLIST

ATC1106I - JOBNAME STEPNAME COMP RC

ATC1107I - * STEP01 EQ 0004

ATC1107I - A37JOB STEP37 GT 0008

ATC1107I - A38JOB STEP55 GT 4096

ATC1107I - A40JOB * GT 0004

ATC1107I - A47JOB STEP37 LT 1000


ASPING

node

id

The status of a remote machine can be determined by using the ASPING operator command.

Note: The remote machine to be contacted must be registered with Unicenter

AutoSys Connect Option 2.4.1.

The syntax of the ASPING command is:

ASPING( node

, id

) where:


Is the identifier assigned when the remote machine is registered.





Output messages are directed to the operator console providing a status of the command. If the remote machine cannot be contacted the appropriate communication error messages are issued. Unicenter AutoSys Connect will mark this remote machine as inactive should the ASPING command fail. Please note, the ASPING command is not a true IP ping command. The ASPING command utilizes the OS/390 Unicenter Framework CCI component to communicate with

Unicenter AutoSys on the remote machine.

F CAUATCON,ASPING(USILSUDT,1)

ATC0257I - PROCESSING COMMAND ASPING(USILSUDT,1)

ATC0259I - ASPING SUCCESSFUL NODE=usilsudt


Remote Machine Validation

The status of a remote machine can be determined by any of the following commands:

■

AGTLIST

■

STATUS (CCI)

■

( node_name,id)

Output of the AGTLIST command:

F CAUATCON,AGTLIST


ATC0257I - PROCESSING COMMAND AGTLIST








Output of the STATUS (CCI) command:


ATC0257I - PROCESSING COMMAND STATUS(CCI)

ATC0514I - OS/390 UNICENTER CCI SERVICES ARE ACTIVE

ATC0203I - LOCAL CCI SYSID=A50SENF

ATC0206I - LOCAL APPLICATION NAME=AUTOSYS-CONNECT







ATC0870I - SEND RETRY LOGIC IS ACTIVE

ATC0517I - CCI STATUS

ATC0518I - RECEIVES (654) ERRORS (0)

ATC0519I - SENDS (333) ERRORS (2)




Direct Job Submit

Direct Job Submit

Unicenter AutoSys Connect can submit and start mainframe based job control outside of using the mainframe scheduler’s batch interface. To invoke direct job submit follow the steps outlined below:

1. Add the ATCJOBS as a DD statement to the Unicenter AutoSys Connect started task job control. The dataset specified by ATCJOBS must be must be a partitioned dataset with an LRECL=80, BLKSIZE=<multiple of

LRECL>,DSORG=PO. The members within this dataset must contain valid job control. Datasets can be concatenated to ATCJOBS.

ATCJOBS DD DISP=SHR,DSN=JOBS.CNTL

2. Within the Unicenter AutoSys job definition only specify the –j and –d options. auto_cnct –a node –j jobname –d

Note: The –s option must not be specified. Direct submit processing is only invoked when the –s is not present or is blank.

3. Start the job within Unicenter AutoSys.


Chapter

4

Operation

This chapter provides an overview of the Unicenter AutoSys Connect Option during its normal operation.

Message Processing

Unicenter AutoSys Connect Option functionality is driven through message requests from remote Unicenter AutoSys nodes. Unicenter AutoSys Connect will receive various message types, which allow it to accomplish the following:

■

Receive a job request from the distributed platform.

■

Submit the job request to a mainframe based scheduling system for execution.

■

Track execution of the mainframe based submitted job.

■

Transmit event status back to the Unicenter AutoSys remote node.

■

Monitor and transmit status on cross instance (external) dependencies.

Operation 4–1

Message Types

Message Types

Unicenter AutoSys Connect Option will process four basic message types:

■

(SJ)

■

ADD AGENT (4A)

■

ADD DEPENDENCY (AD)

■

(0A)

The hexadecimal codes following the message types are the internal one-byte codes used when the Unicenter AutoSys UNICENTER AUTOSYS BROKER transmits a request to Unicenter AutoSys Connect. These codes are listed for reference as they are commonly used throughout debug messages produced by enabling the DEBUG control option.

STARTJOB

The STARTJOB message request is transmitted to Unicenter AutoSys Connect

Option following successful completion of a started job. The startjob request on the distributed platform occurs against a job defined to execute on a Unicenter

AutoSys Connect Option-based system.

The following is a sample Unicenter AutoSys job definition: insert_job: JOBB owner: master machine: MAINF type: c condition: success(JOBA) command: auto_cnct –a MAINF –c RUN –j JOBC –s CA7 –d

The job definition adds a job named JOBB to Unicenter AutoSys when inserted into the database. The job has a dependency on JOBA also defined in Unicenter

AutoSys, which must complete before JOBB can start. For this exercise assume

JOBA has completed successfully. Unicenter AutoSys will now start JOBB. The

Unicenter AutoSys Event Processor on the distributed platform interrogates the start job request, determines the job is not a request to be executed on a

Unicenter AutoSys Remote Agent, and forwards it the Unicenter AutoSys

UNICENTER AUTOSYS BROKER. The UNICENTER AUTOSYS BROKER process packages up the request and transmits it to the mainframe-based

Unicenter AutoSys Connect system (based off machine definition) through the

Unicenter Common Communications Interface or CCI.


Message Types

Once the product receives the request on the mainframe, it performs a two-step process to submit and track the mainframe-based job.

The first step involves parsing the command string past by the UNICENTER

AUTOSYS BROKER process on the distributed platform. It must determine what mainframe based scheduling system the job will run in. It does this by scanning the command string for the “-s” parameter. Using our sample job definition previously shown the scheduling system this job would be executed in is CA-7.

To execute or initiate this request in CA-7, Unicenter AutoSys Connect must first locate the scheduling systems batch interface job control it has loaded in memory

(read from its parmlib dataset during startup). To do this it uses the three character scheduling name passed to it in the command string and appends it to prefix “ATCJ.” Using our sample job definition previously shown Unicenter

AutoSys Connect would attempt to locate the job control for ATCJCA7.

The batch interface job control has now been successfully located. Next,

Unicenter AutoSys Connect extracts the “-j” and “-c” parameters. This will allow

Unicenter AutoSys Connect to build the input command string the schedulers batch interface program will execute. Using our sample job definition previously shown Unicenter AutoSys Connect would insert a command string (replace

$CMDTEXT located within ATCJCA7) with “RUN,JOB=JOBC.” The scheduler’s batch interface job control is now ready to be submitted on the internal reader for execution.

This completes the first step.

Before submitting the batch interface job to the internal reader for execution,

Unicenter AutoSys Connect adds two dependencies to its incore dependency table. The first dependency to be added is an auto-added dependency for the batch interface job control (ATCJCA7). The second to be added is a start job dependency for the job (JOBC) to be executed within the mainframe based scheduling system. This allows Unicenter AutoSys Connect to not only track the job originally requested to be run but to also track the batch interface job control should it result in a failure, this can be transmitted back to Unicenter AutoSys as well. Unicenter AutoSys Connect dependencies can be viewed at the operator console through execution of the DEPLIST operator command.

Once the dependencies are successfully added, the batch interface job control is submitted. Following successful execution of this job, the mainframe-based scheduler should start the requested job.

Operation 4–3

Message Types

Unicenter AutoSys Connect is able to successfully track execution of both these jobs through its integration with the Unicenter ENF component. The Unicenter

AutoSys Connect application subscribes to ENF for the following events:

■

JOBINIT

■

JOBTERM

■

STEPTERM

■

JOBFAIL

■

MEMTERM

■

ENFTERM

If any of the following events occur on the mainframe system, the Unicenter ENF component notifies Unicenter AutoSys Connect of the event. Unicenter AutoSys

Connect interrogates the event data and determines, based on jobname using its dependency array, if the event in question matches a dependency it is tracking. If so, the event is then further evaluated and eventually transmitted back to

Unicenter AutoSys (UNICENTER AUTOSYS BROKER). The result is that the appropriate status (RUNNING, SUCCESS or FAILURE) is set on the original job, which had been submitted to the mainframe for execution.

Once the mainframe job completes and the JOBTERM event has been transmitted back to the Unicenter AutoSys system, the auto-added (ATCJCA7) and start job dependency (JOBC) will be deleted from the dependency array.

This completes the job life cycle (two-step process) within Unicenter AutoSys

Connect system. For additional information on implementing Unicenter AutoSys

Cross Platform Scheduling with Unicenter AutoSys Connect see the appendix

“Initiating Jobs on a Mainframe,” in this guide.


Message Types

ADD AGENT

When Unicenter AutoSys on the distributed platform is activated specifically during the startup of the Unicenter AutoSys, the UNICENTER AUTOSYS

BROKER process will transmit an ADD AGENT message request to Unicenter

AutoSys Connect based systems it will communicate with. This request simply allows Unicenter AutoSys Connect to register this remote Unicenter AutoSys node as someone who will be using its services.

Unicenter AutoSys Connect remote agent nodes can be viewed at the operator console through execution of the AGTLIST operator command.

ADD DEPENDENCY

The ADD DEPENDENCY request is received when a Unicenter AutoSys job definition contains a cross instance (external) dependency reference. For example, the following Unicenter AutoSys job definition would initiate an ADD

DEPENDENCY message request from the UNICENTER AUTOSYS BROKER. insert_job: JOBD owner: master machine: autosys type: c condition: success(JOBC^ACE) command: sleep 10

The ADD DEPENDENCY message request differs from the STARTJOB message request in that Unicenter AutoSys Connect will monitor for the start of job JOBC on the mainframe system. It will not initiate the start of JOBC manually or within some mainframe-based-scheduling system. Once this job is started and completes event statuses are reported back to the Unicenter AutoSys system much in the same fashion STARTJOB dependencies are processed. Please note, cross instance (external) dependencies are not deleted following success or failure of the job on the mainframe. If the same job is submitted again for execution, Unicenter AutoSys Connect treats this as a new execution of the job, will track it and send event statuses back to Unicenter AutoSys.

Unicenter AutoSys Connect dependencies can be viewed at the operator console through execution of the DEPLIST operator command.

Operation 4–5

Message Types

PING

The Unicenter AutoSys Connect system will receive, at two-minute intervals, an internal PING message request from registered Unicenter AutoSys remote nodes. This internal ping is initiated by the UNICENTER AUTOSYS BROKER and transmitted by CCI to Unicenter AutoSys Connect based systems. This allows the UNICENTER AUTOSYS BROKER to keep statuses of all Unicenter

AutoSys Connect based systems it is communicating with. Unicenter AutoSys

Connect internally registers the request and no further processing takes place.

Unicenter AutoSys Connect does not deploy an internal ping subtask to monitor its remote connections, but does track status through SUCCESS or FAILURE of send event buffers or through execution the ASPING operator command.

Unicenter AutoSys Connect remote agent nodes can be viewed at the operator console through execution of the AGTLIST operator command.


XCCODE Processing

XCCODE Processing

The following section covers the XCCODE process flow for Unicenter AutoSys

Connect.

Unicenter AutoSys Connect Startup

During Unicenter AutoSys Connect startup the EXEC PGM=ATCMAIN PARM= statement is verified for the presence of the XCCODE option in addition to verifying the ATCOPTS parmlib member which specify input control options, specifically XCCODE.

If the XCCODE option is active, then ATCMAIN invokes module ATCXCDR to process and load user-defined XCCODE entries into memory. XCCODE entries are located in parmlib member XCCODE and are of the following format:

JOB <jobname> STEP <stepname> RC <operator> <return_code>

JOB * RC NE 4091

JOB JOBA RC GT 8

JOB JOBA STEP99 RC EQ 16

JOB JOBB STEP * RC GT 16

JOB JOBC STEP STEP1 RC LE 4

XCCODE entries are processed by the routine ATCXCDR validating keywords

JOB, STEP, RC and OPERATOR, where OPERATOR can be (LE, LT, EQ, NE, GE,

GT). Each valid XCCODE entry is processed and loaded/sorted into memory.

XCCODE entries are sorted by JOB and then by STEP. Using the XCDLIST operator command, the display output presented to the user is the order in which each XCCODE entry will be applied to the STEPTERM and JOBTERM events of an individual JOB being processed. Invalid XCCODE entries and comment records are ignored.

If XCCODE entries are added or updated during Unicenter AutoSys Connect program execution, the REFRESH(XCCODE) operator command must be issued in order to refresh the incore table entries that currently exist. When the operator command is executed, existing entries will be flushed, followed by the reading

(from the parmlib XCCODE member) and reconstruction of the incore table.

Naturally, recycling Unicenter AutoSys Connect will have the same effect.

Operation 4–7

XCCODE Processing

XCCODE Process Flow

When a job is submitted for execution under control of Unicenter AutoSys

Connect and the XCCODE option is active, during normal event processing,

XCCODE evaluation is performed prior to dispatching the event (in the case of

STEPTERM and JOBTERM) back to AutoSys on the distributed platform. The

XCCODE evaluation routine is responsible for evaluating the incore XCCODE entries against a given step of a job, STEPTERM event, or the overall completion of the job, JOBTERM event.

JOBINIT

XCCODE processing specific to the job start or JOBINIT event is ignored. That is, all XCCODE processing is bypassed.

STEPTERM

When XCCODE processing is entered for STEPTERM processing of a job, and note, this will occur for each step within the job, each specific XCCODE job step entry is evaluated for a best match condition. XCCODE entries, which are job specific and not step specific, are discarded. For further clarification see the following table.

Jobname Stepname Evaluation

JOBA GT 4 NO

JOBA

JOBA

STEP1

*

JOBB

GT

GT

4

8

YES

YES

LT 12 NO

If multiple best match entries are found for a given step, the last best match entry is used when performing the SUCCESS/FAILURE evaluation. Using the table shown previously, there are two entries, which would best match STEPTERM evaluation for JOBA, STEP1. However, because only one entry can be applied to any given specific evaluation, Unicenter AutoSys Connect always uses the last one it finds. Therefore, when evaluating SUCCESS/FAILURE on JOBA, STEP1 the JOBA * GT 8 XCCODE entry would be used.


JOBTERM

XCCODE Processing

Now, if JOBA, STEP1 completes with a return code of “8” or less, an internal flag is set to mark this job dependency as SUCCESS. If the return code is greater than

“8”, the job dependency flag is set to a status of FAILURE. If in a prior step the job dependency flag had been set to SUCCESS and now the current step evaluates to failure, the job dependency flag is set to FAILURE. It should be noted, that once the job dependency flag is set to FAILURE, subsequent steps cannot overwrite the flag when XCCODE evaluation results in a SUCCESS.

Once a given step within a job evaluates to FAILURE, the overall status of the job will result in a FAILURE being sent back to AutoSys on the distributed platform.

All job steps that end with a nonzero return code must have XCCODE job step evaluations result in SUCCESS in order for a job status of SUCCESS to be sent back to AutoSys. Of course, the XCCODE job evaluation can override all subsequent job step evaluations thus nullifying the job dependency SUCCESS status.

When XCCODE processing is entered for JOBTERM processing of a job, each specific XCCODE job entry is evaluated for a best match condition. XCCODE entries, which are job step specific and not job specific, are discarded. For further clarification see the following table.

Jobname Stepname Evaluation

JOBA GT 4 YES

JOBA

JOBA

STEP1

*

JOBB

GT

GT

4

8

NO

NO

LT 12 YES

The same overall logic applies to XCCODE job evaluation. If the evaluation of an

XCCODE job entry results in SUCCESS and the job dependency status of the job being evaluated is not currently FAILURE, the overall status of the job evaluates to SUCCESS. However, if the job dependency status is currently set to FAILURE through prior XCCODE job step evaluation the job SUCCESS dependency is ignored and the overall job status is marked as FAILURE. Again, if more than one XCCODE best match is located for a specific job, the last best match entry is used in the SUCCES/FAILURE evaluation.

Operation 4–9


Unicenter AutoSys Connect and Unicenter AutoSys Failover

Unicenter AutoSys can be configured so it runs a second event processor, called the shadow event processor . The shadow event processor remains in an idle mode, receiving periodic messages (pings) from the primary event processor.

Basically, these messages indicate that all is well. However, if the primary event processor fails for some reason, the shadow event processor will take over responsibility of interpreting and processing events.

For jobs submitted to the mainframe that are currently running when the

Unicenter AutoSys failover occurs, Unicenter AutoSys Connect in prior versions would have attempted to send the job completion status to the primary event processor node. Naturally, this send would have failed and based on whether or not SEND_RETRY control option was active, the job completion status would be queued to memory or would be discarded. No further processing with this job completion status, if queued, would occur until the primary event processor came back online.

With the introduction of the Unicenter AutoSys environment variable

PRIMARYCCISYSID, Unicenter AutoSys Connect will now be able to dispatch job statuses to the Unicenter AutoSys shadow event processor node. This environment variable, if set on the distributed platform, is inserted in the communication buffers that Unicenter AutoSys Connect receives from the distributed platform. This value is used to determine whether or not a queued job status will be dispatched (rerouted) to another node. In this case the shadow event processor node.

For Unicenter AutoSys Connect to support Unicenter AutoSys failover, the only requirement that need be in place on the mainframe is that the SEND_RETRY control option be activated. As long as the Unicenter AutoSys nodes (primary and secondary) have set the environment PRIMARYCCISYSID, the rerouting of queued job statuses will occur seamlessly to the Unicenter AutoSys shadow event processor node.

To display the PRIMARYCCISYSID of a Unicenter AutoSys remote node the

PSYSID operator command can be used. For more detailed information on the

PSYSID operator command see the section Displaying PRIMARYCCISYSID in the chapter “Using Unicenter AutoSys Connect Option,” in this guide. The

PRIMARYCCISYSID is also displayed as part of the output generated by the

AGTLIST(<node_name>, <id>) operator command.



Unicenter AutoSys Connect Failover Support Process Flow

In documenting the process flow within Unicenter AutoSys Connect to support

Unicenter AutoSys High Availability using a Shadow Event Processor the following assumptions are made:

■

■

■

Primary Event Processor “A” installed on node “A.”

Shadow Event Processor “B” installed on node “B.”

Jobs are being submitted by Primary Event Processor “A” to Unicenter

AutoSys Connect for mainframe execution.

■

■

All jobs have completed with the exception of a job named “JOBC” which is currently in a RUNNING status within Primary Event Processor “A”. This indicates that JOBC is still running on the mainframe.

The Shadow Event Processor “B” is running in dormant mode.

With “JOBC” still running on the mainframe side, a failover occurs to Shadow

Event Processor “B” as the Primary Event Processor is no longer accessible on network. Shadow Event Processor “B” as part of its startup will initialize the

Unicenter Autosys Broker who is responsible for all cross-platform communication.

As part of the broker initialization on the shadow machine a setup (initialization) request is sent to Unicenter AutoSys Connect on the mainframe.

The initialization request will include the PRIMARYCCISYSID value as defined within the Unicenter AutoSys environment. When PRIMARYCCISYSID is dispatched from the shadow event processor machine its value will be equal to that of the primary event processor node, in our case Primary Event Processor

“A.” Unicenter AutoSys Connect receives this setup request and creates a new agent array entry. When constructing the new agent array entry, the value of the

PRIMARYCCISYSID is extracted from the setup request (as passed by Unicenter

AutoSys) and is stored for future evaluation.

The shadow event processor machine can now begin normal operations with the mainframe (job submission, external dependency requests, and so forth).

Operation 4–11


With this all said and done, “JOBC” now completes on the mainframe. Unicenter

AutoSys Connect will detect the job termination and attempt to send the job status completion event to Primary Event Processor “A.” This attempt will fail as Primary Event Processor “A” is no longer accessible on the network.

Unicenter AutoSys Connect will now interrogate its agent array list in an attempt to find an agent whose PRIMARYCCISYSID value is equal to that of the failed job status destination node (Primary Event Processor “A”). If a match is found, the status completion event is retrieved, repackaged and sent to the node identified in the matching agent entry, which in this case will be Shadow Event

Processor “B.” Otherwise, the status completion event is queued up for processing at a later point in time.


Appendix

A

Operator Commands

This appendix identifies useful operator commands and options to be used with the product.

Commands

The started task recognizes the following operator commands.

Command Description

STOP taskname

Brings the started task down.

F taskname AGTLIST operand Displays a list of agents and their statuses from which a remote message has been received.

F taskname AGTMOD operand

F taskname ASPING operand

F taskname DEBUG=n or:

F taskname DEBUG=(n)

F taskname DELDEP operand

F taskname DEPLIST operand

Modifies an individual agent’s status.

Obtains the status of a remote node by initiating a ping message to it.

Sets the debugging level, where n is a number from 0 to 9. The volume of debugging messages increases as the debugging level increases.

Deletes orphaned job dependencies.

Displays a list of dependencies (jobnames) being monitored for execution.

Operator Commands A–1

Commands


F taskname PSYSID operand

Displays the PRIMARYCCISYSID of the remote node.

F taskname QSDFREE operand

F taskname QSDLIST operand

Allows a remote nodes queued send entries to be removed.

Displays a list of queued send buffers (send buffers are queued when the initial send to the remote node fails).

F taskname REFRESH operand

Enables a refresh (update) of the specified storage, where operand can be:

PARMLIB—Refreshes private storage with any updated parmlib member. This includes all batch interface JCL members and the XCCODE parmlib member.

ATCJCL—Refreshes batch interface JCL private storage.

XCCODE—Refreshes XCCODE private storage.

XDEP — Refreshes external dependencies received from a remote node.

A–2 Installation and Administrator Guide

Commands


F taskname STATUS operand

Obtain status on the Unicenter AutoSys Connect environment, where operand can be:

VERSION— Displays current version information.

DEBUG— Displays current debug value and where debug messages are directed.

F taskname XCDLIST

DEPENDENCY — Displays total number of dependencies including a break down by the type of dependency.

CCI — Displays the status of the Unicenter AutoSys Connect

CCI interface along with RECEIVE, SEND, QUEUED SEND and ERROR communication counts.

ENF — Displays the status of the Unicenter AutoSys Connect

ENF interface along with processed event counts.

REQUESTS— Displays remote request totals for add dependencies, delete dependencies, start job, refresh and ping requests.

OPERCMD—Displays a total number of operator commands issued.

OPTIONS—Displays the current value of options specified through the EXEC PGM PRM= statement or as coded in the

ACTOPTS parmlib member.

Displays a list of XCCODE entries used to determine whether a job should fail based on job or jobstep condition code.

Operator Commands A–3

Appendix

B

Troubleshooting

This appendix contains message codes for Unicenter AutoSys Connect Option.

Use the following list of messages as a resource for troubleshooting purposes.

Message Codes

The syntax of the Unicenter AutoSys Connect Option Option message codes is:

ATC xxxxC where xxxx is a four-digit identifier and C specifies the type of message as follows:

■

■

■

E for Error

W for Warning

I for Informational

ATC0001E

REQ=ADD_DEP (AD ) FAILED - DATA COUNT IS ZERO

ATC0002E

An Add Dependency (external reference) request was formatted incorrectly on the Unicenter AutoSys platform. Check the job definition on the Unicenter

AutoSys platform to ensure it has been defined correctly.

REQ=ADD_DEP (AD ) FAILED - DATA LENGTH IS ZERO

An Add Dependency (external reference) request was formatted incorrectly on the Unicenter AutoSys platform. Check the job definition on the Unicenter

AutoSys platform to ensure it has been defined correctly.

Troubleshooting B–1

Message Codes

ATC0003E

ATC0004E

ATC0010I

ATC0011I

ATC0012W

ATC0013E

REQ=ADD_DEP (AD ) – DEPENDENCY ADD FAILED

An attempt to add a dependency to the dependency array failed. Check the log to determine why the Add Dependency failed. If the Unicenter AutoSys Connect

Option log does not provide any meaningful information activate the DEBUG control option and work on the problem.

DEPENDENCY NAME IS NOT IN UPPER CASE DEP=[ dependencyname]

-

DEPENDENCY IGNORED

Attempt to add a dependency whose name was not in uppercase failed. Check the job definition on the Unicenter AutoSys platform to ensure the dependency is in uppercase.

READING ACTOPTS INPUT OPTIONS

The ACTOPTS input member in the Unicenter AutoSys Connect Option parmlib is being read. This message occurs during Unicenter AutoSys Connect Option startup.

PROCESSING OPTION [ optionname]

An informational message providing the ACTOPTS input option that is being processed. This message occurs during Unicenter AutoSys Connect Option startup.

ACTOPTS DD STATEMENT IS MISSING

Unicenter AutoSys Connect Option was unable to locate the ATCOPTS DD statement. Product option defaults will be used.

ACTOPTS DD OPEN FAILED

Unicenter AutoSys Connect Option was unable to open the ATCOPTS DD statement. Verify the ACTOPTS DD statement has been coded correctly. The dataset pointed to by ACTOPTS must be a partitioned dataset with an

LRECL=80, BLKSIZE=<multiple of LRECL>,DSORG=PO and contain a member named ATCOPTS. Product option defaults will be used.

B–2 Installation and Administrator Guide

ATC0014W

ATC0015W

ATC0016W

ATC0017W

ATC0018E

ATC0020W

ATC0021E

ATC0022I

Message Codes

DEBUG VALUE ALREADY SET FROM EXEC PARM - OPTION IGNORED

The DEBUG control option has already been specified on the EXEC PGM= statement. The ATCOPTS value will be ignored.

FILTER ALREADY SET FROM EXEC PARM – OPTION IGNORED

The FILTER= control option has already been specified on the EXEC PGM= statement. The ATCOPTS value will be ignored.

XCCODE ALREADY SET FROM EXEC PARM – OPTION IGNORED

The XCCODE control option has already been specified on the EXEC PGM= statement. The ATCOPTS value will be ignored.

INVALID OPTION SPECIFIED - OPTION IGNORED

Unicenter AutoSys Connect Option has detected an invalid control option.

Option record is ignored.

INVALID OPC SUBSYSTEM NAME PASSED

The OPC subsystem name passed on the FILTER command is not valid. Specify a valid OPC subsystem name.

ACTOUT DD STATEMENT IS MISSING

Unicenter AutoSys Connect Option was unable to locate the ATCOUT DD statement when attempting to write DEBUG messages to the ATCOUT dataset.

All DEBUG messages will now be written to the operator console.

ACTOPTS DD OPEN FAILED

Unicenter AutoSys Connect Option was unable to open the ATCOUT DD statement. Verify the ACTOUT DD statement has been coded correctly. The dataset identified by ACTOUT must be a sequential dataset with LRECL=133,

BLKSIZE=<multiple of LRECL>,DSORG=PS and must contain a member named

ATCOPTS. All DEBUG messages will now be written to the operator console.

DEBUG MESSAGES WILL BE LOGGED TO OPERATOR CONSOLE

All DEBUG messages issued due to the setting of the DEBUG control option will now be routed to the operator console.


Message Codes

ATC0023I

ATC0024I

UNICENTER AUTOSYS CONNECT DEBUG LOG START

Starting stamp written to the ACTOUT DEBUG log dataset following execution of the DMSG(LOG) operator command.

UNICENTER AUTOSYS CONNECT DEBUG LOG END

Ending stamp written to the ACTOUT DEBUG log dataset following execution of the DMSG(LOG) operator command.

UNICENTER AUTOSYS CONNECT DEBUG LOG HAS BEEN CLOSED

ATC0025I

An information message issued after the successful close of the ACTOUT

DEBUG log dataset. This occurs after a successful shutdown, or when the writing of DEBUG messages is switched to the system operator console or to the system log.

ATC0030E

ATCJOBS DD STATEMENT IS MISSING

ATC0031E

ATC0032E

In order to use the Unicenter AutoSys Connect direct submit feature the

ATCJOBS DD statement must be present in the Unicenter AutoSys Connect started task job control. The datasets pointed to by ATCJOBS must be a partitioned dataset , DSORG=PO, with LRECL=80.

ATCJOBS DD OPEN FAILED

Unicenter AutoSys Connect was unable to open the ATCJOBS DD statement.

Verify the ACTJOBS DD statement has been coded correctly. The dataset pointed to by ACTJOBS must be a partitioned dataset with an LRECL=80,

BLKSIZE=<multiple of LRECL>,DSORG=PO.

UNABLE TO LOCATE JOB=[ jobname] IN ATCJOBS

A direct submit request was issued to Unicenter AutoSys Connect for job

[ jobname] but the job control could not be located in the ATCJOBS in the datasets. Make sure there is a partitioned dataset member located in the

ATCJOBS dataset by the name [ jobname].


ATC0033E

ATC0034I

ATC0035I

ATC0036I

ATC0037I

Message Codes

GETMAIN FAILED FOR DIRECT SUBMIT SETUP JOB=[ jobname] - DIRECT

SUBMIT ABORTED

An attempt to allocate working storage during direct submit job processing failed. This error condition results in the job request being aborted. The region size of the Unicenter AutoSys Connect task should be increased.

JOB RECORD=[ jobrecord]

This information message is printed when Unicenter AutoSys Connect is reading the job control for the job to be submitted. Each record will be printed prior to putting it on the internal reader. This informational message is printed when the

DEBUG level is >=9.

READING A BLOCK FROM ATCJOBS FOR JOB=[ jobname]

This information message is printed when Unicenter AutoSys Connect is reading the job control for the job to be submitted. This informational message is printed when the DEBUG level is >=9.

READ SUCCESSFUL JOB=[ jobname] FROM ATCJOBS

This information message is printed when Unicenter AutoSys Connect completes reading the job control for the job to be submitted. This informational message is printed when the DEBUG level is >=9.

PROCESSING DIRECT SUBMIT REQUEST JOB=[ jobname]

This message is printed when Unicenter AutoSys Connect receives a direct submit job request. This informational message is printed when the DEBUG level is >=9.


Message Codes

ATC0050E

ATC0052I

ATC0051W

GETMAIN ERROR FUNC=ADD_AGENT (4A)

An attempt to add an agent to the agent array failed because a getmain call failed. Obtain an agent list report (see the AGTLIST operator command) to determine the number of agents in the array. Each array entry is 32 bytes long. If the agent list report shows no errors, the region on the Unicenter AutoSys

Connect Option task should be increased.

REQ=ADD_AGENT (4A) IGNORED - DUPLICATE NODE={ nodename} -

DUPLICATE KEY

An attempt to add an agent to the agent array failed because the agent already exists. The request is ignored and no further processing takes place. This DEBUG message prints when the DEBUG level is set to “9”.

REQ=ADD_AGENT (4A) SUCCESSFUL NODE={ nodename} APPLICATION

NAME={ applicationname}

ATC0053E

An attempt to register a Unicenter AutoSys remote completed successfully. This

DEBUG message prints when the DEBUG level is set to “9”.

REQ=ADD_AGENT (4A) FAILED NODE={ nodename} APPLICATION


An attempt to add an agent to the agent array failed. There should be a preceding message which identifies why the add agent request failed.

ATC0055I

ANODE=[ agentnodename]

AAPPL=[ agentapplicationname]INODE[inputnodename]

IAPPL=[ inputapplicationname]

Unicenter AutoSys Connect Option has received an add agent request and is verifying whether or not this agent already exists. ANODE represents an agent node Unicenter AutoSys Connect Option has already registered. INODE is the new requested node to be added. This DEBUG message prints when the DEBUG level is set to “9”.


ATC0056I

ATC0057I

ATC0058I

ATC0059I

ATC1060I

ATC0101E

Message Codes

REQ=AUTO ADD_AGENT (4A) NODE={ nodename} APPLICATION


A ping request was received from a Unicenter AutoSys remote node but the remote node does not exist in the agent array. The remote node will be added through an auto add request prior to processing the ping request. This DEBUG message prints when the DEBUG level is set to “9”.

NEW STORAGE OBTAINED FOR AGENT ARRAY

An add agent request was received but the current agent array is not large enough to accommodate this request. Unicenter AutoSys Connect Option will dynamically add storage to the array and then process the add agent request.

This DEBUG message prints when the DEBUG level is set to “9”.

OLD AGENT ARRAY STORAGE RELEASED

As a result of processing message ATC0057I and obtaining new storage for the agent array the old storage associated with the original array is freed. This


ADD AGENT SUCCESSFUL NODE={ nodename} APPLICATION


An attempt to register a Unicenter AutoSys remote completed successfully.

SUBMITTED JOB=[ jobname] FROM DIRECT SUBMIT REQUEST

This message is printed when Unicenter AutoSys Connect submits the direct submit job request. This informational message is printed when the DEBUG level is >=9.

FILTER PROCESSING FAILED – GETMAIN ERROR

An attempt to allocate working storage during filter processing failed. This error condition results in the shutdown of the started task. The region size of the

Unicenter AutoSys Connect Option task should be increased.


Message Codes

ATC0102E

ATC0201E

ATC0203I

ATC0204I

FILTER PROCESSING FAILED

An attempt to set up processing failed. An attempt to add an agent to the agent array failed. There should be a preceding message that identifies why the filtering request failed.

UNRECOGNIZED CCI FUNCTION REQUESTED

A call was made to the OS/390 Unicenter CCI Common Services with invalid parameters. This should not occur during normal operations and represents a processing error. If the cause of the error is not obvious, contact Computer

Associates Technical Support for further assistance.

LOCAL CCI SYSID={ sysid}

An attempt to initialize the OS/390 Unicenter CCI services completed successfully. The OS/390 Unicenter CCI sysid is displayed as {sysid} in the message.

OS/390 UNICENTER CCI SERVICES SUCCESSFULLY INITIALIZED

An attempt to initialize the OS/390 Unicenter CCI services completed successfully. This informational message appears during normal startup of

Unicenter AutoSys Connect Option.

OS/390 UNICENTER CCI SERVICES HAVE BEEN TERMINATED

ATC0205I

The OS/390 Unicenter CCI services interface has terminated successfully. This informational message appears during normal shutdown of Unicenter AutoSys

Connect Option.

LOCAL APPLICATION NAME ={ applicationname}

ATC0206I

An attempt to initialize the OS/390 Unicenter CCI services completed successfully. The Unicenter AutoSys Connect Option application name it uses to communicate with Unicenter AutoSys remote nodes is displayed.

ATC0210E

FUNC=[ function] FAILURE

An attempt to perform an OS/390 Unicenter CCI function failed. The function name is identified in the message. Messages ATC0214I, ATC0215I, ATC0216I and ATC0217 follow providing additional information on the function failure.


Message Codes

ATC0211E

OS/390 UNICENTER CCI SERVICES NOT AVAILABLE

An attempt to initialize the OS/390 Unicenter CCI services failed. Check previous messages in the log for an associated message if any. This should not occur during normal operations and could represent a processing error or setup error. Verify the OS/390 Unicenter CCI service is correctly installed and running.

Message ATC0212I will be displayed until Unicenter AutoSys Connect Option initializes successfully with the OS/390 Unicenter CCI service or is shutdown.

If the cause of the error is not obvious, contact Computer Associates Technical

Support for further assistance.

AUTOSYS CONNECT WAITING ON OS/390 UNICENTER CCI SERVICES

ATC0212I

This message is displayed following a failed attempt to initialize with the

OS/390 Unicenter CCI services. Unicenter AutoSys Connect Option will attempt on 60-second intervals to reinitialize with the OS/390 Unicenter CCI services.

ATC0213I

FUNC=[ function] SUCCESSFUL

An attempt to perform an OS/390 Unicenter CCI function was successful. The function name is identified in the message. Messages ATC0214I, ATC0215I, and

ATC0216I follow providing additional information on the successful function call.

ATC0214I

SID=[ sendnode] SAPP=[sendapplicationname]

Identifies the sending node and application name associated with message

ATC0210E or ATC0213I.

ATC0215I

RID=[ receivenode] RAPP=[receiveapplicationname]

Identifies the receiving node and application name associated with message


ATC0216I

RC=[ rc] DRC=[drc]

Identifies the return code and extended return code associated with message



Message Codes

ATC0217I

ATC0220I

ATC0221E

ATC0222I

ATC0230E

ATC0240E

ATC0241E

ERROR DESCRIPTION: [ feedback message]

Identifies the feedback message associated with message ATC0210E.

UNICENTER AUTOSYS CONNECT CURRENTLY PROCESSING ACTIVE

JOBS – CONTINUE SHUTDOWN (Y|N)?

Unicenter AutoSys Connect Option has received a shutdown command and is still processing active jobs. Reply “Y” to continue the shutdown process, or “N” to ignore the request and continue processing.

INVALID REPLY - SHUTDOWN IGNORED

An invalid reply has been detected to message ATC0220I. Unicenter AutoSys

Connect Option has ignored the shutdown request and will continue with normal processing. Valid reply values to message ATC0220I are “Y” or “N.”

UNICENTER AUTOSYS CONNECT SHUTDOWN IGNORED

This message occurs after replying “N” to message ATC0220I. Unicenter

AutoSys Connect Option has ignored the shutdown request and will continue with normal processing.

SUBPARAMETERS MISSING OR ARE INVALID – COMMAND IGNORED

The dependency name, dependency type, node or id specified on the DELDEP operator command is not valid. Specify the correct sub parameter type and resubmit the operator command.

INVALID FORMAT DETECTED - DEPENDENCY NAME NOT VALID

The dependency name specified on the DELDEP operator command is not valid.

Please specify a valid dependency type and resubmit the operator command.

INVALID FORMAT DETECTED - DEPENDENCY TYPE NOT VALID

The dependency type specified on the DELDEP operator command is not valid.

Valid dependency types are “AD,” “SJ” or “**.” Specify a valid dependency type and resubmit the operator command.


ATC0242I

ATC0243I

ATC0244E

ATC0246I

ATC0247I

ATC0245W

Message Codes

PROCESSING OPERATOR DELETE DEPENDENCY REQUEST

This information message is printed when Unicenter AutoSys Connect is processing a delete dependency operator command. This informational message is printed when the DEBUG level is >=9.

**DELETED** DEPNAME=[ dep ndency_name] TYPE=[dependency_type]

NODE=[ node] APPL=[application_name]

This information message is printed when Unicenter AutoSys Connect is processing a delete dependency operator command. It identifies the deleted dependency.

UNABLE TO OBTAIN NODE APPLICATION NAME – COMMAND

IGNORED

When processing a delete dependency request, Unicenter AutoSys Connect was unable to obtain the node application name for the node and id specified on the

DELDEP operator command. Check the command for a valid node and id and resubmit the operator command.

DEPENDENCY DOES NOT EXIST - COMMAND IGNORED

When processing a delete dependency request, Unicenter AutoSys Connect was unable to locate a valid dependency to satisfy this request. Check the command for valid parameters and resubmit the operator command.

SKIPPING DEPENDENCY DELETE

This message is printed when Unicenter AutoSys Connect is processing a delete dependency request. This informational message indicates the dependency will not be deleted. This informational message is printed when the DEBUG level is

>=9.

INODE=[array_node_name] ONODE=[operator_node_name]

IAPPL=[array_application_name] OAPPL=[operator_application_name]

ITYPE=[dependency_type] OTYPE=[dependency_type]

This message is printed when Unicenter AutoSys Connect is processing a delete dependency request. This informational message is printed when the DEBUG level is >=9.


Message Codes

ATC0248I

TOTAL DEPENDENCIES DELETED ( nnnnnn)

This information message is printed when Unicenter AutoSys Connect completes the delete dependency request. This message indicates the total number of dependencies deleted.

ATC0249I

PLEASE ENTER NODE APPLICATION NAME FOR [node] OR ''N'' TO

CANCEL

This message is printed when the agent id specified on the DELDEP operator command is set to “0.” Reply with a valid 20-character application name for this node or reply “N” to cancel the command.

ATC0251W

UNRECOGNIZED OPERATOR COMMAND

An unrecognized operator command was entered for the started task. The command is ignored. This warning message indicates the operator command entered was not valid.

ATC0252W

MODIFY DEBUG OPERATOR COMMAND FAILED – INVALID DEBUG

LEVEL

The DEBUG operator command was entered for the started task with an invalid

DEBUGging value. Valid DEBUG levels are 1-9. The command is ignored and the DEBUG level does not change. This warning message indicates the operator command entered was not valid.

ATC0253W

UNRECOGNIZED MODIFY OPERATOR COMMAND

A modify operator command was entered for the started task but was not recognized. The command will be ignored. This warning message indicates the operator command entered was not valid.

RECEIVED OPERATOR COMMAND

ATC0254I

This information message is printed when an operator command is received.

ATC0255I

COMPLETE

This information message is printed when an operator command has been successfully processed.


Message Codes

ATC0256E

AGENT ID SPECIFIED IS NOT NUMERIC

The operator command received did contain a numeric value required for the agent ID field. Execute the STATUS(CCI) or AGTLIST command to obtain a valid ID for the node. Correct and reenter the command at the operator console.

ATC0257I

COMMAND

ATC0258E

This information message is printed when an operator command has passed initial validation and will begin execution.

AGENT NODE OR ID SPECIFIED IS INVALID

ATC0259I

The operator command received did contain a valid node name or ID. Execute the STATUS(CCI) or AGTLIST command to obtain a list of nodes and their associated ids. Correct and reenter the command at the operator console.

ASPING SUCCESSFUL NODE=[ nodename]

This information message is printed when an ASPING operator command is executed. It indicates that Unicenter AutoSys Connect Option was successful in communicating with the remote node specified within the command.

ASPING FAILED NODE=[ nodename] ID=[id]

ATC0260E

Unicenter AutoSys Connect Option was unable to communicate with the remote node identified in the message. The remote node is marked inactive.

ATC0261W

NODE=[ nodename] ID=[id] NOT PRESENT IN AGENT LIST – COMMAND

IGNORED

Unicenter AutoSys Connect Option was unable to locate the remote node in its agent array. No further processing takes place.

ATC0262I

AGENT MATCH DETECTED

Unicenter AutoSys Connect Option was able to successfully locate a match in its agent array against the target input node. This DEBUG message prints when the

DEBUG level is set to “4”.


Message Codes

ATC0263I


ID=[ agentapplicationname]INODE[inputnodename]

ID=[ inputapplicationname]

Unicenter AutoSys Connect Option has received an add agent request and is verifying whether this agent already exists, searching by node and ID. ANODE represents an agent node that Unicenter AutoSys Connect Option has already registered. INODE is the new requested node to be added. This DEBUG message prints when the DEBUG level is set to “9”.

ATC0264I


AAPPL=[ agentapplicationname]INODE[inputnodename]

IAPPL=[ inputapplicationname]

Unicenter AutoSys Connect Option has received an add agent request and is verifying whether or not this agent already exists searching by node and application name. ANODE represents an agent node Unicenter AutoSys Connect

Option has already registered. INODE is the new requested node to be added.

This DEBUG message prints when the DEBUG level is set to “9”.

ATC0265W

ATC0266E

AGENT LIST IS EMPTY – COMMAND IGNORED

Unicenter AutoSys Connect Option received an operator command, which specifies it as an input node name, but found it has no registered remote nodes.

No further processing takes place.

AGENT ID MAX LENGTH EXCEEDED

ATC0267E

The ID value specified on the input operator command is invalid. A value of 1-99 is allowed. Execute the STATUS(CCI) or AGTLIST command to obtain a list of nodes and their associated ids. Correct and reenter the command at the operator console.

REFRESH EXTERNAL DEPENDENCY FAILED NODE=[ nodename] ID=[id]

The refresh external dependency command has failed. For more information of the failure of the command, see the preceding messages. The id value specified on the input operator command is invalid, only a value of 1-99 is allowed.

Execute the STATUS(CCI) or AGTLIST command to obtain a list of nodes and their associated ids. Correct and reenter the command at the operator console. If the cause of the error is not obvious, contact Computer Associates Technical

Support for further assistance.


Message Codes

ATC0268I

NODE=[ nodename] ID=[id] APPL=[applicationname]

[

ACTIVE|INACTIVE]

ATC0269I

When a remote node is unable to be contacted or after being marked inactive, sends a request to the Unicenter AutoSys Connect Option it will set the respective node either INACTIVE or ACTIVE in its agent array.

DUPLICATE AGENT ENTRY DETECTED– CHECKING STATUS

ATC0270I

A duplicate entry has been detected in the Unicenter AutoSys Connect Option agent array prior to processing a remote node request. Unicenter AutoSys

Connect Option is verifying the current status of the agent in its array. This


REFRESH EXTERNAL DEPENDENCY REQUEST SUCCESSFULLY SENT TO

NODE=[ nodename]

ATC0271I

ATC0272I

ATC0273I

Unicenter AutoSys Connect Option was successful in sending a refresh external dependency request to the remote node.

AGENT ID=< id> SSAX ID=<id>

This message is printed when the agent id comparisons are being executed. This informational message is printed when the DEBUG level is >=9.

COMPARING INODE[ inputnodename] IAPPL=[inputapplicationname]

ANODE=[ agentnodename] AAPPL=[agentapplicationname] PSYSID=[psysid]

This message is printed when the agent id comparisons are being executed. This informational message is printed when the DEBUG level is >=4.

MATCH FOUND USING PSYSID=[ psysid] NODE=[node_name]

ATC0274I

This message is printed when the agent id comparisons are being executed on

PSYSID. The message indicates the search found a match for the identified

PSYSID. This informational message is printed when the DEBUG level is >=4.

MATCH NOT FOUND FOR PSYSID=[ psysid]

This message is printed when the agent id comparisons are being executed on

PSYSID. The message indicates the search did not find a match for the identified

PSYSID. This informational message is printed when the DEBUG level is >=4.


Message Codes

ATC0275I

ATC0276W

ATC0277I

ATC0278I

ATC0279E

PRIMARYCCISYSID=[ psysid] FOR NODE=[node] APPL=[application_name]

ID=[ id]

This message is printed during execution of the PSYSID operator command indicating the PRIMARYCCSYSID value for the input node.

UNABLE TO LOCATE PRIMARYCCISYSID FOR NODE=[ node] ID=[id]

This message is printed during execution of the PSYSID operator command indicating the PRIMARYCCSYSID value for the input node was not found.

NODE=[ node] APPL=[application_name] NOT ACTIVE – QUEUED SEND

BYPASSED

This message is printed after Unicenter AutoSys Connect has determined the node in which to dispatch a queued send buffer through the PSYSID lookup is not active. The queued job status is left unprocessed and remains in memory until either the Unicenter AutoSys primary or shadow event processor nodes become active. This informational message is printed when the DEBUG level is

>=4.

USING PSYSID=[ psysid] FOR THIS QUEUED SEND REQUEST

The psysid or PRIMARYCCISYSID value is used when Unicenter AutoSys

Connect is determining whether or not a queued send buffer should be rerouted to a node other than the one it was originally destined for. The

PRIMARYCCISYSID is sent to Unicenter AutoSys Connect by the remote

Unicenter AutoSys node. It is maintained and used by Unicenter AutoSys

Connect during queued send event processing to support Unicenter AutoSys failover. This informational message is printed when the DEBUG level is >=4.

INVALID AGENT MOD STATUS SPECIFIED – COMMAND IGNORED

An invalid status was specified on the AGTMOD operator command. Valid statuses are:

“A” ACTIVE

“I” INACTIVE

“U” UNKNOWN

“D” DELETED

Specify a valid status and retry the command.


ATC0280W

ATC028II

ATC0301E

ATC0302E

ATC0303E

ATC0304I

Message Codes

UNABLE TO LOCATE SPECIFIED AGENT – COMMAND IGNORED

The remote node specified by the AGTMOD was invalid. Check the remote node name, id or application name specified. Correct and retry the command.

REPLY ''Y'' TO CONFIRM DELETE REQUEST OR ''N'' TO CANCEL. NOTE:

ACTION IS IRREVERSIBLE ONCE COMPLETED

This message is printed when the agent id specified on the AGTMOD operator command is set to “0”. Reply with a valid 20-character application name for this node or reply “N” to cancel the command.

REQ=FIND_DEP (FD) NOT FOUND JOB=[ jobname] NODE=[nodename]

The dependency for jobname was not found. A delete dependency request was sent from Unicenter AutoSys for a dependency that was not found in the dependency array. This can also be a processing error. If the cause of the error is not obvious, contact Computer Associates Technical Support for further assistance.

REQ=FIND_DEP (FD) FAILED JOB=[ jobname] NODE=[nodename]

A call to the dependency find routine failed. Check prior log messages to determine the cause. This can occur during processing of a delete dependency request from Unicenter AutoSys. If the cause of the error is not obvious, contact

Computer Associates Technical Support for further assistance.

REQ=DEL_DEP (DD) FAILED JOB=[ jobname] NODE=[nodename]

A call to the dependency delete routine failed. Check prior log messages to determine the cause. This can occur during processing of a delete dependency request. If the cause of the error is not obvious, contact Computer Associates

Technical Support for further assistance.

REQ=DEL_DEP (DD) SUCCESSFUL JOB=[ jobname} NODE {nodename}

A call to the dependency delete routine completed successfully for jobname sent from nodename. This informational message prints when the DEBUG level is

>=3.


Message Codes

ATC0305I

ATC0306I

ATC0307I

ATC0308I

ATC0351E

DEPENDENCY DELETE ENTERED: JOB=[ jobname] NODE=[nodename]

APPL=[ application_name]

This message is printed when Unicenter AutoSys Connect is processing a delete dependency request. This informational message is printed when the DEBUG level is >=9.

COMPARING INODE=[ input_nodename] IAPPL=[input_applicationname]

DNODE[ dependency_nodename] DAPPL=[dependency_applicationname]

Unicenter AutoSys Connect has received a delete dependency request and is verifying whether or not the input dependency node and application name matches the current dependency node and application name, which is being evaluated. This debug message prints when the debugging level is set to “9”.

IPSYS[ input_prima yccisysid] DPSYS[dependency_primaryccisysid]

Continuation of message ATC0306I. This message identifies the input and dependency primaryccisysid, which is being compared. This debug message prints when the debugging level is set to “9”.

MATCH FOUND - DEPENDENCY WILL BE DELETED

This message identifies that Unicenter AutoSys Connect has successfully matched the input dependency against the current dependency entry. The dependency entry will be deleted. This debug message prints when the debugging level is set to “9”.

REQ=ADD_DEP (AD) FAILED JOB={ jobname} NODE=[nodename] –

GETMAIN ERROR

An attempt to add a dependency to the dependency array failed because a getmain call failed. Obtain a dependency list report (see DEPLIST operator command) to determine the number of dependencies in the array. Each array entry is 64 bytes long. If the dependency list report shows no errors, the region size of the Unicenter AutoSys Connect Option task should be increased. If the cause of the error is not obvious, contact Computer Associates Technical Support for further assistance.


ATC0352W

ATC0353I

ATC0354I

ATC0355I

ATC0356I

Message Codes

REQ=ADD_DEP (AD) IGNORED – ALREADY PRESENT IN LIST

JOB={ jobname}

An attempt to add a dependency to the dependency array failed because the dependency already exists. This warning message indicates an attempt to add a duplicate dependency. To view the current dependency list Unicenter AutoSys

Connect Option is processing use the DEPLIST operator command. This informational message prints when the DEBUG level is >=3.

REQ=ADD_DEP (AD) SUCCESSFUL JOB { jobname} NODE {nodename}

An attempt to add a dependency to the dependency array completed successfully. This addition occurred because of a start job request or an add dependency request from Unicenter AutoSys. This information message prints when the DEBUG level is >=3.

REQ=AUTOADD_DEP (AD) SUCCESSFUL JOB { jobname} NODE {nodename}

An attempt to add a dependency to the dependency array completed successfully. This addition is for the batch interface job that starts the job requested in the start job request from Unicenter AutoSys. This informational message prints when the DEBUG level is >=3.

NEW STORAGE OBTAINED FOR DEPENDENCY ARRAY

An add dependency request was received but the current dependency array is not large enough to accommodate this request. Unicenter AutoSys Connect

Option will dynamically add storage to the dependency array and then process the add dependency request. . This DEBUG message prints when the DEBUG level is set to “9”.

OLD DEPENDENCY ARRAY STORAGE RELEASED

As a result of processing message ATC0355I and obtaining new storage for the dependency array the old storage associated with the original array is freed. This



Message Codes

ATC0401E

REQ=DEL_DEP FAILED - INDEX IS NEGATIVE

An attempt to delete a dependency from the dependency array failed because the specified index is negative. This is a processing error and should not occur during normal processing. If the cause of the error is not obvious, contact


REQ=DEL_DEP FAILED - INDEX IS PAST END OF ARRAY

ATC0402E

An attempt to delete a dependency from the dependency array failed because the specified index is past the end of the array. This is a processing error and should not occur during normal processing.

ATC0501I

XCCODE STATUS IS [ status]

This message displays the current status XCCODE.

ATC0502I

[ version]

This information message is produced as part of the output generated by the

STATUS or STATUS(VER) operator command indicating what version of

Unicenter AutoSys Connect Option is running.

ATC0504I

ATC0505I

OPERATOR COMMAND STATUS


STATUS operator command.

OPERATOR COMMANDS [( xxxxxxxxxxx)]


STATUS operator command indicating the number of operator commands that have occurred since Unicenter AutoSys Connect Option has been started.

ATC0506I

XCCODE STATUS


STATUS or STATUS(XCCODE) operator command.


Message Codes

ATC0507I

[

ACTIVE | INACTIVE]


STATUS or STATUS(XCCODE) operator command indicating the current status of XCCODE.

ATC0508I

ENTRIES[( xxxxxxxxxxx)]

ATC0509I


STATUS or STATUS(XCCODE) operator command indicating the current number of active XCCODE entries.

NO EXEC STARTUP PARMS PASSED


STATUS operator command indicating that no parameters were passed on the

EXEC PGM= statement.

ATC0511I

STATUS


STATUS or STATUS(ENF) operator command.

ATC0512I

[ eventname] [(xxxxxxxxxxx)]

ATC0514I


STATUS or STATUS(ENF) operator command indicating the event name and the number of events that have occurred.

OS/390 UNICENTER [ component] SERVICES ARE [status]


STATUS, STATUS(CCI) or STATUS(ENF) operator commands indicating the status of the respective OS/390 Unicenter component.

ATC0515I

STATUS


STATUS or STATUS(REQ) operator command.


Message Codes

ATC0516I

[ requestname] [(xxxxxxxxxxx)]


STATUS or STATUS(REQ) operator command indicating the remote request type and the number of requests for that type that have occurred.

ATC0517I

STATUS


STATUS or STATUS(CCI) operator command.

ATC0518I

[( xxxxxxxxxxx)]


STATUS or STATUS(CCI) operator command indicating the number of CCI receives Unicenter AutoSys Connect Option has processed from remote

Unicenter AutoSys nodes.

ATC0519I

[( xxxxxxxxxxx)]


STATUS or STATUS(CCI) operator command indicating the number of CCI sends Unicenter AutoSys Connect Option has processed to remote Unicenter

AutoSys nodes.

ATC0520I

STATUS


STATUS or STATUS(DEP) operator command.

ATC0521I

[( xxxxxxxxxxx)]


STATUS or STATUS(DEP) operator command indicating the number of active dependencies Unicenter AutoSys Connect Option is currently processing.

ATC0522I

[( xxxxxxxxxxx)]


STATUS or STATUS(DEP) operator command indicating the number of external dependencies (AD) Unicenter AutoSys Connect Option is currently processing.


Message Codes

ATC0523I

[( xxxxxxxxxxx)]

ATC0524I


STATUS or STATUS(DEP) operator command indicating the number of startjob dependencies (SJ) Unicenter AutoSys Connect Option is currently processing.

PROCESSED STARTJOB [( xxxxxxxxxxx)]

ATC0524I


STATUS or STATUS(DEP) operator command indicating the number of startjob dependencies Unicenter AutoSys Connect Option has processed.

PROCESSED AUTOADD [( xxxxxxxxxxx)]

ATC0530I

ATC0531I

ATC0532I

ATC0533I


STATUS or STATUS(DEP) operator command indicating the number of auto add dependencies Unicenter AutoSys Connect Option has processed.

QUEUED SENDS [( xxxxxxxxxxx)]


STATUS or STATUS(CCI) operator command indicating the number of CCI queued sends Unicenter AutoSys Connect Option is waiting to dispatch to the respective remote Unicenter AutoSys nodes.

PING REQUESTS [(xxxxxxxxxx)]

This information message displays the number of ping requests sent by the remote node.

EXTERNAL DEPENDENCIES [(xxxxxxxxxx)]

This information message displays the number of active external dependencies being monitored for the remote node.

STARTJOB REQUESTS [(xxxxxxxxxx)]

This information message displays the number of processed startjob requests for the remote node.


Message Codes

ATC0534I

ATC0535I

QUEUED SENDS [(xxxxxxxxxx)]

This information message displays the number of queued sends for the remote node.

LAST PROCESSED JOB: [ jobname jobnum compcode timestamp]

This information message displays the last successfully processed job from the remote node.

UNRECOGNIZED ENF FUNCTION REQUESTED

ATC0601E

A call was made to the OS/390 Unicenter ENF function routine with invalid parameters. This should not occur during normal operations and represents a processing error. Contact Computer Associates Technical Support for further assistance.

ATC0602E

FUNC=[ func] FAILED RC=[rc] DRC=[drc]

ATC0603I

ATC0604I

An attempt to perform a OS/390 Unicenter ENF function failed. The function name is identified in the message. If the cause of the error is not obvious, contact

Computer Associates technical support for further assistance.

OS/390 UNICENTER ENF SERVICES SUCCESSFULLY INITIALIZED

An attempt to initialize the OS/390 Unicenter ENF services completed successfully. This informational message appears in the beginning of the log when ENF services are initialized.

OS/390 UNICENTER ENF SERVICES HAVE BEEN TERMINATED

ATC0605I

The OS/390 Unicenter ENF services interface has terminated successfully. This informational message appears during normal shutdown of Unicenter AutoSys

Connect Option.

AUTOSYS CONNECT WAITING ON OS/390 UNICENTER ENF SERVICES

This message is displayed following a failed attempt to initialize with the

OS/390 Unicenter ENF services. Unicenter AutoSys Connect Option will attempt on 60-second intervals to reinitialize with the OS/390 Unicenter ENF services.


Message Codes

ATC0611I

=[ eventname]OCCURRED JOB=[jobname] JNO=[jobnumber]

ATC0615I

This message is printed every time an event is received from the OS/390

Unicenter ENF service. This informational message is printed when the DEBUG level is >= 6.

DISCARDING EVENT=[ eventname] JOB=[jobname] JNO=[jobnumber]

This message is printed for each time a Unicenter AutoSys Connect Option has discarded an ENF event as a result of it not matching any job dependency it had recorded. This informational message is printed when the DEBUG level is >= 6.

ATC0616E

EVENT=[ eventname] – AUTOSYS CONNECT IS ABENDING

A non-existent event was returned to Unicenter AutoSys Connect Option. This should not occur during normal operations and represents a processing error.

Contact Computer Associates Technical Support for further assistance.

ATC0620I

JBKEY=[ jobkey] DPKEY[dependencykey]

During normal job processing as Unicenter AutoSys Connect Option receives events from the OS/390 Unicenter ENF component it compares the event jobname against dependency jobnames it has within its dependency array looking for a match. This informational message is printed when the DEBUG level is >= 6.

ATC0621I

DEPENDENCY KEY MATCH DETECTED

Unicenter AutoSys Connect Option was able to successfully locate a match in its dependency array against the event jobname. This DEBUG message prints when the DEBUG level is set to “6”.

ATC0622I

NO DEPENDENCY KEY MATCH DETECTED

Unicenter AutoSys Connect Option was not able to successfully locate a match in its dependency array against the event jobname. This DEBUG message prints when the DEBUG level is set to “6”.


Message Codes

ATC0623I

ATC0624I

ATC0625I

ATC0626I

ATC0627I

EVENT=[ event_name] JOBNAME=[jobname] JOBNO=[job_number]

RC=[ return_code]

This information message is displayed when Unicenter AutoSys Connect receives a Unicenter CA-7 job completion event (L2JOBCMP) from ENF. This informational message is printed when the DEBUG level is >=6.

JOBNAME=[ jobname] CA7 JOBNO=[CA7 job_number] DEP

JOBNO=[ dependency job_number] SCHEDULER=[scheduler_name]

RC=[ return_code]

This information message is displayed when Unicenter AutoSys Connect is processing a Unicenter CA-7 job completion event (L2JOBCMP). This informational message is printed when the DEBUG level is >=6.

UPDATED CA7 JOB NUMBER FOR JOBNAME=[ jobname] CA7 JOBNO=[CA7 job_number] JES JOBNO=[JES job_number]

This information message is displayed when Unicenter AutoSys Connect updates a job dependency with the internal Unicenter CA-7 job number. This update only occurs when using Unicenter CA-7 as your mainframe scheduling system. This informational message is printed when the DEBUG level is >=6.

CONVERTING L2JOBCMP EVENT TO JOBTERM JOBNAME=[ jobname]

JOBNO=[ job_number] RC=[return_code] NODE=[node_name]

This information message is displayed when Unicenter AutoSys Connect converts a Unicenter CA-7 job completion event to a JOBTERM event as a result of force completing the job in Unicenter CA-7. The JOBTERM event will be dispatched to the remote mode once updated. This informational message is printed when the DEBUG level is >=6.

CA7 FORCE COMPLETE DETECTED FOR JOBNAME=[ jobname] CA7

JOBNO=[ CA7 job_number] JES JOBNO=[JES job_number]

This information message is displayed when Unicenter AutoSys Connect detects a force complete has been issued within Unicenter CA-7.


Message Codes

ATC0652E

ATC0652E

ATC0653I

ATC0654I

DEPENDENCY KEY FUNC=DELETE (DD) FAILED

A call to the dependency delete routine completed failed. This should not occur during normal operations and represents a processing error. Contact Computer


ENF HAS TERMINATED - AUTOSYS CONNECT IS SHUTTING DOWN

This message indicates that the product has detected that ENF is not running.

The product shuts down if ENF is not running.

PROCESSING ENF EVENT

This message indicates that Unicenter AutoSys Connect Option has received an event from the OS/390 Unicenter ENF service. This informational message prints when the DEBUG level is >=6.

DEPENDENCY KEY FUNC=DELETE (DD) SUCCESSFUL JOB=[ jobname]

JNO=[ jobnumber]

A call to the dependency delete routine completed successfully. This informational message prints when the DEBUG level is >=6.

ATC0655I

DEPENDENCY

When Unicenter AutoSys Connect Option is comparing the event jobname against the dependency jobname and a match is not found, this message is generated. This informational message prints when the DEBUG level is >=9.

ATC0660I

JOB=[ jobname] FROM NODE=[nodename]

ATC0661E

This information message is printed when Unicenter AutoSys Connect Option receives a startjob request from a Unicenter AutoSys remote node.

FAILED TO PROCESS JOB=[ jobname] FROM NODE=[nodename]

Unicenter AutoSys Connect Option was unable to process the start job request from the noted Unicenter AutoSys remote node. Refer to preceding messages for an indication of the job failure. If the cause of the error is not obvious, contact



Message Codes

ATC0662I

SUCCESSFULLY PROCESSED JOB=[ jobname] JNO=[job_number] FROM

NODE=[ nodename] APPL=[application_name]

Unicenter AutoSys Connect successfully processed the startjob request from the noted Unicenter AutoSys remote node.

ATC0701E

EVENT=[ eventname}

An attempt to process an event posted by the OS/390 Unicenter ENF service is not recognized. This should not occur during normal operations and represents a processing error. Contact Computer Associates Technical Support for further assistance.

SEND FAILED EVENT=[ eventname] TO NODE=[nodename]

ATC0702E

An attempt to send an event to Unicenter AutoSys has failed. This error can occur if the OS/390 Unicenter CCI services are not available. Verify OS/390

Unicenter CCI is running. For more information on the cause of the error see the message ATC0210E.

ATC0703I

EVENT=[ eventname] JOB=[jobname] JNO=[jobnumber] RC=[rc]

ERC=[ erc] TO NODE {nodename}

Unicenter AutoSys Connect Option is sending an event to a remote node. This informational message prints when the DEBUG level is >=6.

ATC0704I

EVENT=[ eventname] TO NODE {nodename}

Unicenter AutoSys Connect Option is sending an event to the remote node. This informational message prints when the DEBUG level is >=6.

ATC0705I

EVENT=[ eventname] JOB=[jobname] JNO=[jobnumber] RC=[rc]

ERC=[ erc] NODE=[nodename]

This message is printed each time Unicenter AutoSys Connect Option has successfully processed an ENF event. This informational message is printed when the DEBUG level is >= 6.

ATC0706I

SEND SUCCESSFUL EVENT=[ eventname] TO NODE {nodename}

Unicenter AutoSys Connect Option has successfully sent an event to the remote node. This informational message prints when the DEBUG level is >=6.


Message Codes

ATC0707I

EVENT=[ eventname] TO EVENT=JOBFAIL JOB=[jobname]

JNO=[ jobnumber] RC=[rc] ERC=[erc] NODE=[nodename]

ATC0708I

Unicenter AutoSys Connect Option has determined the job request should be failed. The current event is reset to JOBFAIL and transmitted to the remote node.

This informational message prints when the DEBUG level is >=6.

PROCESSING DEP WHERE REQ=[requesttype] JOB=[ jobname]

JNO=[ jobnumber] NODE=[nodename]

ATC0710E

Unicenter AutoSys Connect Option has located a matched dependency and is currently processing the job/dependency. This informational message prints when the DEBUG level is >=9.

GETMAIN FAILED FOR QUEUED SEND BUFFER

ATC0711E

ATC0712I

ATC0713I

Unicenter AutoSys Connect Option attempted to obtain storage to queue a failed send buffer. The region size of the Unicenter AutoSys Connect Option task should be increased.

SEND BUFFER HAS BEEN QUEUED SUCCESSFULLY

Unicenter AutoSys Connect Option has queued a failed send buffer successfully due to the remote node not being available.

RESETTING JOBNAME IN SEND STRUCTURE JOB=[ jobname] TO

JOB=[ jobname]

This message occurs when processing the auto-added batch interface job. Before determining whether the job status information needs to be sent back to the remote node, Unicenter AutoSys Connect Option Option will reset the jobname to the original jobname specified by the –j parameter in the Unicenter AutoSys job definition on the remote machine. This DEBUG message prints when the

DEBUG level is set to =>”6”.

WAIT SPECIFIED – SEND EVENT BYPASSED

This message occurs when processing the auto-added batch interface job. The remote machine job definition has specified that the product must wait on the dependent job start and complete. The event status from the batch interface job is discarded if successful. This DEBUG message prints when the DEBUG level is set to =>”6”.


Message Codes

ATC0714I

ATC0715I

ATC0716I

ATC0717I

ATC0718I

DEPENDENCY SKIPPED - SEND WOULD RESULT IN D UPLICATE EVENTS

BEING DISPATCHED

This information message is displayed when Unicenter AutoSys Connect has determined that the processing of the input event status against the current external dependency would result in duplicate event statuses being sent back to

Unicenter AutoSys. This occurs as the result of a Unicenter AutoSys failover having occurred on the distributed platform. Unicenter AutoSys Connect ensures duplicate event statuses for external dependencies are not sent back to both the primary and shadow event processors. This informational message is printed when the DEBUG level is >=6.

ENTERING SECOND STAGE EVENT AGENT COMPARE

This information message is displayed when Unicenter AutoSys Connect is in evaluation depending whether or not the processing of the input event status against the current external dependency should be skipped. This informational message is printed when the DEBUG level is >=6.

SKIP THIS EXTERNAL DEPENDENCY EVENT

This information message is displayed when Unicenter AutoSys Connect determines that the input event status for an external dependency should be skipped. This informational message is printed when the DEBUG level is >=6.

SKIPPING EVENT=[ event_name] NODE=[nodename]

APPL=[ application_name] AGENT IS INACTIVE

This information message is displayed when Unicenter AutoSys Connect determines that the input event status for an external dependency that failed to be sent to the remote node, should be skipped. If this event status was to be queued up and then sent to the remote node after it came back online, it would have resulted in duplicate event statuses being posted within Unicenter AutoSys on the distributed platform.

RE-ROUTING SEND FOR EVENT=[ event_name] NODE=[nodename]

APPL=[ application_name] AGENT IS INACTIVE

This information message is displayed when Unicenter AutoSys Connect determines the input event status should be re-routed to another node for processing. For additional information see the message ATC0719I.


ATC0719I

ATC0720I

ATC0751E

ATC0752E

ATC0753E

ATC0754I

ATC0755I

Message Codes

NODE=[ nodename] APPL=[application_name]

This information message is displayed when Unicenter AutoSys Connect determines that the input event status should be rerouted to another node for processing. For additional information see the message ATC0718I.

SEND WOULD HAVE RESULTED IN DUPLICATE EVENT DATA

NODE=[ nodename] APPL=[application_name] TOOK OVER.

This information message in conjunction with message ATC0717I.

ALLOCATION OF ATCPARM DD FAILED

The product is attempting to read the JCL used as the batch interface to one or more mainframe schedulers, and was unable to dynamically allocate the

ATCPARM DD. Verify the started procedure has an ATCPARM DD statement and that the ATCPARM DD is allocating a valid data set.

JCL MEMBER FIND FAILED

The product is attempting to read the JCL used as the batch interface to one or more mainframe schedulers. A FIND command failed. Verify that the

ATCPARM DD is allocating a valid dataset.

GETMAIN ERROR READING JCL

The product is attempting to read the JCL used as the batch interface to one or more mainframe schedulers. A GETMAIN failed. The region size of the

Unicenter AutoSys Connect Option task should be increased.

ADDING BATCH INTERFACE JCL MEMBERS

Indicates batch JCL members are being read from the Unicenter AutoSys

Connect Option parmlib dataset.

BATCH INTERFACE JCL ADDED MEMBER=[ membername]

Indicates that a batch JCL member has been read from the parmlib dataset and is now resident in memory for use. The membername in the message indicates which JCL member was loaded. This informational message prints when the

DEBUG level is >=2.


Message Codes

ATC0801E

ATC0802E

ATC0803W

ATC0851I

ATC0852E

ATC0853E

INTERNAL READER ALLOCATION FAILED

An attempt to allocate an internal reader to be used to submit jobs to the various mainframe schedulers using a batch interface has failed. This should not occur during normal operations and represents a processing error. Contact Computer


INTERNAL READER OPEN FAILED

An attempt to allocate an internal reader to be used to submit job to the various mainframe schedulers using a batch interface has failed. This should not occur during normal operations and represents a processing error. Contact Computer


COMMAND TEXT WAS TRUNCATED

The command text was truncated while substituting the command text into the skeleton JCL. The product is attempting to submit a scheduler batch interface job for a startjob request. Truncation can occur because the command text was too long. Check the length of the command text.

UNICENTER AUTOSYS CONNECT IS SHUTTING DOWN

This message indicates that the product is shutting down. This will occur when the operator STOP command is issued.

UNRECOGNIZED PARAMETER ENCOUNTERED – [ parmname]

This message indicates that an unrecognized parameter was found. Parameters are specified with the PARM keyword in the started task JCL. The unrecognized parameter is displayed as { parmname} in this message. Check the started task for an invalid parameter.

UNRECOGNIZED DEBUG LEVEL

This message indicates that the option has found an unrecognized DEBUG level specified with the DEBUG parameter. The DEBUG parameters are specified with the PARM keyword in the started task JCL. Valid DEBUG values are 1-9. Check the started task for an invalid DEBUG level specified with the DEBUG parameter.


ATC0855I

ATC0856I

ATC0857I

ATC0858E

ATC0854I

ATC0859E

Message Codes

PROCESSING INPUT PARAMETERS

This information message indicates that the input parameters are being processed. Parameters are specified with the PARM keyword in the started task

JCL.

DEBUG LEVEL SET TO [

DEBUGlevel]

A DEBUG operator command was entered or the DEBUG input control option is been processed. The DEBUG level has been changed to

DEBUGlevel.

FILTERING IS ENABLED FOR ([ schedulername])

This information message indicates that the filter parameter was specified and processed. Filtering has been enabled for the scheduler { schedulername}.

XCCODE PROCESSING IS ENABLED

This information message indicates that the XCCODE parameter was specified and processed. XCCODE processing has been enabled.

OS/390 UNICENTER CCI SERVICES INITIALIZATION FAILED

An attempt to initialize the OS/390 Unicenter CCI services completed failed.

This should not occur during normal operations and could represent a processing error or setup error. Verify the OS/390 Unicenter CCI service is correctly installed and running. If the cause of the error is not obvious, contact


OS/390 UNICENTER ENF SERVICES INITIALIZATION FAILED

An attempt to initialize the OS/390 Unicenter ENF services completed failed.

This should not occur during normal operations and could represent a processing error or setup error. Verify the OS/390 Unicenter ENF service is correctly installed and running. If the cause of the error is not obvious, contact



Message Codes

ATC0860E

ATC0861E

ATC0862E

ATC0863I

ATC0864I

ATC0865I

ATC0867I

OPC PIF INITIALIZATION FAILED

An attempt to initialize OPC PIF services failed. This should not occur during normal operations and could represent a processing error or setup error. Verify

OPC is correctly installed and running. If the cause of the error is not obvious, contact Computer Associates Technical Support for further assistance.

LINK TO MODULE ATCJCLR FAILED

An attempt to link to module ATCJCLR failed. This should not occur during normal operations and could represent a setup error. Verify the ATCJCLR module is available to the started task. If the cause of the error is not obvious, contact Computer Associates Technical Support for further assistance.

LINK TO MODULE ATCXCDR FAILED

An attempt to link to module ATCXCDR failed. This should not occur during normal operations and could represent a setup error. Verify the ATCXCDR module is available to the started task. If the cause of the error is not obvious, contact Computer Associates Technical Support for further assistance.

UNICENTER AUTOSYS CONNECT [ version] INITIALIZATION COMPLETE

This information message indicates that the initialization of the started task is complete.

UNICENTER AUTOSYS CONNECT SHUTDOWN COMPLETE

This information message indicates that the shutdown processing of the started task is complete.

UNICENTER AUTOSYS CONNECT IS NOW AVAILABLE

This information message indicates Unicenter AutoSys Connect Option is available and ready to receive remote node requests.

DEBUG MESSAGES WILL BE WRITTEN TO THE OPERATOR CONSOLE

This information message indicates that the DMSG control option has specified that DEBUG messages produced by the Unicenter AutoSys Connect Option product will be directed to the operator console.


ATC0870I

ATC0871I

ATC0872I

ATC0868I

ATC0869I

ATC0873I

ATC0874I

Message Codes

DEBUG MESSAGES WILL BE WRITTEN TO THE ATCOUT LOGFILE

This information message indicates that the DMSG control option has specified that DEBUG messages produced by the Unicenter AutoSys Connect Option product will be directed to the ATCOUT log file.

DEBUG MESSAGES WILL BE WRITTEN TO SYSLOG

This information message indicates that the DMSG control option has specified that DEBUG messages produced by the Unicenter AutoSys Connect Option product will be directed to SYSLOG.

SEND RETRY LOGIC IS [ ACTIVE | INACTIVE]

This information message indicates whether or not the send retry control option is active or inactive.

USING INPUT OPC SUBSYSTEM NAME=[opc_subsystem_name]

This message is printed which indicates the OPC subsystem when Unicenter

AutoSys Connect has successfully processed the OPC FILTER command.

ATC0705I EVENT PROCESSED MESSAGES WILL BE ISSUED TO THE

OPERATOR CONSOLE

This information message indicates that event-processing message ATC0705I will be written to the operator console.

ATC0705I EVENT PROCESSED MESSAGES WILL BE SUPPRESSED

This information message indicates that event-processing message ATC0705I will be suppressed.

FAILED JOB DEPENDENCIES WILL BE RETAINED AF TER JOB

COMPLETION

This information message is displayed when Unicenter AutoSys Connect has processed the PURGE_FAILED_JOBDEP option and the user elected to retain failed job dependencies to support manual restarts and force completes within the mainframe scheduling system.

Note: This support is only available for Unicenter CA-7.


Message Codes

ATC0875I

ATC0876I

ATC0877I

ATC0878I

FAILED JOB DEPENDENCIES WILL BE DELETED AF TER JOB

COMPLETION

This information message is displayed when Unicenter AutoSys Connect has processed the PURGE_FAILED_JOBDEP option and the user elected to delete failed job dependencies. This is the default behavior of the product. After a job is processed resulting in a JOBFAIL event being dispatched to the remote node, the job dependency is deleted from memory. No further processing will occur with this job dependency.

DETECTED INVALID SCHEDULER NAME

This information message is displayed when Unicenter AutoSys Connect has detected the scheduler name passed on the PURGE_FAILED_JOBDEP control option was invalid. Valid values are the 3 character names used in scheduling a job from the distributed platform (for example; Unicenter CA-7). Please correct the scheduler name in the ATCOPTS control file and restart Unicenter AutoSys

Connect.

EVENT=[ event_name] NOT AVAILABLE

This message is displayed when Unicenter AutoSys Connect initiates its LISTEN function with the ENF component and the event name listed is not available.

This event name is required for Unicenter AutoSys Connect processing.

Check to make sure all data control modules (DCM) required by Unicenter

AutoSys Connect are properly installed in the ENF database. Restart Unicenter

AutoSys Connect once all DCMs are installed and the events (JOBINIT,

STEPTERM, JOBTERM, JOBFAIL, MEMTERM, ENFTERM) are available.

Note, if using the PURGE_FAIL_JOBDEP control option, the Unicenter CA-7

DCM, CAL2DCM0, must be installed. This introduces the Unicenter CA-7 job completion event, L2JOBCMP, into the ENF database.

LISTENING FOR EVENT NAME =[ event_name]

This message is displayed when Unicenter AutoSys Connect initiates its LISTEN function with the ENF component. It displays the event name that Unicenter

AutoSys Connect has registered with the ENF component to listen for. This informational message is printed when the DEBUG level is >=6.


ATC0903E

ATC0904E

ATC0905E

ATC0906E

ATC0879I

ATC0901E

ATC0902E

Message Codes

EVENT LISTEN COUNT = [event_count]

This message is displayed when Unicenter AutoSys Connect initiates its LISTEN function with the ENF component. It displays the total number of events

Unicenter AutoSys Connect is listening for. This informational message is printed when the DEBUG level is >=6.

RECEIVE BUFFER IS EMPTY

Message processing has detected an empty CCI received buffer. The received message is ignored. This should not occur during normal operations and represents a processing error. Contact Computer Associates Technical Support for further assistance.

RECEIVE BUFFER LENGTH IS INVALID

Message processing has detected an empty OS/390 Unicenter CCI received buffer. The received message is ignored. This should not occur during normal operations and represents a processing error. Contact Computer Associates


REQ=START_ JOB (SJ) REQUEST FAILED

A startjob request from a remote node failed. Check the job log to determine the cause of the failure.

REQ=ADD_DEP (AD) REQUEST FAILED

An add dependency (external reference) request from an agent has failed. Check the job log to determine the cause of the failure.

REQ=DEL_DEP (DD) REQUEST FAILED

A delete dependency request from an agent has failed. Check the job log to determine the cause of the failure.

AN INTERNAL ERROR HAS OCCURRED – LOCATE AGENT – REQUEST

ABORTED

An internal error has occurred while attempting to locate a remote node in the

Unicenter AutoSys Connect Option agent array. Contact Computer Associates



Message Codes

ATC0907E

ATC0908I

UNRECOGNIZED REQUEST IGNORED – [ request]

The product has received an unrecognized request, which it is ignoring. This should not occur during normal operations and represents a processing error.

PROCESSING CCI MESSAGE

The option has received a message from an agent. This informational message prints when the DEBUG level is >=3.

ATC0909I

requestcode] RECEIVED FROM NODE=[nodename]

The product has received a request code from an agent on nodename. This information message prints when the DEBUG level is >=5.

ATC0910E

ATC0911I

AN INTERNAL ERROR HAS OCCURRED – ADD AGENT – REQUEST

ABORTED

An internal error has occurred while attempting to add a remote node in the

Unicenter AutoSys Connect Option agent array. Contact Computer Associates


REQ=AUTO_ADD AGENT (4A) BYPASSED – ALREADY PRESENT IN LIST

NODE=[ nodename] APPL=[applicationname]

ATC0912I

ATC0913I

Unicenter AutoSys Connect Option is bypassing the add of the remote node for the request it received. This information message prints when the DEBUG level is >=4.

VERIFY AGENT PRESENCE IN THE LIST NODE=[ nodename]

APPL=[ applicationname]

Unicenter AutoSys Connect Option is proceeding to locate and verify the existence of the remote node in the Unicenter AutoSys Connect Option agent array. This informational message prints when the DEBUG level is >=9.

AGENT NOT PRESENT IN LIST NODE=[ nodename] APPL=[applicationname]

Unicenter AutoSys Connect Option determined the remote node did not exist in the Unicenter AutoSys Connect Option agent array. This information message prints when the DEBUG level is >=9.


ATC0914I

ATC0915E

ATC0916I

ATC1000I

ATC1001E

ATC1002E

ATC1003E

Message Codes

PRIMARYCCISYSID=[ psysid] NODE=[node] APPL=[application_name]

REQ=[ req]

This information message identifies the PRIMARYCCISYSID for the identified request after it has been received from a Unicenter AutoSys remote node. This information message is printed when the DEBUG level is >=4.

BLANK JOBNAME - DISCARDING REQUEST NODE==[ node]


This error message indicates the jobname passed to Unicenter AutoSys Connect from a Unicenter AutoSys remote node was blank. The request is discarded and no further action takes place.

PRIMARYCCISYSID SET TO <NULL> NODE==[ node]

APPL=[ application_name] REQ=[req]

This information message indicates that no PRIMARYCCISYSID was passed by the Unicenter AutoSys remote node and is being set to NULL. This information message is printed when the DEBUG level is >=4.

OPC PIF INTERFACE HAS BEEN TERMINATED

This information message indicates the OPC PIF interface has terminated.

UNRECOGNIZED OPC PIF INTERFACE REQUEST

The product has received an OPC request. The request will be ignored. This request should not occur during normal operations and represents a processing error. The request will be ignored and the job will be accepted for processing.

OPC PIF TERM CALL FAILED PIF RC=[ rc]

A terminate call was made to OPC PIF and the call failed with a return code of

[ rc]. Verify that OPC PIF is installed and available.

OPC PIF INIT CALL FAILED PIF RC=[ rc]

An initialize call was made to the OPC PIF and the call failed with a return code of [ rc]. Verify that OPC PIF is installed and available.


Message Codes

ATC1004I

ATC1006E

ATC1007E

ATC1008E

ATC1009I

ATC1010I

ATC1011E

OPC PIF INTERACE HAS BEEN SUCCESSFULLY INITIALIZED

An initialize call was made to OPC PIF and it completed successfully. This is an informational message.

OPC PIF LIST CALL FAILED PIF RC=[rc]

A list call was made to the OPC PIF and the call failed with a return code of [ rc].

Verify that OPC PIF is installed and available.

OPC PIF INTERFACE PROCESSING ERROR

While processing the output of an OPC PIF list call, the product encountered a processing error. The request will be ignored and the job will be accepted for processing.

OPC PIF SELECT CALL FAILED PIF RC = [rc]

A select call was made to the OPC PIF and the call failed with a return code of

[ rc]. Verify that OPC PIF is installed and available.

OPC PIF LIST RETURNED ENTRIES=[ entrycount]

A list call was made to the OPC PIF and the call returned a list of length

[ entrycount]. This information message is printed when the DEBUG level is >=7.

OPC PIF INITIALIZATION IN PROGRESS

An initialization request to the OPC PIF interface was received and is currently being processed. This is an information message.

OPC REQUIRED DDNAME=[ ddname] IS MISSING

An initialization call was made to the OPC PIF interface and the interface determined one of the three required OPC DDNAMES were missing from the

Unicenter AutoSys Connect started task procedure. Make sure the following

OPC DDNAMES are present:

■

EQQMLOG

■

EQQMLIB

■

EQQYPARM


ATC1014I

ATC1015I

ATC1016I

ATC1012W

ATC1013I

ATC1017E

Message Codes

OPC FILTER PROCESSING DISABLED DUE TO PREVIOUS ERROR

OPC filter processing has been disabled. For more information about why filtering was disabled see the prior error messages. To reactivate filter processing, you must first correct the error, or errors, shut down, and restart

Unicenter AutoSys Connect.

[ filtername] FILTER PROCESSING INVOKED FOR JOB=[jobname]

JNO=[ jobnumber] EVENT [eventname

]

This message is printed when either OPC or ESP filter processing is invoked during normal job operation. This information message is printed when the

DEBUG level is >=6.

ACCEPTED JOB FROM FILTER PROCESSING

This message is printed when the filtering interface has accepted a job for processing. This information message is printed when the DEBUG level is >=6.

DISCARDING JOB EVENT DUE TO FILTER PROCESSING

This message is printed when the filtering interface has discarded a job for processing. This information message is printed when the DEBUG level is >=6.

ACCEPTED JOB DUE TO FILTER PROCESSING FAILURE

This message is printed as a result of filter processing being disabled due to an error in either initializing or using the filter interface. The job being processed will be accepted and monitored by Unicenter AutoSys Connect. This informational message is printed when the DEBUG level is >=6.

OPC PIF COMM BLOCK POINTER IS ZEROES

This message is printed following the OPC init call and the communication block pointer returned zeros. OPC filtering is disabled due to this error. This error means the filtering interface has discarded a job for processing. Verify that OPC

PIF is installed and available. Also, ensure the OPC subsystem name passed on to the FILTER command is valid.


Message Codes

ATC1018E

ATC1019I

ATC1020I

ATC1021I

ATC1051E

ATC1052E

ATC1053E

OPC PIF DATA POINTER IS ZEROES

This message is printed following the OPC list or select calls and the data pointer returned zeros. The request will be ignored and the job will be accepted for processing.

CPOPJBN=[ opc_jobname] CPOPJES=[jes_jobnumber] CPOPST=[opc_status]

This information message is printed following the OPC list or select call. The message outputs the returned job information from OPC. This information message is printed when the DEBUG level is >=9.

OPC LIST PROCESSING JOB=[ jobname]

This information message is printed when the ATCOPC routine is entered for filter (list) processing. This information message is printed when the DEBUG level is >=9.

USING OPC SUBSYSTEM NAME=[ opc_subsystem_name]

This information message is printed when the ATCOPC routine is entered for filter (init) processing.

UNRECOGNIZED SCHEDULER=[ schedulername ] – REQUEST IGNORED

The product is processing a start job request and the scheduler requested is not supported. The start job request is ignored.

UNABLE TO LOCATE JCL MEMBER SCHEDULER=[ schedulername ] –

REQ=START_JOB (SJ) FAILED JOB=[ jobname]

The product is unable to find a batch interface JCL member in the dataset allocated to ATCPARM in the started task during processing of a start job request. The start job request is ignored.

COMMAND TEXT INVALID FOR SCHEDULER=[ schedulername ] –

REQ=START_JOB (SJ) FAILED JOB=[ jobname]

Invalid command text was encountered during the processing of a start job request. The start job request is ignored.


ATC1057E

ATC1058E

ATC1059E

ATC1054E

ATC1055E

ATC1056I

ATC1061I

Message Codes

INTERNAL READER SUBMIT FAILED JOB=[ jobname]

An attempt to submit a batch job to the internal reader during processing of a start job request has failed. The start job request is ignored. Check the job log to determine the cause of the failure.

REQ=ADD_DEP (AD) FAILED JOB=[ jobname]

An attempt to add a dependency for a job during processing of a start job request has failed. The start job request is ignored. Check the job log to determine the cause of the failure.

SUBMITTED JOB=[ batch interfa e jobname] TO START JOB=[jobname]

SCHEDULER=[ schedulername] NODE=[node_name]


This information message is written to the operator console when Unicenter

AutoSys Connect is processing a start job request from a remote node.

INTERNAL ERROR – DATA COUNT IS ZERO JOB=[ jobname]

An error was encountered during processing of a start job request. This should not occur during normal operations and represents a processing error.

NO COMMAND OR COMMAND TEXT FOUND JOB=[ jobname]

An error was encountered during processing of a start job request. This should not occur during normal operations and represents a processing error.

GENERATE COMMAND TEXT FAILED FOR SCHEDULER=[ schedulername]

START FAILED JOB=[ jobname]

An error was encountered during processing of a start job request. This should not occur during normal operations and represents a processing error. Contact


PARSED JOBNAME (-J)=[ jobname]

This message is printed as a result of parsing the -J parameter passed by

Unicenter AutoSys. This information message is printed when the DEBUG level is >=9.


Message Codes

ATC1062I

ATC1063I

ATC1100E

ATC1101I

ATC1102I

ATC1104I

ATC1105I

ATC1106I

PARSED COMMAND (-C)=[ command]

This message is printed as a result of parsing the -C parameter passed by


PARSED CMDPARM (-P)=[ command parameter]

This message is printed as a result of parsing the -P parameter passed by


XCCODE PROCESSING FAILED – NO ENTRIES

An attempt to perform XCCODE processing has failed because there are no

XCCODE conditions specified.

XCCODE SETTING JOBFAIL (JOBSTEP) JOB=[ jobname]

The status of this job is being set to JOBFAIL because of an XCCODE job step condition. This information message prints when the DEBUG level is >=3.

XCCODE SETTING JOBFAIL (JOB) JOB=[ jobname]

The status of this job is being set to JOBFAIL because of an XCCODE job condition. This information message prints when the DEBUG level is >=3.

XCCODE ENTRY BEST MATCH – COMPARING RC

An XCCODE condition entry that matches the current job being processed has been found. The return code of the step or job is compared against the XCCODE condition entry. This information message prints when the DEBUG level is >=3.

XCCODE SETTING SUCCESS – JOB CONDITION

The status of this job is being set to SUCCESS because of an XCCODE jobstep condition. This information message prints when the DEBUG level is >=3.

JOBNAME STEPNAME COMP RC

This information message is the heading output line for the XCDLIST operator command.


ATC1107I

ATC1108I

ATC1109I

ATC1110I

ATC1111I

ATC1112I

ATC1113I

ATC1114I

Message Codes

[ jobname] [stepname] [comp] [rc]

This information message is the detail output line for the XCDLIST operator command.

NO XCCODE ENTRIES PRESENT

This information message is displayed by the XCDLIST operator command when no XCDLIST entries are present.

XCCODE SETTING JOBTERM SUCCESS JOB=[ jobname]

The status of this job is being set to SUCCESS because of an XCCODE job condition. This information message prints when the DEBUG level is >=3.

JOBNAME JOBNUM NODE [ applicationname] TYPE EVENT

This information message is the heading output line for the DEPLIST operator command.

[ jobname] [jobnum] [node] [applicationname] [type] [event]

This information message is the detail output line for the DEPLIST operator command.

JOB DEPENDENCY LIST IS EMPTY

This information message is displayed by the DEPLIST operator command when no dependency entries are present.

ID NODE STATUS APPLICATION NAME

This information message is the heading output line for the AGTLIST operator command.

[ id] [node] [status] [applicationname]

This information message is the detail output line for the AGTLIST operator command.


Message Codes

ATC1115I

ATC1116I

ATC1117I

ATC1118I

ATC1121I

ATC1122I

ATC1120W

AGENT LIST IS EMPTY

This information message is displayed by the AGTLIST operator command when no remote node entries are present.

REMOTE APPLICATIONS USING UNICENTER AUTOSYS CONNECT

This information message prints when using the STATUS or STATUS(CCI) operator command. For additional information, see to the messages ATC1113I and ATC1114I.

COMPARING DEP=[ dependencyname] AGAINST MASK=[maskname]

This message shows the comparison being done when using the mask functionality of the DEPLIST operator command. Information message prints when using the STATUS or STATUS(CCI) operator command. This informational message prints when the DEBUG level is >=9.

TOTAL DEPENDENCIES [( xxxxxxxxxxx)]


STATUS or STATUS(DEP) operator command indicating the total number of dependencies Unicenter AutoSys Connect Option is processing.

QUEUED SEND LOGIC IS NOT ACTIVE

This warning message is produced when attempting to use the QSDFREE or

QSDLIST commands and queued send logic has not been activated. The command is ignored and no further processing takes place.

QUEUED SEND LIST IS EMPTY

This information message is displayed by any of the QSD* operator commands when no queued send entries are present.

EVENT JOBNAME JOBNUM NODE APPLICATION DATE TIME

This information message is the heading output line for the QSDLIST operator command.


ATC1123I

ATC1124I

ATC1131I

ATC1132I

ATC1134I

ATC1133E

Message Codes

[ event] [jobname] [jobnum] [node] [application] [date] [time]

This information message is the detail output line for the QSDLIST operator command.

TOTAL QUEUED SEND ENTRIES [( xxxxxxxxxxx)]


QSDLIST operator command indicating the total number of queued send entries

Unicenter AutoSys Connect Option is processing.

ATTEMPTING TO LOCATE QUEUED BUFFERS FOR NODE=[ nodename]

ID=[ id] APPL=[applicationname]

This information message is produced when a remote node reestablishes communication with Unicenter AutoSys Connect Option and queued send retry logic is active. This information message prints when the DEBUG level is >=5.

QUEUED SEND SUCCESSFUL NODE=[ nodename] APPL=[applicationname]

JOB=[ jobname]

This information message is produced when Unicenter AutoSys Connect Option successfully sends a queue send to a remote node.

QUEUED SEND FAILED NODE=[ nodename] APPL=[applicationname]

JOB=[ jobname]

This information message is produced when Unicenter AutoSys Connect Option failed to send a queue send to a remote node. For more information see the message ATC0210E, previously shown.

QUEUED BUFFER LOCATED FOR NODE=[ nodename]


This message is produced when Unicenter AutoSys Connect Option is processing the queued send list attempting to locate send buffers for the remote node. This information message prints when the DEBUG level is >=5.


Message Codes

ATC1135I

ATC1136I

ATC1137I

ATC1138I

ATC1139I

ATC1141I

ATC1142I

SENDING QUEUED BUFFER NODE=[ nodename] APPL=[applicationname]

This message is produced when Unicenter AutoSys Connect Option is processing the queued send list when attempting to transmit the send buffer to the remote node. This information message prints when the DEBUG level is >=5.

FOR EVENT JOB=[jobname] JNO=[ jobnumber]

This message is a continuation of message ATC1135I. This information message prints when the DEBUG level is >=5.

QUEUED BUFFER RELEASED

This information message is produced when queued send buffers are freed after the buffers are transmitted to the remote node. This information message prints when the DEBUG level is >=5.

QUEUED SEND BUFFERS RELEASED FOR NODE=[ nodename] ID=[id]


This information message is produced when queued send buffers are freed through execution of the QSDFREE operator command.

NO QUEUED SEND BUFFERS FOR NODE=[ nodename] ID=[id]


This information message is produced when no queued send buffers are freed through execution of the QSDFREE operator command.

QUEUED SEND BYPASSED

This information message is printed when Unicenter AutoSys Connect determines the queued job status is not applicable for the target node. This information message is printed when the DEBUG level is >=6.

RE-ROUTING QUEUED SEND FOR EVENT=[ event_name]

This information message is printed when Unicenter AutoSys Connect determines the queued job status should be rerouted. The job status had been queued because of a failed send.


ATC1143I

ATC1151E

ATC1152E

ATC1153E

ATC1154E

ATC1155E

Message Codes

NODE=[ node1] APPL=[application_name1]

This information message is printed in conjunction with message ATC1142I.

ALLOCATION OF ATCPARM DD FAILED

An attempt to read the XCCODE member used to specify XCCODE conditions has failed, and the product was unable to dynamically allocate the ATCPARM

DD. Verify the started procedure has an ATCPARM DD statement and the

ATCPARM DD is allocating a valid data set.

UNABLE TO LOCATE XCCODE MEMBER

An attempt was made to read the XCCODE member used to specify XCCODE conditions. A FIND command failed. Verify that the XCCODE member appears in the dataset allocated by the ATCPARM DD in the started task JCL.

FIND FOR XCCODE MEMBER FAILED

An attempt was made to read the XCCODE member used to specify XCCODE conditions. A FIND command failed. Verify that the XCCODE member appears in the dataset allocated by the ATCPARM DD in the started task JCL.

GETMAIN ERROR READING XCCODE MEMBER

An attempt to read the XCCODE member into working storage because a getmain call failed. The region size of the Unicenter AutoSys Connect Option task should be increased.

XCCODE JOB KEYWORD NOT FOUND

An attempt was made to parse the XCCODE member used to extract the

XCCODE conditions, but XCCODE parsing did not find a job keyword.

XCCODE parsing expects the job keyword to be the first keyword for an

XCCODE condition. Verify that all XCCODE conditions contain a job keyword and that each condition is contained in only one line of the XCCODE member.


Message Codes

ATC1156E

ATC1157E

ATC1158E

ATC1159E

ATC1160E

XCCODE JOBNAME NOT FOUND

An attempt to parse the XCCODE member used to extract the XCCODE conditions was made, but XCCODE parsing did not find a jobname. XCCODE parsing expects the jobname to follow the job keyword. Verify that all XCCODE conditions contain a jobname and that each condition is contained in only one line of the XCCODE member.

XCCODE STEP KEYWORD NOT FOUND

An attempt to parse the XCCODE member used to extract the XCCODE conditions was made, but XCCODE parsing did not find a step keyword. Verify the XCCODE conditions that are specified in the XCCODE member.

XCCODE STEPNAME NOT FOUND

An attempt to parse the XCCODE member used to extract the XCCODE conditions was made, but XCCODE parsing did not find a stepname value.

XCCODE parsing expects the stepname value to follow the step keyword. Verify that all XCCODE conditions contain a stepname and that each condition is contained in only one line of the XCCODE member.

XCCODE RC KEYWORD NOT FOUND

An attempt to parse the XCCODE member used to extract the XCCODE conditions was made, but XCCODE parsing did not find an RC keyword.

XCCODE parsing expects the RC keyword to follow the jobname or stepname value in an XCCODE condition. Verify that all XCCODE conditions contain an

RC keyword and that each condition is contained in only one line of the

XCCODE member.

XCCODE OPERATOR NOT FOUND

An attempt to parse the XCCODE member used to extract the XCCODE conditions was made, but XCCODE parsing did not find an operator. XCCODE parsing expects the operator to follow the RC keyword in an XCCODE condition.

Verify that all XCCODE conditions contain operators and that each condition is contained in only one line of the XCCODE member.


ATC1161E

ATC1162E

ATC1163I

ATC1164I

ATC1170I

ATC1171I

Message Codes

XCCODE VALUE NOT FOUND

An attempt to parse the XCCODE member used to extract the XCCODE conditions was made, but XCCODE parsing did not find a value. XCCODE parsing expects the value to follow the operator in an XCCODE condition. Verify that all XCCODE conditions contain values and that each condition is contained in only one line of the XCCODE member.

XCCODE CONDITION NOT ADDED - GETMAIN ERROR

An attempt to readd an XCCODE condition to working storage failed because a getmain call failed. The region size of the Unicenter AutoSys Connect Option task should be increased.

ADDING XCCODE ENTRIES

Indicates an XCCODE condition was read from parmlib member XCCODE and is now resident in memory for XCCODE evaluation.

JOB=[ jobname] STEP=[stepname] OP=[operator] RC=[rc]

This is a continuation of message ATC1163I. The message prints the detail output of each XCCODE entry. This information message prints when the

DEBUG level is >=2.

ATTEMPTING TO LOCATE XCCODE BEST MATCH

This information message is printed when Unicenter AutoSys Connect enters

XCCODE processing. This information message is printed when the DEBUG level is >=3.

SKIPPING XCCODE PROCESSING FOR JOBINIT

This information message is printed when Unicenter AutoSys Connect is processing JOBINIT and XCCODE is active. XCCODE processing is not applied to JOBINIT events and is skipped. This information message is printed when the

DEBUG level is >=3.


Message Codes

ATC1172I

ATC1173I

ATC1174I

ATC1175I

ATC1176I

XCCODE BEST MATCH DOES NOT APPLY

This information message is printed when Unicenter AutoSys Connect has applied the best match XCCODE entry to either the STEPTERM or JOBTERM event and is not setting SUCCESS. This information message is printed when the

DEBUG level is >=3.

NO XCCODE BEST MATCH ENTRY DETECTED

This information message is printed when Unicenter AutoSys Connect has applied all XCCODE entries to the specific job event and has not located a match.

This information message is printed when the DEBUG level is >=3.

XCCODE PROCESSING BYPASSED FOR BATCH INTERFACE JOB EVENT

This information message is printed when Unicenter AutoSys Connect is invoked for XCCODE processing and has determined the event being processed is for its batch interface job. XCCODE processing is not applied to any batch interface job events. This information message is printed when the DEBUG level is >=3.

[jobname] [stepname] [operator] [rc]

This information message is printed when Unicenter AutoSys Connect is invoked for XCCODE processing. The message prints the contents of the

XCCODE entry being processed. This information message is printed when the

DEBUG level is >=3.

XCCODE PROCESSING BYPASSED FOR JOBTERM - JO BFAIL EVENT HAS

BEEN SET

This information message is printed when Unicenter AutoSys Connect is invoked for XCCODE during JOBTERM processing. The message prints when

JOBFAIL has already been set. This information message is printed when the

DEBUG level is >=3.


ATC1177I

ATC1178I

ATC1201W

ATC1204E

ATC1205E

Message Codes

XCCODE PROCESSING BYPASSED FOR STEPTERM - JO BFAIL EVENT HAS

BEEN SET

This information message is printed when Unicenter AutoSys Connect is invoked for XCCODE during STEPTERM processing. The message prints when

JOBFAIL has already been set. This information message is printed when the

DEBUG level is >=3.

NO XCCODE BEST MATCH FOUND

This information message is printed when Unicenter AutoSys Connect has applied all XCCODE entries to the specific job event and has not located a match.

This information message is printed when the DEBUG level is >=3.

XCCODE NOT ENABLED – REFRESH IGNORED

An operator REFRESH command was issued for XCCODE, but the option is not enabled. Refresh processing is terminated.

REFRESH COMMAND FAILED

An operator REFRESH command has been issued. The command operation has failed. For more information on why the command failed, see the preceding messages in the operator console.

INVALID DEPENDENCY MASK SPECIFIED

An invalid dependency mask was specified as part of the DEPLIST operator command. Review the mask specification and reenter the operator command.


Appendix

C

Initiating Jobs on a Mainframe

The following tutorial guides you through the procedure necessary to enable

Unicenter AutoSys to initiate jobs on a mainframe system using Unicenter

AutoSys Connect Option. The tutorial's scenario involves the following systems:

AutoSys Machine

Hostname—local_host

Operating System—UNIX

Software Installed—CCI, AutoSys 3.5.1

Parameter Configuration:

AUTOSYS=/opt/autotree/tst/autosys

AUTUSER=/opt/autotree/tst/autouser

AUTOSERV=ACE

Mainframe

Hostname—remote_host

Operating System—OS/390

Software Installed—ENF, Connect

The tutorial proceeds in the following order, and should be performed in its entirety:

2. Start or restart CCI.

3. Enable Unicenter AutoSys cross-platform scheduling support.

4. Install client license key for mainframe (OS/390) machine.

5. Define the option machine to Unicenter AutoSys.

6. Submit command jobs to mainframe.

Initiating Jobs on a Mainframe C–1

Configure CCI

Configure CCI

To configure CCI:

1. Log in as root (to edit the CCI configuration files).

2. Configure the CCI remote daemon by opening the ccirmtd.prf file. The file is found in the following location:

$CAIGLBL0000/cci/config/local_host/ccirmtd.prf

Enter the following values for local and remote parameters:

LOCAL = local_host local_host 32768 startup

REMOTE = remote_host cci_system_id 32768 startup port=7000

Note: For detailed syntax information regarding the ccirmtd.prf file, see ccirmtd.prf in the appendix “Introducing CCI” in the Unicenter AutoSys Job

Management for UNIX Installation Guide.

Start or Restart CCI

You must start or restart CCI to enable the new settings.

■

To start CCI if Unicenter is installed: unistart cci

■

To start CCI if Unicenter is not installed:

$CAIGLBL0000/cci/scripts/CCISA_rc

■

To stop CCI if Unicenter is installed: unishutdown cci

■

To stop CCI if Unicenter is not installed:

$CAIGLBL0000/cci/scripts/CCISA_cshut

C–2 Installation and Administrator Guide

Enable Cross-Platform Scheduling Support

Enable Cross-Platform Scheduling Support

To enable cross-platform scheduling support (that is, to configure the Unicenter

AutoSys machine to fork a process to handle jobs and enable external dependencies to Unicenter AutoSys Connect Option), proceed as follows:

1. Set the AutoSysAgentSupport parameter.

To run jobs directly on an Agent, enable Agent job support by setting the following parameter in the instance configuration file

($AUTOUSER/config.$AUTOSERV):

AutoSysAgentSupport=1

2. Create the config.EXTERNAL file.

To enable cross-platform dependencies, create a file named config.EXTERNAL in the $AUTOUSER directory and add the following entry:

RMT:CNCT=remote_host

Note: For further information on creating the config.EXTERNAL file, see

Create the config.EXTERNAL File in the appendix “Integrating with the

Mainframe and Unicenter AutoSys Agents for AS/400 and OpenVMS” in the

Unicenter AutoSys Job Management for UNIX User Guide.

Install Client License Key for the Mainframe

Install the client license key for the OS/390 machine in the Unicenter AutoSys database as follows: gatekeeper Return

Utility to Add/Delete or Print KEYs.

Add (A) or Delete (D) or Print (P) ? a

KEY Type:[(c)lient,(s)erver,(t)ime,(x)pert ]: c remote_host

Hostid:

KEY: IIJJKKLLMMNNOOPP

*****New Key ADDED!*****

KEY Type: [(c)lient,(s)erver,(t)ime,(x)pert ]: Return


Define the Machine

Define the Machine

Define the machine that is running Unicenter AutoSys Connect Option (OS/390) to Unicenter AutoSys through the JIL command line utility. At the operating system command prompt, enter: jil insert_machine: remote_host job_type: c

Note: For detailed syntax information, see Defining Agent Machines to

Unicenter AutoSys in the appendix “Integrating with the Mainframe and

Unicenter AutoSys Agents for AS/400 and OpenVMS” in the Unicenter AutoSys

Job Management for UNIX User Guide.



Submit Command Jobs to the Mainframe

The auto_cnct command is used in this section to define command jobs. The following is an explanation of the command’s syntax.

Syntax

-a node

-s scheduler code auto_cnct –a node –s scheduler code [-j jobname –c command

–p 'parameters' -d] where:

Specifies the hostname of the machine running the Unicenter AutoSys Connect

Option.

Specifies the scheduler the command is being issued to (see the following table.)

Code Scheduler

OPC OPC/ESA

ESP ESP

CTM Control-M

-j jobname

-c command

-p 'parameters'

-d

Specifies the jobname to be monitored for status.

Specifies the command word, such as ADD or RUN.

Specifies the command parameters for the job.

Specifies to wait for the initiation and termination of the job.



Define Command Jobs to Run on the Mainframe

Define command jobs to run on the OS/390 machine as follows:

CA-7

CA-Jobtrac

Control-M

To submit a job to Unicenter CA-7, enter: insert_job: connect_job1 command: auto_cnct –aremote_host –jASYS7001 –cRUN –sCA7 –d machine: remote_host date_conditions: 1 days_of_week: all start_mins: 25

To submit a job to Unicenter CA-Jobtrac, enter: insert_job: connect_job3 command: auto_cnct –aremote_host –jFCHUA001 –cADD –sJBT –d machine: remote_host

To submit a job to Control-M, enter: insert_job: connect_job2 command: auto_cnct –aremote_host –sCTM -jTESTJOB –cORDERJOB

-p'CM.MTC.JIX.SCHEDULE,TEST123' –d machine: remote_host



Define a Job that Depends on a Job Scheduled on the Mainframe

Define a job that depends on a job defined on a supported OS/390 scheduler, such as Unicenter CA-7 or Unicenter CA-Jobtrac:

1. Define two jobs in the OS/390 scheduling system (remote_host). Name the jobs JB5MINS and JB5HRS.

2. Define a job that depends on the job JB5MINS insert_job: test_dep1 command: sleep 100 condition: success(JB5MINS^RMT) machine: local_host insert_job: test_dep2 command: print_a_message.sh condition: success(JB5HRS^RMT) machine: local_host

3. You can also define jobs as a combination of both command jobs and external dependencies.

■

To submit a job to CA-7, enter: connect_job4 command: auto_cnct -aremote_host -jASYS7002 –cRUN -sCA7 –d remote_host success(JB5HRS^RMT)

■

To submit a job to CA-Jobtrac, enter: insert_job: connect_job5 command: auto_cnct –aremote_host –jFCHUA002 –cADD –sJBT –d remote_host success(JB5MINS^RMT)



Working with Mainframe Scheduling Packages

The mainframe scheduling packages use different methods to schedule jobs. This section explains how Unicenter AutoSys Connect Option accommodates these methods and shows examples of how commands are constructed for the different scheduling packages. The mainframe scheduling packages discussed are:

■

CA-7

■

CA-Scheduler

■

CA-Jobtrac

■

OPC

■

ESP

■

Control-M

CA-7

Example 1

For Unicenter CA-7, Unicenter AutoSys Connect Option submits batch interface job control member ATCJCA7 executing U7SVC when it schedules a job.

The Unicenter AutoSys job is defined as follows: auto_cnct –a remote_host –s CA7 -j TESTJOB –c DEMAND

–p 'SCHID=xxx' -d

Unicenter AutoSys Connect Option constructs the following command and passes it to Unicenter CA-7 to add the job TESTJOB to the schedule:

//ATCJCA7 JOB ,CONNECT-ATCJCA7,

// MSGLEVEL=(1,1),

// MSGCLASS=0,

// CLASS=A

//*

//STEP1 EXEC PGM=U7SVC

//STEPLIB DD DISP=SHR,DSN=*CA-7*.LOADLIB

//CA7DATA DD *

/LOGON MASTER

DEMAND,JOB=TESTJOB,SCHID=xxx

/LOGOFF

/*

//



Example 2

The Unicenter AutoSys job is defined as follows: auto_cnct –a remote_host –s CA7 -j TESTJOB –c run -d

Unicenter AutoSys Connect Option constructs the following command and passes it to Unicenter CA-7 to post the job TESTJOB to the schedule:

//ATCJCA7 JOB ,CONNECT-ATCJCA7,

// MSGLEVEL=(1,1),

// MSGCLASS=0,

// CLASS=A

//*

//STEP1 EXEC PGM=U7SVC

//STEPLIB DD DISP=SHR,DSN=*CA-7*.LOADLIB

//CA7DATA DD *

/LOGON MASTER

RUN,JOB=TESTJOB

/LOGOFF

/*

//

CA-Scheduler

Example

For Unicenter CA-Scheduler, Unicenter AutoSys Connect Option submits batch interface job control member ATCJCAS executing CAJUCMD0 when it schedules a job.

The Unicenter AutoSys job is defined as follows: auto_cnct –a remote_host –s CAS -j TESTJOB –c RUN

–p 'SCHEDULE=AACD0022' -d

Unicenter AutoSys Connect Option constructs the following command and passes it to Unicenter CA-Scheduler to add the job TESTJOB to the schedule:

//ATCJCAS JOB ,CONNECT-ATCJCAS,

// MSGLEVEL=(1,1),

// MSGCLASS=0,

// CLASS=A

//*

//STEP01 EXEC PGM=CAJUCMD0,REGION=4096K

//STEPLIB DD DISP=SHR,DSN=*CA-SCHEDULER*.LOADLIB


//ISPPROF DD DISP=SHR,DSN=*IPFX*.ISPF.ISPPROF

//SYSIN DD *

SC RUN JOB NAME=TESTJOB,SCHEDULE=AACD0022

/*

//



CA-Jobtrac

Example

For Unicenter CA-Jobtrac, Unicenter AutoSys Connect Option submits interface job control member ATCJJBT executing GJTRABTR when it schedules a job.

The Unicenter AutoSys job is defined as follows: auto_cnct –a remote_host –s JBT -j TESTJOB –c RUN

Unicenter AutoSys Connect Option constructs the following command and passes it to Unicenter CA-Jobtrac to add the job TESTJOB to the schedule:

//ATCJJBT JOB ,CONNECT-ATCJJBT,

// MSGLEVEL=(1,1),

// MSGCLASS=0,

// CLASS=A

//*

//STEP1 EXEC PGM=GJTRABTR

//STEPLIB DD DISP=SHR,DSN=*JOBTRAC*.LOADLIB

//JOBTRACB DD DSN=*JOBTRAC-CHKPT*,DISP=SHR


//SYSIN DD *

RUN=TESTJOB

/*

//

OPC

Example

For OPC, Unicenter AutoSys Connect Option submits batch interface job control member ATCJOPC executing EQQEVPGM when it schedules a job.

The Unicenter AutoSys job is defined as follows: auto_cnct –a remote_host –s OPC –j TESTJOB –c BATCH

-p 'STATUS(C), WSNAME(ABCD), ADID(TEST),OPNUM(3),SUBSYS)MSTR)'

Unicenter AutoSys Connect Option constructs the following command and passes it to OPC to add the job TESTJOB to the schedule:

//ATCJOPC JOB ,CONNECT-ATCJOPC,

// MSGLEVEL=(1,1),

// MSGCLASS=0,

// CLASS=A

//*

//STEP1 EXEC PGM=EQQEVPGM

//STEPLIB DD DISP=SHR,DSN=*OPC LOADLIB*

//EQQMLIB DD DISP=SHR,DSN=*OPC LIB DSN*

//EQQYPARM DD DISP=SHR,DSN=*OPC PARM DSN*

//EQQMLOG DD SYSOUT=*

//SYSIN DD *

OPSTAT J(TESTJOB) STATUS(C) WSNAME(ABCD) ADID(TEST) OPNUM(3) SUBSYS(MSTR)

/*

//



ESP

Example 1

Example 2

For ESP, Unicenter AutoSys Connect Option submits batch interface job control member ATCJESP when it schedules a job.

The Unicenter AutoSys job is defined as follows: auto_cnct –a remote_host –s ESP -j TESTJOB -c APPLJOB

–p 'COMPLETE APPL(XYZ)' -d

Unicenter AutoSys Connect Option constructs the following command and passes it to ESP to add the job TESTJOB to the schedule:

//ATCJESP JOB ,CONNECT-ATCJESP,

// MSGLEVEL=(1,1),

// MSGCLASS=0,

// CLASS=A

//*

//STEP1 EXEC PROC=ESPROC

//SYSIN DD *

APPLJOB TESTJOB COMPLETE APPL(XYZ)

/*

//

The Unicenter AutoSys job is defined as follows: auto_cnct –a remote_host –s ESP -j TESTJOB –c TRIGGER

–p 'P=DVLP,U1(JOB1) U2(DD) U3(LL) U4(CC)' -d

Unicenter AutoSys Connect Option constructs the following command and passes it to ESP to add the job TESTJOB to the schedule:

//ATCJESP JOB ,CONNECT-ATCJESP,

// MSGLEVEL=(1,1),

// MSGCLASS=0,

// CLASS=A

//*

//STEP1 EXEC PROC=ESPROC

//SYSIN DD *

TRIGGER ADD DVLP.TESTJOB U1(JOB1) U2(DD) U3(LL) U4(CC)

/*

//



Control-M

Example

For Control-M, Unicenter AutoSys Connect Option submits batch interface job control member ATCJCTM when it schedules a job.

The Unicenter AutoSys job is defined as follows: auto_cnct –a remote_host –s CTM -j TESTJOB –c ORDERJOB –p 'CTM.TABLE.LIB,CTMTAB'-d

Unicenter AutoSys Connect Option constructs the following command and passes it to Control-M to add the job TESTJOB to the schedule:

//ATCJCTM JOB ,CONNECT-ATCJCTM,

// MSGLEVEL=(1,1),

// MSGCLASS=0,

// CLASS=A

//*

//STEP1 EXEC PROC=CTMPROC

//SYSIN DD *

TRACE OFF

MAXCOMMAND 99999999

CALLMEM ORDERJOB CTM.TABLE.LIB CTMTAB TESTJOB NULL FORCE

/*

//

Zeke

For Zeke, Unicenter AutoSys Connect Option submits batch interface job control member ATCJZEK when it schedules a job.

Example

The Unicenter AutoSys job is defined as follows: auto_cnct –a remote_host –s ZEK –j TESTJOB –c ZADD –p REBUILD –d

Unicenter AutoSys Connect Option constructs the following command and passes it to Zeke to add the job TESTJOB to the schedule.

//ATCJZEK JOB ,CONNECT-ATCJZEK,

// MSGLEVEL=(1,1),

// MSGCLASS=0,

// CLASS=A

//*

//STEP1 EXEC PGM=ZEKESET,PARM='SUBSYS=*SUBS*'

//STEPLIB DD DISP=SHR,DSN=*CPFX*.LOADLIB

//SYSPRINT DD SYSOUT=A

//SYSIN DD *

SET ZCOM ‘ZADD JOB TESTJOB REBUILD’

/*

//


Index

A

activating ESP filter, 3-7 activating OPC filter, 3-6 add agent, 4-5 add dependency, 4-5

AGTLIST remote machine validation, 3-25

ASPING, 3-24 remote machine validation, 3-25

ATCOPTS, 3-2 auto_cnct, C-5 syntax, C-5

AutoSys Connect

AutoSys failover, 4-10

CA-7, C-8

CA-Jobtrac, C-10

CA-Scheduler, C-9

Control-M, C-12 define the machine, C-4

ESP, C-11 failover, 4-10 failover support, 4-11 message processing, 4-1 message types, 4-2

OPC, C-10 operation, 4-1 startup, 4-7 using, 3-1 welcome, 1-1

Zeke, C-12

AutoSysAgentSupport parameter, C-3

B

batch interface, 2-2

C

CA Jobtrac, C-10

CA Scheduler, C-9

CA-7, C-8

CAICCI startup options, 2-3 verifying, 2-4

CAIENF, 2-2

CCI ccirmtd.prf file, C-2 configure, C-2 remote daemon, C-2 start or restart, C-2 ccirmtd.prf file, C-2 local parameter, C-2 remote parameter, C-2 client license key, C-3 command jobs auto_cnct, C-5 configuration file, C-3

Index–1

Control-M, C-12 cross-platform dependencies enable, C-3

D

DEBUG controlling output, 3-5 level specifying, 3-3 define the machine, C-4 dependencies deleting orphans, 3-22 displaying, 3-20 direct job submit, 3-26 displaying dependencies, 3-20

PRIMARYCCISYSID, 3-17 remote nodes, 3-16

XCCODE entries, 3-24

E

ESP, C-11

F

failover support, 4-11 features and enhancements, 1-2

FILTER option, 3-5, 3-6, 3-9, 3-14

Force Job Completions in CA-7, 3-8

H

hardware requirements, 1-4

Index–2 Installation and Administrator Guide

I

initiating jobs on a mainframe, C-1 installation client license key, C-3 mainframe, 2-1 upgrading from 2.3 or 2.4 to 2.4.1, 2-5 upgrading from 2.3 or 2.4 to 2.4.1 approach #1, 2-5 approach #2, 2-6 verifying, 2-4 without SMP/E, 2-1

J

JCL install, 2-1

JOB syntax, 3-11

JOBINIT, 4-8

JOBSTEP syntax, 3-12

JOBTERM, 4-9

L

libraries, 2-1 license key, C-3

M

mainframe installation, 2-1 requirements, 1-4

Manual Job Restarts in CA-7, 3-8

MAXUSER value, 1-5

member names syntax, 2-2 message codes, B-1 syntax, B-1 message processing, 4-1 message types, 4-2

O

obtaining environment status, 3-14

OPC, 1-5, C-10 monitoring, 3-5, 3-6, 3-9, 3-14 operator commands, A-1 options activating ESP filter, 3-7 activating OPC filter, 3-6 deleting orphan dependencies, 3-22 displaying PRIMARYCCISYSID, 3-17 displaying remote nodes, 3-16 modifying remote nodes statuses, 3-18 suppressing ATC0705I message, 3-7 orphan dependencies deleting, 3-22

P

PING, 4-6

PRIMARYCCISYSID displaying, 3-17

PURGE_FAILED_JOBDEP, 3-8

R

refreshing extrernal dependencies, 3-21 remote machine validation, 3-25 remote nodes displaying, 3-16 modifying statuses, 3-18 removing queued sends, 3-23 requirements

CSA space, 1-5 hardware, 1-4

LNKLST, 1-5 mainframe, 1-4 operating system, 1-5 software, 1-4 target systems, 1-4

S

schedule identifier, 2-2 scheduler JCL, 2-2 scheduling packages, C-8 software requirements, 1-4

SRETRY activating, 3-9 removing queued sends, 3-23 viewing queued sends, 3-23 started task, A-1

STARTJOB, 4-2 startup options, 3-1, 3-2

Connect-monitored jobs, 3-10

OPC only, 3-5, 3-6, 3-9, 3-14 setting Debug, 3-3

STATUS remote machine validation, 3-25

STEPTERM, 4-8 support technical, 1-2, 1-6 suppressing ATC0705I message, 3-7

Index–3

T

technical support, 1-2, 1-6 technical support license key, C-3 troubleshooting, B-1 troubleshooting message codes, B-1 tutorial, C-1

U

Unicenter AutoSys Broker add agent, 4-5 add dependency, 4-5

PING, 4-6

STARTJOB, 4-2 using AutoSys Connect, 3-1

X

XCCODE displaying entries, 3-24

JOBINIT, 4-8

JOBTERM, 4-9 member activating, 3-13

JOB, 3-11

JOBSTEP, 3-12 setting up, 3-10 process flow, 4-7, 4-8

STEPTERM, 4-8

Z

Zeke, C-12

Index–4 Installation and Administrator Guide

CA 2.4.1 Unicenter AutoSys Job Management Connect Option Installation and Administration Guide

Assistant Bot

Unicenter

AutoSys

Job

Management Connect Option

Installation and Administration Guide

Contents

Chapter 1: Welcome to Unicenter AutoSys Connect Option

Chapter 2: Mainframe Installation

Chapter 3: Using Unicenter AutoSys Connect Option

Chapter 4: Operation

Appendix A: Operator Commands

Appendix B: Troubleshooting

Appendix C: Initiating Jobs on a Mainframe

Welcome to Unicenter AutoSys

Connect Option

Features and Enhancements

Hardware and Software Requirements

Minimum Requirements

Operating System Requirements

CSA Space Requirements

LNKLST Concatenation

Dispatching Priority

Technical Support

Mainframe Installation

Installing Without SMP/E

Verifying the Installation

Upgrade Unicenter AutoSys Connect 2.3 or 2.4 to Unicenter

AutoSys Connect 2.4.1

Upgrade Approach #1

Upgrade Approach #2

Using Unicenter AutoSys Connect

Option

Startup Options

ATCOPTS

DEBUG

FILTER

Suppressing ATC0705I Message

Manual Job Restarts and Force Job Completions (CA-7 only)

Activating Send Retry (SRETRY)

XCCODE

Obtaining Environment Status

Displaying Remote Nodes

Displaying PRIMARYCCISYSID

Modifying Remote Node Statuses

Displaying Dependencies

Refreshing External Dependencies

Deleting Dependencies

Viewing Queued Sends

Removing Queued Sends

Displaying XCCODE Entries

ASPING

Remote Machine Validation

Direct Job Submit

Operation

Message Processing

Message Types

STARTJOB

ADD AGENT

ADD DEPENDENCY

PING

XCCODE Processing

Unicenter AutoSys Connect Startup

XCCODE Process Flow

Unicenter AutoSys Connect and Unicenter AutoSys Failover

Unicenter AutoSys Connect Failover Support Process Flow

Operator Commands

Commands

Troubleshooting

Message Codes

Initiating Jobs on a Mainframe

AutoSys Machine

Mainframe

Configure CCI

Start or Restart CCI

Enable Cross-Platform Scheduling Support

Install Client License Key for the Mainframe

Define the Machine

Submit Command Jobs to the Mainframe