Pre-Con Ed: CA Workload Automation iDash for CA Workload Automation CA 7 r12 – Architecture, Usage...

Preview:

Citation preview

World®’16

CAWAiDashforCA7ArchitectureandTroubleshootingBillSherwinSeniorPrincipalConsultantCATechnologies

MFX15E

MAINFRAMEANDWORKLOADAUTOMATION

2 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

©2016CA.Allrightsreserved.Alltrademarksreferencedhereinbelongtotheirrespectivecompanies.

Thecontentprovidedinthis CAWorld2016presentationisintendedforinformationalpurposesonlyanddoesnotformanytypeofwarranty. The informationprovidedbyaCApartnerand/orCAcustomerhasnotbeenreviewedforaccuracybyCA.

ForInformationalPurposesOnlyTermsofthisPresentation

3 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

Abstract

This session introduces the new CA WA CA 7 Edition Server for iDash architecture, describingwhat needs to be implemented in z/OS and the configuration requirements for CA WA CA 7 thatare required to support integration with a CA iDash server.

The session will also include an overview of the communication methodology between the CAWA CA 7 Edition Server for iDash and a CA WA iDash instance and cover some basictroubleshooting of communication and connectivity issues between these components.

In addition, the session provide a summary of the additional CA WA CA 7 specific functions thatwere introduced with the CA iDash r12.0.01 incremental, such as SCHID=0 support, CA 7 JobLinks and the inclusion of Dataset Requirements in Flow Views, as well as insights into CA 7specific functionality under development for the CA WA iDash r12.0.02 incremental.

A detailed demo of CA WA iDash for CA 7 will be available in the CA World Exhibition Hall.

BillSherwin

CATechnologiesSeniorPrincipalConsultant

4 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

Agenda

CA7SERVERFORIDASHARCHITECTURE

CONFIGURINGFORTHEZ/OS COMPONENTS

MAXIMUMSIX(6)WORDSPERBULLET

IDASHCOMMUNICATIONMETHODOLOGY

TROUBLESHOOTINGCOMMUNICATIONS

IDASHFORCA7R12NEWFUNCTIONALITY

1

2

3

4

5

6

5 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

CA7ServerforiDashArchitecture

6 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

CAWAiDashforCA7ComponentOverview

7 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

CA7ServerforiDashComponent

§ ReplacestheJobFlowMonitorcomponentforiDashusage– JobFlowMonitornowonlyusedforCA7WebClientGUI

§ SimplifieddesignstreamlinedspecificallyforiDashdatafeed

§ AccessesCA7DatabaseforinitialiDashseeddata

§ SubscribestoENFCA7LOGrecordsfortransmissiontoiDash– IncludesjobstatuschangestomaintainSLAjobstatus– ProvidesalldatabasechangestomaintainiDashstoredjobdata

§ MaintainsiDashsubscriptioninformationforcheckpointing

8 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

CA7MaintenanceRequirements

§ ThefollowingPTFs,ataminimum,mustbeappliedtoCA7R11.3– RO87252– RO87253

§ ThesePTFscreatetheCA7ServerforiDash solutionwhichwasdevelopedbasedoncustomerandinternalbusinessfeedback

– Allpre-requirementsfortheabovemaintenancemustbeapplied

§ BestpracticeistoensureCA7FMIDsareatthemostcurrentpublishedmaintenancelevel

9 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

Configuringthez/OSComponents

10 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

CA7INITDeckChanges

§ SVCNOstatementrequiresCA7=parametersettoCA71-CA78– AnyAliasnameusedheremustnowbesetviaCAIRIMADDCA7n

initialisationstatement

§ UCC7VTAMstatementmustincludeTCPTPORT=nnnnnparametersettoassignedportnumber

§ OPTIONSstatementrequiresJFM=YESparameter

§ Use/DISPLAY,ST=CA7toconfirmCA7configurationchanges

11 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

Use/DISPLAY,ST=CA7toConfirm

AssignedPORTnumberTCPIPfieldsset

CA7InstanceName

JMF=YESset

12 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

CACommonServicesRequirements

§ Ifnotalreadyconfiguredthefollowingisrequired

§ ImplementaCADatacom/ADMUFtosupportENFDB

§ CA7LOGENFEventsActiveandRecorded(CAL2DCM3)

§ CCSmustbeatleastatr14.1plusPTFRO67888

§ PreferablyensureCCSisatmostcurrentmaintenancelevel

13 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

ENFSettingsforENFDBUsage

DBspecified

RECORD(YES)

14 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

CA7LOGENFEventDefinition

CA7LOGENFEventActive

RecordedPurge

RetentionPeriod

DCMisCAL2DCM3

15 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

CA7ServerforiDashConfiguration

§ STCsettoREGION=0MandMEMLIMIT=NOLIMIT

§ ProgramExecutionPARM=‘PMEMPFX=IDASH’(optional)– PermitsmultipleSTCstousesameparameterlibrary

§ FiveconfigurationmembersperSTCallwithsameprefix– IDASHAS Addressspacesettings– IDASHEV Eventcaptureandsubscriptionsettings– IDASHMN CA7instancemonitoringspecification– IDASHIP TCPIPPortdefinition– IDASHCEE CEEDUMPsettings

