<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Swathi Javvaji on Medium]]></title>
        <description><![CDATA[Stories by Swathi Javvaji on Medium]]></description>
        <link>https://medium.com/@swathi-javvaji?source=rss-229aa231b240------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*7Wy8BE1O7WDzBPyl</url>
            <title>Stories by Swathi Javvaji on Medium</title>
            <link>https://medium.com/@swathi-javvaji?source=rss-229aa231b240------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 19:41:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@swathi-javvaji/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[CICS in a nutshell]]></title>
            <link>https://swathi-javvaji.medium.com/cics-in-a-nutshell-bce73d7356c1?source=rss-229aa231b240------2</link>
            <guid isPermaLink="false">https://medium.com/p/bce73d7356c1</guid>
            <dc:creator><![CDATA[Swathi Javvaji]]></dc:creator>
            <pubDate>Tue, 01 Mar 2022 16:09:50 GMT</pubDate>
            <atom:updated>2022-03-01T16:09:50.952Z</atom:updated>
            <content:encoded><![CDATA[<p>When a Modern Mainframe DevOps Engineer works on legacy products it is adequate to know the basics in order to support or maintain them. However, when the developer has to come out of the comfort zone to enhance the product with the core mainframe technology, it is nerve-wracking without proper guidance or exposure.</p><p>I was in a similar situation and had to do a lot of research to find out <em>“what to learn and what was important”</em> in CICS. I would like to share my journey of learning CICS in brief.</p><p>I started off by researching on the internet, reading <a href="http://www.redbooks.ibm.com/abstracts/crse0303.html?Open">redbooks</a>, watching <a href="https://www.youtube.com/watch?v=f574xv55cjA">YouTube</a> channels, and asking around for help. It was time taking and I felt lost. I even signed up for interskill, <a href="https://www.udemy.com/course/mainframe-cics-beginner-to-expert/">udemy</a> courses for learning.</p><p>After gaining a basic understanding of CICS, I felt one has to learn the below topics to understand CICS.</p><h4>What is CICS?</h4><p>CICS (Customer Information Control System) is a system, which allows users to develop and execute online applications in an MVS environment. It is a command-level language that consists of a set of commands, coded in the Procedure Division.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*z40OL9iD9IiI65I-H9f5LQ.png" /><figcaption>Sample code from a COBOL program</figcaption></figure><h4>Why CICS?</h4><p>Using CICS, users can share their applications, program, and data files. The system is simple, robust, and compatible. CICS is used by the online banking system, insurance companies, and airline reservation systems. CICS programs can be written in COBOL, Assembler, PL/I, C, C++, Java…</p><h4>Features of CICS</h4><p>CICS is OLTP (Online Transaction Processing system) which means it is an online system consisting of transactions.</p><blockquote>A transaction is a logical unit of work, which is initiated by a single request that may affect one or more objects.</blockquote><p>It is an Operating System in itself with its own processors, file management systems, test manager and provides DB/DC facilities.</p><h4>What are the major components in CICS?</h4><p>Data Communication Functions: It is the interface between CICS and terminals.</p><p>Data Handling Functions: Interface with Data Access Methods such as VSAM and Database Access Methods such as DB2, IMS/DB, IDMS.</p><p>Application Program Services: Interface with COBOL, PL/I, Assembler programs.</p><p>System Services: Interface between CICS and operating system. Also storage control such as acquiring and freeing resources.</p><p>Monitoring Functions: Monitors various events within CICS and provides statistics.</p><figure><img alt="Structure of the components" src="https://cdn-images-1.medium.com/max/975/1*UgEbstn8q1SjegPF73NxCA.png" /><figcaption>Structure of different components</figcaption></figure><p>Since we understand by now that CICS is mainly comprised of transactions, what exactly is a transaction, and what are the default system-defined transactions.</p><p><em>A transaction is a unit of work that is done as an atomic operation and is identified by a four-character ID like T4Z0, T4Z1, T4Z2 that are user-defined. Some of the system-defined transactions are CEMT, CEDA, CEDF, CECI, CEBR, CESF, and CESN. (Usually starting with letter “C”)</em></p><p>CEMT — CICS Execute Master Terminal</p><p>CEDA — CICS Execute Definition and Administration</p><p>CEDF — CICS Execute Debug Facility</p><p>CEBR — CICS Execute Browse</p><p>CESN — CICS Execute Sign-On</p><p>CECI — CICS Execute Command Interpreter</p><p>CMAC — CICS Messages for ABEND Codes</p><p>CESF — CICS Execute Sign Off</p><p>A transaction is initiated by using the TRANSID. Once a transaction is initiated, a lot of programs are invoked internally for the transaction to work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/563/1*uKDl5CV4cGtCm866aM3qyA.png" /><figcaption>CICS Nucleus</figcaption></figure><p>TCP, KCP, PCP, FCP are all CICS control programs.</p><h4>Control Programs in CICS</h4><p>Program Control Program (PCP): It governs the flow between CICS and CICS application programs.</p><p>File Control Program (FCP): It provides manipulation services to the application programs.</p><p>Terminal Control Program (TCP): It provides communication services between application programs and terminals.</p><p>Task Control Program (KCP): It is used to control the execution of tasks simultaneously and their related properties.</p><p>System Initialization Program (SIP): It is used to initialize the program in the communication area.</p><p>Transient Data Control Program (TDP): It allows application programs with the ability to store and retrieve data from Transient Data Queues.</p><p>Storage Control Program (SCP): It is used to control the allocation and deallocation of storage within the CICS region.</p><p>Apart from these control programs in CICS, there are some other programs that CICS uses.</p><blockquote>Data Entry Programs (These programs accept input data from user and use it to update the files after validating the data entered)</blockquote><blockquote>Inquiry Programs (These programs can provide response to a user’s inquiry)</blockquote><blockquote>File Maintenance Programs (These programs can update a file by adding, changing or deleting records)</blockquote><blockquote>Menu Programs (These programs allows the user to select a particular function)</blockquote><p>One more important topic in CICS is multi-tasking.</p><h4>What is multi-tasking?</h4><p>The answer is pretty straightforward. Handling multiple tasks at a time. Wow ! Easy! But what is a task in CICS?</p><p><em>A task is nothing but an instance of the execution of a particular transaction type.</em></p><p>For e.g., Let us say 100 users execute a transaction, and then 100 tasks are created. It means the OS allows more than one task to be executed concurrently, regardless of whether the task uses the same program or different programs.</p><p><em>Multi-Threading means multiple users execute a single program concurrently.</em></p><p>Next we have to know how does communication happens in CICS. There are two modes.</p><blockquote>Conversation Mode- It means sending a message to the terminal and wait for the user to respond. Since there is waiting time, the computer resources are wasted.</blockquote><blockquote>Pseudo Conversation Mode- It means sending a message to the terminal and the control does not wait for the user to respond, instead it is sent to some other task. Since there is no waiting time, the resources are used optimally.</blockquote><h4>BMS role in CICS</h4><p>BMS(Basic Mapping Support) is provided by CICS to help you define and format screens. The screen is developed with a MAPSET.</p><blockquote>Mapset: Collection of maps link-edited together to create a load module. DFHMSD is the macro which defines a map set.</blockquote><blockquote>Map: It is a single screen format. DFHMDI is a macro that defines a map. A map is a collection of Fields and the macro to define fields is DFHMDF.</blockquote><p>BMS acts as an interface between the CICS program and the Terminal Device.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/766/1*J3ZkN8D27glwQjxjWsoSrw.png" /><figcaption>Map Definition in MAPLIB</figcaption></figure><p>Now that you know the basics, I will try to explain small programs and navigation in CICS screens in future.</p><p><strong>Please stay tuned to know more interesting topics in the next blog.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bce73d7356c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wanna know about Risk ???]]></title>
            <link>https://swathi-javvaji.medium.com/wanna-know-about-risk-11cb6c53a116?source=rss-229aa231b240------2</link>
            <guid isPermaLink="false">https://medium.com/p/11cb6c53a116</guid>
            <dc:creator><![CDATA[Swathi Javvaji]]></dc:creator>
            <pubDate>Wed, 10 Feb 2021 15:33:15 GMT</pubDate>
            <atom:updated>2021-02-11T08:01:45.264Z</atom:updated>
            <content:encoded><![CDATA[<h3>Wanna know about Risk ???</h3><p>Now that most of the teams are done with PI Planning, let’s discuss one topic that was heard by everyone and often ignored. Risk 😒</p><h4>So what exactly is risk and how to manage it?</h4><blockquote><strong>Risk :</strong> Risk is the uncertainty on the achievement of the stated objectives. The word ‘risk’ can create some level of fear or anxiety as they are unknown and uncertain.</blockquote><p>However it is an iterative process. It has to be managed appropriately with a contingency plan.</p><p>One has to know that positive risk is an opportunity and positive &amp; negative risk can emanate from an uncertain future event.</p><blockquote><strong>Risk Management:</strong> The systematic application of management policies, procedures, and practices to the tasks of establishing the context, identifying, analyzing, assessing, treating, monitoring and communicating risks with a view to reducing the negative or alternatively enhancing the positive impact on the organization.</blockquote><p>Effective risk management builds confidence for all the stakeholders involved.</p><p>A key purpose of risk management is to identify potential opportunities or problems before they occur, so that risk management activities may be planned and implemented as needed across the life cycle of the project in order to leverage opportunities and mitigate adverse impacts.</p><p><strong>What and how can we know about risk management?</strong></p><p>The answer is pretty simple. Using the risk management canvas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*MvXl4_JlFsXxZA9DKmR3dQ.png" /><figcaption>Risk Management Canvas</figcaption></figure><p><strong>1. Context and Objectives:</strong></p><p>First establishing the context is where formal determination or articulation is made as to where you propose to apply the risk management process.</p><p>SMART way of finding the context of risk:<br>S — Specific<br>M — Measurable<br>A — Aligned<br>R — Realistic<br>T — Time bound</p><p>Now that we know the context, time to identify the types of risks.</p><ol><li>Strategic and Compliant Risks</li><li>Operational Risks</li><li>Potential Risks</li><li>Technical Risks</li><li>Financial Risks</li></ol><p><strong>2. Risk Identification:</strong></p><p>It is a systematic and detailed approach to ensuring that as many risks as possible are identified with the collaboration of stakeholders to ensure that they can be analyzed and responded to appropriately. It is a skill that improves through experience and practice. Identifying risks and potential risks is key to effective risk management.</p><p>Tools to categorize risk is PESTLE.</p><blockquote><strong>P</strong>:Political,<strong>E</strong>:Economic,<strong>S</strong>:Social,<strong>T</strong>:Technological,<strong>L</strong>:Legal,<strong>E</strong>:Environmental</blockquote><p>Different ways of identifying risk :</p><p>a. The Delphi technique: a way to reach consensus through the use of experts on a particular subject area, such as project risk.</p><p>b. Checklists for risk identification.</p><p>c. Diagramming techniques (Ishikawa / Fishbone Diagram, Process flowchart, Influence Diagram).</p><p>Project Managers (in some cases project team members, business owners and external stakeholders) identify risk and develop the risk register. A risk register contains description of the risk, causes and consequences of the risk and finally the existing internal controls that may reduce the likelihood or consequences of risks.</p><p><strong>3. Risk Assessment :</strong></p><p>We need to consider two key dimensions:</p><blockquote>First : It requires an analysis and assessment of the likelihood or possibility of the risk occurring. Second: It is what the consequence or impact may be on you achieving your project objectives, if those risks occur.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/383/1*Njs7WowyaZg42pAcH3kvCQ.png" /><figcaption>Risk Assessment Matrix</figcaption></figure><p>A widely used principle for determining criteria for acceptable risks is ALARP (As Low As Reasonably Practicable) principle.</p><p><strong>4. Risk Response: 4 T’s (Take , Treat, Transfer, Terminate)</strong></p><p>a. Taking the risk means accepting the gross risk.</p><p>b. Treating the risk means putting into place actions or controls that are aimed at reducing that risk/ mitigating the risk .</p><p>c. Transferring the risk means assigning responsibility of that risk to another party such as contractor or agency, who will then become responsible for dealing with it.</p><p>d. Terminating the risk means eliminating it completely. This can be done by changing an inherently risky process or practice to remove the risk,e.g., changing the project scope.</p><p>When implementing a treatment plan, ensure to have adequate resources, time frame, responsibilities and methods.</p><blockquote><strong>Risk Ownership:</strong> It is incremental in ensuring an identified risk is managed, monitored and controlled throughout the risk management process, which makes it a dynamic and continual process. The risk owner should be capable of managing the risk and have the knowledge , resources and authority to deal with the risk.</blockquote><p><strong>5. Communication :</strong></p><p>When reporting risks, it is important to identify key risks in the project, explain why these risks are critical, explain risk responses for critical risks, identify any emerging critical risks.</p><p><strong>6. Monitor and Review: (Continual Process)</strong></p><p>The Risk Management Plan typically includes:</p><p>The process to identify, analyze and treat risks and estimated costings. The process to transfer approved risk costings. The process to transfer risk mitigation strategies. How often the Risk Register will be reviewed, the review process and who will be involved. Who will be responsible for which aspects of risk management. How Risk Status will be reported and to whom. A snapshot of major risks, current risk levels, planned response strategies and costings together with who will be responsible for implementing these strategies.</p><p>Now that we have a picture about what is risk, and how to identify and also how to especially deal with different kinds of risks, lets plan our next quarters with a plan. 😊</p><p><em>Some useful definitions:</em></p><p><strong>Negligible Risk :</strong> These are broadly accepted by most people as they go about their everyday lives such as minor illness or minimal environmental damage.</p><p><strong>Tolerable Risk :</strong> They would rather not have this risk, but it is tolerable in view of the benefits obtained by accepting it. The cost in inconvenience or in money is balanced against the scale of the risk and a compromise is accepted such as injury that incurs a loss of one or more work days.</p><p><strong>Unacceptable Risk :</strong> The risk level is so high that we are not prepared to tolerate it. The losses far outweigh any possible benefits in the situation such as partial permanent disability.</p><p><strong>Residual Risk :</strong> The revised level of risk that is left over. It is the risk that remains after taking controls or treatment actions into account.</p><p><strong>Gross Risk :</strong> It is the assessed risk level achieved and assumes that there are no controls or treatment actions already in place such as closure of business or loss of life.</p><p><strong>Risk Appetite:</strong> The amount of risk a project manager will accept in meeting the project’s objectives.</p><p><strong>Quantitative Risk Assessment :</strong> It is the process of providing numerical or statistical estimates of the overall effect of risks on the project objectives when all the risks are considered simultaneously.</p><p><strong>Qualitative Risk Assessment :</strong> It has certain series of events such as identifying the risks with the robust information and assessing them, later determining the likelihood and consequences of each of those risks and finally by determining the overall risk level by risk management matrix.</p><p><strong>Risk Assessment Record</strong>: It serves as a purpose to remind the priority hazards, standards to be maintained and what action has been taken or still needs to be taken.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11cb6c53a116" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is it worth using VSAM over Sequential files in COBOL ?]]></title>
            <link>https://swathi-javvaji.medium.com/is-it-worth-using-vsam-over-sequential-files-in-cobol-eb254df03803?source=rss-229aa231b240------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb254df03803</guid>
            <category><![CDATA[mainframe]]></category>
            <category><![CDATA[cobol]]></category>
            <dc:creator><![CDATA[Swathi Javvaji]]></dc:creator>
            <pubDate>Wed, 06 May 2020 12:47:17 GMT</pubDate>
            <atom:updated>2020-05-06T12:47:17.531Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Is it worth using VSAM over Sequential files in COBOL ?</strong></h3><p>Who might have thought I would blog one day! I want my first blog to be a special one. So why not choose the most favorite thing in the world. It is mainframes, yeah !</p><p>During the short span of me being a mainframes developer, I always had this tendency to seek a happy path to accomplish things. Then I changed my career path to a QA, then to BA and then to Systems Programmer working on distributed systems and became a stranger to mainframes . I thrive on learning new things and accepting new challenges. When I got a chance to work on Mainframes recently as part of some research in my project, being a great fan of mainframes, in spite of not knowing much about COBOL and VSAM , I gladly accepted the challenge.</p><h4>My experience with VSAM :</h4><p>I have coded small JCLs for creating VSAM files during my mainframe training without giving much thought about advantages and disadvantages of VSAM.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*axaYrIE4yFwnYBLsMLOhBg.jpeg" /><figcaption>Definitely not like this</figcaption></figure><h4>How did the need arise ?</h4><p>Our team is working on a batch application and we wanted to try if it would be possible to make the application robust without changing the functionality. The application was entirely coded using sequential datasets.The suggestion to introduce VSAM in the application popped up.</p><h4>What did the QA in me advise ?</h4><p>Since it was mainframes, I (the developer side)came forward to take the research . But he QA in me is always pessimistic. So I find ways to first prove why that might be a bad idea. Started researching for disadvantages.</p><p>To my surprise, there are very few disadvantages when compared to advantages.</p><h4>Disadvantages of VSAM :</h4><p>• VSAM Datasets require more storage space compared to other type of<br>datasets due to Control Information (CI) present in them.<br>• VSAM can’t be stored in TAPE Volume i.e., VSAM Stored only in DASD<br>• We can’t browse, view, edit the VSAM datasets in ISPF.<br>• VSAM is not a database like DB2, IMS DB &amp; IDMS.</p><p>Then started my actual research for the change.</p><h4>What is a sequential dataset ?</h4><blockquote>In a sequential data set, records are data items that are stored consecutively.</blockquote><p>Creation of sequential dataset is pretty simple and straight forward.</p><p>In JCL :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/613/1*CZSGrUWDjPZgfF5Qq33_oQ.png" /></figure><p>In COBOL :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/332/1*4bv083JRfPqymwgW-gIcmA.png" /></figure><h4>What is a VSAM dataset and VSAM access method ?</h4><blockquote>VSAM datasets are described as four datatypes : KSDS, ESDS, RRDS and LDS</blockquote><blockquote>Key Sequence Data Set (KSDS):This type is the most common use for VSAM. Each record has one or more key fields and a record can be retrieved (or inserted) by key value. This provides random access to data. Records are of variable length.</blockquote><blockquote>Entry Sequence Data Set (ESDS):This form of VSAM keeps records in sequential order. Records can be accessed sequentially.</blockquote><blockquote>Relative Record Data Set (RRDS):This VSAM format allows retrieval of records by number; record 1, record 2, and so forth. This provides random access and assumes the application program has a way to derive the desired record numbers.</blockquote><blockquote>Linear Data Set (LDS):This type is, in effect, a byte-stream data set and is the only form of a byte-stream data set in traditional z/OS files .</blockquote><h4><strong>Why use VSAM instead of sequential ?</strong></h4><ul><li>VSAM improves efficiency.</li><li>Supports more dataset types and variety of I/O techniques.</li><li>Records can be retrieved using VSAM access method (without having to process the preceding records).</li><li>Inserting data is faster and easier due to embedded free space in the cluster.</li><li>Records can be sequentially and randomly.</li><li>Supports online and batch.</li><li>Deletion of records results in them physically removed from DASD.</li></ul><h4>My changes :</h4><p>I did minor changes in JCLs and COBOL programs wherever needed .</p><p>In JCL : The cluster creation of VSAM was tricky.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/611/0*9n15h_ohWmP3oaXn" /></figure><blockquote>IDCAMS utility :</blockquote><blockquote>Utility programs are pre-written programs, widely used in mainframes by system programmers and application developers to achieve day-to-day requirements, organizing and maintaining data. IDCAMS utility is used to create, modify and delete the VSAM datasets.</blockquote><p>In COBOL : We have to declare the file inside the COBOL program as INDEXED for VSAM.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/417/0*XTDs--6bTgzLcA1w" /></figure><blockquote>File Extended Status :</blockquote><blockquote>Extended file status codes use the second byte as a binary (COMP-X) item. Extended file status codes have the character “9” in the first byte. The second byte is a binary (COMP-X) number, which is equivalent to a run-time error number.</blockquote><h4>Some observations :</h4><blockquote>Tip 1 : It is a wise idea to delete the cluster in JCL before creating it (if you run the JCL second time, it might throw a JCL error indicating the existence of dataset).</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/627/0*2dlyv1BhyyouJZ7b" /></figure><blockquote>Tip 2 : Do not forget to add the extended status of file in the file section.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/444/0*Dg7oCRQCN724w_cq" /></figure><h4>The Enhancements :</h4><p>Once the application is changed to using VSAM datasets, we have faster access to the datasets and we could store the data in an organized and structured way. At the end , it was worth experimenting new changes in our application and blogging about it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb254df03803" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>