CA 7 Workload Automation Going Cross-Platform Managing you Enterprise Workload Ellen O'Connell

Transcription

1 CA 7 Workload Automation Going Cross-Platform Managing you Enterprise Workload Ellen O'Connell

2 Terms of This Presentation This presentation was based on current information and resource allocations as of October 2009 and is subject to change or withdrawal by CA at any time without notice. Notwithstanding anything in this presentation to the contrary, this presentation shall not serve to (i) affect the rights and/or obligations of CA or its licensees under any existing or future written license agreement or services agreement relating to any CA software product; or (ii) amend any product documentation or specifications for any CA software product. The development, release and timing of any features or functionality described in this presentation remain at CA s sole discretion. Notwithstanding anything in this presentation to the contrary, upon the general availability of any future CA product release referenced in this presentation, CA will make such release available (i) for sale to new licensees of such product; and (ii) to existing licensees of such product on a when and if-available basis as part of CA maintenance and support, and in the form of a regularly scheduled major product release. Such releases may be made available to current licensees of such product who are current subscribers to CA maintenance and support on a when and if-available basis. In the event of a conflict between the terms of this paragraph and any other information contained in this presentation, the terms of this paragraph shall govern. 2

3 For Informational Purposes Only Certain information in this presentation may outline CA s general product direction. All information in this presentation is for your informational purposes only and may not be incorporated into any contract. CA assumes no responsibility for the accuracy or completeness of the information. To the extent permitted by applicable law, CA provides this document as is without warranty of any kind, including without limitation, any implied warranties or merchantability, fitness for a particular purpose, or non-infringement. In no event will CA be liable for any loss or damage, direct or indirect, from the use of this document, including, without limitation, lost profits, lost investment, business interruption, goodwill, or lost data, even if CA is expressly advised of the possibility of such damages. 3

4 Abstract CA 7 Workload Automation r11.1 has improved methods for controlling workload across the enterprise. Cross-platform scheduling includes sending jobs via CCI (Common Components) to Universal Job Management Agents (XPJOB). These jobs are now defined directly to the CA 7 database. Come learn more ways to control Workload Automation within your enterprise. 4

5 Topics > Setting up the environment > XPJOB and Related Data Definition > XPJOB Submission > Conversion Process 5

6 Cross-Platform Internalization > Eliminate the need of CA7TOUNI z/os batch job to submit request to another platform > Provide better job routing abilities by dynamically altering target node based on availability > Provide automatic retry if communication failure > Provide better protection of the user ID and password data sent to the target node > Provide a high-availability option (HAO or failover) for XPJOB and CA7TOUNI job tracking if CA 7 fails > CA7TOUNI will continue to be supported 6

7 Setting up the environment 7

8 CA 7 Initialization File Changes > Existing Statements New Keywords SCHEDULE XPRETRY retry XPJOB submission for node failures DBASE DEFAULTXPS defaults for XPJOBs being added > New XPDEF statement Defines all cross-platform (XP) options for CA7ONL (online task) May override legacy XP keywords coded on SVCNO statement Defines whether XPJOB submission is allowed Defines user ID/password location options for XPJOBs 8

9 XPDEF Statement Format XPDEF,XSUBMIT={YES NO},SUBROOT={YES NO}, PSWDLOC=({DATABASE,OWNER,NODE,USER}), XMONITOR=CA7nXXX,XPHAO=name, XSERVER={YES NO},XSERVERTRC={YES NO}, XROUTER={YES NO},XPSTRC=(11), XPSSCHD={RUNREF RUN DEMAND}, XPKILL={YES NO},XTRKTRC= XSUBMIT={YES NO} allows XPJOB functions to occur (definition, submission, etc.) 9

10 XPDEF Statement Keywords (1) SUBROOT={YES NO} states whether a user can code the ROOT user ID (UNIX systems) PSWDLOC=({DATABASE,OWNER,NODE,USER}) states the hierarchy from which the user ID, password and optionally domain name can come from; no default XMONITOR=CA7nXXX* states the 7-character CCI monitor name associated with CA 7 used in cross-platform tracking; default shown; may be any name * Denotes keyword moved from SVCNO statement 10

