Welcome
Problem determination procedures
If you have to contact IBM® personnel about a CICS® VR problem, you must classify and describe the problem.
Collecting information about specific problems
After you have chosen a problem-type keyword, use the following procedure to collect problem documentation.
Loop procedure (LOOP)
Use the LOOP keyword to specify a LOOP problem.

What's new in CICS VR 6.1
CICS® VR 6.1 contains these changes.
Operating environment
CICS® VR uses logs to recover your VSAM data.
CICS VR Overview
Getting Started
CICS® VR and CICS® TS
CICS VR Exits
Running CICS® VR forward recovery
CICS® VR forward recovery consists of a restore and then forward recovery.
Running CICS® VR backup
The information in the following topics describe how to take a backup using CICS® VR. The panels and secondary windows are in the sequence that they are displayed during a backup job generation.
Running CICS® VR reorganization
You can reorganize a VSAM sphere using CICS® VR. VSAM sphere reorganization can increase the space of a sphere and its alternate indexes. It can also change the control interval sizes for a sphere's components.
Working with other VSAM sphere list pull-down menus
The CICS® VR recovery and backup functions are typically accessed using the Utilities pull-down menu after selecting VSAM spheres.
Working with CICS® Backout Failed spheres
The CICS® Backout Failed sphere list shows the CICS spheres registered for manual recovery or reorganization after CICS notification of a backout failure.
Working with logs
Using ISMF data set lists with CICS® VR
CICS® VR is integrated with ISMF so that you can create a CICS VR recovery job for the data sets in an ISMF data set list by entering the VSAMREC line operator or list command. When you enter the VSAMREC line operator or list command, the necessary CICS VR panels are called and you can create a recovery job for the VSAM sphere.
Running CICS® VR manually
IBM® recommends that you use the CICS® VR panel interface to create recovery jobs for your VSAM spheres. Using the CICS VR panel interface eliminates the need for you to manually keep track of daily update activity, logs, backups, etc. Also, the CICS VR panel interface automatically creates the recovery JCL for you.
Running CICS® VR batch backout
The CICS® VR batch backout utility allows you to remove updates that were made to KSDS, ESDS, RRDS, and VRRDS VSAM spheres by steps in a batch job. This section describes how to run the CICS VR batch backout utility.
Understanding CICS® VR reports
The CICS® VR forward recovery and batch backout utilities produce a set of reports upon successful completion. The reports are written to the data set allocated to the DWWPRINT ddname. However, the set of reports written for the forward recovery backout utilities differ from the set of reports written for the batch backout utilities.
Understanding IBM® program support
The IBM® Customer Engineering Program Support structure helps you resolve problems with IBM products, and ensures that you can make the best use of your IBM computing systems.
Problem determination procedures
If you have to contact IBM® personnel about a CICS® VR problem, you must classify and describe the problem.
- Classifying a problem
  The first step in diagnosis is classifying the type of problem. Symptoms that suggest the presence of a problem can be valuable clues in diagnosing and solving the problem.
- Collecting information about any problem
  Follow these procedures to collect information about any problem and to collect information about an unidentified problem.
- Collecting diagnostic information
  You can improve the efficiency of this process by preparing and sending the correct diagnostic information when you initially report the problem. Depending on the type and complexity of a problem, the IBM® Support Center might require you to send certain information to help diagnose and resolve the problem.
- Tracing in the CICS® VR server address space
  DFSMSdfp™ provides a trace service for use with CICS® VR server. A special trace table is created in CICS VR server address space and in each address space where CICS VR client applications are run and tracing is selected.
- Collecting information about specific problems
  After you have chosen a problem-type keyword, use the following procedure to collect problem documentation.
  - Abnormal end with a system abend code procedure (ABEND)
    Use the ABEND keyword to document a problem when CICS® VR abends with a system abend.
  - Abnormal end with a user abend procedure (ABENDU)
    Use the ABENDU keyword to document a problem when CICS® VR abends with a user abend.
  - Incorrect output procedure (INCORROUT)
    Use the INCORROUT keyword to document a problem with output.
  - Loop procedure (LOOP)
    Use the LOOP keyword to specify a LOOP problem.
  - Message procedure (MSG)
    Use the MSG keyword to specify a message failure.
  - Performance procedure (PERFM)
    Use the PERFM keyword to specify a performance problem.
  - Wait procedure (WAIT)
    Use the WAIT keyword to specify a WAIT problem.
- Collecting documentation about all problems
  Gather certain information for any problem, even when you cannot identify the type of problem. Record the information on a copy of the worksheet.
- Problem description worksheet
  You can print this worksheet for your use.
Diagnosing the causes of abends
You can determine the cause of a CICS® VR abend in a number of ways.
Reference information
The reference sections of the information contain reference information that you need when you use CICS® VR.
Glossary
The terms in this glossary are defined as they pertain to the CICS VSAM Recovery documentation.
Edition notice
This is the information for CICS VSAM Recovery for z/OS. It applies to CICS VSAM Recovery for z/OS Version 6.1, and to all subsequent versions, releases, and modifications until otherwise indicated in new editions. Make sure you are using the correct edition for the level of the product.
Download PDF
Download the PDF format documentation for CICS VSAM Recovery for z/OS 6.1

Loop procedure (LOOP)

Use the LOOP keyword to specify a LOOP problem.

If new output is being produced in the DWWPRINT file, CICS® VR is not in a loop.

If CICS® VR has ended, the loop is probably recursive: module A calls module B calls module A, and so on. The abend is caused by CICS® VR running out of automatic storage producing user abend code 3001. Loop problems can involve many modules or a single module. Look for messages that are associated with the loop.

If CICS® VR is still running in a loop perform these steps:

Cancel CICS® VR, using the dump option.
Search for repetitive patterns of called modules, using the trace table.
If there is no repetitive pattern, rerun CICS® VR, repeat steps 1 and 2, and compare the trace tables.
Provide a description of the situation leading up to the problem.

See Collecting documentation about all problems to complete your documentation of the problem.