16 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

CA7ServerforiDashParameters

Definesseeddatalocation

SetENFforEvents

DefinesiDashsubscriptionlocation

CA7Instance

AssignedPort

VariousDUMPsettings

17 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

iDashAdminToolCA7InstanceDefinition

CA7Instancez/OSTCPIPAddress

CA7ServerforiDashPort

z/OSLPARTimeZone

18 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

SecuritySettings

§ FACILITYspecifiestheResourceClassforsecuritycalls– NONEbypassesallresourcechecks

§ iDashUserauthorisedfor/LOGONand/DISPLAYcommands– UserIDusedforiDashconnectiontoCA7ServerforiDash– Recommendsettonon-expiringpassword– ConfigurediniDashCA7Instancedefinition– CA7InstanceverificationchecksuserIDauthority

ResourceClasstouse

19 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

iDashAdminToolCA7InstanceDefinition

iDashUserIDandPasswordforCA7Instance

VerifyCA7Instance

20 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

TCPIPNetworkConsiderations

§ TCPIPPortsforCA7andCA7ServerforiDashrequired– z/OSNetworkTeamusuallyassignsportnumbers

§ RecommendusingVirtualIPAddressingforSTCs– SimplifiesmovingCA7componentsifrequired

§ CheckforfirewallbetweeniDashservermachineandLPAR– RequestassignedCA7ServerforiDashportopenedbidirectionally

§ ForTCPIPusageSTCUserIDsrequiresecurityOMVSsegment

21 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

iDashCommunicationMethodology

22 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

CommunicationFormat

§ CommunicationinitiatedbyCAWAiDashserver

§ UsesXMLformsforallconversations

§ VerificationofCA7Instancedefinitioncreatessubscription

§ SubscriptionstoredasXMLforminUSSlocation

§ VerificationinitiatesCA7Databaseextractforseeddata

§ SeeddatastoredascompressedXMLforminUSSlocation

23 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

USSDirectoryRequirements

§ USSfilelocationanddirectorystructurepre-defined– Examplewouldbe/nfs/workload/iDash/

§ Directory/jfmd1/CA7xusedforseeddataforCA7Instance

§ Directory/jfmsubd1usedforalliDashserversubscriptions

24 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

TroubleshootingCommunications

25 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

iDash log foldererror.log – only problem output

info.log – all logging

Tomcat log foldercatalina.log – useful TCP/IP info

localhost.log – webapp info

localhost_access_log.txt –

all HTTP traffic to this host

Server app logCAJFLOG – all logging

JESMSGLG – basic app output

LogstoUseandLocation

26 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

iDashLogs

§ TheselogsareallfoundundertheinstalldirectoryofiDash:– [customerinstallpath]/CA/idash/log

§ Thisisyourfirststopforanytroubleshooting

§ Withintheselogsyoucanfindhintsofbothinternalandexternalissuessuchas:– iDashprocessingerrors(includingseeddata,andevents)– Communicationerrors– Queryresponsesfromthemainframe– andmore!

27 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

iDash - ErrorScenarios CORRECTIONNEEDEDUpdatewithbetterscreenshot

28 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

iDash ErrorScenarios– Cont. CORRECTIONNEEDEDUpdatewithbetterscreenshot

29 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

TomcatLogs

§ TheselogsareallfoundundertheinstalldirectoryofiDash:– [customerinstallpath]/CA/idash/tomcat8/logs

§ TheselogsareusefulforcatchingproblemswheniDash andexternalcomponentsarehavingtroublecommunicating.

§ WithintheselogsyoucanfindhintsofTCP/IPissuessuchas:– Tomcatporterrors(iDashwasalreadystarted,somethingelsehasthe

port,etc)– Communicationerrors– SSLandHTTPScertificateissues

30 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

TomcatErrorExamples CORRECTIONNEEDEDUpdatewithbetterscreenshot

31 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

MainframeServer– ApplicationLogs

§ TheselogsareallfoundintheCA-7ServerforiDash taskspools.

§ UsedforcatchingproblemswheniDashdoesn’tseemtoknowaboutjobdefinitionsoraboutworkloadevents.

§ Hereyoucanfindinformationonsubscriptionsandevents:– iDash subscriptionstatus– Eventdatapushattempts– Communicationerrors– SSLandHTTPScertissues

32 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

JESMSGLG

§ Thisisthemainspoolwhichwillalwaysbeavailable.

§ Ifyoudon’tseethesemessages,inthisgeneralorder,thenthemainframeapplicationisnotconfiguredcorrectly!

§ Takespecialnoteofthehighlightedareas:

CORRECTIONNEEDEDUpdatewithbetterscreenshot

33 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

STATUSCommand

§ UsetheSTATUScommandtogetaverbosedumpofalltheapplication’sstate,includingeveryiDashsubscriptionitisservicing.

§ Thissubscriptioninformationisyour‘healthcheck’foriDash!

CORRECTIONNEEDEDUpdatewithbetterscreenshot

34 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

WheretoStart

35 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

Easy as 1,2,3…iDash health1. Check the instance

