CICS and Transactional VSAM

Transcription

1 IBM Software Group CICS and Transactional VSAM Ed Addison CICS Level2 WebSphere Support Technical Exchange

2 Agenda A brief overview of non-rls and RLS Introduction to Transactional VSAM Recoverable file sharing between CICS and batch IGDSMSxx Parmlib changes for Transactional VSAM Interfaces to Transactional VSAM Application Considerations Transactional VSAM user experience WebSphere Support Technical Exchange 2

3 Local Shared Resources before RLS When a task is updating a record in VSAM it has exclusive control of the entire Control Interval ƒall other tasks attempting to reference a record within the same Control Interval will be put into a FCXCWAIT (File Control Exclusive Control Conflict) until the first task completes the update ƒconsider a data set that has a 32K Control Interval size and 50 byte fixed records. 655 records can fit into the Control Interval. Consequently, there is a good chance another transaction will be locked out until the update has completed When a task is reading or browsing a record in VSAM it has shared control of the entire Control Interval ƒif another task wants to update a record in the Control Interval it will be put into a FCXCWAIT until all tasks are through reading or browsing WebSphere Support Technical Exchange 3

4 Local Shared Resources (LSR) VSAM Record Sharing Non-RLS Transaction Transaction EXEC CICS READ FILE(BIGG) RID(RECD) UPDATE EXEC CICS READ FILE(BIGG) RID(RECF) UPDATE X FCXCWAIT RECA RECD RECF RECJ VSAM Control Interval 4

5 File Sharing in CICS before RLS Function Shipping to File Owning Region (FOR) ƒlu62 connection from different MVS, or within the same MVS ƒmro connection within the same MVS ƒmro/xcf connection within the same Sysplex External CICS Interface (EXCI) ƒallows applications running in a non-cics environment to access CICS application programs Shared Data Tables ƒuses MVS cross-memory services to share a file between different CICS regions in the same MVS image Coupling Facility Data Tables ƒsharing of working data within a Sysplex with update integrity. ƒkeylength restriction of 16 bytes WebSphere Support Technical Exchange 5

6 CICS Function Shipping Before RLS AOR = Application Owning Region FOR = File Owning Region CICS AOR1 CICS AOR2 CICS AOR3 CICS AOR4 CICS FOR1 VSAM VSAM z/os 1 z/os 2 CICS FOR is a single point of failure WebSphere Support Technical Exchange 6

7 Introduction to Record Level Sharing Introduced in DFSMS R1.3 and exploited by CICS TS R510 and above Provides full VSAM data sharing between CICS regions within a Sysplex RLS mode is available for all VSAM files managed by CICS File Control VSAM data sets that are not managed by CICS File Control will not be supported in RLS mode ƒtransient Data Intrapartition data set ƒtemporary Storage data set ƒlocal and Global Catalogs RLS mode is determined at data set open time WebSphere Support Technical Exchange 7

8 Introduction to Record Level Sharing Once the data set is opened in RLS mode within CICS ƒrecord locking only, no Control Interval locking ƒall access to the data set must be in RLS mode within CICS VSAM allows read-only shareoption 2 opens with OW25251 applied. ƒdata set has to be quiesced throughout the Sysplex before switching to non-rls Every CICS region in the Sysplex that has the RLS data set open can close the data set to switch to non-rls - Data set can then be opened in RLS or non-rls mode One CICS region in the Sysplex can issue SET DSNAME( ) QUIESCED command - Data set can only be opened in non-rls mode until UNQUIESCE is issued VSAM is responsible for the locking CICS is responsible for the logging ƒsystem log for backout ƒforward recovery logs ƒautomatic journals WebSphere Support Technical Exchange 8

9 Locking in CICS Before RLS Locking in CICS before RLS ƒvsam acquires a Control Interval lock while an update request is active ƒafter the update is complete CICS will acquire a record lock if the data set was defined as recoverable ƒrecord locks are held until the transaction issues an explicit or implied SYNCPOINT ƒrecord locks are not known by other CICS regions ƒrecord locks are not known by VSAM WebSphere Support Technical Exchange 9

