CA-View (SAR)

Title CA-View (SAR)

Platform All z Systems

Purpose To provide an alternative method of storing computer output.

Source Computer Associates International, Inc.

Access TSO CLISTS, CICS Cross-memory services, ISPF menu select

CA-View (Formerly known as SAR), a SYSOUT Archival and Retrieval

system, is a facility for storing and retrieving computer output.  Clients
should consider CA-View as an alternative to storing listings for their
retention needs.  Since any computer output can be specified for archival,
CA-View is especially well-suited to the management of production JCL
listings and production reports.  CA-View is available on the Rancho
Cordova and Vacaville z Systems through specific individualized CA-View
database repositories based on client departments.  Although the main
purpose is to provide an alternative method of storing and retaining
computer output, CA-View may also be used for AFP to PDF
transformation and PDF collection for output that will also be stored in the
CA-View database.  The storage and retention specifications of output are
dependent upon the needs of the client CA-View database repositories. 
Typically, each day is considered a generation.

Computer outputs may be placed in the CA-View database repositories by

the specification of output class and/or DEST parameter in their batch job
JCL.

SAR is an add-on product, for IBM mainframes, to start with. It is now known as CA-View. As
you might know ,it's a SYSOUT Archival and Retrieval system, is a facility for storing and
retrieving computer output. According to CA' website -- Customers should consider CA-View as
an alternative to both listings and microfiche. Although any output can be specified for
archival, CA-View is especially well-suited to the management of production JCL listings and
production reports. All output archived to CA-View during a given day constitutes one
generation of CA-View data. Currently, four generations (i.e., four days) of CA-View data are
maintained on disk. During the daily CA-View backup cycle, which runs at midnight, the oldest
disk generation is archived to tape (where it remains for approximately one year before being
deleted) and a new disk generation is created.

SYSOUT JCL Examples:

SYSOUT DD Statement:

//REPORT3 DD SYSOUT=G

MSGCLASS Parameter:

//jobname JOB (acct info),name-phone#,MSGCLASS=G

SYSOUT DD Statement with reference to OUTPUT statement:

//OUT1 OUTPUT JESDS=ALL,DEFAULT=Y,DEST=defined dest

//REPORT3 DD SYSOUT=(,),OUTPUT=(*,OUT1)

OUTPUT Retrieval within CA-View database repositories

After the output has been archived to a CA-View database repository. 

The clients can access their outputs via TSO CLISTS, CICS Cross-memory
services, ISPF menu selections, or WebViewer (URL).

Upon accessing a CA-View database repository, the user will be presented

with the primary CA-View selection menu. The first field on the selection
menu is SYSOUT ID, which by default is the same as the jobname. A
partial jobname, such as DCCBA*, can be entered. This would select all
archived jobs that begin with the characters ‘DCCBA’. The SYSOUT ID
field is optional – leaving it blank will result in selecting all jobs that meet
the other selection criteria.

NOTE: Specifying all or even part of the SYSOUT ID will speed up the
search of CA-View’s database for eligible archived output, particularly
when that database contains a significant number of jobs.
In addition to SYSOUT ID, you may enter selection criteria for the
GENERATION or the DATE. For GENERATION, you can enter a generation
number or range of generation numbers (e.g. 640:643). CA-View assigns
a sequential generation number for each day. You can alternatively enter
a relative generation number or range of numbers (e.g., a range of -3::0
would cover all jobs archived during the period beginning 3 generations
ago through the current generation). Specifying * or ALL in the
GENERATION field will return a list of all eligible jobs in the CA-View
database that the user is authorized to browse. Rather than filling in the
GENERATION field, you can use the DATE field, entering a given date in
mm/dd/yy format or a range of dates, such as 01/06/05:02/26/05. A
relative date or range of dates can also be specified. If nothing is entered
in either the GENERATION or the DATE fields, only the current generation
is searched for eligible archived output.

Once the selection menu is completed, a list of jobs that meet the
selection criteria will be displayed.  Depending on the CA-View database
repository, there are different security mechanisms that are deployed. 
These will determine whether the user can do within a given CA-View
database repository.

Example

SYSOUT ID ===> DC*

GENERATION ===> -10::0

CA-View might then display a panel such as the one shown below:

VIEW 12.0 ALL————– SYSOUT SELECTION LIST ———————

COMMAND ===> SCROLL ===> PAGE

SEL ID JOBNAME JOBID ARC DATE ARC TIM

DCAMPLE DCAMPLE J4367 06/10/04 18:22:17

DCTEST1 DCTEST1 J6461 06/08/04 01:02:45

DCTEST2 DCTEST2 J1334 06/01/04 15:32:29

For each selected job, CA-View displays the archival date and time, the
current location of the archived output, the number of print lines and
pages, and the exception code (if any). Possible exception codes may
include SB37, U0024, 0016 (condition code), and JCLERR.

The SEL column at the far left of the display provides an area for CA-View
line commands.

Following are some of the more commonly used line commands:

S – Browse the output.

L – Load the output. This command is used to copy output that has
already been archived to tape into a temporary disk file so the output can
be browsed. A batch job is created to perform the copy operation. You will
be prompted for a JOB statement the first time this command is used.

CA-View will retain this JOB information for all subsequent loads. The
copied output will remain in the temporary disk file until the next CA-View
backup cycle.

J – Print the output. A batch job will be submitted.

