Date post: | 08-Mar-2015 |
Category: |
Documents |
Upload: | rizwanscribd |
View: | 228 times |
Download: | 8 times |
Getting Started
2.3
Unicenter�
AutoSys Connect Option
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.
� 2001 Computer Associates International, Inc.
All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.
Contents iii
ASycntgstoc.doc, printed on 8/27/01, at 6:29 PM
Contents
Chapter 1: Welcome to Unicenter AutoSys ConnectOption
Technical Support.............................................................. 1-1
Chapter 2: Hardware and Software Requirements
Minimum Requirements........................................................ 2-1
Target System.............................................................. 2-1
Mainframe................................................................. 2-2
Operating System Requirements................................................. 2-2
CSA Space Requirements ....................................................... 2-2
LNKLST Concatenation ........................................................ 2-3
Dispatching Priority............................................................ 2-3
Chapter 3: Mainframe Installation
Installing Without SMP/E ...................................................... 3-1
Startup Options................................................................ 3-4
Monitoring OPC Jobs ....................................................... 3-4
Specifying Debug Level..................................................... 3-4
Managing Monitored Jobs................................................... 3-6
Verifying the Installation.................................................... 3-9
iv Getting Started
ASycntgstoc.doc, printed on 8/27/01, at 6:29 PM
Appendix A: Operator Commands
Commands ................................................................... A-1
Appendix B: Troubleshooting
Message Codes................................................................ B-1
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-4
auto_cnct Syntax........................................................... C-4
Define Command Jobs to Run on the Mainframe.............................. C-5
Define a Job that Depends on a Job Scheduled on the Mainframe ............... C-6
Index
Welcome to Unicenter AutoSys Connect Option 1–1
ASycntgs01.doc, printed on 8/24/01, at 4:55 PM
Chapter
1
Welcome to UnicenterAutoSys Connect Option
Unicenter AutoSys Connect Option provides cross-platform
scheduling capabilities to mainframe users by enabling them to
schedule and track jobs on mainframe platforms. The
integration of this option with Unicenter AutoSys provides a
centralized configuration using Unicenter AutoSys to schedule
jobs.
Unicenter AutoSys on UNIX, as the manager, requests initiation
of a job. The option processes the request, monitors the job, and
provides event information for status updates. Users can view
messages through the Unicenter Event Management function.
This product was developed using the foundation provided by
Unicenter Common Services on UNIX as well as on other
distributed platforms. Unicenter AutoSys Connect Option is a
stand-alone product to be installed on any OS/390 system that needs to process jobs managed by Unicenter AutoSys on the
mainframe.
Technical SupportFor 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. Technical support is available 24 hours a day, seven days a week.
Hardware and Software Requirements 2–1
ASycntgs02.doc, printed on 8/27/01, at 5:40 PM
Chapter
2 Hardware and SoftwareRequirements
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 impossible to make a
definitive statement of your hardware requirements.
This chapter provides you with the minimum requirements
based on practical experience to date. Also discussed in this
chapter are the operating system requirements, CSA space
requirements, LNKLST concatenation, and dispatching priority.
Minimum RequirementsThis section identifies the minimum requirements on the target system and the mainframe that are necessary to install the
product.
Target System
The minimum hardware and software requirements for the
target system are as follows:
■ Platform: OS/390
■ Hardware: No specific requirements
■ Software: Installation of Unicenter Framework for OS/390
version 2.2 and components CAIENF and CAICCI
Operating System Requirements
2– 2 Getting Started
ASycntgs02.doc, printed on 8/27/01, at 5:40 PM
Mainframe
The following software is required on the mainframe:
■ TCP/IP (IBM or Interlink)
■ CA90s Services Genlevel 9712 or higher, or Unicenter
Common Services for UNIX
- CAIRIM
- CAICCI - CAIENF
- CA-C Runtime
Operating System RequirementsThis 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 might need to increase this value.
CSA Space RequirementsUnicenter 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
Hardware and Software Requirements 2– 3
ASycntgs02.doc, printed on 8/27/01, at 5:40 PM
LNKLST ConcatenationUnicenter 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 because
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 PriorityWe recommend that dispatching priority be set above batch
processing and equal to noncritical online systems.
Mainframe Installation 3–1
ASycntgs03.doc, printed on 8/27/01, at 5:50 PM
Chapter
3 Mainframe Installation
This chapter provides the step-by-step procedures to install the
product on the mainframe.
Installing Without SMP/ETo install:
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.
//CINST EXEC PGM=IEBCOPY //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY //SYSUT2 DD DSN=connect.install, // SPACE=(TRK,(15,15,30)), // UNIT=SYSDA,VOL=SER=dasd-volume,DISP=(NEW,CATLG,DELETE) //SYSUT1 DD DSN=CONNECT.INSTALL, // UNIT=tape-unit,VOL=(,RETAIN,SER=tape-volume), // LABEL=(1,SL,EXPDT=02000),DISP=OLD
Installing Without SMP/E
3– 2 Getting Started
ASycntgs03.doc, printed on 8/27/01, at 5:50 PM
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 CACONNCT procedure to your installation
procedure library.
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:
ATCJxxx
where xxx specifies the three-byte scheduler identifier. Each
ATCJxxx member contains sample JCL that must be
customized. Refer to the batch interface documentation in
the Unicenter AutoSys User Guide for the appropriate
scheduler for batch interface JCL. See the appendix
“Initiating Jobs on a Mainframe” for a list of valid scheduler
identifiers.
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.
Note: Do not restart CAIENF until you complete Step 7.
7. Update the CAIENF startup options. SAMPJCL member XO4ENFR contains sample CAIENF
startup options. XO4ENFR may be merged into the existing
CAIENF startup options. Use care, since this may not be the
only Computer Associates product using CAIENF. For
information on the CAIENF startup options, see the
Unicenter Framework for OS/390 Administrator Guide.
Installing Without SMP/E
Mainframe Installation 3– 3
ASycntgs03.doc, printed on 8/27/01, at 5:50 PM
8. 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). This 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 SYSID is a 1-8 character identifier that is unique
throughout the CAICCI network, and PROTOCOL is used
to specify the communications protocol supported by this
local host node and its associated network parameters to
access remote CAICCI nodes.
Refer to your OS/390 Framework documentation for
additional details on the individual operands of the
PROTOCOL statement.
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.
9. Start CAIENF. Start (or restart) CAIENF. If you are restarting CAIENF, use
the REINIT option:
S CAIENF,,,REINIT
10. Start the started task using the OS/390 command START
CACONNCT. 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.
Startup Options
3– 4 Getting Started
ASycntgs03.doc, printed on 8/27/01, at 5:50 PM
Startup OptionsThis 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:
■ Monitoring OPC jobs
■ Specifying Debug level
■ Managing Unicenter AutoSys Connect Option-monitored
jobs
Monitoring OPC Jobs
If you are using OPC as your mainframe scheduler and want Unicenter AutoSys Connect Option to monitor OPC jobs
exclusively, you must enable this function through the FILTER
option as follows:
//CONNECT EXEC PGM=ATCMAIN,PARM=’FILTER=OPC’
Enabling this option ensures that jobs submitted outside of the
OPC scheduling application are ignored, and not erroneously
reported back to Unicenter AutoSys.
Specifying Debug Level
Note: This option should only be used under the direction of Computer Associates technical support personnel. See Technical Support in the chapter “Welcome to Unicenter AutoSys Connect Option” for more information.
The Debug level can be set from the mainframe by specifying
the Debug parameter as follows:
//CONNECT EXEC PGM=ATCMAIN,PARM=’DEBUG=n’
where n is a number from 0 to 9. The default Debug level is 1.
Startup Options
Mainframe Installation 3– 5
ASycntgs03.doc, printed on 8/27/01, at 5:50 PM
See the following table for a description of the Debug levels. For
a complete list of message codes, see the appendix
“Troubleshooting”.
DebugLevel
Messages
0 No messages are received.
1 (Default) All Error and Warning messages, and some
Informational messages.
2 Agent-related messages. Includes messages from
all prior levels.
3 CCI notification and job initiation-related
messages. Includes messages from all prior levels.
4 Dependency request and application-related
messages. Includes messages from all prior levels.
5 Job processing-related messages. Includes
messages from all prior levels.
6 Processing console command messages. Includes
messages from all prior levels.
7 Event occurrence messages. Includes messages
from all prior levels.
8 Includes messages from all prior levels.
9 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
where n is a number from 0 to 9.
Startup Options
3– 6 Getting Started
ASycntgs03.doc, printed on 8/27/01, at 5:50 PM
Managing Monitored Jobs
The product 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 it receives, Unicenter AutoSys then
determines whether the job is marked SUCCESS or FAILURE.
To enable the option to intervene or override the job return
code, to allow the user to manage the job’s success or failure
from the mainframe, you must set up the XCCODE member.
Setting Up the XCCODE Member
To enable the product to report a specified job as failed, you
must specify the JOB and/or JOBSTEP parameters in the
XCCODE option.
JOB
The syntax of the JOB parameter is as follows:
JOB jobname RC operator value
where:
jobname 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.
operator 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
value Specifies the value (0 to 4095) to compare to the return code.
Startup Options
Mainframe Installation 3– 7
ASycntgs03.doc, printed on 8/27/01, at 5:50 PM
Conditions specified in the JOB parameter are compared with
the final return code of a specified job. If the conditions are not met, the job is reported to have failed.
JOBSTEP
The syntax of the JOBSTEP parameter is as follows:
JOB jobname STEP stepname RC operator value
where:
jobname 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.
stepname Specifies the name of the step.
operator 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
value Specifies the value (0 to 4095) to compare to the return code.
A job/step combination might 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 may 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 to be 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
Startup Options
3– 8 Getting Started
ASycntgs03.doc, printed on 8/27/01, at 5:50 PM
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 that 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.
Examples
Example 1: PPR235 is JOBFAIL if step EOMTBLD completes
with RC higher than 4.
JOB PPR235 STEP EOMTBLD RC GT 4
Example 2: ZO5EMPQ is JOBFAIL if any step completes with
RC higher than 4.
JOB ZO5EMPQ STEP * RC GT 4
Example 3: 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 the XCCODE keyword in the PARM field on the PGM
statement of the started task JCL as follows:
//CONNECT EXEC PGM=ATCMAIN,PARM=’XCCODE’
Startup Options
Mainframe Installation 3– 9
ASycntgs03.doc, printed on 8/27/01, at 5:50 PM
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 ATC2041 appears in the job
log when the product initializes the CAICCI interface. Message ATC203I 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 Event Notification Facility (CAIENF). Message ATC605I appears
in the job log when the product has initialized itself with the
CAIENF interface.
3. Verify Initialization. Message ATC858I appears in the job log when the
initialization tasks have been completed and processing is
ready to begin.
Operator Commands A–1
ASycntgs0a.doc, printed on 8/27/01, at 5:54 PM
Appendix
A Operator Commands
The started task recognizes the following operator commands.
Commands
Command Description
STOP taskname Brings the started task down.
F taskname DEBUG=n Sets the debugging level, where n is a
number from 0 to 9. The volume of debugging messages increases as the
debugging level increases.
F taskname AGTLIST Displays a list of agents from which a
ping message has been received.
F taskname DEPLIST Displays a list of dependencies
(jobnames) being monitored for
execution.
Commands
A– 2 Getting Started
ASycntgs0a.doc, printed on 8/27/01, at 5:54 PM
Command Description
F taskname REFRESH
operand
Enables a refresh (update) of the
specified storage, where operand can be
PARMLIB, ATCJCL, or XCCODE.
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.
F taskname XCDLIST Displays a list of XCCODE entries used
to determine whether a job should fail based on job or jobstep condition code.
Troubleshooting B–1
ASycntgs0b.doc, printed on 8/27/01, at 5:59 PM
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 CodesThe syntax of the Unicenter AutoSys Connect Option message
codes is:
ATCxxxxC
where xxxx is a 4 -digit identifier and C specifies the type of message as follows:
■ E for Error
■ W for Warning
■ I for Informational
ATC0001E REQUEST AD FAILED - DATA COUNT IS ZERO
An Add Dependency (external reference) request was formatted
incorrectly.
ATC0002E REQUEST AD FAILED - DATA LENGTH IS ZERO
An Add Dependency (external reference) request was formatted
incorrectly.
Message Codes
B– 2 Getting Started
ASycntgs0b.doc, printed on 8/27/01, at 5:59 PM
ATC0003E REQUEST AD FAILED - DEPENDENCY ADD FAILED
An attempt to add a dependency to the dependency array failed. Check the log to determine why the Add Dependency failed.
ATC0050E ADD AGENT FAILED FOR NODE {nodename} - GETMAIN
ERROR
An attempt to add an agent to the agent array failed because a
getmain call failed. Obtain an agent list report (see 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, you may need to increase storage allocated to
the started task.
ATC0051W ADD AGENT IGNORED FOR NODE {nodename} - DUPLICATE KEY
An attempt to add an agent to the agent array failed because the
agent already exists. This should never occur during normal operations and indicates a processing error. Obtain an agent list report (see AGTLIST operator command) and contact tech
support.
ATC0052I ADDED AUTOSYS AGENT ON NODE {nodename} PROCESS {processname}
An attempt to add an agent to the agent array completed. The
product keeps track of each agent pinging it. This informational message prints when the debugging level is >= 2
ATC0101E 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 user may need to increase storage allocated to the
started task.
Message Codes
Troubleshooting B– 3
ASycntgs0b.doc, printed on 8/27/01, at 5:59 PM
ATC0201E UNRECOGNIZED CCI FUNCTION REQUESTED
A call was made to the CCI function routine with invalid
parameters. This should not occur during normal operations and
represents a processing error.
ATC0202E CCI SERVICES INITIALIZATION FAILED
An attempt to initialize CCI services failed. Check previous
messages in the log for an associated message. This should not occur during normal operations and could represent a
processing error or setup error. Verify CCI is correctly installed
and running on the mainframe side and contact tech support.
ATC0203I HOST NODE IS {nodename}
An attempt to initialize CCI services completed successfully and
CCI node name is displayed as {nodename} in the message. This
informational message appears in the beginning of the log when
CCI services are initialized.
ATC0204I CCI SERVICES HAVE BEEN INITIALIZED
An attempt to initialize CCI services completed successfully. This informational message appears in the beginning of the log
when CCI services are initialized.
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.
Message Codes
B– 4 Getting Started
ASycntgs0b.doc, printed on 8/27/01, at 5:59 PM
ATC0252W DEBUG OPERATOR COMMAND FAILED – INVALID
DEBUGGING LEVEL
The debug operator command was entered for the started task
with an invalid debugging value. Valid debugging levels are 1-9. The command is ignored and the debugging 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.
ATC0254I PROCESSING CONSOLE COMMAND
This informational message is printed when an operator
command is received. This message prints when the debugging
level is >=6.
ATC0255I STOP COMMAND ISSUED
This informational message is printed when a stop operator
command is received. The stop command shuts down the
started task.
ATC0256I DEBUGGING LEVEL IS SET TO {debuglevel}
A debug operator command was entered and processed. The
debugging level has been changed to debuglevel.
ATC0301E NO DEPENDENCY FOUND FOR {jobname}
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. Contact tech support if Unicenter
AutoSys did not enter a delete dependency request.
Message Codes
Troubleshooting B– 5
ASycntgs0b.doc, printed on 8/27/01, at 5:59 PM
ATC0302E FIND DEPENDENCY FAILED
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.
ATC0303E DELETE DEPENDENCY FAILED
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.
ATC0304I DELETED DEPENDENCY FOR JOB {jobname} FOR NODE
{nodename}
A call to the dependency delete routine completed successfully
for jobname sent from nodename. This can occur during processing
of a delete dependency request. This informational message
prints when the debugging level is >=4.
ATC0351E ADD DEPENDENCY FAILED FOR JOB {jobname} - GETMAIN ERROR
An attempt to add a dependency to the dependency array failed
because a getmain call failed. Obtain a dependency list report (see AGTLIST 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 user may need to
increase storage allocated to the started task.
ATC0352W ADD DEPENDENCY IGNORED FOR JOB {jobname} - DUPLICATE KEY
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. Obtain a
dependency list report (see DEPLIST operator command).
Message Codes
B– 6 Getting Started
ASycntgs0b.doc, printed on 8/27/01, at 5:59 PM
ATC0353I ADDED DEPENDENCY FOR JOB {jobname} FOR 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 debugging
level is >=4.
ATC0354I AUTO-ADDED DEPENDENCY FOR JOB {jobname} FOR
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
debugging level is >=4.
ATC0401E DELETE DEPENDENCY 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. Contact tech support.
ATC0402E DELETE DEPENDENCY FAILED - INDEX IS PAST END OF
ARRAY
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.
ATC0601E UNRECOGNIZED ENF FUNCTION REQUESTED
A call was made to the ENF function routine with invalid
parameters. This should not occur during normal operations and
represents a processing error.
Message Codes
Troubleshooting B– 7
ASycntgs0b.doc, printed on 8/27/01, at 5:59 PM
ATC0602E ENF INIT FAILED - ENF NOT ACTIVE
An initialize call was made to the ENF function routine but ENF
is not active. Verify that ENF is installed and running.
ATC0603E ENF INIT CALL FAILED
An initialize call was made to the ENF function routine but ENF
is not active. Verify that ENF is installed and running.
ATC0604E ENF STATUS CALL FAILED
An initialize call was made to the ENF function routine, but ENF
is not active. Verify that ENF is installed and running.
ATC0605I ENF SERVICES HAVE BEEN INITIALIZED
An initialize call was made to the ENF function routine and it completed successfully. This is an informational message.
ATC0606E ENF LISTEN CALL FAILED - ENF IS INACTIVE
A listen call was made to the ENF function routine but ENF is
not active. Verify that ENF is installed and running.
ATC0607E ENF LISTEN CALL FAILED
A listen call was made to the ENF function routine but it failed. Verify that ENF is installed and running.
ATC0608E ENF DATA CALL FAILED
A data call was made to the ENF function routine but it failed. Verify that ENF is installed and running.
ATC0609E FILTER PROCESSING FAILED
A call to the filter processing routine failed. This should not occur during normal operations and represents a processing
error.
Message Codes
B– 8 Getting Started
ASycntgs0b.doc, printed on 8/27/01, at 5:59 PM
ATC0610E FIND DEPENDENCY ROUTINE FAILED
A call to the find dependency routine failed. This should not occur during normal operations and represents a processing
error.
ATC0611I EVENT {eventname} OCCURRED FOR {jobname} - {jobnumber}
This message is printed every time an ENF event occurs. This
informational message is printed when the debug level is >= 7.
ATC0612I PROCESSING {eventname} FOR {jobname} - {jobnumber}
This message is printed every time an ENF event occurs and
there is a dependency for the jobname. This informational message is printed when the debug level is >= 7.
ATC0613I ENF INTERFACE HAS BEEN TERMINATED
This informational message indicates that the interface to ENF
services has been terminated.
ATC0651E ENF GET CALL FAILED
This message occurs when an ENF GET call has failed. This
should not occur during normal operations and represents a
processing error.
ATC0652E 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.
ATC0653I PROCESSING ENF EVENT
This message indicates that an ENF event is being processed
because there is a dependency for this ENF event. This
information message prints when the debugging level is >=5.
Message Codes
Troubleshooting B– 9
ASycntgs0b.doc, printed on 8/27/01, at 5:59 PM
ATC0655I DELETED DEPENDENCY FOR JOB {jobname} FOR NODE
{nodename}
A call to the dependency delete routine completed successfully
for jobname sent from nodename. This can occur after a JOBTERM
event for a dependency. This informational message prints when
the debugging level is >=5.
ATC0701E UNRECOGNIZED EVENT - {eventname}
An attempt to send an event to Unicenter AutoSys has failed
because the event is not recognized. This should not occur
during normal operations and represents a processing error.
ATC0702E SEND EVENT FAILED
An attempt to send an event to Unicenter AutoSys has failed. This error can occur if CCI services are not available. Verify CCI is running. This should not occur during normal operations and
represents a processing error.
ATC0703I SENDING EVENT {eventname} TO NODE {nodename}
An event is being sent to the agent residing on nodename. This
informational message prints when the debugging level is >=3.
ATC0751E 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 the ATCPARM
DD is allocating a valid data set.
ATC0752E FIND FOR JCL MEMBER 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 data set.
Message Codes
B– 10 Getting Started
ASycntgs0b.doc, printed on 8/27/01, at 5:59 PM
ATC0753E 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. Allocate more storage to the started task.
ATC0754I 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 debugging
level is >=6.
ATC0801E 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.
ATC0802E 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.
ATC0803W 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 start job request. Truncation can occur because the command text was too long. Check the length of command text.
ATC0851E AUTOSYS/AUTOSYS CONNECT IS SHUTTING DOWN
This message indicates that the option is shutting down. This
may occur because of a processing error or the operation STOP
command.
Message Codes
Troubleshooting B– 11
ASycntgs0b.doc, printed on 8/27/01, at 5:59 PM
ATC0852E 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.
ATC0853E UNRECOGNIZED DEBUG VALUE
This message indicates that the option has found an
unrecognized debugging level specified with the debug
parameter. The debug parameters are specified with the PARM
keyword in the started task JCL. Valid debugging values are 1-9. Check the started task for an invalid debugging level specified
with the debug parameter.
ATC0854I 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.
ATC0855E DEBUGGING LEVEL IS SET TO {debuglevel}
This informational message indicates that the debug parameter
was specified and processed. The debugging level has been
changed to {debuglevel}.
ATC0856I FILTERING IS ENABLED FOR {schedulername }
This informational message is indicates that the filter parameter
was specified and processed. Filtering has been enabled for the
scheduler {schedulername}.
Message Codes
B– 12 Getting Started
ASycntgs0b.doc, printed on 8/27/01, at 5:59 PM
ATC0857I XCCODE PROCESSING IS ENABLED
This informational message indicates that the xccode parameter
was specified and processed. XCCODE processing has been
enabled.
ATC0858E CCI INITIALIZATION FAILED
An attempt to initialize CCI services failed. This should not occur during normal operations and could represent a
processing error or setup error. Verify CCI is correctly installed
and running on the mainframe side and contact tech support.
ATC0859E ENF INITIALIZATION FAILED
An attempt to initialize ENF services failed. This should not occur during normal operations and could represent a
processing error or setup error. Verify ENF is correctly installed
and running on the mainframe side and contact tech support.
ATC0860E 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 on the mainframe side and contact tech support.
ATC0861E 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
and contact tech support.
ATC0862E 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 and contact tech support.
Message Codes
Troubleshooting B– 13
ASycntgs0b.doc, printed on 8/27/01, at 5:59 PM
ATC0863I AUTOSYS/CONNECT {version} INITIALIZATION
COMPLETE
This informational message indicates that initialization of the
started task is complete. Agent requests can now be processed, and dependencies can be monitored.
ATC0864I AUTOSYS/CONNECT SHUTDOWN COMPLETE
This informational message indicates that the shutdown
processing of the started task is complete.
ATC0901E 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.
ATC0902E RECEIVE BUFFER LENGTH IS INVALID
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.
ATC0903E START JOB REQUEST FAILED
A start job request from an agent has failed. Check the job log to
determine the cause of the failure.
ATC0904E ADD DEPENDENCY REQUEST FAILED
An add dependency (external reference) request from an agent has failed. Check the job log to determine the cause of the failure.
ATC0905E DELETE DEPENDENCY REQUEST FAILED
A delete dependency request from an agent has failed. Check the
job log to determine the cause of the failure.
Message Codes
B– 14 Getting Started
ASycntgs0b.doc, printed on 8/27/01, at 5:59 PM
ATC0906E AUTOSYS AGENT PING FAILED
A ping request from an agent has failed. Check the job log to
determine the cause of the failure.
ATC0907E 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.
ATC0908E PROCESSING CCI MESSAGE
The option has received a message from an agent. This
informational message prints when the debugging level is >=3.
ATC0909I REQUEST {requestcode} RECEIVED FROM NODE {nodename}
The product has received request code from an agent on
nodename. This informational message prints when the
debugging level is >=4.
ATC1001E UNRECOGNIZED OPC REQUEST, ABENDING
The product has received an OPC request and is abending. This
should not occur during normal operations and represents a
processing error.
ATC1002E LINK TO EQQYCOM (OPC PIF) FAILED
An attempt to link to module EQQYCOM failed while trying to
initialize the interface. This module is the OPC PIF module. Verify the EQQYCOM module is available to the started task
and contact tech support.
ATC1003E OPC PIF INIT CALL FAILED, RC = X {returncode}
An initialize call was made to the OPC PIF and the call failed
with a return code of {returncode}. Verify that OPC PIF is
installed and available.
Message Codes
Troubleshooting B– 15
ASycntgs0b.doc, printed on 8/27/01, at 5:59 PM
ATC1004I OPC PIF HAS BEEN INITIALIZED
An initialize call was made to OPC PIF and it completed
successfully. This is an informational message.
ATC1005E LINK TO EQQYCOM (OPC) FAILED
An attempt to link to module EQQYCOM failed while trying to
retrieve a list of OPC job. This module is the OPC PIF module. Verify the EQQYCOM module is available to the Connect started
task and contact tech support.
ATC1006E OPC PIF LIST CALL FAILED, RC = X {returncode }
A list call was made to the OPC PIF and the call failed with a
return code of {returncode}. Verify that OPC PIF is installed and
available.
ATC1007E OPC PIF PROCESSING ERROR, ABENDING
While processing the output of an OPC PIF list call, the product encountered a processing error, and is abending for diagnostic
purposes. This is a processing error and should not occur during
normal processing. Contact tech support.
ATC1008E OPC PIF SELECT CALL FAILED, RC = X {returncode }
A select call was made to the OPC PIF and the call failed with a
return code of {returncode}. Verify that OPC PIF is installed and
available.
ATC1009I OPC PIF LIST RETURNED X {entrycount }
A list call was made to the OPC PIF and the call returned a list of length {entrycount}.
ATC1051E UNRECOGNIZED SCHEDULER REQUESTED –
{schedulername} – REQUEST IGNORED
The product is processing a start job request and the scheduler
requested is not supported. The start job request is ignored.
Message Codes
B– 16 Getting Started
ASycntgs0b.doc, printed on 8/27/01, at 5:59 PM
ATC1052E NO JCL FOUND FOR SCHEDULER {schedulername}
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.
ATC1053E COMMAND TEXT INVALID FOR SCHEDULER
{schedulername} – START FAILED FOR JOB {jobname}
Invalid command text was encountered during the processing of a start job request. The start job request is ignored.
ATC1054E INTERNAL READER SUBMIT FAILED FOR {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.
ATC1055E ADD DEPENDENCY FAILED FOR {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.
ATC1056I SUBMITTED {jobname1} FOR {jobname2}
The product is processing a start job request and submitted
jobname1 to start jobname2. This informational message prints
when the debugging level is >=4.
ATC1057E INTERNAL ERROR – DATA COUNT IS ZERO FOR
{jobname}
An error was encountered during processing of a start job
request. This should not occur during normal operations and
represents a processing error.
Message Codes
Troubleshooting B– 17
ASycntgs0b.doc, printed on 8/27/01, at 5:59 PM
ATC1058E NO COMMAND OR COMMAND TEXT FOUND FOR
{jobname}
An error was encountered during processing of a start job
request. This should not occur during normal operations and
represents a processing error.
ATC1059E GENERATE COMMAND TEXT FAILED FOR SCHEDULER
{schedulername} START FAILED FOR {jobname}
An error was encountered during processing of a start job
request. This should not occur during normal operations and
represents a processing error.
ATC1101E XCCODE PROCESSING FAILED – NO ENTRIES
An attempt to perform xccode processing has failed because
there are no xccode conditions specified. This should not occur
during normal operations and represents a processing error.
ATC1102I XCCODE SETTING JOBFAIL – JOBSTEP CONDITION
The status of this job is being set to JOBFAIL because of an
xccode jobstep condition. This informational message prints
when the debugging level is >=5.
ATC1103I XCCODE SETTING JOBFAIL – JOB CONDITION
The status of this job is being set to JOBFAIL because of an
xccode job condition. This informational message prints when
the debugging level is >=5.
ATC1104I 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
informational message prints when the debugging level is >=5.
Message Codes
B– 18 Getting Started
ASycntgs0b.doc, printed on 8/27/01, at 5:59 PM
ATC1105I XCCODE SETTING SUCCESS – JOB CONDITION
The status of this job is being set to SUCCESS because of an
XCCODE jobstep condition. This informational message prints
when the debugging level is >=5.
ATC1151E ALLOCATION OF ATCPARM CC 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.
ATC1152E 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.
ATC1153E 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.
ATC1154E GETMAIN ERROR READING XCCODE MEMBER
An attempt to read the XCCODE member into working storage
because a getmain call failed. The user may need to increase
storage allocated to the started task.
ATC1155E 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
Troubleshooting B– 19
ASycntgs0b.doc, printed on 8/27/01, at 5:59 PM
ATC1156E 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.
ATC1157E 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.
ATC1158E 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.
ATC1159E 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 a 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.
Message Codes
B– 20 Getting Started
ASycntgs0b.doc, printed on 8/27/01, at 5:59 PM
ATC1160E 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 a xccode condition. Verify that all xccode
conditions contain operators and that each condition is
contained in only one line of the XCCODE member.
ATC1161E 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 a xccode condition. Verify that all xccode conditions
contain values and that each condition is contained in only one
line of the XCCODE member.
ATC1162E XCCODE CONDITION NOT ADDED - GETMAIN ERROR
An attempt to read add a xccode condition to working storage
failed because a getmain call failed. The user may need to
increase storage allocated to the started task.
ATC1163E ATCLXCD LIST NODE ENTRY ADDED
Indicates an XCCODE condition was read from parmlib member
XCCODE and is now resident in memory for XCCODE
evaluation. This informational message prints when the
debugging level is >=6.
ATC1201W XCCODE NOT ENABLED – REFRESH IGNORED
An operator REFRESH command was issued for XCCODE, but the option is not enabled. Refresh processing is terminated.
ATC1202I PROCESSING operator_command
This informational message indicates the operator command
being processed.
Message Codes
Troubleshooting B– 21
ASycntgs0b.doc, printed on 8/27/01, at 5:59 PM
ATC1203I REFRESH COMMAND COMPLETE
An operator REFRESH command has been issued. The
command operation has completed successfully. This is an
informational message.
ATC1204E REFRESH COMMAND FAILED
An operator REFRESH command has been issued. The
command operation has failed. Please see preceding messages in
the operator console for information on why the command
failed.
Initiating Jobs on a Mainframe C–1
Asycntgs0c.doc, printed on 8/27/01, at 6:08 PM
Appendix
C
Initiating Jobs on aMainframe
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 MachineHostname—guava
Operating System—UNIX
Software Installed—CCI, AutoSys 3.5.1
Parameter Configuration:
AUTOSYS=/opt/autotree/tst/autosys
AUTUSER=/opt/autotree/tst/autouser
AUTOSERV=ACE
MainframeHostname—honeydew
Operating System—OS/390
Software Installed—ENF, Connect
The tutorial proceeds in the following order, and should be
performed in its entirety:
1. Configure CCI.
2. Start or restart CCI.
3. Enable Unicenter AutoSys cross-platform scheduling
support.
Configure CCI
C– 2 Getting Started
Asycntgs0c.doc, printed on 8/27/01, at 6:08 PM
4. Install client license key for mainframe (OS/390) machine.
5. Define the option machine to Unicenter AutoSys.
6. Submit command jobs to mainframe.
Configure CCITo 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/guava/ccirmtd.prf
Enter the following values for local and remote parameters:
LOCAL = guava guava 32768 startup REMOTE = honeydew honeydew 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 Installation and Getting Started
Guide.
Start or Restart CCIYou 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
Enable Cross-Platform Scheduling Support
Initiating Jobs on a Mainframe C– 3
Asycntgs0c.doc, printed on 8/27/01, at 6:08 PM
Enable Cross-Platform Scheduling SupportTo 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:
HNY:CNCT=honeydew
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 User Guide.
Install Client License Key for the MainframeInstall 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 Hostname: REMOTE_HOST Hostid: 0 KEY: IIJJKKLLMMNNOOPP *****New Key ADDED!***** KEY Type: [(c)lient,(s)erver,(t)ime,(x)pert ]:<Return>
Define the Machine
C– 4 Getting Started
Asycntgs0c.doc, printed on 8/27/01, at 6:08 PM
Define the MachineDefine the machine that is running Unicenter AutoSys Connect Option(OS/390) to Unicenter AutoSys via the JIL command line
utility. At the operating system command prompt, enter:
jil insert_machine: honeydew 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 User Guide.
Submit Command Jobs to the MainframeThe auto_cnct command is used in this section to define
command jobs. The following is an explanation of the
command’s syntax.
auto_cnct Syntaxauto_cnct –a node –s scheduler code [-j jobname –c command –p parameters -d]
where:
-a node specifies the hostname of the machine running the option
(HONEYDEW)
-s scheduler code specifies the scheduler the command is being
issued to (see the following table).
Code Scheduler
CA7 CA-7
CAM CA-Manager
CAS CA-Scheduler
Submit Command Jobs to the Mainframe
Initiating Jobs on a Mainframe C– 5
Asycntgs0c.doc, printed on 8/27/01, at 6:08 PM
Code Scheduler
CTM Control-M
ESP ESP
JBT CA-JobTrac
OPC OPC/ESA
USR User-written scheduler
-j jobname specifies the jobname to be monitored for status.
-c command specifies the command word, such as ADD or RUN.
-p parameters specifies the command parameters for the job.
-d 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 To submit a job to CA-7, enter:
insert_job: connect_job1 command: auto_cnct –aHONEYDEW –jASYS7001 –cRUN –sCA7 –d machine: honeydew date_conditions: 1 days_of_week: all start_mins: 25
Control-M To submit a job to Control-M, enter:
insert_job: connect_job2 command: auto_cnct –aHONEYDEW –sCTM -jTESTJOB –cORDERJOB -p"CM.MTC.JIX.SCHEDULE,TEST123" –d machine: honeydew
CA-JobTrac To submit a job to CA-JobTrac, enter:
insert_job: connect_job3 command: auto_cnct –aHONEYDEW –jFCHUA001 –cADD –sJBT –d machine: honeydew
Submit Command Jobs to the Mainframe
C– 6 Getting Started
Asycntgs0c.doc, printed on 8/27/01, at 6:08 PM
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 CA-7 or CA-JobTrac:
1. Define 2 jobs in the OS/390 scheduling system (honeydew). 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^HNY) machine: localhost
insert_job: test_dep2 command: print_a_message.sh condition: success(JB5HRS^HNY) machine: localhost
3. You can also define jobs as a combination of both command
jobs and external dependencies.
■ To submit a job to CA-7, enter:
insert_job: connect_job4 command: auto_cnct -aHONEYDEW -jASYS7002 –cRUN -sCA7 –d machine: honeydew condition: success(JB5HRS^HNY)
■ To submit a job to CA-JobTrac, enter:
insert_job: connect_job5 command: auto_cnct –aHONEYDEW –jFCHUA002 –cADD –sJBT –d machine: honeydew condition: success(JB5MINS^HNY)
Index–1
ASycntgsix.doc, printed on 8/27/01, at 6:18 PM
Index
A
auto_cnct, C-4
syntax, C-4
AutoSysAgentSupport parameter, C-3
B
batch interface, 3-2
C
CAICCI startup options, 3-3
verifying, 3-9
CAIENF, 3-2
startup options, 3-2
CCI ccirmtd.prf file, C-2
configure, C-2
remote daemon, 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-4
configuration file, C-3
cross-platform dependencies
enable, C-3
F
FILTER option, 3-4
H
hardware requirements, 2-1
J
JCL
install, 3-1
JOB
syntax, 3-6
JOBSTEP
syntax, 3-7
L
libraries, 3-1
license key, C-3
Index– 2 Getting Started
ASycntgsix.doc, printed on 8/27/01, at 6:18 PM
M
mainframe
requirements, 2-2
MAXUSER value, 2-2
member names
syntax, 3-2
message codes, B-1
syntax, B-1
O
OPC
monitoring, 3-4
operator commands, A-1
R
requirements
CSA space, 2-2
hardware, 2-1
LNKLST, 2-3
mainframe, 2-2
operating system, 2-2
software, 2-1
target systems, 2-1
S
schedule identifier, 3-2
scheduler codes
list of, C-4
scheduler JCL, 3-2
software requirements, 2-1
started task, A-1
startup options, 3-4
Connect-monitored jobs, 3-6
OPC only, 3-4
setting Debug, 3-4
support technical, 1-1
T
technical support, 1-1
X
XCCODE member
activating, 3-8
JOB, 3-6
JOBSTEP, 3-7
setting up, 3-6