10 Locking with RLS Locks are VSAM managed Locks are Sysplex wide Locks are at the record level Update requests are queued until the lock is released For non-recoverable requests the lock is released at the end of the request For recoverable requests the lock is released at the end of a syncpoint WebSphere Support Technical Exchange 10

11 RLS and Recoverable Data sets Recoverable data sets participate in syncpoint protocols Changes made by a unit of work are all either committed forward or committed backward Recovery attributes for RLS have been moved to the VSAM ICF catalog ƒlog(undefined NONE UNDO ALL) ƒlogstreamid(log_stream_name) ƒbwo(undefined TYPECICS TYPEIMS TYPEOTHER) CICS will check for inconsistencies in catalog definitions at open time FCT defined recovery attributes are not used for RLS files ƒnon-rls files may also use the ICF catalog for recovery attributes LOG=UNDEFINED means get all attributes from FCT for non-rls Any other value for LOG means get all attributes from ICF catalog CICS never mixes some parameters from FCT with some parameters from ICF catalog WebSphere Support Technical Exchange 11

12 RLS and Recoverable Data sets Data set recovery options for files accessed in RLS mode must be specified in the VSAM ICF catalog. The following is an example of an IDCAMS DEFINE using the new keywords: DEF CLUSTER(NAME(USASSC1.CICSR620.RLSRECV) - CYLINDERS(10 2) - CISZ(8192) - FREESPACE(60 60) - INDEXED - KEYS(4 0) - RECORDSIZE( ) - STORAGECLASS(SXPXXS04) - LOGSTREAMID(USASSC1.IYNXV.DFHJ05) - LOG(ALL)) The type of recovery required for the VSAM Sphere is specified using the LOG parameter: NONE - The sphere is not recoverable UNDO - The sphere is recoverable for backout only ALL - The sphere is recoverable for both backout and forward recovery. A LOGSTREAMID is necessary or the open will fail WebSphere Support Technical Exchange 12

13 RLS and Recoverable Data sets If the LOG parameter is omitted when the data set is defined with IDCAMS to VSAM, recovery is assumed to be undefined and the data set cannot be opened in RLS mode If opening a non-rls data set and recovery attributes are defined in the ICF catalog via IDCAMS then the values in the ICF catalog are used. All values in the CICS FCT definition are ignored WebSphere Support Technical Exchange 13

14 RLS and Sharing Non-Recoverable Data sets Any number of CICS systems can concurrently update a non-recoverable RLS data set Any number of batch jobs can concurrently update a non-recoverable RLS data set WebSphere Support Technical Exchange 14

15 RLS and Sharing Recoverable Data sets Any number of CICS systems can concurrently update a recoverable RLS data set Any number of batch jobs can concurrently read a recoverable RLS data set A batch job may not open a recoverable data set in RLS mode for update To update a recoverable data set from a batch job, you must first quiesce RLS activity and update the data set in non-rls mode. Transactional VSAM allows batch to concurrently share a recoverable RLS data set with CICS WebSphere Support Technical Exchange 15

16 Introduction to Transactional VSAM RLS allows batch sharing of recoverable data sets for read ƒrls provides locking ƒcics provides logging and two-phase commit protocols Transactional VSAM (DFSMStvs) allows batch sharing of recoverable data sets for update ƒlogging is done by Transactional VSAM utilizing the MVS System Logger ƒtwo-phase commit and backout provided using MVS Recoverable Resource Management Services (RRMS) WebSphere Support Technical Exchange 16

17 Why Transactional VSAM? Addresses the batch window problem for CICS and batch sharing of VSAM data sets ƒa period of time when CICS access to recoverable data sets is quiesced so batch jobs can run ƒrequires taking a backup of the data set ƒbatch updates are then performed ƒa forward recovery backup is taken, if needed ƒwhen finished, CICS access to the data set is re-enabled Allows concurrent batch and CICS update access to recoverable data sets WebSphere Support Technical Exchange 17