D – Delete the output. This job will be removed from the CA-View index
and the output will no longer be available for retrieval. A confirmation
panel is provided to prevent inadvertent deletes.

Reference Manuals

CA-View reference manuals are available in PDF form upon request.

Accessing Output Management Reports
To access CA Deliver reports, use one of the following CA View online processing modes:
■ CA Deliver mode (EXP)—report viewing and printing for the end user. Command: Mode EXP

■ CA Deliver Operations mode (EXPO)—report viewing and printing for the operations or production control
user. Command: MODE EXPO
■ ALL mode (ALL)—report viewing and printing for the master user. Command: MODE ALL

Note: For more information about processing modes, see the chapter "User Modes: Initiating Output
Retrieval."

Modes:
This section explains the user modes: ALL, EXPO, EXP, JOB, SARO, and SAR. These modes let you access
SYSOUTs, reports, and jobs for viewing, printing, and emailing. Two of these modes (EXP and SAR) handle
private SYSOUT groups and reports.

A private SYSOUT group or report has one or more distribution identifiers (DIST IDs) linked to it. Only users
who have linked DIST IDs can access that data. Private report viewing is the ability to verify DIST IDs of online
users before the report selection lists are displayed. This ability provides a security level of the displayed
selection list for users.

ALL Mode
Lets you retrieve any archived SYSOUT or any archived CA Deliver reports. No SYSOUTs or reports are
restricted, unless by other security (for example, RACF).

EXPO Mode
Specifies CA Deliver Operations (EXPO) mode. Use this mode to access all reports archived from CA Deliver.
Archived reports initially processed in CA View are not available through this mode.

EXP Mode
Specifies CA Deliver (EXP) mode. Use this mode to access reports that have been archived from CA Deliver and
that are available to your distribution identifier (DIST ID). Archived SYSOUT initially processed in CA View is not
available through this mode.

JOB Mode
Lets you access all archived SYSOUT for each occurrence of each job.
To obtain a list of all jobs that match your selection criteria, type data in one or more of the JOB mode
selection criteria fields and press Enter.
Important considerations follow for JOB mode:
■ Reports are viewable if they were archived via SARSTC, SARFSS text collector, SARXTD, or SARDBB.

■ Binary, AFP, PDF, Xerox, and CA Deliver reports are not viewable.

■ JOB mode access is not available through CA OM Web Viewer. A user can log off from CA View in JOB mode
from the mainframe and later attempt to access CA View again through CA OM Web Viewer. In that case, CA
View checks the mode access indicators for the user and assigns the first mode that permits access. If the user
is authorized for JOB mode only, access is denied with this message in CA OM Web Viewer: "Userid denied.
JOB mode access only. Contact your CA View Administrator." The message prefix in the CA DRAS log is
CAHADOP08.
Introducing Basic Elements
This list introduces some basic terms.
Distribution ID (DIST ID)
The 1- to 32-character name assigned to a distribution point
Reports archived from CA Deliver have a DIST ID automatically linked to them. SYSOUT (not from CA Deliver)
must be assigned a DIST ID by a CA View system administrator.
Report ID (REPORT ID)
A 1- to 32-character name assigned to an individual archived report originating from CA Deliver
The REPORT ID is assigned at the time the report is processed by CA Deliver.
Note: For more information about valid characters, see the table in the next section.
SYSOUT Group
One or more SYSOUT data sets with the same SYSOUT ID (see below)
An example is multiple data sets that are all products of one job (JOB name or JOB statement).
SYSOUT ID
The 1- to 32-character name assigned to a SYSOUT group.

Taking an SNAP of data from CA-View screen to a dataset:

1. Type J infront of the SAR entry that u want to make to a dataset. The

Print Attribute Panel manu appears.
2. In the Print Attribute Panel,
give,
CLASS ===> R
(for me the IOF is routed in CLASS R. Hence I have used it. You can specify your IOF-SDSF
Spool Class here and press Enter.)

You will be retruned to the SAR details page again. In the top left you shud get a message
saying "JCL created"
3. Give the command SUB on the command prompt of that page itself.

This should take you to BATCH JOB JCL. In the menu give the correct job card and press
Enter.
This will submit a job and the job will be in IOF(SDSF Spool).
4. The next step for snapping inot the dataset is, Exit from SAR and go to IOF(SDSF Spool).
5. Select the output job in IOF(SDSF Spool). Select the output file you want to make into
a dataset.
6. Go to the page of the report that you want to have at the beginning of the dataset.

Determine how many lines of the report you need to have sent to a dataset. In this
example, we'll say 1,000 lines. (You can snap a maximum of 999,999 lines.) You need to
select a size large enough to hold all lines in the report.
7. Type SD at the top of the screen and press enter.

In IOF Snap Dataset Options, set the DSNAME parameter. The default is

JOBNAME.IOFLIST. If you leave this set to default, the full dataset name that will be
created will be TSO-ID.JOBNAME.IOFLIST.

Set RECFM to FBA (FB if you don't want an ASA character to be included in the file).
Set LRECL to 133 (or whatever the report format is).
Set BLKSIZE to 1330 (or whatever blocksize is appropriate for the record size).
8. Press enter.
9. Type 'SNAP 1000', and press enter. (Leave out the comma.)
10. Exit IOF(SDSF Spool) entirely. Your dataset won't be populated until you exit from
IOF(SDSF Spool).
11. Look in 3.4 and you will see the dataset TSO-ID.JOBNAME.IOFLIST.[/list]