Automic Automation Intelligence for CA7
This section walks you through all the necessary steps to install Automic Automation Intelligence for CA7.
This page includes the following:
Overview
The Automic Automation Intelligence server makes a connection to the mainframe using either the FTP protocol or the files can be pushed from the mainframe server to the Automic Automation Intelligence server.
There are two types of data that Automic Automation Intelligence retrieves from the mainframe, definitional and operational. A general overview of these two processes follows:
-
Definitional data consists of the job definitions, triggers, predecessors, calendars, resources and data sets defined in the CA7 database. This information is retrieved from the mainframe when the scheduler is added to Automic Automation Intelligence. Definitional data is also updated in the Automic Automation Intelligence server at a user-specified interval (typically overnight). The details of the JCL job that extracts the definitional data are provided below, referred to as the JOBDEF JCL job. The JOBDEF job should run at an interval that is in sync with the user-specified update interval defined in Automic Automation Intelligence. The JOBDEF job should complete prior to the Automic Automation Intelligence server update time to ensure that the latest data is reflected in Automic Automation Intelligence.
-
Operational data refers to the real-time activity of jobs as they run inside of CA7. This includes when a job moves through the CA7 queues, completes, abends, or is canceled. To extract and retrieve this data, Automic Automation Intelligence uses an external data set the trigger to start the EVENT JCL job (described below). The process is automatically initiated from the Automic Automation Intelligence server on a user-specified interval (typically every 1 minute or less).Automic Automation Intelligence initiates an FTP connection to the mainframe and PUTs a file via FTP. CA7 will detect the arrival of the trigger file and run the EVENT JCL job. The Automic Automation Intelligence server waits (polls) for the arrival of the output from the EVENT JCL job. Once the output is detected, Automic Automation Intelligence retrieves the file over FTP and processes the contents to update the Automic Automation Intelligence database. Some configuration may be required for CA7 and FTP which are described in the following sections.
Mainframe Security Configuration
Automic Automation Intelligence requires an FTP user on the mainframe for the Automic Automation Intelligence server to connect to the FTP service.
- Create an FTP User on the Mainframe.
- User must have READ / WRITE / DELETE access to all datasets under the qualifier that will be configured in the Automic Automation Intelligence Add Scheduler dialog as Base Report DSN.
- User must have READ / WRITE / DELETE access to the dataset that will be configured in the Automic Automation Intelligence Add Scheduler dialog as Trigger DSN.
CA7 Configuration
Note: Many installations are already configured for external data set tracking / triggering. These instructions apply to installations that may not have this feature already enabled.
- External data set tracking must be enabled for CA7. For details on setting up external data set tracking, see the CA7 Systems Programming Guide.
- The external data set tracking criteria table must include the data set specified in the Automic Automation Intelligence Add Scheduler dialog as the Trigger DSN. Instructions on configuring the external data set tracking criteria can be found in the CA7 Systems Programming Guide.
Mainframe FTP Service Configuration
Many installations are already configured to post SMF feedback for FTP server activity. These instructions apply to installations that may not have this feature already enabled.
Configure FTP server to enable SMF records. By default, the mainframe FTP server is not configured to record SMF events for FTP activity. In order for the Automic Automation Intelligence server to initiate the triggering of the EVENT JCL job, SMF events must be enabled for the FTP Server. To enable SMF feedback for the FTP server, code the following in the FTP.DATA configuration file (typically TCPIP.FTP.DATA). This setting, along with external data set tracking for CA7, should enable the Automic Automation Intelligence data set trigger in CA7.
-
SMF STD; SMF records use standard subtypes.
Pre-Allocate the EVENT JCL Trigger Data Set
The data set that will be configured in Automic Automation Intelligence as the Trigger DSN should be pre-allocated on the host (mainframe) system. The DCB Information for the allocation is as follows:
- LRECL: 80
- SPACE: 1 TRK
- RECFM: FB
Tailor and Schedule the Automic Automation Intelligence JCL Jobs
Instructions and sample JCL for the EVENT and JOBDEF JCL jobs are below. Scheduling instructions are also included for both jobs.
JOBDEF JCL
Note: Step SCAL001 should be repeated for every calendar that is defined in CA7, with the appropriate calendar suffix (i.e. PE) substituted. Automic Automation Intelligence will also accept a file with all of the calendars for one year in it. This file should be named SCAL followed by the last two digits of the year (i.e. 2014 calendars would be SCAL14). See Note below for sample JCL on creating one file with many calendars.
Tailor the JOBDEF JCL for your installation based on the following example:
//JOBDEF JOB (ACNT-DATA),'JOB DEF JOB',
// CLASS=B,MSGCLASS=X
//*
// SET BASEDSN='ADCDMST.JAWS.'
// SET CAL2LOAD='ADCDMST.CA7.CAL2LOAD'
//*
//** CREATE OUTPUT FILE FOR LJOB
//LJOB EXEC PGM=CAL2X2WB,PARM=',CA71'
//STEPLIB DD DISP=SHR,DSN=&CAL2LOAD
//SYSPRINT DD DSN=&BASEDSN.LJOB,DISP=(OLD,CATLG,CATLG)
//ERRORS DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSIN DD *
/LOGON MASTER
LJOB,JOB=*,LIST=ALL
/LOGOFF
/*
//LDSN EXEC PGM=CAL2X2WB,PARM=',CA71'
//STEPLIB DD DISP=SHR,DSN=&CAL2LOAD
//SYSPRINT DD DSN=&BASEDSN.LDSN,DISP=(OLD,CATLG,CATLG)
//ERRORS DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSIN DD *
/LOGON MASTER
LDSN,DSNBR=DS*
/LOGOFF
/*
//** CREATE OUTPUT FILE FOR SCAL14PE
//SCAL001 EXEC PGM=CAL2X2WB,PARM=',CA71'
//STEPLIB DD DISP=SHR,DSN=&CAL2LOAD
//SYSPRINT DD DSN=&BASEDSN.SCAL14PE,DISP=(OLD,CATLG,CATLG)
//ERRORS DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSIN DD *
/LOGON MASTER
PRINT,SCAL=PE,YEAR=14
/LOGOFF
/*
//** CREATE OUTPUT FILE FOR MAINFRAME TIMEZONE
//TIMEZONE EXEC PGM=BPXBATCH,
// PARM='SH echo $TZ'
//STDOUT DD DSN=&BASEDSN.TIMEZONE,DISP=(OLD,CATLG,CATLG)
Note: For creating a one calendar file for all years, replace the create output file for SCAL14PE with the following example:
//** CREATE OUTPUT FILE FOR SCAL14 //SCAL001 EXEC PGM=CAL2X2WB,PARM=',CA71' //STEPLIB DD DISP=SHR,DSN=&CAL2LOAD //SYSPRINT DD DSN=&BASEDSN.SCAL14,DISP=(OLD,CATLG,CATLG) //ERRORS DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //SYSIN DD * /LOGON MASTER PRINT,SCAL=PE,YEAR=14 PRINT,SCAL=WE,YEAR=14 /LOGOFF
Schedule the JOBDEF JCL job to run on a schedule in CA7 (typically once per day).
Note: After running the JOBDEF JCL, the STDOUT DD for the TIMEZONE step should have a valid timezone in the format MST7MDT.
EVENT JCL
Tailor the EVENT JCL for your installation based on the following example:
//EVENT JOB (ACCT),EVENT.EXTRACTOR, // CLASS=B, // REGION=0M, // TIME=NOLIMIT //* // SET TRIGDSN='ADCDMST.TRIGGERS.JAWS' // SET RPTBASE='ADCDMST.JAWS' // SET CA7LOGP='ADCDMST.CA7.LOGP' // SET CA7LOGS='ADCDMST.CA7.LOGS' //*-------------------------------------------------------- //* IF THE OUTPUT FILE EXISTS, DELETE IT. WE WILL CATALOG //* A NEW ONE LATER //*-------------------------------------------------------- //DELETE EXEC PGM=IEFBR14 //DD1 DD DSN=&RPTBASE..RPT70,DISP=(MOD,DELETE,DELETE), // UNIT=SYSDA,SPACE=(CYL,(0)) //*-------------------------------------------------------- //* GENERATE THE HISTORY FILE FOR JAWS AND PASS IT TO THE //* NEXT STEP TO BE CATALOGED //*-------------------------------------------------------- //REPORT EXEC CA7LOG,PG=SASSHIS8,PA='O,MAX' //SASSRA01 DD DUMMY //SASSRA02 DD DUMMY //SASSRA03 DD DUMMY //COMMANDS DD DSN=&&COMMANDS,DISP=(,PASS), // DCB=(RECFM=FB,LRECL=80,BLKSIZE=0), // UNIT=SYSDA,SPACE=(CYL,(1,1)) //UCC7HIST DD DISP=SHR,DSN=&CA7LOGP // DD DISP=SHR,DSN=&CA7LOGS //SYSIN DD DISP=SHR, // DSN=&TRIGDSN //SYSLIST DD DSN=&&RPT70, // DISP=(NEW,PASS,DELETE), // UNIT=SYSDA,SPACE=(CYL,(50,35)), // DCB=(RECFM=FBA,LRECL=133,BLKSIZE=13300) //SYSOUT DD DUMMY //*-------------------------------------------------------- //* CATALOG THE TEMPORARY FILE CREATED IN THE PREVIOUS STEP //*-------------------------------------------------------- //COPYRPT EXEC PGM=IEBGENER //SYSPRINT DD DUMMY //SYSOUT DD DUMMY //SYSUT1 DD DISP=OLD,DSN=&&RPT70 //SYSUT2 DD DSN=&RPTBASE..RPT70, // DISP=(,CATLG), // UNIT=SYSDA,SPACE=(CYL,(50,35))), // DCB=(RECFM=FBA,LRECL=133,BLKSIZE=0) //SYSIN DD DUMMY
Configure a Data Set Trigger to trigger the EVENT JCL job in CA7.
Note: The triggering dataset must be the same as the DSN configured in the Automic Automation Intelligence Add Scheduler dialog as Trigger DSN.