18 Transactional VSAM Background Transactional recovery ƒallows a group of updates to a file or files to be associated with a Unit of Work (UOW) All are made or none are made Works the same as CICS and recoverable data sets ƒgroup of updates is called a transaction or Unit of Recovery (UR) ƒur is composed of all updates made between syncpoints ƒsyncpoint is a request to commit or backout updates WebSphere Support Technical Exchange 18

19 Prerequisites for Transactional VSAM DFSMStvs builds on the following components: VSAM Record-Level Sharing (RLS) System logger Recoverable Resource Management Services (RRMS) These three components work together to provide the three basic functions necessary for implementing transactional recovery WebSphere Support Technical Exchange 19

20 Prerequisites for Transactional VSAM z/os Version 1 Release 4 Note: RRMS and System Logger shipped in earlier releases of z/os DFSMS component of z/os Version 1 Release 4 CICS TS R530 with APAR PQ73635 CICS TS R620 with APAR PQ73745 CICS TS R630 Base CICSVR version 2 release 3 or higher WebSphere Support Technical Exchange 20

21 Recoverable Files: Sharing without TVS CICS AOR1 CICS AOR2 READ WRITE VSAM RLS Batch Job2 GET Batch Job1 CICS FUNCTION Transactional Recovery logging commit rollback/backout VSAM RLS Function Data Sharing locking buffer coherency READ/WRITE sharing across CICS AORs CICS provides transactional recovery and READ ONLY sharing with/across Batch Jobs WebSphere Support Technical Exchange 21

22 Non-Recoverable Files: Sharing CICS AOR1 CICS AOR2 VSAM RLS Batch Job1 Batch Job2 READ WRITE RLS Functions locking buffer coherency GET PUT NO TRANSACTIONAL RECOVERY (no logging, commit, backout) Read/Write sharing across CICS AORs and Batch Jobs WebSphere Support Technical Exchange 22

23 Recoverable File: Sharing with TVS READ CICS AOR2 WRITE CICS AOR1 CICS FUNCTION Transactional Recovery logging commit rollback/backout VSAM RLS & Transactional VSAM VSAM RLS Function Data Sharing locking buffer coherency Transactional VSAM VSAM RLS Function + Transactional Recovery logging commit rollback/backout Batch Job1 Batch Job2 GET PUT Batch Jobs Designed to Use Transactional Recovery Concurrent Read/Write Sharing of RECOVERABLE FILES Across CICS and Batch Jobs WebSphere Support Technical Exchange 23

24 IGDSMSxx Parmlib changes for Transactional VSAM AKP (default 1000) Specifies the activity keypoint trigger value, which is the number of logging operations between taking keypoints, for one or more DFSMStvs instances Much like the AKPFREQ DFHSIT parameter in CICS LOG_OF_LOGS (default none) Specifies the log stream to use as the log of logs MAXLOCKS (default 0,0) Specifies the maximum number of unique lock requests that a single unit of recovery can make before warning messages are issued IGW859I is put out when the initial value is reached and reissued every time the second value is reached QTIMEOUT (default 300 seconds) Specifies the quiesce exit timeout value WebSphere Support Technical Exchange 24

25 IGDSMSxx Parmlib changes for Transactional VSAM RLSTMOUT (default 300) Changed to include DFSMStvs. Specifies a timeout value for required locks SYSNAME (default none) Specifies the names of the systems on which DFSMStvs instances are to run TVSNAME (default none) Specifies the identifier of DFSMStvs instances that are to run in the sysplex TV_START_TYPE (default WARM) Specifies the type of start that each instance of DFSMStvs is to perform Note: See z/os MVS Initialization and Tuning Reference for greater detail for all these parameters WebSphere Support Technical Exchange 25

26 Changes to CICS for Transactional VSAM This page intentionally left blank because there are no changes within CICS for Transactional VSAM WebSphere Support Technical Exchange 26