11 XPDEF Statement Keywords (2) XPHAO=name states the 1- to 64- character Primary (HAO) name which must be unique across the CCI Network; if coded, HAO is activated for this MONITOR XSERVER={YES NO}* states whether this copy of CA 7 can receive cross-platform requests (XPS SUBMIT MONITOR); was previously combined with SVCNO MONITOR XSERVERTRC={YES NO} states whether tracing should be active for the server * Denotes keyword moved from SVCNO statement 11

12 XPDEF Statement Keywords (3) XROUTER={YES NO}* states if this CA 7 instance should act as the XPS SUBMIT ROUTER XPSTRC=(11) states the trace options for the server XPSSCHD={RUNREF RUN DEMAND}* indicates which command will be used to bring the routed work into the system XTRKTRC= states the trace options for the internal XPS tracker * Denotes keyword moved from SVCNO statement 12

13 Internal Tracker and HAO > CA 7 WA Cross-Platform Tracker (XTRK) currently runs as a subtask under CA7ICOM or as a separate address space > With r11.1, XTRK may execute as a subtask in the CA7ONL address space > Presence of XCKPT DD statement in CA7ONL JCL activates the internal XTRK > XPJOB and the HAO option requires internal XTRK > Commands passed to internal XTRK via /XTASK top-line command 13

14 /DISPLAY,ST=XPS /DISPLAY,ST=XPS *** Cross-Platform Scheduling Options *** DATE= TIME=09:30:19 CCI Local SYSID : A31SENF Host System SMFID : CA31 CA 7 Monitor Name : CA7CA75 CA 7 VTAM Appl ID : A31IL25 CA 7 HAO Primary : CA75PRIME CA 7 Instance Name: CA75 XPJOB Submit : Yes XPJOB PSWD Location: (DATABASE,OWNER,NODE,USER) XPJOB Submit ROOT : Yes XPJOB Kill : Yes XPJOB Tracker Task : Yes - Active Tracker Initial Trace : 11 XPS Router Task : No - Inactive Router Initial Trace : 11 XPS Server : Yes Server Initial Trace : Yes XPS Default Mode : RUNREF XPS Default ID : **NONE** 14

15 Job and Related Data Definition 15

16 JOB Screen Swap > Screens may be swapped if user requests the other job type User lists a CPU job from XPJOB screen; result is CPU job display on JOB (DB.1) screen User lists an XPJOB from a JOB screen; result is XPJOB job display on XPJOB(DB.10) screen User may delete jobs from either screen User may only request update from the same job-type screen (CPU JOB = DB.1, XPJOB= DB.10, AGJOB = DB.11) > Use LJCK command to validate cross-platform parameter data 16

17 XPJOB Definition: DB.10 or XPJOB CA-7 XP Job Definition Function: LIST (Add,DD,Delete,DELPRRN,Format,List,Purge,Update) Job: EROCTST1 System: EROCSYS JOBNET: Owner: UID: 0 XP Node: EROCTST XP EXEC: cau9test.exe XP PARM: Optional PARMLIB: Member: EXEC: Y SUTYPE: Y Cond-Code: 0 RO: 0 DRClass: Hold: N Verify: N Satisfaction Lead Time: 0 ARFSET: Clock Time: 0000 WLBClass: A WLBPRTY: 000 Trace: N Don't Schedule Before: After: Retain: N LTERM: MASTER Prompt: Y Rqmt List: Y Rqmts Not Used: Y PROGRAM: SM22 MSG-INDX: DB / 14:34:15 MESSAGE: LIST SUCCESSFUL 17

18 XPJOB Definition > New formatted screen accessed through DB menu or top-line command XPJOB or DB.10 > Node is the (primary) target node where the job should execute > EXEC is the file or script to be executed at the target node > XP PARM denotes PARM1 data, and may be overridden by PARMLIB PARM1 keyword 18

19 XPJOB PARM Data > PARMLIB is equivalent to JCLLIB and supports numeric JCLID as well as JCL Index (&-) In PARMLIB: PARM1= through PARM64= SUBUSER=, SUBPASS=,DOMAIN= LINELEN={AUTO 72 80} DPROC= to name the standard DPROC > Use the LJCK command to validate the XPJOB information that will be used to build the buffer that will be sent to the remote node DPROCs and Global Variables are permitted in PARMLIB 19