definition

a) Push the Test icon, look for an error response

b) Is the z/OS system name filled in?

c) Is the Protocol HTTP?

2. Check for a seed data file

a) [customer install path] /CA/idash/dat/ca7/ [instance definition ID]/

b) Are there lots of delta files?

Mainframe health1. Are there any error or

warning messages visible in the CA-7 Server task?

2. Issue a STATUS commanda) Is there a subscription for

your iDash?

i. Is it PUSH/LIVE?

ii. Is it in CATCHUP?

iii. Does the IP address match the one you use to open the iDashinterface?

b) Do you see extra subscriptions?

i. Are they named ‘(Cancelled)’?

Next Steps…1. Can you find any known

problem log strings in the iDash or Tomcat logs?

2. Activate the CA-7 Server internal log and collect one hour of log

a) Can you find any known problem log strings with an ISPF FIND?

3. Is the CA7 task active?a) Is its ICOM active?

4. Can you ping the mainframe from the iDashhost, and vice versa?

36 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

…or maybe A,B,CiDash resetA. Simple Reset

1. Delete the instance definition

2. Redefine with the exact same label

B. Full Reset

1. Delete the instance definition

2. Shut iDash down

3. Delete the directory: [customer install path] /CA/idash/dat/ca7/ [instance definition ID]/

4. Start iDash

5. Redefine the instance

Mainframe resetA. Simple Reset

1. Recycle the CA-7 Server task

2. Allow all recovery threads to complete

B. Full Reset

1. End the CA-7 Server task

2. Delete the contents of the PATHNAME and EXTRACTPATH directories

3. Start the CA-7 Server task

Next Steps…A. Perform a Full Reset for both

iDash and Mainframe:

1. Mainframe Full Reset Steps 1 and 2

2. iDash Full Reset (all steps)

3. Mainframe Full Reset Step 3

B. Last Resort:

1. Gather all required doc per the instructions in the next section

2. Open a Support case

37 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

iDash Datau A zip file containing the entire iDash

log directory:[customer install path]/CA/idash/log/

u A zip file containing the entire Tomcat logs directory:[customer install path] /CA/idash/tomcat8/logs/

Mainframe Datau A text file containing the entire

output of the CA-7 Server for iDashtask:u All spools (JESYSMSG, CAJFLOG,

etc…)

u Ensure that the JESYSMSG includes at least one STATUS command output

u Ensure that there is at least one hour of logging at LOGLEVEL(3)

u A text file containing the entire output of the CA7ONL task

Necessary logs and other items…

38 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

iDashforCA7r12NewFunctionality

39 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

CA7DynamicSchID SLAs– Incrementalr12.0.01

§ PreviouslyCA7SLAdefinitionsrequiredaspecificSCHID

§ CannowdefineanSLAwithSchID of0

§ SignifiesthatanySchID runofthejobswillmeetrequirements

§ UsefulwhendifferentSchIDs areusedfordifferentdays

§ EliminatesneedformultipleSLAs,oneforeachday

§ Providesmoreflexibility

40 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

UsingtheCA7DynamicSchID Option

UseSCHID0tosignifyanySCHIDwillmeetthe

requirement

41 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

CA7JobLinks– Incrementalr12.0.01

§ ApplicationsmayrequirelinksnotdefinedinCA7

§ Examplecouldbeanapplicationspreadacross2schedulers

§ Applicationpartonetriggersworktoruninanotherscheduler

§ OtherschedulertriggersbackApplicationparttwo

§ UseCA7JobLinkstoconnectthetwoseparateparts

§ CanspecifyasTriggerorRequirement(Dependency)type

42 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

CA7JobLink– Trigger

43 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

CA7JobLink– Requirement

44 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

CA7JobLinks– SLAFlowViewConnection

45 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

SLAFlowViewCA7Datasets– Incrementalr12.0.01

DatasetTriggersandDependenciesnowinFlowView– r12.0.01CA7Dataset

NameandInformation

46 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

CA7SpecificUpdatesCominginIncrementalr12.0.02

§ EEMAuthorisationoptionforHybridiDashenvironments

§ ConditionalDependencysupport

§ NegativeDependencySupport(MUTEX)– Allowswildcardformatforjobnames– OptiontoexpandNegativeDependencyFlows(defaultFalse)

§ ProgressiveloadingofjobsinSLAFlowView

47 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

RecommendedSessions

SESSION# TITLE DATE/TIME

ABC123DE Magnaconsectet atlor ipustie modolore 11/16/2016at10:00am

FGH456IJ Magnaconsectet atlor ipustie modolore 11/17/2016at11:00am

FGH456IJ Magnaconsectet atlor ipustie modolore 11/18/2016at12:00pm

CORRECTIONNEEDEDUpdatewithSessionDetails

48 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

MustSeeDemos

DemoNameProductXTheater#location

DemoNameServicesYTheater#location

DemoNameSolutionYTheater#location

DemoNameProductXTheater#location

CORRECTIONNEEDEDUpdatewithDemoDetails

49 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

Questions?

50 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD

Thankyou.

Stayconnectedatcommunities.ca.com

Recommended