27 Accessing a data set with Transactional VSAM Define VSAM data set as recoverable ƒlog (UNDO) ƒlog (ALL) Specify RLS access in the ACB or JCL ƒacb MACRF=RLS ƒjcl DD Statement RLS=NRI (No Read Integrity) RLS=CR (Consistent Read) RLS=CRE (Consistent Read Explicit) Example: DD DSN=USASSC1.OPENBTVS.KSDS,DISP=SHR,RLS=NRI Recoverable or non-recoverable data sets ƒopen with CRE Input or output open will be in Transactional VSAM Mode Recoverable data sets ƒopen for output open will be in Transactional VSAM mode WebSphere Support Technical Exchange 27

28 Application Interfaces: VSAM The table below shows the type of OPEN resulting from the parameters specified Left side shows the type of data set & type of open Column headings indicate the RLS option specified Data Set Type & Type of OPEN NRI CR CRE Recoverable Open for Input Recoverable Open for Output Non-recoverable Open for Input Non-recoverable Open for Output RLS RLS Transactional VSAM Transactional VSAM Transactional VSAM Transactional VSAM RLS RLS Transactional VSAM RLS RLS Transactional VSAM WebSphere Support Technical Exchange 28

29 Recovery Logging Overview Transactional VSAM uses the MVS System Logger to log changed data ƒigwlog.syslog ƒigwlog.shuntlog Must be unique logs for each instance of Transactional Vsam in the Sysplex Required logs, Transactional VSAM will not initialize if they are missing The forward recovery log name is an attribute of the data set ƒtaken from IDCAMS LOGSTREAMID parameter ƒmandatory if LOG(ALL) is specified on IDCAMS definition OPEN will fail if log is not found ƒcics will write to the same forward recovery log The Log of Logs ƒoptional logstream used by forward recovery products to quickly reconstruct damaged data sets contains tie-up records when data sets are opened and closed WebSphere Support Technical Exchange 29

30 Transactional VSAM Logging TranVSAM z/os System Logger CICS... TranVSAM z/os System Logger CICS OS/390 1 OS/390 n Coupling Facility CF List Structures for Logstreams CF automatic merging of Forward Recovery Logstreams WebSphere Support Technical Exchange 30

31 Application Interfaces: RRS Unit of Recovery (UR) identifier Provided by Resource Recovery Services (RRS) ƒpart of Recoverable Resource Management Services (RRMS) Application requests Commit/Backout via RRS interfaces ƒcall SRRCMIT or SRRBACK RRS drives Transactional VSAM RRS drives other resources managers (DB2,MQ,...) Commit or backout can be either explicit or implicit ƒexplicit by using RRS Interfaces SRRCMIT to commit updates SRRBACK to backout updates ƒimplicit at end of step / job WebSphere Support Technical Exchange 31

32 Batch Application Redesign Modify program / JCL to request Transactional VSAM access ƒspecify via JCL or ACB Break processing into a series of transactions ƒinvoke RRS for commit and backout Ensure multiple RPLs do not cause UR lock contention ƒrpl1 issues Get Update for key AAAA ƒrpl2 issues Get for key AAAA using RLSREAD option CR ƒrpl2 now waits until RPL1 commits Handle potential loss of positioning at sync point ƒcommit and backout causes release of all locks ƒjust like CICS applications Do not use file backup / restore as job restart technique Account for new VSAM Open, Close, and Logical error codes WebSphere Support Technical Exchange 32

33 Application Considerations Application must have transaction perspective when accessing shared VSAM files RLS and Transactional VSAM provide locking until commit / backout: ƒshare locks on records accessed with read option CRE ƒwrite locks on changed records - held until end of transaction Commit applies all changes and releases all locks Backout will undo all changes and release all locks Application should issue frequent sync points (commit or backout) Data extracted from shared files must not be used across commit / backout ƒneed to re-access the record(s) ƒcannot get a record before a sync point and update it after ƒdo not position to a record before a sync point and access it after Same as CICS application WebSphere Support Technical Exchange 33

34 Application Considerations Exclusive control of resources ƒunit of Recovery updating a record in a recoverable data set has locks until commit / backout / termination ƒother Units of Recovery wanting the records will be locked out Browsing ƒbatch jobs historically issue Get Update (for read integrity) and move to the next record without issuing Put Update ƒuse RLS Read options CR or CRE instead Remember, CRE keeps a shared lock until commit / backout / termination Avoiding deadlocks ƒa deadlock will occur if two URs both need exclusive control of the same record For example, UR A holds record 1 and wants record 2, while UR B holds record 2 and wants record 1 In order to avoid this type of deadlock, it is important that applications access resources in a predictable order WebSphere Support Technical Exchange 34