20 XPJOB User ID and Password Control > XPDEF,PSWDLOC= ({DATABASE,NODE,OWNER,USER}) DATABASE uses Owner-Access record created as a result of XPSWD command NODE uses Node-Access record created as a result of XPSWD command OWNER uses the OWNER field of XPJOB (no password or domain allowed) USER uses PARMLIB member SUBUSER, SUBPASS, and DOMAIN keywords 20

21 XPSWD (XN.2) Command CA-7 XPJOB User ID/Password Definition Function: LIST (Add, Delete, Format, List, Update) Owner: TESTPSWD or Node: User ID: testpswd Password: Reconfirm PSWD: Domain Name: (Password Present) (Windows platform) 21

22 Permanent and Temporary Nodes > Permanent Nodes: Defined to database via XNODE command Read and tabled at initialization time May have one or two Alternate Nodes defined where work may be routed to if primary (defined) node is unavailable > Temporary Nodes: Added because jobs routed to that agent Are not found in the database Cannot have any alternate nodes Cannot have any node user ID/password (i.e., XPSWD) List, then Add through XNODE to create permanent node 22

23 XNODE (XN.1) Screen Format CA-7 XPS Node Table Entry Function: LIST (Add, Delete, Format, List, Update) Node: TRODE05 Description: NODE USED FOR TESTING OF XPJ JOBS Alternate 1: Alternate 2: State: ONLINE (Online, Offline, Stop) PROGRAM: SMX1 MSG-INDX: XN.1 -- MESSAGE: This is a Permanent Node 23

24 Node States > User Controlled: ONLINE: node is available to receive XPJOBs OFFLINE: this particular node is not available to receive XPJOBs from a CA 7 viewpoint If alternate nodes are defined for this primary node, the XPJOB may be routed to the alternate node STOP: node and its alternates are not available to receive XPJOBs from a CA 7 viewpoint XPJOB is requeued to the Request Queue > CA 7 Controlled: FAIL: CA 7 tried to send an XPJOB but CCI returned errors If alternate nodes are defined for this primary node, the XPJOB may be routed to the alternate node XTRK: Internal XTRK subtask is not active 24

25 Node Error Displays and Retry > CA 7 requeues XPJOBs to Request Queue if unable to send XPJOB to a node MCNT=1: Only needs a RESTART action > LQ Display shows N-xxxx job status CA07XPQ0 REQ /1752 *NONE* 073/1752 XPJ- EROCXPJ1 REQ /1752 *NONE* 073/1752 XPJ- CA07XP06 REQ /1759 *NONE* 073/1759 XPJ- 001 DEMD 001 N-OFFL 001 DEMD 001 N-STOP 001 DEMD 001 N-FAIL > Schedule Scan parameter XPRETRY=nn (number of minutes from 1 to 60) retries jobs in Request Queues that are in an N-xxxx status XPRETRY=0 turns off XPJOB retry function 25

26 XPJOB Submission 26

27 XPJOB Submission > XPJOBs flow through the queues like CPU jobs as opposed to CA7TOUNI jobs Job feedback comes to CA 7 Internal Tracker (XTRK) task and job is moved to appropriate queue > XPJOBs can be scheduled, triggered, demanded or run > XPJOBs can *not* be LOADed or have CA-11 interface 27

28 XPJOB JCL and QJCL Commands > XPJOB edits will always present edit session in Mixed Case mode > PARM data, from XP PARM on job definition or from optional PARMLIB, can be edited through XQ/E or QJCL commands > JCL-ERR condition may occur from PARM data errors (unrecognizable keywords) or from executable file/security information from destination node (not found conditions) MCNT=2: PARM data correction and restart 28

29 CA7TOUNI Information > CA7TOUNI edit will always present edit session in Mixed Case mode > CA7TOUNI has new keyword XPHAO in support of the High Availability Option (HAO) XPHAO=primaryname HAO must be supported by Agent 29

30 Queue Update (XUPD) CA-7 Queue Maintenance - XPJOB Attributes Job: EROCXPJ1 CA-7#: 0731 MCNT: 001 Queue: REQ Scheduling Manual Requirements Deadline Time Job Held... N Due-Out Time Manual Verification Required.. N Submit Time... XP Node... EROCTST XP EXEC... calc.exe ----Resources Prompting Misc---- WLBClass... A Eligible for Prompts.. Y Retain... Y WLBPRTY Prompt Acknowledged... Y SUTYPE... Y Clock Time LTERM for Messages... MASTER PROGRAM: QM41 MSG-INDX: QM.3-X / 10:56:20 MESSAGE: Change desired fields or enter a command on the top line 30