35 Non-Shared Vs Shared: Job Rerun Non-Shared Shared Copy Changes If failure, restore from Copy and rerun job(s) Changes Changes Changes If failure, uncommitted changes backed out. Committed changes remain File Level Isolation/Recovery Transaction Level Isolation/Recovery WebSphere Support Technical Exchange 35

36 Transactional VSAM User Experience WebSphere Support Technical Exchange 36

37 IDCAMS Data set Definition //DEFKSDS JOB ,'DEFGENDEL', // CLASS=A,MSGCLASS=C,NOTIFY=USASSC1 //* /*ROUTE PRINT H //ALLOC EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=A //SYSIN DD * DELETE (USASSC1.OPENBTVS.KSDS) CLUSTER SET LASTCC=0 SET MAXCC=0 DEFINE CLUSTER(NAME(USASSC1.OPENBTVS.KSDS) - STORAGECLASS(SXPXXS04) - LOG(ALL) - LOGSTREAMID(USASSC1.IYNXV.DFHJ05) - INDEXED KEYS(4 0)) - DATA (NAME(USASSC1.OPENBTVS.KSDS.DATA) - CYLINDERS(1,1) - CONTROLINTERVALSIZE(4096) - SHAREOPTIONS(2 3) - FREESPACE(10 10) - RECSZ( )) - INDEX (NAME(USASSC1.OPENBTVS.KSDS.INDEX) - CONTROLINTERVALSIZE(512) - TRACKS(1) - SHAREOPTIONS(2 3)) 37

38 Change Batch Job to Open as RLS Option 1: Change JCL //G.F1 DD DSN=USASSC1.OPENBTVS.KSDS,DISP=SHR,RLS=NRI Option 2: Change ACB ACB2 ACB AM=VSAM,DDNAME=F1,BUFND=14,BUFNI=3, MACRF=(KEY,DIR,IN,OUT,RLS),STRNO=14 X WebSphere Support Technical Exchange 38

39 Open Recoverable data set in batch without Transactional VSAM IEC161I ,OPENBTVS,G,F1,,,USASSC1.OPENBTVS.KSDS, RC-009: SMSVSAM Address Space is not available PDF778 CONSTANT(778), /* IDAV194A - TVS not available /D SMS,TRANVSAM IGW800I DFSMS VSAMRLS REQUEST TO DISPLAY TRANSACTIONAL VSAM INFORMATION IS REJECTED: TRANSACTIONAL VSAM IS NOT ACTIVE ON THIS SYSTEM WebSphere Support Technical Exchange 39

40 Open Recoverable Data set in batch with Transactional VSAM /D SMS,TR ANVSAM,ALLLOGS DISPLAY SMS,TR ANSACTION AL VSAM - SERVER STATUS System TVSN AME State Rrs #Urs Start AKP QtimeOut MV23 IGWTV003 ACTIVE REG 0 WARM/WARM DISPLAY SMS,TR ANSACTION AL VSAM - LOGSTREAM STATUS LogStreamName State Type Connect Status IGWTV003.IGWLOG.SYSLOG Enabled UnDoLog Connected IGWTV003.IGWSHUNT.SHUNTLOG Enabled ShuntLog Connected Output from SYSLOG for job IGW474I DFSMS VSAM RLS IS CONNECTING TO TRANSACTIONAL VSAM LOGSTREAM USASSC1.IYNXV.DFHJ05 SYSTEM NAME: MV23 TRANSACTIONAL VSAM INSTANCE NAME: IGWTV003 IGW474I DFSMS VSAM RLS IS DISCONNECTING FROM TRANSACTIONAL VSAM LOGSTREAM USASSC1.IYN XV.DFHJ05 SYSTEM N AME: MV23 TRANSACTIONAL VSAM INSTANCE NAME: IGWTV003 WebSphere Support Technical Exchange 40

41 Open Recoverable Data set in batch with Transactional VSAM /D SMS,DSNAME(USASSC1.OPENBTVS.KSDS) IGW805I DFSMS REQUEST TO DISPLAY TRANSACTIONAL VSAM USAGE OF DATASET: USASSC1.OPENBTVS.KSDS WAS REJECTED. DATASET NOT KNOWN TO TRANSACTIONAL VSAM. /D SMS,JOB(OPENBTVS) IGW801I DFSMS REQUEST TO DISPLAY TRANSACTIONAL VSAM USAGE OF JOB: OPENBTVS WAS REJECTED. JOB IS NOT KNOWN TO ANY TRANSACTIONAL VSAM INSTANCE IN THE SYSPLEX. Job had finished running so it is no longer known to Transactional VSAM WebSphere Support Technical Exchange 41

42 Insert wait for active Unit of Recovery -D SMS,TRANVSAM,ALLLOGS IGW800I DISPLAY SMS,TRANSACTIONAL VSAM DISPLAY SMS,TRANSACTIONAL VSAM - SERVER STATUS System TVSNAME State Rrs #Urs Start AKP QtimeOut MV23 IGWTV003 ACTIVE REG 1 WARM/WARM DISPLAY SMS,TRANSACTIONAL VSAM - LOGSTREAM STATUS LogStreamName State Type Connect Status IGWTV003.IGWLOG.SYSLOG Enabled UnDoLog Connected IGWTV003.IGWSHUNT.SHUNTLOG Enabled ShuntLog Connected USASSC1.MV23.DFHLGLOG Enabled LogOfLogs Connected USASSC1.IYNXV.DFHJ05 Enabled FrLog Connected Now, Log of Logs and Forward Recovery Log show on the display WebSphere Support Technical Exchange 42

43 Insert wait for active Unit of Recovery /D SMS,DSNAME(USASSC1.OPENBTVS.KSDS) IGW805I DISPLAY SMS,DSNAME DATASET: USASSC1.OPENBTVS.KSDS IS CURRENTLY IN USE BY THE FOLLOWING JOBS: System Name: MV23 TVSNAME: IGWTV003 JobNames: OPENBTVS /D SMS,JOB(OPENBTVS) IGW801I DISPLAY SMS,JOB TRANSACTIONAL VSAM Job Status On System: MV23 JobName StepName Urid Ur Status # Locks OPENBTVS G BABEEE3A7E D In-flight 99 WebSphere Support Technical Exchange 43

44 Open same data set in CICS I FILE(OPENBTVS) STATUS: RESULTS - OVERTYPE TO MODIFY Fil(OPENBTVS) Vsa Ope Ena Rea Upd Add Bro Del Sha Rls Dsn( USASSC1.OPENBTVS.KSDS ) Issue Read for Update on record in Unit of Recovery DFHFC /23/ :41:11 IYNXV RDUP TC39 CICSUSER. A request has timed out waiting for an RLS lock. There are 1 transactions or Transactional VSAM units of recovery holding this lock. DFHFC /23/ :41:11 IYNXV RDUP TC39 CICSUSER. Transactional VSAM unit of recovery X'C D D ' running in job OPENBTVS on Transactional VSAM instance 003 in MVS MV23 holds exclusive lock on key X'C1C1C1C3' in data set USASSC1.OPENBTVS.KSDS causing true contention. WebSphere Support Technical Exchange 44

45 CECI Read for Update for record not in Unit of Recovery READ FILE(OPENBTVS) RID(AAAA) UPDATE STATUS: COMMAND EXECUTION COMPLETE NAME= EXEC CICS READ File( 'OPENBTVS' ) < SYsid() > ( SEt() Into( 'AAAA RECORD ONE' ) ) < Length( ) > RIdfld( 'AAAA' ) < Keylength() < GEneric > > < RBa RRn DEBRec DEBKey > < GTeq Equal > < UNcommitted Consistent REpeatable UPdate < Token() > > < Nosuspend > RESPONSE: NORMAL EIBRESP= EIBRESP2= PF 1 HELP 2 HEX 3 END 4 EIB 5 VAR 6 USER 7 SBH 8 SFH 9 MSG 10 SB 11 SF WebSphere Support Technical Exchange 45

46 Batch job needing record lock owned by CICS Note: RLSTMOUT set to 60 seconds IGW10070I OPENBTVS G C D A REQUEST TIMED OUT WAITING FOR A LOCK. THERE ARE 1 UNITS OF RECOVERY HOLDING THIS LOCK. IGW10071I SUBSYSTEM NAME IYNXV TRANSACTION ID C D RUNNING IN JOB IYNXV HOLDS EXCLUSIVE LOCK ON KEY IN BASE CLUSTER NAME USASSC1.OPENBTVS.KSDS CAUSING TRUE CONTENTION. KEY VALUE = C1C1C1C5 IGW10103I JOB OPENBTVS STEP G UNIT OF RECOVERY C D FAILED. BACKOUT WAS SUCCESSFUL WebSphere Support Technical Exchange 46

47 Adding RRS SRRBACK Macro BACKOUT EQU * WTO ' ALL RECORDS LOADED ' XC ECB,ECB WTOR 'BATCHTVS REPLY Y TO END WAIT',REPLY,1,ECB WAIT ECB=ECB CALL SRRBACK,RETCODE,LINKINST=BASSM L R8,RETCODE LTR R8,R8 BZ RETURN ABEND 060,DUMP //L.SYSLIB DD DSN=SYS1.CSSLIB,DISP=SHR // DD DSN=SYS1.MACLIB,DISP=SHR WebSphere Support Technical Exchange 47

48 IDCAMS Prints of data set during and after SRRBACK Macro KEY OF RECORD - C1C1C C1C1C C1C1C *AAB...AAB...* C1C1C *AAB... * KEY OF RECORD - C1C1C C1C1C C1C1C *AAB...AAB...* C1C1C *AAB... * IDC0005I NUMBER OF RECORDS PROCESSED WAS 99 IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0 IDCAMS SYSTEM SER VICES TIME: 03:52:57 02/23/07 PAGE 13 IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 0 LISTING OF DATA SET -USASSC1.OPENBTVS.KSDS IDC0005I NUMBER OF RECORDS PROCESSED WAS 0 IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0 IDCAMS SYSTEM SERVICES TIME: 03:58:19 03/23/07 PAGE 3 IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 0 WebSphere Support Technical Exchange 48

49 Conflicting Opens of Data set Try to open in batch TVS with CICS already opened in non-rls: IEC161I ,OPENBTVS,G,F1,,,USASSC1.OPENBTVS.KSDS,, IEC161I ICFCAT.SYSPLEX1.CATALOGA ccc = RLS processing requested but RLS Sphere already opened for non-rls processing Try to open with CICS non-rls while batch TVS is active: IEC161I ,IYNXV,CICS620,,,P1P100,USASSC1.OPENBTVS.KSDS,, IEC161I ICFCAT.SYSPLEX1.CATALOGA cc = Non-RLS output processing requested but sphere already opened for RLS processing. WebSphere Support Technical Exchange 49

50 Transactional VSAM Summary Addresses long standing CICS batch window requirement Provides read and write access across multiple CICS and batch jobs for recoverable data sets Major step towards 24 x 7 CICS online availability Uses RRS as syncpoint manager Uses z/os System logger for data changes Uses RLS for locking Requires redesign of existing batch jobs to ensure they play well in the data sharing environment WebSphere Support Technical Exchange 50

51 Additional WebSphere Product Resources Discover the latest trends in WebSphere Technology and implementation, participate in technically-focused briefings, webcasts and podcasts at: Learn about other upcoming webcasts, conferences and events: Join the Global WebSphere User Group Community: Access key product show-me demos and tutorials by visiting IBM Education Assistant: Learn about the Electronic Service Request (ESR) tool for submitting problems electronically: Sign up to receive weekly technical My support s: WebSphere Support Technical Exchange 51

52 Questions and Answers WebSphere Support Technical Exchange 52