31 XPJOB Topline Commands Overview New Commands > LNODE List entries in XPJOB Node Table Changed Commands > LJOB Select by type, node and list XPJOB data > LQ Select by type, status and list XPJOB data > LPRRN Select by type and list XPJOB data > LRLOG Select by type > REQUEUE Select by node > CANCEL Causes kill request to be sent to target node 31

32 Conversion Process 32

33 Conversion Process > The conversion process is used to convert existing CA7TOUNI cross-platform jobs to XPJOB-type jobs. > Conversion consists of two components: Conversion Utility is a batch process. It reads CA7TOUNI JCL members and creates the BTI commands. CONVERT command is part of BTI deck created by the Utility. It changes the CA7TOUNI job to an XPJOB within CA 7 WA. > Refer to Interfaces Reference Guide for process and assumptions 33

34 SOME Conversion Assumptions > CA7TOUNI JCL member name must match the CA 7 CA7TOUNI job definition If the same member does not exist in CA 7, the conversion fails or worse, wipes out a CA 7 job definition having the same name > CA7TOUNI job cannot have a SYSIN DD DSN= card, only in-stream data If SYSIN DD data sets must be run through the Pre- Conversion utility before the Conversion utility 34

35 CONVERT Command CONVERT command has two functions Create a back-up of the original job definition using RESTMASK parameter, if specified Update the existing member definition to an XPJOB definition. All requirements, triggers, etc. defined in the original CA7TOUNI job are still in effect. RESTORE command: Changes the XPJOB job definition back to the original CA 7 job definition using the RESTMASK backup member RESTORE,CASE022,BACKUP=CA$E022 Note: The original CA7TOUNI JCL must be copied from the backup (created in the Conversion Utility IEBCOPY step) to the appropriate CA 7 JCLLIB for each restored member. 35

36 Restore Mask (RESTMASK) > Defines 2-character value used to create a restore copy of the data base job definition NO RESTMASK = no backup! > Examples: RESTMASK=#3 for job CA7XJOB, backup = CA#XJOB RESTMASK=$4 for jobs CA71 and CA72, backup is the same CA7$ Beware of how you define what the RESTMASK value and position! 36

37 CA7TOUNI Before Conversion #7UNI //CASE022 JOB ( ,IGN),'CA-7.TOUNI',CLASS= // JCLLIB ORDER=(APCDAL.DEVCA7.CA11CA75.JCLLIB) //SUBMIT EXEC CA7TOUNI //PROFILE DD DSN=CAI.CA7.PROFILE,DISP=SHR //SYSIN DD * Node=TRODE05 SubFile=C:\WINDOWS\system32\calc.exe parm1= parm9= // 37

38 Results of CA7TOUNI Conversion DBM CONVERT,CASE022,BACKUP=CA$E022 XPJOB UPD,CASE022,NODE=TRODE05,EX1=(C:\WINDOWS\system32\calc.exe), SUTYPE=Y JCL DELETE,CASE022,DSN=APCDAL.DEVCA7.CA11CA75.B1ER.B1ER7TST JCL,CASE022 EDIT MIXED XSEQ I, parm1= parm9= $IEND SAVE SAVE,CASE022,DSN=APCDAL.DEVCA7.CA11CA75.B1ER.B1ER7TST CLEAR DBM XNODE ADD,TRODE05 38

39 Pre-Conversion Utility > To convert SYSIN DD data sets to in-stream data within CA7TOUNI jobs > Uses same PDS, containing CA7TOUNI jobs, that the conversion utility uses SAMPJCL XPJPCONV provides JCL > Output is a IEBUPDTE job that contains SYSIN to add each converted CA7TOUNI job to a new PDS > Keyword PDSDDDSN identifies original PDS to Conversion Utility 39

40 Summary > With CA 7 WA r11.1, XPJOB internalizes cross-platform scheduling > XPJOB does not use an JES initiator because the crossplatform request is sent directly from the CA 7 address space > Flexibility in that the job may be directed to an alternate agent if the primary agent is down > Enhanced protection of password data when user IDs are sent with the cross-platform request > Better recovery options for cross-platform jobs with HAO 40